Currently systeminstaller will create /etc/mdadm.conf in your image
even if your disktable do not have any raid devices, the following
patch fixes that:
--- SystemInstaller/Partition/IA.pm.orig 2007-05-28
03:15:45.000000000 -0400
+++ SystemInstaller/Partition/IA.pm 2007-05-28 04:46:18.000000000 -0400
@@ -285,8 +285,8 @@
my ($image_dir,%DISKS) = @_;
# only RAID1 is actually supported currently (EF: Nov 30, 2005)
- return if (!defined($DISKS{RAID0}) && !defined($DISKS{RAID1}) &&
- !defined($DISKS{RAID5}) && !defined($DISKS{RAID6}));
+ return if (!(%{$DISKS{RAID0}}) && !(%{$DISKS{RAID1}}) &&
+ !(%{$DISKS{RAID5}}) && !(%{$DISKS{RAID6}}));
local *RT;
if (-f "$image_dir/etc/mdadm.conf") {
&verbose("Overwriting old mdadm.conf file from image $image_dir...\n");
Since I do not have access to RAID systems, I cannot really test it
completely -- if someone could test it for me, that would be great.
Thanks,
Bernard
-------------------------------------------------------------------------
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
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
