From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 20 Aug 2010 15:29:22 +0000 Subject: Re: cold-plugged usb flash drive not handled correctly in embedded Message-Id: <20100820152922.GB10088@kroah.com> List-Id: References: <20100820144236.GD10027@debian-wegner1.datadisplay.de> In-Reply-To: <20100820144236.GD10027@debian-wegner1.datadisplay.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Aug 20, 2010 at 04:42:36PM +0200, Wolfgang Wegner wrote: > Hi list, > > I am having a problem with udev on an embedded system and > am asking for advice on how to track this down. The system is > an ARM (kirkwood) platform with a busybox-based init. I cross- > compiled udev-161, made a simple udev start script (basically > ripped off from debian and stripped from most of the config > stuff) and a very basic rules file in > /etc/udev/rules.d/50-udev.rules: > ACTION="add", KERNEL="sd[a-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,flush,quiet,nodev,nosuid,exec,noatime,dmask0,fmask1 /dev/%k /mnt/usbdisk", OPTIONS="last_rule" > ACTION="remove", KERNEL="sd[a-z][0-9]", RUN+="/bin/umount -l /mnt/usbdisk" > > It does not matter if I leave the standard rules in > /libexec/rules.d/ or if I remove them altogether, in either > case the USB flash drive is correctly mounted when plugged > into the running system but not when it is already present when > the system boots up. Perhaps because you do not have a 'mount' executable when the device is found during the boot process? thanks, greg k-h