From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pc boot and ether drivers
Date: Wed, 17 Nov 2004 23:10:42 -0800 [thread overview]
Message-ID: <c47509b339115b2daedbf2d3d2f4de91@collyer.net> (raw)
In-Reply-To: <Pine.BSI.4.58.0411171749100.6130@malasada.lava.net>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
That's just plan9.ini with data supplied by a different boot loader,
presumably at a different memory address.
I'd rather have the kernel pick the first (supported) ethernet
interface in the PCI tables and use that to boot load via /cfg/pxe,
thus putting the plan9.ini's in one place.
[-- Attachment #2: Type: message/rfc822, Size: 3018 bytes --]
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] pc boot and ether drivers
Date: Wed, 17 Nov 2004 17:54:51 -1000 (HST)
Message-ID: <Pine.BSI.4.58.0411171749100.6130@malasada.lava.net>
> Command line to what? The kernels don't have command lines.
Many boot loaders provide arguments to the booting kernel.
I don't think it should be very difficult to craft a command
line such as:
9pcdisk bootdisk=local!#S/sdC0/fs *nomp=1 monitor=multisync75
vgasize=1024x768x8
parsing this out from a single argument buffer should be a
trivial addition to the current sources. Looks like getting
at this data is pretty simple:
http://www.gnu.org/software/grub/manual/multiboot/html_node/Boot-information-format.html#Boot%20information%20format
Tim N.
next prev parent reply other threads:[~2004-11-18 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 1:55 Tim Newsham
2004-11-17 2:09 ` geoff
2004-11-17 2:11 ` jmk
2004-11-18 0:54 ` Vester Thacker
2004-11-18 1:28 ` Eric Van Hensbergen
2004-11-18 2:32 ` Karl Magdsick
2004-11-18 2:43 ` geoff
2004-11-18 3:09 ` Tim Newsham
2004-11-18 3:16 ` geoff
2004-11-18 3:54 ` Tim Newsham
2004-11-18 4:01 ` Russ Cox
2004-11-18 4:53 ` jmk
2004-11-18 6:04 ` Vester Thacker
2004-11-18 10:39 ` C H Forsyth
2004-11-18 11:45 ` Vester Thacker
2004-11-18 7:10 ` geoff [this message]
2004-11-18 4:16 ` bs
2004-11-18 3:40 ` Russ Cox
2004-11-18 4:26 ` Vester Thacker
2004-11-18 4:34 ` Vester Thacker
2004-11-18 16:23 ` Ronald G. Minnich
2004-11-18 15:08 ` Ronald G. Minnich
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=c47509b339115b2daedbf2d3d2f4de91@collyer.net \
--to=geoff@collyer.net \
--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).