there's a new method to mounting hotplug devices. Currently, the broken method is to use fstab-sync. This method is prone to error and has corrupted my fstab a few times. This new method uses a utility called pmount (see #69575) which gnome-volume manager uses to mount devices. Attached you'll find a new hal ebuild and a new ebuild/patch for gnome-volume manager that should remove dependencies on fstab-sync.
Created attachment 42979 [details] HAL Ebuild to exclude --enable-fstab
Created attachment 42980 [details, diff] g-v-m patch to use pmount and not /bin/mount
Created attachment 42981 [details] Ebuild to g-v-m to enable the attached patch
Created attachment 42982 [details, diff] g-v-m patch to use pmount and not /bin/mount Oops. Uploaded the wrong file
Created attachment 42983 [details, diff] g-v-m ebuild to depend on pmount (bug 69575).
Comment on attachment 42983 [details, diff] g-v-m ebuild to depend on pmount (bug 69575). oh man am I stupid tonight.
Created attachment 42984 [details] g-v-m ebuild to depend on pmount Ok, Finally got this file right.
Is there any alternative to g-v-m, like ivmsn works for cds, but I never saw something for usb-sticks?
ideally we'd have the choice of fstab-sync vs pmount virtualized, hardcoding the default mount command like that in gvm isn't a good idea. I imagine a better way to handle it would be to set it by a gconf key or try both commands, setting pmount as first choice.
Any progress on this?
i've given suggestions on what needed to change to begin with, so start your progress there. And iirc i had some other issues when last testing this pack, so there's probably some more than that to be fixed.
i'm going to split this bug up, because it is really two different bugs: - fstab-sync is a hal thing and gvm is ignorant of it - hal knows nothing about pmount, while gvm does
new bug numbers are: 92025, 92026
