BIND 10 #1901: be consistent with bind10 or boss or bob name

[BIND 10 Development]

#1901: be consistent with bind10 or boss or bob name
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  Boss of BIND  |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130205
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  9             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:
                                     |  Medium
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 Ok, I guess this is ready for review, due to all the references and uses
 of bob, Bob, BoB, boss, Boss, BOSS, bind10_src, etc. the diff has gotten
 insanely large, but most of it is advanced search&replace.

 I recommend the reviewer takes it in chunks;
 - first commit (cfa26ab8df9b533d32b8dd5aa405bf237bb58f12) is the majority
 of file renaming (barring a few instances which I forgot at the time).
 This one breaks everything as internally nothing is updated
 - Then commits 826ac1b1e637a6aa8b5763c4b810755ac0551446 to
 6aa1c3cc7dbb55d32304ada9b88037346ba929b0 are the replacements of code
 uses.
    - in general it's something like bind10_src -> b10-init, Boss and Bob
 to Init, local variable names such as bob and boss to b10_init
    - made a small import workaround since python doesn't like hyphens in
 code and we import b10-init in a number of tests
    - Left alone the 'bind10' directory name, and the BIND10_ log message
 prefix.
 - commit 476b3eff5488d89b03d7ac34830ad52973e9b0bd updates the config file
 version to 3, and automatically replaces Boss with Init in existing
 configurations. This is a one-way deal which we need to mention in the
 changelog
 - final few commits are some small cleanups (the bind10 script shane
 proposed doesn't work when installed as b10-init is in libexec, so I just
 take it from PATH, not sure if that is the correct way though)


 Proposed changelog:
 [func]*         jelte
 The main initializer script (formerly known as either 'bind10', 'boss', or
 'bob'), has been renamed to b10-init (and Init in configuration).
 Configuring which components are run is henceforth done through
 '/Init/components', and the sbin/bind10 script is now simply a shellscript
 that runs b10-init. Existing configuration is automatically updated. NOTE:
 once configuration with this update has been saved (by committing any new
 change with bindctl), you cannot run older versions of BIND 10 anymore
 with this configuration.

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