IMO what you are looking here are: a) unhelpful ifupdown log messages, and b) a misconfiguration of ifupdown.
On Fri, Feb 21, 2025 at 02:25:31PM +0100, Vincent Lefevre wrote: > Fri Aug 22 02:38:44 2008: Configuring network interfaces...eth0: error > fetching interface information: Device not found > Fri Aug 22 02:38:47 2008: Ignoring unknown interface eth0=eth0. > Fri Aug 22 02:38:48 2008: if-up.d/mountnfs[eth1]: waiting for interface eth0 > before doing NFS mounts (warning). > ^^^^ ^^^^ I can easily reproduce this: | Configuring network interfaces...dhcpcd-10.1.0 starting | DUID 00:01:00:01:2f:4b:41:48:46:52:1b:b9:8f:26 | eth0: interface not found | ifup: failed to bring up eth0 | enp0s1: waiting for carrier [..] | if-up.d/mountnfs[enp0s1]: waiting for interface eth0 before doing NFS mounts ... (warning). | failed. | Cleaning up temporary files.... And I think this is mostly correct for this configuration: | # cat /etc/network/interfaces | auto eth0 | iface eth0 inet dhcp | | auto enp0s1 | iface enp0s1 inet dhcp ... which is just a broken configuration for the machine in question. I believe mountnfs does its job correctly. Chris
