Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

Input redirection: <

The < (less-than) symbol lets you control where a process gets its input from. For example, you’re used to giving input to Bash with your keyboard, one command at a time. Let’s try giving bash input from a file, instead!

Assume I have a file named commands.txt with the following content (I’m using cat here to print out my example file):

# cat commands.txt
pwd
echo $SHELL
cd /tmp
pwd

These are valid shell commands, as far as Bash is concerned, so I’m going to launch a new Bash process and use this file as standard input:

# bash < commands.txt
/tmp/gopsinspect
hello there, friends
/bin/bash
/tmp

Instead of prompting me for input and waiting until I give it, Bash reads and executes one line at a time: it reads input from the file until it comes across a newline (\n) character, and just as if you’d hit the RETURN key, it executes the command.

Standard output is still going back to our terminal. Let’s change that.

...