LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   2 Quick Questions Hal vs. Udev (http://www.linuxquestions.org/questions/slackware-14/2-quick-questions-hal-vs-udev-4175481333/)

NightSky 10-18-2013 04:04 PM

2 Quick Questions Hal vs. Udev
 
First, do you have to:
Code:


chmod +x /etc/rc.d/rc.udev
/etc/rc.d/rc.udev restart

Reason I ask is because during boot process there is always a message that says "udev trigger" failed? So I'm thinking udev has to be activated like 'Messagebus' & 'HAL' did after a fresh install of Slackware 13.37. 'Don't have CDs for 14"

Second question maybe I don't even need 'HAL' in 13.37 if I'm only installing XFCE? (I know, I'm behind the curve ;)

andrewthomas 10-19-2013 05:33 AM

Quote:

Originally Posted by NightSky (Post 5048299)

Second question maybe I don't even need 'HAL' in 13.37 if I'm only installing XFCE? (I know, I'm behind the curve ;)

Hal has not been needed since the move to KDE 4.6 and Xfce 4.8.

Quote:

Originally Posted by Thunar-volman and the deprecation of HAL in Xfce
Until now, volume management (monitoring and mounting) in Xfce was done through HAL, the hardware abstraction layer that is currently being deprecated and dropped by major distributions. The functionality previously provided by HAL has been moved into udev, udisks (formerly known as DeviceKit-disks) and upower (formerly known as DeviceKit-power).

http://gezeiten.org/post/2010/01/Thu...ecation-of-HAL

the3dfxdude 10-21-2013 09:12 PM

HAL is required in XFCE for Slackware 13.37 to have a fully functional desktop.

ReaperX7 10-21-2013 09:37 PM

HAL is also still needed for Adobe Flash for Digital Rights Management support.

Oddly enough, if you have certain software packages like xf86-input-vmmouse and some others, they can still be built against the exist HAL for fdi and callout support methods. Not sure how that support works, but it's there.

If you run FreeBSD, HAL is still part of devd's extended support matrix for hardware devices.

NightSky 10-22-2013 11:56 AM

My gratitude & greetings to everyone for your input.
I don't have the newest XFCE or KDE ...tried downloading after 3 days of >reget slackware64-14.0-install-dvd.iso it was corruptedd Wish I could just buy it from slackware store.

First question is do i chmod +x /etc/rc.d/rc.udev and restart it like HALD & Messagebus as part of the "Initial Post Install" of a fresh install?

hpfeil 10-22-2013 01:01 PM

HAL is started in /etc/rc.d/rc.M if /etc/rc.d/rc.hald is executable.

business_kid 10-22-2013 01:21 PM

I found I needed hal for the adobe flash plugin to serve certain content (My local TV station). Flash uses hal to get some lib or other.

ReaperX7 10-22-2013 08:22 PM

There are several patches available floating around that patch HAL for building against modern kernels. I think someone posted a few links in here somewhere, so a quick search should turn them up.

I've built HAL myself on LFS and it's used alongside udev. It's purpose might be deprecated, but deprecated doesn't mean useless.

andrewthomas 10-22-2013 08:37 PM

I know that I have not had hal on my Gentoo system for a couple of years. Udisks/upower and solid seem to be doing the work. I also turned hald off in Slackware once I began using Alienbob's ktown with udisks/upower.

the3dfxdude 10-23-2013 07:25 PM

Quote:

Originally Posted by NightSky (Post 5050432)
First question is do i chmod +x /etc/rc.d/rc.udev and restart it like HALD & Messagebus as part of the "Initial Post Install" of a fresh install?

I don't believe you are getting an answer to your question here. I don't really understand your question myself, so I have held back on answering. When you install slackware, /etc/rc.d/rc.udev should already be executable. So when you get to booting, it should already be loaded. Check with

ps aux|grep udev

As far as the udev message you got, I'm not sure what that is, but it may be solved in a later version of slackware. I think you can probably ignore it if udev, hal, and dbus are running otherwise okay.

catkin 10-24-2013 09:56 AM

Quote:

Originally Posted by NightSky (Post 5048299)
Reason I ask is because during boot process there is always a message that says "udev trigger" failed?

If the message is Triggering udev events: /sbin/udevadm trigger --type=failed then it is normal. It is generated by /etc/rc.d/rc.udev which is called by /etc/rc.d/rc.M.

IIRC Slackware 14.0 does not generate the same message.

NightSky 11-03-2013 01:13 AM

Thank you the3dfxdude, catkin... for answering my questions. s The answer is rc.udev does not have to be made executable and started after a fresh install like hald. I appreciate everyone's input everyone provided lots of useful info.


All times are GMT -5. The time now is 06:08 PM.