>Swap drive in computer.
>DE does not start (drops to emergency shell with no explanation).
>Look at journalctl - no useful output.
>Remember systemd - comment line in /etc/fstab
>Compiler finally boots.
Pottering deserves the guillotine.
It could keep booting or output; "drive missing or failed - press enter to continue, press C-d to enter emergency shell" - but systemd must be terrible.
>DE does not start (drops to emergency shell with no explanation).
>Look at journalctl - no useful output.
>Remember systemd - comment line in /etc/fstab
>Compiler finally boots.
Pottering deserves the guillotine.
It could keep booting or output; "drive missing or failed - press enter to continue, press C-d to enter emergency shell" - but systemd must be terrible.
Follow
+bonifartius 𒂼𒄄
@Suiseiseki the systemd people always manage to fuck up yet another thing.
bUt iT's sO gReAt, I doN't NeeD tO wRiTE sHeLLscRipTs!!!1
@bonifartius @Suiseiseki
The best thing is it uses ini style files which fucking sucks and it's one more thing to get used to on top of bash scripts, which is something any GNU+Linux user is (should be) familiar with.
The best thing is it uses ini style files which fucking sucks and it's one more thing to get used to on top of bash scripts, which is something any GNU+Linux user is (should be) familiar with.
@sally @Suiseiseki ini is ok for some things. starting services isn't amongst them.
@sally @bonifartius ini files are in fact good - but of course the way systemd does them is terrible.
@bonifartius @Suiseiseki I don't need to write shell scripts either (for the init system anyway).
GNU Shepherd can't stop winning