> Am 05.01.2022 um 15:05 schrieb Ben Cotton <bcotton@xxxxxxxxxx>: > > https://fedoraproject.org/wiki/Changes/NoIfcfgFiles > > == Summary == > Do not not include NetworkManager support for legacy network > configuration files by in new installations. > > …… > == Scope == > * Proposal owners: Split the ifcfg plugin into a subpackage package. > Make sure the ifcfg plugin stays on upgrades. Provide a migration > tool. > > ... > == Documentation == > We'll need to write the documentation for the migration tool. > Perhaps also something the sysadmins wondering why their ifcfg files > don't work anymore could find and refer to. > A big ++ for that. It is overdue. However, as members of the Server WG, I wonder how many administration tools, scripts and Ansible playbooks will need to be rewritten. We would need to have a test case as soon as possible and communicate that very actively in the sysadmin community. Otherwise, the surprise could be quite big. The migration tool comes a bit short in the proposal. I consider it an indispensable prerequisite for this change. From my own unfortunate experience - I have had to make this change manually on our servers without a migration tool and without dedicated documentation - how tedious and time-consuming such an action is. And while I can't help with a migration tool, I can offer help for documentation, just in case there's a shortage of hands. And may be, we should be prepared to postpone the change to F37 but provide the migration tool and doc with F36. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
