From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HaM4m-0000iI-BJ for garchives@archives.gentoo.org; Sun, 08 Apr 2007 01:20:16 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l381JMnL025903; Sun, 8 Apr 2007 01:19:22 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l381HVnN023653 for ; Sun, 8 Apr 2007 01:17:31 GMT Received: from [192.168.2.88] (ip68-12-46-112.ok.ok.cox.net [68.12.46.112]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 9E64F64D52 for ; Sun, 8 Apr 2007 01:17:30 +0000 (UTC) Message-ID: <4618425C.5060300@gentoo.org> Date: Sat, 07 Apr 2007 20:16:12 -0500 From: Steev Klimaszewski User-Agent: Thunderbird 2.0b2 (X11/20070219) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] *DEVELOPMENT* mail list, right? References: <20070405230345.GA22227@paradox.datanode.net> <46169764.1050905@gentoo.org> <200704080220.30661.mail@eliasprobst.eu> In-Reply-To: <200704080220.30661.mail@eliasprobst.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 78b31c84-34e2-4c58-af49-73ad16d14dc5 X-Archives-Hash: 4fa4b92fd07e6fe82f6ccc7ae5520d62 mail@eliasprobst.eu wrote: > *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. Odd that dbus would crash/restart - hald uses dbus, not the other way around - however, dbus should be restarted to read the new (possibly) hald.conf - the real fix would be for the apps that use hal to NOT bomb when hal is yanked out from under them. Glad it was fairly painless for you. And it is good to know that some people are using KNetworkManager - I don't have a machine currently with KDE installed (my KDE machine died) and so I haven't tested it at all recently. -- Steev -- gentoo-dev@gentoo.org mailing list