Thanks for the reply. I guess I should have RTFM about --autodetect-disk. I will test that the next time I make an image...
As for UUIDs I'm already using disk labels now, they are like UUIDs but with human readable names and easier to remember (e.g. LABEL=boot instead of UUID=01234...). With this the only problem was the autoinstallscript, which expected hda disks (from the golden client) instead of the sda disks (from the normal clients). So I guess --autodetect-disk should work in this case... My clients use Kubuntu 7.04. My image server for testing was Debian (Etch), the production server runs with Gentoo (2007.0). Thomas Krause -----Ursprüngliche Nachricht----- Von: Andrea Righi [mailto:[EMAIL PROTECTED] Gesendet: Montag, 6. August 2007 16:36 An: Thomas Krause Cc: sisuite-users@lists.sourceforge.net Betreff: Re: [sisuite-users] Yet another SDA/HDA problem Thomas Krause wrote: > Hi, > > [snip] > > Thomas Krause > Thomas, many thanks for reporting all these interesting and useful info. BTW, maybe a cleaner workaround could be to use only UUIDs in /etc/fstab and create a master autoinstall script using the --autodetect-disk option (both available in si_getimage and si_mkautoinstallscript). I've not tested it, but theoretically in this way we could be totally independent on the particular udev disk naming rules and we should be able to handle the hda -> sda transition problem without any additional configuration... Regards, -Andrea PS which distro did you use for your installations? ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
