Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by kstenerud on Friday January 27, 2012 @04:53PM
(#3520342)
Every one of those paths I mentioned are paths I have encountered during my use of various unix distributions since 1991 (Solaris was the worst offender). And that's not even the complete list. I gave up trying to predict where software would install to a long time ago.
My point is that what "makes sense" is subjective. Each developer/distro manager who made one of those paths thought to himself "it makes perfect sense to do it this way". FHS does go a long way towards cutting back on the craziness (by arbitrarily dictating "do it this way"), but it's still clunky.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by dredmorbius on Friday January 27, 2012 @05:07PM
(#3520402)
Your encountering them doesn't make them part of FHS.
Their being included in FHS does.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by kstenerud on Friday January 27, 2012 @05:26PM
(#3520483)
At no point did I ever say they were part of the FHS.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by dredmorbius on Friday January 27, 2012 @07:45PM
(#3520903)
OP did, and by inference (with my pedant bit set) you were supporting his statements.
http://news.ycombinator.com/item?id=3520178
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by kstenerud on Friday January 27, 2012 @08:04PM
(#3520953)
Hmm that was not my intent.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split
by nknight on Friday January 27, 2012 @06:53PM
(#3520746)
Most of us are more concerned about the real world than a "standard" that is routinely ignored.
Of the paths you mentioned, there is no such thing as:
All the paths that involve `share` are for non-executable data, so `bin` and `lib` subdirectories of these don't make sense. That's not to categorically say that there isn't any OS that provides them anyway--I've seen plenty of Linux distros with disorganized file systems--but that's a problem with the distro, not the FHS as a whole.The `/opt` hierarchy is pretty much the wild west, I'll give you that. It's basically like `Program Files` on Windows; packages get an entire hierarchy to themselves. Most of the software I've seen that installs to `/opt` is Linux ports of Windows software, where the authors were either ignorant of the Unix way of organizing things, or simply didn't want to bother conforming with the norms of a different platform.
Incidentally, one of the reasons I prefer Arch Linux over some other distros is that the organization of the file system follows the standard and actually makes sense. Things are always where I expect them to be.
Your overall point may have some merit, but it feels a little like you're reaching for support for your position by making up wacky, confusing paths that don't actually exist.