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? 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 be avoided. > Ideally, avoid incompatibility even among distros.
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 by the user / grub/lilo/yaboot/etc override the detected partition. This is always a good idea, as we showed with the root= kernel command line option, and will allow the user to recover more easily from mistakes and such. 2) have yaird look at the resume option in /etc/fstab as suggested here. Not sure if this is the best thing to do though. 3) have it specified/specifiable in /etc/yaird.conf. The real question being what other tools who do the suspend step usually use for configuration, the resume step is rather easy once we know that. > * Could we avoid configuration altogether? We could simply always do the > resume > code for all swap devices, if swsusp or swsusp2 is enabled in the kernel > config. > If the distro has swsusp in the kernel, this would mean users could start > using swsusp without having to regenerate the initramfs; downside is they > would > have to edit the grub/lilo menu. Notice that one thought i had about swsusp is to have multiple swap partitions associated with multiple non-overlapping partition sets and be able to resume in the one or the other, so i believe your idea will kill this kind of setup. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
