lilo -v -t says nothing?
nastos-JAjqph6Yjy8fbXvGcxQkLSwD8/FfD2ys at public.gmane.org
Mon Dec 15 04:51:16 UTC 2003
On December 14, 2003 11:27 pm, Alan Cohen wrote:
> -rw-r--r-- 1 520771 Aug 18 11:34 System.map-2.4.20-20.9
> -rw-r--r-- 1 520771 Dec 1 11:56 System.map-2.4.20-24.9
> -rw-r--r-- 1 518292 Feb 27 2003 System.map-2.4.20-6
> -rw-r--r-- 1 3180534 Aug 18 11:34 vmlinux-2.4.20-20.9
> -rw-r--r-- 1 3180534 Dec 1 11:56 vmlinux-2.4.20-24.9
> -rw-r--r-- 1 3149037 Feb 27 2003 vmlinux-2.4.20-6
> lrwxrwxrwx 1 19 Dec 6 22:10 vmlinuz -> vmlinuz-2.4.20-24.9
> -rw-r--r-- 1 1117322 Aug 18 11:34 vmlinuz-2.4.20-20.9
> -rw-r--r-- 1 1117198 Dec 1 11:56 vmlinuz-2.4.20-24.9
> -rw-r--r-- 1 1117057 Feb 27 2003 vmlinuz-2.4.20-6
It looks like everything is there.
$] lilo -t -v -v
(-v times two gives even more info).
If that doesn't give anything, then what happens if you do the following:
i) create an empty file called test_lilo.cfg
$] touch test_lilo.cfg
ii) as root, run
$] lilo -t -C test_lilo.cfg
It should say "Fatal: No images have been defined."
> > It was my understanding that up2date properly installs the kernel, and
> > runs /sbin/lilo for you, and if that fails then it tells you... but I may
> > be mistaken.
> up2date did modify lilo.conf but didn't run /sbin/lilo
> (However it did advise me to do so.)
Hmm... to install a new kernel when using lilo, /sbin/lilo must be run, right?
I've up2dated my kernel about seven times in the past couple of years using
up2date, and I never had to run /sbin/lilo myself. I've had to do everything
by hand if I removed a kernel, but not when downloading. The kernel was
downloaded from redhat?
> In any case, I would have at least
> expected /sbin/lilo -t to at least say something like
> "The boot sector and the map files has NOT been altered"
Yes, I would have expected that also.
The Toronto Linux Users Group. Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
More information about the Legacy