|
| 1 | +# Day 02 – Linux Architecture, Processes, and systemd |
| 2 | + |
| 3 | +## Task |
| 4 | +Today’s goal is to **understand how Linux works under the hood**. |
| 5 | + |
| 6 | +You will create a short note that explains: |
| 7 | +- The core components of Linux (kernel, user space, init/systemd) |
| 8 | +- How processes are created and managed |
| 9 | +- What systemd does and why it matters |
| 10 | + |
| 11 | +This is the foundation for all troubleshooting you will do as a DevOps engineer. |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +## Expected Output |
| 16 | +By the end of today, you should have: |
| 17 | + |
| 18 | +- A markdown file named: |
| 19 | + `linux-architecture-notes.md` |
| 20 | + |
| 21 | +or |
| 22 | + |
| 23 | +- A hand written set of notes (Recommended) |
| 24 | + |
| 25 | +Your notes should be clear enough that someone new to Linux can follow them. |
| 26 | + |
| 27 | +--- |
| 28 | + |
| 29 | +## Guidelines |
| 30 | +Follow these rules while creating your notes: |
| 31 | + |
| 32 | +- Explain **process states** (running, sleeping, zombie, etc.) |
| 33 | +- List **5 commands** you would use daily |
| 34 | +- Keep it **short and practical** (under 1 page) |
| 35 | +- Use bullet points and short headings |
| 36 | + |
| 37 | +--- |
| 38 | + |
| 39 | +## Resources |
| 40 | +You may refer to: |
| 41 | + |
| 42 | +- Linux `man` pages (`ps`, `top`, `systemctl`) |
| 43 | +- Official systemd docs |
| 44 | +- Your class notes |
| 45 | + |
| 46 | +Avoid copying/pasting AI Generated content. |
| 47 | +Focus on understanding. |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +## Why This Matters for DevOps |
| 52 | +Linux is the base OS for almost every production system. |
| 53 | + |
| 54 | +If you know how processes and systemd work, you can: |
| 55 | +- Debug crashed services faster |
| 56 | +- Fix CPU/memory issues |
| 57 | +- Understand logs and service restarts confidently |
| 58 | + |
| 59 | +This knowledge saves hours during incidents. |
| 60 | + |
| 61 | +--- |
| 62 | + |
| 63 | +## Submission |
| 64 | +1. Fork this `90DaysOfDevOps` repository |
| 65 | +2. Navigate to the `2026/day-02/` folder |
| 66 | +3. Add your `linux-architecture-notes.md` file |
| 67 | +4. Commit and push your changes to your fork |
| 68 | + |
| 69 | +--- |
| 70 | + |
| 71 | +## Learn in Public |
| 72 | +Share your Day 02 progress on LinkedIn: |
| 73 | + |
| 74 | +- Post 2–3 lines on what you learned about Linux internals |
| 75 | +- Share one systemd command you found useful |
| 76 | +- Optional: screenshot of your notes |
| 77 | + |
| 78 | +Use hashtags: |
| 79 | +#90DaysOfDevOps |
| 80 | +#DevOpsKaJosh |
| 81 | +#TrainWithShubham |
| 82 | + |
| 83 | + |
| 84 | +Happy Learning |
| 85 | +**TrainWithShubham** |
0 commit comments