LaggyKar

If you’re running Wine on a case-sensitive file system, and you it tries to open a file, it would first try to open a file whose case matches exactly. But if it doesn’t find one, it would then need to list all the files in the directory, normalize their case, and go through them all to see if there is a file with the given name but in a different case. That can take some time if there is a lot of files in the directory.

But if you’re on a case-insensitive filesystem, the FS can keep case-normalized names of all files on disk, so you can do a case-insensitive open just as fast as you can do a case-sensitive open.

BTW, another application that can benefit from this is Samba, since SMB is case-insensitive.

It does, but having case insensitivity in the file system can get you better performance.

It isn’t normally, but it, like e.g. Ext4, allows case insensitivity mostly for the sake of Wine.

Kobo store, Google Play Books, and various other places (here in Sweden for example we have Bokus and Adlibris) have Epub downloads. Usually with Adobe Digital Editions DRM (which you can get rid of pretty easily with DeDRM, or alternatively Kobo tablets support Digital Editions), but some books are sold DRM free, or with LCP DRM which I don’t have experience with. Something I’ve noticed at least on Bokus is that many books in Swedish are sold as DRM free Epubs with watermarks, even if they’re translated from an English version which is sold with DRM on the same store, though that’s probably not relevant for people in other regions.

It’s not a daemon

Yes, it says so in the first paragraph

One thing that you do still need root for however is proper backups. The built-in backup system is tied to Google, and it’s very limited in what it will back up, nowhere near what you can do with root backup software like Titanium Backup.

A normal copy consists of a program reading from one file and writing to another. There is no way for the filesystem to do a reflink in that case, it just sees that the program is reading and writing stuff. In order to do a reflink, the program must tell the filesystem what data should be “copied” to where using FICLONE or FICLONERANGE. Though some programs will do that by default if possible nowadays when copying files or when moving files between different subvolumes on the same partition, including the Coreutils cp, mv and install commands and some GUI file managers.

Yes, using KDE Connect, which has had this functionality for ages. Though you’re best off using the F-Droid version since Google has severely limited the Play Store version using SAF. Seems like they’ve they’ve given Microsoft a pass here even though they’ve blocked KDE Connect from doing the exact same thing for years.

Apparently so it does, and it says “HDMI Freesync” rather than “HDMI [2.1] VRR”. FreeSync HDMI is a completely different protocol and is supposed to work under Linux. Found a thread here, can you try cat /sys/kernel/debug/dri/0/HDMI-A-1/vrr_range and edid-decode < /sys/class/drm/card0-HDMI-A-1/edid? Though there is no solution there.

I thought that there was VRR support over HDMI even for versions below 2.1 spec.

Yes, there is FreeSync HDMI, which is supposed to be supported on Linux, and which is unrelated to HDMI 2.1 VRR. Don’t see anything about the monitor supporting that though (LG 24GS60F based on your previous post). Nor anything about HDMI 2.1 VRR, it probably only supports VRR via DisplayPort Adaptive Sync.

You can have a physical SIM alongside an eSIM. These days you may have to have at least one of them be an eSIM, as many phones only have one physical SIM slot.

It’s better in one way, in that updates are applied on reboot rather than pulling the rug put from under running applications. But I agree that it doesn’t go all the way, as it doesn’t provide a verifiable base system with clearly separated modifications. OSTree would be great.

Another possibility would be to distribute a base image as a btrfs send stream (possibly differential against previous versions) containing a compose-fs image and associated files. And then OS extensions could be installed with systemd-sysext.

Figured I’d do the math on the power required.

In the article, they show a iPhone 15 Pro, which has a 3274 mAh battery, so let’s go with that. Assuming a 3.7 V battery and a 1 minute charging time, that’s 3274 mAh × 3.7 V / 1 min ≈ 727 W.

I used to use it, but then I switched to MPV, as it works a lot better with hardware acceleration. MPV supports more methods for hardware decoding (e.g. nvdec), and also MPV will keep the frames in VRAM when doing hardware decoding, and do additional processing and presentation using the GPU, while VLC copies everything back to system RAM and processes the frame on the CPU.

At the time I switched hardware decoding with copy-back would actually result in twice the CPU usage compared to software decoding, but that was a long time ago. Also, I would get tearing in VLC and not in MPV.

You’re right, that might work

That requires root

Oops, I misread, that was a different monitor

So it’s not really a 4K 1000Hz screen then, if it’s just togglable between being a 4k 240 Hz screen and a 1080p 1000 Hz screen.

What’s the difference between significantly and extensively?