clone 550152 -1
retitle -1 udev rules must not rename kernel devices
reassign -1 dmsetup
thanks
/lib/udev/rules.d/55-dm.rules needs to be fixed:
On Apr 19, Kay Sievers kay.siev...@vrfy.org wrote:
ENV{DM_NAME}==?*, NAME=mapper/$env{DM_NAME}, SYMLINK+=$kernel
This is not supported and must
On Sun, Apr 18, 2010 at 23:08, Marco d'Itri m...@linux.it wrote:
On Apr 18, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
KERNEL==audio, NAME=%k0, SYMLINK+=%k
Nowadays this is considered bad, accordingly to the upstream maintainer
you should not change
On Apr 19, Kay Sievers kay.siev...@vrfy.org wrote:
/lib/udev/rules.d/55-dm.rules
Device-mapper is work-in-progress, and probably just uses NAME=
which is ok.
There is this rule, which is what the original poster was complaining
about:
ENV{DM_NAME}==?*, NAME=mapper/$env{DM_NAME},
On Mon, Apr 19, 2010 at 11:46, Marco d'Itri m...@linux.it wrote:
On Apr 19, Kay Sievers kay.siev...@vrfy.org wrote:
/lib/udev/rules.d/55-dm.rules
Device-mapper is work-in-progress, and probably just uses NAME=
which is ok.
There is this rule, which is what the original poster was
On Mon, Apr 19, 2010 at 11:56:37AM +0200, Kay Sievers wrote:
This is not supported and must be fixed. Udev does not support
swapping primary device names around, and devtmpfs will always create
the device node with the kernel name anyway.
The documentation does not stat this constraint. And
On Mon, Apr 19, 2010 at 12:13, Bastian Blank wa...@debian.org wrote:
On Mon, Apr 19, 2010 at 11:56:37AM +0200, Kay Sievers wrote:
This is not supported and must be fixed. Udev does not support
swapping primary device names around, and devtmpfs will always create
the device node with the kernel
On Mon, Apr 19, 2010 at 11:39:28AM +0200, Kay Sievers wrote:
On Sun, Apr 18, 2010 at 23:08, Marco d'Itri m...@linux.it wrote:
On Apr 18, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
KERNEL==audio, NAME=%k0, SYMLINK+=%k
/etc/udev/rules.d/00-local.rules
On Apr 19, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
I don't know what you exactly consider different... just a few
examples for you to explain which of those you consider good and which
bad:
All these just define the standard kernel name for the benefit of old
kernels which did
On Mon, Apr 19, 2010 at 13:28, Mario 'BitKoenig' Holbe
mario.ho...@tu-ilmenau.de wrote:
On Mon, Apr 19, 2010 at 11:39:28AM +0200, Kay Sievers wrote:
On Sun, Apr 18, 2010 at 23:08, Marco d'Itri m...@linux.it wrote:
On Apr 18, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
Udev should no longer delete the link it has created:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=6252f9e732c827defdac38e2eccab0657492d9c9
Still, replacing the default kernel-named nodes with links with the
same name can result in unexpected behavior and is not supported. It
Hello Kay,
On Mon, Apr 19, 2010 at 07:06:06PM +0200, Kay Sievers wrote:
Udev should no longer delete the link it has created:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=6252f9e732c827defdac38e2eccab0657492d9c9
Thank you very much. The patch works well:
$ ls -l /dev/dm*
On Mar 15, Marco d'Itri m...@linux.it wrote:
Can you still reproduce this bug with a recent udev a 2.6.32?
Sure.
Then please raise the log level to debug in udev.conf, restart udevd and
trigger an event.
I need both the log and the udevadm monitor output.
udevadm monitor --property
On Apr 18, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
KERNEL==audio,NAME=%k0, SYMLINK+=%k
Nowadays this is considered bad, accordingly to the upstream maintainer
you should not change the kernel name of a device.
I expect that if you swap NAME and
On Sun, Apr 18, 2010 at 08:27:44PM +0200, Marco d'Itri wrote:
On Apr 18, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
KERNEL==audio,NAME=%k0, SYMLINK+=%k
Nowadays this is considered bad, accordingly to the upstream maintainer
you should not change the
On Feb 28, Marco d'Itri m...@linux.it wrote:
Can you still reproduce this bug with a recent udev a 2.6.32?
Sure.
Then please raise the log level to debug in udev.conf, restart udevd and
trigger an event.
I need both the log and the udevadm monitor output.
udevadm monitor --property
--
Can you still reproduce this bug with a recent udev a 2.6.32?
--
ciao,
Marco
signature.asc
Description: Digital signature
On Sun, Feb 28, 2010 at 03:02:32PM +0100, Marco d'Itri wrote:
Can you still reproduce this bug with a recent udev a 2.6.32?
Sure.
Bastian
--
Bones: The man's DEAD, Jim!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Feb 28, Bastian Blank wa...@debian.org wrote:
Can you still reproduce this bug with a recent udev a 2.6.32?
Sure.
Then please raise the log level to debug in udev.conf, restart udevd and
trigger an event.
I need both the log and the udevadm monitor output.
--
ciao,
Marco
signature.asc
Package: udev
Version: 146-4
Severity: important
udev removes symlinks it created before.
| Oct 7 23:47:00 devel udevd-work[16719]: creating symlink '/dev/dm-0' to
'mapper/vg0_devel-swap'
| Oct 7 23:47:00 devel udevd-work[16719]: removed kernel created node
'/dev/dm-0'
Bastian
--
Earth --
19 matches
Mail list logo
