I would like one of my kickstart scripts to prompt for disk and networking only. Commenting out the disk and network settings makes the installer prompt for disk settings but not for network settings, they default to DHCP. Any idea's how to fix this? Thanks Dean
Plant, Dean wrote:> I would like one of my kickstart scripts to prompt for disk and > networking only. Commenting out the disk and network settings makes the > installer prompt for disk settings but not for network settings, they > default to DHCP. Any idea's how to fix this?I think you need to have the network settings defined - something like: network --bootproto static If you don't give it an IP address (with the --ip option), then it will prompt for it. This is what I do for NFS installs - as my netmask, gateway and nameserver addresses are static, I also give these on the network line. James Pearson
James Pearson wrote:> Plant, Dean wrote: >> I would like one of my kickstart scripts to prompt for disk and >> networking only. Commenting out the disk and network settings makes >> the installer prompt for disk settings but not for network settings, >> they default to DHCP. Any idea's how to fix this? > > I think you need to have the network settings defined - something > like: > > network --bootproto static > > If you don't give it an IP address (with the --ip option), then it > will prompt for it. This is what I do for NFS installs - as my > netmask, gateway and nameserver addresses are static, I also give > these on the network line. >Does not work, still defaults to DHCP with no prompt. Also if it makes any difference im using v5.1. I have tried with the 2 network lines shown below in the kickstart file, with and without interactive variable. Still no network configuration screen. :-( Below is my test kickstart. #platform=x86, AMD64, or Intel EM64T # System authorization information authconfig --enableshadow --enablemd5 # System bootloader configuration bootloader --location=mbr --md5pass=apssword # Reboot after installation reboot # Interactive interactive # Use graphical install graphical # Firewall configuration firewall --disabled # Run the Setup Agent on first boot firstboot --disable # System keyboard keyboard uk # Network settings #network --bootproto=static --device=eth0 --gateway=192.168.10.1 --nameserver=192.168.10.1 --netmask=255.255.255.0 --onboot=on network --bootproto=static # System language lang en_GB # Installation logging level # Use this to debug logging --host=alogmachine.domain.co.uk --level=info # Use network installation url --url=http://amachine.domain.co.uk/5/en/os/i386/ # Root password rootpw --iscrypted apassword # SELinux configuration selinux --disabled # System timezone timezone --isUtc Europe/London # Install OS instead of upgrade install # XWindows configuration information xconfig --depth=16 --resolution=1280x1024 --defaultdesktop=GNOME --startxonboot
On Tue, Apr 22, 2008 at 12:47:39PM +0100, Plant, Dean wrote:> I would like one of my kickstart scripts to prompt for disk and > networking only. Commenting out the disk and network settings makes the > installer prompt for disk settings but not for network settings, they > default to DHCP. Any idea's how to fix this?I'm assuming you are using CentOS 5 here. I'm not sure why upstream disabled this feature -- it was very useful to be able to use kickstart with a DHCP IP address initially, but still be prompted for network information during the installer portion later (as it did in RHEL4). See: https://bugzilla.redhat.com/show_bug.cgi?id=401531 In addition, I have an RFE in with Upstream to re-add this feature and I believe it's slated for inclusion in 5.2 with the --bootproto=query option. The attachment there however: https://bugzilla.redhat.com/attachment.cgi?id=291881 patches Anaconda to not skip the network step during installation. I've been using this successfully here to "do what I need" while waiting for the official fix. You can include this in an updates.img file and have it loaded automatically on installs. Ray
James Pearson wrote:> Plant, Dean wrote: >> James Pearson wrote: >> >>> Plant, Dean wrote: >>> >>>> I would like one of my kickstart scripts to prompt for disk and >>>> networking only. Commenting out the disk and network settings makes >>>> the installer prompt for disk settings but not for network >>>> settings, they default to DHCP. Any idea's how to fix this? >>> >>> I think you need to have the network settings defined - something >>> like: >>> >>> network --bootproto static >>> >>> If you don't give it an IP address (with the --ip option), then it >>> will prompt for it. This is what I do for NFS installs - as my >>> netmask, gateway and nameserver addresses are static, I also give >>> these on the network line. >>> >> >> >> Does not work, still defaults to DHCP with no prompt. Also if it >> makes any difference im using v5.1. >> >> I have tried with the 2 network lines shown below in the kickstart >> file, with and without interactive variable. Still no network >> configuration screen. :-( > > Hmmm, works OK for me with CentOS 4.X - however, I used a hacked > version of anaconda - one of my hacks is to set 'netDev.isDynamic' to > 0 in loader2/loader.c i.e. make static IP the default ... however, I > thought this was for non-kickstart installs only ... but may be it > isn't. >Looks like it's a CentOS 5 feature/bug as I have just tested every incarnation of the network line and they all get ignored unless I put in the complete line as per Marc-Andre's post. This DID work in CentOS 4 as long as the interactive line was specified. Dean
Ray Van Dolson wrote:> On Tue, Apr 22, 2008 at 12:47:39PM +0100, Plant, Dean wrote: >> I would like one of my kickstart scripts to prompt for disk and >> networking only. Commenting out the disk and network settings makes >> the installer prompt for disk settings but not for network settings, >> they default to DHCP. Any idea's how to fix this? > > I'm assuming you are using CentOS 5 here. I'm not sure why upstream > disabled this feature -- it was very useful to be able to use > kickstart with a DHCP IP address initially, but still be prompted for > network information during the installer portion later (as it did in > RHEL4). > > See: > > https://bugzilla.redhat.com/show_bug.cgi?id=401531 > > In addition, I have an RFE in with Upstream to re-add this feature and > I believe it's slated for inclusion in 5.2 with the --bootproto=query > option. > > The attachment there however: > > https://bugzilla.redhat.com/attachment.cgi?id=291881 > > patches Anaconda to not skip the network step during installation. > I've been using this successfully here to "do what I need" while > waiting for the official fix. > > You can include this in an updates.img file and have it loaded > automatically on installs. > > RayAhhhhh. Im not going daft then. Ill give the patches a go. Thanks everyone for your replies. Dean.