Cedar-backup3

* Fix bug in setup.py (need to install extensions properly).

* Fixed doc/cback.1 .TH line to give proper manpage section.
* Updated README to more completely describe what Cedar Backup is.
* Fix a few logging statements for the collect action, to be clearer.
* Fix regression tests that failed in a Debian pbuilder environment.
* Add simple main routine to cli.py, so executing it is the same as cback.
* Added optional outputFile and doNotLog parameters to util.executeCommand().
* Display byte quantities in sensible units (i.e. bytes, kB, MB) when logged.
* Refactored private code into public in action.py and config.py.
* Created MySQL extension in CedarBackup2.extend.mysql.
* Created sysinfo extension in CedarBackup2.extend.sysinfo.
* Created Subversion extension in CedarBackup2.extend.subversion.
* Added regression tests as needed for new extension functionality.
* Added Chapter 5, Official Extensions in the user manual.

* Complete ground-up rewrite for 2.0.0 release.
* See doc/release.txt for more details about changes.

* Add experimental support for new Linux 2.6 ATA CD devices.
* SCSI id can now be in the form '[ATA:]scsibus,target,lun'.
* Internally, the SCSI id is now stored as a string, not a list.
* Cleaned up 'cdrecord' calls in cdr.py to make them consistent.
* Fixed a pile of warnings noticed by the latest pychecker.

* Removed extraneous error parameter from cback's version() function.
* Changed copyright statement and year; added COPYRIGHT in release.py.
* Reworked all file headers to match new Cedar Solutions standard.
* Removed __version__ and __date__ values with switch to Subversion.
* Convert to tabs in Changelog to make the Vim syntax file happy.
* Be more stringent in validating contents of SCSI triplet values.
* Fixed bug when using modulo 1 (% 1) in a few places.
* Fixed shell-interpolation bug discovered by Rick Low (security hole).
* Replace all os.popen() calls with new execute_command() call for safety.

* Fix boundaries calculation when using kernel >= 2.6.8 (closes: 16).
* Look for a matching boundaries pattern among all lines, not just the first.