I'm new to both SuSE and Autoyast. I've read through the autoinstall docs on the Suse site and find that I don't seem to know enough about autoyast in the first place to figure out what they are telling me. Here's what I've done and the problems I am having: I created a directory /SUSE9 and copied (cp -a /mnt/* /SUSE9/) all 5 CDs into this directory. I setup Yast to use this as a repository (I already used Yast update to patch this machine, so my yast utilities should be the latest available). I found that, using the GUI to select my source directory, if it appends a trailing / to the path (/SUSE9/) - it is not seen as a valid source. Finally figured that out and got autoyast to see the directory as well. I created a config for a server I am building. I used the Minimal+X11 selection plus added dhcp and bind. I setup some user accounts, etc. Everything seemed fine (the disks on this compaq dl360 show as /dev/ida/c0d0 so I had to hand-edit my config file afterwards). I then chose to build an ISO based on this config. It said it found all the necessary files and created an iso file, which I burned to media. First problem I had was that the compaq seems to have acpi issues, so I had to boot the cd with "linux acpi=off". Is there a way to configure autoyast to add those parameters by default? This CD will be used to rebuild the system should it die for some reason (hard drive crash or something) - it would be easier to hand off to my support people if they had very few ways of generating problems ;-) Second, I had an error installing grub (in the config file I told it to use the MBR and to replace what is there) The error was 'File not found'. I chose to reconfigure and retry and it worked ok - not sure if this is a problem with this particular machine or in my config. Any ideas? Next, it rebooted and went to install packages, but it suddenly couldn't find most of my packages and started prompting me for CD2. Shouldn't the 'Create ISO' setup the necessary paths in the iso image so that it works? Is there something I have to configure elsewhere? Once I get past this I'll hack away at adding extra packages (samba3, etc). I haven't had any luck getting autoyast to recognize my custom .sel file (it can't open any of my CD-provided .sel files either, so I don't understand how it works) Also, autoupdate pulls down patch.rpm files. Is there a way to apply these to my source directory so that my final build cd is patched already? Thanks Steve Oh, is there any plan to make the mailing list archives searchable?