On 14 February 2012 07:32, Pawel Soltys <sh4dou@...> wrote: > On Tue, Feb 14, 2012 at 10:49 AM, Pawel Soltys <sh4dou@...> wrote: >> On Tue, Feb 14, 2012 at 1:58 AM, David C. Rankin >> <drankinatty@...> wrote: >>> Guys, >>> >>> I don't know if this is worth looking into from a TDE standpoint or if it is >>> still relevant, but HAL and udev stopped the boot process on my Arch box today. >>> Calvin had the issue that I believe he solved by removing an offending udev >>> rule[1]. That raised the question to me whether there is some standardization >>> that HAL will require across distros in order to support TDE or if there is some >>> part of udev that is needed to support HAL? >>> >> Calvin got it to work? >> >>> Arch no longer provides HAL as a standard package. I believe what triggered >>> the boot fail today was the loss of the 'udev-compat' package (unconfirmed). I'm >>> still digging into this, but if HAL will be required for TDE, then should we >>> look into either insuring that a generic HAL version that is compatible with >>> upstream udev is available to the project? >>> >>> I don't know how HAL + udev affect TDE or what the long term thoughts are on >>> either, but I thought I would raise the issues to those smarter than I am in >>> case there is a looming issue coming down the road. >>> >>> What say the experts? Is there any issue with HAL + udev on TDE, or is it just >>> a matter of the individual distro TDE builders to sort out? What worries me is >>> Arch no longer packages HAL and the version we have in the user supported >>> repository (done by 'l0ner' -- thank you!) is hal 0.5.14-7 with a *900K patch* >>> file. If this is where all the distros are ultimately going, we may be better >>> served by deciding how to handle it now rather than waiting until we run into >>> build problems later... >>> >>> >> This may be an arch-only problem for a while. From what I understood >> arch uses last bleeding-edge version of udev, where other distros are >> using older version. >> Trinity team doesn't maintain hal, so it is something for the hal >> package maintainers to fix. >> Anyway I'm looking into it. Since I haven't updated my arch box yet, I >> recovered error that I was getting for some time, but never actually >> figured that it could cause problems in the future: >> >> everything.log.2:Feb 1 05:15:16 localhost udevd[141]: >> RUN+="socket:..." support will be removed from a future udev release. >> Please remove it from: /etc/udev/rules.d/90-hal.rules:2 and use >> libudev to subscribe to events. >> >>> Footnote [1]: (which we are still trying to determine exactly what he removed :) >>> >>> -- >>> David C. Rankin, J.D.,P.E. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: trinity-devel-unsubscribe@... >>> For additional commands, e-mail: trinity-devel-help@... >>> Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ >>> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting >>> > Strangely enough... for me everything works well and starts well after > upgrade. I still get the previously stated errors, but I don't have > hangups of any sort. > Even if HAL is still working - it will break in upcomping udev versions unless we get rid of that rule, and add a patch to hal to subscribe to the changes via libudev instead. Calvin