From: Michael Tokarev <mjt@tls.msk.ru>
To: Lewis Shobbrook <mylists@blue-matrix.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Grub vs Lilo
Date: Wed, 26 Jul 2006 14:40:11 +0400 [thread overview]
Message-ID: <44C7468B.4070500@tls.msk.ru> (raw)
In-Reply-To: <200607261943.24828.mylists@blue-matrix.org>
Lewis Shobbrook wrote:
> Hi All,
>
> Wondering if anyone can comment on an easy way to get grub to update all
> components in a raid1 array. I have a raid1 /boot with a raid10 /root and
> have previously used lilo with the raid-extra-boot option to install to boot
> sectors of all component devices. With grub it appears that you can only
> update non default devices via the command line. I like the ability to be
> able to type lilo and have all updated in one hit. Is there a way to do this
> with grub?
You only need to update stuff for grub once - when installing it.
And during installation, it's ok to run it multiple times, once for
each component device - not a big deal really. Just like you will
partition your disks and install an MBR - once for each disk.
After installation, grub does not need to modify boot records - only
/boot/grub/menu.lst (whatever) file is updated to reflect your kernels,
and this is a normal file (grub will find it by its own, by properly
reading the filesystem).
/mjt
next prev parent reply other threads:[~2006-07-26 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 9:43 Grub vs Lilo Lewis Shobbrook
2006-07-26 10:40 ` Michael Tokarev [this message]
2006-07-26 16:44 ` Jason Lunz
2006-07-26 18:00 ` Michael Tokarev
2006-07-26 18:59 ` Bernd Rieke
2006-07-26 19:58 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 13:16 Lewis Shobbrook
2006-07-27 11:50 ` Simen Thoresen
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=44C7468B.4070500@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=mylists@blue-matrix.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 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).