You could simply re-run mkinitrd/grub at the end of the image copy in the post-install script
-Drew -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrea Righi Sent: Monday, June 04, 2007 7:00 AM To: [email protected] Subject: Re: [sisuite-users] Back, have some time,. SDA to HDA imaging Jan Groenewald wrote: > I had the same hda/sda trouble. It was an ide-scsi module, which I had > to add to a pre-UYOK SI kernel, but that is another story. Yes... this is another bad story, but I think we should address it in some ways... it should depend on the udev config, so a very bad, ugly, orrible hack would be to copy the /etc/udev/ conf into the initrd_template and re-create the boot package via si_prepareclient or si_mkbootpackage (kernel + initrd.img). If I'm not wrong Bernard tested it with a CentOS, but IMHO passively copying the /etc/udev dir into the initrd_template should be done only in the strictly necessary cases (think at all the possible dependencies that the udev conf files could require...) Ideas? -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
