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.
Anyways, I will just look up major and minor numbers manually
until cryptsetup either reports all matching in /dev/ or has
a preferred device for a major/minor combination.
Regards
-Sven
Regards
-Sven
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
