I know this is a little off-topic, but why don't we use systemd-networkd in Fedora proper as a replacement for the ifcfg scripts when NetworkManager isn't desired? Or at least provide it as an alternative option to NetworkManager and ifcfg scripts in general?
On Tue, Jun 23, 2015 at 2:34 AM, Jan Kurik <jkurik@xxxxxxxxxx> wrote:
= Proposed Self Contained Change: Cloud Systemd Networkd =
https://fedoraproject.org/wiki/Changes/Cloud_Systemd_Networkd
Change owner(s): Kushal Das <kushaldas at gmail dot com>
We will use systemd-networkd to configure network in Cloud base image.
== Detailed Description ==
systemd-networkd is a system daemon that manages network configurations. It detects and configures network devices as they appear. Cloud base image will use systemd-networkd for its network.
systemd is a default package in Fedora, and we can use its latest feature to control the network configurations. We will remove the hacks we have in the current kickstart file, and use systemd tools for network configuration.
== Scope ==
* Proposal owners: The Cloud base image.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
_______________________________________________
devel-announce mailing list
devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
真実はいつも一つ！/ Always, there's only one truth!
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
