public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: runlevels and service list
Date: Sun, 20 Sep 2009 15:18:54 +0200	[thread overview]
Message-ID: <200909201518.54815.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <1253451002.10837.123.camel@rattus>

On Sunday 20 September 2009 14:50:02 William Kenworthy wrote:
> On Sun, 2009-09-20 at 15:40 +0300, Nikos Chantziaras wrote:
> > On 09/20/2009 03:34 PM, William Kenworthy wrote:
> > > Is there a "reference" list of what services should be started in which
> > > runlevels?  I am interested in hald and dbus in particular.
> > >
> > > Googling shows mostly people set them to the default runlevel, but I
> > > would like a reference or reason ...
> >
> > The reason is that they are used by X, and since X is in the default
> > runlevel, hal and dbus go there too.
> 
> Lots of other things use them as well - not just X, so thats not a
> reason (and lots of systems that dont have X but need dbus and hal).  I
> would like to know why they are started in the default run-level, not at
> boot which seems more reasonable for low level hardware support.

It comes down to personal preference. Any service in the boot runlevel will 
always be started, unlike default or other runlevels which can be run or not 
run by user choice. There's no good reason to mandate that dbus and hal will 
*always* run.

Normally, nothing in the boot runlevel uses hal or dbus as these are userspace 
daemons used by apps that run when the system is up in its normal state. The 
primary consumer of dbus is of course the desktop. When the system is in 
single user mode for maintenance, dbus and hal will not normally be required.

If it makes you feel better, start dbus and hal in the boot runlevel by all 
means. They are normally in default because everything that uses them is in 
default.

Like I said earlier, there is no good, sane, all-encompassing reason to have 
or not have them in boot. They are not there by default because the maintainer 
probably saw no good reason to do so, and for no other reason.

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2009-09-20 13:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20 12:34 [gentoo-user] runlevels and service list William Kenworthy
2009-09-20 12:40 ` [gentoo-user] " Nikos Chantziaras
2009-09-20 12:50   ` William Kenworthy
2009-09-20 13:18     ` Alan McKinnon [this message]
2009-09-20 16:33     ` Neil Bothwick
2009-09-20 18:45       ` Philip Webb
2009-09-20 18:51         ` Nikos Chantziaras
2009-09-20 19:54           ` Neil Bothwick
2009-09-20 20:06             ` Dale
2009-09-20 20:10               ` Alan McKinnon
2009-09-20 21:51                 ` Dale
2009-09-21  0:11                   ` walt
2009-09-21  0:37                     ` Alan McKinnon
2009-09-21  0:45                       ` Dale
2009-09-21  0:40                     ` Dale
2009-09-21  2:51                       ` walt
2009-09-27  3:25                         ` Eric Martin
2009-09-27  5:00                           ` Jonathan Callen
2009-09-21 14:37                   ` [gentoo-user] " walt
2009-09-20 22:01             ` [gentoo-user] " Nikos Chantziaras
2009-09-20 23:50               ` Neil Bothwick
2009-09-21  0:41                 ` Dale

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=200909201518.54815.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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