Hi all, I have an odd problem which is causing me some grief, and I was wondering if anyone else has seen it. The problem (I think) leads to others in the process. Not as unattended as I would like! I am remotely installing SuSE 9.2 a Compaq DL380-G4. When I come to start the install, I am using (IPs changed to protect the guilty): initrd netdevice=eth0 HostIP=10.10.5.9 netmask=255.255.255.0 gateway=10.10.5.1 install=http://10.10.5.50/9.2 autoyast=http://10.10.5.50/conf/system.xml The problem starts during the 'initializing hardware' section. It stops at this point complaining that it can't find the SUSE Linux installation source. Now some might think that I'd made a mistake - but this is certainly not the case. If I now go through the steps: Select the language Choose a keyboard map Start Installation Or System Start Installation Or Update Network HTTP Your network is already configured. Keep this configuration (YES) Enter the IP address of the HTTP server (10.10.5.50) Use a HTTP proxy? (NO) I then get another error saying: connect: No route to host If I try again too quickly, I get the same error. If I wait 30 seconds or and it comes back and prompts for the installation directory (9.2) I'm not sure what causes the initial fault, but the subsequent one suggests a timeout period before the NIC comes on-line, and/or YaST is not waiting for the NIC to initialise before continuing. Now I can crack on with the install (though now its not exactly unattended anymore)! The third problem is that now I have to acknowledge a number of prompts (I think as a result of dropping out to manual mode earlier? - I think I saw that mentioned on the mailing list somewhere). The fourth problem comes after the first CD is finished with. The system reboots, and then goes on to CD2 - and here the system prompts me to load the second CD (a bit annoying as its all under HTTP control). Again, wait for 30 seconds and the install continues OK. Finally, once the system comes up, the network settings are incorrect (I override the one supplied on the command line with a new one in the xml). A reboot cures this, but the option to autoreboot (according to the manual, and bourne out by the fact I couldn't get it to work) appears to have been obsoleted. Has anyone seen this elsewhere, and any ideas on how to prevent the problem(s)? Thanks! Colin Topliss Senior UNIX Sys Admin Noli habere bovis, vir! ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________