So, thanks telnet!
Apache won't serve certain files unless the permissions are just so, and he could not get them to fix them or give him a shell to do it himself. So he couldn't do his job.
I ended up telling him about the shell escape trick.
He was having a rough time, and nobody wanted to be the one to tell him he was going to be kicked by association, so it was lucky we had a workaround.
The sort of people who could do that back then generally had much better things to do with their time. And resources. When you’re dealing with idiots who only have access to dialup or their university computer lab, it doesn’t take much to stop them. It was just a bunch of 20 year olds trying to have fun. Not defense networks.
Was this, by chance, a .umn.edu dialup ?
Just curious ...
Back in the early 90s the local university used to have a free dial-up that you'd connect to via modem and then could telnet anywhere. You didn't need to be a student or anything. As a teenager I used this to connect to various shell accounts I had around, and to various MUDs. (This was in the pre-ISP days -- there was nobody in my area offering dial-up Internet at all.)
At some point they pulled this and made it for students only. But they had a dial-up gopher service for campus information and library access that was actually a telnet session to a gopher client on a SunOS machine somewhere.
But they didn't disable the telnet escape character.
So for a few months back then the way I got Internet access was to dial into the gopher client, hit ^], close the session to the gopher client, and open to anywhere else I chose. Eventually they closed this hole, too, but it was glorious for a while.