• TrickDacy@lemmy.world
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    1 day ago

    The way these tools are designed, typically unless something goes wrong you need to understand basically none of it. And if something goes wrong, the resulting error messages normally at least give you something to search for in order to understand more

    • binarytobis@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 day ago

      Yesterday I installed a program to run windows games. The installation through the terminal spat out ten different types of “Error reading the jupitos bus” type messages that I simply could not parse, but they sounded grim and serious.

      But it ran just fine afterwards so those messages couldn’t have been that important?

      • hexagonwin@lemmy.today
        link
        fedilink
        arrow-up
        1
        ·
        8 hours ago

        in wine there are many partially implemented/stubs, which generate warning messages but usually work fine

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 day ago

      the resulting error messages normally at least give you something to search for

      lp0 on fire

      And:

      #include <errno.h>
      #include <stdio.h>
      
      int main (void) {
          errno=ENOANO;
          perror("");
          return 0;
      }
      

      Yields:

      $ ./a.out 
      No anode
      $