Red Hat Bugzilla – Bug 846724
RFE: Pick up and use kickstart files from persistent storage on a usb key
Last modified: 2013-06-20 21:42:55 EDT
Description of problem:
The general use case is for administrator that need to go onside to clients to install/setup Fedora/RHEL.
The idea in steps
1. Administrators creates an install usb key with persistent storage
2. Administrator creates and copy's the kick start file(s) to the persistent storage space on the usb key.
3. Administrator goes on site and boots into the installer.
4. Anaconda reads the content of the relevant persistent storage space and offers the administrator to choose kickstart file to install from withing the UI.
Although not tested I assume this works already with "ks" from the kernel command line with either ks=file:<path> or ks=hd:<dev>:<path>
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 876032 has been marked as a duplicate of this bug. ***
will this work with f18 Anaconda Beta DVD? Has anyone written a wiki page on how to do this?
Any idea when this will happen? At this point it would make sense to just dump floppy support and substitute usb keys.
ks deployment from arbitrary mountable block devices is already supposed to work: see https://fedoraproject.org/wiki/Anaconda_Boot_Options#ks , "ks=hd:<dev>:<path> (dev = 'hda1', for example)".
(In reply to Adam Williamson from comment #4)
> ks deployment from arbitrary mountable block devices is already supposed to
> work: see https://fedoraproject.org/wiki/Anaconda_Boot_Options#ks ,
> "ks=hd:<dev>:<path> (dev = 'hda1', for example)".
It seems to work with recent images: I have a thumb drive which is mounted as sdb4 which had a partial kickstart file ks.cfg, so I booted the 19 Final TC2 i386 DVD in a VirtualBox guest, using "inst.ks=hd:sdb4:/ks.cfg". The resulting behavior is exactly the same as that noted in bug 972265 and bug 972266, so it appears to work the same as if the kickstart file was downloaded. (It did NOT work when I booted the F18 DVD, so the support must be more recent.)
Note that most thumb drives are mounted as sdb1, mine was sdb4 due to being reformatted for USB-ZIP compatibility.
You should also be able to use the UUID or LABEL so that you don't need to know what device it showed up as.