• smoothbrain coldtakes
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    3
    ·
    1 year ago

    Linux is easily fixed but the problem is that the issues that crop up needing to be fixed are generally not pain points on Windows. The first Arch install I did this year was busted and I thought I had broken my networking setup because it wouldn’t connect, but the issue was that the system clock was wrong. Something like that may pop up in Windows but you can quickly press the sync time and date button in the settings and it’ll sort itself out, while Arch requires a lot more work than just that, especially if it has no connectivity.

    • SkyeStarfall@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      …I’ve certainly had that issue on windows as well. I had to manually set the time. Windows sync at least didn’t use to always work.

    • pete_the_cat@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      I’ve been using Linux for like 15 years and Arch for about a decade. I’ve never had an issue where the system time prevents the network connection from working. That’s odd.

      • smoothbrain coldtakes
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        1 year ago

        It makes sense because all of our cryptography is based around time limits. If the system time is way off it can’t verify the cryptographic signatures and it’s not going to validate any certs since the time doesn’t line up properly.