From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karel Zak Subject: Re: [PATCH] 90crypt: keys on external devices support Date: Thu, 21 Oct 2010 15:29:16 +0200 Message-ID: <20101021132916.GC22186@nb.net.home> References: <4CBDA328.40401@googlemail.com> <1287497223-sup-3606@etiriah> <4CBDAC3D.7050906@googlemail.com> <4CBE44D3.6070000@googlemail.com> <1287580805-sup-6517@etiriah> <4CBF004F.9070201@googlemail.com> <1287586242-sup-9146@etiriah> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <1287586242-sup-9146@etiriah> Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="utf-8" To: Amadeusz =?utf-8?B?xbtvxYJub3dza2k=?= Cc: Mr Dash Four , initramfs On Wed, Oct 20, 2010 at 05:17:22PM +0200, Amadeusz =C5=BBo=C5=82nowski = wrote: > When you're mounting device are you always specifying "-t fs_type"? := -) > Disk is mounted readonly, so even if mount performs wrong guess, noth= ing > bad happens. This is rare case. Although maybe we can add it=E2=80=A6= :-) Then > it would be: >=20 > rd.luks.key=3D::: The LABEL and UUID are always stored in filesystem specific superblock (or root directory) on the device. It means that your system has to be able to detect FS type before it's able to read LABEL/UUID from the device. The is unnecessary. Karel --=20 Karel Zak http://karelzak.blogspot.com