In linux the distinction between the operating system and the applications is a little bit blurred.
The technically linux part is the kernel, the basic bit that interacts with the hardware. What we casually refer to as linux, is the
GNU operating system running on top of the linux kernel. GNU coreutils provides all the basic core utilities and tools, coping files, moving files, and such. But there is no reason the two have to be paired. Debian has a project where they are running with
FreeBSD kernel, instead of a linux kernel.
Distros take all the components, mix em together, and put out a release. They might include custom patches to software, or custom software created by the project, they'll have built the kernel with custom options or patches, there are a lot of little under the hood tweaks that can happen. And when they package all this different software, they need to make sure it all works together.
A distro like Slackware does very little custom patching. They pretty much package software as released from the upstream developers. They also don't have a lot of graphical configuration tools. Everything is done by hand editing config files. And famously, their basic package manager doesn't resolve dependencies.
I was the one who recommended Arch to you, primarily based on the package management. Really, manual dependency resolution is a pain in the you know what. On the other hand, Arch does not auto-configure some things that slackware does, leaving it up to user choice.
Quote:
|
I want to learn the original true Linux way.
|
I'm not sure there is such a thing. Linux is very customizable. The point is, any particular user can find a system that works for them. If you like having a lot of control over the nitty gritty bits of the system, go Arch, Slackware, Gentoo, or Crux. If you just want a system you can plug in and start surfing the web for celebrity gossip, go Ubuntu, Mint, or OpenSuse.
But whatever you go with, all distros offer you the power to get under the hood and fiddle. You can accomplish any task on the command line that you could in a GUI, sometimes things are easier from the CLI, sometimes things are better suited to a GUI.
About 6 months ago I did a little experiment for a while, where I ran without a GUI. Read about it here.
http://www.linuxforums.org/forum/cof...ine-tools.html