On Wed, Sep 30, 2020 at 4:45 PM PGNet Dev <pgnet.dev@xxxxxxxxx> wrote: > > anyone else more confused? > > On 9/30/20 1:26 PM, Neal Gompa wrote: > > And like it or not, all our legacy network configuration mechanisms > > are deprecated and*will be removed eventually*. > > is plain-vanilla systemd-networkd -- no NM wrapper around it, no (in)direct dependency on systemd-resolved -- considered 'legacy'? > NetworkManager never uses networkd. But when I refer to legacy setups, I'm referring to everything related to ifcfg and legacy network-scripts. Insofar as networkd goes, I wouldn't consider it legacy, but I would also not consider it contemporary, since nobody bothered to make it useful enough to support all the cases that Wicked and NetworkManager support. > > Moreover, *all* Fedora variants use NetworkManager. *ALL* OSTree > variants, as shipped today, *MUST* use NetworkManager. > > how 'bout I turn the question around ... > > what specific steps must be done POST- F32->F32 upgrade to > > (1) not use NetworkManager > (2) not use systemd-resolved > > (3) return/preserve local configs for systemd-networkd & 'enterprise' (own resolver) DNS configs? > > ? > > > Regular Fedora is considerably more > customizable post-installation than OSTree-based variants. > > For those of us that don't live&breathe the lingo, it's not exactly clear what 'Regular Fedora' is. > Regular Fedora variants are installed via normal package management actions and have full granularity. RPM-OSTree reduces the granularity of the operating system to a singular image that you layer on top. But you cannot pull out stuff from the image. > Is there _any_ variant of Fedora that's immune now, and in the planned future, from "use NetworkManger" and (therefore) systemd-resolved? > > Iiuc, the upgrades WILL install/enable systemd-resolved; that's post-upgrade maintenance that apparently needs to be planned for -- as long as its still doable. > > If/when does that no longer remain an option? If you want to deactivate resolved and use something else, you can. If you did so prior to upgrading to F33, that will persist. Only users who didn't do anything would get the change. One of my machines uses dnsmasq and I have NetworkManager configured with that. That does not break with the move to Fedora 33, since I set it up that way. I'm sure there are people running NetworkManager with unbound, and I expect that to stay working too. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ 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
