Mailinglist Archive: opensuse-factory (475 mails)
| < Previous | Next > |
Re: [opensuse-factory] Dropping lilo support from YaST
- From: Kevin Ivory <Ivory@xxxxxxxxx>
- Date: Fri, 01 Aug 2008 11:21:16 +0200
- Message-id: <E1KOqp2-006QJG-HH@xxxxxxxxxxxxxxxx>
Hi,
On 2008-07-31 18:09, Stanislav Visnovsky wrote:
We use lilo for all Software RAID1 systems on SLES & openSUSE
the typical lilo.conf entries are:
raid-extra-boot = mbr-only
boot = /dev/md3
root = /dev/md3
Calling lilo then automatically writes the boot-records on the
necessary disks:
The Master boot record of /dev/sda has been updated.
Warning: /dev/sdb is not on the first disk
The Master boot record of /dev/sdb has been updated.
Is this as easily possible with Grub/YaST combination?
Kevin
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.SerNet.DE, mailto: Info @ SerNet.DE
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
On 2008-07-31 18:09, Stanislav Visnovsky wrote:
Any feedback appreciated.
We use lilo for all Software RAID1 systems on SLES & openSUSE
the typical lilo.conf entries are:
raid-extra-boot = mbr-only
boot = /dev/md3
root = /dev/md3
Calling lilo then automatically writes the boot-records on the
necessary disks:
The Master boot record of /dev/sda has been updated.
Warning: /dev/sdb is not on the first disk
The Master boot record of /dev/sdb has been updated.
Is this as easily possible with Grub/YaST combination?
Kevin
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.SerNet.DE, mailto: Info @ SerNet.DE
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |