

Even further: The support is exclusively for the 32bit libraries. The 32bit kernel and therefore cpu support was dropped a long time ago in Fedora. Fedora 31 in 2019.
Even further: The support is exclusively for the 32bit libraries. The 32bit kernel and therefore cpu support was dropped a long time ago in Fedora. Fedora 31 in 2019.
To be a little more precise, Linux is still available for 32-bit x86, just not from the Fedora distro. The Linux project is just now dropping support for 486 CPUs, because the maintenance burden for a virtually unused system type is too high for the mainline. That still leaves 32-bit Pentiums and newer though.
Is dropping support for 32bit hardware more important than being able to run on everything?
Yes evidently, because they dropped that hardware support in 2019. Specifically they dropped 32-bit x86 kernels in Fedora 31
The argument is utterly stupid.
Ignoring that it is building on a fantasy reality for the moment. Even if you had free healthcare, and if only the financial costs of survival motivated people to get jobs, then the other costs of living, like for food and shelter, would still provide that motivation.
Is this Amichai Shilo someone important? I don’t recognize the name
I don’t get along well with people who aren’t at least within “discussing distance” politically. I wonder how people even date when they don’t agree on some fundamentals.
Using 1 is fun. That means the circumference of a circle is equal to its diameter.
it should automatically shut down after applying the updates
Okay, that part it does for me though. That’s extra annoying for you then.
apply everything that is possible, then restart and apply the remainder
Yeah on one hand I get the concept, on the other macOS and Linux manage without, and I don’t really remember older Windows doing this either, so I wonder if there is a real reason why it’s needed, or they just engineered themselves into a bad corner…
This week I heard from a network group lead of a university hospital, that they have a similar issue. Some medical devices that come with control computers can’t be upgraded, because they were only certified for medical use with the specific software they came with.
They just isolate those devices as much as possible on the network, not much else to do, when there is no official support and recertification for upgrading. And of course nobody wants to spend half a million on a new imaging device when the old one is still fine except for the OS of the control computer.
Sounds like a shitty place to be, I pity those guys.
That said, if you were talking about normal client computers then it’s inexcusable.
That’s always so annoying, because Windows isn’t my default boot entry, so I need to babysit its “totally not a reboot” update.
Hm the word yacht is easy, it means Jacht :-)
I mean it’s Eliezer Yudkowsky, so it has to be a joke, plus the way he upped it in the reply confirms it, but I don’t really get the funny bit.
Claim Musk is a dangerous foreign influence and force a sale like for Tiktok
though you’d need to supply power
Go for really old ones with the crank handle for ringing. Like from army surplus and you don’t need the power :-)
We played around with these for a day in the army https://en.wikipedia.org/wiki/Feldtelefon_50 when you crank the handle while your friend is still putting down the line you can shock them.
Pre-UEFI they were fighting over the boot sector, sure, but now that everything is more well defined, and every OS can read the FAT32 ESP? Never seen it…
At worst the UEFI boot entry is replaced. There are some really shitty UEFI implementations out there which only want to load \efi\microsoft\boot\bootx64.efi
or \efi\boot\bootx64.efi
, or keep resetting you back to those.
Assuming you were dumped into Windows suddenly, you can check if you have the necessary boot entries still with bcdedit and its firmware option
bcdedit /enum firmware
If you just have a broken order you can fix it with
bcdedit /set {fwbootmgr} displayorder {<GUID>} /addfirst
If you actually need a new entry for Linux it’s a bit more annyoing, you need to copy one of the windows entries, and then modify it.
bcdedit /copy {<GUID1>} /d "Fedora"
bcdedit /set {<GUID2>} path \EFI\FEDORA\SHIM.EFI
bcdedit /set {fwbootmgr} displayorder {<GUID2>} /addfirst
Where GUID1 is a suitable entry from windows, and GUID2 is the one you get back from the copy command as the identifier of the new entry. Of course you will have to adjust the description and the path according to your distro and where it puts its shim, or the grub efi, depending on which you’d like to start.
Edit: Using DiskGenius might be a little more comfortable.
I am not a computer science major, I studied linguistics.
We’re not falling for your deceit, Noam Chomsky. You probably used some context-free grammar to hack the website.
We have a handful of portraits of one, and hours of animated material of the other. Who do you think gets looked at more? If that survey was actually conducted that was a huge waste of time.
Okay good. I thought it would, just didn’t know any specifically. I wasn’t trying to suggest a public blockchain would be the only solution or even the best of multiple solutions, only that they needed to consider more angles beyond just making a hash.
That’s a kernel saying. A bit unfitting to repeat it for the distro that builds said userspace.