From: Ralf Baechle <ralf@uni-koblenz.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: Persistent module storage - modutils design
Date: Thu, 9 Nov 2000 13:22:51 +0100 [thread overview]
Message-ID: <20001109132250.A1106@bacchus.dhis.org> (raw)
In-Reply-To: <200011071330.eA7DUdw26230@pincoya.inf.utfsm.cl> <E13t9EH-0007Ra-00@the-village.bc.nu>
In-Reply-To: <E13t9EH-0007Ra-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Nov 07, 2000 at 01:55:59PM +0000
On Tue, Nov 07, 2000 at 01:55:59PM +0000, Alan Cox wrote:
> > Note! This _has_ to be in the / filesystem so it works before mounting the
> > rest of the stuff (if ever). This would rule out /var, and leave just
> > /lib/modules/<version>. Makes me quite unhappy...
>
> The /lib filesystem is likely not writable so /var is the right default.
In theory yes. In practice /var is often a mounted filesyste so for
modules loaded before /var is mounted this solution gets somewhat ugly.
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-09 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 4:00 Persistent module storage - modutils design Keith Owens
2000-11-07 4:45 ` Keith Owens
2000-11-07 12:45 ` Horst von Brand
2000-11-07 13:30 ` Horst von Brand
2000-11-07 13:51 ` Keith Owens
2000-11-09 4:52 ` Rusty Russell
2000-11-09 5:09 ` H. Peter Anvin
2000-11-09 5:25 ` Keith Owens
2000-11-09 5:21 ` Keith Owens
2000-11-07 13:55 ` Alan Cox
2000-11-09 12:22 ` Ralf Baechle [this message]
2000-11-07 13:33 ` Keith Owens
2000-11-07 14:47 ` Horst von Brand
2000-11-07 15:19 ` Keith Owens
2000-11-07 16:01 Jesse Pollard
2000-11-07 21:51 ` Keith Owens
2000-11-07 22:30 Jesse Pollard
2000-11-07 22:52 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001109132250.A1106@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).