The Unix Workbench Book (My solutions)

You can read the book from here

Contents

• Introduction

• Before you start...

• Chapter 3: Command Line Basics

• Chapter 4: Working with Unix

• Chapter 5: Bash Programming

• Chapter 6: Git and Github

• Chapter 7: Nephology

• Contributions

---

Introduction

I've always wanted to know more than just the command line basics that we used to study in university. I wanted to explore more in Linux and aquire the skills of shell scripting since I'm interested in embedded systems and want to make my own build systems and set a professional environment for myself. Then eventually after searching for a gentle source, I found my way to this elegant and powerful book "The Unix Workbench". It's a very good start if you want to grasp the concepts of shell scripting quickly and get your hands dirty on many useful and practical examples.

---

Before you start...

• Make sure you approach the book exercises before checking these solutions.

• These solutions are not intended to be used for cheating but as a guide.

• Sections that are not mentioned have no exercises.

---

Chapter 3: Command Line Basics

• 3.1.2 Exercises

• 3.2.2 Exercises

• 3.3.2 Exercises

• 3.4.2 Exercises

---

Chapter 4: Working with Unix

• 4.1.2 Exercises

• 4.2.2 Exercises

• 4.3.7 Exercises

• 4.6.2 Exercises

---

Chapter 5: Bash Programming

• 5.1.2 Exercises

• 5.2.2 Exercises

• 5.3.2 Exercises

• 5.4.5 Exercises

• 5.5.2 Exercises

• 5.6.2 Exercises

• 5.7.5 Exercises

• 5.8.4 Exercises

• 5.9.5 Exercises

---

Chapter 6: Git and Github

• 6.3.2 Exercises

• 6.4.4 Exercises

• 6.5.2 Exercises

• 6.6.6 Exercises

---

Chapter 7: Nephology

• 7.4.5 Exercises

---

Contributions

Everyone is welcome to contribute to this repo

Types of contribution:

1. Fixing a typo.

2. Introducing a more interesting solution.

3. Solving a new Exercises section in the book.

4. Solving unsolved questions.

Steps of contribution:

1. Fork this repo.

2. Clone your fork on your local machine.

3. Make sure your master is up-to-date then make a new branch.

4. Add your change.

5. Push your new branch to your repo on GitHub.

6. Create a pull request to my repo (base is my master and head is your new branch).

Notes on contribution

1. If you are solving a new Exercises section, stick to the naming convention in this repo.

2. If you are introducing a more interesting solution, don't remove my own but concatenate to it. For example:

   # My solution

   A more interesting solution:

   # Your solution