All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: New hotplug interface is not working right for me
Date: Fri, 11 Mar 2005 20:48:04 +0000	[thread overview]
Message-ID: <20050311204804.GA23927@thyrsus.com> (raw)
In-Reply-To: <20050311060405.GA16141@thyrsus.com>

Kay Sievers <kay.sievers@vrfy.org>:
> On Fri, 2005-03-11 at 14:07 -0500, Eric S. Raymond wrote:
> > Kay Sievers <kay.sievers@vrfy.org>:
> > > > Will gps.dev will be executed on every tty activation, or just
> > > > when a gps%e node gets created?   
> > > 
> > > Yes, that is right.
> > 
> > Your answer is ambiguous.  Which arm of the disjunct are you referring to?
> 
> The first one. It will get executed for every tty.

That's what I thought you were going to tell me.  Oh, well.

OK.  My descision is that I'm going to stick with old-style hotplug
until udev is a bit more mature.  I have a hotplug agent that works,
and I doubt distro makers will break it in the forseeable future, because
tremendously popular USB cameras rely on the same mechanism.

But I like the udev approach better, and when It grows the right kind
of event filtering that I needn't worry about causing nasty amounts of
boot lag, I'll move to it.

I support the proposed HOTPLUG key and Kay's proposal for an
additional rules file.  But I'm not attached to either.

Thanks for the help and explanations.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


-------------------------------------------------------
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://ads.osdn.com/?ad_ide95&alloc_id\x14396&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

  parent reply	other threads:[~2005-03-11 20:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  6:04 New hotplug interface is not working right for me Eric S. Raymond
2005-03-11  6:45 ` Greg KH
2005-03-11  8:54 ` Kay Sievers
2005-03-11 13:38 ` Eric S. Raymond
2005-03-11 14:16 ` Kay Sievers
2005-03-11 15:38 ` Hannes Reinecke
2005-03-11 15:40 ` Eric S. Raymond
2005-03-11 16:05 ` Kay Sievers
2005-03-11 17:03 ` Eric S. Raymond
2005-03-11 17:32 ` Kay Sievers
2005-03-11 18:58 ` Christian Zoz
2005-03-11 19:07 ` Eric S. Raymond
2005-03-11 20:35 ` Kay Sievers
2005-03-11 20:48 ` Eric S. Raymond [this message]
2005-03-14 17:06 ` Darren Salt
2005-03-14 18:16 ` Marco d'Itri
2005-03-14 18:25 ` 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=20050311204804.GA23927@thyrsus.com \
    --to=esr@thyrsus.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 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.