• 0 Posts
  • 361 Comments
Joined 1 year ago
cake
Cake day: April 13th, 2024

help-circle



  • 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.








  • 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.







  • Is there some sort of rule that says that there can only be two political parties.

    No, but I think the issue lies with their system of government. As a presidential republic they don’t have parliamentary government where parties enter coalitions to form the executive, so smaller parties have no good way to get established and share executive power and responsibility while growing.

    Couple that with the voting system which also favours the trend to only two parties, and there you have the mess.

    PS: They have the Green Party and the Libertarian Party, but they remain at the fringe and largely irrelevant. No seats for either of them.




OSZAR »