Ah, I got PXE to work - there is a special and hidden
configuration menu for the boot agent. The easter egg
was hidden at CTRL + ALT + B.
On Sun, Aug 1, 2010 at 4:38 PM, Akshat Kumar
wrote:
> The real problem here being that my 3com ethernet
> card grabs 9pxeload (or so it seems) via BOOTP
> and
The real problem here being that my 3com ethernet
card grabs 9pxeload (or so it seems) via BOOTP
and TFTP, but then can't run the damn thing.
The ROM has Managed PC Boot Agent (MBA) v4.32.
However, downloading and running 9load works
just fine.
On Sun, Aug 1, 2010 at 4:05 PM, Akshat Kumar
wrote:
On Sun, Aug 1, 2010 at 3:28 PM, Steve Simon wrote:
>> Can I get it to download
>> the INI file as well, some how?
>
> I don't beleive so.
>
> Normally the plan9.ini is be read from the same
> device that 9load is loaded from.
see /sys/src/boot/pc/load.c - the loader searches for plan9.ini
in vari
> Can I get it to download
> the INI file as well, some how?
I don't beleive so.
Normally the plan9.ini is be read from the same
device that 9load is loaded from.
-Steve
I'm booting over ethernet, using the basic 9load (not 9pxeload).
However, in /lib/ndb/local on my CPU server (where it downloads
9load), I can only specify
bootf=/386/9load
that is, I can't specify an INI file. I know the 9pxeload loader looks
in /cfg/pxe/ to grab INI details; what can be done fo
