Using kickstart with "mouse --kickstart none" in ks.cfg my produces a python syntax error. The following patch fixes the problem. kickstart.py 228,229c228 < (args, extra) = isys.getopt(args, '', [ 'device=', 'emulthree', < 'kickstart']) --- > (args, extra) = isys.getopt(args, '', [ 'device=', 'emulthree' ]) -- Alf. ----------------------------------------------------------------------- Alf Wachsmann | e-mail: alfw.edu SLAC Computing Service | Phone: +1-650-926-4802 2575 Sand Hill Road, M/S 97 | FAX: +1-650-926-3329 Menlo Park, CA 94025, USA | Office: Bldg. 50/323 ----------------------------------------------------------------------- http://www.slac.stanford.edu/~alfw (PGP) -----------------------------------------------------------------------
Brock - please verify this is fixed in pinstripe, the above patch already appears to have been applied.
I tried to reproduce this bug and Anaconda crashes. I get a Python traceback that says: Type Error: bad argument --kickstart: unknown option According to the kickstart documentation for 6.2 (http://www.redhat.com/support/manuals/RHL-6.2-Manual/ref-guide/s1-kickstart2-commands.html), --kickstart is not a valid entry for the mouse in the kickstart file. However, I've seen other reports in Bugzilla from other people trying to use the --kickstart option. Where does this come from? Closing as not a bug.
Hey RedHat folks. while trying to find help on my 'part' bug, found one example of the bad --kickstart arg to mouse reference: http://www.linuxworld.com/linuxworld/lw-1999-12/lw-12-kickstart.html both the HOWTO, and the RH Ref Guide make no mention BTW.