Re: Not-so-predictable network names

On Thu, 2016-08-04 at 22:20 +0200, Thomas Lange wrote: [...] > I'm not sure if the kernel version or systemd or both are responsible > for this. You may want to try a 4.x kernel from backports inside the > nfsroot. Here's how to install the 4.x kernel inside the nfsroot: >

Re: Not-so-predictable network names

> On Thu, 4 Aug 2016 17:09:58 +0200, Alexander Thomas > said: > I now have the same problem while installing xenial from a jessie > NFSroot. It defines an interface eth0 in /etc/network/interfaces, but > when the installed system boots, the

Re: Not-so-predictable network names

On Thu, 2016-08-04 at 17:09 +0200, Alexander Thomas wrote: [...] > Although it feels dirty and unreliable and I don't know why I need to > use SLOT here instead of PATH, it worked fine, at first. When I try to > install a VM with a virtio network interface, it breaks. In that case, >

Re: Not-so-predictable network names

Network naming has been troublesome for a bit. If you want to keep the classic names, your boot string needs to contain: net.ifnames=0 biosdevname=0 On Thu, Aug 4, 2016 at 10:09 AM, Alexander Thomas < alexander.tho...@esaturnus.com> wrote: > There was a discussion titled “example network

Not-so-predictable network names

There was a discussion titled “example network script will misname interface if installing stretch” just a few weeks ago. It ended with: Thomas Lange wrote: > > Using jessie as the base os to install stretch. > > 30-interface will setup /etc/network/interfaces with > > something like eth0, and if