On Mon, 06 Nov 2006 12:42:40 +0100
Frank Küster <[EMAIL PROTECTED]> wrote:
> Vagrant Cascadian <[EMAIL PROTECTED]> wrote:
>
> > Package: uswsusp
> > Version: 0.3~cvs20060928-2
> > Severity: serious
> > Justification: Policy 10.7.3
> >
> > i had locally modified my /etc/uswsusp.conf to use a different "resume
> > device", but on a recent upgrade, it over-wrote my configuration file
> > changes without asking.
> >
> > this also results in my resume partition getting written to a device it
> > can't read from(an encrypted swap device on lvm), which could cause
> > data loss if i do not manually regenerate the initramfs image and try to
> > use s2disk.
I think standard resume is started after encrypted swap is setup, so you
should be able to use it without problems.
>
> At a short glance, it looks like the config script sets resume_device
> unconditionally to the first partition in /proc/swap (or rather, the
> first one produced from
>
> sort -r -k 3 /proc/swaps | awk '$2=="partition" {print $1}'
>
> ) without asking or, what's more important, without checking the
> configuration file. Later, the postinst script enters this value into
> the configuration file, which would be correct if the config script had
> taken it from there.
Thanks for looking in to this Frank, but I think you're mistaking. What
it does (well, is supposed to do) is make a debconf list of valid swap
partitions, with the biggest as the default. Then it parses the config
file and set values it found as the answers to the questions. Depending
on the priority the questions are then asked or not.
So the only scenario I can imagine that this goes wrong is that the swap
partition you configured in /etc/uswsusp.conf is not active at the time
of the upgrade.
Vagrant, was that the case? Can you send me the content of /proc/swaps?
Frank, did you have the same problem or where you just bug-hunting?
grts Tim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
