1. FC4 used to use /dev/hdx in both lilo.conf and in /etc/fstab and
those need to be changed to /dev/sdx
2. after fixing the above references, just run...
/sbin/lilo -v
it should work
Craig
On Thu, 2008-06-26 at 23:02 +0200, Thomas Rabaix wrote:
Ok, my host install FC4 with lilo, so I update to F8. I suppose the
update script from Fedora keep lilo and don't use grub at all.
Now how can I reinstall lilo to make boot.b appears. I have only one
chance :) (remote location)
I am not sure that my system will reboot properly without this file,
am i right ?
Thanks
Thomas
On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt <mschwendt(a)gmail.com> wrote:
> On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote:
>
>> On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote:
>> > On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
>> >
>> > > watching this thread with interest.
>> > >
>> > > I have several Dell Optiplex 320's that will not boot with grub
but will
>> > > boot with lilo and so I have lilo installed on them.
>> >
>> > Is this problem known upstream?
>> ----
>> very much so
>>
https://bugzilla.redhat.com/show_bug.cgi?id=379201
>>
https://bugzilla.redhat.com/show_bug.cgi?id=219715
>
> Those are about grub and the kernel. If you think grubby suffers from a
> bug when updating LILO installations, grubby is part of the "mkinitrd"
> package.
>
>> ----
>> >
>> > > Unfortunately though, kernel updates do produce the error above
(unable
>> > > to open /boot/boot.b) generated by grubby. Is there any way around
>> > > getting grubby to re-run lilo to execute an update when new kernels
are
>> > > installed?
>> >
>> > With LILO, no. LILO must be rewritten with every change in lilo.conf.
>> > GRUB, on the contrary, must not be rewritten after modifying grub.conf,
>> > because it can read the ext2/ext3 fs directly to load its config file.
>> >
>> > If you're interested in where grubby is executed, take a look at
>> > /sbin/new-kernel-pkg which is called by the "kernel" package
scriptlets.
>> ----
>> been there...never could figure out what to change
>> as noted here...
>>
https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18
>
> Well, if you have reason to believe that grubby does something wrong,
> find out what it does wrong. Run it manually, it has a man page, too.
> And /boot/boot.b must exist when it is specified in lilo.conf. Do you
> say that grubby deletes that file by accident?
>
> And if you're really fed up with grubby, you could modify new-kernel-pkg
> to execute your own lilo-update script/program instead of grubby.
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
>