From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] Question on #r/nvram
Date: Wed, 14 May 2003 14:48:05 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0305141446220.10982-100000@maxroach.lanl.gov> (raw)
Is there any reason to have #r/nvram readable and writeable only be eve?
Is this historical? I have commented out the permission check for eve but
I'm wondering if that is the wrong thing to do.
You can't really do this with the eve permission check:
bind '#r' rtc
echo blah > rtc/nvram
which makes it tough to reset nvram.
thanks
ron
next reply other threads:[~2003-05-14 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 20:48 ron minnich [this message]
2003-05-14 20:52 ` Russ Cox
2003-05-14 21:04 ` ron minnich
2003-05-14 21:11 ` Russ Cox
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=Pine.LNX.4.44.0305141446220.10982-100000@maxroach.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).