[703] in arla-drinkers

home help back first fref pref prev next nref lref last post

Re: location of cache dir

daemon@ATHENA.MIT.EDU (linas@us.ibm.com)
Wed Mar 17 12:02:58 1999

From owner-arla-drinkers@stacken.kth.se Wed Mar 17 17:02:57 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 21340 invoked from network); 17 Mar 1999 17:02:56 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 17 Mar 1999 17:02:56 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA26391
	for arla-drinkers-list; Wed, 17 Mar 1999 17:56:29 +0100 (MET)
Received: from smtp8.ny.us.ibm.com (smtp8.ny.us.ibm.com [198.133.22.20])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA26387
	for <arla-drinkers@stacken.kth.se>; Wed, 17 Mar 1999 17:56:22 +0100 (MET)
From: linas@us.ibm.com
Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209])
	by smtp8.ny.us.ibm.com (8.8.7/8.8.7) with ESMTP id LAA78560;
	Wed, 17 Mar 1999 11:55:06 -0500
Received: from d54mta01.raleigh.ibm.com (d54mta01.raleigh.ibm.com [9.67.228.33])
	by southrelay02.raleigh.ibm.com (8.8.7/NCO v1.8) with SMTP id LAA98508;
	Wed, 17 Mar 1999 11:55:23 -0500
Received: by d54mta01.raleigh.ibm.com(Lotus SMTP MTA Internal build v4.6.2  (651.2 6-10-1998))  id 85256737.005CF501 ; Wed, 17 Mar 1999 11:55:20 -0500
X-Lotus-FromDomain: IBMUS
To: magus@cs.cmu.edu
cc: arla-drinkers@stacken.kth.se
Message-ID: <85256737.005CF318.00@d54mta01.raleigh.ibm.com>
Date: Wed, 17 Mar 1999 11:55:13 -0500
Subject: Re: location of cache dir
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk



Dan is right,

The current file-system heirarch standards call for /usr to be more-or-less
read-only, and logfiles/caches/spools to go into /var.  On systems were
security is important, its nice to
have /var in its own partition (even if its small). Although transarc may
use /usr/vice (and
this usage is old and not up to modern standards), you will note that
transarc *always* puts
/usr/vice into its own partition (and thier manuals warn of grave dangers
if this is not done).

From what I've seen, Redhat does not violate the FS stanadard; I beleive
you can take a
red-hat system and mount /usr read-only and experience no pain whatsoever.
I beleive this would be normal proceedure e.g. on firewalls and/or on boxes
accessible
to undergrads where you want to discourage foul play as much as possible.

--linas
(sorry for the funny mail formatting; I am forced to use crippleware here
...)
=============================================================

Dan Winship <danw@mit.edu> writes:

> Most OSes these days (or at least the cool ones :) seem to believe
> that /usr should be able to be both read-only and shared across
> multiple machines. Maybe the default cache dir location should be in
> /var instead of /usr?

Most machines I deal with either have /var on the relatively small
root partition, with log rotation set up to keep it from overflowing,
or they have a little /var partition with the same log rotation
stuff. All the big stuff goes somewhere in /usr<blah>. And hey, the
Transarc cache goes in /usr/vice. Also, I'd guess that most users of
Arla are running Linux machines. Most Linux machines are probably
Redhat boxes. Since RPM usually puts everything in /usr, making /usr
be read-only might be painful.

So I guess I don't really see why changing the default to /var is a
good idea.


--nat



home help back first fref pref prev next nref lref last post