From: frank@inua.be
To: 9fans@9fans.net
Subject: Re: [9fans] plan9.ini bootfile= syntax for 9pxeload client?
Date: Thu, 9 Dec 2010 16:45:41 +0100 [thread overview]
Message-ID: <20101209154541.GB8123@chiron.galaxy> (raw)
In-Reply-To: <F156DF30-C96D-4281-AA0D-C83BD77C1F26@xmission.com>
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
prev parent reply other threads:[~2010-12-09 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 15:32 Lloyd Caldwell
2010-12-09 15:39 ` erik quanstrom
2010-12-09 15:55 ` Lloyd Caldwell
2010-12-09 15:45 ` frank [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=20101209154541.GB8123@chiron.galaxy \
--to=frank@inua.be \
--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).