From linux Thu Feb 13 15:56:24 1992
Return-Path: <linux-standards-request@concert.net>
Received: from jazz.concert.net by banjo.concert.net with SMTP (PP) 
          id <598-0@banjo.concert.net>; Thu, 13 Feb 1992 15:55:35 -0500
Received: from Kodak.COM by jazz.concert.net (5.59/tas-concert/6-19-91) 
          id AA29651; Thu, 13 Feb 92 15:55:30 -0500
Received: from kodak.kodak.com by Kodak.COM (5.61+/2.1-Eastman Kodak) 
          id AA06159; Thu, 13 Feb 92 15:54:33 -0500
Reply-To: nobody@Kodak.com
Received: from sisd.kodak.com by kodak.Kodak.COM (4.1/SMI-4.1) id AA18837;
          Thu, 13 Feb 92 15:55:08 EST
Received: from acorn.UUCP by sisd.kodak.com (4.1/SMI-4.x_sisd_main_v1) 
          id AA18048; Thu, 13 Feb 92 15:53:46 EST
Received: from flash.acorn by acorn (4.1/SMI-4.0) id AA09661;
          Thu, 13 Feb 92 15:50:52 EST
Received: by flash.acorn (4.1/SMI-4.1) id AA15641; Thu, 13 Feb 92 15:50:50 EST
Date: Thu, 13 Feb 92 15:50:50 EST
From: obz@sisd.sisd.Kodak.com (Orest Zborowski)
Message-Id: <9202132050.AA15641@flash.acorn>
To: linux-standards@concert.net
Subject: standard directory hierarchy

i have a few thoughts on this directory issue:

1) linux is supposed to support posix - it does a pretty good job supporting
   posix.1, the os interface layer. there is a posix.2 which describes a bunch
   of utilities available from the shell. i'm not sure it has produced any
   standards document, but i do believe i've read about its progress in
   communications of the acm, and in ieee computer. this should be the
   authority.

2) following svr4 standards seems to be the logical next step. svr4 is truly
   posix compliant and posix seems to lean heavily to sysv for certain things
   like directory structure. bsd, especially sunos, is also moving towards
   svr4.

3) its true, certain applications have /lib/cpp burned into them and its gonna
   be difficult to remove it. even things like the standards can't remove that
   stain; you can move it (like sunos, which symlinks everything), but you can't
   remove it.

i think its a little naive to believe that we can come up with some special
directory hierarchy which is the be-all and end-all of structures, and then
we should change all these programs to conform. if you like, you can make
whatever changes you desire, like using symlinks to keep a partition readonly,
or shareable; changing the entry in /etc/passwd and make roots directory
/root, etc. for the standard distribution i would choose to make as few
changes from existing standards or existing implementations as possible.

zorst
obz@sisd.kodak.com