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 505206
To read all comments associated with this story, please click here.
by acobar on Mon 30th Jan 2012 22:52 UTC
Member since:

Well, first lets recap that standards structure do not come always from a well thought process in its beginning. Most of the times they are decided upon a need to make interoperability work once a "critical mass" is achieved on some activity or when technical or practical knowledge determine than for safety reasons. The last cases are not prevalent on what we are talking about, at least a priori.

So, it really does not matter how it started but how it will guarantee that its goals will be fulfilled.

Now, going back to the proposed merge of bin/* to usr/bin/*.

I know that fedora (red hat) people do a lot of the hard work to make a working and modern system of FOSS software, linux + gnu + projects, but frankly I think they should grow inside a more respectful attitude towards the FOSS community. Look how this "fix it now" posture created a lot of problems that took "forever" to be finally solved and wasted too many manpower. HAL and Pulse Audio (ok, I know, first rushed by ubuntu folks), just to name few, are terrible examples of this.

We already crossed that point when "fix it now" was a must. Our systems already work reasonably. We already have the knowledge and already achieved the critical mass point. It is time to do things properly and have open discussions about possible solutions for our problems like they have on every other engineering field, be our concerns related to interoperability, safety or whatsoever it may be.

If someone wonder, I really prefer a more structured approach like they have on debian guidelines and FreeBSD. I see this "dump everything on /usr/bin" as a rushed solution more than a properly build one.

Reply Score: 4