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 565721
To read all comments associated with this story, please click here.
RE: Comment by Wafflez
by UltraZelda64 on Wed 26th Jun 2013 22:03 UTC in reply to "Comment by Wafflez"
Member since:

/bin, /etc, /usr - it's all dinosaurs.
Atleast dinosaurs went extinct...

So, what are you trying to say? That "C:\WINDOWS" and "C:\Program Files" are better? That you'd rather deal with something like "C:\WINDOWS\system32\drivers\etc\hosts" instead of "/etc/hosts"?

I'd say that the UNIX file system structure is far from "extinct." It could use a few improvements (some of which are already being done), but as it is it's very comfortable to navigate--either by command line or by graphical file manager. By comparison, I can navigate a Windows file system fine with Windows Explorer (well, in most cases--the hosts file example above is one that I never remembered...), but there is no point in even trying to navigate the Windows file system structure by commands. Too many special characters needed to bypass spaces in file/directory names, and the file/directory names tend to just be too damn long.

Reply Parent Score: 6