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."
Thread beginning with comment 565780
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Fedora for the rescue
by Soulbender on Thu 27th Jun 2013 09:19 UTC in reply to "Fedora for the rescue"
Soulbender
Member since:
2005-08-18

# ls -l
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin


I'm curious, what real-world problem does this solve?

Reply Parent Score: 3

RE[2]: Fedora for the rescue
by SeeM on Thu 27th Jun 2013 10:27 in reply to "RE: Fedora for the rescue"
SeeM Member since:
2011-09-10

"# ls -l
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin


I'm curious, what real-world problem does this solve?
"

Main goal is to have one less directories for "exe" files, and generally more clean /. There's too much in there now. I can leave with /etc, /usr, /home, /boot, but /srv, /mnt&/media, /bin&/sbin, /opt? I rarely even look inside of those, so why they are exposed so much? I simply type something in terminal (or #!/usr/bin/env) and hoping that PATH in shell config is OK. Or plug usb memory stick and click the icon.

I wonder if ever we'll have one dir for binaries in Linux and throw PATH away.

Reply Parent Score: 2