From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: remove permissions file from udev
Date: Wed, 22 Dec 2004 06:18:37 +0000 [thread overview]
Message-ID: <20041222061837.GB31513@kroah.com> (raw)
In-Reply-To: <1103476209.5746.19.camel@localhost.localdomain>
On Wed, Dec 22, 2004 at 03:41:44AM +0000, Willem Riede wrote:
> On 12/19/2004 01:12:34 PM, Kay Sievers wrote:
> >On Sun, 2004-12-19 at 17:36 +0000, Willem Riede wrote:
> >> On 12/19/2004 12:10:09 PM, Kay Sievers wrote:
> >> >
> >> > # tape devices
> >> > KERNEL="ht*", NAME="%k", GROUP="tape", MODE="0660"
> >> > KERNEL="nht*", NAME="%k", GROUP="tape", MODE="0660"
> >> > KERNEL="pt*", NAME="%k", GROUP="tape", MODE="0660"
> >> > KERNEL="npt*", NAME="%k", GROUP="tape", MODE="0660"
> >> > KERNEL="st*", NAME="%k", GROUP="tape", MODE="0660"
> >> > KERNEL="nst*", NAME="%k", GROUP="tape", MODE="0660"
> >>
> >> Would you mind adding OnStream tape drives?
> >>
> >> KERNEL="osst*", NAME="%k", GROUP="tape", MODE="0660"
> >> KERNEL="nosst*", NAME="%k", GROUP="tape", MODE="0660"
> >
> >I've added it to the gentoo rules.
>
> What about the redhat rules?
Red Hat's rules are in their rpm package, and we every once in a while,
sync up the udev tarball with it. Gentoo's rules, on the other hand,
live in the udev tarball, as it's easier for me to maintain them over
time that way :)
So in short, we can guess as to what Red Hat's rule files should look
like, but Red Hat doesn't pull them from us, it's the other way around.
Hope this helps,
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-12-22 6:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 17:10 udev: remove permissions file from udev Kay Sievers
2004-12-19 17:31 ` Marco d'Itri
2004-12-19 17:36 ` Willem Riede
2004-12-19 17:49 ` Kay Sievers
2004-12-19 18:12 ` Kay Sievers
2004-12-19 19:57 ` Kay Sievers
2004-12-20 0:59 ` Marco d'Itri
2004-12-20 1:17 ` Kay Sievers
2004-12-20 13:36 ` Kay Sievers
2004-12-20 14:03 ` Marco d'Itri
2004-12-20 14:54 ` Kay Sievers
2004-12-20 17:13 ` Lindsay Haisley
2004-12-20 20:30 ` Kay Sievers
2004-12-20 20:49 ` Kay Sievers
2004-12-20 20:51 ` Marco d'Itri
2004-12-20 20:55 ` Kay Sievers
2004-12-20 20:58 ` Tobias Klauser
2004-12-20 23:36 ` Lindsay Haisley
2004-12-21 3:04 ` Kay Sievers
2004-12-22 3:41 ` Willem Riede
2004-12-22 6:18 ` Greg KH [this message]
2004-12-22 14:25 ` Willem Riede
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=20041222061837.GB31513@kroah.com \
--to=greg@kroah.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).