linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rules
Date: Fri, 19 Aug 2005 22:51:37 +0000	[thread overview]
Message-ID: <20050819225137.GB30811@kroah.com> (raw)
In-Reply-To: <87y86yxhv5.wl%muneda.takahiro@jp.fujitsu.com>

On Fri, Aug 19, 2005 at 08:53:50PM +0900, MUNEDA Takahiro wrote:
> Hi,
> 
> I have a question about udev.rules files.
> 
> What is the role of these files?
> 
>  debian/udev.rules
>  gentoo/udev.rules
>  suse/udev.rules
>  ...
> 
> Are these files offical for each distribution?

More or less, they come from the the different distribution packages.
Every distro has slightly different rules files because of different
issues.

> The meaning of this question is, I want to know where is the
> best place to post the distribution specific patch.

To the distro itself.  It will flow back into the main udev package
after the distro accepts it.

thanks,

greg k-h


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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

  parent reply	other threads:[~2005-08-19 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 11:53 udev rules MUNEDA Takahiro
2005-08-19 12:04 ` Marco d'Itri
2005-08-19 22:51 ` Greg KH [this message]
2005-08-21 23:12 ` MUNEDA Takahiro

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=20050819225137.GB30811@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).