DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
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:00:42 +0200	[thread overview]
Message-ID: <4C403BDA.8020405@archlinux.org> (raw)
In-Reply-To: <4C403A2A.5040004@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Am 16.07.2010 12:53, schrieb Aaron Lewis:
> device name is dynamiclly allocated , i think so.
> Shouldn't there be some ways to identify it like UUID ? In that case ,
> i'll be able to put more accurate rules.

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.

>>> How can i get rid of that together ?
> 
>> Update package which provides DM new rules. Yor distro should provide
>> it if they update udev.
> 
> Guess gentoo never provide such services.

They should. Upstream device mapper provides udev rules that should be
installed with device-mapper. If no udev rules are installed, I would
consider that a bug.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2010-07-16 11:01 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 [this message]
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

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=4C403BDA.8020405@archlinux.org \
    --to=thomas@archlinux.org \
    --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