Systemd

>systemd
>run recursive removal to clean drive
>deletes OS
>somehow touches the motherboard firmware too
>bricks it
Holy kek

Attached: 1641963018014.jpg (1447x1437, 291.77K)

Other urls found in this thread:

github.com/systemd/systemd/issues/2402
twitter.com/SFWRedditImages

>Things that didn't happen

>he doesnt know
github.com/systemd/systemd/issues/2402

That's not a systemd thing it's a UEFI thing

>UEFI mode gives the userland access to the firmware
Why would you want that?

To be able to modify EFIvars without having to boot into a recovery mode (as Windows does), as explains.

Why are you blaming systemd for UEFI being retarded? Have the Any Forums init flamewars rotted your brain?

>mount efi with write access by default
Lennart you need to kill yourself

If you think that's bad you should check how many distros mount SSDs with discard by default. Hint: it's none. /etc/fstab is the source of almost every problem that makes Linux bad for daily use unless you spend 20 hours reading up.

t. lennart

Even the guys who maintained efivarfs admitted this issue was on their end. Get some new material.

discard is yet another mount meme like noatime
you don't need more than fstrim, in fact you don't even need fstrim (OpenBSD is right)
Use ext4 with the defaults and call it a day.

>Use ext4 with the defaults and call it a day.
"the defaults" is not enabling anything that's been added since ext2

why would you care about defaults, aren't you freetards all about configuring everything?

Are you visiting from Any Forums or reddlt?

>(as Windows does)
Not since Vista. Seriously freetards, get better at making up shit.

Doesn't discard wear out the SSD faster though ? That's the only reason I set trim to cron instead of fstab

explain ?

>access to the firmware
The OS should be able to modify the boot entries.

Why? BIOS worked didn't? Why is UEFI so special?

Legacy BIOS doesn't have boot entries, it 'boots disks' as in their respective boot sector codes.