If you’re just looking for remote access, openvpn on port 443 should (in theory) be indistinguishable from normal https traffic.
If you’re just looking for remote access, openvpn on port 443 should (in theory) be indistinguishable from normal https traffic.
Tor. It’s free, it works, and there’s nobody to sell you out when the cops come knocking.
Ok, there’s the problem. Your boot partition is pretty much full. You’re using partitions instead of lvm, so expanding the partition will be next to impossible; so start looking through /boot for stuff that’s safe to delete. It’s weird that you have so much stuff in there, I don’t think I’ve ever seen my boot partition go above 250mb used.
zstd: error 25 : Write error : No space left on device (cannot write compressed block)
What’s the output of df -H
?
Also, this sounds like it’s installing initramfs, which is normally only done when first installing the OS; can we get a list of the packages it’s trying to install/upgrade?
Auto update itself isn’t the root problem. The problem is that apt update is hanging and never finishing. It just happens to be getting called automatically as part of an auto update system, but the root issue would still persist even if OP disables auto updates.
When apt update fails to complete, it’s almost always because of a broken repo somewhere; hence my question about sources.list.
I’d leave the main sources.list alone, but temporarily move all of the files out of sources.list.d and see if that fixes it.
Definitely sounds like auto-update if it’s respawning itself on every boot. The fact that it never exits is weird though; have you added any third party repos? What’s in your apt sources.list file(s)?
“Maybe if we slap his wrist again, he’ll start being a good cop this time!”
Holy shit, she’s even crazier than I thought, yikes
I’m out of the loop, what’s the context for all this?
Relevant: https://youtu.be/Fb7N-JtQWGI
Netflix rolled out av1 support for a handful of Samsung smart TV’s about a year and a half ago, then kinda shoved the project under the rug and never mentioned it again. My guess is that the added costs of having to store their entire library twice plus having to re-encode everything made it uneconomical. Besides, av1 doesn’t have a bandwidth advantage over h.265; all of the comparisons that Google likes to use to show off the codec are av1 vs h.264, which is pretty sneaky and misleading imo.
No arguments about it being a good TV, but the vast majority of people do not have shiny new LG oled TV’s. Hell, most people are still using old 1080p lcd’s without any smart TV features, and the people who have got new TV’s over the past few years tend to skew heavily towards buying relatively cheap 4k TV’s that may not have any smart TV features (after all; if i already have a roku/apple tv/chromecast/etc that covers all of my streaming needs, why would I pay a huge premium to get these features a second time?)
The trouble with AV1 is that it’s about a decade behind h.265 in terms of hardware support. Most people aren’t upgrading their gpus every single generation, so by the time AV1-compatible hardware starts to see significant market share, it’s pretty likely that h.266-compatible hardware will be on the market as well.
Of course, there’s also software encoders; but benchmarks of current software encoders put av1 anywhere between 50-1000x slower than x265 for comparable quality and bitrate.
It’s definitely cool that people are working on a royalty-free video codec, but h.265 is the undeniable king for the time being.
If they did, I haven’t heard about it. China has been trying and failing to block tor for decades though, so I kinda doubt Russia managed to beat them to it overnight.