public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Cooper <gentoo@lakedaemon.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] udev-032 script disabling
Date: Thu, 16 Sep 2004 07:05:59 -0400	[thread overview]
Message-ID: <20040916110559.GQ7924@lakedaemon.net> (raw)
In-Reply-To: <20040916104802.GP7924@lakedaemon.net>

Jason Cooper (gentoo@lakedaemon.net) scribbled:
> Will a future version allow toggling the use of the scripts in that
> directory?  Is there a reason why an average user needs those to run,
> especially in light of things working fine before (well, at least for me
> :) )?

damn.  I started going through the code (delusions of patch-writing
danced in my head) and saw "PROGRAM=", then I found it in 
/etc/udev/rules.d/50... Sorry for the noise.  

Just a thought, perhaps the scripts directory could be under rules.d?
That way it is not confused with something handled in udev.conf.  

Cooper.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-09-16 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 10:48 [gentoo-dev] udev-032 script disabling Jason Cooper
2004-09-16 11:05 ` Jason Cooper [this message]
2004-09-16 15:31   ` Greg KH

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=20040916110559.GQ7924@lakedaemon.net \
    --to=gentoo@lakedaemon.net \
    --cc=gentoo-dev@lists.gentoo.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