9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Karl Magdsick <kmagnum@gmail.com>
To: Eric Van Hensbergen <ericvh@gmail.com>,
	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 21:32:42 -0500	[thread overview]
Message-ID: <cd8ecdef041117183241b55f37@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a04111717284511bdbe@mail.gmail.com>

How difficult would it be to make the Plan9 kernel compliant with the
MultiBoot standard?

This would seem to be the path of least resistance for getting the
Plan9 kernel working with other bootloaders.  In addition to working
"out of the box" with MultiBoot bootloaders, there are tools that will
wrap any MultiBoot kernel (plus any modules) along with some stub code
into an image that can be booted by any bootloader that can boot a
Linux kernel.  There is a similar tool to get any MultiBoot kernel
(plus any modules) to mimic one of the BSD kernels.


-Karl

On Wed, 17 Nov 2004 19:28:20 -0600, Eric Van Hensbergen
<ericvh@gmail.com> wrote:
> On Thu, 18 Nov 2004 09:54:40 +0900, Vester Thacker
> <vester.thacker@gmail.com> wrote:
> > On Tue, 16 Nov 2004 21:11:42 -0500, jmk@plan9.bell-labs.com
> > <jmk@plan9.bell-labs.com> wrote:
> >
> > Are you looking for volunteers for creating a new
> > bootstrap? If so, then maybe a working group
> > could be formed... something akin to what EricVH
> > has done with v9fs.
> >
> 
> Personally, I'd rather see us punt on the whole loader issue
> where-ever possible.  It seems reasonable enough to use "other
> people's loaders" to boot Plan 9.  I believe Ron talks about booting
> Plan 9 from LinuxBIOS on the Wiki and I'm sure other loaders could be
> made to work.  We have enough to do without having to worry about
> writing boot loaders.
> 
>           -eric
>


  reply	other threads:[~2004-11-18  2:32 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 [this message]
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
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=cd8ecdef041117183241b55f37@mail.gmail.com \
    --to=kmagnum@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=ericvh@gmail.com \
    /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).