Skip to contentSkip to conversation

Problem with udev-161 and isdn capi device nodes

DISCUSSION Silvan Minghetti 2 participants 2 messages Aug 16, 2010 – Aug 17, 2010

lore
Share & tools
lore
#0 lore raw

Hi

I'm having a problem with udev >= 154, as it warns on NAME= values different from the kernel provided names, as done per changeset

http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;hucb1ac51ea0176926c749bd0f22c19ce8b20e5f

The problem is, with the following isdn capi rules (which were removed from udev anyway), udev is not able to create the wanted devices, because of a missing directory (/dev/capi), which has to be created beforehand:

SUBSYSTEM="capi", KERNEL="capi", NAME="capi20", GROUP="dialout" SUBSYSTEM="tty", KERNEL="capi[0-9]*", NAME="capi/%n"

so, instead of /dev/capi20 we now get /dev/capi
and /dev/capi0 instead of /dev/capi/0

Is this here to stay or is this going to be changed in the kernel? The new layout breaks quite a few apps/libs...

silvan

#1 lore raw
Quoted 9 lines · Silvan Minghetti

I'm having a problem with udev >= 154, as it warns on NAME= values different from the kernel provided names, as done per changeset

http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;hucb1ac51ea0176926c749bd0f22c19ce8b20e5f

The problem is, with the following isdn capi rules (which were removed from udev anyway), udev is not able to create the wanted devices, because of a missing directory (/dev/capi), which has to be created beforehand:

Quoted 8 lines

SUBSYSTEM="capi", KERNEL="capi", NAME="capi20", GROUP="dialout" SUBSYSTEM="tty", KERNEL="capi[0-9]*", NAME="capi/%n"

so, instead of /dev/capi20 we now get /dev/capi
and /dev/capi0 instead of /dev/capi/0

Is this here to stay or is this going to be changed in the kernel? The new layout breaks quite a few apps/libs...

It needs to be changed in the kernel. It's rather trivial, but I don't know if anybody is working on this at the moment. I guess people have moved to mISDN, and that's why this hasn't really come up so far?

Kay