X.org server 1.8.0 released => no more HAL needed (hopefully)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As ive said before, xorg isnt the only piece of software relying on HAL. Theres also KDE and XFCE.
As long as Slackware stays with KDE 4.3.5 (regarding polkit and the lack of a shadow backend for it), it will also need HAL.
Obviously XFCE has to get a new release as well.
I understand your standpoint but selfishly, i.e. as a Fluxbox user, at least and at last I won't have to re compile xorg-server --without-config-hal anymore
You can also re-compile it with a patch to support udev hotplugging instead of hal hotplugging. In that way, you don't need xorg.conf, and you don't need hal, either. You just need a newer udev.
Generally speaking I avoid patching source tarballs and would be afraid to upgrade a major package like udev. Also, I'm used to edit xorg.conf anyway (BTW, xorg.conf is still usable with X.org server 1.8.0).
Thanks for the heads-up though, it could be useful to somebody more adventurous than me.
the X server gives preference to udev over HAL as a device manager if it finds the libudev library in the system. Part of the library is the 10-evdev.conf configuration file from which udev draws the data to load the X driver as the input device.
I too try to not patch the original source for things where possible, so this xorg looks attractive. I'm with you Didier in that I don't use KDE or XFCE any longer -- but I wonder if/what anything else might be that *requires * HAL to be around on Slackware? I don't auto-mount anything (except fstab partitions during boot). Might have to look into this some more.
Who knows, maybe this Xorg will get into Slack 14 or so!
As for upgrading udev (RE post #6): udev has always been a fast moving target, at least it was when I paid attention, from Slack 11 up until 13.0. I haven't paid as close attention to it the last number of months.
I have successfully upgraded it many times (prior to Slack 13.0) but you must be observant about this because at several points in its lifetime, udev behavior had changed rather drastically from one version to the next, particularly (what I noticed was) syntax in the rules changed, requiring fixing up of any custom udev rules one had made. Besides this, upgrading udev has for the most part not given me much grief.
As ive said before, xorg isnt the only piece of software relying on HAL. Theres also KDE and XFCE.
As long as Slackware stays with KDE 4.3.5 (regarding polkit and the lack of a shadow backend for it), it will also need HAL.
Obviously XFCE has to get a new release as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.