Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
General Unix Finally something really interesting to talk about. If you've used UNIX or any of its derivatives, you've probably wondered why there's /bin, /sbin, /usr/bin, /usr/sbin in the file system. You may even have a rationalisation for the existence of each and every one of these directories. The thing is, though - all these rationalisations were thought up after these directories were created. As it turns out, the real reasoning is pretty damn straightforward.
Permalink for comment 505211
To read all comments associated with this story, please click here.
RE[4]: Wow, That Was Simple
by leech on Mon 30th Jan 2012 23:15 UTC in reply to "RE[3]: Wow, That Was Simple"
leech
Member since:
2006-01-10

"/users
/system
/programs (or /Apps, in this day and age).

More is not needed at root.



That looks a lot like:

Documents and Settings
Windows
Program Files


Just sayin'
"

Yeah, and those that actually have to dig through file locations occasionally find the "windows way" a nightmare! I need to find where a file is on Linux? There are a ton of ways. I need the actual location of an executable? Use 'which <program>' and it'll show you the full path. You need to know what package a file belongs to? dpkg -S <filename> (at least on Debian based distributions.)

The Windows way is a mess, because while you have Program Files or Program Files (x86), not all installers default to put things there, and even then you can change the default so not all systems will have files in the same place.... Then you have the fact that some installers want to put the company name in there, so you end up getting a huge mess. A good example is Steam. C:\Program Files (x86)\Steam\SteamApps\common\rainbow six 3 gold\Mods\ is where I have to install mods to. Not all mod installers detect where it is installed, so I manually have to drop files in there.

Far easer to have /usr/games/doom/ and throw the files in there, wouldn't you say?

Reply Parent Score: 5