Testcase 1: Maverick install on non-windows partition
========================================
Installed Wubi maverick 10.10 on my E: 'drive' (ntfs partition /dev/sda3).
Ran all standard updates.
Added Proposed to the sources.
Processed all proposed updates.
Expected result
===========
1. /wubildr on C: 'drive' (/dev/sda2) would be updated
2. No prompt to suggest installing grub2 bootloader to /dev/sda
3. New grub modules placed in /boot/grub
4. Different grub.cfg
Results
======
1. /wubildr on C: 'drive' was not updated. Remains at version
1.98+20100804-5ubuntu2
Grub2 version (grub-install -v) shows 1.98+20100804-5ubuntu3.3
debconf-show grub-pc shows grub-install devices are blank.
2. There was no prompt to suggest installing grub2 bootloader on /dev/sda2
3. No additional files in /boot/grub
4. No difference in grub.cfg (except the addition of the new kernel in
proposed)
Comments:
a. Positive that there is no prompt that user could select to install grub
bootloader to drive MBR
b. OK that wubildr isn't updated, because the grub.cfg also doesn't contain
the instructions that cause the loopback memory corruption.
c. But result not quite as expected (or is my understanding incorrect?)
Testcase 1: Maverick install on non-windows partition ======= ======= ======= ======= =====
=======
Installed Wubi maverick 10.10 on my E: 'drive' (ntfs partition /dev/sda3).
Ran all standard updates.
Added Proposed to the sources.
Processed all proposed updates.
Expected result
===========
1. /wubildr on C: 'drive' (/dev/sda2) would be updated
2. No prompt to suggest installing grub2 bootloader to /dev/sda
3. New grub modules placed in /boot/grub
4. Different grub.cfg
Results 5ubuntu2 5ubuntu3. 3
======
1. /wubildr on C: 'drive' was not updated. Remains at version
1.98+20100804-
Grub2 version (grub-install -v) shows 1.98+20100804-
debconf-show grub-pc shows grub-install devices are blank.
2. There was no prompt to suggest installing grub2 bootloader on /dev/sda2
3. No additional files in /boot/grub
4. No difference in grub.cfg (except the addition of the new kernel in
proposed)
Comments:
a. Positive that there is no prompt that user could select to install grub
bootloader to drive MBR
b. OK that wubildr isn't updated, because the grub.cfg also doesn't contain
the instructions that cause the loopback memory corruption.
c. But result not quite as expected (or is my understanding incorrect?)