9 Sep
2011
9 Sep
'11
5:27 p.m.
On Sep 9, 2011 12:38 PM, "Timothy Pearson" <kb9vqf(a)pearsoncomputing.net>
wrote:
Hi.
Call this ridiculous, call it what you will.
Why don't we maintain HAL? As with Qt3, if no one supports it, it can just
"disappear into our source. No one need bother with it.
I mean it is an integral part of a desktop and there is no viable
replacement. Therefore I vote that we should adopt it.
Thoughts?
Calvin
> On Friday 09 September 2011 19:46:47 Timothy Pearson wrote:
>
>>
>> I should mention as well that if OpenSUSE does not automount into
/media
>> either, then the patch is not
distro-specific, it is simply incomplete,
>
> It is complete in the part that is related to KDE3. It does not provide
> HAL functionality
> because HAL is not a part of KDE3.
>
>> as
>> it does not provide all the functionality for pluggable media that once
>> existed with HAL.
>
> Yes, it needs either an auto-mounter such as devmon or udiskie started
or
an auto-mount
udev rule enabled.
With devmon the patch works well currently on my machine. Enabling
automount
in udev rules comes into conflict with fsck on each boot because the
devices get mounted before fsck
starts which leads it to complain that the devices already mounted and
unaccessible
(but this may be distro-specific behavior).
In light of this, I would consider this patch a temporary workaround to a
far more serious problem, and would reject the patch for inclusion in the
upstream TDE sources.
In fact, as a matter of policy I am going to reject all piecemeal HAL
workarounds unless they implement portions of the libraries (TUComputer,
TUPower) that I have mentioned earlier. This decision is an effort to
keep Trinity maintainable and stable, and continue with the philosophy of
having dedicated system access libraries that then distribute information
and control of system functions to higher level TDE applications.