<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9"> <TITLE>The Linux UUCP HOWTO: Requirements</TITLE> <LINK HREF="UUCP-HOWTO-4.html" REL=next> <LINK HREF="UUCP-HOWTO-2.html" REL=previous> <LINK HREF="UUCP-HOWTO.html#toc3" REL=contents> </HEAD> <BODY> <A HREF="UUCP-HOWTO-4.html">Next</A> <A HREF="UUCP-HOWTO-2.html">Previous</A> <A HREF="UUCP-HOWTO.html#toc3">Contents</A> <HR> <H2><A NAME="s3">3. Requirements</A></H2> <P> <!-- UUCP!requirements --> <P> <H2><A NAME="ss3.1">3.1 Hardware </A> </H2> <P> <!-- UUCP!requirements!hardware --> <P>There are no specific hardware requirements for UUCP under Linux. Basically any Hayes-compatible modem works painlessly with UUCP. <P>In most cases, you'll want the fastest modem you can afford, i.e. 56000 bps actually. In general, you want to have a 16550 UART on your serial board or built into your modem to handle speeds of above 9600 baud. <P>If you don't know what that last sentence means, please consult the <EM>comp.dcom.modems</EM> group or the various fine modem & serial communications FAQs & periodic postings on USENET. <P> <H2><A NAME="ss3.2">3.2 Software </A> </H2> <P> <!-- UUCP!requirements!software --> <P>UUCP for linux is available everywhere, for example on sunsite.unc.edu. But before trying to get any version, try to install & make your current uucp work ; there're many little differences between each linux distribution, therefore it's easier for you to configure/install your distribution's UUCP package rather than editing sources for some options, setting the right paths & permissions, installing, etc. <P>But if you prefer sources ... <P> <P> 1) Unpack <P> <P>To extract a gzip'd tar archive, I do the following: <PRE> gunzip -c filename.tar.z | tar xvf - </PRE> A "modern" tar can just do a: <PRE> tar -zxvf filename.tgz </PRE> <P> <P> 2) Run "configure" <P> <P>Type <CODE>"sh configure"</CODE>. <P>The configure script will compile a number of test programs to see what is available on your system & will calculate many things. <P>The configure script will create <CODE>conf.h</CODE> from conf.h.in & <CODE>Makefile</CODE> from Makefile.in. It will also create config.status, which is a shell script which actually creates the files. <P> <P> 3) Decide where to install <P> <P>Rather than editing the Makefile.in file in the sources you can get the same effect by: <P> <PRE> "configure --prefix=/usr/lib" </PRE> <P> <P> 4) Edit "policy.h" for your local system <P> <P> <UL> <LI> - set the type of lockfiles you want (HAVE_HDB_LOCKFILES) </LI> <LI> - set the type of config files you want built in (HAVE_TAYLOR_CONFIG, HAVE_V2_CONFIG, HAVE_HDB_CONFIG)</LI> <LI> - set the type of spool directory structure you want (SPOOLDIR_HDB)</LI> <LI> - set the type of logging you want (HAVE_HDB_LOGGING)</LI> <LI> - set the default search path for commands (I added /usr/local/bin to mine)</LI> </UL> <P> <P> 5) Then compile & install the software <P> <P> <UL> <LI>Type <CODE>"make"</CODE> to compile.</LI> <LI>Type <CODE>"make install"</CODE> to install.</LI> </UL> <P> <HR> <A HREF="UUCP-HOWTO-4.html">Next</A> <A HREF="UUCP-HOWTO-2.html">Previous</A> <A HREF="UUCP-HOWTO.html#toc3">Contents</A> </BODY> </HTML>