From: Aaron Lewis <aaron.lewis1989@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Problem with udev and dmcrpyt
Date: Fri, 16 Jul 2010 19:59:26 +0800 [thread overview]
Message-ID: <4C40499E.4020307@gmail.com> (raw)
In-Reply-To: <4C4041E9.9040909@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/16/2010 07:26 PM, Milan Broz wrote:
> On 07/16/2010 01:15 PM, Aaron Lewis wrote:
>
>>> The "name" is whatever you call it when you run cryptsetup luksOpen (or
>>> create). The file system inside the volume can be identified by UUID as
>>> any file system can.
>>
>> For example ? With udev rules or dmcrypt configurations ?
>
> See ehat dm udev rules is doing - using DM_NAME attribute to create symlinks etc.
> There is nothing special needed for dm-crypt - DM rules are common.
>
> ls /lib/udev/rules.d/*-dm-*
> /lib/udev/rules.d/11-dm-lvm.rules
> /lib/udev/rules.d/13-dm-disk.rules
> /lib/udev/rules.d/95-dm-notify.rules
Yep , so udev reads two directory as configurations ?
+ /etc/udev/rules.d
+ /lib/udev/rules.d
All Right , i removed my hacks , now:
%> sudo cryptsetup luksClose /dev/mapper/code
%> sudo cryptsetup luksOpen /dev/sda8 code
Kernel Messages:
udevd-work[11168]: kernel-provided name 'dm-1' and NAME=
'mapper/temporary-cryptsetup-11166' disagree, please use SYMLINK+= or
change the kernel to provide the proper name
udevd-work[11168]: device node '/dev/mapper/temporary-cryptsetup-11166'
already exists, link to '/dev/mapper/temporary-cryptsetup-11166' will
not overwrite it
udevd-work[11168]: kernel-provided name 'dm-1' and NAME= 'mapper/code'
disagree, please use SYMLINK+= or change the kernel to provide the
proper name
udevd-work[11168]: device node '/dev/mapper/code' already exists, link
to '/dev/mapper/code' will not overwrite it
Doesn't looks like anybody else , wired problem.
I should be able to get rid of those messages , right ?
Many thanks.
- --
Best Regards,
Aaron Lewis - PGP: 0x4A6D32A0
FingerPrint EA63 26B2 6C52 72EA A4A5 EB6B BDFE 35B0 4A6D 32A0
irc: A4r0n on freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxASZ4ACgkQvf41sEptMqCKhQCfbCvgWy3lAyMPwCmVMpCO5rRr
c7oAnRzR4mMJI8FHkS5XUNKC72FeAarS
=Ml7s
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-16 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 2:44 [dm-crypt] Problem with udev and dmcrpyt Aaron Lewis
2010-07-16 7:42 ` Milan Broz
2010-07-16 10:53 ` Aaron Lewis
2010-07-16 11:00 ` Thomas Bächler
2010-07-16 11:15 ` Aaron Lewis
2010-07-16 11:26 ` Milan Broz
2010-07-16 11:59 ` Aaron Lewis [this message]
2010-07-16 13:24 ` Milan Broz
2010-07-16 15:22 ` Aaron Lewis
2010-07-16 11:20 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C40499E.4020307@gmail.com \
--to=aaron.lewis1989@gmail.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.