From: Milan Broz <mbroz@redhat.com>
To: 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 13:20:04 +0200 [thread overview]
Message-ID: <4C404064.5010001@redhat.com> (raw)
In-Reply-To: <4C403A2A.5040004@gmail.com>
On 07/16/2010 12:53 PM, Aaron Lewis wrote:
>> Update package which provides DM new rules. Yor distro should provide
>> it if they update udev.
>
> Guess gentoo never provide such services.
It does, I am using it there:-)
maybe it is masked - that's bug, lvm must depend on new rules/udev then.
Long answer for the archive:
Formerly LVM/DM/cryptsetup managed dev nodes itself.
Later it started to utilize udev for this job, but the transition process
was very painfull and had many iterations. DM used some extension to block
device concept which were incompatible with udev view and vice versa.
So there were several versions of udev rules using various udev extensions,
some of these extension were removed from udev in later releases
(changing base device name is one of them).
It probably takes some time until all changes are propagated to distros...
Bu we finally iterated to situation that udev rules are now working properly
- with compromises on both sides.
(Only one problems remains - namely "watch" rule but is is not related to this problem).
Still, there is fallback mechanism in libdevampper - if the required device node
is not created by udev, it fallback to manual node creation.
(So even in misconfigured system it should work.)
The above means, that distro maintainers should start to compile lvm with udev
support, provide most recent udev rules (part of upstream lvm2/dm package)
and require new udev package which includes all require functionality.
Milan
prev parent reply other threads:[~2010-07-16 11:20 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
2010-07-16 13:24 ` Milan Broz
2010-07-16 15:22 ` Aaron Lewis
2010-07-16 11:20 ` Milan Broz [this message]
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=4C404064.5010001@redhat.com \
--to=mbroz@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox