Erich, since minix was never used with systemimager I propose to put it at the bottom of the filesystems list in UseYourOwnKernel.pm (instead of just after cramfs).
In this way minix will be used only if cramfs, ext[23] or reiserfs are unavailable. Moreover, what kind of failures have you found exactly with cpio initrd? in my tests it worked very well with a suse10.0. Cheers, -Andrea -------- Original Message -------- Subject: [systemimager-commits] r4017 - in trunk: initrd_source/skel/etc initrd_source/skel/etc/init.d lib/SystemImager Date: Tue, 10 Apr 2007 09:28:58 -0500 From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Author: efocht Date: 2007-04-10 09:28:57 -0500 (Tue, 10 Apr 2007) New Revision: 4017 Added: trunk/initrd_source/skel/etc/dhclient-script.si-prefix Removed: trunk/initrd_source/skel/etc/dhclient-script.systemimager-prefix Modified: trunk/initrd_source/skel/etc/init.d/functions trunk/lib/SystemImager/UseYourOwnKernel.pm Log: Added support for minix filesystem initrd. The opensuse10.2 kernel has only minix builtin. To my failures to use a UYOK cpio built initramfs on opensuse10.2 this was the only workaround. The minix filesystem allows filename lengths of maximum 30 characters. This means the longest filenmae in the initrd skeleton had to be shortened. ------------------------------------------------------------------------- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
