Solar Bear

  • 1 Post
  • 257 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle



  • Whatever you get for your NAS, make sure it’s CMR and not SMR. SMR drives do not perform well in NAS arrays.

    I just want to follow this up and stress how important it is. This isn’t “oh, it kinda sucks but you can tolerate it” territory. It’s actually unusable after a certain point. I inherited a Synology NAS at my current job which is used for backup storage, and my job was to figure out why it wasn’t working anymore. After investigation, I found out the guy before me populated it with cheapo SMR drives, and after a certain point they just become literally unusable due to the ripple effect of rewrites inherent to shingled drives. I tried to format the array of five 6TB drives and start fresh, and it told me it would take 30 days to run whatever “optimization” process it performs after a format. After leaving it running for several days, I realized it wasn’t joking. During this period, I was getting around 1MB/s throughput to the system.

    Do not buy SMR drives for any parity RAID usage, ever. It is fundamentally incompatible with how parity RAID (RAID5/6, ZFS RAID-Z, etc) writes across multiple disks. SMR should only be used for write-once situations, and ideally only for cold storage.



  • Hard disagree. Everything you learn on Arch is transferable because Arch is vanilla almost to a fault. The deep understandings of components I learned from Arch have helped me more times than I can count. It’s only non-transferable if you view each command as an arcane spell to be cast in that specific situation. I’ve fixed so many issues over the years using this knowledge, and it’s literally what landed me my current job and promotions.

    Arch is why I know how encryption and TPM works at a deeper level, which helped me find and fix the issue a Windows Dell PC was having that kept tripping into Bitlocker recovery. Knowledge of Grub and kernel parameters that I learned from Arch’s install process is why I was able to effortlessly break into a vendor’s DNS server whose root password was lost by the previous sysadmin before me when everybody else was panicking. Hell, it even helps in installing other distros, because advanced disk partitioning is a hot mess on a lot of distro GUI installers, so intimate knowledge of what I actually need helps me work around their failings. Plus all the countless other times that knowledge has helped me solve little problems instantly, because I knew how it worked from implementing it manually. When my coworkers falter because the GUI fails them and they know nothing else, I simply fix it with a command.

    If you use Arch and actually make the effort to learn, not just copy and paste commands from the wiki, you will objectively learn a lot about how Linux works. If you seek a career in Linux, there’s nothing I can recommend more than transitioning to using Arch (not Garuda, not Manjaro, Arch) full-time on your daily driver computer.

    Anyways, after about a decade I’ve recently switched to NixOS. Now there’s a distro where the skills you learn can’t be transferred out, but the knowledge I gained from Arch absolutely transferred in and gave me a head start.




  • Personally I’d rather have a choice of who to follow based on whose opinions align better with my own, instead of everyone being forced to go with the majority…

    NixOS is FOSS. People can freely fork it. Your choice is not being taken away.

    in other words I respect people’s freedom to have opinions I do not like, which I think this type of “community power” is in some ways the opposite of that.

    I’m not sure how voting makes it so we can’t respect each other’s opinions.


  • I’ve switched to Kagi recently and honestly it’s better than Google ever was. You can assign weights to sites to see more or less of them in your results, it automatically cuts the listicle crap out, it has various built in filters for specific things like forums or scientific studies.

    Downside: it’s $10/mo. But I’m at the “I’d rather pay with money than data” stage of my life. Especially if it actually makes the experience fucking usable again.


  • Have it just be form-fitted outside contacts, with magnetic adhesion to hold the plug in place.

    I actually really like this idea. If we’re breaking backwards compatibility anyways, let’s do something useful with it. This form factor was invented in the 1950s. I’m sure we can do something better now.

    We need to move away from everything having a battery anyways. Wireless headphones were a mistake. Now people are walking around with 4-6 batteries on them at all times. Phone, laptop, earbuds, earbud case, battery backup, smart watch. Batteries aren’t great for the environment, not to mention they typically condemn something to being tech waste in a few short years. We need to significantly rethink this model.










  • Your response is “why are you doing X, you should do Y”

    Because they’re right, you shouldn’t do X. I know that’s not a satisfying answer for most people to hear, but it’s often one people need to hear.

    If the process must run as root, then giving a user direct and unauthenticated control over it is a security vulnerability. You’ve created a quick workaround for your issue, and to be clear it is unlikely to realistically cause you problems individually, but on a larger scale that becomes a massive issue. A better solution is required rather than recommend everybody create a hole in their security like yours in order to do this thing.

    If this is something that unprivileged users reasonably want to control, then this control should be possible unprivileged, or at least with limited privilege, not by simply granting permanent total control of a root service.

    This is ultimately an upstream issue more than anything else.