Quoting Donovan Craig (email@example.com):
> Even though the Canon Ixus cameras aren't mass storage
> still have to mount the USB file system.
> Try this as root, it seemed to get my little Ixus talking and working
> with gtkam.
> modprobe usb-uhci
> mount -t usbdevfs usb /proc/bus/usb
That's useful, and links to the even more broadly useful USB
I've been working with USB on my laptop, since my wife gave me
a 32 MB
Easy Disk flash-memory drive, a cute plastic thing on a keychain fob. It
needs the usb-uhci and usb-storage drivers (impliedly also usbcore). At
which point, one can do:
# mount -o uid=1000,gid=1000,noatime -t vfat /dev/sda /mnt/fob/
(where 1000 is my own login account's UID and GID).
Note: That command (or anything like it) always returns:
mount: block device /dev/sda is write-protected, mounting read-only
Two points about that:
(1) I think the automatic read-only mounting default is
protect the device against early failure from wear: Flash memory is
good for about 10,000 write cycles. This is also why I mount using
"noatime": Otherwise, even as routine an operation as "ls" would cause
a write in the form of updating atime (access time).
(2) The Easy Disk appears to be treated like a floppy disk
instead of a
hard drive, which is why it's sda instead of sda1. I.e., the block
device it's addressed via cannot be partitioned.
Therefore, attempting "fdisk /dev/sda" returns...
# fdisk /dev/sda
You will not be able to write the partition table.
...because of this device-class consideration (and is the same
you'd get from attempting "fdisk /dev/fd0").
To enable write access after initial mounting, do:
# mount -o rw,remount /mnt/fob
The mount options cited previously can and should be put in
/dev/sda /mnt/fob vfat uid=1000,gid=1000,user,noauto,noatime 0 0
Cheers, Founding member of the Hyphenation Society, a grassroots-based,
Rick Moen not-for-profit, locally-owned-and-operated, cooperatively-managed,
firstname.lastname@example.org modern-American-English-usage-improvement association.