From: Silvan Minghetti <bu1137@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Problem with udev-161 and isdn capi device nodes
Date: Mon, 16 Aug 2010 20:19:11 +0000 [thread overview]
Message-ID: <4C699D3F.9080104@gmail.com> (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
next reply other threads:[~2010-08-16 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 20:19 Silvan Minghetti [this message]
2010-08-17 6:18 ` Problem with udev-161 and isdn capi device nodes Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C699D3F.9080104@gmail.com \
--to=bu1137@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).