> On Tue, 19 Jan 2021 21:00:28 +0100, Stefan Möding
> said:
> It seems the path based name is used when booting the NFSROOT while the
slot
> based name is used when the machine is rebooted after installation. To me
> that looks like a problem with the NFSROOT like missing
fai1...@macrotex.net writes:
> I am already using that patch. The problem seems to be that the altname
> returned by "ip link show eth0" in 30-interface is "enp11s0" and hence
> that is the filename what 30-network puts into /etc/network/interfaces.d, but
> when the new system boots the name in
> On Tue, 19 Jan 2021 06:57:26 -0800, fai1...@macrotex.net said:
> I am already using that patch. The problem seems to be that the altname
> returned by "ip link show eth0" in 30-interface is "enp11s0" and hence
> that is the filename what 30-network puts into
>
On 1/19/2021 1:58 AM, Thomas Lange wrote:
On Mon, 18 Jan 2021 18:23:05 +0100, Thomas Lange said:
> I found out that "udevadm trigger" is executed when doing the
> inventory but not when doing the installation.
I found out, that I've added a patch after the release of 5.9.4 which
> On Mon, 18 Jan 2021 18:23:05 +0100, Thomas Lange
> said:
> I found out that "udevadm trigger" is executed when doing the
> inventory but not when doing the installation.
I found out, that I've added a patch after the release of 5.9.4 which
tries to get the interface name if
