From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4] connman: ignore the networking device which nfs for rootfs is working on
Date: Fri, 18 Oct 2013 14:47:57 +0200 [thread overview]
Message-ID: <ly7gdawxs2.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAJTo0LZBVxwoUufz4dbpaCXoV4x3x+S_q3NYowGsjstXHDs=tQ@mail.gmail.com> (Ross Burton's message of "Fri, 18 Oct 2013 12:17:22 +0100")
"Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:
> Can you explain why connman needs to ignore the device that NFS is
> reading the rootfs from? I ask because the very latest connman
> release shouldn't be dropping and re-configuring interfaces if there's
> a provisioned configuration for them (see connman-conf, which does
> this for all qemu machines) and that configuration matches the current
> configuration. Would this be sufficient for the rootfs-on-NFS
> situation?
not really... the provisioning stuff does not seem to work for the
'ip=dhcp' case.
I know that this case is not handled well with this patch either (it
misses renewal of dhcp leases, setup of dns + ntp). But it is still
better than actual behavior.
On first glance, the do-not-cleanup patch in connman seems to cover
system startup only. I might miss something, but afais, interface will
be still shut down in the middle of reboot which is bad because '/' is
needed nearly to the end of shutdown.
Enrico
next prev parent reply other threads:[~2013-10-18 12:48 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 [this message]
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
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=ly7gdawxs2.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--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