On Dec 1, 2016, at 10:29 , David Woodhouse
On Wed, 2016-11-30 at 20:59 +0200, Pantelis Antoniou wrote:
> Until now for root NFS you either had to manually blacklist
> the interface or disable connman all together
> This patch automatically blacklists the interface the NFS server
> is reachable from and populates the resolver entries that the
> DHCP server provided on startup.
> It is now possible to use a vanilla rootfs tarball without
> having to manually edit connman configuration entries.
That looks like it supports Legacy IP only. Is that also true of the
kernel's built-in nfsroot support, or did that get brought into the
21st century? And part of the *reason* for not updating the old nfsroot
support in the kernel is that it can be done from an initramfs....
should we attempt to handle that case too?
In-kernel support is IPv4 as far as I know so that’s why this is
IPv4 only. It is not hard to add IPv6 support.
When using initram rootnfs and rootnfs? I haven’t tried it but it should
be possible to detect that your root is on an NFS share. All you need is
to find out the server ip and the same method to find the interface to
Personally I dislike using initramfs on embedded systems because a) uses up
memory for not a particularly valid reason b) slows down boot and c) on
an embedded system you have a pretty good chance of booting directly without
needing to load non-free drivers from initramfs. Unfortunately most PC based
distros seem to use it :)
If someone wants to do it, please go ahead ;)