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 yiu can find the actual program causing the problem.

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 actaully 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.

You mention timeshift, did you restore to the working snapshot after selecting it in grub, then reboot AGAIN?

Booting a snapshot, does not restore from it. When booting a snapshot from grub, you need to open timeshift, restore the snapshot, then boot up a second time (this time without selecting it in grub).

Otherwise, you didn’t really restore it, you just booted into it, and if you re-attempted the broken update, messed the snapshot up, too (leaving you with no working snapshot to go back to).

He’s kinda grown up with his audience. I dropped out of watching as I hit adulthood, then tuned back in for his “meme review” phase, where the inside joke was that everyone watching was a nine-year-old, when in reality he already had an aging audience.

He eventually grew bored with the format (and at that point already he made it clear he was doing it for fun, not because he needed to). The view counts steadily trended downwards as he switched to making videos he wanted to make, instead of ones that made money, as he was set by then.

At some point he ran a book-club style format, because he wanted to get into reading more. At least some portion of the fanbase was into that, but at that point he lost a lot of viewership.

Nowadays he seems to post very infrequently, and it seems to mostly be vlog-style content about family life and living in Japan.

The integrated GPU in your processor is not an additional bit of computing power your computer is not using, but special software that can use your processor to put out graphics if a dedicated GPU is missing. It is extremely inferior at processing graphics compared to the real dedicated GPU, and if you were running firefox to watch (Not decode) youtube, you would very likely see things like screen tearing as the processor struggled to keep up.

This is straight up wrong. You are confusing GPUs with display adapters.

iGPUs are an actual on-die GPU, consiting of their own hardware, present on the die in addition to the CPU.

They can game. They can hardware decode and encode media, etc. They are full GPUs. Some are even quite powerful, though usually you’ll find them to be designed for everyday use and only light gaming.

The GPU in every recent game console is technically an iGPU, same goes for phones, and the Steamdeck.

They do not “translate” GPU instructions into running on the CPU cores.

That’s software rendering, and is what CPUs do when there isn’t an iGPU at all. (Though they’ll still need a display adapter, which a GPU can act as. But a display adapter doesn’t need to be a full on GPU. And iGPUs aren’t just display adapters.)

There is.

You can add a taskbar icon for KDE night color. Clicking it opens a panel with a toggle, and quick acess to the full settings page. It should be in the config for the taskbar icon applet.

KDE also lets you set it to specific times if you want, maybe it didn’t use to?

KDE has similar functionality built-in. (Called night color, you can find it in display settings, and add a control icon in the taskbar).

If Linus genuinely went off the rails, the kernel would just get forked. Even right now, if the way the mainline project is run doesn’t work for someone or what they are doing, that can and does happen.

Linus has power because the people who contribute to the project allow it, and they allow it because over the years he has consistently endeavoured to make decisions based on what is in the best interest of the project. People want him in charge, because he has done, and keeps doing, a really good job.

He hasn’t always been nice to deal with, and he can get spicy when he puts his foot down, but whem he does, its not on a whim. And if he’s wrong, and you can articulate why and how, in good faith, he won’t ignore the logic of what you are saying out of some childish sense of pride.

Yup. And it’ll be a huge improvement overall to simply have both performance and accuracy in one, and not have to pick one or the other, regardless of what application is being run.

fsync isn’t part of wine, which is what they are referring to.

Fsync and Esync are both inaccurate representations, and while they help performance in many places (particularly games), they break other things. Hence, while useful, they never got mainlined.

NTsync is an accurate reimplementation, hence why this functionality will finally become part of wine proper.

then what’s the advantage of using that over the native capabilities of btrfs?

btrfs multi device file systems have some limitations. Adding a drive is instant, but if you want to stripe the data using raid0, that requires a lengthy balancing operation. The alternative is “single” mode, which does not concern itself with striping, and just pools the storage available. The disadvantage, is that in single mode you get the risk of raid0, with no performance benefit. btrfs does not actually make sure that the different blocks that constitute a single file end up on the same drive, which means that if one fails, you still likely lose everything.

MergerFS does not mess with any of the filesystems being combined. It can be configured to work in different ways, but each drive will remain its own, consistent, functioning file system. Drives can be browsed individually, removed, added etc. Instantly. To “empty” a drive, you just move the files on it to the rest by using the non merged folders. By default, “writing” a new file will always go to the drive with the most free space, and individual files cannot be stored “across” several drives even though the contents of a folder can be. This way, whatever is on each drive, can never be damaged by the failure of another drive.

So the benefits are isolation, and convenience. The downside is a definite performance hit, which may not be significant depending on your system or what you’re storing in the merged filesystem.

So I could do that for the root folder as well I imagine?

No. And you wouldn’t want to. First for the performance hit. Second, because mergerfs merges folders (drives have to be mounted, first), and uses a third as a mountpoint. As an example, to “expand” your home folder, you’d move your homefolder somewhere else, then merge that moved folder with the new drive (which you still have to mount somewhere), and then you’d mount the resulting file system where your old home folder was before.

You could even have two folders on the second drive. Use one to merge somewhere you want to pool all your storage, and the other to put stuff on the second drive in a way where losing the first won’t make half the files go missing. You might use that to store a copy of the OS install on the first drive, for example.