On Friday, 23 November 2018 10:06:30 CET Rémy Dernat wrote:
> Hi Steffen,
>
> That is weird; this should work even for pure debian.
>
> However, reading my message, I saw that some parts of my scripts are
> useless. Maybe you can try the following instead (just replacing $NIC1 by
> $iface which
Hi Steffen,
That is weird; this should work even for pure debian.
However, reading my message, I saw that some parts of my scripts are
useless. Maybe you can try the following instead (just replacing $NIC1 by
$iface which is not used) :
```
#! /bin/bash
iface=`ip -o -f inet addr show |awk '$2
On Thu, 2018-11-22 at 12:18:52 +0100, Rémy Dernat wrote:
> Ok; replying to myself. I found the solution.
>
> I just created a script for my BIONIC64 class (using the debian script) :
>
> ```
> #! /bin/bash
>
> iface=`ip -o -f inet addr show |awk '$2 !~ "lo|docker" {print $2;exit;}'`
> mac=`ip
dy too late to get hold of the old-style if names) - during a
>> half-hearted
>> test, the grub cmdline trick did not work for me.
>>
>> What still makes me curious is
>>
>> > > What I still haven't found is which magic FAI uses to avoid the
>> r
akes me curious is
>
> > > What I still haven't found is which magic FAI uses to avoid the
> renaming
> > > to "predictable network interface names" (a term that's completely
> misleading
> > > to me as I'm unable to predict the network names if I'm given
ic FAI uses to avoid the renaming
> > to "predictable network interface names" (a term that's completely
> > misleading
> > to me as I'm unable to predict the network names if I'm given a brand-new
> > machine). Thomas, can you shed some light on this?
If I run
n't work,
> udev does its job reliably outside of FAI.
> What I still haven't found is which magic FAI uses to avoid the renaming
> to "predictable network interface names" (a term that's completely misleading
> to me as I'm unable to predict the network names if I'm given a
Have a look at this script
https://github.com/faiproject/fai-config/blob/master/scripts/DEBIAN/30-interface
Does this help you?
--
regards Thomas
rk,
> udev does its job reliably outside of FAI.
> What I still haven't found is which magic FAI uses to avoid the renaming
> to "predictable network interface names" (a term that's completely misleading
> to me as I'm unable to predict the network names if I'm given a brand-
en't found is which magic FAI uses to avoid the renaming
to "predictable network interface names" (a term that's completely misleading
to me as I'm unable to predict the network names if I'm given a brand-new
machine). Thomas, can you shed some light on this?
My plan is to read the (old-st
> On Thu, 23 Aug 2018 09:44:00 +0200, Alexander Bugl
> said:
> P.S.: I use some more (minor) modifications for 30-interface, probably
> you like to apply the attached patch?
Thanks for your patch. It's now applied.
--
regards Thomas
Hi Thomas!
> > # less /var/log/fai/localhost/last/shell.log
> > = shell: DEBIAN/30-interface =
> > Device "ens192" does not exist.
> > DEBIAN/30-interface OK.
> I wonder which command prints the 'Device does not exist'
> message. Oh I see. It's this call:
> ip -o -f
> On Wed, 22 Aug 2018 16:54:59 +0200, Alexander Bugl
> said:
> # less /var/log/fai/localhost/last/shell.log
> = shell: DEBIAN/30-interface =
> Device "ens192" does not exist.
> DEBIAN/30-interface OK.
I wonder which command prints the 'Device does not exist'
Hi,
I currently have a problem with FAI version 5.3.6 directly from stretch
regarding Predictable Network Interface Names:
When I boot a VM to be installed I get eth0 as network interface name:
# grep eth0 /var/log/fai/localhost/last/dmesg.log
[0.990874] vmxnet3 :0b:00.0 eth0: NIC Link
14 matches
Mail list logo
