From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug events vs proc - timing
Date: Wed, 02 Jun 2004 17:20:21 +0000 [thread overview]
Message-ID: <20040602172021.GA12139@kroah.com> (raw)
In-Reply-To: <40BCD9C6.1040909@cornell.edu>
On Tue, Jun 01, 2004 at 01:32:22PM -0600, Ivan Gyurdiev wrote:
> Fedora's updfstab tool (part of kudzu) is trigged by hotplug to
> add/remove things from fstab, such as my Fujifilm Digital Camera
> (usb-storage, scsi emulation). However... it reads /proc/scsi/scsi, and
> doesn't work as it should because it's triggered before /proc/scsi/scsi
> is updated most of the time. Where is the bug, and how should this race
> be corrected?
The race should be fixed by having the hotplug script wait around for
the proc file to show up.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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-06-02 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 19:32 Hotplug events vs proc - timing Ivan Gyurdiev
2004-06-02 17:20 ` Greg KH [this message]
2004-06-02 17:36 ` Bill Nottingham
2004-06-02 17:41 ` Greg KH
2004-06-02 17:57 ` Marcelo Ricardo Leitner
2004-06-02 18:05 ` Greg KH
2004-06-02 23:19 ` Ivan Gyurdiev
2004-06-03 8:30 ` Harald Hoyer
2004-06-03 16:54 ` Greg KH
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=20040602172021.GA12139@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.