From: Keith Owens <kaos@ocs.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Persistent module storage - modutils design
Date: Thu, 09 Nov 2000 16:25:10 +1100 [thread overview]
Message-ID: <4983.973747510@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "08 Nov 2000 21:09:49 -0800." <8udbit$pne$1@cesium.transmeta.com>
On 8 Nov 2000 21:09:49 -0800,
"H. Peter Anvin" <hpa@zytor.com> wrote:
>Remember that we cannot rely on ANY form of persistent storage to be
>available in the beginning; / may very well be readonly (on a ROM,
>say.) Since that means that we can't rely on writable storage being
>available until at least one other filesystem has been mounted, it
>might as well be the standard for variable data, i.e. /var.
Agreed. Default is /var/lib/modules-persist. People who have a
separate /var partition that is mounted after modules are loaded can
use / and specify
persist /lib/modules/persist
in /etc/modules.conf. If you have a separate /var and you do not want
to write to /, change your initialization scripts to load modules after
mounting /var.
-
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 5:26 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 [this message]
2000-11-09 5:21 ` Keith Owens
2000-11-07 13:55 ` Alan Cox
2000-11-09 12:22 ` Ralf Baechle
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=4983.973747510@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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).