From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Replacing 9load
Date: Mon, 5 Dec 2005 11:42:28 -0800 [thread overview]
Message-ID: <3e1162e60512051142i58a2fddeu3bcbfa23ac63d5ff@mail.gmail.com> (raw)
In-Reply-To: <20051204044833.GD9700@server4.lensbuddy.com>
> My comments about grub still stand. It's great for booting
> Linux kernels, which it was designed for, and it is okay for
> chainloading to get to Plan 9. I still think Smart Boot Manager
> is far and away the best PC multi-OS booter out there. It looks
> at the partitions and says "here is what I found: pick one."
> No manual config. In grub you have to boot to Linux to tell it
> about a new Plan 9 partition. Grub is really a Linux loader
> disguised as a multiboot loader. In that situation it works great.
> Beyond that it's just a pain.
Actually, it was meant for GNU Hurd as it loads microkernels and
modules containing drivers and other bits of a "system" into separate
address spaces.
GRUB2 works on PPC platforms as well now for the same effect. [the
solution for L4 based systems was to build a monolithic "piggybacked"
image to achieve the multiboot effect]
I agree chainloader is a bit of a pain in the ass. Grub has
filesystem modules and ways to do things like set VESA modes before
you boot an OS [used with House for example... written in Haskell
using the GHC runtime as OS services, yes ethernet drivers written in
Haskell.]
grub is also capable of adding netboot capabilities to old PCs that
didn't have the BIOS for it. I used to boot an old P2 with a grub
floppy to netboot OSes on it because it had no hard disk.
Grub has a lot of value to me as a result for some of these projects.
I've not seen another loader come along that can provide me with that
level of configuration [besides perhaps OpenFirmware on my mac....
even that needs Grub2 to do multiboot stuff though]
>
> Finally, do not believe even for a moment that Plan 9 thinks
> that all the world's a 386. We have always had a couple other
> architectures running, and running well. That's still true today.
> On the other hand, if you're writing a pc kernel, you're going
> to have to do some pc-specific things.
I just wish BIOS would die a quick painful death and we can move on to
something else. OpenFirmware would have been my preference but EFI
appears to be the way for PCs.
>
> Russ
>
> ----- End forwarded message -----
>
> If I can find the irc logs I'll post them for context, but I don't think
> any of us said anything very useful.
>
> uriel
>
next prev parent reply other threads:[~2005-12-05 19:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 4:48 Uriel
2005-12-04 7:01 ` jmk
2005-12-04 16:00 ` Russ Cox
2005-12-04 16:56 ` Nigel Roles
2005-12-04 19:07 ` Charles Forsyth
2005-12-04 19:29 ` jmk
2005-12-04 22:13 ` C H Forsyth
2005-12-05 19:42 ` David Leimbach [this message]
2005-12-05 20:11 ` jmk
2005-12-05 20:47 [9fans] replacing 9load Russ Cox
2005-12-05 20:52 ` William Josephson
2005-12-05 21:02 ` Ronald G Minnich
2005-12-05 21:06 ` Charles Forsyth
2005-12-05 23:22 ` Ronald G Minnich
2005-12-05 21:21 ` Russ Cox
2005-12-05 23:27 ` Ronald G Minnich
2005-12-05 23:33 ` Russ Cox
2005-12-06 0:19 ` 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=3e1162e60512051142i58a2fddeu3bcbfa23ac63d5ff@mail.gmail.com \
--to=leimy2k@gmail.com \
--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).