[9fans] Question on #r/nvram

[9fans] Question on #r/nvram

[ron minnich]

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

Re: [9fans] Question on #r/nvram

[Russ Cox]

> which makes it tough to reset nvram.

Only if you're not eve.  If you're not eve,
what right do you have to reset the nvram?

Re: [9fans] Question on #r/nvram

[ron minnich]

On Wed, 14 May 2003, Russ Cox wrote:

> Only if you're not eve.  If you're not eve,
> what right do you have to reset the nvram?

Yes, that is true. It makes all kinds of sense until you have a bad key in
CMOS. What's the approved way to nuke the bad key in CMOS besides yanking
the battery?

In other words, I can do this as bootes
echo blah > /dev/sdC0/nvram
but can not do this:
echo blah > /dev/rtc/nvram

and that would be useful.

ron

Re: [9fans] Question on #r/nvram

[Russ Cox]

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.

Re: [9fans] Question on #r/nvram

[ron minnich]

On Wed, 14 May 2003, Russ Cox wrote:

> 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.

hokay, I'll try it again.

thanks

ron