I'm just in the beginning stages of understanding SuSE's autoinstall process, which I'm implementing for an OpenMosix cluster. The scenario is that I have a server w/ the appropriate media directories, a standard SuSE boot CD, and a floppy w/ a custom autoinst.xml and info file at the root. And using SuSE 9.0 Yast 2. Problem 1: Info file not working. Because this is on a cluster, and for various reasons we don't want to run DHCP on the control node, I would like to use an info file to statically assign IP info and have the YaST look for the nfs install directory. Here's the contents of my info file: netdevice: eth0 ip: 192.168.1.200 netmask: 255.255.255.0 gateway: 192.168.1.200 install: nfs://192.168.1.1/usr/local/SuSE/current autoyast: floppy During the boot process the system searches for the info file, loads usb drivers, etc., searches for autoinstall file, then says "Sending DHCP request to eth0". I've watched, and the system reads the floppy drive both times. If I use this info file and autoinst.xml file on a network that has a DHCP server available, the network card grabs an IP, finds the nfs share, and proceeds to install according to my autoinst settings. But it fails if I use it on the cluster segment where no DHCP is available. I can do a manual installation, load the card drivers and manually enter all the IP and NFS info, and the autoinstallation proceed wonderfully. So my question is - what's wrong w/ my info file that the systems keep trying to use DHCP instead of the static info? Clearly they're getting at least some of the info from the file since the install finds the NFS shared okay. Problem 2: Not so much a problem as looking for additional tips/docu resources for how to make a custom kernel as part of the autoinstall process. I need to have the openmosix kernel installed, and am looking for the best way to accomplish this automatically. I tried to have it install as an addon package like any other RPM (like section 4.5.3 of the documentation says for general RPMS) - the install completes partially, then fails. However, I'm thinking I may be confused and should be adding it as a kernel package (is this any different than a standard RPM?) per section 4.5.4 of the documentation. If so, other than specifying the "kernel" property, is there anything different I will need to do to get the custom kernel to install automatically? Any suggestions very much appreciated! Nicoya Helm University of Kansas Medical Center nhelm2@kumc.edu