Grml should use Predictable Network Interface Names

[jkirk]

This is a follow up of grml/grml-debootstrap#126:

Debian/stretch and later already use Predictable Network Interface Names. We should start doing so too.

This issue should coordinate the implications of this change. For instance, will grml-network still work? Any other Grml-Tools affected by this change?

[jkirk]

JFTR: Removing net.ifnames=0 leads to the following ip a output (when running Grml in VirtualBox with NAT network):

root@grml ~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:45:a8:0c brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic enp0s3
       valid_lft 86319sec preferred_lft 86319sec
    inet6 fe80::a00:27ff:fe45:a80c/64 scope link 
       valid_lft forever preferred_lft forever

[jkirk]

Tested grml-network with "Use DHCP broadcast" and with static IP address. Both worked fine.

[jkirk]

We also need to test grml-terminalserver.

[jkirk]

We could add a boot menu item which starts Grml without net.ifnames=0. This makes life easier to test our tools. Once everything works well we could change the default boot configuration.