Post B4MJK2ZjGchdzR1PcW by mwl@io.mwl.io
(DIR) More posts by mwl@io.mwl.io
(DIR) Post #B4MDoeNUgORuCAVlyK by mwl@io.mwl.io
0 likes, 1 repeats
Ah, Debian. Add a disk and you yet again renumber your network interfaces. #sysadmin :flan_molotov: :flan_cleaver: :flan_executioner: :flan_reaper:
(DIR) Post #B4MGdQ1A2798KpOwZk by agreeable_landfall@mastodon.social
0 likes, 1 repeats
@mwl It's time we recognize that systemd never solved any problem we actually had. It needs to be yanked out by the roots.
(DIR) Post #B4MIw46bvSSJmnyAvQ by EF@bsd.cafe
0 likes, 0 repeats
@mwl there are good reliable options that are not Debian or contain systemd where network interfaces do not randomly renane themselves.
(DIR) Post #B4MJK2ZjGchdzR1PcW by mwl@io.mwl.io
0 likes, 0 repeats
@kbm0 according to debian, this is no longer supported.https://wiki.debian.org/NetworkInterfaceNamesThe Predictable Names scheme is the current thing afaict, which the wiki makes appear tortuous
(DIR) Post #B4MJd4MOr3Az1nrQfY by mirabilos@toot.mirbsd.org
0 likes, 0 repeats
@mwl boot with net.ifnames=0 (but bringing back the persistent net generator from wheezy would be the proper fix)
(DIR) Post #B4MJlGE8cOPc9Hu0Js by mirabilos@toot.mirbsd.org
0 likes, 0 repeats
@agreeable_landfall @mwl especiallynow that it’s "AI" microslop
(DIR) Post #B4Nytu5caHwnNN7PbE by kbm0@mastodon.social
0 likes, 0 repeats
@mwl I've just tried the wiki recommendation of changing the naming policy in .link files and I'd say you will probably find it more convenient than using udev rules, unless you have very specific requirements.If you just want fixed naming above all else, set the default NamePolicy to "mac" and you will get names which are unique and very stable, but a wee bit verbose.I guess this may be why they opted for the less stable PCI address as the default naming scheme, just for brevity.
(DIR) Post #B4NytuHfrTaXykl2O0 by mwl@io.mwl.io
0 likes, 0 repeats
@kbm0 that actually worked, thank you.hideous interface names are better than random ones.