Bruce Marshall wrote:
Well the discussion got me curious and as I said in a previous mail, I had shut down haldaemon as an experiment.
So I thought to myself.... why not boot the server and see what happens, But first lets disable HAL so it won't come up at boot time.
Nope.... here's where you can see what shutting down HAL does....
All you have to do is to go into YAST2--> System services and try to disable HAL. You will get a dialog which tells you what other services must also be shut down because they depend on HAL. Many, many, of which network, fetchmail, vsftpd, named, cron, xinetd, ssh, dhcpd .... ad nauseum....
Interesting experiment - I'm getting tempted to do one myself. I do wonder where those dependencies came from though - if you check for init scripts dependent on 'haldaemon' - which is what hald provides - only 'powersaved', 'sane-dev' and 'network' have such a dependency. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com