also sprach David Härdeman [EMAIL PROTECTED] [2006.11.13.0014 +0100]:
So that means that suspend2disk actually removes the swap signature from
disk when you suspend. I seemed to recall that the suspend solutions
didn't do that but reading the source it seems I'm wrong.
Aparently. Also note
On Mon, November 13, 2006 10:39, martin f krafft said:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.13.0014 +0100]:
So that means that suspend2disk actually removes the swap signature from
disk when you suspend. I seemed to recall that the suspend solutions
didn't do that but reading
block 397887 398302
thanks
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.13.1350 +0100]:
I take it that you're referring to the in-kernel swsusp and out-of-kernel
suspend2 projects?
Yes, sorry for not being clear.
And on a related note, this bug now seems to be as fixed as can be
in
unblock 397887 398302
clone 397887 -1
retitle -1 Add resume partition setup to initramfs
severity -1 minor
block -1 398302
tags -1 -pending
thanks
On Mon, Nov 13, 2006 at 02:39:16PM +0100, martin f krafft wrote:
And on a related note, this bug now seems to be as fixed as can be
in the sense of
On Sat, Nov 11, 2006 at 05:52:35PM +0100, martin f krafft wrote:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.11.1239 +0100]:
cryptswap /dev/hda2 cryptroot
keyscript=/root/decrypt_derived,hash=sha256,size=256,cipher=aes-cbc-essiv:sha256
So how do I initialise /dev/hda2 for this to
On Sat, Nov 11, 2006 at 05:09:44PM +0100, martin f krafft wrote:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.11.1239 +0100]:
Ok, I've committed fixes for both your bugs to the SVN repo. Could you
please test the package? Either by downloading it from:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.12.1645 +0100]:
Then, provided that the swap entry is configured in /etc/crypttab, run
/etc/init.d/cryptdisks start and it'll do the setup for you.
lapse:~# grep hda2 /etc/crypttab
cr_hda2 /dev/hda2 cr_hda5
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.12.1715 +0100]:
I'm not able to reproduce this (by using a valid keyscript which
is present and executable)
Of course I forgot to make it +x. More in the other reply.
--
.''`. martin f. krafft [EMAIL PROTECTED]
: :' : proud Debian
On Sun, Nov 12, 2006 at 09:48:16PM +0100, martin f krafft wrote:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.12.1645 +0100]:
Then, provided that the swap entry is configured in /etc/crypttab, run
/etc/init.d/cryptdisks start and it'll do the setup for you.
lapse:~# grep hda2
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.12.2308 +0100]:
created/setup correctly, /bin/fstype returns unknown for FSTYPE,
and thus the cryptroot script thinks that something went wrong
and loops endlessly. For some reason, mkswap didn't work. It did,
however, when I tried again.
On Sun, Nov 12, 2006 at 11:24:53PM +0100, martin f krafft wrote:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.12.2308 +0100]:
created/setup correctly, /bin/fstype returns unknown for FSTYPE,
and thus the cryptroot script thinks that something went wrong
and loops endlessly. For some
On Fri, Nov 10, 2006 at 01:43:05PM +0100, martin f krafft wrote:
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.10.1331 +0100]:
The hook should warn about these situations though and then skip
adding the resume partition details to the initramfs image...I'll
fix that
That's what I
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.11.1239 +0100]:
Ok, I've committed fixes for both your bugs to the SVN repo. Could you
please test the package? Either by downloading it from:
http://www.hardeman.nu/~david/cryptsetup_1.0.4-7_i386.deb
I installed it, made the changes you
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.11.1239 +0100]:
cryptswap /dev/hda2 cryptroot
keyscript=/root/decrypt_derived,hash=sha256,size=256,cipher=aes-cbc-essiv:sha256
So how do I initialise /dev/hda2 for this to work? Am I expected to
run the decrypt_derived script and take the
Package: cryptsetup
Version: 2:1.0.4-4
Severity: important
As of late, cryptsetup figures out what swap device I need to resume
from disk and tells initramfs to also initialise that device even
before root is brought up.
The problem is quite simply that some of us have previously
configured the
On Fri, November 10, 2006 10:34, martin f krafft said:
As of late, cryptsetup figures out what swap device I need to resume
from disk and tells initramfs to also initialise that device even
before root is brought up.
The problem is quite simply that some of us have previously
configured the
On Fri, November 10, 2006 12:10, David Härdeman said:
On Fri, November 10, 2006 10:34, martin f krafft said:
As of late, cryptsetup figures out what swap device I need to resume
from disk and tells initramfs to also initialise that device even
before root is brought up.
The problem is quite
also sprach David Härdeman [EMAIL PROTECTED] [2006.11.10.1331 +0100]:
The hook should warn about these situations though and then skip
adding the resume partition details to the initramfs image...I'll
fix that
That's what I meant. Thanks for reading through my blather.
On a related note, if
18 matches
Mail list logo
