On Wed, 07 Feb 2007, Nigel Cunningham wrote: > Ok, as far as usage scenario goes, that's fair enough. But as to the > solution, I wonder though whether it's making life more complicated than > it needs to be. After all, we should also be able to cope okay with > having the power suddenly go out. If we can cope with that, cleaning > filesystems prior to suspending should be a non-issue.
We don't cope okay with the power going out, at all. And as an user case, a need for fsck if you do something that is a reasonable use case (unplugging devices while suspended) is not okay, either. > Likewise with changes in hardware. Once hotplugging support is mature, > suspending, switching around hardware and resuming should just result in > hot[un]plug events. Well, if we add *move* events for when someone unplugs a usb stick in one port and replugs it in another while the system is in lala-land... maybe :-) It would be normal to do it, when dealing with docks. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/