The OS would crash entirely before that happens

Those bitflips are probably more likely to skip the section erroneously than waiting for the array to be sorted.

I don’t know, but I think it’s works on Wayland too. Probably something built in.

On Plasma Desktop, pressing Ctrl+Alt+ESC kills anything you click on next, instantly. There is truly nothing you can’t kill that way, even the desktop itself.

Both systemd and pulseaudio were more or less directly architected after MacOS’ design of Core Audio and launchd.

Really shows how little you actually know.

Can you tell Cron to catch up on the things that should’ve happened but didn’t because the system was off?

Good thing it’s editor agnostic so everybody can do the right thing in the end and choose nano

Clearly this is LFS (Lute From Scratch)

A regional dialect doesn’t a whole language make

Dunno, but looks at man service.unit I think)

# nano /etc/systemd/{system,user}.conf
----
DefaultTimeoutStopSec=10s

You’re welcome.

I thought we were doing NixOS this year ._.

Just enter a channel number and it will auto switch

I’d also add that, if after an accident you can “walk it off”, why should that even be relevant for policy decisions?

Yeah, that’s quite a stretch from the looks of it

I’m struggling to image who this is for

Really, the correct way would be to set the limit you want for journald. Put this into /etc/systemd/journald.conf.d/00-journal-size.conf:

[Journal]
SystemMaxUse=50M

Or something like this using a timer: systemd-run --timer-property=OnCalender=daily $COMMAND

Wouldn’t compressed logs make even more sense (they way they’re now)?

If we’re using systemd already, why not a timer?

I manually upgraded a 3rd gen i7 (2012) machine to 32GB in 2016. Doesn’t make that laptop ant less old tho.