I guess you could use Ansible to continue with the install.
Note that with WSL 2 you loose VirtualBox (unless you are on the very last Windows version)
Very good article anyway, I just finished the install. (Had to deactivate the local McAfee firewall in Windows for the network to work)
Thoughtful. Can you say more about the "rollback" part? And what sort of problems you are encountering around package updates? Which packages, specifically?
I think I like the idea. But let's say, for instance, that I want to use systemd-analyze on occasion. (I know, not useful for a non-systemd WSL, but I do maintain other systems as well.) It would seem that I shouldn't exclude systemd updates, then.
In other words, if it is not breaking anything, I could still see some advantages to keeping systemd packages up to date. Thoughts?
The update included dependencies and weak-dependencies and systemd got installed as well as systemd-networkd I guess which deleted resolv.conf ... instantly removing name resolution ... For sure systemd adds itself to /etc/dnf/protected.d/ it does not ease rolling back.
Maybe it is possible to exclude just systemd-networkd I did not try.
I guess you could use Ansible to continue with the install.
Note that with WSL 2 you loose VirtualBox (unless you are on the very last Windows version)
Very good article anyway, I just finished the install. (Had to deactivate the local McAfee firewall in Windows for the network to work)
Glad you found it helpful! Thank you.
After a first update and rollback, you might want to add:
exclude=systemd*
in /etc/dnf/dnf.conf
Thoughtful. Can you say more about the "rollback" part? And what sort of problems you are encountering around package updates? Which packages, specifically?
I think I like the idea. But let's say, for instance, that I want to use
systemd-analyzeon occasion. (I know, not useful for a non-systemd WSL, but I do maintain other systems as well.) It would seem that I shouldn't exclude systemd updates, then.In other words, if it is not breaking anything, I could still see some advantages to keeping systemd packages up to date. Thoughts?
The update included dependencies and weak-dependencies and systemd got installed as well as systemd-networkd I guess which deleted resolv.conf ... instantly removing name resolution ... For sure systemd adds itself to /etc/dnf/protected.d/ it does not ease rolling back.
Maybe it is possible to exclude just systemd-networkd I did not try.
Just curious...
systemd-networkdis still messing withresolv.confeven after anunlink /etc/resolv.confthen creating a new one?