From: tjm@hrt213.brooks.af.mil (Tim Miller)
Subject: Re: patriot.mit.edu (vanity server alert)
Organization: AL/HRTI, Brooks AFB
	<1992Dec15.202923.9973@rat.csc.calpoly.edu>
	<9212161402.AA06659@hrt213.brooks.af.mil>
	<1992Dec16.193715.20487@rat.csc.calpoly.edu>
Date: Thu, 17 Dec 1992 14:31:21 GMT

On 16 Dec 92 19:37:15 GMT, asamonte@polyslo.csc.calpoly.edu (Just some loser...) said:

 A> And how do you know patriot would be any different.  According to what
 A> has been said it hasn't even been attempted to fix, so how are you going
 A> to know it's gonna break other things?

	Clue you in:

	System's Administrator's School of Hard Knock Rule of Thumb #1:

	1) If it ain't broke, don't fix it.
		Corrallary:  Don't touch anything you don't have to touch.

	"Broke" means that the following criteria are *not* met:
		1) It's running.
		2) The users can do what the users do without major
		   problems.
		3) Your chief user isn't yelling about something.

	System's Administrator's School of Hard Knock Rule of Thumb #2:

	2) If it is broken, wait until it gets to be a crisis, that
	   way you look like a saviour.

> > Oh, a few days, a week...Well atleast you're expedient in fixing it.
> > From mystroms post, he did not see it a a problem, nor did he show
> > any indication of wanting to fix it.

	Well, as mystrom has pointed out and you pointedly ignored, he
runs IRC, not the bloody machine.  Since he's not the sysadmin, there
really is *nothing* he can do.

 A> Oh I see, you wouldn't consider it broken huh?  Maybe a feature?  Doubtful.
 A> I wouldn't say it's working as it should.

	No, I consider it to be a DEC braindead ULTRIX.  

	For example:

/link pat*
Server: Patriot.mit.edu (8 Fastest draw in the East)

/admin patriot.mit.edu
-Patriot.mit.edu- ### Administrative info about Patriot.mit.edu
-Patriot.mit.edu- ### Mika Nystroem, Cambridge, Mass., U.S.A.
-Patriot.mit.edu- ### mnystrom@athena.mit.edu
-Patriot.mit.edu- ### MIT test server.

/w *patriot*
Search for: *patriot*
 Nickname     Channel Name                                          <User@Host>
 Shere       #ESPANOL 8 Shere                             <gjaque@146.83.3.129>
-Khan                 8 Khan                              <gjaque@146.83.3.129>
@apache         #viet 8 AH64                              <khang@140.183.6.115>
@YoYo        #ESPANOL 8 YoYo                              <gjaque@146.83.3.129>
-ed                   8 the standard text editor                               
                                             <friedman@nutrimat.gnu.ai.mit.edu>
 Jake         #Hotsex 8 Another Gentleman Loser   <gage0001@student.tc.umn.edu>
 horny                8 Steve Mosher - Sun USOPS WSU PCA TEST ENGINEERING      
                                                              <smosher@Sun.COM>
-Help      #twilight_zone 8 -=The Almighty Sphinx=-                      
                                                      <help@passion.njit.ed
   u>

	Seems like everyone using the server shows up as
user@host.domain; also, the administrative info gives the full domain,
as does /links, and user@athena.mit.edu is a valid address as well.
There doesn't seem to be anything wrong with the server, yet you call it
hacked.  It isn't.

	So what exactly is your problem?  

	Oh, that's right, it's personal.  I'm sorry, I forgot.

-- Cerebus <tjm@hrt213.brooks.af.mil>

"'Personal' as in a personal problem with someone else.  The matter of
 any personality disorders you might suffer is entirely private."