this post was submitted on 11 Mar 2025
1035 points (97.0% liked)
linuxmemes
23433 readers
771 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My Windows 10 computer eerily waking itself from sleep got me in the habit of shutting it down completely every night. I'd be lying in bed, turn over and open my eyes, and see the light of the screen reflecting off the wall. It was like something out of a shitty horror movie about computers taking over the world.
To this fucking day, even in Windows 11, it takes "Update and Shut Down" as a mere fucking suggestion. About half the time, it'll restart after the update and just sit there chilling at the login screen. Not a single fuck given.
Linux is a breath of fresh air by comparison. Though, if you choose to run Arch you need to stay on top of updates or else a day will come where you won't be able to update because you're now too far behind. It can be fixed manually, but it's still annoying and a little scary if you're not familiar with it.
ACPI enabled BIOSes and UEFI support wake timers.
Windows uses this feature to wake the PC all spooky like so you don't get to click the update button yourself.
While Windows doesn't have an Arch wiki, the instructions for turning the automatic wake feature off are a web search away. You'll need another web search to disable automatic updates though.
Imagine your oven or clothes iron turning itself on while you're not home. Why TF people just accept their computers doing this is beyond me. Either it's a boiling frog situation, or people simply don't remember the times us users had complete control over our devices and think things were always this way.
As an 80s/90s kid, I can tell you they most definitely were not.
I hate windows doing windows things but that's an oxymoron take because computers aren't known to cause fires, if there was an apparent danger around leaving PCs on unattended, then there would've been legal repercussion. This is just a mere annoyance to most.
Windows has no idea of the state of the hardware it's running on. Someone could be using a janky molex to sata power adapter, which are known to catch fire and only uses it when someone is present. Or a cheap-ass wish.com power supply with exploding capacitors.
Electricity isn't free, and neither is it's impact on your computer hardware. The life expectancy of a circuit may reasonably be approximated as a function of watt-hours. this is why hardware manufactuers test their circuits in ovens: the heat simulates high wattage.
it doesn't matter if the power drain is low. So long as your computer is on, it's lifetime watt-hours are constantly ticking down.
Sleep disruption is a serious health issue
Itβs called Hardware (1990)
The software is arrogant and needs to know its place. It serves the user. It should obey.
i didnt know arch did that. never happened to me, though i guess that's because i update it like once every month or every two months, sometimes every day (depends on how long i can forget about updates existing)
The GPG keys that are used to sign packages expire and are rotated something like every six months to a year. If you don't get the new ones in an update before they start being used, pacman will refuse to update at all.
It's easily fixable, but if you don't know that, it can be quite intimidating.
oh that makes sense, thx for explaining :D
You can update arch from any point of time to the current, it just takes a bit of time. Just use arch archove and update by month or two.
Windows wakes up from hibernate? How tf is that happening? Also how tf it knows when to update when its hibernated/sleeping?
Better always keep a gun next to your bed if you use Windows.
Good thing i don't
CPU interrupts. There are timer interrupts that can be used for this. In hibernate, only a tiny fraction of the CPU is changing the transistor states. A transistor only uses power when it changes state; i.e. "off" or Hibernate. Transistor state changes when you cycle the clock on a CPU. Anyways, set the register for the timer interrupt and signal the CPU for Hibernate. The timer circuit is still listening to the clock while the rest of the CPU stops listening to the clock. Each clock cycle you subtract one from the register. When the register reaches zero, the timer interrupt wakes the rest of the CPU. Just like moving your mouse or pressing the power button; they signal an interrupt which wakes the CPU.
There is a thing called wake timers on Windows. There is also Wake-on-LAN but not sure if that's enabled on default or not.
So they don't wake when new update arrives but only for prescheduled previously downloaded update?
Yeah, update arriving part is not necessary but it wakes the PC up, checks for updates and install them if there are any, does this every night. And if you disabled auto-sleep it just stays like that until you interfere.
Shit its wake to check for updatesπ€¦ββ So it happens even if there is no update.. Thats so fucked up
from what i understood it wakes up randomly to check for updates, then goes back to sleep. or maybe it just stays on? im not sure