/usr/lib/systemimager/perl/SystemImager/Common.pm
on the client system, around line 426, "my $cmd". Change the sfdisk option "-uM" to "-uS" and save the file.
prepareclient then adapts to using sectors instead of "mebibytes". I had no idea, but further Googling reveals that mebibytes is a legitimate unit for measuring memory.
Why SuSE defaults to mebibytes instead of megabytes, I don't know.
The empty 4th partition was apparently irrelevant.
-- Carl Benson, PHS Linux NetAdmin (206-667-4862, [EMAIL PROTECTED])
Carl J. Benson wrote:
"sfdisk -l -uM /dev/hda" yields:
Disk /dev/hda: 1216 cylinders, 255 heads, 63 sectors/track Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End MiB #blocks Id System /dev/hda1 * 0+ 6149- 6150- 6297448+ 83 Linux /dev/hda2 6149+ 7177- 1028- 1052257+ 82 Linux swap /dev/hda3 7177+ 9538- 2362- 2417782+ 83 Linux /dev/hda4 0 - 0 0 0 Empty
I noticed a difference in a heading, "MiB" on SuSE9.0, "MB" on RH9. Also "mebibytes" -- what the heck? Could this version of sfdisk be corrupt?
That 4th partition puzzles me; it seems to be an artifact of the installation program. I used fdisk, removed it, and rebooted, but it's still there. Wierd.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
