Comment 60 for bug 610898

Testcase 4: Lucid 10.04.2 on C: drive (ntfs partition /dev/sda2)
=============================================
Grub version in wubildr at install 1.98-1ubuntu5
Grub version in Ubuntu at install 1.98-1ubuntu10
debconf-show grub-pc --> install-devices: <blank>

Test method:
Add proposed to sources and update grub-pc through synaptic (not running
other updates)

Expected result:
===========
1. wubildr on /host (/dev/sda2) will be updated
2. grub modules added to /boot/grub
3. grub.cfg contains extra code (similar to normal install)

Results
======
1. wubildr on /host updated
2. grub modules added to /boot/grub
3. grub.cfg contains extra code

grub is now 1.98-1ubuntu12
debconf-show grub-pc --> install devices changed to /dev/loop0

Conclusion
========
Results as expected, but there is still a distinct difference between wubi
not installed to the same partition as windows.

PS Grub menu (from wubildr) now shows 1.98-1ubuntu12 (as expected)

NOTE:
I don't plan to do any more tests at this point, unless the code changes.
Although I expected the code to work more like Natty (updating wubildr no
matter which partition it is installed to), on the positive side, it doesn't
prompt to install grub to the MBR. And when it does update the grub.cfg to
the state that caused the memory corruption on recreating the loopback
device, it also updates the wubildr - to prevent the booting problem.
Although the same bad wubildr will exist on the non windows partition
installs, the bug shouldn't be triggered.

However, installs with a bad wubildr where it is still booting (I've seen
cases where the corruption only occurs following a subsequent kernel update)
might still have problems.

Also, it seems that the grub-install-devices is a factor in whether the
wubildr is updated on non-windows partition installs, but not on windows
partition installs.