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.
Thread beginning with comment 505219
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Thom is right
by leech on Mon 30th Jan 2012 23:40 UTC in reply to "Thom is right"
leech
Member since:
2006-01-10

Really... Am I the only one, who thinks that all what Thom said is correct? I mean, the directory structure on unix and linux is shit. Really. This is the only word, that is as precise as possible to describe it.

I mean, when making it like
/apps
/user
/systems

How easy would it be to build on that? I mean, there is no good reason to make a directory system like that, with virtual links for programs, which needs the /usr /bin and so on stuff


Yes, you are the only one ;)

The symbolic links for everything that Fedora is doing is retarded. Every package managed program goes into the proper /usr/bin, the data into /usr/share/<packagename>/ and documentation goes into /usr/share/doc/<packagename> how hard is that? Then anything you compile yourself gets put into /usr/local/bin with data going to /usr/local/share. Granted, you can change this in the configure scripts, but that is the default.

Makes total sense.

Reply Parent Score: 2