On Fri, 2010-04-30 at 08:41 +0000, Chow Loong Jin wrote: > That basically defines the whole problem, as I understand it right now. From > here on, I see two possible solutions to fix this: > 1. Improve wait-for-root, udev, and blkid to be able to check for signatures > even with resume_offset. This will not be easy, and will result in lots of > code changes. TuxOnIce detection will also be needed, of course. > You've gone barking up the wrong tree here, this is only supposed to be the signature of the block device *itself* returned from the udevdb.
When resume_offset is set, a further probe would be warranted. There's no reason to modify any of the blkid stack. > 2. Bring back the previous behaviour, i.e. tell the splash that it's > attempting to resume, attempt to resume, and if resume failed, update > the splash and go along its merry way. This is the easiest path, and > will definitely not result in false negatives. > This doesn't work for people who have swap on a different device that we have to wait for. That's a great big false negative. > If possible, I'd like like this as a SRU. > No. We don't add features in SRU. If this worked for you in the past, it wasn't by intent, it was by luck. Scott -- Scott James Remnant [email protected] -- Resume from disk (swapfile) fails https://bugs.launchpad.net/bugs/554009 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
