From: benavento@gmail.com (Federico G. Benavento)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Diskless cpu servers
Date: Fri, 9 Jun 2006 10:53:54 -0300 [thread overview]
Message-ID: <59f11e6e99544f6453ed1bb4147bdd95@yourdomain.dom> (raw)
In-Reply-To: <44897AB8.1070304@tecmav.com>
[-- Attachment #1: Type: text/plain, Size: 93 bytes --]
I just remembered about this:
http://rs-rlab.narod.ru/9nvram.html
Federico G. Benavento
[-- Attachment #2: Type: message/rfc822, Size: 4453 bytes --]
From: Adriano Verardo <a.verardo@tecmav.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Diskless cpu servers
Date: Fri, 09 Jun 2006 15:42:16 +0200
Message-ID: <44897AB8.1070304@tecmav.com>
Nils O. Selåsdal wrote:
> Ronald G Minnich wrote:
>
>> Adriano Verardo wrote:
>>
>>> Hi, all.
>>>
>>> My i386 CPU servers have no magnetic/flash storage. The only
>>> solution I found to boot them
>>> without human intervention has been to add the driver of a "fake"
>>> nvram.
>>> It works but I'm not sure it's a good idea, because it entails to
>>> 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
>>> adding files, without modifying the distribution.
>>> A more elegant solution with no consequences on the normal update
>>> activity by replica/pull.
>>
>
> Would this be of any help ?
>
> cpu% man plan9.ini|grep nvram
> nvram=file
> This is used to specify an nvram device and optionally the
>
>
The .ini file is downloaded by 9pxeload (/cfg/<macaddr>) .
I could add
nvram= #Z/fknvram
nvrlen=...
nvroff=...
in the ini files and choose a driver letter not used for i386 (instead
of 'Z').
This way I could restore the original libauth etc
Correct ?
Adriano
next prev parent reply other threads:[~2006-06-09 13:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 0:31 Adriano Verardo
2006-06-09 0:35 ` andrey mirtchovski
2006-06-09 14:41 ` Adriano Verardo
2006-06-09 4:13 ` Ronald G Minnich
[not found] ` <000b01c68b7b$503cadb0$14aaa8c0@utelsystems.local>
2006-06-09 7:58 ` "Nils O. Selåsdal"
2006-06-09 13:02 ` Ronald G Minnich
2006-06-09 13:09 ` Charles Forsyth
2006-06-09 13:23 ` Ronald G Minnich
2006-06-09 13:27 ` Charles Forsyth
2006-06-09 14:43 ` Ronald G Minnich
2006-06-09 13:42 ` Adriano Verardo
2006-06-09 13:53 ` Federico G. Benavento [this message]
2006-06-09 9:22 ` Steve Simon
2006-06-09 10:53 ` Charles Forsyth
2006-06-09 13:28 ` Adriano Verardo
2006-06-09 13:03 ` Ronald G Minnich
2006-06-10 18:32 ` Adriano Verardo
2006-06-09 14:30 jmk
2006-06-09 16:54 ` Dave Lukes
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=59f11e6e99544f6453ed1bb4147bdd95@yourdomain.dom \
--to=benavento@gmail.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).