> Edited /etc/updfstab.conf.default and added the following:
>
> device usbdrv {
> partition 1
> match hd JumpDrive #Wild guess...it worked!
> }
>
> I executed the following commands as root:
>
> #Add the usb-storage device information to the usb.usermap (necessary
> step??)
> cat /lib/modules/<your kernel>/modules.usbmap | grep usb-storage >>
> /etc/hotplug/usb.usermap
> mkdir /mnt/usbdrv #Needed for a mount point
> mkdir /var/run/usb #This was missing on my computer,
> resulting in no auto
> umount...
>
> Create /etc/hotplug/usb/usb-storage (adapted from Bugzilla
> report 113787)
>
> #!/bin/bash
> mount /mnt/usbdrv
> echo '!#/bin/bash' > "$REMOVER"
> echo 'umount /mnt/usbdrv' >> "$REMOVER"
> chmod u+x $REMOVER
>
> Be sure to make usb-storage executable:
> chmod ugo+x /etc/hotplug/usb/usb-storage
>
> That should be it.
>
I want to make it clear that the information above came from the bugzilla
report that Alexandre Ganso published (#113787) and Jason Cortezzo came up
with.
Also, I have a another question regarding usb-storage. By what means is
Gnome/KDE mounting the JumpDrive when it is mounted manually (with an
ordinary fstab entry, right click desktop-->disks-->JumpDrive) without the
use of the above? It clearly is mounting as the current user vs. root as
when attempting the above procedure. If a script controls the process in
the GUI, perhaps it can be adapted to the usb-storage script to work around
the root issue?
Also, the copy process from modules.usbmap to usb.usermap should not be
necessary even though it is needed to get the usb-storage script to execute
in its entirety. The scripts in /etc/hotplug should, I believe, read the
information right out of modules.usermap. Perhaps a bug lies therein?
Actually, without the entries in usb.usermap, the script *is* still being
executed (as evidenced by the file in /var/run/usb); it is just not mounting
the device for reasons beyond me at this point.
