old-www/LDP/nag/node175.html

42 lines
1.7 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>Setting up getty</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node176.html">Providing UUCP Accounts</A>
<B>Up:</B> <A HREF="node174.html">Setting up your System </A>
<B> Previous:</B> <A HREF="node174.html">Setting up your System </A>
<BR> <P>
<H2><A NAME="SECTION0014510000">Setting up getty</A></H2>
<A NAME="uucpdialinuugetty"></A>
If you want to use a serial line as a dial-in port, you have to enable
a getty process on this port. However, some getty
implementations aren't really suitable for this, because you usually
want to use a serial port for dialing in and out. You therefore have
to make sure to use a getty that is able to share the line with
other programs like uucico, or minicom. One program that
does this is uugetty from the getty_ps package. Most
distributions have it; check for uugetty in your
/sbin directory. Another program I am aware of is Gert
Doering's mgetty, which also supports reception of facsimiles.
You can also obtain the latest versions of these from
sunsite.unc.edu as either binary or source.
<P>
Explaining the differences in the way uugetty and mgetty
handle logins is beyond the scope of this little section; for more
information, please refer to the Serial HOWTO by Grag Hankins, as well
as the documentation that comes along with getty_ps and
mgetty.
<P>
<BR>
<HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>