try ks=hd:sda1/ks.cfg -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx]On Behalf Of Terje Kvernes Sent: Wed, August 25, 2004 12:16 PM To: kickstart-list@xxxxxxxxxx Subject: kickstart from a USB pen / harddrive. howdy all. since cdroms are annoying to add kickstart files to, and floppies being, well floppies, we've decided to look at using USB pens to store kickstart files here at the department. before anyone says "PXE!", let's just say that we've been there, done that and for several reasons want something else. now, I've managed to get RHEL 3.0 WS to boot from the pen, and everything works rather well. the problem comes with finding the darn kickstart file. now, we get the pen as /dev/sda1 according to the logs, which is fine, but anaconda doesn't seem to want to find the kickstart file on /dev/sda1. I've tried ks=/dev/sda1/ks.cfg and ks=/dev/sda1:/ks.cfg as best guesses, after the cdrom:/ks.cfg-model, but this doesn't seem to work. I've also tried ks=/ks/ks.cfg, but the all lead to the same error: "Error opening kickstart file (null): Bad address" now, I'm more than willing to modify the appropriate bit in anaconda or whatever to get /dev/sda1 mounted somewhere so that the kickstart files can be found, but I can't seem to find the appropriate image to edit. help? ;-) -- Terje _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list *********************************************************************************** Information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the postmaster@xxxxxxx and destroy the original message. ***********************************************************************************
