old-www/HOWTO/PLIP-1.html

46 lines
1.8 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>LINUX PLIP MINI-HOWTO: Introduction: what is PLIP and why should I use it?</TITLE>
<LINK HREF="PLIP-2.html" REL=next>
<LINK HREF="PLIP.html#toc1" REL=contents>
</HEAD>
<BODY>
<A HREF="PLIP-2.html">Next</A>
Previous
<A HREF="PLIP.html#toc1">Contents</A>
<HR>
<H2><A NAME="s1">1. Introduction: what is PLIP and why should I use it?</A></H2>
<P>There are many ways to create a connection between multiple hosts. PLIP,
like SLIP, allow a local connection between two machines, but uses the
parallel ports.
<P>Parallel ports transfer more than one bit at a time, this means it is
possible to achieve higher speeds than with a serial interface.
<P>The speed achieved depends completely on your hardware (CPU and parallel
port) and system load, in general it may be from 5 Kb/sec up to even
40 Kb/sec.
<P>The PLIP interface is fast enough to allow some decent tcp/ip functions,
like NFS. So, you may have a computer with all your Linux stuff and
another with only the minimal system, where you can mount all the rest
from the main machine.
<P>The disadvantage is that most users have only one parallel port, this
means that you won't be able to print and use PLIP together. Even with two
parallel ports it is impossible to print and use PLIP without using kernel
modules.
<P>This disvantage can be also eliminated, if you have two or more parallel
ports, applying a patch that you can find in this Mini-HOWTO.
<P>Finally I am now able to give a hopefully good way to set up a PLIP link
between DOS and Linux.
<P>I won't stress it enough: so far nobody reported a successful link between
Linux and Windows95.
<P>
<HR>
<A HREF="PLIP-2.html">Next</A>
Previous
<A HREF="PLIP.html#toc1">Contents</A>
</BODY>
</HTML>