Still seeing this bug on an up-to-date Lucid system.

Is there a way to test this outside of usb-creator? I'm not familiar
with how the boot sector in a DOS filesystem is modified, let alone what
the "proper" way of doing it (that would update the backup as well)
would be. But if usb-creator is writing the boot sector by doing the
equivalent of a dd(1) directly to the device, then I don't think the
filesystem driver can be faulted.

-- 
Target FAT32 filesystem has fsck errors after install
https://bugs.launchpad.net/bugs/500696
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

Reply via email to