Bug#442470: uswsusp: s2disk should try and warn that correct kernel no longer available
On Sun, Sep 16, 2007 at 09:15:24PM +0200, Tim Dijkstra wrote: On Sun, 16 Sep 2007 14:23:03 +0100 Dominic Hargreaves d...@earth.li wrote: If you think this is a good idea, I am happy to implement the feature (and test it on unstable; currently I only use s2disk on an etch system but I believe that this bug report is valid for the version in unstable too). Depends a bit on how you think to do this. And how fragile the implementation will be. Can you maybe explain how you think to detect this? Apologies for never getting back to you on this. Unfortunately I no longer use the system in question so I won't be able to work on this now. Feel free to leave this bug open in case anyone else is interested or close it as you see fit. Regards, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#442470: uswsusp: s2disk should try and warn that correct kernel no longer available
Package: uswsusp Version: 0.3~cvs20060928-7 Severity: minor If the kernel is upgraded and system subsequently suspended, it will not be possible to resume (the resume scripts check for this condition and abort). It would be nice if s2disk could try and detect whether the booted kernel is still available, and abort if not. As this is probably needs to be a Debian-specific feature, perhaps a wrapper script to s2disk would be best. If you think this is a good idea, I am happy to implement the feature (and test it on unstable; currently I only use s2disk on an etch system but I believe that this bug report is valid for the version in unstable too). -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages uswsusp depends on: ii debconf [debconf-2.0] 1.5.11Debian configuration management sy ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libgcrypt111.2.3-2 LGPL Crypto library - runtime libr ii libgpg-error0 1.4-1 library for common error values an ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages uswsusp recommends: ii initramfs-tools 0.85h tools for generating an initramfs -- debconf information: uswsusp/compute_checksum: false uswsusp/no_snapshot: uswsusp/suspend_loglevel: uswsusp/no_swap: uswsusp/early_writeout: true uswsusp/image_size: 427135303 uswsusp/compress: true uswsusp/create_RSA_key: false uswsusp/snapshot_device: uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/max_loglevel: uswsusp/resume_device: /dev/mapper/crypt-swap uswsusp/shutdown_method: platform uswsusp/encrypt: false uswsusp/splash: false uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442470: uswsusp: s2disk should try and warn that correct kernel no longer available
On Sun, 16 Sep 2007 14:23:03 +0100 Dominic Hargreaves [EMAIL PROTECTED] wrote: Package: uswsusp Version: 0.3~cvs20060928-7 Severity: minor If the kernel is upgraded and system subsequently suspended, it will not be possible to resume (the resume scripts check for this condition and abort). Hmm, I agree this is a nice possibility to shoot yourself in the foot. But I also think that most people that have just done an kernel upgrade will reboot. It would be nice if s2disk could try and detect whether the booted kernel is still available, and abort if not. As this is probably needs to be a Debian-specific feature, perhaps a wrapper script to s2disk would be best. If you think this is a good idea, I am happy to implement the feature (and test it on unstable; currently I only use s2disk on an etch system but I believe that this bug report is valid for the version in unstable too). Depends a bit on how you think to do this. And how fragile the implementation will be. Can you maybe explain how you think to detect this? grts Tim signature.asc Description: PGP signature
