From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: savannah
Date: Tue, 9 Aug 2005 14:37:15 +0200 [thread overview]
Message-ID: <200508091437.16103.okuji@enbug.org> (raw)
In-Reply-To: <87zmrrweep.fsf@student.han.nl>
On Tuesday 09 August 2005 13:14, Marco Gerards wrote:
> This can be easily implemented in GRUB 2 just like I implemented the
> "loopback" support. I did not know how software raid worked in GRUB
> Legacy (I did not know it had software raid support) and I do not know
> if this is the right way to implement it...
GRUB Legacy does not have explicit support, but it works with RAID 1 if you
install GRUB to /dev/md0, because the disks are just mirroring.
> > -"lilo -R"-like functionality (what's that ? an automatic fallback when
> > kernel can't be read ?) to make remote kernel changes safer.
>
> Something like this is possible with later (the latest?) GRUB Legacy
> release AFAIK/
Yes.
> > What comes up is also that most users just keep the default bootloader
> > from their distro. And grub seems to be the default bootloader in a
> > growing number of distributions.
>
> Right. I think it is our task to make GRUB 2 the default. :)
Yes, if your interest is to get many users. I'm not interested very much.
Okuji
next prev parent reply other threads:[~2005-08-09 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 20:29 savannah Yoshinori K. Okuji
2005-08-08 21:23 ` savannah Vincent Pelletier
2005-08-08 23:17 ` savannah Yoshinori K. Okuji
2005-08-09 5:23 ` savannah Vincent Pelletier
2005-08-09 11:14 ` savannah Marco Gerards
2005-08-09 12:37 ` Yoshinori K. Okuji [this message]
2005-08-09 13:20 ` savannah Marco Gerards
2005-08-09 18:46 ` savannah Yoshinori K. Okuji
2005-08-09 21:07 ` savannah Marco Gerards
2005-08-10 20:49 ` savannah Yoshinori K. Okuji
2005-08-11 10:43 ` savannah Marco Gerards
2005-08-11 13:31 ` savannah Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 10:15 Savannah Tommy Muller
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=200508091437.16103.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.