On 18 January 2018 at 03:28, David Demelier <markand@xxxxxxxxxxxx> wrote: > Hello all, > > Since systemd-networkd is a mature network system daemon nowadays, > NetworkManager can be avoided in many cases where people do not need > desktop features. > > I propose to remove NetworkManager from the “Core” group and mark it as > optional or eventually move it into a dedicated group. Perhaps “Common > NetworkManager Submodules”? > > What do you think? > If you are looking for a change in Fedora 28, then that train has left the station as this would be a large change. For a Fedora 29 change it is possible to look at if a lot of code is written to allow all the existing systems to 'upgrade' smoothly and a user can configure their system cleanly with it. That is a lot of work and would need to land in 7-9 months to be seen as a viable attempt. That means you need to start working on this for probably Fedora 30. 1. Identify the legacy software which is looking for methods that NetworkManager had to implement. [Yes they are from the 90's.. no they aren't going away.] 2. Identify the methods to get them to work with systemd-network 3. Identify the various items which come up a lot for required needs. NetworkManager had to do a TON of backfill which took many many many releases to implement. This was because Linux gets used in a LOT of different methods and those are still expected to work. Everything from routing to infiniband to various failover routing, etc. [Going over the old 2009-2015 time frame of "why can't NetworkManager be default yet?" would be useful.] 4. Make sure there is a configuration tool which can deal with a majority of those. It doesn't need to be 100%.. NetworkManager finally took over when it was probably 80% coverage. 5. Realize that you are going to spend at least N releases with NetworkManager as a copilot. 6. Deal with a lot of backlash and whipping over every little network problem being now linked with your tool. The original NetworkManager people were quite surprised that they would get blamed for DNS problems in Australia causing routing problems in EU.. but it happens a lot. They worked through that and pushed it through. That is probably a 1000 kilometer high window of what it will take to get it into most OS's (except for Arch). > -- > David > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
