Here is a little round-up about my issues: Problem Nr. 1: aaa_base-9-29.46.i586.rpm produces a 2595 bytes log /etc/sysconfig/kernel file with nothing but null- bytes in it. Solution for Nr.1: In our PXE-Environment we are using for the "kernel" and "initrd" files that ones from SLES9 without any SP. During an AutoYast installation "SUSE LINUX Enterprise Server 9 installation program v1.6.36" is displayed. I made some tests with the versions from the SLES9 SP3 CDs. There it says "v1.6.53", and works like a charm: Even when no hostname is provided in my eth_default_dhcp.xml the file /etc/sysconfig/kernel gets created with almost perfect content (BusLogic apperas twice in INITRD_MODULES=). Hopefully merely copying the correct file in our production-systems is enough in order to get a neat environment. Problem Nr.2: After installation of postfix-2.1.1-1.17.i586.rpm with AutoYast the file /etc/postfix/main.cf contains a line with myhostname = .testdomain.com instead of myhostname = testhost.testdomain.com. With this mistake postfix is unstartable. Workaround for Nr.2: Either call SuSEconfig.postfix when hostname is available. or call "postconf myhostname=`hostname -f`" when hostname is available. (I tend to the second one, perhaps in a kind of post-postinstallation script) Using dhcpcd (like Stefan suggested) I made the following experiences: During first AutoYast stage it is possible to call the following in the alt+F2 shell: / # hostname linux / # /lbin/dhcpcd -k / # /lbin/dhcpcd -D / # hostname testhost But with the solution for Nr.1 this seems to be not neccesary anymore. During the second AutoYast stage you can use similar commands. But then errors are thrown: linux:/ # hostname linux linux:/ # dhcpdcd -k **** dhcpcd: not running linux:/ # dhcpcd -D linux:/ # ERROR: Interface eth0 is not configured for dhcp. So don't use '-o dhcp'. linux:/ # hostname linux Later, when the second stage has finished and the installed system is completing the boot process, recieving the IP address fails at all: eth0 (DHCP) . . . . . no IP address yet... backgrounding eth0 interface could not be set up When I don't use any commands in the 2nd stage, booting works correctly! Well, as a conclusion I think I found acceptable work-arounds, but this makes me not 100% happy. Nevertheless I learned some new things about (SUSE) Linux while my investigations ;-). Thanks for your participation. Bye Christoph ---- Hol Dir jetzt Deine coole @uni.de E-Mail Adresse. Der einzigartige Webservice und auch noch kostenlos. -- www.uni.de -- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org