Coming from Debian, it was…not expected. I understand how and why it happened, but the user experience was surprising.
Debian keeps the previous kernel around, which makes perfect sense to me — in the event that a kernel update borks your system you can just load the previous one. This would probably only happen due to out of tree modules (looking at you, Nvidia…).
Linux distros can still do…questionable things. In grad school I tried Arch for a bit, and I once was late to a video call because I had updated my kernel but did not reboot. Arch decided that because there was a new kernel installed, I didn’t need the modules for the old — but currently running! — kernel, so it removed them. So when I plugged in a webcam, the webcam module was nowhere to be found.
But yeah…somehow, still not as bad as Windows updates.
Our Internet went out for a few hours today, so naturally my smart switches, lights, cameras, motion sensors, door sensors, and power monitoring… continued to work as of nothing was wrong.
Home Assistant is great, and using local-only devices is awesome. If my smart home stops working it’s my own fault, not some 3rd party.
ZigBee router thing:
I’ve been happy with the SMLIGHT SLZB-06M. You can easily flash firmware, and it has PoE which was important for me. I believe it also supports Thread, but I haven’t tried this yet (and I’m not sure if it supports it at the same time as Zigbee).
Zigbee smart plugs from Third Reality have been pretty solid in my experience, and they report power usage.
For circuit breaker level monitoring, I have an Emporia Vue2. I have it running esphome, completely local — unfortunately this requires some simple soldering and flashing, so it’s not turnkey. But it’s been rock solid ever since flashing it. (Process is well documented online.)
I’ve had decent luck with cheap wifi Matter bulbs, but provisioning them is finicky, and sometimes they just crap out and need to be power cycled; Zigbee bulbs (e.g., Ikea) have generally been reliable, though sometimes I’ve had difficulty pairing them initially. After power cycling a Matter WiFi bulb, it takes a while for it to respond to Home Assistant; Zigbee bulbs generally respond as soon as you power them on.
I have a wired smart light switch from TP-Link/Kasa (KS205), and it’s been completely hassle free (and totally local — Matter over wifi). The Kasa smart switch dongles I have work flawlessly but need proprietary pairing, and I’m afraid to update firmware in case they lose local support.
Good luck! Fun adventure :)
Most Linux filesystems, being case sensitive, won’t find the SUDO command.
I think a lot of companies view their free plan as recruiting/advertising — if you use TailScale personally and have a great experience then you’ll bring in business by advocating for it at work.
Of course it could go either way, and I don’t rely on TailScale (it’s my “backup” VPN to my home network)… we’ll see, I guess.
…are Turing Complete, so what you can do with them is exactly equal.
But they’re only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.
Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)
Bonus points: use non-qwerty keyboard for added obfuscation (but keep the qwerty key caps of course).
I hope I’m wrong! I’d definitely consider buying some — hopefully you can report back with results. If they’re slower than advertised but have the actual capacity that’d still be awesome!
This looks like it might be it:
The drive doesn’t provide 4TB of storage either, considering the single NAND chip. That means if you were to attempt to write that much data to the SSD, at some point it would either fail or start overwriting existing data.
I’d say it gets a little different with command line utilities — maybe “utility” is the appropriate term here, but I’d call something like grep a program, not an application (again — “utility” also works).
To be sure, grep is extremely powerful, but its scope is limited.
Physics is like sex: sure, it may give some practical results, but that’s not why we do it.
— Richard P. Feynman
I think the same is true for a lot of folks and self hosting. Sure, having data in our own hands is great, and yes avoiding vendor lock-in is nice. But at the end of the day, it’s nice to have computers seem “fun” again.
At least, that’s my perspective.
Whatever you decide for your laptop, I’m a proponent of a barebones off-site setup if you’re trying for 3-2-1 backup or similar.
I use a raspberry pi 3 with a single HD (ZFS) retaining some number of daily/weekly/monthly snapshots. Daily rsync, everything over WireGuard+VPS (TailScale would work too).
Others mentioned virtualization — I have had issues with COW filesystems (btrfs), as COW does not always play nicely with VM drives (extreme fragmentation and very poor performance).
from stdlib.h import cout
Wait this looks wrong, shit…
Anything can use it, but I think by convention it’s used for http on a non-privileged port.
Maybe there’s some interplay between amd64 and x64 architectures.
AMD64 and x64 are the same thing. Do you mean AMD64 and x86? There is definitely interplay there, as AMD64 implements the x86-32 instruction set.
Same — rsync to a pi 3 with a (single) ZFS drive at family’s house. Retain some daily/weekly/monthly snapshots.
I have a (free) VPS with static IPv4 which is how I connect everything.
Both the VPS and the remote site have limited network speed (I think 50Mbps for VPS), so the initial sync was done sneakernet (well…“airplane net”). Nightly rsync is no problem bandwidth-wise, and is mostly just any new videos I’ve uploaded to my local Immich instance.
Coming from Debian, it was…not expected. I understand how and why it happened, but the user experience was surprising.
Debian keeps the previous kernel around, which makes perfect sense to me — in the event that a kernel update borks your system you can just load the previous one. This would probably only happen due to out of tree modules (looking at you, Nvidia…).