On Mon, Dec 12, 2022 at 7:57 AM Jiri Slaby <jslaby@suse.cz> wrote:
On 12. 12. 22, 13:51, Thorsten Kukuk wrote:
On Mon, Dec 12, Jiri Slaby wrote:
On 12. 12. 22, 11:46, Thorsten Kukuk wrote:
The move from wicked to NetworkManager as default for everything during the last months revealed some (welcomed) side effects: since several weeks sysconfig-netconfig is no longer installed on a fresh default installation.
\o/ and thanks for the effort.
Last time (3 weeks ago) I uninstalled sysconfig-netconfig, the system (VM) didn't come up. I am using NM on all my systems. Let me retry.
None of my systems have sysconfig-netconfig installed anymore. But if you did confgure your system with /etc/sysconfig/network/ifcfg-* files, then you need netconfig, else NetworkManager is not able to read that network configuration.
As I wrote, it's NM-only: # ll /etc/sysconfig/network/ifcfg* -rw-r--r-- 1 root root 21738 Aug 31 15:21 /etc/sysconfig/network/ifcfg.template
A few years ago, Jakob and I had looked into tweaking the ifcfg plugin so that it could handle SUSE ifcfg flavored files in addition to the Red Hat ones. My early experiments in just changing it to read the SUSE path seemed to bear fruit, but seemingly nobody was interested then. On the RH/Fedora side, we dropped ifcfg in favor of using plain NM keyfiles a couple of years ago[1]. As part of that, I believe a migrator tool was in the works. I've CC'd Thomas Haller, who worked on the change in Fedora. Thomas, did that migrator tool get written? If so, could we trivially extend it to be able to read SUSE-flavored files too? [1]: https://fedoraproject.org/wiki/Changes/NetworkManager_keyfile_instead_of_ifc... -- 真実はいつも一つ！/ Always, there's only one truth!