From: Olivier Galibert <galibert@pobox.com>
To: linux-kernel@vger.kernel.org, isdn@linux-pingi.de
Subject: Re: [PATCH] Fix capi devicenames
Date: Thu, 30 Sep 2010 19:35:47 +0200 [thread overview]
Message-ID: <20100930173547.GA91193@dspnet.fr> (raw)
In-Reply-To: <1285851024.748.97.camel@marc>
On Thu, Sep 30, 2010 at 02:50:24PM +0200, Marc - A. Dahlhaus wrote:
[...]
> The only setup that could get broken by this is the setup that uses udev
> to handle the devices and gives the nodes different access rights or
> something.
>
> And that already happened by the time the rules used to create the capi
> devices got removed from udev and it was right to remove them from udev
> IMO.
[...]
> capifs is already deprecated and scheduled for removal soon because udev
> is able to replace its functionality and fedora has a patch in srpm that
> removes the capifs load from capiinit.
>
> Userspace expects the capifs device nodes.
[...]
So if I understand correctly, capifs was deprecated and is soon be
removed because udev was able to replace it given a set of rules, then
after the deprecation was done the rules were deliberately removed
from udev. And that's supposed to be a kernel issue?
Sounds... typical, actually.
OG.
next prev parent reply other threads:[~2010-09-30 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 19:21 [PATCH] Fix capi devicenames Marc - A. Dahlhaus
2010-09-30 9:30 ` Alan Cox
2010-09-30 10:08 ` Kay Sievers
2010-09-30 10:56 ` Alan Cox
2010-09-30 10:37 ` Marc - A. Dahlhaus
2010-09-30 10:50 ` Kay Sievers
2010-09-30 11:29 ` Alan Cox
2010-09-30 12:50 ` Marc - A. Dahlhaus
2010-09-30 17:35 ` Olivier Galibert [this message]
2010-09-30 19:20 ` Kay Sievers
2010-10-01 8:02 ` [PATCH] Fix capi devicenames v2 Marc - A. Dahlhaus
2010-10-01 8:36 ` [PATCH] Fix capi devicenames Marc - A. Dahlhaus
2010-10-01 9:20 ` Kay Sievers
2010-09-30 11:35 ` Alan Cox
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=20100930173547.GA91193@dspnet.fr \
--to=galibert@pobox.com \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.