From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: default udev rules
Date: Sat, 09 Aug 2008 15:23:19 +0000 [thread overview]
Message-ID: <20080809152319.GA16448@bongo.bofh.it> (raw)
In-Reply-To: <1218277281.31266.32.camel@lgn.site>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Aug 09, Kay Sievers <kay.sievers@vrfy.org> wrote:
> We like to remind everybody, that all distros should work towards a
> default udev rules set, instead of maintaining their own home-grown
Not going to happen, because:
- I consider my rules much more readable and elegant than yours
- anyway there are differences in the permissions (e.g. uucp vs. dialout)
- the default rules are unusable for Debian since we need to support
older kernels (currently and until Xen dom0 will be supported by new
kernels or obsoleted by KVM, >= 2.6.18)
> Please consider adapting the default rules now, and let us find a common
> solution for everybody. New packages, like the upcoming DeviceKit-*
> packages will depend on a recent udev with a proper rules setup.
You should formalize what "a proper rules setup" is, not make other
packages depend on the undocumented behaviour of a default configuration.
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-09 15:23 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 10:21 default udev rules Kay Sievers
2008-08-09 15:23 ` Marco d'Itri [this message]
2008-08-09 18:55 ` Greg KH
2008-08-09 19:30 ` Marco d'Itri
2008-08-09 19:44 ` Greg KH
2008-08-09 20:03 ` Kay Sievers
2008-08-10 18:07 ` Scott James Remnant
2008-08-10 19:18 ` Marco d'Itri
2008-08-10 19:25 ` Greg KH
2008-08-10 19:47 ` Kay Sievers
2008-08-10 20:35 ` Kay Sievers
2008-08-11 8:45 ` Kay Sievers
2008-08-11 8:58 ` Marco d'Itri
2008-08-11 9:01 ` Marco d'Itri
2008-08-11 13:03 ` Scott James Remnant
2008-08-11 14:54 ` Kay Sievers
2008-08-11 15:18 ` David Zeuthen
2008-08-11 15:20 ` Scott James Remnant
2008-08-11 15:21 ` Scott James Remnant
2008-08-11 15:27 ` Kay Sievers
2008-08-11 15:28 ` Kay Sievers
2008-08-11 15:35 ` Scott James Remnant
2008-08-11 15:36 ` Scott James Remnant
2008-08-11 15:42 ` Scott James Remnant
2008-08-11 15:50 ` Kay Sievers
2008-08-11 16:00 ` Scott James Remnant
2008-08-11 16:06 ` piterpk
2008-08-11 16:14 ` Marco d'Itri
2008-08-11 16:19 ` Kay Sievers
2008-08-11 16:26 ` Marco d'Itri
2008-08-11 16:34 ` Kay Sievers
2008-08-11 16:37 ` Greg KH
2008-08-11 16:41 ` Kay Sievers
2008-08-11 16:45 ` Marco d'Itri
2008-08-11 16:48 ` Marco d'Itri
2008-08-11 16:48 ` Kay Sievers
2008-08-11 16:53 ` Scott James Remnant
2008-08-11 16:54 ` Marco d'Itri
2008-08-11 16:58 ` Greg KH
2008-08-11 17:00 ` Kay Sievers
2008-08-11 17:01 ` Kay Sievers
2008-08-11 17:06 ` Scott James Remnant
2008-08-11 17:08 ` Scott James Remnant
2008-08-11 17:10 ` Scott James Remnant
2008-08-11 17:24 ` Kay Sievers
2008-08-11 17:37 ` David Zeuthen
2008-08-11 17:40 ` Scott James Remnant
2008-08-11 18:00 ` Scott James Remnant
2008-08-11 18:01 ` Kay Sievers
2008-08-11 18:06 ` Scott James Remnant
2008-08-11 22:26 ` Greg KH
2008-08-11 22:28 ` Greg KH
2008-08-11 22:29 ` Greg KH
2008-08-11 23:40 ` Scott James Remnant
2008-08-11 23:41 ` Scott James Remnant
2008-08-12 0:00 ` Greg KH
2008-08-12 20:32 ` Kay Sievers
2008-08-13 1:53 ` H. Peter Anvin
2008-08-13 1:55 ` H. Peter Anvin
2008-11-18 17:39 ` Harald Hoyer
2008-11-18 17:52 ` Kay Sievers
2008-11-19 2:09 ` Piter PUNK
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=20080809152319.GA16448@bongo.bofh.it \
--to=md@linux.it \
--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 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.