On 24 May 2002, Gordon Messmer wrote:

> On Thu, 2002-05-23 at 13:07, Ward William E DLDN wrote:
> > 
> > Benefits:
> > 
> > One, single /var so ALL logs still show up; and nicely,
> > during boot, it TELLS you what kernel you're booting to,
> > so you can decipher.
> 
> /var contains data that may not be compatible between 7.2 and 7.4.  For
> instance, PostgreSQL won't work.
> 
> Skip sharing /var.

(out of curiosity, how did this thread suddenly referring to "7.4"?
you guys must have a *serious* pre-alpha version or something. :-)

the more i think about this, the more i realize that this is related
to the file and directory layout being discussed in the FHS (filesystem
hierarchy standard).

the biggest hassle is clearly the /var directory, which currently
is a mess.  /var currently contains, on the one hand, truly variable
data (/var/log, /var/lock) that does not have to be carried across
to a new release, but also config and data files (/var/www, /var/ftp,
/var/named, etc.) that *could* be carried across (or, more 
specifically, *should* be carried across to a new release).

one of the proposals of the FHS was to create a new top-level
directory, /srv, for stuff to be *served*, such as /srv/ftp,
/srv/http and so on.  if things were designed more cleanly,
that would make my little exercise here a lot simpler.
so i'm going to peruse the last few months of the FHS archives
and think on this some more.

rday



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to