There might be a bug: when I tried an install, it also activated my extended (container) partition. Using the rescue system to (re)activate the boot partition cured the problem. I did not try to reproduce it though Thierry On Tuesday 06 January 2009, L. V. Lammert wrote:
At 08:59 PM 1/6/2009 +0100, you wrote:
On Tuesday, 2009-01-06 at 12:39 -0600, L. V. Lammert wrote: Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 2 3917 31455270 f W95 Ext'd (LBA)
Woahh! :-O
That is strange indeed. An extended (container) partition as bootable. Right now, I wouldn't know how to handle that. I simply do not know.
The REALLY STRANGE part is that the installation went just fine! I have been trying to get the mouse working for a couple of weeks, .. rebooting MANY times with no problem at all.
/dev/sda2 3918 11749 62910540 83 Linux /dev/sda3 11750 15012 26210047+ 83 Linux /dev/sda5 2 392 3140676 82 Linux swap / Solaris /dev/sda6 393 3655 26210016 83 Linux /dev/sda7 3656 3917 2104483+ 83 Linux
Notice that you have about half of the disk unused (15013..30401), and due to the strange positioning of sda2 and sda3, it has to go to sda4, all of it.
Yep, .. eventually that will be a separate partitions for VMs.
Now, if 'Repair System' would only work (it's 15 minutes & counting since I had to reboot).
TFTR!
Lee
-- “Microsoft isn't evil, they just make really crappy operating systems.” Linus Torvald -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org