Interesting. Looks like perhaps your boot loader isn’t properly pointing at your root partition.

I’m assuming you’ve just done the install and never successfully booted, yes? In that case, you can try to re-run the installer, or try rescue mode and try repairing the bootloader.

Are you doing dual-booting, or is this system dedicated to Linux?

Yes, back in the early 00s. We toyed with making a net-bootable image with it for our computer labs, but it was really not practical. It definitely taught me a ton about systems, though.

I admit, I’m not a big fan of putting more functionality into systemd (or just of systemd in general), but that is a well-reasoned argument for having sudo live in the init system.

“No lawful way…”

I just finished saving backups of the games I bought using my (hackable) Switch, and I’m planning on setting it up w/ Yuzu on my Steam Deck.

And no one’s going to stop me from fairly using my stuff.

I read the man page, but I didn’t see the answer to your question in there.

I am assuming that it would only dump the root filesystem in your example. Other mounted filesystems like /home or /media, if they’re separate filesystems, probably aren’t included. You’d have to run a separate dump for each one.

Best option to find out is to try it and see what happens. No better way to learn than by doing.

Read the error again. It’s journalctl.

PowerShell makes that a lot better these days. It’s still not perfect, but a lot better.

It’s not that it’s deleted automatically. If you define deleting as “not being referenced by the file system,” then it’s deleted as soon as it’s unlinked.

Fun story - create a big file, and hold it open in an application. Unlink the file. Then compare the output of du and df for the mount point the file was on. It will differ until the app closes and the inode of the file is finally freed.