It was meant tongue-in-cheek, you seem to be taking it much more seriously than I intended it to be. 🙂
But in reality is not done because it simply doesn’t bring any benefit.
Fully agree that there is absolutely no benefit to NAT66, it only causes enormous headaches. I sincerely hope nobody uses it these days, this poor bastard however did manage to find a VPS provider that used NAT66 back in 2018: https://blog.apnic.net/2018/02/02/nat66-good-bad-ugly/ 🤢
Edit: I’ll just add an ‘/s’ for good measure, as apparently I was too subtle. Be sensible, don’t do NAT66.
Fedora was one of the first to get rid of pulseaudio and replace it with Pipewire, so that shouldn’t be an issue.
Yeah, that’s definitely a concern. My first installation shredded its SD card in no time due to each request getting logged and stored on disk. Turning off long term query logging mitigated that issue, for my home network I don’t care about that history anyway.
Anybody got the feeling some games may be negatively affected by a PiHole ?
My RPi 2 has been happily running PiHole in my network for about 8 years now and with a number of pretty strict block lists, personally I never had any issues with games.
The early Lenovo period W series were (imho) very good as well, still have my W500 series which is built like a tank. Survived years of college, years of lugging it around to customers and data centres and having somebody spill a full cup of coffee over it (yes, the drain holes do work!). It only required replacing of the monitor cable once, which was a pretty easy thing to do. Unfortunately the CCFL backlight has lost quite some luminance by now, but guess after 16 years that is to be expected. Can’t get myself to part from it though, so many memories attached to it.
Or SuSE Linux, the non-slackware or jurix version was bleeding edge at the time.
And that’s just the quick summary, first time I just restored a backup. But as my system immediately failed again after updating I started digging and came across some obscure posts of Lenovo users (ok, maybe Lenovo isn’t that great with implementing Secure Boot after all 😋) having the same issue and devised that rescue plan. Quite the nightmare indeed, but at the other hand it also taught me some new skills. After going through the same routine on each update of that package I ended up excluding it from updates in DNF.
Don’t now if the issue was ever resolved, I’ve since stepped away from Fedora as I’ve just had too many of these weird issues with it on each new release. Creating bug reports and the accompanying warm feeling of helping to improve the Linux ecosystem is nice, but in the end I just need to get work done.
This has nothing to do with Lenovo perse, this is the average experience for every laptop I’ve owned which had Secure Boot turned on.
You know what is fun? Having your Dell basically bricking because Fedora starts shipping a new version of shim-x64 which completely fails the UEFI handover to bootloader. Leaving you unable to boot at all, so no chance of reaching rescue mode. Then more fun times of booting a live environment from a usb stick after going through the same hoops you went through, finding out how to decrypt your BTRFS partitions, manually mounting and chrooting them so you can finally downgrade the offending package.
Linux and Secure Boot just isn’t a great combination if you ask me.
Isn’t dendrite formation and the shorts they can cause a much bigger concern when dealing with old batteries that are being charged 24/7? Asking a genuine question here, so please don’t shoot me if I’m wrong. 🙂 I’d love to hear more about the most common failure modes and causes for li-po/ion batteries.
when was the last time you heard any such news for PC
A few seconds ago, when I read that the new Linux kernel contains TCP related performance improvements!
Recently switched from Fedora to Manjaro.
Unfortunately I found Fedora to be too unstable for daily use. Just too many issues, some (like shim-x64 versions after 15-8 not being able to boot my system) which just didn’t get fixed. And every new major version had its own new set of issues. So after seeing the umpteenth attempt to automatically install a firmware update fail due to shim-x64 being too old and the gazillionth window manager crash wiping all my open applications I bit the bullet and migrated away.
So far no major issues with Manjaro, one of the things that did work excellent on Fedora was Wireplumber automatically switching Bluetooth profiles when I connected to a online call. That seems to be a bit more unstable in Manjaro and often requires manually changing to the correct one. But I don’t attend enough meetings for that really to become a major issue for me.
Haha, don’t worry, no harm done. Maybe I was a bit too subtle in hindsight.
That’s Poe’s Law by the way.