From: Simon Busch <morphis@gravedo.de>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] connman: Ignore eth0 cleanup when booting over the network
Date: Fri, 31 Aug 2012 09:42:27 +0200 [thread overview]
Message-ID: <50406AE3.1020208@gravedo.de> (raw)
In-Reply-To: <1346369662-17265-1-git-send-email-sgw@linux.intel.com>
Am 31.08.2012 01:34, schrieb Saul Wold:
> 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.
>
> [YOCTO #3008]
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/recipes-connectivity/connman/connman/connman | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-connectivity/connman/connman/connman b/meta/recipes-connectivity/connman/connman/connman
> index f01bf37..2c8354a 100644
> --- a/meta/recipes-connectivity/connman/connman/connman
> +++ b/meta/recipes-connectivity/connman/connman/connman
> @@ -29,7 +29,7 @@ done
> do_start() {
> EXTRA_PARAM=""
> if test $nfsroot -eq 1 ; then
> - EXTRA_PARAM="-P ethernet"
> + EXTRA_PARAM="-P ethernet -I eth0"
> fi
> $DAEMON $EXTRA_PARAM
> }
>
What about other devices where eht0 is not available but rndis0 for
example which has to be ignored?
As of right we have this fix for several machines in meta-smartphone
already ignoring rndis0 and usb0.
regards,
Simon
--
Simon Busch - http://mm.gravedo.de/blog/
prev parent reply other threads:[~2012-08-31 8:02 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
2012-08-31 7:42 ` Simon Busch [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=50406AE3.1020208@gravedo.de \
--to=morphis@gravedo.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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