Hi everybody, I use autoyast2-2.8.14-20 and try to install Suse 9.0 to a couple of Workstations I use the grubfloppy from Anas's Website to boot the system to be installed. This is my menus.lst for the grubfloopy ---snip title autoinstall-bootp bootp tftpserver 172.18.127.43 root (nd) kernel (nd)/opt/ignite/linux install=nfs://172.18.127.126/.home/install/suse9.0/DVD1 autoyast=nfs://172.18.127.126/var/lib/autoinstall/repository initrd (nd)/opt/ignite/initrd --snap on 172.18.127.126 the installation server ll /var/lib/autoinstall/repository drwxr-xr-x 5 root root 272 Mar 23 09:33 . drwxr-xr-x 5 root root 128 Nov 14 2005 .. -rw-r--r-- 1 root root 390 Mar 22 18:07 AC127F57 -rw-r--r-- 1 root root 390 Mar 22 17:53 AC127F8C drwxr-xr-x 4 root root 96 Mar 22 17:47 classes lrwxrwxrwx 1 root root 8 Mar 22 18:07 hatti -> AC127F57 drwxr-xr-x 2 root root 48 Sep 24 20:44 rules drwxr-xr-x 2 root root 48 Sep 24 20:44 templates AC127F57 is HEX for 172.18.127.87 which is the TCP/IP of the client booted with the grubfloppy. ->My test system boots stage2 successfull ->Loads the kernel and initrd via tftp from the tftpserver 172.18.127.43. ->starts thekernel ->starts linuxrc 1.5 ->starts yast2 for automated install mounts the installation source But yast2 does not find the controlfile for autoyast The control file is available as: see above. The system to be installed ends up in a yast2 mask where the server and mountpoint of the controllfile is displayed as told to yast2 by the autoyast= statement to the kernel. (this shows the 'control file repository' is known!) If I extend the repository path by AC127F57 and hit enter the installation rolls on as expected. This shows that NFS works for 172.18.127.126/var/lib/autoinstall/repository. It seems as if the autochoose feature of the control file fails for a reson I cannot see! The /var/log/message file on the Installation server (172.18.127.126) shows, that no trial to mount /var/lib/autoinstall/repository is done,however, /.home/install/suse9.0/DVD1 is mounted succesfully. Only after I extend the repository path by the control file's name the nfs mount is done as seen in messages on the installation server. Does anybody can help ? -- Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD EDA IS P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller@epcos.com Web: http://www.epcos.com