• elouboub
    link
    fedilink
    481 year ago

    With these updated routing tables, a lot of people were unable to make calls, as we didn’t have a correct state

    You’re relying on windows for critical infrastructure? Are you nuts?

      • elouboub
        link
        fedilink
        241 year ago

        Indeed, nothing is perfect, but closed source stuff doesn’t provide a lot of recourse. If you have a linux expert in your team, they can investigate and if need be even dig into the code of linux itself to find the core issue. Microsoft doesn’t provide anything even remotely similar.

          • elouboub
            link
            fedilink
            171 year ago

            Don’t need one. If you can read C/C++ you can read the kernel code. And in most cases, you won’t have to, as the problem is probably in a component in the distro. Those are written in python, ruby, or bash, which are all much more readable than C/C++.

            No such luck on windows

          • I worked at a small company without a kernel dev and we periodically looked into the code to solve problems. I don’t know how much we upstreamed, but we relied on Linux so it was either the or try to get someone on the mailing list to care.

            It’s really not that hard to look through the kernel source, it’s pretty well written and documented. It’s a lot harder to be a kernel developer writing new code, but finding bugs and contributing fixes isn’t that bad.

          • You don’t have to be a kernel dev for that. Reading source code is much easier than writing it. I myself have even read the code that handles the battery management drivers, and it’s mostly self documenting, even though I’m bad at C and it’s pointers, and also have never yet written a kernel driver.

    • @eee@lemm.ee
      link
      fedilink
      11 year ago

      The US navy ran on windows xp for so long that they paid Microsoft to continue maintaining it after EOL.