--=-=-= Content-Transfer-Encoding: quoted-printable Brad N Bendily <[EMAIL PROTECTED]> writes:
> I was with COX during the conversion, being a system admin, I didn't > think it went all that bad. I know what it's like to convert your > systems and network over to something else. I've never experienced > a system conversion on such a large scale. I would never have > expected COX to keep the system up and running 24/7 during this time. I worked for Charter and actually did an @HOME conversion in Montgomery, AL. I thought Cox's went o.k. considering how difficult a cutover it is. What I did was a fraction of the users/systems Cox had to transition. There was only about 2 days worth of trouble here in New Orleans. Of course I was able to surmise what the problem was when everything went south (DHCP server issues) and just statically assigned my IP and DNS servers on my edge router until things settled down. This was in the New Orleans area. There's a cox engineer on the nolug list but I doubt he'll be able to answer any questions that relate to a pending lawsuit. =2D-=20 Scott Harney<[EMAIL PROTECTED]> "...and one script to rule them all." gpg key fingerprint=3D7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQA+hLzv8CR9pgvHlOURAhPSAJ9h12RhZxxmSMZqadGdQ8aAVCSoowCgkk2X vqv3xG+h1vMx7sPLueYJs3Q= =mIDL -----END PGP SIGNATURE----- --=-=-=--
