Yeah, that despicable russophobia that makes us brain-washed russophobes hallucinate how Russia is invading neighbouring countries while committing war crimes, attacking other countries’ IT infrastructure, commiting sabotage and flooding social media with propaganda 24/7 for years… 🤡
It’s been years since I took a look at this but I vaguely remember a handy kioskrc config file under xfce4…
That sounds like the non-techies would be able to fix it themselves on Windows without you being around, which in my experince isn’t the case.
It might be different for you with a lot of tech-affine people in your family. But for those of us being forced to be the tech support anyway, it can really make a difference if you have to fix a Linux issue once in a while or have to reinstall Windows for the 5th time this year…
I do know it’s not completely literal
Are you trying to kink shame?
Batteries losing more than 20-25% of their capacity in 150.000km had a defect in production already. You can find similiar numbers in any OEM’s warranty. So a non-defective battery will provide at least 80% of its capacity at 150.000km. The average car manages about 250.000km over their life-time of about 15 years (reference numbers from the US, so the most pessimistic view as barely anyone else in the world is matching those distances).
You are not completely wrong. Used batteries will be a problem… somewhere far down the road because electric vehicles are expected to easily manage 800.000km or more (less moving/wear parts).
But we are not there yet. The whole EV market isn’t old enough to have produced these long-lived vehicles and we are back at my original point. Today it’s not about battery degradation but about EVs not getting old fast enough to already have established a robust used market. In fact the first big batch of EVs on the used market is often not expected for another 2 years (see here for example, and that’s again rather new vehicles because of a loophole for leased cars in the EU).
In short: There isn’t a huge used EV market yet and (more importantly) the demand is stifled by battery degradation fairy tales not relevant (EVs old enough for this basically don’t exist yet) and political mismanagement subsidising new EVs.
It’s obvious for everyone with basic logic skills.
But that doesn’t mean we can’t try and twist the fact for anti-EV propaganda. Because it’s really, really, really important we keep burning oil… if you are someone selling oil and have the money to spread bullshit for personal gains that is.
What do you think the average 10 year old car has done to that point? Battery degradation is hugely overrated and stories are based on tech already left behind.
The actual problem for the used car market is the opposite: EVs live much longer than traditional cars and thus don’t lose their worth that rapidly, while on the other hand new cars still see a fast development cycle while also getting cheaper.
So no, it’s not a problem of used EVs per se and that their expensive batteries are allegedly dying. It’s the fact that a new EV just a couple of years later is ahead 1-2 generations and also cheaper.
You could…
But then one is an open system where you can disable the UI put on top and have a working linux system, while the other is a closed blob destroying compatibility and trying hard to lock you out from accessing the underlying linux system.
ARM is shit at hardware discovery in general. So no, chromebooks don’t need a special distro. They however need a kernel adapted to the specific hardware, often down to the model (that’s also the reason Android updates take so long on phones and there is very time limited support… there’s always someone needed to adapt new updates to the specific hardware for each device, so they don’t bother for anything but their latest products).
Decryption isn’t a problem if you use the systemd hooks when creating your initrams. They try to decrypt every given luks volume with the first key provided and only ask for additional keys if that fails.
I have 3 disks in a btrfs raid setup, 4 partitions (1 for the raid setup on each, plus a swap partition on the biggest disk), all encrypted with the same password.
No script needed, just add rd.luks.name=<UUID1>=cryptroot1 rd.luks.name=<UUID2>=cryptroot2 rd.luks.name=<UUID3>=cryptroot3 rd.luks.name=<UUID4>=cryptswap to your kernel parameters and unlock all 4 with one password at boot.
It has lots of small issues that add up to a frustrating experience for mainstream users.
And 99% of those are out of Linux’ actual resposibility because they are caused by third parties screwing up… sometimes even intentional (from companies producing lackluster drivers only having a fix cobbled together for Windows specifically -looking at Realtek networking for example- to ones actually going out of their way to block Linux (MS FUD included…).
The majority of “Linux issues” is created intentionally. It’s often not enough to not support Linux officially (even if there would be no additional work involved anyway) and let players figure out problems on their own. A lot of studios, publishers and developers actually go out of their way and actively invest time to block Linux.
So nothing will obviously change. Windows could run on a fully compatible Linux kernel tomorrow and games would still check for Linux to artificially create issues.
Car-brains don’t do standard logic, only car-logic…
There is a difference here.
Unlocking home later in the boot process is not a problem, so the you can indeed have a keyfile on your root and get your home unlocked and mounted after root is done.
Swap however needs to be available early, at least if you want to use it for hibernation.
This would -at least as far as I understand it- limit your swap’s functionality for hibernation etc. Because there your swap needs to be available early. You can still do it in theory, but the key file then would need to be included in you initrams, which kind of defeats the purpose.
There is however a much more easier option: either use LVM on luks (so the volume is decrypted with the password and then contains both, root and swap) or just use the same password for root and swap while switching over to the systemd hooks (as those encryption hooks try unlokcing everything with the first provided password by default, and only ask for additional password if this fails).
Hydrogen or battery?
The answer is battery. If battery is an option then the answer is battery. Always.
This will only change if either there is an unlimited amount of free energy available or the laws of thermodynamics stop being valid.
Stick to a specific distro and train your staff
Linux is Linux. Train your staff to properly use one and they can use them all. “Distro” is just a fancy word for “which package manager and update cycle to we chose and what logo do we put on our pre-installed wallpaper”.
Yes, I actually just use Wine with a default prefix and pray it works. If it doesn’t (rarely) then the game gets his own prefix to tweak the settings.
you didn’t say what file system your /boot partition was using, so I don’t want to guess
It’s actually easy to guess. There is exactly one filesystem UEFI has to support by its specification, everything else is optional… so unless you produce for Apple -because they demand apfs support for their hardware- no vendor actually cares to implement anything but FAT.
Removed by mod