[OE-core] [PATCH v4] connman: ignore the networking device which nfs for rootfs is working on

Iorga, Cristian cristian.iorga at intel.com
Tue Oct 22 14:37:35 UTC 2013


Sorry to ask, what is this case: 'ip=dhcp'?
Care to clarify?

-----Original Message-----
From: openembedded-core-bounces at lists.openembedded.org [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf Of Enrico Scholz
Sent: Friday, October 18, 2013 3:48 PM
To: openembedded-core at lists.openembedded.org
Subject: Re: [OE-core] [PATCH v4] connman: ignore the networking device which nfs for rootfs is working on

"Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w at 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
_______________________________________________
Openembedded-core mailing list
Openembedded-core at lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core



More information about the Openembedded-core mailing list