General * Make damn certain our Docbook markup is both _CORRECT_ and _CONSISTANT_. There's many places where the sections are very different. They should all be of this form. darkstar:~$ _EVERYTHING_ the user types Anything the screen prints that the user doesn't type. I've found several cases where the tag was used inside of a section. This is wrong and must be avoided. When the book goes to the publisher, all of those tags will be formatted one way for printing and the tags could be formatted another. Also, wrapping only applications in tags could make the reader wonder just how much they are supposed to type. * Aim to update references to kernel versions and Slackware versions to those used in the most recent release of Slackware. I've seen kernel 2.6.29.4 and Slackware 12.0.0 for instance. * more extensive CLI apps like v2.0 * no idea where the hell udev is covered in here, but we need to do a bit of talk about it. Nothing too advanced, and we definitely DO NOT want to imply that users should have to do much with udev. All of the asshattery out there with trying to automount shit with udev is, well, asshattery. * need to mention that /etc/udev/rules.d/ overrides an identically named file in /lib/udev/rules.d/ * need to mention persistent rules that are system-generated, especially in reference to how the admin might be misled into thinking that they are causing breakage... * need to point out that the persistent rules themselves are (according to upstream) a bad idea - not sure I completely agree, but there is a lot of potential for breakage, it seems... * Need to mention iptables somewhere - perhaps consolidate some bits from my iptables/netfilter presentations? --rworkman Chapter 2. Installation * Should we include some partitioning examples using gdisk since this tool is increasingly required with today's modern systems? Perhaps add it as an appendix and mention it within the partitioning section? Chapter 14. Networking * We should probably include a "screenshot" of netconfig somewhere.