Hello!

I am pleased to announce a new version of my Linux Command Line Computing ebook.

This ebook aims to teach Linux command line tools and Shell Scripting for beginner to intermediate level users. The main focus is towards managing your files and performing text processing tasks. Plenty of examples are provided to make it easier to understand a particular tool and its various features. There are 200+ exercises to help you practice what you’ve learned and solutions are provided for reference. I hope this ebook would make it easier for you to discover CLI tools, features and learning resources.

Links:

I would highly appreciate it if you’d let me know how you felt about this book. It could be anything from a simple thank you, pointing out a typo, mistakes in code snippets, which aspects of the book worked for you (or didn’t!) and so on. Reader feedback is essential and especially so for self-published authors.

Happy learning :)

    • ____@infosec.pub
      2·
      7 months ago

      sed harbors no demon beasts, in my experience.

      On the other hand, by default using sed -i is where the demons come in.

      No, sed, NOT in place. Not the first time. Show me what you want to do based on the instructions I gave you, and then we’ll talk about letting you play with the real data.

    • learnbyexample@programming.devOPEnglish
      2·
      7 months ago

      Is it regex or sed/awk syntax (or both) that gives you trouble?

      I had similar reaction and didn’t even try to learn them for years - then I caught the stackoverflow craze of answering CLI questions (and learning from others).

      • CosmicTurtle0@lemmy.dbzer0.comEnglish
        4·
        7 months ago

        I am pretty okay with regex. Enough that I can do what I want.

        sed/awk I’ve used on occasion, usually sed to change something in a pipeline.

        I still feel like I’m casting a demon.