* 'Priv' would never have been shown as a channel name for +p channels.

* Opers with a small o in their O:Line flags were being propagated as a big O
* New command line option -x is for 'network debug' which will verbosely spit
  out synch info to the network via GLOBOPS.  This will spam a network like
  crazy, so please don't use it unless you've been instructed to.  This is to
  assist in debugging of misbehaving servers (read: software) over the network.
* Rewrote this.setusermode(), because it was a mess.
* Began work on breaking out usermodes into more discrete sections ala Bahamut,
  in particular:
        +w (Users) Allows the user to receive all WALLOPS messages.
        +b (Opers) User may receive CHATOPS messages.
        +g (Opers) User may receive GLOBOPS messages.
        +s (Users) Reception of variou server messages, including KILL.
        +c (Opers) Receive client connecting/disconnecting messages.
        +r (Opers) Receive 'rejected' client messages (i.e. unregd clients)
        +k (Opers) Receive server kill messages.
        +y (Opers) Observe STATS/INFO/LINKS/etc requests for possible abuse.
        +d (Opers) Can receive DEBUG notices.
        +n (Opers) For reception of 'routing' notices.
* Because of this, WALLOPS is now an oper only command.
* Replaced oper_notice() with umode_notice(), which writes out to all users
  of a particular user mode.
* CHATOPS, GLOBOPS, and GNOTICE now all work properly.
* Some appropriate messages are broadcast across the network, including more
  informative server messages (i.e. remote CONNECT, SQUIT, etc.)
* Let other opers know that a user is doing /EVAL.
* Add a kludge for 3.10 machines so that they'll mswait() longer, thus won't
  time out as quickly, hopefully giving them at least a few weeks worth of
  uptime.  The downside to this is that they run slower, alas.  (They probably
  should anyway, considering they don't have select() to throttle CPU usage.)