Hello Matt, Matthew Richards wrote: > The USB drive is identified differently depending upon the hardware > configuration of the system with which it is booted. Generally > speaking if the system has only IDE disks then the USB drive becomes > /dev/sda. If the system has a SCSI or SATA disk then the USB drive > becomes /dev/sdb, etc. I'm having the same problem here... The solution I'm thinking of is a little bit different. It started as a solution for installing over the network where it is required to have static ip-addresses configured, but booting (installation) over PXE is required. In this case the static IP-address is given on the commandline in a pxelinux.cfg. (Backgound for the wondering readers: booting and 100% functionality without delays if there are network problems.) The solution needs one extra step/stage. Normally anaconda does a two stage installation. Stage1 is the loader, stage2 the installer in Python which contains a nice GUI. The extra step used is in our case stage0. Stage0 is an initrd which does a minimal setup of the hardware and some small ks.cfg editing with sed. After preparing ks.cfg, the original initrd from the install-set is downloaded, extracted and 'started'. In my opinion, in a stage0 like the above it would be possible to detect SATA/IDE/USB drives and replace/change ks.cfg with correct values. Any thoughts? Niels
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
