Comment Yawn. Duh. (Score 1) 269
While we're stating the obvious for attention, let me join in.
Programs and files in your unix-style computer do not grow on trees. There is a purpose to each and every file in your filesystem, and they all have sources.
The kernel, and all the files that make up the kernel are packaged by the kernel authors.
The shell, of which you can choose from dozens, are packaged by the creators.
The little dipshit programs like cat, du, whatever generally come from some major FSF-written program bundles. Textutils, shutils, binutils, diffutils, fileutils, and findutils come to mind.
make, m4, and other packages provide tools for compiling things.
GCC is a collection of tools and compilers and programs that enable software of many different languages to be compiled, analyzed, and changed.
This is a rudimentary list, There are many more things I have neglected to mention that your computer comes with.
X11 brings dozens of programs and resource files and libraries with it.
Your desktop environment(s) bring multiple thousands of libraries, binaries, and configuration files to the scene.
Applications bring thousands of files of their own.
Just because binaries tend to be thrown into a common location (/usr/local/bin) doesn't mean they're an amorphous blob called UNIX.
Don't forget servers, scripting languages, games, all the other crap that makes things fun.
It is a testament to the Unix project that with merely a functioning kernel, a terminal driver, a shell, and a few dozen one-trick-pony 'applets', profoundly neat things can be accomplished.
If you are bored, play with these commands.
'type somecommandhere'
Likely, you will be shown what binary is actually run when you type in that command.
'alias' might tell you "secret" aliases that have been set up to make the command line more useful.
If you have an RPM-based system, you can try 'rpm -qf /somedir/somefile' to see where the file in question came from.
'rpm -qa' will tell you all the packages installed on your system.
My penis hurts.
Programs and files in your unix-style computer do not grow on trees. There is a purpose to each and every file in your filesystem, and they all have sources.
The kernel, and all the files that make up the kernel are packaged by the kernel authors.
The shell, of which you can choose from dozens, are packaged by the creators.
The little dipshit programs like cat, du, whatever generally come from some major FSF-written program bundles. Textutils, shutils, binutils, diffutils, fileutils, and findutils come to mind.
make, m4, and other packages provide tools for compiling things.
GCC is a collection of tools and compilers and programs that enable software of many different languages to be compiled, analyzed, and changed.
This is a rudimentary list, There are many more things I have neglected to mention that your computer comes with.
X11 brings dozens of programs and resource files and libraries with it.
Your desktop environment(s) bring multiple thousands of libraries, binaries, and configuration files to the scene.
Applications bring thousands of files of their own.
Just because binaries tend to be thrown into a common location (/usr/local/bin) doesn't mean they're an amorphous blob called UNIX.
Don't forget servers, scripting languages, games, all the other crap that makes things fun.
It is a testament to the Unix project that with merely a functioning kernel, a terminal driver, a shell, and a few dozen one-trick-pony 'applets', profoundly neat things can be accomplished.
If you are bored, play with these commands.
'type somecommandhere'
Likely, you will be shown what binary is actually run when you type in that command.
'alias' might tell you "secret" aliases that have been set up to make the command line more useful.
If you have an RPM-based system, you can try 'rpm -qf
'rpm -qa' will tell you all the packages installed on your system.
My penis hurts.
