Closed ruizlenato closed 3 weeks ago
[root@redstar ~]# systemctl
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
...
systemd-firstboot.service loaded activating start start First Boot Wizard
...
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
137 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
I found this, it's probably the cause of the problem.
Hi, I'm really sorry for the late reply, been busy. I will take a look at this in a few days. This problem would likely traceback to wsl itself rather than the distro.
A solution here: Ubuntu 22.04 with systemd can't start.
create symbolic /usr/sbin/init -> /lib/systemd/systemd
See if it works for your Arch distro.
Closing this issue due to inactivity by the OP.
When I enable systemd on Arch Linux in the official way, here's an example:
It crashes and won't start, I executed a systemd-analyze to see what's going on and it returned this:
If you want to know which services are running, here they are: