Return-Path: owner-LDP-L@cornell.edu
Received: from listproc.mail.cornell.edu (LISTPROC.MAIL.CORNELL.EDU [132.236.56.14]) by keos.Helsinki.FI (8.6.9/H46) with SMTP id RAA07708 for <LARS.WIRZENIUS@CS.HELSINKI.FI>; Tue, 13 Dec 1994 17:17:07 +0200
Received: from listproc.mail.cornell.edu ([127.0.0.1]) by listproc.mail.cornell.edu with SMTP id <95442-2>; Tue, 13 Dec 1994 09:58:20 -0500
Received: from cornell.edu ([132.236.56.6]) by listproc.mail.cornell.edu with SMTP id <95402-2>; Tue, 13 Dec 1994 09:57:54 -0500
Received: from cornell.edu (PHQUERY) by cornell.edu with cornell-phquery id <372768-3>; Tue, 13 Dec 1994 09:57:48 -0500
Received: from burdell.cc.gatech.edu ([130.207.3.207]) by cornell.edu with SMTP id <372766-6>; Tue, 13 Dec 1994 09:57:28 -0500
Received: from forge.cc.gatech.edu (gregh@forge.cc.gatech.edu [130.207.9.19]) by burdell.cc.gatech.edu (8.6.9/8.6.9) with ESMTP id JAA17601 for <LDP-L@cornell.edu>; Tue, 13 Dec 1994 09:57:20 -0500
Received: (from gregh@localhost) by forge.cc.gatech.edu (8.6.9/8.6.9) id JAA16728 for LDP-L@cornell.edu; Tue, 13 Dec 1994 09:57:19 -0500
Message-Id: <199412131457.JAA16728@forge.cc.gatech.edu>
Date: 	Tue, 13 Dec 1994 09:57:19 -0500
Reply-To: LDP-L@cornell.edu
Sender: owner-LDP-L@cornell.edu
From: gregh@cc.gatech.edu (Greg Hankins)
To: Linux Documentation Project writers <LDP-L@cornell.edu>
Subject: Re: Some comments
In-Reply-To: <9412121402.AA12568@thokk.cs.cornell.edu> from "Matt Welsh" at Dec 12, 94 09:02:12 am
Content-Type: text
X-PH: V4.1@cornell.edu (Cornell Modified) 
X-Mailer: ELM [version 2.4 PL23]
X-Listprocessor-Version: 7.1 -- ListProcessor by CREN
Content-Length: 1147
Status: RO
X-Status: 

Matt Welsh writes:
>Is he wrong or right? If wrong, what is he doing wrong that won't allow
>him to use gettyps? What's wrong with documenting mgetty if other people
>seem to have less problems with it?

mgetty and getty_ps are almost a religeous issue.  My main reason for not
documenting mgetty is the fact that it doesn't follow the Linux standard
of using cua and ttyS devices.  I am going to incorportate mgetty stuff
somehow in the next version.  Also, the mgetty documentation is really good
and doesn't really need any supplementing, like the getty_ps docs do.

I have no idea what he's doing wrong for getty_ps.  I'm not convinced mgetty
gives people less problems, either.  What I'm thinking of doing is just
discussing the merits of each package, and then letting the user decide which
one he wants to use.

Greg

-- 
"Wenn ist das Nunstuck git und Slotermeyer? | Greg Hankins (gregh@cc.gatech.edu)
Ja! Beiherhund das Oder die Flipperwaldt    | Georgia Tech College of Computing,
gersput!" - World's Funniest Joke           | Computing and Networking Services 
<A HREF="http://www.cc.gatech.edu/staff/h/Greg.Hankins/">Greg Hankins</A>

