Lindsay Haisley <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Sat, 02 Aug
2008 17:10:27 -0500:
> This is a Royal PITA! We need to have, preferably as an easy to
> configure option, a consistent, named, filesystem location on which a
> particular device will mount, identified by the media type ("cdrom") or
> some other predictable name. I have a photo cataloging program I wrote
> which expects to find all photo CDs, which have different names
> reflecting dates and sequence, mounted at a location which can be
> specified in its config file. There are all kinds of applications which
> expect this!
It's the automount stuff that's breaking. If I just tell the hal/kde
popup to ignore the new media, and mount it manually, it works as
expected (mount still uses fstab, thank goodness). If I let hal mount
it, it does so but then I have to figure out where. So just not using
hal works in general; it was just the k3b thing that triggered a problem
here, because in that specific instance, right after a burn when it tries
to verify, apparently hal interferes, and there isn't a lot I can do to
avoid it, except doing the verify manually.
That's why I've not experienced serious problems elsewhere, however. I
tend to be very suspicious of automounting, etc, and in general don't use
it, preferring to issue the mount command directly, so I haven't had a
problem in general, only in that corner-case.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
