

The APIs are part of the Linux Kernel, so you’d be forcing the Kernel to completely change their development policy of internal breakages being allowed. That’s a no-go.
The APIs are part of the Linux Kernel, so you’d be forcing the Kernel to completely change their development policy of internal breakages being allowed. That’s a no-go.
I’d interpret that as a local social network app, not map/navigation.
docker-machine doesn’t use emulation, it’s virtualization.
Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.
Hm, unfortunately nothing obvious. And your last boot ended with a crash?
Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/
That’s unfortunately a bit cut off. Could you run this again with the following command? sudo journalctl -xeb -1 --no-pager
OP, do this - it’s the best way to figure out what’s happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.
I don’t know, plastic feels fairly unnatural
Though it’s fairly close at least
huh… brb
Edit: darn, I just remembered I don’t have a sister :(
I’m less disgusted and more intrigued by the mechanics of it.
I think if we found a way to get horny teenagers to try and fuck quantum mechanics, we’d have unified QM with gravity by now.
How did the sewer water taste? Can’t leave out the most important details!
It depends on what you’re running, but if it’s running in Docker using the official images, it will still be supported. The article explicitly says:
The Home Assistant operating system and container images (like Docker) will be the only supported installation methods.
You can run these images on any system/SBC, so nobody is discouraging “anything else than a Raspberry Pi”.
It’s been a while since I looked into installing/reinstalling HA but AFAIK using anything else than a Raspberry Pi seems discouraged, which is… discouraging.
I don’t think that’s the case, the docker containers are still going to be officially supported, and you can run those on any hardware.
6 months is not “absurdly” short considering it won’t suddenly stop working. It’s an open source project, 6 months is fairly reasonable for such circumstances.
Similarly, something being deprecated & something being depreciated.
The same turn of phrase exists in e.g. German.
I’ve started saying “beyond the pale” and “copacetic” after playing Disco Elysium
There’s really no way to do this without making the whole driver source-available, as there’s no way to update it to a new Kernel without full source access. That’d be great, but the manufacturers will fight tooth-and-nail against that, especially since the drivers can contain trade secrets.