Bug#329319: [Yaird-devel] Bug#329319: yaird: swsusp not all that hard

2005-12-14 Thread C. Scott Ananian
On Tue, 13 Dec 2005, Sven Luther wrote: My impression is that they use the resume= option on the kernel command line, which is then parsed by initrd-tools or whatever. I feel the sane thing to do is to support all three possible ways : 1) have the resume= kernel command line option provided

Bug#329319: yaird: swsusp not all that hard

2005-12-12 Thread Erik van Konijnenburg
On Fri, Dec 09, 2005 at 11:12:05AM -0500, C. Scott Ananian wrote: Package: yaird Version: 0.0.11-12 Followup-For: Bug #329319 It's not all that hard to prevent log replay: just don't mount the file systems! Resume should happen *after* the modules required to access the swap partition are

Bug#329319: yaird: swsusp not all that hard

2005-12-12 Thread C. Scott Ananian
On Mon, 12 Dec 2005, Erik van Konijnenburg wrote: Two points to consider: * what do other tools do? We would not want people that convert to or from initrd-tools or mkinitramfs to have to change their grub of fstab configuration to keep their swsusp working. Only be incompatible if it can't

Bug#329319: [Yaird-devel] Bug#329319: yaird: swsusp not all that hard

2005-12-12 Thread Sven Luther
On Mon, Dec 12, 2005 at 11:59:05PM +0100, Erik van Konijnenburg wrote: The issue of where to resume from is indeed the most important for end-users; your idea of using a 'resume' option is interesting, but I'm not yet sure it's what we want. Two points to consider: * what do other tools do?

Bug#329319: yaird: swsusp not all that hard

2005-12-09 Thread C. Scott Ananian
Package: yaird Version: 0.0.11-12 Followup-For: Bug #329319 It's not all that hard to prevent log replay: just don't mount the file systems! Resume should happen *after* the modules required to access the swap partition are installed (ide, piix, etc), but *before* the root partition is mounted.