Hi Luca
'grubby' is the tool to automate modifications to /etc/grub.conf (and the config files of other boot loaders).
Amongst other things, in my %post section I have
grubby --grub --update-kernel=`grubby --default-kernel` --args "${KERNEL_PARAMS} root=LABEL=/"
Where $KERNEL_PARAMS are programatically determined previous in the %post section.
Hope this helps.
CC
________________________________
From: kickstart-list-bounces@xxxxxxxxxx on behalf of Mariani, Luca
Sent: Wed 3/7/2007 6:55 PM
To: Discussion list about Kickstart
Subject: RE: kernel parameters
Hi CC,
the only reason that let me modify kickstart files in order to add kernel parameters is that it was the only way I knew to do it
do you think it should be better using grubby? I'll try this way too.
thanks
/Luca
________________________________
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Coe, Colin C. (Unix Engineer)
Sent: 06 March 2007 22:46
To: Discussion list about Kickstart
Subject: RE: kernel parameters
Hi Luca
Is there a reason you can't call grubby from the %post section to add the parameters you need?
CC
-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Mariani, Luca
Sent: Wednesday, 7 March 2007 12:52 AM
To: Discussion list about Kickstart
Subject: RE: kernel parameters
Hi Tom,
now it can start but soon anaconda breaks reporting the following Exception:
"An error occurrder unmounting the CD. Please make sure you're not accessing /mnt/source from the shell on tty2 and then clik OK to retry"
Shell on tty2 is on /
from /tmp/anaconda.log file I see this:
...
...
* moving (1) to step readcomps
* exception in unmountCD: (16,'Device or resouce busy')
I did the following steps:
- modified isolinux.cfg file to add the kernel parameter I need
- modified some .msg files to customize this new CD
- modified the kickstart files to add the kernel parameter to boot loader (as I did yesterday)
- recreate the ISO
Any ideas? I really don't known how to investigate on it...
thanks
/Luca
________________________________
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Mariani, Luca
Sent: 06 March 2007 11:09
To: Discussion list about Kickstart
Subject: RE: kernel parameters
Hi Tom,
thanks a lot for your quickly response...
I'll try this ASAP
Bye
Luca
________________________________
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Callahan, Tom
Sent: 05 March 2007 19:34
To: Discussion list about Kickstart
Subject: RE: kernel parameters
You have to modify the syslinux files on the boot CD and rebuild the CD. Change the append= lines and add the option you need.
Thanks,
Tom Callahan
TESSCO Technologies
Desk: (410)-229-1361
Cell: (410)-588-7605
Email: callahant@xxxxxxxxxx
size=2 width="100%" align=center tabindex=-1>
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Mariani, Luca
Sent: Monday, March 05, 2007 1:04 PM
To: kickstart-list@xxxxxxxxxx
Subject: kernel parameters
Hi all,
I'm upgrading a bootable CD which uses kickstart to automatically install REHL4 Upgrade3 and a subset of programs.
The upgrade is needed by a new hardware that requests a special kernel parameter to boot the system (in particular the kernel parameter is 'pci=nommconf' and it should be needed to use the Smart Array Controller)
I've been able to add this parameter in kickstart config file and now the boot is working fine (I'm using GRUB as bootloader), but I must type the kernel parameter by hand at installation prompt...
Is there a way to configure kickstart (or something else) in order to autamatically pass this kernel parameter to installation process too?
Thanks
Regards
/Luca
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
<<winmail.dat>>
