التدفقات القياسية وإعادة التوجيه

In the Linux terminal, commands communicate using 'standard streams'. Think of these as default channels for data to flow in and out of a program.

• Standard Input (stdin): Where a command gets its input from (usually keyboard).
• Standard Output (stdout): Where a command sends its normal results (usually screen).
• Standard Error (stderr): Where a command sends its error messages (usually screen).

These streams let you control how commands interact!

When a command successfully runs and produces a result, that result is sent to standard output. By default, stdout is displayed directly on your terminal screen.

For example, when you use the echo command, its output goes to stdout.

The > (greater than) symbol is used to redirect standard output from the screen to a file. If the file doesn't exist, it's created. If it already exists, its content is overwritten!

This is useful for saving command results for later.

Try running this example. Notice how the echo command's output isn't shown on screen, but stored in message.txt. Then, cat displays the file's content.

What if you want to add output to a file without deleting its existing content? That's where >> comes in!

The >> (double greater than) operator redirects standard output to a file, appending the new content to the end of the file.

Let's add another line to our message.txt file without losing the first line. Run the code and observe the output of the final cat command.

Standard input is the channel through which a command receives data. By default, stdin comes from your keyboard – you type commands or input values directly.

Some commands are designed to process input that you provide, or that comes from another source.

The < (less than) symbol allows you to redirect standard input from a file instead of the keyboard. This is incredibly useful for feeding data from a file into a command that expects input.

The command will then process the file's content as if you typed it.

The wc -l command counts lines. Here, we'll create a file and then use < to make wc -l read its input directly from that file.

When a command encounters a problem or an error, it sends diagnostic messages to standard error. Like stdout, stderr is typically displayed on your screen by default.

Keeping stderr separate from stdout helps you easily spot errors.

To redirect standard error to a file, you use the file descriptor 2 followed by the redirection operator: 2>.

This lets you capture error messages in a log file, keeping your main output clean. You can also redirect stdout and stderr to the same file using &> or > file 2>&1.

Let's try to list a directory that doesn't exist. We'll redirect the error message to a file named errors.log.

The | (pipe) symbol is one of the most powerful features of the Linux shell. It connects the standard output (stdout) of one command directly to the standard input (stdin) of another command.

This allows you to create complex data processing pipelines by chaining simple commands together.

Here, the output of ls -l (a detailed list of files) is 'piped' as input to wc -l (word count - lines). This effectively counts how many items are listed by ls -l.

Consider the following sequence of commands:

echo "Apple" > fruits.txt
echo "Banana" >> fruits.txt
echo "Cherry" > fruits.txt
cat fruits.txt

What will be the final content of fruits.txt displayed by the cat command?

Great job! You've learned the fundamentals of standard streams and how to redirect them:

• Standard Streams: stdin (input), stdout (normal output), stderr (error output).
• >: Redirects stdout to a file, overwriting it.
• >>: Redirects stdout to a file, appending to it.
• <: Redirects a file's content to a command's stdin.
• 2>: Redirects stderr to a file.
• | (Pipe): Connects the stdout of one command to the stdin of another.

These techniques are essential for powerful command-line workflows. Next, you'll learn how to filter text using the mighty grep command!