I’ve got to confess, I have for years been guilty if not reading the documentation. I simply go with the flow and hope it works…

But not anymore! And why the change you may ask? We’ll, I’m reading the f…ing documentation on Rocky linux and I’m just blown away from the amount of great information!

If you’ve been guilty of not reading the documentation, let me me know what changed it for you

If you’re not reading the documentation, this is your time to confess!

  • yesman@lemmy.worldEnglish
    26·
    8 hours ago

    It’s weird that Linux certification requires rote-memorization of commands. The only people who make any effort to memorize commands are newbies and people studding for exams. You will always have access to bash history, man, and --help, even from an offline machine.

    Every command I’ve memorized is simply the natural process of repetition. Is that your experience?

    • med@sh.itjust.worksEnglish
      2·
      4 hours ago

      Yes. But also, despite having done it literally thousands of times, I still can’t tell you which way round to put the target and the link name for a softlink on the first go.

      My first guess is always

      ln -s $NAME $TARGET

      No amount of repetition will fix this.

      • shrugs@lemmy.worldEnglish
        1·
        2 hours ago

        My trick to remember:

        You can link to a target without giving a name to the link. ln will use the basename of the target file then. You can’t create a link without a target, so target has to go first since it’s not optional. Did it for me

      • Bobby Turkalino@lemmy.yachtsEnglish
        1·
        3 hours ago

        I used to have that problem with ln until I realized it’s essentially the same ordering as cp: source, then destination. The source being the existing file that you’re linking to, and the destination being the link that you’re creating