# Examples for the tcpdump and dig man pages

DevFeed: [Examples for the tcpdump and dig man pages](<https://devfeed.tech/articles/examples-for-the-tcpdump-and-dig-man-pages-21126.md>)

Original publisher: [Read original article](<https://jvns.ca/blog/2026/03/10/examples-for-the-tcpdump-and-dig-man-pages/>)

Author: Julia Evans

Published: 2026-03-10T00:00:00Z

Content type: article

Language: en

Sources: [Julia Evans](<https://devfeed.tech/sources/julia-evans.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>)

Tags: [beginners](<https://devfeed.tech/tags/beginners.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [examples](<https://devfeed.tech/tags/examples.md>), [learning](<https://devfeed.tech/tags/learning.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [tool](<https://devfeed.tech/tags/tool.md>), [writing](<https://devfeed.tech/tags/writing.md>)

## AI overview

The article describes adding beginner-friendly examples to the dig and tcpdump man pages. It explains why accurate, reviewed official documentation is valuable and notes that maintainers can provide useful details that are easy to miss. The author also describes using a basic Markdown-to-roff script for man-page updates.

## Source excerpt

Hello! My big takeaway from last month's musings about man pages was that examples in man pages are really great, so I worked on adding (or improving) examples to two of my favourite tools' man pages. Here they are: the dig man page (now with examples) the tcpdump man page examples (this one is an update to the previous examples) the goal: include the most basic examples The goal here was really just to give the absolute most basic examples of how to use the tool, for people who use tcpdump or dig infrequently (or have never used it before!) and don't remember how it works. So far saying "hey, I want to write an examples section for beginners and infrequent users of this tools" has been working really well. It's easy to explain, I think it makes sense from everything I've heard from users about what they want from a man page, and maintainers seem to find it compelling. Thanks to Denis Ovsienko, Guy Harris, Ondřej Surý, and everyone else who reviewed the docs changes, it was a good experience and left me motivated to do a little more work on man pages. why improve the man pages? I'm interested in working on tools' official documentation right now because: Man pages can actually have close to 100% accurate information! Going through a review process to make sure that the information is actually true has a lot of value. Even with basic questions "what are the most commonly used tcpdump flags", often maintainers are aware of useful features that I'm not! For example I learned by working on these tcpdump examples that if you're saving packets to a file with tcpdump -w out.pcap, it's useful to pass -v to print a live summary of how many packets have been captured so far. That's really useful, I didn't know it, and I don't think I ever would have noticed it on my own. It's kind of a weird place for me to be because honestly I always kind of assume documentation is going to be hard to read, and I usually just skip it and read a blog post or Stack Overflow comment or ask a f