From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] booting plan 9 from LILO (was matrox ...)
Date: Sun, 5 May 2002 02:00:31 -0400 [thread overview]
Message-ID: <7575b2c10221e528dcf38c78c9ff5216@plan9.bell-labs.com> (raw)
I've had very little luck with GRUB.
I don't think ït has a greater potential
for success than LILO. LILO is simple and
works with legacy systems. GRUB is complicated
and requires oodles of weird configuration
to make it think about talking to legacy systems.
Russ
next reply other threads:[~2002-05-05 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 6:00 Russ Cox [this message]
2002-05-05 12:39 ` Michael H.Collins
-- strict thread matches above, loose matches on Subject: below --
2002-05-06 15:26 Russ Cox
2002-05-06 13:34 Russ Cox
2002-05-06 14:35 ` Jatin Nansi
2002-05-06 12:04 Jatin Nansi
2002-05-06 9:13 Fco.J.Ballesteros
2002-05-04 17:35 Russ Cox
2002-05-04 18:47 ` Sam
2002-05-04 19:29 ` Quinn Dunkan
2002-05-05 1:31 ` Michael H.Collins
2002-05-23 18:36 ` Tomas
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=7575b2c10221e528dcf38c78c9ff5216@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).