<snip>
I don't know the whole story, but here's a piece of it:Quote:>What is the differnce say, between /usr/local/bin and /bin. And what is
>with the sbin and lbin etc.
>Of course I guess a lot of this could be specific to this particular system,
>but what are the different bins for?
>path (/usr/local/lbin /usr/local/mbin /usr/local/msbin /usr/local/sbin
>/usr/local/bin /us r/lbin /usr/lsbin /usr/sbin /usr/bin /llbin /lmbin /lsbin
>/lbin /sbin /bin /usr/bin/X11 /usr /TeX/bin /usr/local/games /usr/games
>/usr/local/netpbm/bin /usr/local/nn/bin /usr/local/devt eam/bin
>/usr/local/staffbin /usr/local/ssl/bin)
/sbin - for binaries essential to booting the system
/bin - for other core system utilities (e.g. ps, ed, ...)
/usr/bin- for common user utilities (e.g. mail, who, ...)
/usr/local/bin
- for common user utilities added to the system
by your administrator (e.g. Mosaic, GNU stuff)
I don't know about lbin, llbin, lmbin, lsbin. My guess is they are peculiar
to your flavor of Unix, or your particular administrator.
Sometimes you'll find packages installed in tree fashion under /usr/local
(e.g. /usr/local/nn) so that they're easier to remove/upgrade later.
Note that another general reason for grouping binaries into logically
distinct directories is to allow them to be shared as NFS volumes, or
even to allow them to reside on distinct filesystem slices of your drive.
--
The CRT Corporation
Computer Based Research and Training