Am Freitag, 6. April 2007 20:54:28 schrieb Doug Goldstein:
> Michael Cummings wrote:
> steev got hal 0.5.9 into the tree (it's masked) and we've both been
> solidly kicking it to behave how we need it. Anyone interested in
> testing it out would be very helpful.
>
> I can promise it won't come to your house and beat up your dog. But I
> can't promise you might have some little glitches here and there that I
> end up asking you to help debug. Overall it's a much more enjoyable
> version to work with then 0.5.7 and 0.5.8 ever were. We're currently
> sitting at 4 patches and that number will probably move to 5 over the
> next few days. They're fairly straight forward and not to difficult to
> manage.

It works really fine here (finally, selecting CPU scaling schemes works again 
in KPowersave).

The only thing, that bugged me was after installing it, a lot of daemons* 
crashed because hald did an autoreload because of it's inotify feature to 
reload rules as soon as there are changes to it's rules files.

*daemons/applications that crashed:
dbus
powersaved -> KPowersave
Networkmanager -> KNetworkmanager

Also, the new hald didn't want to start, because dbus had crashed because of 
the auto-hald-reload.

So we need to prevent this before it goes stable:

a) print out a big fat warning before doing the update / make the update 
interactive, so we make sure, the user knows about the dangers

b) find a way, to postpone the reload until the next reboot / disable 
auto-reloading for the currently running session

This were the only problems I could find so far.
What I really liked about the update: didn't have to re-emerge 
(revdep-rebuild) a single package.. ;-)

Regards,

Elias P.

Attachment: pgpVYakR5uzGo.pgp
Description: PGP signature

Reply via email to