SystemD not in github-downloaded AppBundle?

[elegos]

Is your feature request related to a problem? Please describe.
I read that since Fedora remix 35, it should support SystemD as a separate launch configuration. I've just (re)installed fedoraremix 37 and I don't have such option, nor I have the possibility to start at launch it in the app's advanced settings.

Describe the solution you'd like
I'd like the SystemD variant to be in place

Describe alternatives you've considered
Any way to start systemd in any way?

Additional context
Fedora-Remix-for-WSL-SL_37.0.4.0_x64_arm64.msixbundle

Thanks

[crramirez]

Hello @elegos,

The version published here on GitHub doesn't have this option. To start systemd with your version run from the command-line: fedoraremix -s

Also if you have the wsl from the store, you can use the Microsoft own implementation. Check it with wsl --version from the command line. If it returns a version number, you can use the Microsoft one. Please follow these steps: https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/

Best Regards

[elegos]

Thank you @crramirez !
I resolved by using wsl's "native" systemd. Is there any practical difference between wsl's and fedora remix's?

Also when Fedora 38 will come out, will it always be valid the rule that systemd has to be shut down before upgrade, whatever the implementation?

Thanks :)

[crramirez]

The practical difference is that the included in fedoraremix you can start it on demand. It is useful to start a daemon with systemd but everything else you work well without systemd. Also you don't need to completely shutdown the distro to start systemd.

The Microsoft one is like a permanent one. You need to make a change in a file and fully shutdown the distro. But the Microsoft one is more compatible with WSLg and newer improvements that Microsoft makes to WSL.

Eventually we will stop distributing the systemd feature in Fedora Remix, when incompatibilities begin to appear.

For now Fedora Remix 38 is planned to behave as 37 regarding systemd

[crramirez]

OK I didn't understand well the question. Yes, shutdown systemd for the upgrade. And I think that the newer the version is, more imperative is to disable it.

Fedora upgrades in two fases. And it really upgrades upon restart with SystemD. But the one in WSL or built in won't start this task and the system will become inoperable.