RE: kickstart

["Robinson, Andrew W." <Andrew.W.Robinson@xxxxxxx>]

Title: Message

The ksdevice=eth# directive has worked for me doing a pxe network install. I assume it would work with an isolinux install.

 

Andrew Robinson

 

-----Original Message-----
From: Chris Mckenzie [mailto:Chris.McKenzie@xxxxxxxxxxx]
Sent: Friday, November 19, 2004 10:50 AM
To: 'Discussion list about Kickstart'
Subject: RE: kickstart

 

That's a good question.

 

add ksdevice=eth# to the append line.

 

label ks

  kernel vmlinuz

  append ks=nfs:<nfs server IP>:<nfs path to...>/ks.cfg ksdevice=eth0 initrd=initrd.img

 

Don't know if it works, I just gleaned it from the RH docs. My final hardware will ship with dua nics so I will be testing this out eventually, but don't know how well it works right now.

 

- Crhis

-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Gordon McDowall
Sent: November 19, 2004 11:43 AM
To: 'Discussion list about Kickstart'
Subject: RE: kickstart

Hi Chris

 

I was wondering, looking at the isolinux.cfg file you have is it possible to specify what ethernet card to use if you have dual NICs in the machine?

 

Thanks

 

Gordon

 

---

From: Chris Mckenzie [mailto:Chris.McKenzie@xxxxxxxxxxx]
Sent: 19 November 2004 15:36
To: 'Discussion list about Kickstart'
Subject: RE: kickstart

Actually I just work some instruction based on a RH CD1 customization. Nothing fancy, just the basics. You can replace the append ks= with ks=cdrom:/<path on CD to kickstart>.

 

Hope this helps.

 

Basic steps to create a basic custom RedHat "Install CD" from an existing RedHat install:

 

1.       Create a cdimage directory:

 

mkdir /var/bootcd/cdimage

 

2.       Mount and copy the RedHat CD1 contents into the CD image directory.

3.       Edit the /isolinux/isolinux.cfg file, add the bold changes below.

 

default ks

prompt 1

timeout 10

display boot.msg

F1 boot.msg

F2 options.msg

F3 general.msg

F4 param.msg

F5 rescue.msg

F7 snake.msg

label linux

  kernel vmlinuz

  append initrd=initrd.img

label text

  kernel vmlinuz

  append initrd=initrd.img text

label expert

  kernel vmlinuz

  append expert initrd=initrd.img

label ks

  kernel vmlinuz

  append ks=nfs:<nfs server IP>:<nfs path to...>/ks.cfg initrd=initrd.img

label lowres

  kernel vmlinuz

  append initrd=initrd.img lowres

 

The label ks parameter supports http, nfs, floppy, cdrom and pretty much all /dev devices. See RedHat kickstart docs for specifics.

 

Note: The kickstart location must be good. By hardcoding it's location, this "Install CD" will always look in the defined location.

4.       Create an ISO using mkisofs, or other comparable iso creation tool. (note the below is all 1 line)

 

mkisofs -o ../installcd.iso -V 'AppCD' -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -V -T .

5.       The "Install CD" iso is now ready to be burnt, mounted or virtually used by a VM. When booted in the appliance, the loader will initiate the ks.cfg install within 10 milliseconds.

 

-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Brian Zuromski
Sent: November 19, 2004 10:33 AM
To: kickstart-list@xxxxxxxxxx
Subject: kickstart

Hello,

           Can someone layout the steps for creating a kickstart iso from scratch for RHES3.

 

Thanks,