You have any 2.4 GHz WiFi problems? In theory there is a problem, and I know a dude with a lot of ZigBee and a lot of 2.4GHz problems, but without going over with work equipment and spending some time doing work for free, I can’t be sure it’s ZigBee. It’s just my best guess.
You already married to ZigBee? If not, maybe don’t. It causes 2.4Ghz interference. You’ll need to think about WiFi channels and avoid ones that overlap with ZigBee. Either that, or use 5Ghz WiFi and repeaters to make up for the lower penertration (if an issue).
Yer it’s nonsense. The first device I switched from Ubuntu to Debian on was the SheevaPlug because Ubuntu dropped support for it. Debian still supports it now well over a decade later.
The joke is Mac and Linux users, who aren’t actually effected, are incapacitated due to being busy gloating on social media.
Mmm depends. I have some automatic updates on my servers: https://wiki.debian.org/UnattendedUpgrades
Few things, in rough order:
Smaller = less attack surface. You can strip a Linux OS down to only what is needed.
Open source, so it’s can be peered review. There are Unix distros like OpenBSD, that share lot of user space component options, where auditing is a big thing. The whole sunlight and oxygen stops things festering as much. As abosed to things locked in a box in another box down in a cellar.
Open source transparency forces corporates to be better. We can see what they are and aren’t doing.
Diversity. The is no “Linux”, it’s a ecosystem of Linux distros all built and configured differently, using different components. Think of Linux as just a type of base board in a sea of Unix Lego bits. There are plenty of big deployments on BSD bases that share a lot with some Linux deployments.
Unix security is simplier than Windows security, so easer to not mess up.
Yes and no. Linux is inherently more diverse. All the different distros doing things in different ways, sometimes with different components. It’s not as much of a monoculture as Windows. There isn’t a Linux that 90% is.
Someone got to say it…
There is no Debian if everything was a pile of Snaps/Flatpack/Docker/etc. Debian is the packaging and process that packaging is put through. Plus their FOSS guidelines.
So sure, if it’s something new and dev’y, it should isolate the dependencies mess. But when it’s mature, sort out the dependencies and get it into Debian, and thus all downstream of it.
I don’t want to go back to app-folders. They end up with a missmash of duplicate old or whacky lib. It’s bloaty, insecure and messy. Gift wrapping the mess in containers and VM, mitigates some of security issues, but brings more bloat and other issues.
I love FOSS package management. All the dependencies, in a database, with source and build dependencies. All building so there is one copy of a lib. All updating together. It’s like an OS ecosystem utopia. It doesn’t get the appreciation it should.
I can only speak of on Linux. If you know the disk is bad, clone it, with ddrescue, and fix the clone. But in future RAID and backup remotely. Also, next gen filesystems like ZFS and Btrfs for check sums and self healing and subvolumes with send/receive deltas between them.
These may be good: https://www.mylocalbytes.com/products/smart-bulb-9w-rgbct
I trust Tasmota more than some random closed source thing.
As I said, “if this no other option”. And to be honest, that was once, for a few weeks before the new KiCad hit Debian repos. And only because hardware team wouldn’t wait to switch, so to open stuff, I needed it too.
I’ve been on Debian Testing for my own desktops for about 15 years now. Sometimes as a Frankendebian mixing in SID/unstable. Sometimes mainly unstable, but mostly just Testing.
It rarely breaks, but when it does, it’s a learning opportunity. Stable for servers and other people’s desktops. Maybe with backports. Flatpacks if this no other option.
You don’t get 100% solid and 100% new. Ever. With anything.
Busybox is used in the initramfs normally. It’s the shell used by any scripts in that early stage, as well as the fallback shell environment.
Google is not really much better than MS. It still leaves you under the yoke of big tech. “Meet the new boss, the same as the old boss”.
You spelt monopoly wrong.
Also depends on the country. It isn’t everywhere. Non-commercial file-sharing is legal in a number of European countries and I’m sure elsewhere.
It could be taken as a sign of the health of the democracy’s function and technically literacy of the population. In a society of tech heads with a highly functional democracy, it would be DRM measures that would be illegal…
Just a follow up to this.
So I never ended up contacting O2 to say “please stop this”, I just used Wireguard to home and ignored it. Until the local Morrison’s wifi started doing the same thing but worse and I couldn’t event Wireguard round it.
So I finally just bought a domain and setup my Apache to redirect the old duckdns to the new domain.
So far this all seams to be working great.
That is a low bar for duckdom.
More like file descriptor. File path is like address system, but it’s not how you get all file descriptors. For example: sockets (there is bash’s fake /dev/{tcp,udp}), epoll, timer, event, inotify.
In UNIX systems event systems have a list of filedescriptors with a callback for each. You could have your event loop an epoll fd itself and nest it in another.
I hope it continues to be a non issue for you. Without you having to take any measures. Just saying it can be an issue. Search “zigbee 2.4ghz wifi interference” if you don’t believe me.