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>