BIND 10 #2305: Document bindctl in the BIND 10 guide

[BIND 10 Development]

#2305: Document bindctl in the BIND 10 guide
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  jreed
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:         |  Sprint-20121120
  medium                             |            Resolution:
                  Component:  bind-  |             Sensitive:  0
  ctl                                |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  7
            Defect Severity:  N/A    |           Total Hours:  1.25
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => jreed


Comment:

 Replying to [comment:10 jreed]:
 > I made a variety of minor changes. See commit
 3d71b86e777c7280043a1191bbeb0bb115f88078  -- please review the content
 changes in the diff.
 >

 look good, thanks.

 I noticed one more small issue there; in the section about
 default_user.csv, it said 'stores username and password for logging in a
 file', which would suggest it would be something about logfiles. Changed
 it to 'for logging in in a file' (i.e. double in).

 > I also have a few comments:
 >
 > In the bindctl_command_arguments section, maybe write about it before
 examples. (Currently it just uses examples to explain it.)
 >

 changed that section, is this better?

 > ", to add and remove elements."  (line 1686) what is this for? Reads
 strange or maybe is missing some content?
 >

 reworded.

 > Are the brackets in the list examples [value] required or optional? (See
 around line 1683)
 >

 also reworded (and some more in that paragraph)

 > Also the boss chapter examples are shown before bindctl is taught. Maybe
 split the boss chapter up into two chapters?
 >

 Yes, but maybe we should discuss that a bit (i'm thinking that initially
 we should only talk about boss as some component that runs the rest, and
 how to start the entire system. Then discuss Boss as a module in a
 separate chapter (i.e. perhaps simply make 3.2 its own chapter to be put
 either after chapter 7 or 8)

-- 
Ticket URL: <http://bind10.isc.org/ticket/2305#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development