On Wed, 10 Dec 2003, Anas Nashif wrote:
Is there another way of stopping the redundant DHCP request? At best this leads to a delay until the request times out. At worse the machine could end up with an invalid configuration.
Hmm, this should not happen. Can you check the file /var/lib/YaST2/install.inf and see if the network values you have supplied are present there!
menu.lst on GRUB floppy includes: title autoinstall ifconfig --address=131.111.11.209 --server=131.111.10.90 root (nd) kernel (nd)/suse/linux \ hostip=131.111.11.209 netmask=255.255.0.0 \ gateway=131.111.11.62 nameserver=131.111.8.42 \ install=nfs://131.111.8.10/linux/suse/i386/9.0 \ autoyast=tftp://131.111.10.90/suse/autoyast.xml \ textmode=1 initrd (nd)/suse/initrd /var/lib/YaST2/install.inf on installed system includes: NetConfig: static Netdevice: eth0 NetUniqueID: 7EWs.weGuQ9ywYPF IP: 131.111.11.209 Hostname: 131.111.11.209 Broadcast: 131.111.255.255 Network: 131.111.0.0 Netmask: 255.255.0.0 Gateway: 131.111.11.62 Nameserver: 131.111.8.42 Server: 131.111.8.10 /var/log/messages right after first reboot: Dec 8 12:38:16 linux dhcpcd[2782]: broadcasting DHCP_DISCOVER Dec 8 12:38:26 linux dhcpcd[2782]: timed out waiting for a valid DHCP server response /etc/sysconfig/network/ifcfg-eth0 is created a few seconds later by the autoinst postinstall script: -rw-r--r-- 1 root root 160 2003-12-08 12:38:41.000000000 +0000 /etc/sysconfig/network/ifcfg-eth0 and contains: BOOTPROTO='static' BROADCAST='131.111.255.255' IPADDR='131.111.11.209' NETMASK='255.255.0.0' NETWORK='131.111.0.0' STARTMODE='onboot' UNIQUE='7EWs.weGuQ9ywYPF' ifcfg-eth0 doesn't exist before that point in time. -- David Carter Email: David.Carter@ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH.