Modifying the syslog support to not install /etc/syslog.conf affects
many manifest.  Just ignore it for now.

The original method of overriding the use of /etc/syslog.conf failed
because of a duplicate declaration of the file resource.  This
restructuring should solve that problem.

This change does not affect the current usage of the module.  It does
allow manifests to choose to retire /etc/syslog.conf in favor or
fragments in /etc/rsyslog.d to control the syslog activity.  One
default fragment, 90-local.conf, that writes syslog messages
locally.

This change also include a fragment define that is used for the
management of rsyslog fragments.

* since it's too easy to use a hyphen--which is invalid

These files are supposed to have different permissions (0660 for
btmp and 0664 for wtmp), which isn't possible using a single united
base::newsyslog::config stanza.  Separate them into two stanzas
with the correct permissions.

We keep running into other packages that depend on it, which makes
removing it unnecessarily difficult.

Map Ubuntu raring to wheezy instead of squeeze for the Stanford-local
Debian repositories.

Avoid too many levels of redirection through variables and
variables with studly-caps in favor of a single variable.
Default to the jessie and sid package, since that's what we'll
use going forward.  Avoid using regexes; this isn't really a
regex match, and we'll soon be able to delete the lenny case
anyway.

Two versions of puppet dev config one for puppetca-dev and
one for lsdb-dev (this is for testing the PuppetCA migration to frankoz1).

Replaced frankoz-dev with two servers: frankoz1-dev and
frankoz2-dev. Updated the Puppet conf file to reflect this change.

Try to stick with the same method of a conditional blank line.

Comment the protocol restriction and the explicit enabling of
UsePrivilegeSeparation on Red Hat.

This should be next to the port configuration, since it's related,
and is important enough that it needs to be at the top of the file
so that it can be easily found.  It also doesn't make sense after
per-user settings.

If no ListenAddress directives are specified, then sshd will list for
incoming connections at all addresses. You can alter this by specifying
the listen_addresses parameter. For example:
listen_addresses => '192.168.1.1,192.168.2.1'