Bug#335315: yaird: vgchange does not find logical volumes on a dm-crypt device

2005-10-23 Thread Tino Keitel
Package: yaird Version: 0.0.11-6 Severity: normal Hi, my root partition is located in a LVM2 on a dm-crypt device. vgchage doesn't find any VGs during boot. The reason is that vgchange doesn't look for VGs on other device mapper devices per default. To enable this, this line has to be added to

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-05-19 Thread Tino Keitel
On Tue, May 17, 2005 at 19:35:22 +0200, maximilian attems wrote: > On Tue, 17 May 2005, Tino Keitel wrote: > > > On Sat, May 14, 2005 at 18:23:27 +0200, maximilian attems wrote: > > > hello tino, > > > > > > thanks for your patch, > > > i had a l

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-05-17 Thread Tino Keitel
le in the cryptsetup initscript. > > On Sat, Apr 23, 2005 at 22:32:24 +0200, Tino Keitel wrote: > > > here is a patch for mkinitrd to parse the cryptsetup options from > > > /etc/cryptdisks, as it is already done by the initscript from the > > > cryptsetup package.

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-04-23 Thread Tino Keitel
Hi, here is a patch for mkinitrd to parse the cryptsetup options from /etc/cryptdisks, as it is already done by the initscript from the cryptsetup package. Regards, Tino -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-04-23 Thread Tino Keitel
On Sat, Apr 23, 2005 at 22:32:24 +0200, Tino Keitel wrote: > Hi, > > here is a patch for mkinitrd to parse the cryptsetup options from > /etc/cryptdisks, as it is already done by the initscript from the > cryptsetup package. > > Regards, > Tino ...and here is the pa

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-04-06 Thread Tino Keitel
On Sun, Jan 16, 2005 at 17:38:50 +0100, Wesley W. Terpstra wrote: > On Sun, Jan 16, 2005 at 03:42:50PM +, Martin Michlmayr wrote: > > > Maybe the information in /etc/crypttab should be used the same way as in > > > the initscript to contruct the command line for cryptsetup. > > > > Wesley, can

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-01-15 Thread Tino Keitel
Package: initrd-tools Version: 0.1.76 Followup-For: Bug #290708 I was referring to the initscript from the cryptsetup package here. It does some parsing of the options in /etc/crypttab. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture:

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

2005-01-15 Thread Tino Keitel
Package: initrd-tools Version: 0.1.76 Severity: normal I use LVM2 on top of a dm-crypt device. With the initrd created by mkinitrd the cryptsetup command is called with wrong arguments. The -s 128 and -h plain options are missing. The system won't be bootable. If I hack mkinitrd to call cryptsetup