71c75a5ea0
Configuring the network interface with DHCP via /etc/network/interfaces generally does not work when NFS booting. The DHCP configuration will initially bring the interface down and system then hangs at that point as the root filesystem is no longer accessable. This adds a script to be run via a pre-up line in /etc/network/interfaces. It checks for a NFS root filesystem and if the interface to be configured is used for access to the NFS server. If this is the case, then it returns a failure code so that ifup will not configure the interface. This works for DHCP and another config methods (static, bootp, etc.). This system does detect if the interface to be configured isn't the one used for NFS and doesn't skip it when that is the case. NFS filesystems that aren't the root fs aren't considered. Fixes bug #4790. Signed-off-by: Trent Piepho <tpiepho@kymetacorp.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
21 lines
846 B
Bash
Executable File
21 lines
846 B
Bash
Executable File
#!/bin/sh
|
|
|
|
# This allows NFS booting to work while also being able to configure
|
|
# the network interface via DHCP when not NFS booting. Otherwise, a
|
|
# NFS booted system will likely hang during DHCP configuration.
|
|
|
|
# Attempting to configure the network interface used for NFS will
|
|
# initially bring that network down. Since the root filesystem is
|
|
# accessed over this network, the system hangs.
|
|
|
|
# This script is run by ifup and will attempt to detect if a NFS root
|
|
# mount uses the interface to be configured (IFACE), and if so does
|
|
# not configure it. This should allow the same build to be disk/flash
|
|
# booted or NFS booted.
|
|
|
|
nfsip=`sed -n '/^[^ ]*:.* \/ nfs.*[ ,]addr=\([0-9.]\+\).*/s//\1/p' /proc/mounts`
|
|
if [ -n "$nfsip" ] && ip route get to "$nfsip" | grep -q "dev $IFACE"; then
|
|
echo Skipping $IFACE, used for NFS from $nfsip
|
|
exit 1
|
|
fi
|