public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Marcus.Meissner@caldera.de, linux-kernel@vger.kernel.org
Subject: Re: hotplug mopup
Date: Mon, 11 Dec 2000 13:10:19 -0800	[thread overview]
Message-ID: <3A3542BB.F2D7FA0F@pacbell.net> (raw)

> > - I don't think we can say that the kernel hotplug interface is 
> >   complete until we have real, working, tested userspace tools. David, 
> >   could you please summarise the state of play here? In particular, 
> >   what still needs to be done? 
> 
> Well, for USB I would like to know which device major/minor entry a newly 
> plugged device is associated with. 
> 
> Like if I insert a new USB camera, I want to easy find out it is char 81.1 
> (/dev/video1). Or if I plugin a USB storage device I want to easy find out 
> it is /dev/sda now. 

How might that relate to devfs integration?  It addresses similar
problems, and devfsd can call to userspace when such drivers (ones
that show up through major/minor device nodes) appear.  True, some
folk who want to hotplug might want to not run devfs.

- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-11 21:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-11 21:10 David Brownell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-10 12:31 hotplug mopup Andrew Morton
2000-12-10 12:58 ` Jeff Garzik
2000-12-10 13:25   ` Andrew Morton
2000-12-10 15:10 ` Marcus Meissner
2000-12-11  2:36   ` Albert D. Cahalan
2000-12-11  7:04     ` Andrew Morton
2000-12-10 16:35 ` David Brownell

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=3A3542BB.F2D7FA0F@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Marcus.Meissner@caldera.de \
    --cc=linux-kernel@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