Existing systems are going to continue to boot. The expiry date is enforced for signing new binaries, not for deciding whether an already signed binary is allowed to boot (barring buggy firmware).
Shim, the first stage bootloader on Linux, is designed to be updated infrequently. Distributions embed their own signing certificate in it and have that binary signed by Microsoft. The actual bootloader (typically either grub or systemd-boot) is then signed with the distribution certificate, as is the kernel. Distributions get to set their own policy around how long that certificate lasts for, it's entirely unrelated to the Microsoft certificate expiry.
No, distros uses a shim binary that is less likely to need updates. If that shim needs an update (only signed with the new key) then we get into a situation where old machines will fail to boot it.
I’ve had both - the 380 is much lighter to carry around than the 480.
I wouldn't recommend either though, for both, the keys are not nice to type on if you don’t press perfectly downward, if you have any angle other than vertical, the keys occasionally bind a little. This is amplified on the 480 with longer key travel. They’re different types of key mechanisms on both but suffer the same problem.
If you have any kind of case, the 480 stand slot can be harder to use.
I played with a negative ion generator at my desk, and it was great at knocking out my 1440p monitor signal, but the 1080p seemed more resilient.
Since then I got a 4K display, and it likes to drop out in thunderstorms. I switched to a better DP to HDMI adapter, and the chunky original Samsung cable. I'm waiting for the next storm to see if it helps.
It’s not properly shielded. If you have a multimeter you can do a quick low-hanging fruit pass by checking continuity between the metal shields on both ends. No continuity means no shielding, but the clever assholes will run a thin wire between the shields so it passes that test, even though it’s not actually shielded. That means it won’t tell you if it is shielded, only if it definitely isn’t.
I found a similar issue with nearly all of my cheap USB cables, which I started looking into when I realized only some of them would work right with my camera or Arduino. Out of ~30 cables perhaps 14-16 of them had no shielding at all. I cut open five “shielded” ones and two of them had a thin wire connecting the shields, just to fool people casually testing them. It’s a real crap industry.
Bubble envelopes are all wrong? Flipped bubbles would make it harder to slide objects in and out of the envelope, but they would reduce movement inside the envelope.
The difference seems minor other than the ability to tape the flat side, and we have cling bubble wraps that don't need tape anyway.
I got a IPX in 2022 and restored it. I was a bit lucky and mine was an ex-IBM unit that came with the Weitek SPARC POWER μP processor (80 MHz) upgrade.
It makes for a pretty good project box as one of the smaller SPARC machines. Lots of documentation from hobbyists, Sun's own service manuals, and OpenBSD/NetBSD. Flash SCSI disk replacements are much easier to get your hands on now (I used a ZuluSCSI).
It seems to have been part of IBM's IBM-IPT Tester system. Hostnames were interesting: flower, owl, piglet, diamond, hotlips. I didn't get any interesting data though since this system relied on network resources.
Altitude can be a huge limiting factor. I biked from Texas to Oregon, and the first days in the Rockies were brutal. It seemed I could barely travel 50 feet up hill without taking a break. I even considered turning around because it just felt impossible.
https://mjg59.dreamwidth.org/72892.html (Secure boot certificate rollover is real but probably won't hurt you)
https://wiki.debian.org/SecureBoot/CAChanges#OMG.21.21.21_Wi...