From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] renaming of device
Date: Fri, 15 Jan 2010 04:58:05 +0100 [thread overview]
Message-ID: <20100115035805.GA31381@tansi.org> (raw)
In-Reply-To: <4B4FD035.2030705@whgl.uni-frankfurt.de>
On Fri, Jan 15, 2010 at 03:17:25AM +0100, Sven Eschenberg wrote:
> Arno Wagner schrieb:
>> On Thu, Jan 14, 2010 at 11:16:29PM +0100, Sven Eschenberg wrote:
>>> Hi Arno,
>>
>>> Concerning udev - you could either modify the configuration for the
>>> scsi subsystem, or you could copy it to you own rule file modify it
>>> and override debian's defaults.
>>>
>>> This ways you are a little safer, when the distribution modifies some
>>> rules (for some odd reason) and are sure that dmcrypt returns the
>>> name you expect. In general this is true for most device names where
>>> you have special needs.
>>>
>>> On my debian there are no rules for creating /dev/scsi/* names, at
>>> least not for scsi disks. Might be you are stuck with an older udev
>>> or some outdated configuration maybe?
>>
>> I don't know and do not really have time to investigate now.
>> Come to think of it, it could also have some connection to a
>> recent kernel upgrade, I am running 2.6.32.2 from kernel.org.
>> I did not notice the issue before, so maybe the kernel now also
>> creates device files and there was something about a device
>> pseudo filesystem or the like in the patchnotes.
>
> Ah, I guess you unfortunately actiavted kernel managed tmpfs in /dev,
> which is an experimental feature. Check for CONFIG_DEVTMPFS in your
> kernel config, I bet it is turned on.
Good idea, but no. Must be something in the udev configuration
after all. Not that I found anything. Or anything in the logs.
Hmm. Oh, well. It is not that important. But I really hate this
badly documented obscure "automagical" stuff. As soon as anything
breaks, it really sucks.
On the side of where cryptsetup finds the device for a specific
major and minor number, it is indeed a simple recursive directory
traversal. Unfortunately it is in libdevmapper.c, i.e. in the
system lib of that name. That means it cannot easily be changed.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-01-15 3:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 15:16 [dm-crypt] renaming of device Arno Wagner
2010-01-10 19:49 ` Arno Wagner
2010-01-10 20:33 ` Milan Broz
2010-01-11 16:17 ` Arno Wagner
2010-01-13 7:01 ` Luca Berra
2010-01-13 10:20 ` Sven Eschenberg
2010-01-13 13:13 ` Arno Wagner
2010-01-13 16:18 ` Sven Eschenberg
2010-01-13 17:29 ` Arno Wagner
2010-01-14 18:18 ` Sven Eschenberg
2010-01-14 21:42 ` Arno Wagner
2010-01-14 22:16 ` Sven Eschenberg
2010-01-14 22:46 ` Arno Wagner
2010-01-15 2:17 ` Sven Eschenberg
2010-01-15 3:58 ` Arno Wagner [this message]
2010-01-15 11:28 ` Sven Eschenberg
2010-01-16 0:30 ` Ross Boylan
2010-01-16 2:46 ` Arno Wagner
2010-01-16 8:39 ` Milan Broz
2010-01-16 16:22 ` Arno Wagner
2010-01-16 18:52 ` Sven Eschenberg
2010-01-18 14:06 ` Milan Broz
2010-01-18 14:58 ` Sven Eschenberg
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=20100115035805.GA31381@tansi.org \
--to=arno@wagner.name \
--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.