On Sat, 2 Dec 2006 13:58:26 -0500, Jerry McBride wrote:

> > I don't normally want it to leave CF cards alone, but just tried and
> > it worked perfectly. Bear in mind that there is no differentiation
> > between different physical formats of flash media, but that KDE
> > considers anything with a dcim directory in the root to be a camera.
> > I just set the auto-action for unmounted camera to Ignore and plugged
> > in my camera's CF card and it did not automount. all that happened
> > was that an icon appeared on the desktop, which I could also disable
> > if I wished.
> >
> > It sounds more like a misconfiguration than a bug.  
> 
> If you spend a bit of time googleing the problem, a lot of people are
> trying to deal with it.

I would if I understood what the problem was. You say you want KDE to
leave CF cards alone, now you seem to be saying that you want it to
automount them and then leave them alone. Please provide a URL
explaining the problem.

> Not everyone works on a desktop/gui all the time... What happens, and
> this is documented in a lot of google matches, once you mount a cf
> card... hald won't let go... the only way to get in unmounted is to
> turn the hal daemon off. This is a horrible situation if you do work
> with cli while kde is being used by someone else.

I've just tried this. I plugged in a CF card, let KDE automount it and
then switched to a VC and pumounted it as the same user, no problem. I
expected there to be a problem if a file manager window was showing the
contents of the card, this used to happen because konqueror had a lock on
the mount point, but that also worked perfectly.

> Form the looks of everything offered... it's easier to not support the
> kde media manager and use autofs... It'll be something to plan on
> administrating, but at least it works 100% with concurrent kde and cli
> sessions.

Autofs polls the drive to see if it's still there, unlike HAL/D-BUS based
solutions that use system messages. This always struck me as rather
kludgy. KDE's automount/hotplug support was patchy a few releases ago,
particularly in 3.4 IIRC correctly, but it seems to work just as expected
now.


-- 
Neil Bothwick

Anything worth fighting for is worth fighting dirty for.

Attachment: signature.asc
Description: PGP signature

Reply via email to