All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: RE: Manual udev invocation & via hotplug method gives different
Date: Fri, 12 Mar 2004 18:54:53 +0000	[thread overview]
Message-ID: <1079117692.1430.8.camel@pim> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E9021E2549@orsmsx409.jf.intel.com>

On Fri, 2004-03-12 at 19:44, Sabharwal, Atul wrote:
> >>Have you tried using udevtest to see if that gives you the same
> result?
> 
> I tried udevtest and it gives same result as udev. The scsi
> commands give three device entries. 

Seems that the kernel emits 3 hotplug events for this device.
If you compile udev with 'make DEBUG=true' you can follow the invocation
of udevsend in the syslog.

Kay



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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:[~2004-03-12 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12  1:26 Manual udev invocation & via hotplug method gives different results Sabharwal, Atul
2004-03-12  1:42 ` Greg KH
2004-03-12  1:51 ` Sabharwal, Atul
2004-03-12 18:44 ` Sabharwal, Atul
2004-03-12 18:54 ` Kay Sievers [this message]
2004-03-12 19:03 ` Patrick Mansfield
2004-03-12 19:43 ` Sabharwal, Atul
2004-03-12 23:50 ` Sabharwal, Atul

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=1079117692.1430.8.camel@pim \
    --to=kay.sievers@vrfy.org \
    --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.