From: Saul Wold <sgw@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] connman: Ignore eth0 cleanup when booting over the network
Date: Fri, 31 Aug 2012 09:48:42 -0700 [thread overview]
Message-ID: <5040EAEA.7050000@linux.intel.com> (raw)
In-Reply-To: <A19E8B5D-4A0F-439C-B67C-8CBB0CE84E16@dominion.thruhere.net>
On 08/31/2012 12:28 AM, Koen Kooi wrote:
>
> Op 31 aug. 2012, om 01:34 heeft Saul Wold <sgw@linux.intel.com> het volgende geschreven:
>
>> There was a change to connman, such that it cleans up the
>> route table for devices at startup, this was causing the
>> network to get lost and NFS to loose it connection.
>>
>> The -I option will cause the device to be ignored.
>
> Apart from the missing PR bump, what happens when you don't boot of the network? Will connman keep ignoring eth0?
> FWIW I asked about nfsroot and connman and Marcel said: don't do that! So I'm inclined to say that if you're using nfsroot you shouldn't be using connman.
>
What if there are multiple network interfaces, but just one (eth0, usb0,
...) is the nfsroot provider?
Is there a way to determine which interface nfs is active on and only
ignore that one?
I am going to disable connmand for now in a v2 patch, but I think we
need to address this better either via connman or here in oe-core.
Sau!
next prev parent reply other threads:[~2012-08-31 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 23:34 [PATCH] connman: Ignore eth0 cleanup when booting over the network Saul Wold
2012-08-31 7:28 ` Koen Kooi
2012-08-31 16:48 ` Saul Wold [this message]
2012-08-31 7:42 ` Simon Busch
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=5040EAEA.7050000@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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