News for hackers. Stuff that matters.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split by kstenerud on Friday January 27, 2012 @04:23PM (#3520232)
Because everyone's idea of what "makes sense" is different. Thus:

/bin

/usr/bin

/usr/share/bin

/usr/share/local/bin

/usr/local/bin

/usr/local/share/bin

/opt/bin

/opt/some/clever/path/system/bin

Followed by hacky symlinks so that programs can find what they're looking for in /usr/local/share/lib/x, which really resides in /usr/share/lib/x or maybe /var/lib or maybe /var/local/lib or maybe just /lib because it's considered "essential" on some systems but not others.

It reminds me of this: http://xkcd.com/927/

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by tmhedberg on Friday January 27, 2012 @04:41PM (#3520304)
This is a little bit disingenuous. I can certainly see the point that all of this separation is unnecessary on a typical modern desktop system, but several of the paths you listed in support of your argument are not actually specified by the FHS, nor do they even make sense.

Of the paths you mentioned, there is no such thing as:

    /usr/share/bin
    /usr/share/local/bin
    /usr/local/share/bin
    /usr/local/share/lib
    /usr/share/lib
    /opt/bin
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.

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.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split by chronomex on Saturday January 28, 2012 @07:24AM (#3521936)
I put Java in /opt/java/, and embedded toolchains in /opt/[platform]/. Not exactly Windows ports, but they're the sort of thing that can get out of hand easily. :)
Re:Understanding the bin, sbin, usr/bin , usr/sbin split by jonhohle on Friday January 27, 2012 @04:36PM (#3520279)
Perhaps you have some misbehaving software, but I've never seen /usr/share/bin, or /usr/local/share/bin or a lib directory in either of those locations. I just checked FreeBSD boxes (which, admittedly, follow their own standards closely), and a Redhat box.

var is a directory which may be found under /usr or /usr/local, but won't contain a local directory.

Think of it as 3 roots: / is required for boot, /usr is stuff maintained by an administrator (say, company wide), /usr/local is where files installed by local users go. Within each of these 3 roots, you'll have some subset of bin, etc, lib, libexec, sbin, and var. The root directory has some additional singleton directories which don't make sense in the other directories: dev, root, mnt, boot, proc, rescue.

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by X-Istence on Friday January 27, 2012 @07:26PM (#3520844)
/usr is maintained by the OS, and contains stuff that isn't required for boot but to round out the system.

/usr/local is where local modifications to the OS go, these can be site-wide (company wide) and can be hosted on NFS for example for network boots. User installed stuff belongs in /usr/home/<name>/*. Users shouldn't have root access to install stuff in /usr/local.

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by lmm on Saturday January 28, 2012 @04:58AM (#3521732)
Side point: it really bothers me that on freebsd the ports system takes over /usr/local. I expect /usr/local to consist of things that I as admin have installed by hand, and nothing else.
Re:Understanding the bin, sbin, usr/bin , usr/sbin split by X-Istence on Saturday January 28, 2012 @05:18PM (#3523482)
You can change where packages are installed using some make.conf flags. You can then install the software anywhere you want. Your users will need to add the new path to their PATH and you'll need to set some flags in rc.conf to pick up the new rc.d path as well (so software installed through ports gets auto-started).

Then again, when you install ports you as the sysadmin are installing those by hand ...

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by elehack on Saturday January 28, 2012 @09:47AM (#3522173)
Agree totally.

NetBSD uses the more sensical /usr/pkg for package-managed software, leaving /usr/local for the admin.

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by pconf on Saturday January 28, 2012 @09:26PM (#3524204)
I really like the way FreeBSD separates system and third party software, the latter typically being installed to /usr/local.

Linux' failure to differentiate between system and non-system binaries is IMO one of it's worst features.

Neither FreeBSD nor Linux accommodate network mounted NFS mounted applications as well as SunOS did so successfully by the late '80s. This is probably due to the corrupting influence of Unix and Linux engineers who came from MS Windows backgrounds. Windows admins waste countless hours having to install software locally on every machine. Sad that only Solaris provides for a standard network-based application filesystem. Odd too that Solaris is home to the single most ill-thought-out non-system directory, /opt.

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by Sorpigal on Tuesday January 31, 2012 @08:30AM (#3533109)
BSD is in a position to differentiate in a way that Linux just isn't. In Linux all* software is third party, except for the kernel and util-linux (and maybe fileutuls or some other set of GNU software).

To me the BSD distinction doesn't make much sense anyway. You still have to just know which bits are "local" and which are not, plus anything I pull in that isn't a port gets lumped in with them anyway.

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by aangjie on Saturday January 28, 2012 @12:08PM (#3522542)
Actually it reminded me of http://xkcd.com/981/

But i do remember seeing /usr/share/bin and /usr/share/local/bin and thinking wtf... But then i play around too much with my OS to reliably blame it on the distro...

Re:Understanding the bin, sbin, usr/bin , usr/sbin split by moe on Friday January 27, 2012 @07:08PM (#3520786)
You forget my favorites: /usr/libexec and /usr/lib/$progname