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] Fresh install and problem with net.* init.d script
Date: Mon, 22 Jul 2013 23:44:59 +0200	[thread overview]
Message-ID: <51EDA7DB.90900@gmail.com> (raw)
In-Reply-To: <81cd8b64fd20f43855a535a449411a58@drakonix.fr>

On 22/07/2013 23:35, FredL wrote:
>>
>> Do you perhaps have NetworkManager or wicd installed?
>>
>>
>> no, none of them, it is a very basic install, with only the minimum
>> packages installed . I have checked at the init script and find a line
>> in the depend section saying :
>>
>> after lo lo0 dbus
>>
>> but dbus is not yet installed, can this be the cause of my problem?
> 
> so I have just installed dbus and add it to default runlevel and my
> net.* script are loaded correctly setting my static config, so every
> thing is fine now.
> 
> But why do we need dbus in a very minimalistic system? I was thinking
> that it would be helpful in a full desktop environnement for
> automagically mounting device and things like that...



dbus is NOT a desktop daemon. This is very important, and that single
misunderstanding is probably behind all the fud you read about it.

dbus implements a message bus - an amazingly useful thing to have.

Why do you need or want a message bus?

You might as well ask why do you need or want any other form of IPC you
already have, as that is what dbus is. It's a very small, light daemon,
can run system-wide or per-session and has the potential to many of the
IPC implementations you already have. Those are the ones that don't
happen to show up in ps so you hear very little whinging about them.

That desktop systems are the main user of dbus at this point in time
doesn't change one bit what dbus is designed to do and it's usefulness.




-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2013-07-22 21:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 20:42 [gentoo-user] Fresh install and problem with net.* init.d script FredL
2013-07-22 20:54 ` Paul Hartman
2013-07-22 21:13   ` FredL
2013-07-22 21:35     ` FredL
2013-07-22 21:44       ` Alan McKinnon [this message]
2013-07-22 22:02         ` FredL
2013-07-22 22:08           ` Alan McKinnon
2013-07-22 22:45             ` FredL
2013-07-23  0:13               ` Neil Bothwick
2013-07-23  7:43                 ` FredL
2013-07-23 11:06             ` Tanstaafl
2013-07-23 12:02               ` Bruce Hill
2013-07-23 12:20               ` Yohan Pereira
2013-07-23 14:22                 ` FredL
2013-07-24  2:17         ` [gentoo-user] " Steven J. Long
2013-07-24  9:02           ` Neil Bothwick
2013-07-24  9:39             ` Alan McKinnon
2013-07-24 17:51               ` [gentoo-user] " Steven J. Long
2013-07-24 19:37                 ` Alan McKinnon
2013-07-24 20:18                   ` [gentoo-user] " Steven J. Long
2013-07-24 21:04                     ` Alan McKinnon
2013-07-27 18:28                       ` [gentoo-user] Reinventing the wheel Steven J. Long
2013-07-24 17:32             ` [gentoo-user] Re: Re: Fresh install and problem with net.* init.d script Steven J. Long
2013-07-26 19:59       ` [gentoo-user] " Markus Kaindl

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=51EDA7DB.90900@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