Re: script to execute after reboot

What I do is to run an fai softupdate via a line in cron upon reboot. @REBOOT root fai --class=POSTINSTALL softupdate Kind of nice to do an FAI softupdate after every reboot -- especially the 1st one after the initial install. Over the years, I've moved more and more stuff into the post

Re: Interface Naming inside nfsroot

Hey Thomas, thanks for your reply. I've tried the new "30-interface" from github, but it doesn't work for Ubuntu 16.04. This script found eno1628 as interface name, but after the installation of Ubuntu 16.04 the name changed to "ens32": ubuntu:~# udevadm info /sys/class/net/ens32 P:

script to execute after reboot

Hi, I have a script with some commands that should be executed on first reboot after installation only. Now I could put a call to it into rc.local and delete it afterwards, but I’m sure I have seen a more elegant solution directly with FAI. Could someone point my nose to the right direction?

AW: Interface Naming inside nfsroot

Hello Dennis, we also had to change things like order and name of our network devices, which we solved using a udev rule. You cound write a role which changes to name from ens160[...] to eth0 and so on. Details can be found under

Re: Interface Naming inside nfsroot

> On Tue, 14 Mar 2017 11:21:27 +0100, Dennis Steinmann > said: > When I boot the installed systems (CentOS 7 or Ubuntu 16.04), I have > eno16777984 (CentOS 7) or ens160 (Ubuntu) instead of eth0. Have a look at the new code in DEBIAN/30-interfaces

Interface Naming inside nfsroot

Hi there, I'm using FAI 5.0.3 on an Ubuntu 16.04 machine with a Debian 8 nfsroot. My problem is to setup the interface for the installed system correctly. When I boot the nfsroot, all interfaces named eth[0-9]*. The variable "$NIC1" is also set to eth0. The script "30-interface" is doing this: