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: recent hotplug changes are too distro specific
Date: Mon, 05 Jan 2004 18:07:33 +0000	[thread overview]
Message-ID: <20040105180733.GB21940@kroah.com> (raw)

On Wed, Oct 15, 2003 at 10:12:54PM +0200, Olaf Hering wrote:
> Greg,
> 
> I have to veto against a few of the CVS changes from this week. They are
> too distro specific, and I think one of them cant work at all.

Well, they all did come from a Red Hat employee ;)

> I suggest to not check for a distro specifc tool, instead we should
> check if a generic distro provided script exists and execute it. This
> would reduce the patch mess.
> 
> if [ -x /usr/sbin/distro.usb.agent.sh ] ; then
>         /usr/sbin/distro.usb.agent.sh
> fi

Ok, that sounds good, but can we keep the scripts for distros in
/etc/hotplug/ to keep from cluttering up /usr/sbin?

Care to send a patch against the recent changes?

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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

             reply	other threads:[~2004-01-05 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 18:07 Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-15 20:12 recent hotplug changes are too distro specific Olaf Hering

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=20040105180733.GB21940@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).