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

help-circle


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






  • In my experience that’s usually the case for XG-PON and XGS-PON networks. Because you’re sharing one port on the OLT with up to 63 neighbours. Though I think most build outs aim for 16 or 32 splits.

    Anyway they don’t want to risk you sending when it’s not your turn or disturbing your neighbours connection in any other way, they make you use their ONU. Basically the same old story like with the coax cable modems. Just because some idiot (or rather industry group of idiots) had to go and turn fiber back into a shared medium to save on cable and ports a bit.






  • Yep. Relevant sentence bolded by me below

    6d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.


  • violated the terms of the GPL

    Well we don’t know that, the terms say that you need to make the source available to people who got the binary. Either ship them together or ship a written offer for obtaining the source with the binary. You do not have to make the source available to the public (but any of your customers later could).

    To verify your claim we would have to get the binary from them, and check if source or an offer for it was included.

    Edit: The above is true for GPL2, but it seems Signal is under GPL3, in which distribution of offers of source have been curtailed a bit compared to GPL2, if I’m reading Section 6 here right