ah ok well i have seem the contents of /boot and yes there are files called
vmlinux-2.4.18-14
and
vmlinux-2.4.18-24.8.0
things do look ok.
but in another post to this list i mentioned that when visiting
/lib/modules/
i saw dirs called
linux-2.4.18-14/
linux-2.4.18-24.8.0/
in the 2.4.18-14 one there was a sym link called build, linked to
/urr/src/linux-2.4.18-14/
but in the /lib/modules/linux-2.4.18-24.8.0 , there was a build sym link that was
broken. i.e. no target
on investigating /usr/src i found
linux-2.4.18-14/
redhat/
linux-2.4 (some kind of symlink)
but no dir for linux-2.4.18-24.8.0
i do not think the source was built, and so the build sym link was created broken.
some replies to my post suggested installing the i386 version of the kernel source
(rather than the SRPMs version). on trying this, i still get no dir
linux-2.4.18-24.8.0/ being created in /usr/src
anyway could this grubby error thing when installing the actual kernel be a cause of
some difficulties in other things not being placed properly? and could this be the
cause of the lilo dirty buffer error?
-----Original Message-----
From: Michael Fratoni [mailto:[EMAIL PROTECTED]
Sent: Thursday, 6 March 2003 1:44 PM
To: [EMAIL PROTECTED]
Subject: Re: grubby complains
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 05 March 2003 06:24 pm, Mirabella, Mathew J wrote:
> ok i use lilo.
> here is the lilo.conf
>
> prompt
> timeout=50
> default=linux
> boot=/dev/hda5
> map=/boot/map
> install=/boot/boot.b
> message=/boot/message
> lba32
>
> image=/boot/vmlinuz-2.4.18-14
> label=linux.old
> initrd=/boot/initrd-2.4.18-14.img
> read-only
> append="hdd=ide-scsi root=LABEL=/ speakup_synth=dectlk"
>
> image=/boot/vmlinuz-2.4.18-24.8.0
> label=linux
> initrd=/boot/initrd-2.4.18-24.8.0.img
> read-only
> append="hdd=ide-scsi root=LABEL=/ speakup_synth=dectlk"
>
> the second image is the newer updated kernal.
Did you add the stanza for the new kernel manually, or did the kernel rpm
scripts do it? I haven't used lilo for a while, but the config looks OK
to me.
> here is the output from lilo
>
> LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
> 'lba32' extensions Copyright (C) 1999,2000 John Coffman
[snip]
> but at the end, a dirty buffer error appeared, but i think this would
> have gone to standard error because it did not come out in the file
> when i redirected lilo to the file with > maybe i have done the wrong
> thing here...
It was mainly the error message I wanted to see. ;) Try this:
lilo -v > lilo.out 2>&1
That will direct stdout and stderr to the file lilo.out
> rpm -q kernel gives
> kernal-2.4.18-14
> kernal-2.4.18-24.8.0
>
> and sorry, i forgot to get the output of 'ls /boot/{vmlinuz*,initrd*}'
That's fine, I just wanted to be sure the files listed in the config file
existed in /boot/
> anyway can you tell me an easy way to dump the contents of a console to
> a file...?
You mean redirect output as the command above?
- --
- -Michael
pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+ZrYKn/07WoAb/SsRAhiPAJ9Tz+bYDm0hfbUSCyS/zHZte/SYZwCgluU1
JZybu3oNGWKU78gd7sA+sg8=
=TmBt
-----END PGP SIGNATURE-----
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
