

I don’t think there’s any effective difference between timeshift and snapper. They’re both essentially just GUIs for features supported by the underlying btrfs filesystem.
Timeshift backup to another disk, is just rsync.
Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.
Introverted, yet I enjoy discussion to a fault.
I don’t think there’s any effective difference between timeshift and snapper. They’re both essentially just GUIs for features supported by the underlying btrfs filesystem.
Timeshift backup to another disk, is just rsync.
Sure.
But there’s no program that just creates a handy partition image. You’ll have to get into the weeds of how your filesystem actually works.
I haven’t found anything that is quite like Macrium. Mostly, because something that works the same way is a bad idea on linux. Because as you suspect, an image backup cannot be done while the partition being imaged is live.
Macrium creates restorable images of your entire boot partition or disk, as-is, which can then be restored onto the same, or an entirely different, disk.
This isn’t really something you can do in linux, with a system that is live. Hence, partition images should be done offline, when the given partition isn’t booted.
That said, everything that matters can be backed up simply by copying the relevant files. For this, I use Kopia.
As for making sure you always have a bootable system, for this I use Timeshift on btrfs.
For MS office, you might try winapps. Sounds like what you’re hoping for.
That is what xrandr allows you to do on X11, create and set display modes that aren’t reported by the monitor.
EDID editing is basically replacing the data reported by the monitor, which also allows you to add display modes it doesn’t report itself. This is the only way to do what you are looking for on wayland.
You can either switch to X11, and use xrandr, or create an EDID file with the display mode you want, and have it load on boot. Doing that is unfortunately not simple.
Are you referring to monitor refresh rate overclocking?
This would not be something you do with a kernel launch option, or DE setting.
You need to be doing stuff with the display server, which would be X11 or Wayland.
This might be a case of Xorg vs Wayland.
Are you trying to use XClicker (which is an X11 application), while running Wayland?
That is bound to cause wierdness.
Yep.
Once an encrypted storage volume is mounted and in use, you just transfer stuff into and out of it like normal.
There’s nothing unusual about the files themselves.
I recently switched to Kopia for my offsite backup solution.
It’s apparently one of the faster options, and it can be set up so that the files of the differential backups are handled by a repository server on the offsite end, so file management doesn’t need to happen over the network at a snails pace.
The result is a way to maintain frequent full backups of my nextcloud instance, with almost no downtime.
Nextcloud only goes into maintenance mode for the duration of a postgres database dump, after which the actual file system backup occurs using a temporary btrfs snapshot, containing a frozen filesystem at the time of the database dump.
You wont get windows in Grub, but since you’re using separate drives, you can boot each one by just setting the boot drive in BIOS.
You can also look up how to add windows later, once you have fedora working and re-enable the drive with windows.
This should be sufficient. Go for it.
This is why you get a prenup saying you keep the lego.
Yes.
If your keyboard is RGB, you could even color-code your F-keys according to what they do.
I’ve had the steam overlay bound to shift+f12 for years, for this exact reason.
Also, framedata and system usage overlay toggle on shift+f9, obs recording on shift+f11, and linux terminal on shift+f10.
Is it actually being used?
My guess it just doesn’t evict stuff from before the suspend, starts re-loading stuff after the resume, which makes the apparent amount “used” go up.
On a normal linux system, “free” RAM will over time drop down to zero, as the kernel puts the extra memory available to use. But it doesn’t mean there isn’t room to evict less-needed stuff if necessary.
AFAIK linux only starts actively evicting RAM once it fills up.
Like the other guy mentioned, drill down and see if you can find the actual program causing the problem.