response 75 of 222:

May 18 12:42 UTC 2000

        disk full?

response 77 of 222:

May 18 22:19 UTC 2000

Er, programs.

response 79 of 222:

May 22 11:32 UTC 2000

        I often have the problem in #78.

response 81 of 222:

Jun 2 21:33 UTC 2000

I've had a problem with the conferences lately. I have to keep looking at the
same responses to some conferences 3 or 4 times. That's not bad when it's one
of the smaller conferences, but very annoying on agora.

response 83 of 222:

Jun 3 17:22 UTC 2000

        /var: write failed, file system is full

response 85 of 222:

Jun 3 18:58 UTC 2000

Newuser doesn't list all of the available shells.
I know that at least zsh is not listed, and it seemed like perhaps more were
also not listed (not as many as /etc/shells).

And chsh won't let you update the passwd database to zsh if you answer "no"
to when it prompts for either the creation of a .login (should be .zlogin,
I believe) or a .cshrc (again, pretty sure it should be .zshrc; .zlogin,
.zshenv, and .zshrc are the associated files, and though zsh is some sort of
derivation of bourne and c shells, I believe it only checks for the .z*'s).

response 87 of 222:

Jun 5 19:47 UTC 2000

The MOTD says:

M-Net is down temporarily. Read Item 32 in the M-Net Conference. -dpc

Can this message be changed to point people to the "mnet" conference?  
There is no conference on Grex called either M-Net or m-net, at least 
the way Backtalk understands conference names.

Thanks!

response 89 of 222:

Jun 6 01:45 UTC 2000

The terminal server was down.  I just rebooted it.

response 91 of 222:

Jun 6 06:06 UTC 2000

   Grex had a root breakin on another machine we use for things,
in which the vandal MAY have tried grabbing passwords from users
as they typed them in.

   Grex itself was NOT affected.  The machine that was, gryps, is
used for some functions like teaching the terminal server what to
do when it boots up, and some other things.  This machine was running
an an older copy of the FreeBSD operating system, and apparently,
a vandal saw this, and applied some exploit to it, and got in.  We
see clearly that the vandal installed some software to steal passwords
(called a network sniffer), but we do not know how much time the
vandal had to run this and harvest passwords.  It doesn't look like
they (it?) had much time, but we can't tell for sure.

   It is for this reason that we strongly suggest that anyone who
logged in between June 3rd and June 6th to change their passwords
now.  We know that whatever damaged this cyberslime did will be
minimized by folks changing their passwords.  IF YOU USE YOUR GREX
PASSWORD ON SOME OTHER MACHINE, CHANGE THAT TOO!

   Grex was down today as we looked at it, and there is no evidence
that the vandal did anything to Grex.  The vandal was not terribly
sophisticated, left tracks, and in general did not display either
the intelligence or panache needed to harm Grex itself.

   The FreeBSD machine is currently powered down.  We have another
machine waiting to be used which runs the OpenBSD operating system
which will be the new Gryps within a day or two.

   We do not think that anything else on the system has been 
damaged, but of course there is the possibility that we have missed
something, so if you see something weird, please tell staff right
away (mail to staff).

response 93 of 222:

Jun 6 12:33 UTC 2000

The dial-ins work intermittently

response 95 of 222:

Jun 6 16:53 UTC 2000

I just used !change from here to change my password, and wondered what
tpryan meant by it being "agrumentative", unless he really was referring
to all the extra words that have *grown* there. 

response 97 of 222:

Jun 6 17:41 UTC 2000

OK...I've never had that problem, so didn't think of that.

response 99 of 222:

Jun 6 17:56 UTC 2000

I use a password generating scheme that easily creates new ones based
on old ones, but so different that algorithm can't detect the relation.