From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Wed, 02 Jun 2004 17:41:59 +0000 Subject: Re: Hotplug events vs proc - timing Message-Id: <20040602174159.GB12396@kroah.com> List-Id: References: <40BCD9C6.1040909@cornell.edu> In-Reply-To: <40BCD9C6.1040909@cornell.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, Jun 02, 2004 at 01:36:09PM -0400, Bill Nottingham wrote: > Greg KH (greg@kroah.com) said: > > 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. > > Hm, as I was thinking, the hotplug event is triggered by the USB > insertion; what's really needed for updfstab is that it gets > run triggered on the *scsi* device creation. Or is this the proc > file you're referring too? Yes, good point, you should update the fstab after the device node is created. You can learn of that by putting your script in the /etc/dev.d/ directory tree. 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