On Thu, 25 Jul 2013, Ben Hutchings escribió: > On Thu, 2013-07-25 at 09:54 +0000, Rodolfo García Peñas (kix) wrote: > > Ben Hutchings <b...@decadent.org.uk> escribió: > > > > > On Wed, 2013-07-24 at 15:57 +0400, Askar Safin wrote: > > >> > I think this file should be updated every time the package > > >> "initramfs-tools" is reconfigured. > > >> > > >> Also, ideally, initramfs should be rebuilded every time user changes > > >> fstab. But, I think this is very hard to reach. > > >> Also, I think, every tool which updates fstab, should call initramfs > > >> rebuilding (if swap is changed and hibernation is enabled). > > >> In particular, every package configuration script which updates fstab > > >> should trigger initramfs-tools reconfiguring. > > > > > > I think there is only one such script, which is the postinst script for > > > linux-base which made a one-time update of configuration files to use > > > UUIDs. It updated the initramfs-tools resume file too. > > > > > > But I wonder whether this configuration file is really needed for most > > > system. Couldn't we use blkid to find the swap partition automagically? > > > (The configuration file would still be necessary if there are multiple > > > swap partitions.) > > > > > > Ben. > > > > > > -- > > > Ben Hutchings > > > Once a job is fouled up, anything done to improve it makes it worse. > > > > Hi Ben, Askar, > > > > thanks a lot for your replies. I will update the uswsusp.config and > > uswsusp.postinst scripts to write that file and then call > > update-initramfs script. I will use UUIDs in that file (when available). > > uswsusp is not allowed to change an initramfs-tools config file > directly: > <file:///usr/share/doc/debian-policy/policy.html/ch-files.html#s10.7.4>
Yes, sorry about that. Then initramfs-tools should update that file, checking if the /etc/uswsusp.conf file exists and reading the value of "resume device". Should I forward the bug to initramfs-tools package? > And why should it make a difference whether uswsusp or kernel-only > suspend is used? uswsusp has three tools: * s2ram: suspend to RAM. * s2disk: suspend to disk. * s2both: save the memory to the disk, like s2disk, and then suspend to RAM, like s2ram. If the system runs out the battery or it has a power failure, then the system will found the image disk in the next boot. s2ram includes a machine whitelist and it can suspend using three different methods (using the whitelist, using kernel mode set (KMS) or forced). This tool doesn't use the resume file. s2disk and s2both tools use the resume file, so your question is about these tools. These tools can write the image to the swap file selected by the user (the resume file), they can compress the image (using less swap and doing the suspend faster (less disk I/O)), they can encrypt the image file and other less important things. kix. > Ben. > > -- > Ben Hutchings > Once a job is fouled up, anything done to improve it makes it worse. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
