• 0 Posts
  • 334 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle



  • There is certainly a very big amount of fuckery going on right now with nvidia drivers.

    “Right now” meaning every year for the past decade or two.

    It’s always something with Nvidia drivers. Performance+stability is more the exception than the rule.

    That said, AMD drivers have a bad rep too. Personally I’ve had zero issues since I switched to AMD but experiences seen to vary a lot from what I’ve read.

    Before that, I don’t think I ever got through a full year without at least one weekend lost to troubleshooting Nvidia bullshit. CUDA is a pain in the ass even on Windows.


  • Also, people’s goals change and “secure” means something different.

    When I was making half as much as I am now, I felt fairly secure. I could pay my rent, I had no credit card debt, and I had a few months’ worth of savings. Money was not a day-to-day worry. Most of my peers were in debt and/or living paycheck-to-paycheck so I felt like I was living large.

    Now I am objectively more secure but I feel less secure because I am thinking about retirement, childcare, college funds, and elder care. I have nowhere near enough savings to retire in the foreseeable future. I honestly don’t know if I’ll ever get there.





  • I’m a software developer first and a gamer second. Being a “gaming” distro does not detract from anything else, really. It just means that getting proper GPU acceleration is easy, and you’re likely to want that for development too. That was actually why I chose Bazzite. I was tired of wrestling with CUDA and ROCm.

    It’s not “gaming” vs “developing”. That’s a false dichotomy.

    The real choice is immutable vs traditional. And I’ll admit, immutable distros have a big learning curve. But it forces you to learn techniques that will make your life easier no matter where you go. The time I spent wrestling with dependencies on Debian or Ubuntu or OpenSuse just because I didn’t know about Distrobox…

    Unless your needs are very narrow and unchanging, you’re likely to run into something that’s a giant pain in the ass no matter which distro you choose. I used to use Ubuntu LTSR so I could install a few big things in easy mode, but it made everything else harder because it was so outdated. Switched to OpenSuse Tumbleweed and everything was modern but those few vendors don’t support it so I had to wrestle with dependencies.

    The answer to this problem is Distrobox. It’s the answer on Ubuntu, it’s the answer on OpenSuse, and it’s the answer on Bazzite. I’m never going back to dependency hell because I can just run everything the environment it is specifically designed for.

    If you’re wondering “should I use distro X, Y, or Z”, the answer is simply “yes”. :D


  • On bazzite, your search order for apps/packages should be something like:

    1. Flathub
    2. ujust. This is more for general configs than specific apps, but take a look at what it offers.
    3. Homebrew
    4. Distrobox
    5. Podman/Docker images
    6. rpm-ostree

    rpm-ostree is a last resort because it compromises the “atomic” principle of the system, but in a pinch it will give you access to anything you could get with dnf on a regular Fedora install.

    Don’t sleep on Distrobox. I have a Debian box so I can run Signal from its official repo and install Geany with both GUI and CLI support. Once you export applications from distrobox they behave like first-class citizens within your desktop.

    I strongly recommend trying Distrobox. If you instead hop distros, you’re going to find yourself in a similar situation eventually, where something is unreasonably difficult. That’s why Distrobox exists; so you can get the best of all worlds.









  • Thanks for posting the solution!

    If you happen to be using a BTRFS or XFS file system, you might want to try duperemove. It will help you reclaim usable disk space without deleting any files, by using those filesystems’ built-in support for data deduplication and copy-on-write. In other words, it will make duplicate files point to the same data on disk, but still work as individual files. Files will appear and function exactly the same, and editing one copy will not change another (unlike with hard links, for example). That way it won’t interfere with cases like Flatpak or Python virtual environments where you really need multiple copies of the same files.


  • Generally speaking, xz provides higher compression.

    None of these are well optimized for images. Depending on your image format, you might be better off leaving those files alone or converting them to a more modern format like JPEG-XL. Supposedly JPEG-XL can further compress JPEG files with no additional loss of quality, and it also has an efficient lossless mode.

    Do any of them have the ability to recover from a bit flip or at the very least detect with certainty whether the data is corrupted or not when extracting?

    As far as I know, no common compression algorithms feature built-in error correction, nor does tar. This is something you can do with external tools, instead.

    For validation, you can save a hash of the compressed output. md5 is a bad hashing algorithm but it’s still generally fine (and widely used) for this purpose. SHA256 is much more robust if you are worried about dedicated malicious forgery, and not just random corruption.

    Usually, you’d just put hash files alongside your archive files with appropriate names, so you can manually check them later. Note that this will not provide you with information about which parts of the archive are corrupt, only that it is corrupt.

    For error correction, consider par2. Same idea: you give it a file, and it creates a secondary file that can be used alongside the original for error correction later.

    I also want the files to be extractable with just the Linux/Unix standard binutils

    That is a key advantage of this method. Adding a hash file or par file does not change the basic archive, so you don’t need any special tools to work with it.

    You should also consider your file system and media. Some file systems offer built-in error correction. And some media types are less susceptible to corruption than others, either due to physical durability or to baked-in error correction.