On Thursday 23 April 2009 20:31:45 Andrei Thorp wrote:

"When HAL initializes it will check for the presence of D-Bus and load it automatically. If you have dbus in your list of daemons, remove it, since it can cause problems."

-AT

Just out of curiosity, does anyone know what problems could arise? Kind regards, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855)

Alright. Perhaps if we're in agreement on this point, it should be removed from the wiki that this can "cause problems". Honestly, I'm not sure what these problems could be, I was just going as per advice. Regardless, nice to keep my DAEMONS list a bit shorter. Cheers, -AT On Thu, Apr 23, 2009 at 3:43 PM, Jan de Groot <jan@jgc.homeip.net> wrote:

On Thu, 2009-04-23 at 21:37 +0200, Bram Schoenmakers wrote:

...

On Thursday 23 April 2009 20:31:45 Andrei Thorp wrote:

...

"When HAL initializes it will check for the presence of D-Bus and load it automatically. If you have dbus in your list of daemons, remove it, since it can cause problems."

-AT

Just out of curiosity, does anyone know what problems could arise?

Kind regards,

There is no problem putting dbus in the DAEMONS array, as long as it's started before hal it's fine. This "start dbus" logic was added to hal because users didn't put dbus in rc.conf and reported bugs about "hal not working". Hal won't start dbus when it's already running.

Very cool :) Cheers. -AT On Thu, Apr 23, 2009 at 11:28 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:

Andrei Thorp wrote:

...

Alright. Perhaps if we're in agreement on this point, it should be removed from the wiki that this can "cause problems". Honestly, I'm not sure what these problems could be, I was just going as per advice. Regardless, nice to keep my DAEMONS list a bit shorter.

Cheers,

-AT

       Well, it's confirmed that hal must check for dbus and with dbus before hal in the DAEMONS list there are no apparent problems because I have done it both ways in the past 24 hours with no visible problems. However, I have removed dbus from the DAEMONS list per AT's suggestion, and it works like a champ that way as well.

       Thanks again for the tip on backgrounding the processes in the DAEMONS list. DAEMONS=(syslog-ng network hal @sshd @crond @avahi-daemon @mysqld @samba @sensors kdm3) works fantastic. Boot time is the best I have seen out of any distro.

-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

I think I might have mentioned this to you before, but if you think your boot speed is fast compared with SUSE now, put some @s in front of some of the things in your boot process. Try: DAEMONS=(syslog-ng network hal @sshd @crond @avahi-daemon @mysqld @samba @sensors kdm3) Note: - I removed netfs -- do you need mounting of network filesystems in your boot process? - I removed dbus -- as I said several posts back, you shouldn't have both hal and dbus, since hal starts dbus. - the @ signs will background processes. I asked it to start your log, network, hal, and kdm3 normally. I don't think the ordering of anything else particularly matters here, so I put @ signs in front of them. This will probably make your boot time about half of what it is now. Cheers. -AT On Thu, Apr 23, 2009 at 11:46 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:

Bram Schoenmakers wrote:

...

On Thursday 23 April 2009 19:29:30 David C. Rankin wrote:

Hello David,

...

I thought I was ready to rock and roll, but when I grabbed the mouse - it didn't move?? Then I tried typing my pw, and no characters (or dots) appeared? The I tried ctrl+alt+backspace to kill X -- no joy. Then ctrl+alt+F1, still no joy.

     OK, ssh into box and kill kdm, back to normal login. Now I'm scratching my head on what to check to get my mouse and keyboard back? Any ideas?

...

From Xorg.0.log, this is obviously the problem:

(==) ModulePath set to "/usr/lib/xorg/modules" (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Keyboard0 (WW) Disabling Mouse0

     Huh? They must have been there a minute ago what gives?

     I wonder how they got started last time?

Make sure to start D-Bus and HAL before you start KDM. In rc.conf:

DAEMONS=( ... dbus hal kdm ... )

Kind regards,

Ahah!

[13:38 archangel:/etc] # cat rc.conf | grep -E DAEMONS\|MODULES # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist. # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array. MODULES=(dm_mod dm_mirror sata_sil nvidia) # DAEMONS DAEMONS=(syslog-ng network netfs sshd crond avahi-daemon mysqld samba sensors kdm3)

       I swear I put them in there! Where did they go? Somebody must have typed ':q' instead of ':wq' on the last trip into rc.conf. What idiot could that have been? Fixed now:

[13:43 archangel:/etc] # cat rc.conf | grep DAEMONS # DAEMONS DAEMONS=(syslog-ng network netfs sshd crond dbus hal avahi-daemon mysqld samba sensors kdm3)

       I'll give kde another go and report back. Thanks Bram.

       Also, if you see anything wrong with the daemon loading order, please let me know. I'm just putting things in a order I think is logical (that doesn't really mean the order 'is' actually logical;-)

-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com