Bug#1003835: udev: XEN domU: Guest RX stalled, unreachable due to nw device naming change
Michael Biebl
biebl at debian.org
Mon Jan 17 16:33:43 GMT 2022
Am 17.01.22 um 08:20 schrieb Michael Biebl:
> Am 17.01.22 um 08:15 schrieb Michael Biebl:
>> I don't think we want to get into the business of mangling other
>> packages configuration files (which would be a policy violation
>> anyway). Also keep in mind that ifupdown is by no means the only
>> network configuration scheme.
>>
>> At most we could let postinst generate a warning message.
>> That said, I have no idea if such a script would be feasible and how
>> reliable the detection would be.
>> I'm happy to take suggestions how this could be implemented.
>> Even better, if you have an idea, please submit a MR.
>
> Another alternative could be to add a udev.NEWS entry.
I'm tossing out another idea:
debian-installer, when installing the system initially, could write a
config for grub which appends net.naming-scheme=<version of systemd the
system was installed with>
So, once the system is installed, the net-naming-scheme would no longer
change.
Haven't yet made up my mind, whether this is a good idea or not.
Would welcome feedback!
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220117/18666f25/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list