9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ethernet booting
Date: Sun,  1 Aug 2010 16:54:45 -0700	[thread overview]
Message-ID: <AANLkTinQf=gFhVzmj0ufhGY6kRXP5mQ2wp_3v3Gm8oxa@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim_P+X=romBmgmGKzghHtuteX_xuq8niTdNQq4d@mail.gmail.com>

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
<akumar@mail.nanosouffle.net> wrote:
> 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
> <akumar@mail.nanosouffle.net> wrote:
>> On Sun, Aug 1, 2010 at 3:28 PM, Steve Simon <steve@quintile.net> 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 various places; in the case of PXE, it even searches over
>> ethernet at /cfg/pxe/MAC. It would be enough if this case was
>> extended to the general loader, instead of just 9pxeload (what's
>> so special about that anyways?).
>>
>>
>> ak
>>
>



      reply	other threads:[~2010-08-01 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-01 21:52 Akshat Kumar
2010-08-01 22:28 ` Steve Simon
2010-08-01 23:05   ` Akshat Kumar
2010-08-01 23:38     ` Akshat Kumar
2010-08-01 23:54       ` Akshat Kumar [this message]

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='AANLkTinQf=gFhVzmj0ufhGY6kRXP5mQ2wp_3v3Gm8oxa@mail.gmail.com' \
    --to=akumar@mail.nanosouffle.net \
    --cc=9fans@9fans.net \
    /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).