Package: udev Severity: minor Tags: sid
-- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: x86_64 Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Hello team! I do not know, if the following is a real bug or just a config problem. Well, after upgrading to the latest kernel, I get some messages by udev, exactly by something called "udev-work". It is telling me, that the names of my encrypted devices are somehow not compatible to the kernel, and I have either to change the kernel or set SMLINK+= or similar. It is further telling me, that the new name "dm-0" is not compatible to "mapper/home". Please apologise, that I did not send the copy of the message, as it is shown at booting, and does not appear in any logfiles. Well, I suppose, it might be easily to change some configurations, but I still could not find out, how udev is exactly working. I suppose, it has something to do with /lib/udev/rules.d/80-udisks.rules. Anyway, I attach the related files, it would be nioce, if you could point me to the error: /etc/fstab # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/sda3 /boot ext2 defaults 0 1 /dev/sda5 none swap sw 0 0 /dev/sda6 / ext3 defaults,errors=remount-ro 0 1 /dev/sda2 /winxp auto user,rw,noauto 0 1 /dev/mapper/home /home ext3 defaults,errors=remount-ro 0 2 /dev/mapper/usr /usr ext3 defaults,errors=remount-ro 0 2 /dev/mapper/var /var ext3 defaults,errors=remount-ro 0 2 /dev/cdrom /media/cdrom0 udf,iso9660 user,ro,noauto 0 0 none /proc/bus/usb usbfs auto,devmode=0666 0 0 /dev/disk/by-label/UIT-KEY1 /mnt/sdc1 vfat / uid=0,gid=0,umask=277 0 0 As you see, I am using an usb-key with the key on it. /etc/crypttab # <target name> <source device> <key file> <options> home /dev/sda7 /mnt/sdc1/key luks usr /dev/sda8 /mnt/sdc1/key luks var /dev/sda9 /mnt/sdc1/key luks home /dev/sda7 none luks,retry=1,cipher=aes-lrw-benbi:sha256 usr /dev/sda8 none luks,retry=1,cipher=aes-lrw-benbi:sha256 var /dev/sda9 none luks,retry=1,cipher=aes-lrw-benbi:sha256 This configuration worked for a long time. I think, I have to rename the devices and/or mountpoints. As this configuration is still working (except of the strange output), I could still not decide, if it is a rwal bug or not. However, thank you very much for reading this mail! Please ask for more information if needed. This behaviour appears on 32-bit and 64-bit systems. Best regards Hans-J. Ullrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
