❦ 13 juillet 2017 13:55 -0700, Russ Allbery <r...@debian.org> : >>> The workaround was a bunch of bullshit in our install process to try to >>> figure out which NIC got the DHCP response and then pin that one to >>> eth0 for subsequent boots. (Which is basically what udev persistent >>> naming did.) > >> At least when you netboot there's a protocol supported by PXELINUX to >> pass a BOOTIF= option to the kernel with the MAC address of the NIC that >> performed the PXE boot. And d-i is supposed to then DHCP on that >> particular interface. But if that all is properly persisted onto the >> final system without intervention, that I don't know[1]. > > Yeah, we were using FAI, but I believe that's the basic mechanism we were > using and then found a way to use it to generate the udev rule to do > persistent naming.
This is a perfect use case for the new udev. It would have provided you with reproducible names on your fleet of hosts without any tweaking. -- Parenthesise to avoid ambiguity. - The Elements of Programming Style (Kernighan & Plauger)
signature.asc
Description: PGP signature