From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rc-update add hald default or boot?
Date: Mon, 13 Apr 2009 18:43:47 -0700 [thread overview]
Message-ID: <5bdc1c8b0904131843t4af14a67ve1a5c95deea234e8@mail.gmail.com> (raw)
In-Reply-To: <49E3DB68.7060403@kutulu.org>
On Mon, Apr 13, 2009 at 5:40 PM, Mike Edenfield <kutulu@kutulu.org> wrote:
> Mark Knecht wrote:
>>
>> Hi,
>> I've wondered for a while whether the design intention of hald was
>> to be run at boot time or as a default level process? Googling for
>
> It's intended that you'll be running it at the default level. Hal requires
> D-BUS, which means it needs to be run at the earliest after your local
> mounts, clock, etc. are started. If you put them both into the boot
> runlevel I don't see why it would necessarily hurt, but it doesn't need to
> be there to work properly.
>
> --Mike
>
>
Thanks for the responses guys. I've always had it at default also. I
was just wondering.
Now, does hald need dbus? Require dbus? Interesting. I have dbus
installed but it's not running because it caused the Jack sound server
problems. Not even sure what it does or why I should need it but it
caused more problems for me and I couldn't tell what it helped with.
When should dbus be started if I run it? As a boot level process or
default also?
Thanks,
Mark
next prev parent reply other threads:[~2009-04-14 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 0:00 [gentoo-user] rc-update add hald default or boot? Mark Knecht
2009-04-14 0:23 ` Paul Hartman
2009-04-14 0:40 ` Mike Edenfield
2009-04-14 1:43 ` Mark Knecht [this message]
2009-04-14 6:47 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0904131843t4af14a67ve1a5c95deea234e8@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox