From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum.hack -> factotum and ... no more CMOS as nvram
Date: Tue, 4 Nov 2003 10:30:28 -0500 [thread overview]
Message-ID: <E1AH38W-0005b3-FP@t40.swtch.com> (raw)
In-Reply-To: Your message of "Tue, 04 Nov 2003 09:40:59 MST." <Pine.LNX.4.44.0311040939110.32465-100000@maxroach.lanl.gov>
> > yes, it will break every system we have.
>
> Well, it's hard to argue with that reason. I have no desire to break all
> the systems, but, why would this break them? On normal systems the sdC0
> nvram would be found first.
>
> Anyway I may not need this, as I can just set up the compact flash with an
> nvram partition, and give up on the CMOS anyway.
Okay, well if you put it last in the list then it won't
break all the current systems.
But if you've got a system where you have forgotten
to create a disk nvram partition, it is usually _not_
okay to start scribbling on #r/nvram. I think we only
want to use #r/nvram if directed, and we can do that
by setting nvram= in plan9.ini.
Russ
next parent reply other threads:[~2003-11-04 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0311040939110.32465-100000@maxroach.lanl.gov>
2003-11-04 15:30 ` Russ Cox [this message]
2003-11-04 18:14 ` ron minnich
[not found] <b5fc626be2e3710701ce3d07f98cfbd0@plan9.bell-labs.com>
2003-11-04 18:03 ` ron minnich
2003-11-04 5:17 ron minnich
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=E1AH38W-0005b3-FP@t40.swtch.com \
--to=rsc@swtch.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).