Re: [RFC] User Accesable Filesystem Hierarchy Standard
Henning Makholm <henning-+DL+Sue2To/[email protected]>
| Newsgroups | gmane.linux.arklinux.devel,gmane.linux.debian.devel.general,gmane.linux.redhat.fedora.devel |
|---|---|
| Message-ID | <[email protected]> |
Scripsit Gary L Greene Jr <[email protected]> > URL to get to the document is: > http://www.csis.gvsu.edu/~abreschm/uafhs/ Another problem is that any standard that just says ~/.bin or something like that (~/$FOO/bin) will be inherently broken on sites where NFS-mounted home directories are shared between machines of different architectures. That may not be a problem for living-room home machines (yet!), but as soon as one looks at at-work setups, it is possibility that needs to be considered. In order for a standard to be robust enough to deserve widespread adoptance it needs a more complex system, perhaps something like ~/.debian/i386/bin ~/.debian/i386/lib ~/.debian/alpha/bin ~/.debian/alpha/lib ~/.debian/share ~/.solaris/sparc/bin ~/.solaris/sparc/lib ~/.solaris/share ... in a fairly diverse hypothetical environment. One needs different .../share for each vendor, because FHS /usr/share is only sharable between different architectures of the *same* OS. (This is not widely known; I only learned it when I tried having my own equivalent ot /usr/share/terminfo on a NFS $HOME, and watched it malfunction once I logged into one of the HP-UX boxen we ran then). Still, one probably wants ~/.debian/share/texmf and ~/.solaris/share/texmf to symlinked to each other, nevertheless... -- Henning Makholm "Jeg har tydeligt gjort opmærksom på, at man ved at følge den vej kun bliver gennemsnitligt ca. 48 år gammel, og at man sætter sin sociale situation ganske overstyr og, så vidt jeg kan overskue, dør i dybeste ulykkelighed og elendighed."