From: Markus Kaindl <markus.kaindl@stusta.mhn.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fresh install and problem with net.* init.d script
Date: Fri, 26 Jul 2013 21:59:50 +0200 [thread overview]
Message-ID: <51F2D536.7060809@stusta.mhn.de> (raw)
In-Reply-To: <81cd8b64fd20f43855a535a449411a58@drakonix.fr>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
Am 22.07.2013 23:35, schrieb FredL:
>>
>> 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...
>
> Saying that I've just remenbered that I have selected the desktop
> profile instead of the default one, can this be why my init script need
> dbus for starting net iface?
>
As Bruce did show: You don't need to have dbus installed for net.* to
work. Also it did work, when you started net.* it manually, without
having dbus installed, right?
I don't know, what did start dhcp on your interfaces, you should check
that. AFAIK your kernel does a automatic dhcp-configuration of your
interfaces when you have set CONFIG_IP_PNP_DHCP. You could try to
disable dbus and check, if your interfaces get up with dhcp again and
then disable CONFIG_IP_PNP or all CONFIG_IP_PNP_*-options and check
again. (If they where activated of course ;) )
For your net.* initscripts not starting automatically I don't have an
idea other than maybe you forgot to add them to the runlevels right now,
but that would not explain, why they do start after adding dbus...
It would be interesting, to know, what did really happen, so please let
us know, what you find out ;)
Regards,
Markus
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
prev parent reply other threads:[~2013-07-26 20:00 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
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 ` Markus Kaindl [this message]
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=51F2D536.7060809@stusta.mhn.de \
--to=markus.kaindl@stusta.mhn.de \
--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