• 0 Posts
  • 25 Comments
Joined 2 months ago
cake
Cake day: February 10th, 2025

help-circle








  • Timeshift is a good piece of software doing a tired trick.

    The new hotness is copy on write file systems and snapshots. I can snapshot, instantly, then do a system update and revert to the previous snapshot also instantly.

    Instead of using symlinks files, like Timeshift, the filesystem is keeping track of things at the block level.

    If you update a block it writes a new copy of the block (copy on write). The old copy is still there and will be overwritten unless it is part of a snapshot. Since the block is already written, snapshots don’t require any data to be copied so they’re instant.

    Once you finish the system update, all of the overwritten blocks are still there (part of the snapshot) and reverting is also just a filesystem operation, theres no mass data to be copied and so it is also instant.

    It does use disk space, as allocated blocks AND snapshotted blocks are stored. It uses less than Timeshift though, since Timeshift copies the entire file when it changes

    ZFS and btrfs are the ones to use.






  • It doesn’t stop cheating, it just makes cheating require spending a few hundred dollars and dealing with complex hardware setups. This means that relatively few people try.

    Non-kernel anti-cheat can be bypassed by software. So it’s cheap and easily available.

    That’s the only difference. Kernel anti-cheat doesn’t prevent cheating, it just makes it more expensive.


  • Developers who use kernel anti-cheat don’t support Linux because userspace anti-cheat is largely pointless. It doesn’t matter if you personally don’t care, the companies that want anti-cheat do care.

    The workaround for kernel anti-cheat requires hundreds of USD in hardware. The workaround for userspace anti-cheat is entirely software.

    Because of this, you will have less cheaters if cheating has a $500 price tag. That’s why kernel anti-cheat is effective, there’s no way for that to be solved with a WINE patch.





  • 75C is fine, the CPU will throttle in order to avoid max temps. This isn’t something that should cause instability.

    It’s POSSIBLE that this is a bug that’s fixed with a microcode update, see here for installing it: https://wiki.archlinux.org/title/Microcode

    TL;DR:

    1. Install amd-ucode
    2. Edit /etc/mkinitcpio.conf, add microcode after autodetect
    3. sudo mkinitcpio -P
    4. reboot

    If that doesn’t fix it, and it crashes in Windows too, it may be a hardware problem. There isn’t much you need to do in order to get a CPU working.