On Wed, Sep 28, 2005 at 01:05:00PM -0500, JD Runyan wrote: > Lan Barnes wrote: > >Unfortunately, I find for myself that /etc and /var are a mixed bag of > >stuff I need and stuff I want to write over. I cope with /etc (not well) > >by keeping .../RCS archives of key files. It's a pain because they're in > >different subdirectories. I take some key files (like hand rolled X > >config files) off to floppy and put that in my machine envelope. > > > >I frequently rail against the shoddy situation in /var. It still enrages > >me when applications use it for the location of data bases that I need. > >If it were up to me, I wouldn't allow anything in /var but spools, logs, > >temp files, and data bases that are local to the installation, like the > >RPM data base and the locate data base. But that ain't so, so explore > >/var before purging. > > > > You should read the FHS(http://www.pathname.com/fhs/). It basically says > that all variable files should go in /var. This includes logs, > databases, and spools. This was done to allow for more filesystems to > be mounted as read only.
Reading it and agreeing with it are two different things ... or am I not allowed to think any more? Tell me, what files besides /usr/bin are not potentially "variable"? Should my resume and correspondence go in there? _All_ data bases? What's the advantage of a partition scheme where one partition is so ill defined that any damn thing can go in there? Should I put everything in /tmp that might someday get erased? /var is ill defined IMNSHO. -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
