[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#408767: kde mount removable media without iocharset and ignore HAL mountoptions



Hi,

2007 m. sausis 28 d., sekmadienis 14:02, Alexander Gerasiov rašė:
> KDE allow users to mount removable media via HAL.
> HAL has some system-wide settings for media mounting
> (volume.policy.mount_option.* keys which are accessible via
> libhal_volume_policy_get_mount_options()). This settins are depricated for
> now, but gnome, ivman, pmount-hal and may be other soft still use this
> settings.
If volume.policy.mount_option.* is depreciated, what is the replacement for 
it?

> Non-uft8, non-latin1 systems need codepage=,iocharset= for mounting some
> media (e.g. vfat).
> KDE don't allow to configure mounting, to force using of this settins,
> and doesn't use mount options from HAL.
> (Look at http://bugs.kde.org/show_bug.cgi?id=133456 also)
Uncheck "UTF-8 charset" in <your media>->Properties->Mounting. Then, I 
believe, HAL should mount with your current locale charset.

> So KDE doesn't use HAL settins (as most analogous software do), and
> doesn't allow Russian (and other non-latin1) non-utf8 users mount vfat
> media in their local codepage. If we force KDE a little bit, it will use
> HAL settings and that will solve our problem.
Where do those HAL settings come from? A custom HAL config file? It does not 
look like a user-friendly solution. So it adds little benefit.

> Unability to mount vfat with iocharset,codepage is very serious problem
> with makes KDE's mounting useless for most of Russian (and other
> non-latin1) users.
You can always setup a plain old /etc/fstab entry for your device. This way 
you can mount with whatever options you need. Beware that, unfortunately, 
LABEL= stuff in /etc/fstab is not supported by KDE media manager.

> Unfortunately I've found this problem so late. If it's impossible to
> include the following patch into Etch release, may be it's possible to
> push it into one of following proposed-update builds? And into r1?
r1 and later will only contain fixes for security and serious/grave bugs. This 
bug is not such. So now or never (wrt to etch).

Attachment: pgp321UIadjw5.pgp
Description: PGP signature


Reply to: