From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Manual udev invocation & via hotplug method gives different results
Date: Fri, 12 Mar 2004 01:42:17 +0000 [thread overview]
Message-ID: <20040312014217.GA28756@kroah.com> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E9021E2549@orsmsx409.jf.intel.com>
On Thu, Mar 11, 2004 at 05:26:29PM -0800, Sabharwal, Atul wrote:
> Is there a difference between invoking udev manually from the command
> line versus
> invoking it from a hotplug event ? I expect the same result but have a
> case where
> the results are different :
Have you tried using udevtest to see if that gives you the same result?
I am not sure what the /proc/scsi... echoing really does with regards to
creating hotplug events. Are you sure it is identical?
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-12 1:42 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 [this message]
2004-03-12 1:51 ` Sabharwal, Atul
2004-03-12 18:44 ` Sabharwal, Atul
2004-03-12 18:54 ` Manual udev invocation & via hotplug method gives different Kay Sievers
2004-03-12 19:03 ` Manual udev invocation & via hotplug method gives different results 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=20040312014217.GA28756@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 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.