[9fans] plan9.ini bootfile= syntax for 9pxeload client?

[9fans] plan9.ini bootfile= syntax for 9pxeload client?

[Lloyd Caldwell]

Trying to boot a plan9 diskless terminal (pc) over network. The boot
"master" is a combined cpu/fs/auth server.

dhcp/tftp works to set diskless terminal ethernet ip, fs and auth ip
addresses and downloads 9pxeload to diskless terminal.  9pxeload then
fails with an exception.

I suspect it fails because I haven't told 9pxeload how to load what
kernel.  I have created the /cfg/pxe/<etheraddr> file but have yet to
guess the correct incantation of syntax to specify the kernel location.

each man page (boot, booting, plan9.ini, 9load) directs the reader to
another page that also doesn't specify how to network load a kernel
on a pc.  I think the bootfile= option of the /cfg/pxe/<etheraddr>
plan9.ini file would be where to specify the kernel?

I have included ether0=type=i82557 in this file so 9pxeload knows
which device to use.

The 9load man page says that the plan9.ini file attribute
bootfile=device!file or bootfile=device!partition!file specifies what
kernel to load. However it says if you specify ether0 for device,
'file' is determined by /lib/ndb which just loaded 9pxeload, which is
pretty circular logic (imho).  I've tried bootfile=manual to no avail.

An example of a /cfg/pxe/<etheraddr> plan9.ini diskless boot file
would be great or the actual syntax to successfully induce 9pxeload
to suck down a kernel and run it would be even better.

couldn't find this info on the list either, sorry if this has been
previously resolved.

Lloyd Caldwell
lmc@xmission.com

Re: [9fans] plan9.ini bootfile= syntax for 9pxeload client?

[erik quanstrom]

> dhcp/tftp works to set diskless terminal ethernet ip, fs and auth ip
> addresses and downloads 9pxeload to diskless terminal.  9pxeload then
> fails with an exception.
>
> I suspect it fails because I haven't told 9pxeload how to load what
> kernel.  I have created the /cfg/pxe/<etheraddr> file but have yet to
> guess the correct incantation of syntax to specify the kernel location.

in addition, you need to add "bootf=/386/9pxeload" in the /lib/ndb/local
entry for this machine.

> I have included ether0=type=i82557 in this file so 9pxeload knows
> which device to use.

not necessary.

> The 9load man page says that the plan9.ini file attribute
> bootfile=device!file or bootfile=device!partition!file specifies what
> kernel to load. However it says if you specify ether0 for device,
> 'file' is determined by /lib/ndb which just loaded 9pxeload, which is
> pretty circular logic (imho).  I've tried bootfile=manual to no avail.

the kernel is specified in /cfg/pxe/<ea>.  e.g.
nobootprompt=ether0!/386/9pccpu

- erik

Re: [9fans] plan9.ini bootfile= syntax for 9pxeload client?

[frank]

On Thu, Dec 09, 2010 at 08:32:21AM -0700, Lloyd Caldwell wrote:
> I suspect it fails because I haven't told 9pxeload how to load what
> kernel.  I have created the /cfg/pxe/<etheraddr> file but have yet to
> guess the correct incantation of syntax to specify the kernel location.
>
> each man page (boot, booting, plan9.ini, 9load) directs the reader to
> another page that also doesn't specify how to network load a kernel on a
> pc.  I think the bootfile= option of the /cfg/pxe/<etheraddr> plan9.ini
> file would be where to specify the kernel?
>
> I have included ether0=type=i82557 in this file so 9pxeload knows which
> device to use.
>
> The 9load man page says that the plan9.ini file attribute
> bootfile=device!file or bootfile=device!partition!file specifies what
> kernel to load. However it says if you specify ether0 for device, 'file'
> is determined by /lib/ndb which just loaded 9pxeload, which is pretty
> circular logic (imho).  I've tried bootfile=manual to no avail.
>
> An example of a /cfg/pxe/<etheraddr> plan9.ini diskless boot file would be
> great or the actual syntax to successfully induce 9pxeload to suck down a
> kernel and run it would be even better.

bootfile=ether0!/386/9pc
        nobootprompt=tcp!192.168.1.12!564
        mouseport=ps2
        monitor=vesa
        vgasize=1024x768x8

with 192.168.1.12 being my cpu/fs server.

> Lloyd Caldwell

--
Frank Lenaerts ---------------------------------------- frank@inua.be

Re: [9fans] plan9.ini bootfile= syntax for 9pxeload client?

[Lloyd Caldwell]

On Dec 9, 2010, at 8:39 AM, erik quanstrom wrote:

>> dhcp/tftp works to set diskless terminal ethernet ip, fs and auth ip
>> addresses and downloads 9pxeload to diskless terminal.  9pxeload then
>> fails with an exception.
>>
>> I suspect it fails because I haven't told 9pxeload how to load what
>> kernel.  I have created the /cfg/pxe/<etheraddr> file but have yet to
>> guess the correct incantation of syntax to specify the kernel
>> location.
>
> in addition, you need to add "bootf=/386/9pxeload" in the /lib/ndb/
> local
> entry for this machine.

had this :)
>
>> I have included ether0=type=i82557 in this file so 9pxeload knows
>> which device to use.
>
> not necessary.
>
>> The 9load man page says that the plan9.ini file attribute
>> bootfile=device!file or bootfile=device!partition!file specifies what
>> kernel to load. However it says if you specify ether0 for device,
>> 'file' is determined by /lib/ndb which just loaded 9pxeload, which is
>> pretty circular logic (imho).  I've tried bootfile=manual to no
>> avail.
>
> the kernel is specified in /cfg/pxe/<ea>.  e.g.
> nobootprompt=ether0!/386/9pccpu
>
Awe the magic incantation, THANKS!  Maybe the man page should be
"revised"?

> - erik
>