You saved me the trouble of typing all this up. :) I would add that it isn't necessary for you to define a loop0 *and* a loop1 in grub, as grub only needs to know about your new boot.disk in order to boot. The "loop=" kernel parameter referencing root.disk is unrelated, and has nothing to do with grub. Rest assured the kernel will find the root.disk when the time comes. Hence simply defining loop0 to be /ubuntu/disks/boot.disk is adequate. Which also means that /boot/grub/grub.cfg requires absolutely no changes. :)
The missing piece to your (my) instructions is how to make grub-install now do the correct thing to /host/wubildr (on C:\) in order for the system to boot as normal to the grub menu. As I mentioned previously, it requires a rather simple change to /usr/share/lupin-support/grub- mkimage, which I've attached as a unified-diff patch. After creating the separate boot.disk and applying my patch, you can simply run e.g. "grub-install hd0" and wubildr will now properly update to boot your boot.disk, and all will be right in the world. heheh. By the way, grub-install leaves all the files behind in /boot/grub that it uses to generate wubildr, which it REALLY should clean up afterwards. They're harmless, but it's messy. ** Attachment added: "grub-mkimage patch for Wubi booting separate boot.disk fs" http://launchpadlibrarian.net/35980900/grub-mkimage.diff -- Wubi/Karmic boot: kernel panic - not synching: VFS https://bugs.launchpad.net/bugs/477169 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
