On 08/26/2014 08:28 PM, Russell King - ARM Linux wrote:
Now take a target booting using DHCP in uboot, which then mounts its root NFS. If it tries to startup a DHCP client, the first thing the DHCP client does is to clean up the interface... resulting in it killing the root NFS connection. If that doesn't happen, then you end up with a problem at shutdown, because DHCP clients always deconfigure the interface when they're killed off - resulting in "reboot" not being functional. Here, I run exactly that setup, and I have found that ubuntu suffers quite a bit from problems if you don't tell it to keep its fingers off the ethernet device configuration when running root-NFS
When you do an iSCSI boot on x86, the network boot firmware passes the interface and IP information to the OS as well (stored in the iBFT along with the iSCSI connection information), and that generally does work out-of-the-box. Guess major Linux distributions have special handling for that in their networking scripts.
Don't see why they couldn't have the same for NFS, if the way of passing along the IP information and indicating which network interface should require the special handling was standardized.
Yours sincerely, Floris Bos -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
