From: frank@inua.be (Frank Lenaerts)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] panic
Date: Thu, 22 Nov 2007 16:39:58 +0100 [thread overview]
Message-ID: <20071122153958.GB12286@lisa.galaxy> (raw)
In-Reply-To: <20071121162925.GA14392@lisa.galaxy>
On Wed, Nov 21, 2007 at 05:29:26PM +0100, Frank Lenaerts wrote:
Hi,
Apart from the original problem (the panic), where should I put the
plan9.ini style file when booting via PXE from a non-Plan 9
(e.g. Linux) box. Would 9pxeload look for the file in /cfg/pxe under
the tftp root directory (e.g. /tftpboot)?
> As this machine does not have a floppy drive and I do not want to burn
> a new CD just to modify plan9.ini, I tried to boot the system using
> PXE (from a Linux machine running a dhcp and tftp server). The
> intention was to get 9pxeload to load a plan9.ini file from the Linux
> machine and to then continue booting from the CD (i.e. trying to pass
> the *noe820scan to the kernel).
>
> To do this, I did the following:
>
> - configured the dhcp server (MAC, filename...)
> - put 9pxeload in place
> - modified plan9.ini so that it contains *noe820scan and renamed it to
> the MAC address of the NIC
>
> Booting the PC using PXE loads 9pxeload but the plan9.ini file is not
> found:
>
> --- begin ---
> initial probe, to find plan9.ini...pcirouting: ...
>
> Boot devices: fd0
> boot from:
> --- end ---
>
> The 9load manpage says that the file should be put in /cfg/pxe (which
> I then created under /tftpboot on the Linux box). I thought that
> 9pxeload would request /cfg/pxe/<MAC> using TFTP but even that does
> not seem to be the case i.e. it seems as if 9pxeload doesn't request
> any file using TFTP... Could somebody explain me how it is supposed to
> work?
--
Frank Lenaerts ---------------------------------------- frank@inua.be
next prev parent reply other threads:[~2007-11-22 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 16:29 Frank Lenaerts
2007-11-21 17:02 ` erik quanstrom
2007-11-21 17:31 ` Tim Wiess
2007-11-21 18:19 ` erik quanstrom
2007-11-22 15:39 ` Frank Lenaerts [this message]
2008-09-17 16:08 Markus Sonderegger
2008-09-17 13:07 ` erik quanstrom
2008-09-17 15:04 ` geoff
2008-10-05 16:30 erik quanstrom
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=20071122153958.GB12286@lisa.galaxy \
--to=frank@inua.be \
--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).