Nickelback

in “Russia”

Polishing up your resume and LinkedIn?

Are you okay?

They do. By default the system partition is straight up mounted read-only.

https://github.com/gerardog/gsudo

More like SudoExW

Is that… ICQ? Why?

They banned flavored pods. That’s why disposables took off. Those are banned now too, but enforcement is basically non-existent at the federal level.

besides memory leaks

Have you tried auto memory reclaim yet?

https://devblogs.microsoft.com/commandline/windows-subsystem-for-linux-september-2023-update/#:~:text=Automatic memory reclaim&text=When this is set to,you’re not using it!

Do you want to talk about it?

The customary reply is “Thanks! I’ll add it to my list”

That’s a funny way to say “Have you opened a ticket?”

https://arstechnica.com/gadgets/2023/12/linux-distros-are-about-to-get-a-killer-windows-feature-the-blue-screen-of-death/#:~:text=The systemd-bsod component is,photo or write it down.

What a great idea! They should automate something like that! Maybe they could call it System Restore?

https://www.silentinstall.org/msiexec

This is one of the issues that systemd purports to solve, and it gets nothing but flack for it.

Granted, systemd does have its flaws. But the religious war around it is unjustified.

systemctl disable systemd-critic.service

Systemd-init, the core part of systemd, offersa wide range of features surpassing other init systems. More features lead to more bugs and security vulnerabilities.

This is a bad take. Many of systemd’s features improve security significantly. And having all that code in one cohesive place can’t possibly be inherently less secure than the cornucopia of init scripts we used to use.

And if the backup was merged into existing contacts, just take a new one. Then you can purge all contacts instead of trying to sort through the broken ones.

Adversarial interoperability is not exploitative.