Linked by Thom Holwerda on Wed 26th Jun 2013 14:12 UTC
Linux "This document outlines the set of requirements and guidelines for file and directory placement under the Linux operating system according to those of the FSSTND v2.3 final (January 29, 2004) and also its actual implementation on an arbitrary system. It is meant to be accessible to all members of the Linux community, be distribution independent and is intended to discuss the impact of the FSSTND and how it has managed to increase the efficiency of support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems."
Permalink for comment 565708
To read all comments associated with this story, please click here.
by MeinNick on Wed 26th Jun 2013 20:08 UTC in reply to "RE: ROFL"
Member since:

No, sbin is for SYSTEM binaries. Anything that normal user will never run. sbin is usually not in user's PATH.

sbin and bin have their use and should/will remain separated forever.

/usr/bin /usr/sbin /usr/lib are redundant given the size of our disks however. In fact, a few distro create them as symlinks to /bin /sbin /lib.

Other distributions use the opposit, with symlinks behing in the root and real dir being in usr.

Those arguing that /sbin and /bin are useful for rescue, then explain to me what is the purpose of the initrd? Drivers can perfectly be loaded from the disk or built into the kernel, what remains? The rescue prompt!

Edited 2013-06-26 20:10 UTC

Reply Parent Score: 4