Mandrake Linux: cooker@mandrivalinux.org
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
On Sunday 15 January 2006 01:45 am, Andrey Borzenkov wrote: > > I know this has been discussed before but never answered. > > Will root remain or will it go back to mounted as user one day? > > http://qa.mandriva.com/show_bug.cgi?id=20379 > http://qa.mandriva.com/show_bug.cgi?id=20496 > > Well, as it stands now, it likely to remain broken for some time. > > Current situation: HAL creates /etc/fstab entry with all needed options > that user can mount using /bin/mount (indirectly via another program like > g-v-m does not matter). > > Strategic goal (of HAL development): HAL provides Mount/Unmount methods for > devices. User calls them via D-Bus. It is user's responsibility to provide > all required options, possibly mount point etc (HAL will provide default > one). HAL will add user=<calling user> to make mounted device accessible to > mounting user. > > The net effect is - while now we have centrally managed removable storage > mount configuration, in the future *every user-level interface* like g-v-m, > k-v-m or whatever will have to manage own repository of mount options. > Currently user switching to another desktop transparently gets the same > mounts because they are defined in /etc/fstab. After the change users have > to wait for KDE to catch up in the first place (I have no idea when it is > planned to add support for new model) and in any case, use switching from > DE to GNOME will have to redefine all mount points. May be it is not a > problem, user do not change desktop every day. > > Anyway to really fix the bug you need one of > > - new HAL, and new g-v-m (possibly with gnome-mount) > - new HAL, current g-v-m and fixed hal-system-storage-mount > - current HAL, current g-v-m, hal-system-storage-mount from CVS fixed as > above > > -andrey Thanks Andrey for the explanation. This way, one doesn't not have to ask everyday. -- Thomas Spuhler