From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Iorga\, Cristian" <cristian.iorga@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v4] connman: ignore the networking device which nfs for rootfs is working on
Date: Tue, 22 Oct 2013 17:13:28 +0200 [thread overview]
Message-ID: <lytxg9cp9j.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB16CA102D@IRSMSX105.ger.corp.intel.com> (Cristian Iorga's message of "Tue, 22 Oct 2013 15:00:28 +0000")
"Iorga, Cristian" <cristian.iorga@intel.com> writes:
> I might be wrong, but I fail to see how this relates to our situation.
> Care to elaborate?
The provisining works only when static ips are configured. Using connman
in dhcp setup will do all the bad things which were tried to be fixed by
the provisioning (bringing down interface, clearing default route).
Ideally, provisioning mechanism would be extended so that connman uses
dhcp by requesting current ip and without reconfiguring the interface
(neither on startup, nor on shutdown).
But for now, only solution seems to ignore the netwrok interface which
is done by the patch.
Enrico
prev parent reply other threads:[~2013-10-22 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 8:12 [PATCH v4] connman: ignore the networking device which nfs for rootfs is working on rongqing.li
2013-10-18 8:57 ` Koen Kooi
2013-10-18 9:03 ` Rongqing Li
2013-10-18 11:17 ` Burton, Ross
2013-10-18 12:47 ` Enrico Scholz
2013-10-22 14:37 ` Iorga, Cristian
2013-10-22 14:54 ` Enrico Scholz
2013-10-22 15:00 ` Iorga, Cristian
2013-10-22 15:13 ` Enrico Scholz [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=lytxg9cp9j.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=cristian.iorga@intel.com \
--cc=openembedded-core@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