From: Julien BLACHE <jblache@debian.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Questions on udev-acl rules, ACL_MANAGE + bug report
Date: Wed, 16 Jun 2010 04:49:31 +0000 [thread overview]
Message-ID: <87iq5jfup0.fsf@sonic.technologeek.org> (raw)
In-Reply-To: <87k4q82l9k.fsf@sonic.technologeek.org>
Kay Sievers <kay.sievers@vrfy.org> wrote:
Hi,
[udev-acl]
> There is no real long-term plan to explain. It's just that stuff is
> moving all the time. There might be upcoming changes in ConsoleKit
> which require changes again. I'm not really involved in this, don't
It's a bit puzzling to read that, to be honest. "We're going to break
things, deal with it" is becoming a bit old.
> know the details, but I know people talking about new stuff.
Could the above "people" please shed some light on this?
>> Instead of duplicating the rules from libsane, I propose to also set
>> libsane_matched for SCSI scanners starting with the next SANE release
>> (whenever that happens, and I'd encourage distributors to patch the SANE
>> rules right now already).
>>
>> Would that be OK with you?
>
> Sure, sounds good to me. Just let us know, when this is generally
> available in a released version, and we can remove the rule from udev.
I'll do. In the meantime, distributors should patch this up themselves,
as we're probably months away from the next SANE release.
JB.
--
Julien BLACHE <jblache@debian.org> | Debian, because code matters more
Debian & GNU/Linux Developer | <http://www.debian.org>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
next prev parent reply other threads:[~2010-06-16 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 17:01 Questions on udev-acl rules, ACL_MANAGE + bug report Julien BLACHE
2010-06-14 9:08 ` Kay Sievers
2010-06-16 4:49 ` Julien BLACHE [this message]
2010-06-16 7:04 ` 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=87iq5jfup0.fsf@sonic.technologeek.org \
--to=jblache@debian.org \
--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).