diff --git a/LDP/howto/linuxdoc/Apache-Overview-HOWTO.sgml b/LDP/howto/linuxdoc/Apache-Overview-HOWTO.sgml
index 16a13da6..0a885fd1 100644
--- a/LDP/howto/linuxdoc/Apache-Overview-HOWTO.sgml
+++ b/LDP/howto/linuxdoc/Apache-Overview-HOWTO.sgml
@@ -1,31 +1,43 @@
+
+
-Apache Overview How-to
+Apache Overview HOWTO
Daniel Lopez Ridruejo, v0.4, 11 September 2000
+v0.6, 8 March 2000
-The purpose of this document is to give an overview of the Apache webserver
-and related projects. It provides pointers for further information and
-implementation details.
+This documents gives you an overview of the Apache webserver and
+related projects. It provides pointers for further information and
+implementation details.
Introduction
-The purpose of this document is to give an overview of the Apache web server
-and related projects. Apache is the . New Apache
users, specially those coming from a Windows background, are often unaware
-of the possibilities of Apache, useful addons and how everything works
+of the possibilities of Apache, useful addons and, more in general, how everything works
together. This document aims to show a general picture of such possibilities
with a brief description of each one and pointers for further information.
The information has been gathered from many sources, including projects' web
@@ -35,6 +47,8 @@ this document would not have been possible or necessary.
Disclaimer: I work for . We
provide products and support services for the Apache webserver, and I mention some
of them here, as I do for our competitors and similar open source projects.
+
If you find typos, errors or you have suggestions for improvement or comments,
+please let me know so I can correct the document.
Apache
Apache is the leading internet web server, with over 60% market share, according
to the .
@@ -42,11 +56,13 @@ Several key factors have contributed to Apache's success:
The . It is
an open source, BSD-like license that allows for both commercial and non-commercial
-usage of Apache.
+uses of Apache.
Talented community of
with a variety of backgrounds and an open development process based on technical merits.
-Modular architecture.
+Modular architecture. Apache users can easily add functionality or taylor Apache to their
+specific enviroment.
Portable: Apache runs on nearly all flavors of Unix (and Linux), Windows, BeOs, mainframes...
+Robustness and security
Many commercial vendors have adopted Apache based solutions for their products, including , and .
@@ -70,6 +86,12 @@ is good enough for them, it is also good enough for you :)
The Apache project has grown beyond building just a web server into other critical server side technologies
like Java or XML. The Apache Software Foundation, described in the next section serves as an umbrella for these projects.
+
Related talk
+
+W09: Introduction to the Apache Web Server
+F16: Licensing issues in commercial OSS products
+
+
Apache Software Foundation
The Apache Software Foundation exists to provide organizational, legal, and financial support for the Apache open-source
@@ -83,12 +105,16 @@ collaborative software development projects that use the Apache methods of
collaboration over the Internet to create, maintain, and extend the infrastructure
of the Web and enforce the standards that define it.
You can learn more about the foundation .
-
-
Developing web applications with Apache
There are several ways of providing content with Apache.
+
+
Related talk
+
+W07: Web Application Technologies - surveying the landscape
+
+
Static
Apache can serve static content, like HTML files, images, etc.
@@ -106,7 +132,7 @@ directory services, customer records, other websites) and deliver the content
to the user.
CGI scripts
-CGI stands for common gateway interface. CGI scripts are external programs
+CGI stands for Common Cateway Interface. CGI scripts are external programs
that are called when a user requests a certain page. The CGI receives information
from the web server (forms variable values, type of browser, IP
address of the client, etc) and uses that information to output a web page for the client.
@@ -152,6 +178,12 @@ protocol. The main improvement is that a single spawned process can process
more than one request. There is an Apache module that implements the Fast CGI
protocol and libraries for Tcl, Perl etc. More information at
+
+
Related talk
+
+F18: FastCGI -- The forgotten treasure
+
+
Java servlets
PLIP Install HOWTO
Gilles Lamiral, lamiral@mail.dotcom.fr
- v1.27, 11 August 2000
+ v1.30, 13 April 2001
@@ -55,19 +55,19 @@
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 by Traveling Software under the number 75466713
since 1986, so I won't use it anymore.
- This HOWTO will be obsolete when every Linux distribution include a
+ This HOWTO will be obsolete when every Linux distribution includes a
PLIP install option. For example, the Debian installation only needs
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
+ it will never be, because some builders of some distributions do
include PLIP installation sometimes but forget to maintain it in new
releases (REDHAT for example).
@@ -325,7 +325,7 @@
name="PLIP.txt">, by Donald Becker, located at:
/usr/src/linux/Documentation/networking/PLIP.txt on your source linux computer, Luke.
-
+ Alternatively, read my notes in section "Building your own cable".
Conventions
@@ -378,12 +378,6 @@
#
- graham says:
-
- 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 "$" in the remainder of this
documentation "$", even if it should be "#". This
is because "#" often means comment, so it is ambiguous. I
@@ -461,13 +455,14 @@ connected to the metallic DB-25 shell at one end only.
25 - 25 not connected to metallic shield
- Unlike the kernel document says, my cable has pins 1, 14, 16 connected.
- It doesn't matter, apparently, since plip works fine for me.
+ Unlike the cable described in the kernel document, my cable has pins
+ 1, 14, 16 connected. It doesn't matter, apparently, since plip
+ works fine for me.
Network parameters
- We will make a plip point-to-point network with those IP
+ We will make a plip point-to-point network with this IP
configuration:
@@ -524,7 +519,7 @@ connected to the metallic DB-25 shell at one end only.
- Because the portmaper tries to resolve IP addresses, add the IP
+ Because the portmapper tries to resolve IP addresses, add the IP
addresses and names in /etc/hosts
@@ -588,7 +583,7 @@ connected to the metallic DB-25 shell at one end only.
capabilities.
You are not obliged to eliminate the lp device : the scheme may work
- with lp. Without guaranty (it works for me). Check it yourself.
+ with lp. Without guarantee (it works for me). Check it yourself.
Check that your parallel port is handled:
@@ -783,9 +778,11 @@ connected to the metallic DB-25 shell at one end only.
100003 2 tcp 2049 nfs
- Lines with nfs or portmapper have to be there. NFS
- on tcp ? progress have been made !
+ Lines with nfs or portmapper have to be there. We
+ have NFS on tcp? progress have been made!
+ It doesn't matter if you have only NFS on udp. NFS has to work,
+ that's the thing you need.
Then, rerun portmap, mountd, nfs:
@@ -804,12 +801,12 @@ connected to the metallic DB-25 shell at one end only.
/etc/rc.d/init.d/ is /sbin/init.d/ on SuSE Linux
- systems. I had a dream last nigth: LSB was respected. (LDB: Linux
+ systems. I had a dream last night: LSB was respected. (LDB: Linux
Standard Base)
Then, try to mount it "locally" (via nfs) on the source box
- and clean the test:
+ and when the test is good remove the test directory:
$ mkdir /tmp/nfstest
@@ -885,8 +882,8 @@ connected to the metallic DB-25 shell at one end only.
fips20.zip file) in /cdrom/debian/tools/fips15.zip
(It supposes your cdrom is mounted on /cdrom)
- I guess you are on a Unix world but you're not compelled to do
- so. Go in a good working place on the source computer:
+ I guess you are on a Unix world but you're not compelled to be. Go
+ in a good working place on the source computer:
$ mkdir /tmp/fips-2.0/
@@ -912,7 +909,7 @@ connected to the metallic DB-25 shell at one end only.
Be aware of hidden files.
- Graham comment: Hidden files will not be moved by DeFrag (as far as
+ Graham's comment: Hidden files will not be moved by DeFrag (as far as
I know), so FIPS will reclaim less space for use by Linux. Use the
ATTRIB command to remove the "hidden" attribute. Some things may
require that files are hidden, so it will be necessary to hide the
@@ -929,15 +926,19 @@ connected to the metallic DB-25 shell at one end only.
called "Virtual Memory".
Adjust the size to none, Click<-Click<-Click<-Click back plus Alt-F4
- to close all your windows. Don't you think the Gates are too closed
- too?
+ to close all your windows. Don't you think the Gates are closed too?
- Graham comment: I am not sure that this is a good idea. What
+ Graham's comment: I am not sure that this is a good idea. What
happens if "386spart.par" is not hidden? I think that DEFRAG will
move it, and Windows will complain next time it starts, then rebuild
the file. Since we are clearly keeping DOS/Windows, the user will
require a swap file again later. By not deleting it, the disc space
- is reserved for that time.
+ is reserved for that time.
+
+ Graham's new comment: "Make sure that the file is not hidden (attrib
+ -h -s 386spart.par), then delete it (del 386spart.par). The disc
+ space is then free. Run FIPS. Next time Windows starts, it will
+ complain that the file is corrupt, and will recreate it."
I don't what to say. I've just parroted FIPS manual because I
succeeded with it.
@@ -985,18 +986,18 @@ connected to the metallic DB-25 shell at one end only.
$ mcopy errors.txt fips.exe restorrb.exe a:
- Graham comment: Doesn't this assume that mtools are installed? If
+ Graham's comment: Doesn't this assume that mtools are installed? If
the floppy disc is mounted as type msdos, the standard "cp" command
should do the job, and mtools would not be needed. I have never
used mtools, but I have played with DOS files from Linux.
- Yes, this assume that mtools are installed. mcopy is faster to type
- than mkdir, mount, cp, umount, rmdir.
+ Yes, this assumes that mtools are installed. mcopy is
+ faster to type than mkdir, mount, cp, umount, rmdir.
Boot the target with the floppy. Run fips while reading the
section "Using FIPS" in the file fips.doc
- Do not forget to answer yes when fips ask for a
+ Do not forget to answer yes when fips asks for a
rootboot saving.
When everything is ok, save your hard disk space:
@@ -1035,11 +1036,11 @@ connected to the metallic DB-25 shell at one end only.
already have a dos partition on the target computer.
This solution is simpler and faster because no floppy drive nor plip
- network are necessary during the installation process. If you are
+ network is necessary during the installation process. If you are
interested in this solution, go directly to the section . I'm keeping the old installation routine because
- this new one needs a DOS partition that becomes superfluous when you
+ partition">. I'm keeping the old installation routine because this
+ new one needs a DOS partition that becomes superfluous when you
definitely want to leave the dark side.
@@ -1051,11 +1052,17 @@ connected to the metallic DB-25 shell at one end only.
$ mount -t iso9660 /dev/hdd /cdrom
+
+
+ The device for your CDROM may be /dev/hdb or /dev/hdc or another
+ device (SCSI), depending on where is plugged your CDROM.
+
+
$ cd /cdrom/debian/dists/stable/main/disks-i386/current/
Read the file install.html with a browser or install.txt with a
- cat, less or more (a dog?).
+ more, a less, a cat (or a dog?).
Now, record the install (alias rescue) floppy. Write a
"resc1440.bin" label on it:
@@ -1140,10 +1147,11 @@ connected to the metallic DB-25 shell at one end only.
safe.
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 Installation-HOWTO, especially if
- you have more than 1024 cylinders and an old LILO software.
+ a big Linux one. If you want to create more partitions, leave some
+ free space or extended partitions, you can. But read the
+ documentation about "Partitioning" in the
+ Installation-HOWTO, especially if you have more than 1024
+ cylinders and an old version of LILO.
If you previously ran the FIPS program, you see the
hda1 partition (DOSFAT16). Switch to the next free
@@ -1239,7 +1247,7 @@ connected to the metallic DB-25 shell at one end only.
Select <YES> and press <ENTER>
A new page full of numbers. You can take a rest because it takes
- some time (especially with big hard disk).
+ some time (especially with a big hard disk).
Next: Mount a Previously-Initialized Partition
@@ -1581,7 +1589,7 @@ connected to the metallic DB-25 shell at one end only.
Remove the floppy and press <ENTER>
- The system reboot. Are you still with the dark side? I guess yes,
+ The system reboots. Are you still with the dark side? I guess yes,
so insert the boot floppy you've just made and reboot again with
Ctrl-Alt-Del
@@ -1671,30 +1679,32 @@ connected to the metallic DB-25 shell at one end only.
Have fun.
- Mail me a feedback.
+ Mail me some feedback.
- Installing Slackware, RedHat, Caldera
+ Installing Slackware, Caldera
This section is written by Florent SAUNIER.
sabetflo@freesurf.fr
+
+ Here, '&' is used for the root prompt, rather than '$'.
- I have performed a Slakware installation using PLIP very
- succesfully. I have also been able to install REDHAT and caldera
+ I have performed a Slackware installation using PLIP very
+ succesfully. I have also been able to install RedHat and Caldera
Open linux using the very same method described below.
- As previously specified by Gilles, a slakware installation requires
- everything specified in the chapter "What do you need" with time
+ As previously specified by Gilles, a Slackware installation requires
+ everything specified in the chapter "What do you need?" with the time
increased to 10 hours if you desire to install xfree(86) and some
- developpement tools.
+ development tools.
- Further on, you need to read first Gilles installation as I set up
- mine accordingly to his preset.
+ Further on, you first need to read Gilles' installation as I set up
+ mine according to his method.
- Finally, I have performed Slakware and Caldera installation on
- Twinhead 550C laptop, with 8Mb Ram, and 2Gbytes Hard drive.
+ Finally, I have performed Slackware and Caldera installation on
+ a Twinhead 550C laptop, with 8Mb Ram, and 2Gbytes Hard drive.
Slakware installation
@@ -1702,151 +1712,160 @@ connected to the metallic DB-25 shell at one end only.
1- Make 2 disks (boot and root) and prepare a plip disk
2- Install PLIP module
3- Create a NFS drive to use PLIP with
- 4- Launch the Slakware (or Caldera) Installation
- 5- Drink all remainder of coffee and go to bed waiting completion of
- installation
+ 4- Launch the Slackware (or Caldera) Installation
+ 5- Drink all remaining coffee and go to bed waiting completion of
+ installation. Graham said: Comment ? Du café avant de dormir ?
+ Non ! Le café au petit matin, après la nuit. Avant, du vin.
Making boot,root and plip disks
- To install slakware verion using ATAPI CDROM from your source you
- will need standard kernel image bareapm.i or bare.i. If you want
- to make an install from SCSI support take scsinet.i image.
+ To install Slackware verion using an ATAPI CDROM from your source,
+ you will need the standard kernel image bareapm.i or bare.i. If you
+ want to make an install with SCSI support, use the scsinet.i image.
- Other image exists, such as net.i which sould include PLIP
- function but on my i486 laptop, Twinhead550C, the imagedoes not
- work. I have experienced that the standard image allways work on
+ Other images exist, such as net.i which should include the PLIP
+ function but on my i486 laptop, Twinhead550C, the image does not
+ work. In my experience, the standard image always works on
any laptop I have used.
1a- creating the boot and root disks.
- From ms-dos create the boot disk by typing:
+ From DOS (PC-DOS, DR-DOS, FreeDOS, ...) create the boot disk by typing:
rawrite bareapm.i
then create the root disks:
- rawrite color.gz.a (if you are using color screen)
+ rawrite color.gz.a (if you are using a color screen)
1b- Creating the PLIP disk
- On a dos format disk copy the following file :
+ On a DOS formated disk copy the following files:
1- plip.o (object program for the plip tool)
2- parport_pc
3- parport
- Those programs are compulsory prior a PLIP install, you will find them
- into the slakware installation CDROM under the directory /MODULES.
- Same apply to the Caldera installtion. MAke find file if you cannot
- find them.
+ Those modules are compulsory prior to a PLIP install, you will find
+ them into the Slackware installation CDROM under the directory
+ /MODULES. The same applies to the Caldera
+ installation. Run a "find" if you cannot find them.
1c- launching the installation.
- Insert your boot disk in your Laptop and start computer.
- Follow the installtion procedure and wait till the system ask for
- the root disks.
- Insert it and wait for the prompt login: "Slakware login".
+ Insert your boot disk in your Laptop and start the computer.
+ Follow the installation procedure and wait until the system ask for
+ the root disk.
+ Insert it and wait for the prompt login: "Slackware login".
- To start the Slakware installation you must log as root. Type then root
- at the prompt. Be aware that at that time of installation your keyboard is
- still qwerty.
+ To start the Slackware installation you must log in as root. Type
+ "root" at the prompt. Be aware that at the time of installation your
+ keyboard is still qwerty.
2a- Install PLIP module
- Install your source computer according to Gille indication.
- From chapter 7 to 9.
+ Install your source computer according to Gilles' instructions,
+ from chapter 7 to 9.
- Install PLIP on the target.
- To install PLIP module you need to launch program from your PLIP disk.
- Remember you did it no !!!
+ Install PLIP on the target. To install the PLIP module you need to
+ launch the program from your PLIP disk. Remember you did it, no !!!
- Access to your floppy disk by:
+ Access your floppy disk with:
- & mount /dev/fd0h1440 /floppy
- & cd /floppy
- & insmod parport 'it will install your parallel port
- & insmod parport_pc 'it will set it up
- & insmod plip 'it will install plip module
+ $ mount /dev/fd0h1440 /floppy
+ $ cd /floppy
+ $ insmod parport # it will install your parallel port
+ $ insmod parport_pc # it will set it up
+ $ insmod plip # it will install plip module
- If during the PLIP installation you encounter an error. It means that
- your paralell port has not been correctly installed. you may type again
+ If during the PLIP installation you encounter an error, it means that
+ your parallel port has not been correctly installed. You may type again
the instruction above, it does work sometimes !!, or go to the parport
- directory and write appopriate setting.
+ directory and write the appropriate setting.
- & cd /proc/parport/0
- & vi IRQ 'Verify that 7 is written in it if you are using
- 'that interruption'
+ $ cd /proc/parport/0
+ $ vi IRQ # Verify that 7 is written in it if you are using
+ # that interrupt'
- Look at chapter 8,"PLIP on the source side" to get the proper setting.
+ See the chapter "PLIP on the source side" to get the proper setting.
- You should not bother too much as at 95% on the 5 laptop I have
- installed everyting went smoothly.
-
+ You should not bother too much as at 95% on the 5 laptops I have
+ installed everyting went smoothly. (Comment peut-on avoir "95% de
+ cinq", said rational Graham)
+
+
+
3a- Now create your NFS drive.
-
From that point I have choosed to use the creation of a NFS drive
+
From that point I have chosen to use the creation of a NFS drive
on the target computer. Then I will make an installation using the
- "From directory" option rather than from an nfs support.
+ "From directory" option rather than from nfs.
- Do not forget you are still in US keyboard.
- Of course you have set up your source accordingly to chapter 7,
- "Network parameters".
- You then did ping your source, but yet you cannot ping the target.
+ Do not forget you still have a US keyboard layout. Of course you
+ have set up your source according to chapter "Network parameters".
+ You did then ping your source, but you cannot yet ping the target.
So the first step is to configure your PLIP connection:
On the target type:
-& ifconfig plip0 192.168.0.1 pointopoint 192.168.0.2 netmask 255.255.255.255 up
-
+ id="SLACKWARE_TARGET_IP_ADRESS_IFCONFIG">
+
+
+ $ ifconfig plip0 192.168.0.1 pointopoint 192.168.0.2 netmask 255.255.255.255 up
+
+
Test your Plip configuration by pinging the target from the source
-
- & ping target
-
- then create your nfs drive:
-
- & cd /
- & mkdir nfsdrive
- mount -t nfs 192.168.0.2:/cdrom /nfstest
-
- You have just configure a drive linked to your source directory /cdrom
- were you suppose to have slakware CDROM connected to, from your target
- directory call nfstest
- Now everything is set up and you are ready to launch the Slakware
+
+ $ ping target
+
+ then mount your nfs drive on the target:
+
+ $ cd /
+ $ mkdir nfstest
+ $ mount -t nfs 192.168.0.2:/cdrom /nfstest
+
+ You have just configured a drive linked to your source
+ directory /cdrom were you suppose to have the Slackware CDROM
+ connected, from your target directory called nfstest.
+
+ Now everything is set up and you are ready to launch the Slackware
installation program, by typing "setup".
- note:if you do not have enough memory, below 8mb
- setup will not being launched then, you will have to make a swap
+ note:if you do not have enough memory, below 8MB
+ setup will not be launched, then you will have to make a swap
space to allow the program to work.
- first Create you disk partition with your swap by typing
- & fdisk
- note your swap disk name eg /hda3
- quit fdisk with 'w'
- Once its done type:
-
- & mkswap -c /dev/hda3
- & swapon /dev/ha3
+ First, create your disk partition with your swap by typing
+
+ $ fdisk
+
+ Note which is your swap partition (e.g. /hda3), then quit fdisk with
+ 'w'. Once it's done, type:
+
+
+ $ mkswap -c /dev/hda3
+ $ swapon /dev/ha3
+
+
Your swap is now set up.
You may then launch the "setup" program.
-
- the setup programm shows various menu:
+ the setup programm shows various menu items:
HELP - Help file
- KEYMAP - Keyboard select (Azerty at least !!!)
+ KEYMAP - Keyboard select (Azerty at last !!!)
ADDSWAP - Create and select swap
TARGET - Select target
SOURCE - select the source
- SELECT - Select pakages to install
- CONFIGURE - Set up your linux system and make LILO
+ SELECT - Select packages to install
+ CONFIGURE - Set up your Linux system and make LILO
EXIT - bye bye setup
@@ -1856,30 +1875,24 @@ connected to the metallic DB-25 shell at one end only.
4d- Select the target, default is '/'
- 4e- Select the source. Here is the tricky stuff choose
- Installing from a drive
- type the drive so : /nfsdrive/slakware
- '/slakware' because your drive must point to your
- slakware CDROM directory
+ 4e- Select the source. tricky stuff: choose "Installing from a
+ drive", then type the drive so : /nfstest/slackware
+ '/slackware' because your drive must point to your slackware
+ CDROM directory
4f- Select packages to install
4g- Wait, Wait, Wait and Wait........
-
-
-
-
-
-
- Caldera Installation
-
- I told you that Caldera work also with that install. In fact as
- Caldera launch automatically is Setup program, once you arrived
- at the menu were you suppose to choose your source disks type
- ALT F2 and go to another screen then log as root and make your
- nfs drive as described above in point 2 to 4.
- Then go back to the installtion screen with ALT F1, and type
- the famous nfsdrive as your source directory. Caldera will than
+
+ Caldera Installation
+
+ I told you that Caldera works also with that install. In fact, as
+ Caldera automatically launches its Setup program, once you arrived
+ at the menu where you are supposed to choose your source disks, type
+ ALT F2, go to another screen, then log on as root and make your
+ nfs drive as described above in points 2 to 4.
+ Then go back to the installation screen with ALT F1, and type
+ the famous nfstest as your source directory. Caldera will then
install without problem.
@@ -1887,7 +1900,7 @@ connected to the metallic DB-25 shell at one end only.
Troubleshooting
If you are experiencing any trouble with that installation you may
- report it tome and I'll try to help as best as I can.
+ report it to me and I'll try to help as best as I can.
@@ -1940,7 +1953,7 @@ connected to the metallic DB-25 shell at one end only.
port. Typical values are iobase=0x378 or iobase=0x3bc. Interrupt most
often is "irq=7".
- 3- Validate, that the kernel loads the module and finds the
+ 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".
@@ -1960,7 +1973,7 @@ connected to the metallic DB-25 shell at one end only.
Building your own "bootnet" disk
If the above bootnet disk is not suitable for your needs, I will
- present a small description on how to transform a standard bootnet
+ present a small description of how to transform a standard bootnet
disk for using "plip". This description is quite short and is
addressed to the advanced user.
@@ -1981,7 +1994,7 @@ connected to the metallic DB-25 shell at one end only.
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
+ 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
@@ -2005,7 +2018,7 @@ connected to the metallic DB-25 shell at one end only.
/mnt2/modules/modules.dep
10- insert entry for parport_pc module into module-info so
- that the user could select the parport_pc module during
+ that the user can select the parport_pc module during
installation. Append the following text to the end of
/mnt2/modules/module-info:
parport_pc
@@ -2025,18 +2038,176 @@ parport_pc
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.
+ installation. Please follow the instructions elsewhere in this how-to
+ on how to do the installation with the new disk.
-
+ Installing RedHat 7.0
+
+ This section is written by
+
+ To install RedHat 7.0 over PLIP the easiest way to go is to use a
+ patched bootnet.img which is available via
+ http://home.hetnet.nl/~ottolander. This saves the need for a driver
+ disk, which might be useful when installing on a machine which
+ floppy drive stops functioning after boot (I made this
+ bootnet-plip.img to do an install to a Toshiba Libretto 30 which has
+ a funny PCMCIA floppy drive that is no longer available after boot).
- Installing from a DOS partition
+ This disk is a full bootnet.img for RedHat 7.0, with the modules
+ necessary for PLIP added to it. Since there was enough disk space,
+ no modules had to be deleted. So you can use this image as if it
+ were a full featured bootnet.img. No need for different disks.
+
+ I am not going into detail on the actual installation procedure, but
+ there are a few things to note:
+
+
+
+ The parport module should be loaded before the PLIP
+ module. Specify i/o address and irq parameters for the parallel
+ port when inserting the parallel port module.
+
+ After inserting the parport_pc module the installer will show the
+ "Installation method" screen a second time. This is expected
+ behaviour. Choose the PLIP module this second time. No parameters
+ need to be specified when inserting the PLIP module.
+
+ When specifying network parameters, do not use a netmask of
+ 255.255.255.255 as you might normally do for a PLIP connection. If
+ you do this by accident you will have to reboot to be able to
+ mount the installation directory succesfully. Going back and
+ respecifying the parameters will not help you out.
+
+ When doing an NFS install with RedHat 7.0 make sure all files from
+ the RedHat directories from both CD's are copied to the NFS mount
+ point (cp -a RedHat for both CD's). It is not possible to use the
+ mounted CD's.
+
+
+
+ Creating your own bootnet-plip disk
+ This section is a slightly adapted copy of the procedure to create
+ a bootnet-plip image for RedHat 6.2 described by Tilmann
+ Bubeck. Thanx Tilmann!
+
+
+
+ 1) Mount a copy of the standard bootnet disk and copy all files to
+ a temporary directory:
+
+ mount -o loop -t vfat /tmp/bootnet.img /mnt/bootnet
+ cp -a /mnt/bootnet /tmp
+
+
+ 2) Gunzip the initial ramdisk, mount it and copy all files to a
+ temporary directory:
+
+ mv /tmp/bootnet/initrd.img /tmp/bootnet/initrd.gz
+ gzip -d /tmp/bootnet/initrd.gz
+ mount -o loop /tmp/bootnet/initrd /mnt/initrd
+ cp -a /mnt/initrd /tmp
+
+
+
+ 3) Gunzip and extract the modules directory with:
+
+ cd /tmp
+ zcat /tmp/initrd/modules/modules.cgz | cpio -ivd
+
+
+
+ 4) Install the kernel-BOOT-2.2.16-22 rpm and copy the modules
+ parport.o, parport_pc.o and plip.o from /lib/modules/2.2.16-22BOOT
+ to /tmp/2.2.16-22BOOT, or use the midnight commander to extract
+ these files from rpm. When building modified boot disks you will
+ always need the modules from the kernel-BOOT rpm.
+
+
+ 5) If you need additional space on your bootnet-plip disk, delete
+ an unused module from the modules directory, fe:
+
+ rm /tmp/2.2.16-22BOOT/old_tulip.o
+
+
+ Note that this is not necessary for the RedHat 7.0 bootnet
+ disk. There is enough space left for the added modules. Do *not*
+ delete modules like sunrpc.o, lockd.o, nfs.o, fat.o, vfat.o and
+ the like. This will make your disk useless. Use common sense.
+
+
+ 7) Insert a new modules dependency line into modules.dep saying
+ that module "parport_pc" needs module "parport":
+
+ echo "parport_pc: parport" >> /tmp/initrd/modules/modules.dep
+
+
+
+ 8) Insert entries for the parport_pc and plip modules into
+ module-info. These entries should look like this:
+
+
+ parport_pc
+ plip
+ "Parallel Port, Insert Before PLIP"
+ io "Base I/O address"
+ irq "IRQ level"
+ plip
+ plip
+ "PLIP (Parallel Link Interface Protocol)"
+ io "Base I/O address"
+ irq "IRQ level"
+
+
+ You probably may omit the io and irq entries for plip. Also
+ delete any entries that refer to modules that you removed from
+ the archive (ie old_tulip in the previous example).
- You can use this section if you already have a DOS partition on
- your target computer. I think it is a faster installation
- method.
+
+ 9) Copy the modified module files to the initial ramdisk:
+
+ cp -a /tmp/initrd/modules/module* /mnt/initrd/modules
+
+
+
+ 10) Unmount and gzip the initial ramdisk and copy it to the disk
+ image:
+
+ umount /mnt/initrd
+ gzip -9 /tmp/bootnet/initrd
+ cp /tmp/bootnet/initrd.gz /mnt/bootnet/initrd.img
+ umount /mnt/bootnet
+
+
+
+ 11) The file /tmp/bootnet.img is now your new
+ bootnet-plip.img. You might want to clean up your temporary
+ files:
+
+
+ rm -r /tmp/2.2.16-22BOOT
+ rm -r /tmp/initrd
+ rm -r /tmp/bootnet
+
+
+
+
+
+ Installing from a DOS partition
+
+
+ You can use this section if you already have a DOS partition on your
+ target computer. I think it is a faster installation
+ method.
Read the section 5.3.1 "Installing from a DOS partition" from
.
- I just going to help you to make the first point : "1. Get the
- following files from your nearest Debian" repository"
+ I am just going to help you to make the first point : "1. Get the
+ following files from your nearest Debian repository"
- The transfer is easy with .
+ The transfer is easy with the floppy-disc based Linux from
+ .
Export the source cdrom drive via nfs.
@@ -2098,12 +2269,12 @@ parport_pc
C:\DEBIAN> install
- Here you go to install Debian from a DOS partition. You do not need
- plip nor floppy during the installation process. Everything deals
- with the hard drive. Read the Debian install documentation, it is a
- very good and clear one.
-
+ Now you start to install Debian from a DOS partition. You do not
+ need plip or floppy during the installation process. Everything
+ deals with the hard drive. Read the Debian install documentation, it
+ is very good and clear.
+
Install the plip interface permanently
@@ -2156,7 +2327,7 @@ exit 0
Only the ifconfig lines are strictly necessary. Perhaps you will
need to add some modprobe commands if you don't use
- kerneld nor the kmod feature of new kernels 2.2.x
+ kerneld or the kmod feature of new kernels 2.2.x
Create the symbolic links in the rc*.d directories:
@@ -2266,13 +2437,13 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
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
+ network job. In that case, I shut down 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.
+ box. I'll write an "install a second parallel port" when I succeed
+ in opening the box and add that beautiful card in the last connector
+ I have left.
Need to compile a new kernel ?
@@ -2324,18 +2495,34 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
$Id$
+
+ v1.30, 13 April 2001
+
+
+
+ Corrected more mistakes in my English. Thanks again Graham.
+
+
+
v1.27, 11 August 2000
-
The SLIP line was not needed, SLIP is serial line
+ The SLIP line was not needed, SLIP is serial line
oriented. The PPP line was partly wrong, we need PPP support by
the kernel.
-
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...
+
Corrected more mistakes in my English, though I know
+ that more remain and new ones come every time I write a
+ sentence...
Added a "compatibility with a printer" section.
@@ -2347,11 +2534,13 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
id="SLACKWARE_TARGET_IP_ADRESS_IFCONFIG" name="Here"> (inverted
IP adresses). Thanks to Brad Rigby.
-
never be obsolete paragraph in Introduction section.
+
Removed obsolete paragraph from the "Introduction" section.
-
known translated version demand in the Introduction section.
+
Added request for information about translations in
+ the "Introduction" section.
-
Mentioned the what's new section at the top of the document.
+
Mentioned the "what's new section" at the top of the
+ document.
Added a vc-header in the What's new section
@@ -2369,14 +2558,11 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
-
-
v1.22, 16 June 2000
-
-
+
Added a mention to PARTED
http://www.gnu.org/software/parted as told by Andrew Clausen
(clausen@gnu.org).
@@ -2473,6 +2659,15 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
+
+
+ Graham Bosworth <graham@bozikins.connectfree.co.uk>
+
+
+ Graham corrected my bad English all over the document. Several
+ times.
+
+
Simon Forget <sforget@camelot.ca>
@@ -2488,7 +2683,7 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
Andrew Clausen <clausen@gnu.org>
- Andrew suggested me to talk about parted
+ Andrew suggested that I talk about parted
http://www.gnu.org/software/parted