> > lilo.conf
> > ---
> > disk=/dev/md0
> > # fdisk of hda
> > bios=0x80
> > sectors=63
> > heads=16
> > cylinders=39770
> > partition=/dev/md1
> > # from fdisk -ul -- starts at block 408
> ^ you probably mean cylinder :)
> > start=410256
> >
> > boot=/dev/hda
> >
"Michael" <[EMAIL PROTECTED]> writes:
> lilo.conf
> ---
> disk=/dev/md0
> # fdisk of hda
> bios=0x80
> sectors=63
> heads=16
> cylinders=39770
> partition=/dev/md1
> # from fdisk -ul -- starts at block 408
^ you probably mean cylinder :)
>
Martin Bene wrote:
> You CAN make lilo boot off raid1, you just have to supply all the
> info it normaly gets from getgeometry() in the config file.
Just to reiterate (again)
*OR* you can use the lilo.raid1 patch included in the SRPM of lilo
in RH 6.1
James
--
Miscellaneous Engineer --- IBM N
Martin Bene wrote:
> let me repeat
> something I learned from Harald Nordgard-Hansen
> ([EMAIL PROTECTED]) (Thanks!!):
>
> You CAN make lilo boot off raid1, you just have to supply all the
> info it normaly gets from getgeometry() in the config file.
>
This is what I have
/ /dev/md
At 19:54 20.09.99 +1000, Glenn McGrath wrote:
>none of the above can point to a file residing on a md device, if it does
>lilo gives the device not known error.
Since it still doesn't seem to be common knowledge, let me repeat something
I learned from Harald Nordgård-Hansen ([EMAIL PROTECTED]) (
What i realise now is that the lilo.conf file cant make any reference at all
to ANY files on a md device.
install=
map=
image=
none of the above can point to a file residing on a md device, if it does
lilo gives the device not known error.
I probably should have realised this before now, but th
Thanks for the advice people.
I now have a 64MB boot/emergency partition that ive actually put a mini
debian distribution on, so i can copy my linux boot files into there and
update lilo from there.
I was trying to set boot=/dev/md0 which i realise now doesnt work (thanks
for pointing that one o
