WSL VS dnf

I have found some documentation here https://github.com/MicrosoftDocs/WSL/issues/536 and here https://learn.microsoft.com/en-us/windows/wsl/faq#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware--or-VirtualBox and intend to read them fully including the links inside them tomorrow or the day after when I have time.

Off the top of my head was this bug that caused a lot of people using vbox to swap to vmware. Just a bunch of really annoying compatibility bugs that made it a nightmare if you were trying to use it like a native linux instance.

>and I’m almost certain that when you run multiple wsl distros they are all in one VM, though that may be wrong

Yes, they run as containers.

From https://github.com/MicrosoftDocs/WSL/issues/1573#issuecommen...:

WSL distributions (instances) are not VMs. They are best described as "containers" running inside the WSL2 VM. Each WSL2 distribution/instance has its own isolated:

PID namespace

(As I've understood, Hyper-V Management Tools should not be needed when using WSL2, based on: https://github.com/MicrosoftDocs/WSL/issues/899)

Here https://github.com/MicrosoftDocs/WSL/issues/536

I just use dnf-makecache.service to handle background metadata syncs. Just modify the dnf-makecache.timer to manage when these occur.

https://github.com/rpm-software-management/dnf/pull/1879

However its o my going to work on rhel 10 or anything that has very very up to date DNF version.

Sure. Raise a bug report. Asking nicely on Reddit isn't going to make it happen.

I'm not sure, I'm not a dnf developer. It was implemented in C++, so it would probably have to be done differently in version 4. I belive dnf development is focused on version 5 right now, so adding features to version 4 is probably not a high priority. It would be nice to see it in version 4 so it could be added to current versions of RHEL and Fedora, but time is a finite resource. Perhaps you could implement and send a pull request, or at least file a bug to discuss it upstream?

dnf uses python only for command line functionality. Its core part, libdnf, is written in C++. However yes, dnf in my experience is still significantly slower than apt and pacman.

Lots of people use python apps and not know about it. I don't get where the idea that it's complicated comes from. You run them the same way as everything else. For example if you use anything redhat-based you're running a python app (https://github.com/rpm-software-management/dnf). If you're running any desktop environment, you're likely using at least one python app or something with python scripting embedded.

Of course they also changed the default fedora dnf.conf to make it include best=False, so there was no change, except users can simply delete this line in dnf.conf to enable best.