Comment

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.

source

Sort:hotnew top

SkyeStarfall@lemmy.blahaj.zone ⁨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.

source
pete_the_cat@lemmy.world ⁨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.

source
- canis_majoris@lemmy.ca ⁨1⁩ ⁨year⁩ ago
  It makes sense because all of our cryptography is based around time limits. If the system time can’t verify the cryptographic signatures it’s not going to validate any certs since the time doesn’t line up properly.
  
  source
  - pete_the_cat@lemmy.world ⁨1⁩ ⁨year⁩ ago
    Yeah, true.
    
    source
AProfessional@lemmy.world ⁨1⁩ ⁨year⁩ ago
Every district has ntp setup by default. New users shouldn’t use Arch…

source
- canis_majoris@lemmy.ca ⁨1⁩ ⁨year⁩ ago
  Yeah and old users shouldn’t be fucking snobs, yet here we are.
  
  source