halevt-dev
[Top][All Lists]
Advanced

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

Re: [Halevt-dev] wrong message about fstab


From: Patrice Dumas
Subject: Re: [Halevt-dev] wrong message about fstab
Date: Mon, 6 Jul 2009 15:44:57 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Sat, Jul 04, 2009 at 08:46:31PM +0200, DoubleHP wrote:
> reference: http://bugs.gentoo.org/show_bug.cgi?id=276097
> 
> /org/freedesktop/Hal/devices/volume_uuid_ba10196b_ce79_4026_a04f_a18dc8829474:
> DBus Error org.freedesktop.Hal.Device.Volume.PermissionDenied: Device
> /dev/sdb1
> is listed in /etc/fstab. Refusing to mount.
> 
> when in fact my fstab contained:
> 
> LABEL=arch_longtime /mnt/arch_longtime ext3 defaults,noauto 0 0
> 
> Message says: "/dev/sdb1 is listed in /etc/fstab" but searching the
> patern with vim or grep gave no result. So, the way the message is
> phrased is wrong.

It is not an halevt-mount message, but a message from HAL, that 
halevt-mount merely relays. So I doubt anything can be done at the
halevt/halevt-mount level.

> furthermore, after commenting the line, it still refused to mount my
> volume automatically:
> 
> Jul  1 21:33:05 moon-gen-3 logger: Mount error for
> /org/freedesktop/Hal/devices/volume_uuid_ba10196b_ce79_4026_a04f_a18dc8829474:
> Jul  1 21:33:05 moon-gen-3 logger: DBus Error
> org.freedesktop.Hal.Device.Volume.InvalidMountOption: The option
> 'umask=000' is
> not allowed for uid=0

Same here. It is an error message generated by HAL.

> But without the mask "000", FAT usb keys mounted by halevt are not
> writable for user (what renders halevt useless to me).
> 
> please:
> - change the error message when the device is mentioned in fstab by his
> label
> - make halevt more "user writable"
> - document this feature a better in example/squeleton files

For these, I think that the issue is in HAL (or, possibly, in the hal
or polkit configuration), so I don't think anything can be done in halevt.

> - provide the URL of a full ducomentation in each conf file (and not
> just the URL of the XML format itself: it's missing all hal specific
> available variables).

HAL specific variables should not be documented in the halevt 
documentation itself in any case. If you have an url for all the
hal variables, I'd be happy to make a link in the manual.

> I think the usable variables are the names given by lshal, but i am not
> sure at all. This is not stated anywhere. 

Indeed. It would be worth mentionning in the documentation, I'll add
a section.

> Furthermore, the syntax to use
> variables is no more the same as used to be with ivman. Confusing.

I used ivman as inspiration for the design of halevt, but it is definitely
different. For example, it tries to avoid the design issues of ivman (most 
of them having been reported to me by Rohan). So I am not very worried 
with differences with ivman syntax, any similarity being more or less 
luck. The important thing is that it is properly documented.

--
Pat




reply via email to

[Prev in Thread] Current Thread [Next in Thread]