From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Connman and rootfs over NFS
Date: Mon, 26 Oct 2009 23:08:52 +0100 [thread overview]
Message-ID: <hc56lk$h83$2@ger.gmane.org> (raw)
In-Reply-To: <1256592782.7623.3.camel@utx.utx.cz>
On 26-10-09 22:33, Stanislav Brabec wrote:
> Enric Balletbò i Serra wrote:
>> Hi all,
>>
>> Running my Angstrom image and mounting the rootfs over NFS seems that
>> the connman package reconfigures the network interface (nfs: server
>> 192.168.2.6 not responding, still trying). There are any way to
>> prevent this ?
>
> I see very similar problem with Bluetooth networking (BNEP) and openvpn.
> Connman steals the device when it goes up and mis-configures it.
>
> I use a work-around - stopping or not starting the connman daemon.
You can also edit /var/lib/conmmand/<if>.conf and set policy to manual
(the GUI can also do that for you).
regards,
Koen
prev parent reply other threads:[~2009-10-26 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 12:47 Connman and rootfs over NFS Enric Balletbò i Serra
2009-10-26 21:33 ` Stanislav Brabec
2009-10-26 22:08 ` Koen Kooi [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='hc56lk$h83$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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