• 3 Posts
  • 251 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle
  • The thing that annoys me the most is how it cares about whitespace/carriage returns. I remember back in college when I was taking a CS class, learning Python and writing the Code on a Windows PC, emailing it to myself, and then attempting to run the code on Linux. Before I learned about the carriage return conversions, I remember having to rewrite about 75 lines of code before I got it to run. 🤬








  • Linux is so lean, it will run on practically anything. Windows, on the other hand, became an increasingly bloated sack of crap post-XP when they attempted to solve “DLL Hell” by keeping multiple versions of the same driver. The installation size went from 5 GB in XP to around 20 GB on 7, now I think a Windows 10 or 11 I install requires around 150 GB for the recovery partition, system partition, and other garbage.

    It always amazes/disgusts me that on a fresh install of Windows 10 there’s like 50-75 services running and like 6-8 GB of RAM already in use.






  • Threadripper already accomplished all of this years ago. My TR2970WX has 24 cores/48 threads, 48 PCI-E lanes, and it supports ECC and non-ECC RAM. My AsRock Rack board has BMC support as well.

    The Threadripper series was the perfect workstation CPU. I’ve had mine for a few years and it can handle anything I throw at it, it can easily transcode 2-3 4K videos while doing multiple other things.

    It wasn’t cheap though, it was like $650 on sale, originally like a grand or so.




  • Q1: No it shouldn’t matter as long as you didn’t import the pool using device names (sda, sdb, etc…). If you’re using labels or UUIDs (the better option for portability sake). If they do happen to use device names, just export the pool and then reimport it on the same system using labels or UUIDs.

    Q2: It should work just fine assuming you’re not using device names for your pools

    Q3: it’s just as robust as FreeBSD’s implementation. Once again, see the answer to Q1.

    Q4: IMO virtualizing your NAS just adds more headaches and performance overhead compared to running it on bare metal.

    Out of my years running TrueNAS on and off, I’ve always had issues with it when doing anything other than using it purely as a storage box. I tried 24.04 a few weeks ago, thinking that most of the issues I had originally when SCALE was launched would be resolved. They weren’t. So I went back to Arch w/OpenZFS…again