Talk:Filesystem Hierarchy Standard
|This is the talk page for discussing improvements to the Filesystem Hierarchy Standard article.|
|WikiProject Computing||(Rated Start-class, Low-importance)|
I'm removing the sentence about Plan 9, because not only is FHS not a Plan 9 thing, but it also didn't _influence_ Plan 9's names for system folders. Plan 9 existed before FHS. Also, the paragraph, which goes
- Modern Linux distributions include a /sys directory as a virtual filesystem (sysfs, comparable to /proc, which is a procfs), which stores and allows modification of the devices connected to the system, whereas many traditional UNIX and Unix-like operating systems use /sys as a symbolic link to the kernel source tree. Likewise, Plan 9 from Bell Labs includes a /net directory.
makes it sound like Plan 9 has /net _in addition_ to all that /sys registry stuff, which it doesn't.
This particular mention of Plan 9 in this article makes no sense whatsoever. It might however make sense in Unix directory structure.
/usr/local "specific to host"?
The item on /usr/local says "for local data, specific to this host" and the attached footnote (currently 12) expands with "historically and strictly according to the standard, /usr/local/ is for data that must be stored on the local host (as opposed to /usr/, which may be mounted across a network)." "Historically" is as it may be but looking at the standard I can see nothing that that supports the "local host" assertion. Instead it says "[it] may be used for programs and data that are shareable amongst a group of hosts", which would seem to imply exactly the opposite. The unfortunate word "local" seems no to be specifically defined. I will thus plan reword this section unless someone can show me how I'm reading this wrong ... 18.104.22.168 (talk) 20:43, 27 August 2010 (UTC)
- The sentence "historically and strictly according to the standard, /usr/local/ is for data that must be stored on the local host (as opposed to /usr/, which may be mounted across a network)", is bogus. Actually, the word "local" here simply referred to the customer organization, as opposed to the Unix vendor. For a long time, the directory didn't even exist out of the box; the sysadmin had to create it. It was common to mount /usr/local/ site wide over the LAN. For more about the history of the filesystem hierarchy, see this article. --Sumafi (talk) 17:30, 3 November 2012 (UTC)
Pronunciation of etc.
I have /never/ heard etc pronounced as et-see. This is after 10 years working with Linux, numerous workshops and classes. I have heard it pronounced as E-T-C and sometimes as etcetera. Not sure what wiki policy is on pronunciation guides (and much too lazy to look it up), but I have found that uncited pronunciations are usually reflecting the bias of a particular community of speakers, and usually there is more than one accepted pronunciation. Tagged as citation needed, but probably worth deleting in the absence of a citation 22.214.171.124 (talk) 00:25, 5 March 2011 (UTC)
- I agree that this seems suspicious (I've never heard it that way over an even longer time). I guess it's a possible pronunciation, but it's uncited and obviously not common knowledge (even contradicts it), so I'm going to remove it. Definitely not critical to the article at hand, so no need to keep a trivial contested detail for now. DMacks (talk) 18:43, 12 March 2011 (UTC)
- "/tmp" has the same problem; User:Calinucs replaced the /tmp link with a link to tmpfs, but the FHS doesn't say that /tmp has tmpfs mounted on it (even though that might be the case in practice), so that's not really the right fix. The right fix for both /tmp and /var/tmp is to get rid of the link; I did that for both. (I also fixed both of them to point to Unix directory structure, as both /tmp and /var/tmp long antendate the FHS.) Guy Harris (talk) 17:30, 2 December 2012 (UTC)
- Agree about the redirect on /tmp. I just thought that, since FHS is Linux specific, a link to tmpfs (perhaps in the description) would still be helpful for people using this page to learn about Linux (like the description of /boot links to initrd even if initrd is not in the spec). Calinucs (talk) 11:46, 3 December 2012 (UTC)
- Maybe something such as "May have tmpfs mounted on it." would be useful; I considered it, but as the FHS doesn't say anything about tmpfs, I wasn't sure whether it was the right thing to do or not (I didn't want readers to think the FHS was speaking of tmpfs - that's an implementation detail). Guy Harris (talk) 19:53, 3 December 2012 (UTC)