at least latest udev rules (I detected it with sys-fs/udev-115-r6) CAPI is broken and unusable. REASON: following lines are missing in *.rules # capi devices KERNEL=="capi", NAME="capi20", SYMLINK+="isdn/capi20", GROUP="uucp", MODE="0660" KERNEL=="capi*", NAME="capi/%n", GROUP="uucp", MODE="0660" after adding a custom rule with above lines, CAPI is working again. Reproducible: Always Steps to Reproduce:
Does capi require one special package to be installed? If yes the rules should be part of this package.
(In reply to comment #0) > at least latest udev rules (I detected it with sys-fs/udev-115-r6) CAPI is > broken and unusable. This error occurs since udev-115-r5
well, there is net-dialup/capi4k-utils, which is needed for using CAPI. I can include it there, no problem; it's my package. But it was historically always included in UDEV, so it's odd that it was removed w/o any notice. I will "pimp up" net-dialup/capi4k-utils asap (i.e. this weekend). But a quick(er) fix would to block net-dialup/capi4k-utils-20050718-r1 to -r3 with udev-115-r5 and above.
(In reply to comment #3) > well, there is net-dialup/capi4k-utils, which is needed for using CAPI. I can > include it there, no problem; it's my package. But it was historically always > included in UDEV, so it's odd that it was removed w/o any notice. > Well, you may have not noticed, but there was a major udev redesign starting from udev-115-r2. w/o notice: Look at thread: http://thread.gmane.org/gmane.linux.gentoo.devel/51484 and http://thread.gmane.org/gmane.linux.gentoo.devel/51750 > I will "pimp up" net-dialup/capi4k-utils asap (i.e. this weekend). > > But a quick(er) fix would to block net-dialup/capi4k-utils-20050718-r1 to -r3 > with udev-115-r5 and above. > You also can block >=udev-115-r2 from within capi4k-utils.
ok, I will block it for the time being within capi4k-utils. At least for the current ones. And then I try to rev-bump with added udev-rules.
Added this rule back to udev-116-r1.
thanks!