A Reddit Refugee. Zero ragrets.

Engineer, permanent pirate, lover of all things mechanical and on wheels

moved here from lemmy.one because there are no active admins on that instance.

  • 5 posts
  • 98 comments
Joined 3 years ago
Cake day: December 22nd, 2023
  • I’ve never ran into issues either, but generally in any situation where data integrity is somewhat important, ECC is a very good idea. Its never a problem until suddenly it is.

    I don’t give a crap about my Minecraft server having ECC, but a storage server where cached data gets written to disk, I’d rather have ECC ensure nothing gets corrupted.

  • ABSOLUTELY ECC memory, 32gb or higher if you can afford it these days as TrueNAS does benefit from a decent cache space, especially with so many drives to spread data slices across.

    Realistically unless you expect multiple concurrent users, any 4 core or higher CPU from 2015-on will be plenty of power to manage the array. No need for dedicated server hardware unless the price is right

    I have a Dell PowerEdge t3 SOHO/small business server tower that I gutted and turned into a 5x8tb config. It only has a middling 4 core Xeon 1225v5 and I never get above 50% CPU usage when maxing the drives out. More CPU is needed if you’re doing filesystem compression or need multiple concurrent users.

  • The reset button is basically just a signal to the CPU/BIOS that it should wipe memory and begin the boot process from scratch. If it was not working, that indicates the CPU was hard locked and not responding to any sort of input, not just an os fault The power button sends an actual trigger signal to the PSU through the ATX connector so it bypasses any mainboard lock.

    Random shit happens, see if it does it again.
    My go to for random stability issues is to always run a full deep memtest to look for bad RAM and then a CPU stress test to see if it’s a random thermal or core issue. More often than not I find stability problems just with these two steps.

  • Debian is what you make of it, definitely. But it is also inanely stability focused to the point of being a detriment. It takes many months for simple package updates to hit Debian repos and it leads to frustration when stuff I expect to be updated is still very much not. As a server distro I recommend it, but as a play around distro it’s a bit more annoying and you have to do a ton more self maintenance on packages to get the latest and greatest.

  • All Linux distros are roughly the same under the hood. They have a version of the Linux kernel, a service management system, a basic set of packages and preinstalled software, and some kind of UI. How those pieces are put together realistically doesn’t change much. What distro maintainers then do is update the packages and kernel and make sure they work together.

    Specific design distros like the one for scientific modelling is probably based around having a lot of data processing stuff built in. Unless they had a specially modified kernel (which is rare, but possible if they had to integrate special lab data collection hardware support), I see no reason why you couldn’t just recreate the same package structure on a modern Linux 6 kernel and have it be a spiritual successor to the original distro.

I run Debian 13 with MATE. I recently switched from the distro release to the flatpak version of FreeCAD, as the distro release is of course a few versions behind. Bear with me, as I am very new to using Flatpak or anything other than normal apt packages.

I just noticed that FreeCAD announces it is running as super user in the window title bar.

The interesting part is it doesn’t ask for privilege escalation with password entry when I launch it.

Seeing as FreeCAD never ran as SU with the distro release installed via apt, and I don’t think the program does anything that really needs SU… As much as I trust FreeCAD, this seems like a security hole I’d rather not have.

Is the Flatpak version running inside it’s own “box” and it isn’t getting SU permissions across my whole system? Or what am I missing here.