Kind of like salting.
jabjoe
joined 1 year ago
I know, but there us as quiet war going on between the chippers and manufacturers. EV is a new battle front and we the consumers are losing right now.
Law makes need to join this century and get involved ensuring competition and longer product lives.
They DRM it all if we let them. We must not. It should going the other way. More open, repairable and upgradable.
Without right to repair, there will be planned obsolescence.
My Citroen EV developed an on board charger fault. It wouldn't charge. The part was a "coded part" which meant it had to specifically programmed with my EV's ID by Citroen at manufacture. It took months to finally be fitted and ready. So basically, not only does the coded parts system make service shit, but also means when the manufacturer is done making the part, the car is dead. You can't swap parts between cars and there is no third party parts. It's meant to be about car theft, but it's very convenient it blocks competition and long product life....
By communities, but not the manufacturer. Custom ROMs is the only way to keep it up to date for long enough for the hardware to become too old to be worth it.
No custom ROM for cars anytime soon.
Your want to store a copy of the private key on the encrypted machine so it can automatically sign kernel updates.
I'm sorry, but competition is good.
Installing some closed blob into your kernel, that's on you.
The problem is if anything is not enough competition. We just saw a centralized monoculture fall over.
Yer, I didn't, but this does seams a very Windows'y way of doing things, so can't see it widely done in Linux/BSD/Unix world.
I don't need some closed blob, with auto updates, in my OS. I doubt many Linux people would be happy with that.
To deal with a bad update, I'd boot a Btrfs snapshot from before the bad update. 'grub-btrfs' is great. I confess, it works great for my laptop, but I've not yet got it on one of my server. When I finally rebuild my home server, I will though. Work servers, I hope won't always be my problem!
Not quite the same thing. I doubt, for example, they have a big bag of device trees for different ARM devices to build from.
Can't see many Linux, or BSD, admins, being happy with "self-updating ring-0 proprietary software". That's very much a Windows culture thing.
You can get past these with a user agent, lying about which browser it is. However, they aren't testing for other browsers, so their site maybe as buggy as hell. As yet Firefox doesn't do a WINE and match Chrome, bug for bug, so sites work as intended. Google have cause IE6's return.