From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 22 Oct 2009 17:01:50 +0200 (CEST) MIME-version: 1.0 Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KRX005AY8F10340@mta-1.ms.rz.RWTH-Aachen.de> for dm-crypt@saout.de; Thu, 22 Oct 2009 17:01:49 +0200 (CEST) Received: from [134.61.40.115] ([unknown] [134.61.40.115]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KRX0005U8F1BN20@relay-auth-1.ms.rz.rwth-aachen.de> for dm-crypt@saout.de; Thu, 22 Oct 2009 17:01:49 +0200 (CEST) Message-id: <4AE073DD.9070903@archlinux.org> Date: Thu, 22 Oct 2009 17:01:49 +0200 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= References: <4ADD7639.6060904@archlinux.org> <4ADD7B1F.9060704@redhat.com> <4ADD9876.8000006@redhat.com> <4ADDA96F.2080109@archlinux.org> <4AE05FE8.7090908@redhat.com> In-reply-to: <4AE05FE8.7090908@redhat.com> Content-type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary=------------enig2C394B9BB38643B56761EC1E Subject: Re: [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or resource busy List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Rajnoha Cc: dm-crypt@saout.de, Milan Broz This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2C394B9BB38643B56761EC1E Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Peter Rajnoha schrieb: > ..ok, finally we kept the "last_rule" in the lvm/dm upstream. This is t= he > safe way. Maybe later we can think of a solution where we will rely on = the > others so they will check the variables we set for them (if that's > possible at all). But it would be too dangerous now, I have to admit. >=20 > You can check the rules we have in the upstream - if you have any comme= nts > or hints, just feel free to write me back... I am going to replace our own device-mapper rules with upstream rules (I = think when we made our own rules, dm didn't have any, or I overlooked the= m). --------------enig2C394B9BB38643B56761EC1E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkrgc90ACgkQEda5KzHP/VA1jgCggaApqULAXlAtTi0po1FW2K4H oWcAnik+gAyR1iZZtgn2ur88/xPgoUjs =LlUZ -----END PGP SIGNATURE----- --------------enig2C394B9BB38643B56761EC1E--