this post was submitted on 10 Oct 2023
245 points (93.9% liked)
Technology
59106 readers
3246 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
...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.
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.
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.
Yeah, true.
Every distro has ntp setup by default. New users shouldn’t use Arch…
Yeah and old users shouldn't be fucking snobs, yet here we are.