From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <44897AB8.1070304@tecmav.com>
Date: Fri,  9 Jun 2006 15:42:16 +0200
From: Adriano Verardo <a.verardo@tecmav.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Diskless cpu servers
References: <4488C16E.3050404@tecmav.com>	<000b01c68b7b$503cadb0$14aaa8c0@utelsystems.local>
	<44892A2C.40008@Utel.no>
In-Reply-To: <44892A2C.40008@Utel.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 63d7a5ea-ead1-11e9-9d60-3106f5b1d025

Nils O. Sel=E5sdal wrote:

> Ronald G Minnich wrote:
>
>> Adriano Verardo wrote:
>>
>>> Hi, all.
>>>
>>> My i386 CPU servers have no magnetic/flash storage. The only=20
>>> solution I found to boot them
>>> without human intervention has been to add the driver of a "fake"=20
>>> nvram.
>>> It works but I'm not sure it's a good idea, because it entails to=20
>>> modify libauth
>>> to insert the new device in the list searched by factotum, wrkey etc.
>>> Instead,  I think it would be better to get the result only by=20
>>> adding files, without modifying the distribution.
>>> A more elegant solution with no consequences on the normal update=20
>>> activity by replica/pull.
>>
>
> Would this be of any help ?
>
> cpu% man plan9.ini|grep nvram
>         nvram=3Dfile
>           This is used to specify an nvram device and optionally the
>
>
The .ini file is downloaded by  9pxeload (/cfg/<macaddr>) .

I could add

     nvram=3D #Z/fknvram
     nvrlen=3D...
     nvroff=3D...

in the ini files and choose a driver letter not used for i386 (instead=20
of 'Z').
This way I could restore the original libauth etc

Correct ?

Adriano