I've been doing some preparation for (PXE+HTTP) network installation of a group of new servers (soon to be ordered, don't have them yet) using VMware (V5 beta, with host system running SuSE 9.2 Professional). I was originally installing SLES9 but switched to an evaluation download of OES for Linux (i.e. SLES9 + extras) when that became available. This is using PXE boot and HTTP access to the installation source. [I suspect those details aren't relevant to the problem, but mentioned "just in case".] The fairly basic (so far!) autoinstallation configuration that worked fine with SLES9 also mostly worked with OES, but one significant detail (that I've noticed so far, there may be others) fails consistently without any explanation or comment that I've seen. [Side-issue: is there any documentation of changes and additions to the available XML configuration settings, for OES as compared to SLES9? The DTDs show what differs at the syntactic level, but that's only half the story.] The problem is with nameserver configuration - with SLES9, that "just worked" but with OES it simply fails to create /etc/resolv.conf with the obvious effects on network access. Other aspects of the network configuration (e.g. setting up static IP addresses and default router, and enabling the network) *did* work in OES, the effect is as though something simply forgot to install the nameserver configuration. The namserver-related part of the configuration that's currently getting ignored is <dns> false false <domain>mynet</domain> <hostname>oestest</hostname> <nameservers config:type="list"> <nameserver>131.111.8.32</nameserver> <nameserver>131.111.12.20</nameserver> </nameservers> <searchlist config:type="list"> <search>mynet</search> <search>cam.ac.uk</search> </searchlist> </dns> Has anyone else seen this problem? Is there any better solutio than creating the missing file by using a postinstall script? I tried recreating the network configuration definitions for autoinstallation, using yast after manually installing OES, but I don't think it was any different from what I'd been trying and it made no difference anyway, resolv.conf still not created - so the obvious possibility, that the required XML definitions had changed incompatibly for OES - seems to be ruled out as an explanation. John Line -- John Line - web & news development, University of Cambridge Computing Service