Hello.

The client system runs SuSE9.2, SuSE10.0, or SuSE10.1 on x86_64
architecture, with the following RPMs installed:

systemimager-common-3.6.3-1
systemimager-x86_64initrd_template-3.6.3-1
systemimager-client-3.6.3-1

The output of parted looks like, for example:

Disk geometry for /dev/sda: 0kB - 500GB
Disk label type: msdos
Number  Start   End     Size    Type      File system  Flags
1.......32kB....13GB....13GB....primary   reiserfs     boot, type=83
2.......13GB....21GB....8595MB..primary   linux-swap   type=82
3.......21GB....500GB...478GB...primary   reiserfs     type=83

(I ADDED THE DOTS TO MAKE IT EASIER TO COUNT COLUMNS.)

Common.pm incorrectly parses the output and generates these errors:

Argument "3GB    13GB" isn't numeric in numeric gt (>) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 333.
Argument "1GB    8595M" isn't numeric in numeric gt (>) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 333.
Argument "00GB   478GB" isn't numeric in numeric gt (>) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 333.
Argument "   32kB    1" isn't numeric in subtraction (-) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 441.
Argument "3GB    13GB" isn't numeric in subtraction (-) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 441.
Argument "   13GB    2" isn't numeric in subtraction (-) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 441.
Argument "1GB    8595M" isn't numeric in subtraction (-) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 441.
Argument "   21GB    5" isn't numeric in subtraction (-) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 441.
Argument "00GB   478GB" isn't numeric in subtraction (-) at 
/usr/lib/systemimager/perl/SystemImager/Common.pm line 441.

The result is a master script with no numbers for partition sizes.

On the other hand, Common.pm seems to work fine for systems
with i386 architecture running SuSE9.2, 9.3, and 10.0. Why?
Is it parsing the output of sfdisk instead?

If so, how can I influence it to use sfdisk instead of parted
for x86_64 systems? Or is there some other workaround?

Please and thank you for your anticipated help.

--Carl Benson

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to