Mission 355

Package origin review

Compare installed package metadata with package-owned files and change logs.

Package/process ops
8 minutes Admin Lesson 355 of 360
aptdpkggrep
Lesson 355 of 360 0/360 lessons 0/17 missions Package/process ops · 8 minutes
0%
Continue View profile
Ops lab terminal Training lab
New learnerrank 0XP 0%complete
learner@clairos:/home/learner $ Unix ops lab: type a command, press Enter
Instructions 8 minutes

Click any instruction for the command details, the why, and the common mistake to avoid.

Read package origin

Run apt policy fake-nginx.

apt policy fake-nginx
List package-owned files

Run dpkg -L fake-nginx.

dpkg -L fake-nginx
Find installation evidence

Run grep install /var/log/dpkg.log.

grep install /var/log/dpkg.log
Lesson support

What to notice while you play.

Objective

Build repeatable confidence with tracing an installed package to its files and history.

Hint

Start with apt policy fake-nginx, inspect the result, then continue in order.

Why it matters

Tracing an installed package to its files and history helps operators explain what they know before they change anything.

Common mistakes
  • Skipping the output that proves tracing an installed package to its files and history.
  • Changing several things before recording a baseline.
Reference

Commands in this lesson.

grep [-i] <text> <file>

Find literal text inside a file.

apt|dpkg|brew

Inspect simulated Linux and macOS package metadata.