leyrerSystemd and I will never be friends.
Took me two hours to figure out how to get a coredump. Because systemd ...
Took me two hours to figure out how to get a coredump. Because systemd ...
BenBE@leyrer Can you provide an abstract?
@benbe there is nor core file in the working directory anymore. use coredumpctl to extract coredumps from effing systemd
(1) Enno T. Boland@leyrer It's called systemd/linux.
Dickenhobelix@leyrer I just was like "ah, old man - just use coredumpctl". But then I tried it on my Work-WSL2 and it doesn't work. Like... not at all...
(I just tried it on my personal linux machine where it works like a charm, so it's microsoft again. It's always microsoft...)
Sigh.
<writes 'debug coredumps on f*ing WSL2' onto a long list of workitems>
stodarahodan@dickenhobelix @leyrer Ohh wow, i just thought „coredumpctl, nice joke“ well, now i‘m crying…
@stodarahodan @leyrer It's actually not *that* bad. Maybe it's just stockholm syndrom, but coredumpctl is one of the rather straightforward utilities in systemd and has some nice convenience functions, e.g. launching gdb with your core by calling `coredumpctl debug`
WooShell@leyrer Systemd should have stayed within the original project outlines to become a better init system. Instead, it became a mediocre init system and usurped the places of a dozen other services, at none of which it even achieves feature parity, let alone improves anything. On the way there, it trampled over decades of well-established admin practices and conventions, with no apparent coordination between the subprojects to attempt to keep the user interface unified. Rip out, start from scratch.
Björn ❄️ Starkimarm@leyrer
systemd/GNU/Linux 🥴
systemd/GNU/Linux 🥴
kay 🖤 R.I.P. #natenom