Viewing and Editing File Content

# CHAPTER 5

Viewing and Editing File Content #

1. Introduction #

2. Learning Objectives #

• Quickly print file contents to the terminal using the cat command.

• Paginate and navigate massive text files using the less command.

• Extract the top or bottom lines of a log file using head and tail.

• Monitor live, updating server logs using tail -f.

• Edit configuration files using the beginner-friendly nano editor.

• Understand the basic operational modes of the advanced vim editor.

3. Reading Files (cat and less) #

cat /etc/hostname

*Use case:* Great for reading small, 5-line configuration files. *The Problem:* If you cat a 10,000-line server log, the text will scroll past your eyes at lightning speed, leaving you looking at only the very last page.

2. The less Command (The Pager): To read a large file, you use less. It opens the file in a clean, scrollable interface.

less /var/log/syslog

*Navigation in less:*

• Press Spacebar to scroll down one page.

• Press Up/Down Arrows to scroll line by line.

• Type /error to search the document for the word "error".

• Press q to quit and return to the terminal.

4. Surgical Reading (head and tail) #

• head: Prints the first 10 lines of a file.

  head -n 20 report.txt  # Prints the first 20 lines instead of 10
  ```
- **`tail`:** Prints the last 10 lines of a file.
  ```bash
  tail /var/log/auth.log  # Shows the most recent login attempts
  ```

**The Superpower: `tail -f` (Follow)**
If a web server is currently crashing, you want to watch the errors happen in real-time. By adding the `-f` flag, the terminal "locks on" to the bottom of the file. As the web server writes new lines to the log file, they instantly pop up on your screen live! (Press `Ctrl+C` to exit).

### 5. Editing Text: `nano` (The Beginner's Tool)
To change the text inside a file, you need a terminal text editor. `nano` is the easiest editor to learn because it has a menu at the bottom of the screen.

bash nano config.txt ``

1. 1. The terminal changes into a text editing window.

1. 3. At the bottom, you see shortcuts like ^O Write Out and ^X Exit. (The ^ symbol means the Ctrl key).

1. 4. To save: Press Ctrl + O, hit Enter to confirm the name.

1. 5. To close: Press Ctrl + X.

6. Editing Text: vim (The Professional's Tool) #

1. 1. Command Mode (Default): When you open a file (vim script.sh), you are in command mode. If you press the d key twice, you instantly delete a line of text.

1. 2. Insert Mode: To actually type text, you must press the i key. At the bottom left, it will say -- INSERT --. Now you can type normally.

1. 3. Escaping: To save, you must press the Esc key to return to Command mode.

1. 4. Saving and Quitting: Type a colon :, followed by wq (Write and Quit), and press Enter.

• Never edit production configurations directly: Before using nano or vim to edit a critical system file (like /etc/ssh/sshdconfig), always use cp to make a backup copy first (cp sshdconfig sshd_config.backup). If your edits break the server, you can instantly restore the original text.

1. 1. Open a terminal. Type ping google.com > network.log &. (This runs a ping command silently in the background and writes the output to a text file).

1. 2. Type tail -f network.log.

1. 4. Press Ctrl + C to stop watching.

1. 5. (Cleanup: Type killall ping to stop the background process).

1. 1. What is the fundamental operational difference between reading a file with cat versus reading a file with less?

1. 2. Detail the exact sequence of keystrokes required to open a file in vim, type the word "Hello", save the file, and exit back to the terminal.

• Q: A junior engineer complains that when they run cat on a massive 5GB database dump file, the terminal freezes for 10 minutes. Explain why this happens and what command they should use instead to safely view the contents.

• Q: Explain the paradigm of "Modes" within the vim text editor. Differentiate between Command Mode and Insert Mode.

• Q: Walk me through the terminal commands required to view only the top 15 lines of a script file named deploy.sh.

16. Next Chapter Recommendation #