s it's back.
--
Wesley W. Terpstra <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
le configuration of swap when the
crypttab specifies /dev/*random for the key or the 'swap' option. This
breaks software suspend, but with a random key that's not possible anyways.
--
Wesley W. Terpstra
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
em runs
> without swapspace.
I don't understand what you mean here, could you clarify?
--
Wesley W. Terpstra
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Jan 20, 2005 at 04:17:25PM -0500, Joey Hess wrote:
> Great, so something like this? (Untested)
Worked for me.
--
Wesley W. Terpstra
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ake last-minute changes
> to d-i and debian-cd to add dmsetup everywhere.
At any rate, I agree with your solution, if there is no dmsetup it makes
sense to fall back to using lvm. Since cryptsetup depends on dmsetup, there
is nothing wrong with this solution.
--
Wesley W. Terpstra
--
To
On Tue, Jan 18, 2005 at 02:00:24PM +0100, Marco d'Itri wrote:
> On Jan 18, "Wesley W. Terpstra" <[EMAIL PROTECTED]> wrote:
> > I propose: always add usbhib to the list of modules mkinitrd includes.
> > I'm not certain whether this works w/o the usb host d
this should be done in
mkinitrd. Even if you aren't using cryptsetup, when the initial ram disk
drops you into interactive mode (on failure), you need keyboard control.
Right now, usb keyboard users just get screwed. =)
I propose: always add usbhib to the list of modules mkinitrd includes.
I&#x
x27; and call this from both /etc/init.d/cryptdisks and
/usr/sbin/mkinitrd.
This means I will need to upload a new cryptsetup and provide you a
mkinitrd patch. Then initrd-tools will have to conflict with old versions
of cryptsetup.
--
Wesley W. Terpstra
--
To UNSUBSCRIBE, email to [E
Package: kernel-headers-2.6.8-2-amd64-k8
Severity: serious
The following packages have unmet dependencies:
kernel-headers-2.6.8-2-amd64-k8: Depends: kernel-headers-2.6.8-2 but it is
not installable
E: Broken packages
I see from the changelog the comment:
- Removed i386 from architecture lis
Actually I'm not certain about #266540.
Certainly #266591 is caused by it though.
Possibly also #264339.
On Sun, Aug 29, 2004 at 03:26:24PM +0200, Wesley W. Terpstra wrote:
> Oh, btw the release critical bug #266540 which is holding up
> kernel-image-2.6.8-1-686 from testing is caus
Oh, btw the release critical bug #266540 which is holding up
kernel-image-2.6.8-1-686 from testing is caused b/c this patch is not
applied.
On Sun, Aug 29, 2004 at 03:16:00PM +0200, Wesley W. Terpstra wrote:
> Hello, bug #247054 has been open forever.
>
> The previous maintainer
.
Also, there is a regression in the lvm handling which Herbert Xu fixed
months ago. It now again spews error messages during vgchange. They are
non-fatal, but extremely amature looking.
What is going on?
--
Wesley W. Terpstra
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-1
Severity: normal
Hi, I am running kernel-image-2.6.7-1-686 and using software suspend.
Unfortunately, the 'swsusp' module is missing and /proc/acpi/sleep does
nothing anymore. With kernel-image-2.6.6-1-686 I had no problems.
Also, I have no inter
wice -- once for each device (swap+root).
--
Wesley W. Terpstra
--- mkinitrd.orig 2004-06-05 22:54:52.0 +0200
+++ mkinitrd.mine 2004-06-07 12:08:25.0 +0200
@@ -321,8 +321,90 @@
fi
}
+dmcrypt() {
+ local cipher_mode devname submajor subminor
+
+
On Mon, Jun 07, 2004 at 08:07:16PM +1000, Herbert Xu wrote:
> On Mon, Jun 07, 2004 at 12:02:15PM +0200, Wesley W. Terpstra wrote:
> >
> > It looks to me like the initrd doesn't even need to setup root, right?
> > The boot process will replace the entire kernel, it's
l update my patch and setup swsusp on my machine to test it.
--
Wesley W. Terpstra
On Sun, Jun 06, 2004 at 06:14:01PM +1000, Herbert Xu wrote:
> On Sun, Jun 06, 2004 at 01:19:35AM +0200, Wesley W. Terpstra wrote:
> >
> > Why on earth is swap being configured in the initrd?!
>
> Swap is used for swsusp.
I see.
I'm not familiar with swsusp. Howeve
ms b/c I have a swap partition which uses a different crypto key
on every boot.
Anyways, my patch removes the swap support, and adds support for cryptoroot.
I have attached the patch, as well as an updated example of a script which
uses a USB stick to share the keys.
cryptsetup is sitting i
18 matches
Mail list logo
