Thomas Rabaix wrote:
<snip>
----
to g :
# lilo -v -t
LILO version 22.7.3 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006.
Reading boot sector from /dev/sda
Using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz-2.6.25.6-27.fc8
Mapping RAM disk /boot/initrd-2.6.25.6-27.fc8.img
Added 2.6.25.6-27.fc8 *
Boot image: /boot/vmlinuz-2.6.24.7-92.fc8
Mapping RAM disk /boot/initrd-2.6.24.7-92.fc8.img
Added 2.6.24.7-92.fc8
Boot image: /boot/bzImage-2.6.24.5-xxxx-grs-ipv4-32
Added linux
The boot sector and the map file have *NOT* been altered.
----
isn't that because you are running '-t' (test) instead of just
installing?
craig,
this is true, as noted in 1st line of lilo response, it proves out
what i was wondering about his concern over 'boot.b' missing.
Yes I just return the command asked by geleem@xxxxxxxxxxxxx
thomas,
tho i did not ask for posting results, i am glad you did. reason being is
that as you will note, test ran 100% clean. if it had not, you would not
have seen last line, it would have stopped on 1st error and noted what
was in error. therefore it will work.
as for having 'install=boot.p' in config, it is not relevant. in one of
my 'lilo.conf' i have 'install=menu' and why i was curious as to what
would happen, as i have no 'menu' in '/boot' directory.
so, a couple of suggestions;
1) make room on hard drive, 4 to 5 gigs for when you need to install
a new kernel, then you can have a 'fall back' to old kernel if new bombs
on you and you can still get back up. it will require a short script
in an early rc.d to do a time out and reboot if things fail.
2) log this site, http://freshmeat.net/~johncoffman/
and have a session with john.
hth.
--
tc,hago.
g
.
in a free world without fences, who needs gates.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
