Red Hat Bugzilla – Bug 461549
Install from USB disk: Awkward to provide a ks.cfg
Last modified: 2008-09-15 11:56:22 EDT
Description of problem:
When booting anaconda from USB disk
- a ks.cfg file at the root of the USB disk is not picked up
- a ks.cfg file at the root of the ISO disk where stage2 is (see #461548) is also ignored
- the usb disk does not have a stable device - a menu entry in syslinux.cfg setting ks=hd:sdb1:ks.cfg will work _most_ of the time, but is by no means something you can count on...
Version-Release number of selected component (if applicable):
got the logs?
anaconda never implicitly looks for a kickstart file, so you will always have to tell it that you want to use kickstart and where the file is located. In rawhide (and hence F10) you are able to say ks=hd:LABEL=whatever:ks.cfg or ks=hd:UUID=whatever:ks.cfg, provided you have given the filesystem a label or UUID.
Does that take care of this problem for you?
Chris - you are right, it is correct that the ks file is not picked up automatically.
The problem remains with USB-based installs that there is no way to tell anaconda "use the usb disk you've booted from". For example, "cdrom:" is clearly an alias for "whatever it is - SATA/PATA/USB/SCSI that is the first CD-ROM-like thing in the system".
So to reword my request: can we have a have similar alias, that allows us to say ks=usbdisk:/ks.cfg and have 'usbdisk' mapped to the first usb drive around?
In a separate discussion, Jerry was suggesting a udev rule could help. Perhaps that's how cdrom is implemented?
The problem is that different people have a different interpretation of what a "usbdisk" entails. Is a USB flash drive a disk or just a hard disk? What about a USB floppy drive? cdrom: harkens back to the dya when one CD drive was all you (almost) ever had on the system.
More explicit use of mounting by label/uuid for finding things like kickstart configs is definitely the way of the future.