Errar es humano. Propagar errores automáticamente es #devops

https://vsis.online/

  • 8 Posts
  • 153 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle





  • Nobody likes Adobe, nobody wants to work with Adobe. Nobody can avoid Photoshop. That’s just the world we live in and I don’t like it.

    This sounds like Stockholm syndrome. You are just too familiar with Photoshop, so using anything else is hard and less efficient.

    In photography there is this mantra about “the most important part is right behind the camera”. A good photographer is not a good Nikon user, or good Canon user. A good photographer can deliver decent pictures with a potato camera if needed.

    Sure, a potato camera is less efficient for any work that an actual good one. So it’s good to invest in a good brand. But the point is: if you are not capable to make average results with a potato software, the problem is not in the software.


  • Not true.

    The immutability of the thing is just Merkle trees. And integrity of the writings is any form of authorized blocks. From a certificate from an authority a la PKI to proof of work. And anything in between.

    The thing is that there are not too many applications for slow distributed inmutable databases.

    DNS is the only thing that I know that is globally distributed, with slow updates of domains being acceptable.









  • vsis@feddit.cltoPrivacy@lemmy.mlImprove Your Privacy Setup
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    If you’re concerned about security, consider GPG signing your kernel with Libreboot GRUB for an additional layer of verification at boot.

    Hey! I had no idea that was possible. I usually encrypt everything but /boot, because it’s easy that way.

    I don’t have a “threat model” of someone puting malware in /boot while I’m away of the computer. But it would be nice to know how to prevent that.

    Do you have a link of a guide or tutorial for that?







  • vsis@feddit.clOPtoLinux@lemmy.mlIs my NVME drive dying?
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    8 months ago

    I opened it. All cables were looking good. I used a hand blower to clean the dust. Taked out the SSD and blew the socket and everything around.

    Now I’m going to monitor if it keeps happening.

    $ journalctl --since yesterday  | grep -c "nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical"
    16