This may be more appropriate for an upstream list. That said...
I'm doing kickstart setups of CentOS 5. My kickstart config includes a network configuration item. Depending on options passed at boot-time, the network config item may or may not include a --hostname option, but always specifies eth0.
When I do a kickstart install, I notice that even though I am using 'interactive' (basically so the user can override any of the kickstart settings should they need to), the networking screen never pops up and the values from my network get used. If the usr didn't provide a hostname entry on bootup, then localhost.localdomain gets used as the system hostname.
I'd like for the user to be able to select the hostname via the installation wizard as they would normally in a non-kickstart install.
Perhaps for CentOS 5 kickstarts I should just not include the network option at all in order to make the network configuration screen accessible inside the installer?
Ray
Ray Van Dolson wrote:
Perhaps for CentOS 5 kickstarts I should just not include the network option at all in order to make the network configuration screen accessible inside the installer?
you can try run anaconda in debug mode to work out exactly what is going on at what stage..
On Sat, Dec 08, 2007 at 03:28:36PM +0000, Karanbir Singh wrote:
Ray Van Dolson wrote:
Perhaps for CentOS 5 kickstarts I should just not include the network option at all in order to make the network configuration screen accessible inside the installer?
you can try run anaconda in debug mode to work out exactly what is going on at what stage..
Booted with loglevel=debug and syslog set and also am using logging --level=debug in my kickstart file.
I don't really see anything too informative in the debug output though:
Dec 12 09:04:32 10.49.51.39 DEBUG no preexisting size for volume group VolGroup00 Dec 12 09:04:32 10.49.51.39 DEBUG got pv.size of 20371.4868164, clamped to 20352 Dec 12 09:04:32 10.49.51.39 DEBUG total space: 20352 Dec 12 09:04:41 10.49.51.39 INFO moving (1) to step partitiondone Dec 12 09:04:41 10.49.51.39 INFO moving (1) to step partitiondone Dec 12 09:04:41 10.49.51.39 INFO moving (1) to step bootloadersetup Dec 12 09:04:41 10.49.51.39 INFO moving (1) to step bootloadersetup Dec 12 09:04:41 10.49.51.39 INFO moving (1) to step bootloader Dec 12 09:04:41 10.49.51.39 INFO moving (1) to step bootloader Dec 12 09:04:56 10.49.51.39 INFO moving (1) to step networkdevicecheck Dec 12 09:04:56 10.49.51.39 INFO moving (1) to step networkdevicecheck Dec 12 09:04:56 10.49.51.39 INFO moving (1) to step timezone Dec 12 09:04:56 10.49.51.39 INFO moving (1) to step timezone Dec 12 09:05:21 10.49.51.39 INFO moving (1) to step accounts Dec 12 09:05:21 10.49.51.39 INFO moving (1) to step accounts Dec 12 09:05:27 10.49.51.39 INFO moving (1) to step reposetup Dec 12 09:05:27 10.49.51.39 INFO moving (1) to step reposetup
Perhaps it should normally stop at networkdevicecheck? The documentation seems to imply that if the kickstart installation requires networking but no network configuration has been provided in the kickstart file, then it is assumed that both the installer and the installed system should acquire its IP address via DHCP.
So it seems my only option will be to either specify the network information inside the kickstart file or to not use the network to install the system which would then prompt me for network information.
http://www.centos.org/docs/5/html/5.1/Installation_Guide/s1-kickstart2-optio...
This is different than the behavior in RHEL4/CentOS 4. I guess I will take this discussion to the kickstart list for now.
Ray
-
Karanbir Singh -
Ray Van Dolson