Bug 10184

Summary:	udev-rule for capi tries to rename device node to capi20 - not supported anymore.
Product:	Mageia	Reporter:	Christian Lohmaier <lohmaier+mageia>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, mageia, thierry.vignaud
Version:	3	Keywords:	Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	systemd-195-22.mga3.src.rpm	CVE:
Status comment:

Description Christian Lohmaier 2013-05-20 20:59:57 CEST

Loading capi driver results in logmessages:
May 20 20:43:08 maindesk systemd-udevd[2539]: NAME="capi20" ignored, kernel device nodes can not be renamed; please fix it in /usr/lib/udev/rules.d/50-udev-mageia.rules:34
May 20 20:43:08 maindesk systemd-udevd[2539]: NAME="capi/%n" ignored, kernel device nodes can not be renamed; please fix it in /usr/lib/udev/rules.d/50-udev-mageia.rules:35

And the capi20 entry is not created. Also the rules don't setup a default group, which it probably should.

I suggest:

old/current & broken (triggering the error-message, ignoring the rule):
# CAPI devices
KERNEL=="capi",                NAME="capi20", SYMLINK+="isdn/capi20"
KERNEL=="capi*",       NAME="capi/%n"

new/should be:
# CAPI devices
KERNEL=="capi", GROUP="dialout", SYMLINK+="capi20 isdn/capi20"

*) use group dialout, as capi devices usually are used to make calls, either to a telephone or to a fax machine.
*) don't try to rename the device, but make an additional symlink instead
*) drop the capi* rule, as honestly think that creating that under capi/%n creates quite a bit of inconsistency (and won't work anyway, when the capi one cannot be renamed anymore) - then again I don't have multipe capi-instances, so your judgement is needed.

Reproducible: 

Steps to Reproduce:

Thierry Vignaud 2013-05-21 12:22:48 CEST

CC: (none) => mageia, mageia, thierry.vignaud

Manuel Hiebel 2013-05-21 22:43:06 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 Manuel Hiebel 2013-05-21 22:44:54 CEST

(sorry didn't have seen thierry already added people, I should read all actions)

Comment 2 Marja Van Waes 2015-03-31 16:03:15 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD