Solar Bear

  • 0 Posts
  • 97 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.



  • 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.










  • Solar Bear@slrpnk.nettoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    English
    arrow-up
    26
    ·
    6 months ago

    it’s probably time to come to terms with the fact that better alternatives would have arisen had anyone thought they could truly manage it.

    This is the most important takeaway. There’s a lot of people whining about Wayland, but Wayland devs are currently the only people actually willing to put in the work. Nobody wants to work on X and nobody wants to make an alternative to Wayland, so why do we keep wasting time on this topic?





  • Solar Bear@slrpnk.nettoLinux@lemmy.mlCanonical changes the license of LXD to AGPL
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    1
    ·
    edit-2
    7 months ago

    The full details are complex but I’ll give you the basic gist. The original GPL licenses essentially say that if you give somebody the compiled binary, they are legally entitled to have the source code as well, along with the rights to modify and redistribute it so long as they too follow the same rules. It creates a system where code flows down freely like water.

    However, this doesn’t apply if you don’t give them the binary. For example, taking an open source GPL-licensed project and running it on a server instead. The GPL doesn’t apply, so you can modify it and do whatever, and you aren’t required to share the source code if other people access it because that’s not specified in the GPL.

    The AGPL was created to address this. It adds a stipulation that if you give people access to the software on a remote system, they are still entitled to the source code and all the same rights to modify and redistribute it. Code now flows freely again, and all is well.

    The only “issue” is that the GPL/AGPL are only one-way compatible with the Apache/MIT/BSD/etc licenses. These licenses put minimal requirements on code sharing, so it’s completely fine to add their code to GPL projects. But themselves, they aren’t up to GPL requirements, so GPL code can’t be added to Apache projects.