From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Whither nvram?
Date: Thu, 9 Jan 2003 07:09:05 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0301090708050.12571-100000@carotid.ccs.lanl.gov> (raw)
In-Reply-To: <fb8ff0af4aaa626d14265c500fceb91a@plan9.bell-labs.com>
On Thu, 9 Jan 2003, Russ Cox wrote:
> I like that suggestion. Then I could get rid
> of the cputype=debug hack.
Out here andrey did a set up so that our linuxbios nodes had nvram in
cmos; it really was nvram. The types of nvram are becoming more varied. An
environment variable to describe nvram would be very useful.
ron
prev parent reply other threads:[~2003-01-09 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 5:08 Dan Cross
2003-01-09 5:10 ` Russ Cox
2003-01-09 14:09 ` Ronald G. Minnich [this message]
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=Pine.LNX.4.44.0301090708050.12571-100000@carotid.ccs.lanl.gov \
--to=rminnich@lanl.gov \
--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).