I have been running gnome-shell with the --no-x11 flag for quite some time now and haven’t been missing anything.

use the official home.arpa as specified in RFC 8375

None

Thank you for your work on this! It’s highly appreciated!

I’m about as broke as it gets currently, but are there ways to send money your way in case someone who’s able to comes across this?

thank you for providing such a thorough reply, good shit

I try to avoid using the command line as much as possible

Why would you do that?

Wouldn’t it make more sense to focus on an open standard like RISC-V instead of ARM?

Would you mind providing some reasoning so this doesn’t come off as unsubstantiated badmouthing?

I really like Wormhole for this exact purpose.

My users home directory is ephemeral as well, so this wouldn’t happen. Everything I didn’t declare to persist is deleted on reboot.

What I do use tools like these for is verifying that my persistent storage paths are properly bind mounted and files end up in the correct filesystem.

I use dust for this, specifically with the -x flag to not traverse multiple filesystems.

selber hs °^°

My / is a tmpfs.

There is no state accumulating that I didn’t explicitly specify, exactly because I don’t want to deal with those kind of chores.

I don’t think they meant forcing themselves because their RAM would fill up, but because their stuff would be gone after rebooting if they didn’t move it.

They don’t support DNSSEC.

I meant like in general…

I do agree it’s worth investigating if it happens again. My best guess so far would be some kind of data written to a tmpfs. That’d explain it not being associated with a particular process, yet counting towards actual used RAM.

Why do you care so much about memory usage?

Unused RAM is wasted RAM.

You can use journalctl -b <index>, where 0 is the current boot session, -1 the previous boot session and so on.

You can see all sessions with journalctl --list-boots if you want to pick a specific one.

Spacebar looks promising IMO.

EteSync?

Glad to help! Just keep in mind that what you’re doing there is dumping the entire dconf settings tree and applying it as is. That will include a lot of things you don’t want/care about, including state data of certain applications. You should probably sift through the dump file and throw stuff out before loading it again, but I’m sure you’ll figure it out.