From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PXE
Date: Thu, 18 Sep 2003 10:45:12 -0400 [thread overview]
Message-ID: <76e6091ee713d2fb1857a0dd75d58ac0@plan9.bell-labs.com> (raw)
In-Reply-To: <20030916191304.H9751@cackle.proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
No documentation. I have to finish the PXE stuff to make it a little easier.
Right now, I use PXE to get a 9load and then type the real kernel address
by hand when 9load prompts.
What I intend to do is have an extra entry in the ndb that indicates which
file to download for PXE and which for 9load. I can distinguish using the
vendor id (or some such). I'm on vacation but I'll finish it when I get back,
not a lot of work.
[-- Attachment #2: Type: message/rfc822, Size: 2769 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] PXE
Date: Tue, 16 Sep 2003 19:13:05 +0200
Message-ID: <20030916191304.H9751@cackle.proxima.alt.za>
I now have a VXL Precio diskless workstation that I would like to run
Plan 9 on. I can convince it to use PXE to boot, but I don't know
quite what's involved to make it work properly.
Right now, it looks like it doesn't even register a DHCP requests, but
I really don't know enough about PXE (in fact, I think I know
precisely nothing about PXE) to judge.
What seems I ought to know, anyway, is how I can tuck a plan9.ini
somewhere for 9pxeload to find it, if I can get PXE to load it, of
course.
Is anyone preapred to give me a crash course on PXE for Plan 9? Or
point me to relevant documentation?
++L
next prev parent reply other threads:[~2003-09-18 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 17:13 Lucio De Re
2003-09-18 14:45 ` David Presotto [this message]
2004-11-07 13:36 Sergey Reva
2004-11-07 13:39 ` Sape Mullender
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=76e6091ee713d2fb1857a0dd75d58ac0@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).