If there's a process for this that's already established in some Meta question, I couldn't find it either through searching or in the "Similar questions" list, but I'd welcome a "Duplicate" pointer if it can answer the question.
There are a sizeable number (upwards of 35 by my count) of questions where the root cause (or occasionally an ancillary cause) is the lack of systemd support in Windows Subsystem for Linux. Now that might make it a general-computing issue (and it sometimes is), but there are also a number of questions where:
- The root cause is lack of systemd support
- The question is (IMHO) on-topic (unique to programming, e.g. installation of code-server)
- There are non-systemd solutions available.
But yesterday, Microsoft released a new preview version of WSL that supports systemd. Pretty much every one of those 35+ questions I have found could be answered with a new answer that says something like:
With yesterday's preview release of WSL 0.67.6, it is now possible to run systemd under WSL2. With this enabled, you should be able to do (x from question) without any other workarounds.
This feature does require Windows 11, so those using WSL on Windows 10 should continue to use the workarounds from the other answer(s) here.
Some of these questions could certainly be closed as off-topic or duplicates. However, since there's been no activity on them in some time, I can't take them to SOCVR. From past history, they are unlikely to get the votes-to-close since WSL is a low-volume tag where close-votes typically expire before action.
I'd love to avoid having 35+ questions updated with (essentially) the same answer somehow, but what's the right way to handle this type of situation?