From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 Description of problem: A number of kickstart directives are `forgotten' when the kickstart file contains the `interactive' directive, so you have to put them in again. The ones I've noticed are: network --bootproto dhcp --hostname free --hostname free is ignored, and the boot loader screen comes up with `get name from DHCP' bootloader --location=partition --md5pass=$1$zLedeO4B$md7uZnrqXfn7dl9zNbaeM0 The advanced bootloader configuration screen comes up with MBR selected (perhaps a dupe of bug #70380, even though that's for non-interactive kickstart installs). The bootloader password comes up disabled. rootpw --iscrypted <omitted> The root password comes up empty. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Write a non-interactive kickstart file with the directives above 2.Install, and verify that they've been taken into account (except bootloader --location=partition) 3.Add `interactive' to the kickstart file. 4.Install again. Actual Results: A password for root is requested during the interactive install. The boot loader password is shown as disabled in the bootloader screen, even though the password in the kickstart file made it to grub.conf and anaconda-ks.cfg. The MBR is overwritten and the boot sector of the /boot partition is not set up. Hostname comes up as localhost.localdomain. Expected Results: Same as the non-interactive install. Additional info:
Network bootproto one is because we're not allowing the specification of a static hostname with DHCP right now. Bootloader location is a dupe. Passwords don't get filled in because they're crypted and I can't decrypt them, so there's nothing sensible for me to put in the entry boxes (there's another deferred bug about this from the 7.2-ish time frame)
> Network bootproto one is because we're not allowing the specification of a static hostname with DHCP right now. Err... Why does it work if done interactively, then? > Passwords don't get filled in because they're crypted and I can't decrypt them, so there's nothing sensible for me to put in the entry boxes The actual password is not displayed anyway, so why not just put in say `encrypted: <encrypted password>' in the password field? The user would still be able to modify it, and the encryption algorithm could recognize this special pattern. It might be wise to add characters that can't be entered from the keyboard to the special pattern, to make sure it's not entered by mistake, as unlikely as it would be.
Not going to do anything with these at this point. If any of them still occur and you feel strongly about them, please file again against a newer release.