I’ve been setting up a new Proxmox server and messing around with VMs, and wanted to know what kind of useful commands I’m missing out on. Bonus points for a little explainer.

Journalctl | grep -C 10 'foo' was useful for me when I needed to troubleshoot some fstab mount fuckery on boot. It pipes Journalctl (boot logs) into grep to find ‘foo’, and prints 10 lines before and after each instance of ‘foo’.

    • Will@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 days ago

      For interactive editing, the keybind alt+. inserts the last argument from the previous command. Using this instead of $_ has the potential to make your shell history a little more explicit. (vim $_ isn’t as likely to work a few commands later, but vim actual_file.sh might)

        • pssk@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          2 days ago

          You can use M-. instead of $_ to insert last param of last command. You can also access older commands’ param by repeated M-. just like you would do for inserting past commands with up arrow or C-p

      • wheezy@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        2 days ago

        I have my .bashrc print useful commands with a short explanation. This way I see them regularly when I start a new session. Once I use a command enough that I have it as part of my toolkit I remove it from the print.