Actually, I did some more Googling today and found this:
http://wiki.archlinux.org/index.php/...es_to_a_device This seems to present a solution to the problem. I haven't yet tried this on my system, but plan to soon as I get a chance... |
<_<
And people say that HAL's autmounting is useless... I used to have these same problems too. But that was well over a year ago. The only way that I personally know how to do this would be to use "fstab-sync", but then again that is hal dependent. It adds a new entry to /etc/fstab whenever a device(user configurable) is added to the system, and then removes the entry when that device is removed.(it can also only modify entries that it itself made, not user created entires) |
Yah - I may have to try something like that, assuming it would work with 2.4.31 kernel (that's what I'm using at the moment, so the link I posted earlier is somewhat useless for me, if what I'm reading about udevinfo is true...) Right now I made an ugly hack to /etc/fstab to set my camera to it's own mount point, which I imagine will break if I reboot my system, but for now it'll work until I can find something better. I may move up to 2.6 if these USB issues become a major headache (assuming that'll help any)
Thanks, |
thamnks MDG for your advice.
this has worked perfectly for me as '/dev/sda1' using sandisk cruzer titanium usb key i have spent so many hours trying to figure out how to use the /proc area to do this - im confused now as to how i got on that track. thanks again!! |
Mounting flash drive
Same problem here, and that help link seems to be dead at the moment.
|
Quote:
Quote:
|
you may find http://wiki.kde.org/tiki-index.php?page=DBUS interesting along with the excellent Arch ref.
|
All times are GMT -5. The time now is 06:36 PM. |