[21853] in Athena Bugs
Re: Why is update_ws in /etc/athena?
daemon@ATHENA.MIT.EDU (John Hawkinson)
Fri Apr 18 13:22:46 2003
Date: Fri, 18 Apr 2003 13:22:43 -0400
From: John Hawkinson <jhawk@MIT.EDU>
To: Jonathan Reed <jdreed@MIT.EDU>
Cc: Greg Hudson <ghudson@MIT.EDU>, bugs@MIT.EDU
Message-ID: <20030418172243.GP27037@multics.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E9FF611.149129A2@mit.edu>
Jonathan Reed <jdreed@MIT.EDU> wrote on Fri, 18 Apr 2003
at 08:56:49 -0400 in <3E9FF611.149129A2@mit.edu>:
> > I'm kind of skeptical on the console login thing. People run it under
> > X all the time and I don't think there's any widespread perception
> > that that is not ok...
>
> Well, the PWOG does explicitly say that you should type C-p at the login
> screen and run it in console mode. And really, people should be reading
> the PWOG if they're going to run update_ws.
Designing the system with the expectation that people read documentation
is generally not a great plan. Even less of a good plan when the documentation
is supplementary information not shipped in /usr/athena/man. Add to that the
in my experience, basically no one reads or knows about the PWOG...
> I'm curious about this concept that "people don't know where update_ws
> is". A cursory dsgrep through OLC transactions reveals that of all of
> our questions mentioning update_ws, they were in two primary categories:
Try answering the SIPB phone or reading -c help. It's not every week,
but I think it's at least once/month.
--jhawk
