[701] in arla-drinkers
Re: location of cache dir
daemon@ATHENA.MIT.EDU (Love)
Wed Mar 17 00:03:39 1999
From owner-arla-drinkers@stacken.kth.se Wed Mar 17 05:03:37 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 13601 invoked from network); 17 Mar 1999 05:03:34 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 17 Mar 1999 05:03:34 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id FAA20384
for arla-drinkers-list; Wed, 17 Mar 1999 05:57:42 +0100 (MET)
Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id FAA20380
for <arla-drinkers@stacken.kth.se>; Wed, 17 Mar 1999 05:57:28 +0100 (MET)
Received: from anchor.s3.kth.se (anchor.s3.kth.se [130.237.43.59])
by elixir.e.kth.se (8.9.2/8.9.2) with ESMTP id FAA21114;
Wed, 17 Mar 1999 05:57:26 +0100 (MET)
Received: (from lha@localhost)
by anchor.s3.kth.se (8.9.2/8.9.2) id FAA03840;
Wed, 17 Mar 1999 05:57:25 +0100 (MET)
From: Love <lha@stacken.kth.se>
To: Nat Lanza <magus@cs.cmu.edu>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: location of cache dir
References: <199903161644.QAA22065@antharia.MIT.EDU> <uoc1ziosuzl.fsf@evelake.pdl.cs.cmu.edu> <am6780vivw.fsf@anchor.s3.kth.se> <uocsob4rayw.fsf@evelake.pdl.cs.cmu.edu>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 17 Mar 1999 05:57:24 +0100
In-Reply-To: Nat Lanza's message of 16 Mar 1999 23:33:59 -0500
Message-ID: <am3e34vhl7.fsf@anchor.s3.kth.se>
Lines: 39
X-Mailer: Gnus v5.5/Emacs 20.2
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Nat Lanza <magus@cs.cmu.edu> writes:
> Love <lha@stacken.kth.se> writes:
>
> > Since /usr might not be avaible at boot-time and later be mounted read-only
> > on all systems.
>
> Well, sure, but if your binaries are in /usr, then that cache in /var
> really isn't useful without /usr mounted anyway.
Just the kernel module, arlad, the cache and mount_xfs is need for booting
and those could be easily be installed on / and /var.
> The Right Thing is probably just having both '--prefix=' and
> '--with-cache-dir=' configuration options, with the cache-dir option
> defaulting to somewhere under $prefix. Go for the common case, but
> make it easy to adapt to the less common ones.
(I don't expect any answers, just pointing out that is not really obvious
where to store thing to make it work everywhere and there is no right way)
Where should you place you kernel module to make it load automagicly ? For
varius operating system those are:
FreeBSD /lkm (/kld now ?)
Linux /lib/modules/n.n.n
osf /subsys,/usr/sys/BINARIES,...
solaris /kernel/<subsys>
Should arlad be placed in /sbin, and where should we install the
headerfiles and (shared)libs to make them simple to use ?
And remember that it should be simple at the same time (ie configure &&
make all install).
The only obvious programs is fs, vos and friends.
I don't think there is a Right Way<tm>, just a Easy, Fast and Stupid Way.
Love
