When using the command below, the second problem regarding cciss disks has been
corrected:
/usr/bin/mksidisk -A --name oscarimage1 --file
/usr/share/oscar/oscarsamples/cciss.disk
/var/lib/systemimager/images/oscarimage1/etc/systemimager/autoinstallscript.conf
is now correctly generated when cciss disks are used.
BOOTDEV = /dev/cciss/c0d0
Which is now correct (trailing "p" is dead once for all... I hope)
Regards,
--
Olivier LAHAYE
CEA Saclay
DRT-LIST-DETECS-SSTM
--- ./systeminstaller/SystemInstaller/Partition/IA.pm 2009-11-10 18:00:09.000000000 +0100
+++ ./systeminstaller/SystemInstaller/Partition/IA.pm.orig 2009-10-30 19:48:27.000000000 +0100
@@ -352,11 +352,7 @@
foreach my $dev (keys(%{$DISKS{PARTITIONS}})) {
# Figure out the diskname
my $diskname=$dev;
- if ($dev=~/c[0-9]+d[0-9]+p[0-9]*$/) {
- $diskname=~s/p[0-9]*$//;
- } else {
- $diskname=~s/[0-9]*$//;
- }
+ $diskname=~s/[0-9]*$//;
$diskname=~s/^\/dev\///;
my $parnum=$dev;
$parnum=~s/\/dev\/$diskname//;
@@ -463,11 +459,7 @@
$bootdev=$rootdev;
}
if (!($bootdev =~ m:/dev/md:)) {
- if ($bootdev =~ /c[0-9]+d[0-9]+p[0-9]*$/) {
- $bootdev =~ s/p[0-9]*$//;
- } else {
- $bootdev =~ s/[0-9]*$//;
- }
+ $bootdev =~ s/[0-9]*$//;
}
return SystemInstaller::Image::write_scconf($ipath, $rootdev, $bootdev);
} # create_systemconfig_conf
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
