RE: Upgrade kernel from kickstart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Is there any specific reason you need to use LILO? I have run into a similar
issue, and my solution with GRUB was to run the following in the post
install:

"perl -pi -e 's/default=.*/default=0/g' /boot/grub/grub.conf"

Good luck
--N

-----Original Message-----
From: Beattie, Chad [mailto:Chad.Beattie@xxxxxx] 
Sent: Thursday, July 18, 2002 3:24 PM
To: kickstart-list@xxxxxxxxxx
Subject: Upgrade kernel from kickstart



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am working on automating a RedHat 7.3 setup on a couple of DL380
servers. I have built a custom kernel and made an rpm package from
the original src rpm for the generic kernel. After installing the
base os, I copy over some additional rpm files in the %post section
of the script. I then install the rpm packages. After the rpm's are
done, I copy over a pre-made lilo.conf file for the new kernel, the
last command I run from kickstart is /sbin/lilo -v. From watching the
install, everything works fine, even the lilo command works without
any errors. After server is rebooted, it still boots to the old
kernel. If I log into the server and run lilo again and reboot, it
boots to the new kernel. Anything I am missing here?

Here are the messages I get. This one is what I see when watching the
kickstart install via the virtual terminal:

Message when lilo is run at the end of
kickstart.

LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman

Reading boot sector from /dev/cciss/c1d0p1
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/vmlinuz-2.4.18-3
Mapping RAM disk /boot/initrd-2.4.18-3.img
Added linux-old
Boot image: /boot/vmlinuz-2.4.18-3.netmgr.v01
Mapping RAM disk /boot/initrd-2.4.18-3.netmgr.v01.img
Added linux *
Backup copy of boot sector in /boot/boot.6901
Writing boot sector.

Now, after kickstart, the boot menu only
shows linux and it still points to old kernel.
After reboot, I run lilo again. Here is the output.

LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman

Reading boot sector from /dev/cciss/c1d0p1
Merging with /boot/boo.b
ide-floppy driver 0.99.newide
hda: ATAPI 24x CD-ROM drive, 128kb Cache
Mapping message file /boot/message
Boot image: /boot/vmlinuz-2.4.18-3
Mapping RAM disk /boot/initrd-2.4.28-3.img
Added linux-old
Boot image: /boot/vmlinuz-2.4.18-3.netmgr.v01
Mapping RAM disk /boot/initrd-2.4.18-3.netmgr.v01.img
Added linux *
/boo/boot.6901 exists - no backup copy made
Writing boot sector

After this, when I reboot, I see both linux and linux-old as an
option and linux boots to my new kernel.


Here is my lilo.conf file that I copy over during the kickstart
install:

prompt
timeout=50
default=linux
boot=/dev/cciss/c1d0p1
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.18-3
label=linux-old
initrd=/boot/initrd-2.4.18-3.img
read-only
root=/dev/cciss/c1d0p2

image=/boot/vmlinuz-2.4.18-3.netmgr.v01
label=linux
initrd=/boot/initrd-2.4.18-3.netmgr.v01.img
read-only
root=/dev/cciss/c1d0p2

Chad C. Beattie
Network Engineer
Work 402-758-7744
Cell 402-203-6437


- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGPfreeware 7.0.3 for non-commercial use


mQGiBDz+W6gRBADCge5O+na+vLWOoI5V/lKsSxrCdYsHNO/n8rkhhDJFwu0abvkc
GeNJiLWVBY5mMtNrQFsBmS2uNy3zZeLTjRuxn1U863/Sr7TZwoHQbSfUYRl5OL65
/XbvXNu/UtdZTTlsukElrsApQm80T8rSrQJTkF7vTL7S4ia9q4rv/IaPuQCg/zIE
DBFR62E5oecc0mCEEZbYOI8D/2vpL8jyzzf+XLFnB6lqSEh5aVeScxD4d7gDz4vZ
YqaWJkjzDjTJDl2jq55LHvwk+tnbbjwyfWMBTgUkR+O2jGqSVkjchuERDlIQR5hj
7KX7ecm99wGB8uS3HPhN49/negYJSRYPdTTH/tOZatRDmOMkkINdl1+nfyP2xYuI
Pl7yBACqfAFj7b9tGlrT9Dd6lukBzgKKPXueZf4PifVrQVdWcWehNU+8LtvYuqqh
6kbs8DkSvQ6atdTiAqZQ+MsAARD+cB44VMoyYhctiq8mnTiVMJ9jBfeW95GOP0jU
WQingmtAfpJP8gd0JVKijf7UWHH8APVyyreCxvmkGXjSr/pNcrQlQ2hhZCBDLiBC
ZWF0dGllIDxjaGFkLmJlYXR0aWVAaHAuY29tPokAWAQQEQIAGAUCPP5bqAgLAwkI
BwIBCgIZAQUbAwAAAAAKCRATPN9ozIi4+e3DAKCFV8J0SnffedDovvZfoYT8GiHO
cgCg6XJJocOS9ixN9skZqFxtaa0KRI+5Ag0EPP5bqBAIAPZCV7cIfwgXcqK61qlC
8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyDvWXpF9Sh
01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm/xX5u/2RXscB
qtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMcfFst
jvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISn
CnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVeky
CzsAAgIH/jRcxOMlyI8Os7/VPY27t9978I4kt/QxrH7Y3jb/vsHm/8H8PYAqnSx2
+8OtNEwGOdPvddl13LYNmmE68dI4KHyNkPYn27/kldjrnEr6HalSE6XmAHc2vxil
dPpHUpG5y7lXVgEf3sUxezDk+gzpQb4h/N8sWuPuxhJYEwat9m8OdEPZQFem7Oxq
iET0Nt9LXvU/50d8C6jn23ol+Mh/s0a0LA3Vyq2b42oBAM1yjr0WrUHXu1fkLKum
IP5nAPmUpizSBitaEko0ki45ClLIbbHsMQ+vGCkjdXr/kuRXf//Gj3VpLnHsb4iL
fBV5jayTFHaoOnaxG1QSJ3tnc/vn7kCJAEwEGBECAAwFAjz+W6gFGwwAAAAACgkQ
EzzfaMyIuPmYMgCff3/uqYIXVyZUxeymzx27LweMQFcAn2oFSRiEbOfWIhYMxez+
pUUkqKmm
=MSi0
- -----END PGP PUBLIC KEY BLOCK----- 

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use 

iQA/AwUBPTcV0xM832jMiLj5EQKN0ACdF40DVjG/LAOtT8+nLd3O+lBTb0IAoPZc
f+bgQ/f6Cp2FItIi8U58JNzU
=w4JJ
-----END PGP SIGNATURE-----


------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA) that may be confidential, proprietary copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named on this message.  If you are not the intended recipient, and have received this message in error, please immediately return this by e-mail and then delete it.

==============================================================================





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux