Those who have been following my Twitter feed know most of this, but here’s the status on this book.
Why are things written out of order? Depends on what I’m doing at the time. Also, some chapters can be written without Internet access. Otherwise, I write chapters in order.
I believe I’ve chopped down the outline to where it needs to be for a book roughly the same size as Absolute FreeBSD. Chapter titles are subject to change. Heck, everything is subject to change.
1: Community Support
2: Installation Prep
3: Installation Walk-Through
4: Post-Install Setup
6: User Management
7: Root, and how to avoid it
8: Disks & Filesystems
9: More Filesystems
10: OpenBSD Security Features
11: IPv4 & IPv6
12: Network Connections
13: Software Management
16: Daemons (sensorsd, snmp, etc)
17: Desktop OpenBSD (cwm, tmux, etc)
18: Kernel Configuration
19: Building Custom Kernels
21: Packet Filtering
22: managing PF
Trimming to this length hurt, but one of my critical design goals is to write a book small enough to hold in the bathtub. I might sometimes recommend books that exceed that limit, but they have to be freaking awesome books.
One thing that helps is Peter Hansteen’s Book of PF. It didn’t exist when the first edition of AO came out, so I needed to do pretty exhaustive coverage into PF. My coverage of primordial PF took three chapters in the first edition, and PF and family has roughly doubled its features since then. He does an excellent deep dive into PF, so I can reduce those chapters.
I’ve talked about word count before, but I need to stop doing that. The book has flailed around enough that the number of words I write isn’t exactly useful. I wrote 7,000 anti-words on Chapter 17 before sending it to Henning, for example.
On the plus side, the AO2e narrator now sounds a little less Dexter Morgan and a little more BOFH. That’s probably a good thing.Stalk me on social media