From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] changes in 9load
Date: Wed, 21 May 2003 13:35:17 -0400 [thread overview]
Message-ID: <90b20611bddbc6da6a3a70d5d136263a@plan9.bell-labs.com> (raw)
In-Reply-To: <20030521192502.C7647@cackle.proxima.alt.za>
> Yeah. I also considered a rw /boot, but, without even looking, I
> assumed it would be a bitch, at best. Being read-only is of course
> a security advantage. On the other hand, could a script in /boot
> not read the configuration files from the boot medium instead of
> inheriting them off the "environment"?
What would a rw /boot mean? Changing it certainly
wouldn't change the kernel image (wherever it may
have been picked up from), so you might as well use
ramfs if you want an in-memory rw file system.
Russ
next prev parent reply other threads:[~2003-05-21 17:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 14:31 Fco.J.Ballesteros
2003-05-21 14:58 ` Russ Cox
2003-05-21 15:00 ` Fco.J.Ballesteros
2003-05-21 15:22 ` Russ Cox
2003-05-21 15:46 ` [9fans] VAIO ATI RAGE MOBILITY-M1 AGP 1024x768x16 lcd display boyd, rounin
2003-05-21 17:45 ` Russ Cox
2003-05-22 8:46 ` boyd, rounin
2003-05-22 9:32 ` Philippe Anel
2003-05-22 17:49 ` Russ Cox
2003-05-23 8:37 ` Adrian Tritschler
2003-05-23 14:04 ` Russ Cox
2003-05-23 14:53 ` Sape Mullender
2003-05-23 15:11 ` Dan Cross
2003-05-23 15:17 ` Russ Cox
2003-05-23 15:24 ` Dan Cross
2003-05-21 15:57 ` [9fans] changes in 9load Fco.J.Ballesteros
2003-05-21 17:24 ` Russ Cox
2003-05-21 16:26 ` northern snowfall
2003-05-21 17:06 ` Lucio De Re
2003-05-21 17:15 ` Fco.J.Ballesteros
2003-05-21 17:25 ` Lucio De Re
2003-05-21 17:32 ` Fco.J.Ballesteros
2003-05-21 17:35 ` Russ Cox [this message]
2003-05-21 17:39 ` Fco.J.Ballesteros
2003-05-21 18:03 ` Lucio De Re
2003-05-21 18:11 ` Fco.J.Ballesteros
2003-05-21 18:39 ` Lucio De Re
2003-05-21 17:47 ` Lucio De Re
2003-05-21 17:51 ` Russ Cox
2003-05-21 17:56 ` Lucio De Re
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=90b20611bddbc6da6a3a70d5d136263a@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).