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 505255
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: why not / instead of /usr
by jimmmy on Tue 31st Jan 2012 08:17 UTC in reply to "RE: why not / instead of /usr"
Member since:

Of course, that would break just about every piece of software out there that expects to install to /usr.

Which would be mostly proprietary software which can't be rebuilt. The bulk of open source software that I've seen can be fixed by telling the build system where to put it. I don't see much of any reason why software shipped with a distribution would be affected much at all by this change.

Most closed source software that I've encountered doesn't care where you run it from so long as it can find some libraries. A shell script wrapper to set LD_LIBRARY_PATH or whatever and off you go. It's probably more likely that your binary only software will break due to an ABI change.

At lest that's been my experience (happy go lucky as it may seem).

I'm neither for or against it. IMO there's bigger things to fret about.

Reply Parent Score: 3