All of lore.kernel.org
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: replace dev.d/ with a rule based program execution
Date: Sat, 26 Feb 2005 01:06:17 +0000	[thread overview]
Message-ID: <20050226010617.GA2318@wonderland.linux.it> (raw)
In-Reply-To: <20050221181242.GA22891@vrfy.org>

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

On Feb 26, Kay Sievers <kay.sievers@vrfy.org> wrote:

> >> Remember, it's easier for a package to drop a symlink into the
> >> /etc/dev.d/ directory tree, than it is for it to modify / add a udev
> >> rule.
> >True, but creating a symlink in /etc/udev/rules.d/ is as easy (as long
> >as distribution maintainers have discipline and properly document how
> >new files should be named to have them processed at the right time).
> Sure, it may be easier, but dropping brute-force executed programs to a
> directory _is_ the current problem we need to address, and what all the
> discussion is about, right?
Yes, what I am saying is that it will not be a problem if packages
will need to provide udev rules instead of a dev.d/ script.
And if we keep dev.d/ we are left with the issue of making it scale.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-02-26  1:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 18:12 replace dev.d/ with a rule based program execution Kay Sievers
2005-02-22  8:08 ` Hannes Reinecke
2005-02-22 17:53 ` Harald Hoyer
2005-02-23  1:08 ` Marco d'Itri
2005-02-24 20:15 ` David Zeuthen
2005-02-24 20:34 ` Kay Sievers
2005-02-24 20:45 ` David Zeuthen
2005-02-24 21:04 ` Kay Sievers
2005-02-24 21:52 ` Kay Sievers
2005-02-24 22:03 ` David Zeuthen
2005-02-25 23:26 ` Greg KH
2005-02-26  0:28 ` Kay Sievers
2005-02-26  0:57 ` Marco d'Itri
2005-02-26  1:04 ` Kay Sievers
2005-02-26  1:06 ` Marco d'Itri [this message]
2005-02-26  2:22 ` 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=20050226010617.GA2318@wonderland.linux.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.