automatic mounting of mass storage devices: light shed on the problem in it's true form after experimentation, consultation and study

[Anil Kumar Sharma]

First thing first, Auto mount USB device in FC4 is limited to craeting a
mount point and providing an icon on desktop to manage the USB device
through right click. This is my understanding for USB on FC4+KDE.
 2. Please tell me if it work like this (for you); in case you have one USB
device (camera/drive/anything) already mounted and you insert another device
in any other free USB port. Does it auto mount second time?
 3. In my experience, it does not work and the second device need be
manually mounted after creating a mount point.
 4. Strangely the second auto mount works for second device also, atleast on
my FC4 box, if login is root (Which I generally do not do). This all under
kde.
 Thanks.


 On 10/27/05, kwhiskers <kwhiskers at gmail.com> wrote:
>
> Thanks to all who have tried to help. I hope to consolidate the thread
> here.
>
> I have partially solved the automounting of usb 'scsi' mass storage
> cameras, which is done by hal. No udev rules are necessary. No device
> definitions are required. It's all already there. fstab-sync takes care of
> creating mount points. /dev/sda and sda1 both appear when the camera is
> plugged in; the necessary kernel modules are automatically loaded.
> Furthermore, it all works...
>
> If one is using gnome: plug in the camera and the filesystem on the
> camera's memory chip will be automatically mounted to /media/usbdisk.
>
> The problem is how to get this to happen under kde. Under kde, one has to
> manually mount the camera. Isn't there a way to make this behave under kde
> the way it is supposed to?
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
>


--
Anil Kumar Shrama
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20051027/173fb0ed/attachment-0001.htm>