> > so what about /var/lib? (another directory I don't fully understand
> > the reasoning behind; I'm just throwing this out as an idea).
>
> /var/lib is for state information, such as editor backup files,
> distribution packaging system data, and so forth. 'lib' is arguably
> an unfortunate name, as other '*/lib's are for libraries.
exactly. from what I see, most of the stuff in /var/lib could be
better put in /var/cache or /var/spool; or even their own subdirs under /var.
> As far as I can tell, the GNU coding standards would place the
> contents of /var/lib in /com. Maybe there are other subdirectories of
> /var whose contents would be in /com, too.
what's the logic behind the /com name?
Carl Soderstrom
--
Network Engineer
Real-Time Enterprises
www.real-time.com
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd