From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Question on #r/nvram
Date: Wed, 14 May 2003 17:11:48 -0400 [thread overview]
Message-ID: <4b4a8097c8ac7aeb9f46b060737376e0@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305141502520.10982-100000@maxroach.lanl.gov>
Eve is the host owner. If you are not the host owner,
then you should not be able to write to nvram.
If you are the host owner, then you can.
I just tried on my terminal:
g% echo hi >'#r/nvram'
g%
No problems. (Of course, I'll probably regret
that when I reboot.)
If the machine is running with bootes as the
host owner, then bootes should be able to
echo blah >'#r/nvram'
or even
echo blah >/dev/nvram
assuming '#r' is bound onto /dev.
next prev parent reply other threads:[~2003-05-14 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 20:48 ron minnich
2003-05-14 20:52 ` Russ Cox
2003-05-14 21:04 ` ron minnich
2003-05-14 21:11 ` Russ Cox [this message]
2003-05-14 22:02 ` 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=4b4a8097c8ac7aeb9f46b060737376e0@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).