![]() |
What is relationship between udev and hal in etch?
I've not done the big upgrade in Etch to kde 3.5 yet, nor to the new udev. I notice in synaptic that upgrading udev will cause hal to be UN-installed. Is this a good thing? :-) What is the relationship between the two. I thought they worked together.
Thanks, al |
Hello,I am just thinking of starting a thread,so this One Thanks.
I am using Sarge 3.1 r1.i upgraded many packages from http://www.backports.org .yesterday i tried updating udev081 to udev_084.but this removed hal and hal device manager.also after upgrading to udev_0.084-2bpo1_i386. i rebooted noted some errors scrolling on the screen.help appreciated.. |
If I remember correctly, the udev that gets installed provides a suitable version of hal.
Edit: appy-polly-logies. Got a bit confused. Going to find out differences between the three right now :silly: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ esje@Etch:~$ apt-cache show udev Package: udev Priority: optional Section: admin Installed-Size: 956 Maintainer: Marco d'Itri <md@linux.it> Architecture: i386 Version: 0.084-3 Replaces: initramfs-tools (<= 0.41) Provides: hotplug Depends: libc6 (>= 2.3.5-1), libselinux1 (>= 1.28), initscripts (>= 2.85-16), makedev (>= 2.3.1-77), sed (>= 3.95), lsb-base (>= 3.0-6) Conflicts: hotplug, lvm-common (<< 1.5.13), module-init-tools (<< 3.2-pre9-1), initramfs-tools (<< 0.39), hal (<< 0.5.6-2) Filename: pool/main/u/udev/udev_0.084-3_i386.deb Size: 273900 MD5sum: 6b4c4eebcb51af09b2055fb44c895ed8 Description: /dev/ and hotplug management daemon udev is a daemon which dynamically creates and removes device nodes from /dev/, handles hotplug events and loads drivers at boot time. It replaces the hotplug package and requires a kernel not older than 2.6.12. Tag: admin::boot, admin::filesystem, admin::hardware, interface::daemon, role::sw:server |
try google.com/linux
|
I think most of us are quite capable of finding google :) However, making sense of what google is telling us is not always that easy. Google and the official web-sites of hal, dbus, udev and hotplug are very informative indeed, but if you want to know how they work (or fail to work) together and are not a long-time hardcore kernel hacker, a question such as this is much more useful.
|
So any answer.I asked in backports.org mailing list,but it bounced saying me not a member!
|
acanton, not sure if this will help but I hope you are using at least 2.6.12 kernel(linux-image-2.6.x) because that is needed by newer udev in etch ;and hal removal is normal because hal is also upgraded. When/if you upgrade udev/hal you may also see message to purge hotplug--a normal thing too.
When I upgraded to Etch the process was made easier by upgrading xorg and kernel 1st. Then rest of dist-upgrade went smoothly. Good luck. |
Well.now my Sarge 3.1 is updated to udev 0.084-4bpo1.and hal is removed already.am waiting for a HAL backported for Sarge.:rolleyes:
|
hal/udev in sarge
deepclutch, good to here but be careful with how many backports you use. The more you use the more likely you are to break system because of dependency problems. Enjoy!
|
Thanks.but I use apt-pinning.only few backports am using like linux-image,gimp etc.
here's my /etc/apt/preferences: Code:
Package: *Code:
apt-get -t sarge-backports foobar |
| All times are GMT -5. The time now is 12:55 PM. |