You can put dd= anywhere on the line after boot: Order is not important. Putting dd= on the boot line will give you the exact same result as putting --driverdisk in the kickstart file. About the only time I can think that you would NEED to put it on the boot line would be if you were loading your ks.cfg via the network and needed a network driver that wasn't supported. Also, be aware of the 255 character limitation on the boot: line. This is the reason we have added it to the ks.cfg file and not to the boot: line -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Ryan C. Spaulding Sent: Friday, April 14, 2006 9:20 AM To: Discussion list about Kickstart Subject: Re: Adding drivers to kickstart initrd.img I guess since I have never needed it before it's new to me :) Wait can I do dd= before I put in ks ks= ? On Apr 14, 2006, at 9:12 AM, Shabazian, Chip wrote: > You can use --driverdisk in a kickstart file, or dd= at the boot: > prompt. > > This isn't a new option though, it's been there quite a while. > > -----Original Message----- > From: kickstart-list-bounces@xxxxxxxxxx > [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Ryan C. > Spaulding > Sent: Friday, April 14, 2006 8:12 AM > To: Discussion list about Kickstart > Subject: Re: Adding drivers to kickstart initrd.img > > > Hi All, > > Thank you for the instructions. I was looking over the kickstart > documentation again and it looks like it has been updated with 4.0 > release 3. I am going to attempt using what looks like a new option > called --driverdisk (with Dan's driver disk). Looks like I can specify > a driver disk via ftp, http and nfs. > > I will let you all know how it goes. > > Thank you, > > Ryan > > > > On Apr 14, 2006, at 1:02 AM, Dan Carpenter wrote: > >> On 4/13/06, Ryan C. Spaulding <rspaulding@xxxxxxxxxxxxxxxxx> wrote: >>> I think that a rebuild of anaconda could fix this problem but I >>> could > >>> be totally going in the wrong direction. >>> >> >> A little bit in the wrong direction, yes. >> >> I'll forward you the driver disk in a seperate email. >> `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` Boot from the CD and use >> "linux dd" to specify that there is a driver disk. You'll need a >> floppy or USB key or something. >> >> If you want to automate the package. >> 1) Download the anaconda source rpm >> 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv >> 3) make >> 4) apply this patch >> https://www.redhat.com/archives/anaconda-devel-list/2005-November/ >> msg00018.html >> 5) cd loader2/ ; make loader >> >> 6-9) Unpack the initrd. Replace the old loader with the one you just >> created. Put the driver disk in the initrd as /dd.img. Pack it back >> up. >> >> Then it's automatic. Or you could just put the driver disk on the >> network I suppose but I don't recall the format for that... >> >> regards, >> dan carpenter >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
