LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-08-11 14:23:15 +00:00
parent 7f5e7030c1
commit 3647cb91a0
2 changed files with 422 additions and 103 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
View File

@ -1384,7 +1384,7 @@ Applies to all the operating sytems where PHP is ported. </Para>
PLIP-Install-HOWTO</ULink>,
<CiteTitle>PLIP Install HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: June 2000</CiteTitle>.
<CiteTitle>Updated: August 2000</CiteTitle>.
How to install a GnuXXPIPELinux distribution on a computer without
Ethernet card, nor cdrom, but just a local floppy drive and a remote
nfs server attached by a Null-Modem parallel cable. </Para>

523
LDP/howto/linuxdoc/PLIP-Install-HOWTO.sgml
View File

@ -10,7 +10,7 @@
<title> PLIP Install HOWTO
<author>Gilles Lamiral, <tt>lamiral@mail.dotcom.fr</tt>
<date>v1.22, 16 June 2000
<date>v1.27, 11 August 2000
<abstract>
@ -29,10 +29,14 @@
name="PLIP-Install-HOWTO">, by Gilles Lamiral, located at: <newline>
<tt>http://www.linuxdoc.org/HOWTO/PLIP-Install-HOWTO.html</tt>
If you have already read this HOWTO and you wonder what is new is
this release, first read the section <ref id="WHAT_IS_NEW"
name="what's new">.
<sect>Introduction
<p>
"PLIP is Parallel Line IP, that is, the transportation of IP packages
over a parallel port." Donald Becker (becker@super.org).
Writing a PLIP install HOWTO seems useless nowadays since Ethernet
cards are cheap: NE2000 cards cost about the same as a Null-Modem
@ -47,10 +51,12 @@
This paper is just what I've done to install a <htmlurl
url="http://www.debian.org" name="Debian GNU/Linux"> distribution on
a Toshiba Port&eacute;g&eacute; 620CT laptop, from a NFS exported
cdrom drive, via a Null-Modem cable.
cdrom drive, via a Null-Modem cable.
A Null-Modem cable is also called a LapLink cable but this word is
<htmlurl
A Null-Modem cable is also called a Null-Printer cable.
A Null-Modem cable is also called a LapLink (or Turbo Laplink) cable
but the word LapLink is <htmlurl
url="http://www.marksonline.com/app/tmsearch/find_mark?tok=laplink"
name="trademarked"> by Traveling Software under the number 75466713
since 1986, so I won't use it anymore.
@ -60,6 +66,11 @@
to add two commands to make this HOWTO obsolete (ifconfig +
route). I hope one Debian maintainer will consider this point.
I hoped this HOWTO would become obsolete but in fact it seems that
it will never be obsolete because some distributions builders do
include PLIP installation sometimes but forget to maintain it in new
releases (REDHAT for example).
I would be happy to know if someone used the PLIP-Install-HOWTO
to install other Linux distributions from other network protocols
(ftp, http, nfs, samba, or even NT/Novell servers)
@ -67,6 +78,9 @@
Feedback with typos, bad English, comments, money, job, joy, fears,
cries are welcome and recommended (not all with the same eagerness).
If a translation in any language exists, please let me know, I'll be
happy.
<!-- He who can do more can do less. -->
<sect>License
@ -347,7 +361,7 @@
The file content lines should never begin with white space. You'll
have to remove them, if any. Sorry, I'm fed up with <tt>C-a
M-AltGr-\</tt> (remember, I'm a French azerty writer). Tab-emacs
reflex is untamable (coders who use Emacs always press the tabular
reflex is untameable (coders who use Emacs always press the tabular
key like a twitch).
Command input lines begin with a dollar <tt>$</tt> (the prompt), you
@ -366,9 +380,9 @@
graham says:
Why this "#"? Because this is for root's prompt. So, in the next
paragraph, say that you will use the '$' for the remainder of
this. See my comment below.
Why this "#" caracter ? Because this is for root's prompt. So, in
the next paragraph, say that you will use the '$' for the remainder
of this. See my comment below.
The prompt will be shown as "<tt>$</tt>" in the remainder of this
documentation "<tt>$</tt>", even if it should be "<tt>#</tt>". This
@ -376,6 +390,80 @@
don't like ambiguity in computer science.
<sect>Building your own cable
<p>
Extract from /usr/src/linux/Documentation/networking/PLIP.txt,
written by Donald Becker (becker@super.org):
<verb>
Parallel Transfer Mode 0 Cable
==============================
The cable for the first transfer mode is a standard
printer "null" cable which transfers data four bits at a time using
data bit outputs of the first port (machine T) connected to the
status bit inputs of the second port (machine R). There are five
status inputs, and they are used as four data inputs and a clock (data
strobe) input, arranged so that the data input bits appear as contiguous
bits with standard status register implementation.
A cable that implements this protocol is available commercially as a
"Null Printer" or "Turbo Laplink" cable. It can be constructed with
two DB-25 male connectors symmetrically connected as follows:
STROBE output 1*
D0->ERROR 2 - 15 15 - 2
D1->SLCT 3 - 13 13 - 3
D2->PAPOUT 4 - 12 12 - 4
D3->ACK 5 - 10 10 - 5
D4->BUSY 6 - 11 11 - 6
D5,D6,D7 are 7*, 8*, 9*
AUTOFD output 14*
INIT output 16*
SLCTIN 17 - 17
extra grounds are 18*,19*,20*,21*,22*,23*,24*
GROUND 25 - 25
* Do not connect these pins on either end
If the cable you are using has a metallic shield it should be
connected to the metallic DB-25 shell at one end only.
</verb>
I checked my cable twice. On both sides, pins are connected like
this:
<verb>
1 - 1 Yes
2 - 15
3 - 13
4 - 12
5 - 10
6 - 11
7 not connected
8 not connected
9 not connected
10 - 5
11 - 6
12 - 4
13 - 3
14 - 14 Yes
15 - 2
16 - 16 Yes
17 - 17
18 not connected
19 not connected
20 not connected
21 not connected
22 not connected
23 not connected
25 - 25 not connected to metallic shield
</verb>
Unlike the kernel document says, my cable has pins 1, 14, 16 connected.
It doesn't matter, apparently, since plip works fine for me.
<sect>Network parameters
<p>
@ -923,18 +1011,18 @@
<sect>Debian installation
<p>
I'm not a Debian proselyte since it is my first Debian installation.
I'm a Debian proselyte since it is my first Debian installation.
Debian lovers are the same kind of people as Macintosh lovers or
Linux lovers in the operating systems space. Nothing else
counts. Since I'm already a Mac and Lin lover (and French too :-) it
was time to fall in love.
counts. Since I'm already a Mac and Linux lover (and French too :-)
it was time to fall in love.
Debian is well, clearly and internationally documented. Thanks to
all those guys who bred this really open distribution.
all those people who bred this really open distribution.
I could leave you on your own during the installation process. But
since we have to interact with a shell during it, the entire process
will be described in details.
will be described in detail.
I know the description is Debian specific. I prefer to give you a
complete example than nothing except a ``run a shell at the right
@ -950,15 +1038,15 @@
network are necessary during the installation process. If you are
interested in this solution, go directly to the section <ref
id="INSTALL_FROM_A_DOS_PARTITION" name="Installing from a DOS
partition">. I'm keeping the old one installation routine because
partition">. I'm keeping the old installation routine because
this new one needs a DOS partition that becomes superfluous when you
definitively want to leave the dark side.
definitely want to leave the dark side.
<sect1>Preparing the two floppies
<p>
On the <bf>source</bf> side, mount the cdrom and go in the install
On the <bf>source</bf> side, mount the cdrom and go to the install
directory
<verb>
@ -967,7 +1055,7 @@
</verb>
Read the file install.html with a browser or install.txt with a
cat, less or more (a dog).
cat, less or more (a dog?).
Now, record the install (alias rescue) floppy. Write a
"<tt>resc1440.bin</tt>" label on it:
@ -976,29 +1064,26 @@
$ dd if=resc1440.bin of=/dev/fd0H1440
</verb>
Record the drivers floppy. Write a "<tt>drv1440.bin</tt>" label on it:
Write the drivers floppy. Write a "<tt>drv1440.bin</tt>" label on it:
<verb>
$ dd if=drv1440.bin of=/dev/fd0H1440
</verb>
Lock the writing on those floppies.
Then make sure that the floppies are write-protected.
Now you're ready to start the real installation process.
Now you're ready to start the real installation process.
<sect1>The real installation process
<p>
Insert the resc1440.bin floppy on <bf>target</bf> drive. Reboot your
<bf>target</bf> box.
Insert the resc1440.bin floppy on <bf>target</bf> drive. Reboot
your <bf>target</bf> box.
<verb>
Welcome to Debian GNU/Linux 2.x!
...</verb>
Read the text
The prompt is :
Read the text. The prompt is:
<verb>
boot:</verb>
@ -1043,11 +1128,11 @@
Press <tt>&lt;ENTER&gt;</tt>
<verb>
Select Disk Drive
/dev/hda</verb>
Select Disk Drive
usually /dev/hda</verb>
If you have several disks choose the good one (where you want to
install Linux) and Press <tt>&lt;ENTER&gt;</tt>
install Linux) and press <tt>&lt;ENTER&gt;</tt>
You are now using the program <tt>cfdisk</tt>. Using
<tt>cfdisk</tt> is safe until you decide to <tt>[Write]</tt> the
@ -1057,7 +1142,8 @@
We are going to make just two new primary partitions, a Swap one and
a big Linux one. If you want to do more partitions, leave some free
space or extended partitions, you can. But read the documentation
about Partitioning in the <em>Installation-HOWTO</em>.
about Partitioning in the <em>Installation-HOWTO</em>, especially if
you have more than 1024 cylinders and an old LILO software.
If you previously ran the <tt>FIPS</tt> program, you see the
<tt>hda1</tt> partition (<tt>DOSFAT16</tt>). Switch to the next free
@ -1068,24 +1154,24 @@
Select <tt>[Primary]</tt> and press <tt>&lt;ENTER&gt;</tt>
Enter the size of your swap partition. Twice the ram is usual if you
have less than 128 mega bytes of ram. If you have 2 giga bytes of
ram, it's because you don't want to swap. In that case, no swap
Enter the size of your swap partition. Twice the RAM is usual if you
have less than 128 megabytes of ram. If you have 2 gigabytes of
RAM, it's because you don't want to swap. In that case, no swap
partition is needed.
Select <tt>[Beginning]</tt> and press <tt>&lt;ENTER&gt;</tt>
Select <tt>[Type]</tt> and press <tt>&lt;ENTER&gt;</tt> Type
<tt>82</tt> (Linux Swap) and press <tt>&lt;ENTER&gt;</tt>
Select <tt>[Type]</tt> and press <tt>&lt;ENTER&gt;</tt>. Type
<tt>82</tt> (Linux Swap) and press <tt>&lt;ENTER&gt;</tt>.
Switch to the next free partition with the up/down arrow keys Select
<tt>[New]</tt> and press <tt>&lt;ENTER&gt;</tt>
Switch to the next free partition with the up/down arrow
keys. Select <tt>[New]</tt> and press <tt>&lt;ENTER&gt;</tt>
Select <tt>[Primary]</tt> and press <tt>&lt;ENTER&gt;</tt>
Enter the size in MB (You can leave the default) and press
<tt>&lt;ENTER&gt;</tt> Its type is already Linux. If not, change to
Linux (83) with <tt>[Type]</tt>
Enter the size in MB (you can leave the default) and press
<tt>&lt;ENTER&gt;</tt> Its type should be already Linux. If not,
change to Linux (83) with <tt>[Type]</tt>
The partition table is defined now. Verify everything looks good. If
you're not sure, read the documentation with <tt>[Help]</tt>. If
@ -1093,14 +1179,14 @@
installation process. Go for a walk and restart from the beginning
of this section.
I assume your are confident now.
I assume you are confident now.
Select <tt>[Write]</tt>
<verb>
Are you sure you want to write the partition table to disk?</verb>
Type <tt>yes</tt> and press <tt>&lt;ENTER&gt;</tt>
Type "<tt>yes</tt>" and press <tt>&lt;ENTER&gt;</tt>
Select <tt>[Quit]</tt> and press <tt>&lt;ENTER&gt;</tt>
@ -1112,7 +1198,7 @@
<verb>
Please select the partition to initialize as a swap device</verb>
Select <tt>/dev/hda2</tt> (normally already selected)
Select <tt>/dev/hda2</tt> (normally already selected).
Press <tt>&lt;ENTER&gt;</tt>
<verb>
@ -1136,11 +1222,11 @@
Press <tt>&lt;ENTER&gt;</tt>
<verb>
Select Partition Please select the to initialize as a Linux "ext2"
file-system.</verb>
Select Partition. Please select the partition to initialize as a
Linux "ext2" file-system.</verb>
Select <tt>/dev/hda3</tt> (normals already selected) and press
<tt>&lt;ENTER&gt;</tt>
Select <tt>/dev/hda3</tt> (normally already selected) and press
<tt>&lt;ENTER&gt;</tt>.
<verb>
Scan for Bad Blocks?</verb>
@ -1230,9 +1316,10 @@
Press <tt>&lt;ENTER&gt;</tt>
Select <tt>Exit</tt> (Finished with these modules) and press <tt>&lt;ENTER&gt;</tt>
<newline> Then you see the same kind of screen again. <newline>
Select <tt>Exit</tt> (Finished with these modules) and press <tt>&lt;ENTER&gt;</tt>
Select <tt>Exit</tt> ("Finished with these modules") and press
<tt>&lt;ENTER&gt;</tt> <newline> Then you see the same kind of
screen again. <newline> Select <tt>Exit</tt> ("Finished with these
modules") and press <tt>&lt;ENTER&gt;</tt>
<verb>
Next: Configure the Network</verb>
@ -1288,7 +1375,7 @@
<4>plip1: Parallel port at 0x378, using assigned IRQ 7
...
Ctrl-c</verb>
Ctrl-c (or ^C if you prefer)</verb>
Configure the plip interface:
@ -1349,9 +1436,9 @@
<tt>dmesg</tt>, <tt>ifconfig</tt>, <tt>route</tt>. Verify
everything. Take a rest. Restart.
When the ping is ok, return to the normal installation process:
When the ping is okay, return to the normal installation process:
On the target: Press <tt>Alt F1</tt>
On the target: press <tt>Alt F1</tt>
<sect1>Return to the normal install process
@ -1446,8 +1533,8 @@
<verb>
Timezone Configuration.</verb>
An other page
Read, select <tt>&lt;YES&gt;</tt> and press <tt>&lt;ENTER&gt;</tt>
An other page. Read, select <tt>&lt;YES&gt;</tt> and press
<tt>&lt;ENTER&gt;</tt>
<verb>
Next: Make Linux Bootable Directly From Hard Disk</verb>
@ -1476,7 +1563,7 @@
Please place a blank floppy disk in the first floppy drive.</verb>
Do it and press <tt>&lt;ENTER&gt;</tt> <newline>
The floppy is being formated
The floppy is being formatted
<verb>
Creating a filesystem on the floppy...
@ -1509,12 +1596,13 @@
<verb>
Re-enter new password</verb>
Do it.
Do it. And learn it.
<verb>
Shall I create a normal user account now? [Y/n]</verb>
Enter <tt>n</tt> and press <tt>&lt;ENTER&gt;</tt>
Enter <tt>n</tt> and press <tt>&lt;ENTER&gt;</tt>. Unless you want
to do it (it is safe and good, in fact).
<verb>
Shall I install shadow passwords? [Y/n]</verb>
@ -1560,14 +1648,15 @@
distribution and go on with the Unix system administration job.
When you reboot your system, the plip connection won't be in good
shape. But now you now what to do.
shape. But now you know what to do.
I suggest you some work:<itemize>
<item>Configure the plip interface for the normal boot process (in
the file <tt>/etc/init.d/network</tt>).
<item>Configure <tt>/etc/fstat</tt> on the <bf>target</bf> to mount
simply the remote <bf>source</bf> cdrom via nfs.
<item>Configure <tt>/etc/fstat</tt> on the <bf>target</bf> to
simply mount the remote <bf>source</bf> cdrom via nfs.
<verb>
source:/cdrom /cdrom nfs noauto,intr 1 2
</verb>
@ -1710,9 +1799,9 @@
You then did ping your source, but yet you cannot ping the target.
So the first step is to configure your PLIP connection:
On the target type:
<verb>
& ifconfig plip0 192.168.0.2 pointopoint 192.168.0.1 netmask 255.255.255.255 up
On the target type: <label
id="SLACKWARE_TARGET_IP_ADRESS_IFCONFIG"><verb>
& ifconfig plip0 192.168.0.1 pointopoint 192.168.0.2 netmask 255.255.255.255 up
</verb>
Test your Plip configuration by pinging the target from the source
<verb>
@ -1802,6 +1891,143 @@
</p>
</sect1>
<sect>Installing RedHat 6.x
<p>
This section is written by Dr. Tilmann Bubeck,
bubeck@think-at-work.de
<p>
I tried hard to install a laptop through PLIP with a RedHat 6.2 but
the installer from RedHat is buggy and could not be used for
PLIP. I verified that it was already broken in RedHat 6.1, but
works in RedHat 5.2 as desired. Patches have been sent to RedHat
and will hopefully be applied to the upcoming RedHat 7.0.
So if you want to install a RedHat 6.x over PLIP you <bf>must</bf>
follow these instructions.
The problem is the "bootnet" disk. This disk should be used for
PLIP installation but has 2 serious errors:
<itemize>
<item>it does not contain the necessary driver "parport_pc"
<item>it does not allow you to specify important module
parameters to "parport_pc" (especially "iobase" and "irq").
</itemize>
<sect1>Using a fixed "bootnet" disk
<p>Probably the easiest way to solve the above problem is to use a
fixed "bootnet" disk. You can get a fixed "bootnet" disk for RedHat
6.2 from <htmlurl
url="http://www-ti.informatik.uni-tuebingen.de/~bubeck/bootnet-plip-62.img"
name="http://www-ti.informatik.uni-tuebingen.de/~bubeck/bootnet-plip-62.img">
Use the following command to copy the downloaded image to an empty disk:
<tt>dd if=bootnet-plip-62.img of=/dev/fd0</tt>.
Then insert the disk and turn your computer on. When you come to
the point where you must choose your network device driver please
do:
<itemize>
<item>1- Choose "Parallel Port Module for PC" and select "specify
module parameters".
<item>2- Enter iobase and interrupt for your parallel
port. Typical values are iobase=0x378 or iobase=0x3bc. Interrupt most
often is "irq=7".
<item>3- Validate, that the kernel loads the module and finds the
parallel port. Use ALT+F4 to switch to kernel messages and look
for a line saying: "parport: ... irq: 7".
<item>4- The installation will then try to access the network
which is still not available. So the installer asks again for the
installation method. Choose your method again.
<item>5- Now choose the "plip" module without any
parameters. Again verify the loading of the module in the kernel
messages.
<item>6- Network should be up and running, installation should
proceed. If not, then check the modules parameters to
"parport_pc".
</itemize>
<sect1>Building your own "bootnet" disk
<p>If the above bootnet disk is not suitable for your needs, I will
present a small description on how to transform a standard bootnet
disk for using "plip". This description is quite short and is
addressed to the advanced user.
<itemize>
<item>1- make a copy of the standard bootnet disk by using "dd".
<item>2- insert this copy of standard bootnet disk and mount it
with: <tt>mount /dev/fd0 /mnt</tt>
<item>3- gunzip initial ramdisk with <tt>cp /mnt/initrd.img
/tmp/initrd.img.gz; gunzip /tmp/initrd.img.gz</tt>
<item>4- Mount initial ramdisk with <tt>mkdir /mnt2; mount -o loop
/tmp/initrd.img /mnt2</tt>
<item>5- gunzip and extract modules directory with: <tt>cd /tmp;
zcat /mnt2/modules/modules.cgz | cpio -ivd</tt>
<item>6- You should now have a directory called with your kernel
version number (e.g. "2.2.14-5.0BOOT") containing a lot
of modules. Check, if the modules "parport_pc.o" is
included in this directory (it is unfortunately NOT
included in RedHat 6.0-6.2). If you can not find it, then
please build a custom kernel with the EXTRAVERSION number
like your bootnet disk (in this case: "5.0BOOT") and
"parport" support as module. Copy the newly created
parport_pc.o module to your new modules directory: <tt>cp
.../parport_pc.o /tmp/2.2.14-5.0BOOT</tt>.
<item>7- delete a normally unused module, so that you have
additional space on the disk: <tt>rm
/tmp/2.2.14-5.0BOOT/sktr.o</tt> (driver for token ring
network adapter).
<item>8- rebuild modules archive with: <tt>find
/tmp/2.2.14-5.0BOOT | cpio -ov -H crc | gzip &gt;
/mnt2/modules/modules.cgz</tt>
<item>9- insert a new modules dependency line into modules.dep
saying that module "parport_pc" needs module "parport":
<tt>echo "parport_pc: parport" &gt;&gt;
/mnt2/modules/modules.dep</tt>
<item>10- insert entry for parport_pc module into module-info so
that the user could select the parport_pc module during
installation. Append the following text to the end of
/mnt2/modules/module-info: <verb>
parport_pc
plip
"Parallel Port Module for PC"
io "Base I/O address"
irq "IRQ level"
</verb>
<item>11- unmount and gzip initial ramdisk with: <tt>umount /mnt2;
gzip -9 /tmp/initrd.img</tt>
<item>12- copy initial ramdisk to bootnet disk and unmount: <tt>
cp /tmp/initrd.img.gz /mnt/initrd.img; umount /mnt</tt>
</itemize>
By following these instructions, you get a bootnet disk containing
all necessary modules and therefore allowing for a PLIP
installation. Please follow the instructions above on how to do the
installation with the new disk.
<sect> Installing from a DOS partition <label
@ -1842,7 +2068,7 @@
e) Do './install.s'
</verb>
Boot the <bf>target</bf> with the floppy. Log in root.
Boot the <bf>target</bf> with the floppy. Login as root.
<verb>
$ insmod plip
@ -1950,12 +2176,16 @@ exit 0
$ ln -s ../init.d/plip S11plip
</verb>
You can choose other numbers. Be aware to place the K??plip files
after the ones that shutdown services depending on plip. Be aware
to place the S??plip files before the ones that start services
depending on plip, nfs, nis, ftp, http etc.
You can choose other numbers. Make sure that the two-digit number
after 'K' is greater than the number of every other file that stops
a service depending on plip.
Update the <tt>/etc/conf.modules</tt> file:
Make sure that the two-digit number after 'S' is less than the
number of every other file that start a service depending on plip:
nfs, nis, ftp, http etc.
Update the <tt>/etc/conf.modules</tt> file, choosing the correct
IRQ number (7 is mine, yours may be different):
<verb>
# /etc/conf.modules
@ -1965,8 +2195,6 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
...
</verb>
Choose the good irq number (7 is mine, not yours).
Test the plip shell:
<verb>
@ -1991,11 +2219,11 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
Starting plip interface: done
</verb>
Updating the start scripts is a good accasion to reboot a Unix
Updating the start scripts is a good occasion to reboot a Unix
system, to check the modifications. Do it:
<verb>
$ init 6
$ init 6 # or "shutdown -t now" or "reboot"
</verb>
@ -2027,7 +2255,25 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
$ init 6
</verb>
<sect>Compatibility with a printer (lp)
<p>
I use the same parallel port for printing on a printer and
networking with my laptop without big problems. It takes less than
one second to switch from printing to networking. I just add a cheap
manual switch between the parallel port, the printer and the
laptop. The cable between the switch and the desktop computer is a
fully connected one. The switch is just the one used to shared
printers when no network is available. It works.
Sometimes, the kernel is not very happy because it can't finish its
network job. In that case, I shutdown the plip interface and restart
it when needed.
I bought a new parallel card last year but it is still in its
box. I'll write an "install a second parallel port" when I'll
succeed in opening the box and add that beautiful card in the last
available connector I have left.
<sect>Need to compile a new kernel ?
<p>
@ -2037,7 +2283,7 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
could be needed.
I list the things you need to change or set. If you have never
compile a kernel, read the <em>Kernel-HOWTO</em>.
compiled a kernel, read the <em>Kernel-HOWTO</em>.
<verb>
Loadable module support --->
@ -2055,9 +2301,7 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
[*] Network device support
<*> Dummy net driver support
<M> PLIP (parallel port) support
< > or <M> PPP (point-to-point) support
< > or <M> SLIP (serial line) support
<*> or <M> PPP (point-to-point) support
Character devices --->
<M> Parallel printer support
@ -2072,8 +2316,60 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
</verb>
<sect>What's new
<sect>What's new<label id="WHAT_IS_NEW">
<p>
This tag is automatic so it IS the reference.
(Sometimes I forget to update the version number and the date)
$Id$
<descrip>
<tag>v1.27, 11 August 2000
<p>
<itemize>
<p> <item>The SLIP line was not needed, SLIP is serial line
oriented. The PPP line was partly wrong, we need PPP support by
the kernel.
<p> <item> Finished to correct my bad English checked by
Graham. I know it still remains many mistakes and new ones come
every time I write a sentence...
<p> <item> Added a "compatibility with a printer" section.
<p> <item> Added a Null-Printer == Null-Modem comment.
<p> <item> Added a "build your own cable" section.
<p> <item> Corrected a bug in the Slackware section. <ref
id="SLACKWARE_TARGET_IP_ADRESS_IFCONFIG" name="Here"> (inverted
IP adresses). Thanks to Brad Rigby.
<p> <item> never be obsolete paragraph in Introduction section.
<p> <item> known translated version demand in the Introduction section.
<p> <item> Mentioned the what's new section at the top of the document.
<p> <item> Added a vc-header in the What's new section
<p> <item> Added the WHAT_IS_NEW label
<!--
<p> <item>
-->
</itemize>
</p>
</descrip>
<descrip>
<tag>v1.22, 16 June 2000
@ -2090,14 +2386,7 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
<p> <item> Corrected some English faults, thanks to Graham and
Tomas.
<!--
<p> <item>
-->
</itemize>
</p>
@ -2114,9 +2403,9 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
<p> <item>The section "List of contributors and acknowledgements".
<p> <item>Made the different chapters dealing with the detailed
Debian installation be a single chapter with the actual chapters
as just subsections.
<p> <item>Joined the different chapters dealing with the
detailed Debian installation to form a single chapter with the
actual chapters as just subsections.
<p> <item> Made a new section "Installing from a DOS
partition". A simpler and faster method.
@ -2134,21 +2423,19 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
<tt>.config</tt> file) with only the options I gave. Add the
missing ones if any.
<p> <item>Make the Mandrake, SuSE, Turbo Linux, and Stampede
detailed installation chapters. Contributions are welcome. Gilles
Lamiral won't do that job unless given new computers and CDs.
<p> <item>Make the Mandrake, SuSE (Graham? Are you there?), Turbo
Linux, and Stampede detailed installation chapters. Contributions
are welcome. Gilles Lamiral won't do that job unless given new
computers and CDs.
<p>Debian (done), Red Hat (done), Slackware (done), Caldera
OpenLinux (done).
<p>Debian (done), Red Hat (redone by Tilmann Bubeck), Slackware
(done), Caldera OpenLinux (done).
<p> <item>Make "The cdrom nfs server side" chapter become simply
<p> <item>Make "The CD-ROM NFS server side" chapter become simply
"the server side" chapter with subsections like "cdrom medium",
"zip medium", "hard disk medium", and "ftp server" "nfs server",
"samba server" "http server". Again, contributions are welcome.
<!--
<p> <item>
@ -2190,8 +2477,9 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
<tag>Simon Forget &lt;sforget@camelot.ca&gt;
</tag>
<p>
Simon had a problem with his pcmcia floppy drive. So he made me
search a solution that is, in fact, simpler and faster.
Simon had a problem with his pcmcia floppy drive. So he led me
search for a solution that is, in fact, simpler and faster (the
DOS one).
</p>
</descrip>
@ -2232,7 +2520,38 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
</p>
</descrip>
<descrip>
<tag>
Brad Rigby &lt;brigby@rocketmail.com&gt;
</tag>
<p>
Brad corrected a bug in the Slackware section (inverted IP
adresses).
</p>
</descrip>
<descrip>
<tag>
Donald Becker &lt;becker@super.org&gt;
</tag>
<p>
Donald wrote the PLIP kernel documentation<newline>
/usr/src/linux/Documentation/networking/PLIP.txt
</p>
</descrip>
<descrip>
<tag>
Tilmann Bubeck &lt;bubeck@think-at-work.de&gt;
</tag>
<p>
Tilmann wrote the section called "Installing RedHat 6.x".
</p>
</descrip>
</article>