On Tue, Apr 05, 2011 at 02:30:39AM -0000, NoOp wrote:
> @Colin re comment #14: I'm not sure that I understand "filesystem
> corruption in the context of hibernation". The system hasn't been
> hibernated since installing Natty on the /dev/sda7 partition.
I wasn't saying that your bug was due to hibernation. I was saying that
if I reverted the os-prober changes that caused this bug, then that
would have the effect of resurrecting an old bug that caused filesystem
corruption in the context of hibernation.
It may be less typing, but it may also take considerably longer to run,
depending on what needs to be checked.
> Either way something has to give, as continuing to have to go through
> contortions every time that natty installs/overwrites/changes grub is
> growing very tiresome. Next step will be to install grub to it's own
> partition so that natty can't mess with it at all.
I realise that this bug is a problem. All I'm saying is that simply
reverting to the previous state isn't an option.
On Tue, Apr 05, 2011 at 02:30:39AM -0000, NoOp wrote:
> @Colin re comment #14: I'm not sure that I understand "filesystem
> corruption in the context of hibernation". The system hasn't been
> hibernated since installing Natty on the /dev/sda7 partition.
I wasn't saying that your bug was due to hibernation. I was saying that
if I reverted the os-prober changes that caused this bug, then that
would have the effect of resurrecting an old bug that caused filesystem
corruption in the context of hibernation.
> BTW:
> $ sudo fsck /dev/sda5 && sudo update-grub
> seems simpler than:
> $ sudo mount /dev/sda5 /mnt && sudo umount /dev/sda5 && sudo update-grub
It may be less typing, but it may also take considerably longer to run,
depending on what needs to be checked.
> Either way something has to give, as continuing to have to go through overwrites/ changes grub is
> contortions every time that natty installs/
> growing very tiresome. Next step will be to install grub to it's own
> partition so that natty can't mess with it at all.
I realise that this bug is a problem. All I'm saying is that simply
reverting to the previous state isn't an option.