The last patch, "autoudev", in that thread fixed the problem correctly.  I
would suggest packaging up and including it.

Thanks again for the quick response,

Mark

On Fri, Jun 19, 2009 at 9:42 PM, Stefan Lesicnik <ste...@lsd.co.za>
wrote:

> nlinux: Could you try the fix described here and let us know...
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495459
>
> Thanks!
>
> --
> Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'
> https://bugs.launchpad.net/bugs/64059
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “zaptel” source package in Ubuntu: Confirmed
> Status in “zaptel” source package in Debian: New
>
> Bug description:
> After loading modules zaptel and wcte11xp new devices are created:
>
> zap14       zap2        zap25       zap30       zap8
> zap1        zap15       zap20       zap26       zap31       zap9
> zap10       zap16       zap21       zap27       zap4        zapchannel
> zap11       zap17       zap22       zap28       zap5        zapctl
> zap12       zap18       zap23       zap29       zap6        zappseudo
> zap13       zap19       zap24       zap3        zap7        zaptimer
>
> But zttest, zttmonitor and chap_zap (asterisk) are expecting:
>
> /dev/zap/*
>
> As described here there are some files needed in /etc/udev/rules.d/ to get
> this to work:
>
> http://asterisk.gnuinter.net/files/digium/zaptel/README.udev
>
> Something like this would do the work:
>
> vim /etc/udev/rules.d/51-zaptel.rules
>
> # Section for Zaptel devices
> KERNEL="zapctl", NAME="zap/ctl", GROUP="asterisk", OWNER="asterisk"
> KERNEL="zaptimer", NAME="zap/timer", GROUP="asterisk", OWNER="asterisk"
> KERNEL="zapchannel", NAME="zap/channel", GROUP="asterisk", OWNER="asterisk"
> KERNEL="zappseudo", NAME="zap/pseudo", GROUP="asterisk", OWNER="asterisk"
> KERNEL="zap0-9*", NAME="zap/%n", GROUP="asterisk", OWNER="asterisk"
>
>
>

-- 
Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'
https://bugs.launchpad.net/bugs/64059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to