81–90 of 230 posts
>Why isn't this build into every major operating system by now? Because no desktop OS besides MacOS can handle Sleep with any semblance of competency. >Why isn't this the default See above.
My usual comment: out of windows, macos and Linux only the Linux on laptop and on steamdeck can sleep and wake up reliably without draining all the battery for me. I know others have a different experience, but I'd just go with "none of the systems handle it reliably" if we're generalising.
>Why isn't this build into every major operating system by now? Because no desktop OS besides MacOS can handle Sleep with any semblance of competency. >Why isn't this the default See above.
> Because no desktop OS besides MacOS can handle Sleep with any semblance of competency. The Chromebook I'm using right now handles sleep perfectly, and always has.
Earlier quoted context omitted.
I've never had any issues with stand-by on Windows.
Windows in particular is notorious as of late for brutally draining the battery while Sleeping[1]. [1]: https://www.youtube.com/watch?v=OHKKcd3sx2c
Smartphones can be connected for days on the internal battery, using well under a watt, and they can be ready to respond instantly, and they have an app container system that makes everything just work. I really think we need to start making Android servers a thing, at least for self hosting, maybe for everything. Judging by how WearOS seems to be able to run on 35mA or less, I think there's a good case for just maki…
The big issue is the home server community being overly focused on creating "battle stations" that look cool and run 40 different Docker containers rather than simple low-power solutions.
You don't even need magic packets from a dedicated machine for wake on lan for some NIC's. For example on linux using `ethtool -s enp3s0 wol pug` will wake the system on p (PHY activity), u (unicast activity) and g (magic packet activity). Of course this is entirely dependent on how "noisy" your network is. This is something I've been thinking about for some time as I'm working on re-building my homelab for a more po…
My solution was to move all my online use-cases to a separate SSD and mount the HDDs only when I need them for a manual process. E.g. when I want to watch a movie I have downloaded, I'll mount the disk pool and copy it to the SSD (although my internet is fast enough that just downloading it again is usually faster than the manual process).
Earlier quoted context omitted.
>Does Time Machine run on a schedule? Add a cron job (whatever the Mac equivalent is) to send a WoL ~1min beforehand? I believe on x86 the BIOS supports setting a timer for self-wakeup. The OS can tell the BIOS "I'm going to sleep. Pull me out of sleep if the RTC passes this datetime."
Of all the x86 type BIOS and EFI, I've never seen one that didn't support that. Even thinclients and things you'd expect to leave that feature out.
Smartphones can be connected for days on the internal battery, using well under a watt, and they can be ready to respond instantly, and they have an app container system that makes everything just work. I really think we need to start making Android servers a thing, at least for self hosting, maybe for everything. Judging by how WearOS seems to be able to run on 35mA or less, I think there's a good case for just maki…
Currently automatic updates are an issue and remote management needs work.
What else am I missing?
Smartphones can be connected for days on the internal battery, using well under a watt, and they can be ready to respond instantly, and they have an app container system that makes everything just work. I really think we need to start making Android servers a thing, at least for self hosting, maybe for everything. Judging by how WearOS seems to be able to run on 35mA or less, I think there's a good case for just maki…