mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
parent
80397276c9
commit
8e9c7797c1
|
@ -1,18 +1,31 @@
|
|||
|
||||
<!-- To-do: Apache toolbox, (development a packaged versions of Apache (Nusphere, etc.)
|
||||
|
||||
Databases currently used with Apache
|
||||
APR
|
||||
Caching
|
||||
LDAP
|
||||
Hosting
|
||||
Wireless
|
||||
Frontpage
|
||||
|
||||
|
||||
-->
|
||||
|
||||
<!doctype linuxdoc system>
|
||||
|
||||
<article>
|
||||
|
||||
<!-- Title Information -->
|
||||
|
||||
<title>Apache Overview How-to
|
||||
<title>Apache Overview HOWTO
|
||||
<author>Daniel Lopez Ridruejo, <tt/ridruejo@apache.org/
|
||||
<date>v0.4, 11 September 2000
|
||||
<date>v0.6, 8 March 2000
|
||||
|
||||
<!-- Abstract -->
|
||||
<abstract>
|
||||
The purpose of this document is to give an overview of the Apache webserver
|
||||
and related projects. It provides pointers for further information and
|
||||
This documents gives you an overview of the Apache webserver and
|
||||
related projects. It provides pointers for further information and
|
||||
implementation details.
|
||||
</abstract>
|
||||
|
||||
|
@ -20,12 +33,11 @@ implementation details.
|
|||
<toc>
|
||||
<sect>Introduction
|
||||
<p>
|
||||
The purpose of this document is to give an overview of the Apache web server
|
||||
and related projects. Apache is the <url
|
||||
name="most popular server on the Internet"
|
||||
This document gives you an overview of the Apache web server and related projects.
|
||||
Apache is the <url name="most popular server on the Internet"
|
||||
url="http://www.netcraft.com/survey/">. 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.
|
|||
<p>Disclaimer: I work for <url name="Covalent" url="http://www.covalent.net">. 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.
|
||||
<p>If you find typos, errors or you have suggestions for improvement or comments,
|
||||
please let me know so I can correct the document.
|
||||
<sect>Apache
|
||||
<p>Apache is the leading internet web server, with over 60% market share, according
|
||||
to the <url name="Netcraft survey" url="http://www.netcraft.com/survey">.
|
||||
|
@ -42,11 +56,13 @@ Several key factors have contributed to Apache's success:
|
|||
<itemize>
|
||||
<item>The <url name="Apache license" url="http://www.apache.org/LICENSE.txt">. It is
|
||||
an open source, BSD-like license that allows for both commercial and non-commercial
|
||||
usage of Apache.
|
||||
uses of Apache.
|
||||
<item>Talented community of <url name="developers" url="http://www.apache.org/contributors/index.html">
|
||||
with a variety of backgrounds and an open development process based on technical merits.
|
||||
<item>Modular architecture.
|
||||
<item>Modular architecture. Apache users can easily add functionality or taylor Apache to their
|
||||
specific enviroment.
|
||||
<item>Portable: Apache runs on nearly all flavors of Unix (and Linux), Windows, BeOs, mainframes...
|
||||
<item>Robustness and security
|
||||
</itemize>
|
||||
Many commercial vendors have adopted Apache based solutions for their products, including <url name="Oracle"
|
||||
url="http://www.oracle.com">, <url name="Red Hat" url="http://www.redhat.com"> and <url name="IBM" url="http://www.ibm.com">.
|
||||
|
@ -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.
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>W09: Introduction to the Apache Web Server
|
||||
<item>F16: Licensing issues in commercial OSS products
|
||||
</itemize>
|
||||
|
||||
<sect>Apache Software Foundation
|
||||
<p>
|
||||
<em>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.</em>
|
||||
<p>You can learn more about the foundation <url name="here" url="http://www.apache.org/foundation/">.
|
||||
<!-- members mail describing role -->
|
||||
<!-- <sect>What is important in a web server -->
|
||||
|
||||
<sect>Developing web applications with Apache
|
||||
<p>
|
||||
There are several ways of providing content with Apache.
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>W07: Web Application Technologies - surveying the landscape
|
||||
</itemize>
|
||||
|
||||
<sect1>Static
|
||||
<p>
|
||||
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.
|
||||
<sect1>CGI scripts
|
||||
<p>
|
||||
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.<p>
|
||||
|
@ -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 <htmlurl
|
||||
url="http://www.fastcgi.com">
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>F18: FastCGI -- The forgotten treasure
|
||||
</itemize>
|
||||
|
||||
<sect1>Java servlets<label id="javaservlets">
|
||||
<p>An external Java virtual machine processes requests. The JVM can reside in
|
||||
the same computer or in a different one. This is how a lot of application
|
||||
|
@ -159,13 +191,21 @@ servers work. Usually standard libraries are included for server side
|
|||
processing. You want to check <ref name="JServ" id="jserv"> and
|
||||
<ref name="Tomcat" id="tomcat">. Related Java application server projects
|
||||
can be found <ref name="here" id="applicationservers">
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>W16: Recommendations for Java-Based Web Application Architectures
|
||||
</itemize>
|
||||
|
||||
|
||||
<sect1>Embeded interpreters
|
||||
<p>An alternative to out-of-process webservers is to embed the interpreter in
|
||||
the server itself. There are roughly two categories in this kind of modules:
|
||||
Modules that answer or modify requests directly and modules aimed to process
|
||||
commands embeded in HTML pages before serving it to the client. The most
|
||||
representative approaches are <ref name="mod_perl" id="modperl"> and <ref
|
||||
representative approaches are <ref name="mod_perl" id="mod_perl"> and <ref
|
||||
name="PHP" id="php">
|
||||
|
||||
<sect>Performance and bandwidth management<label id="performance">
|
||||
<p>Raw performance is only one of the factors to consider in a web server
|
||||
(flexibility and stability come usually first).<p>
|
||||
|
@ -186,6 +226,19 @@ size of files and remote IP/domain</em>.
|
|||
<item><bf><url name="Mod_throttle_access" url="http://www.fremen.org/apache/"></bf>: useful if you are <url name="slashdotted" url="http://everything2.com/index.pl?node_id=13464">. Allows throttling based on resources
|
||||
(file, directory, etc.)
|
||||
</itemize>
|
||||
|
||||
<sect>Virtual hosting
|
||||
<p>
|
||||
Apache provides extensive virtual hosting support, there are additional modules that provide specific functionality:
|
||||
|
||||
<itemize>
|
||||
<item><url name="mod_dynvhost" url="http://funkcity.com/0101/">
|
||||
<item><url name="mod_pweb" url="http://www.joytec.de/mod_pweb.html">
|
||||
<item><url name="mod_v2h" url="http://www.fractal.net/mod_v2h.tm">
|
||||
</itemize>
|
||||
<p>
|
||||
In addition, Apache 2.0 allows children serving different domains to have different user ids, improving security.
|
||||
|
||||
<sect>Load balancing
|
||||
<p>Apache has several modules that allow distribution of requests among servers, for redundancy, increased availability, etc.
|
||||
<p>
|
||||
|
@ -201,6 +254,11 @@ can be used to target machines with under-utilized resources, thus providing fin
|
|||
requests</em>. More information at <htmlurl url="http://www.backhand.org/">.
|
||||
</itemize>
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>TH06: mod_backhand: Internals explained
|
||||
</itemize>
|
||||
|
||||
<sect>Secure transactions
|
||||
<p>There are several solutions that provide secure transactions for Apache servers.
|
||||
This enables Apache servers to be used for ecommerce or other scenarios where
|
||||
|
@ -210,7 +268,7 @@ sensitive information is exchanged (like credit card numbers).
|
|||
implementations. They are European based, unencumbered by RSA patents.
|
||||
<item><url name="Red Hat" url="http://www.redhat.com"> offers a secure server derived from Apache. Red Hat adquired C2Net, makers
|
||||
of StrongHold, another Secure server derived from Apache.
|
||||
<item><url name="Covalent" url="http://www.covalent.net"> sells secure versions of Apache as well as the RavenSSL module that
|
||||
<item><url name="Covalent" url="http://www.covalent.net"> sells secure versions of Apache as well as the CovalentSSL module that
|
||||
plugs on existing Apache installations.
|
||||
</itemize>
|
||||
<p><bf>Credit card transactions</bf>
|
||||
|
@ -222,6 +280,8 @@ Apache. Template based, tax calculations.
|
|||
clearinghouses support, failover operation, PHP, Perl, Java support.
|
||||
</itemize>
|
||||
|
||||
|
||||
|
||||
<sect>SNMP
|
||||
<p>SNMP stands for Simple Network Management Protocol. It allows monitoring
|
||||
and management of network servers, equipment, etc. SNMP modules for Apache
|
||||
|
@ -230,10 +290,12 @@ offered and integration of Apache in existing management frameworks.
|
|||
<itemize>
|
||||
<item>Open source <url name="Mod SNMP"
|
||||
url="http://www.simpleweb.org/software/packages/mod-snmp/"> for Apache 1.3.
|
||||
<item><url name="Raven SNMP" url="http://www.covalent.net"> provides
|
||||
<item><url name="Covalent SNMP" url="http://www.covalent.net"> provides
|
||||
a commercial SNMP module, support for the latest SNMPv3 standard, integration
|
||||
with HP-Openview, Tivoli, etc.
|
||||
</itemize>
|
||||
|
||||
|
||||
<sect>Authentication modules
|
||||
<p>In many situations (subscription services, sensitive information,
|
||||
private areas), user authentication is required. Apache includes basic authentication
|
||||
|
@ -244,6 +306,8 @@ The LDAP modules are specially interesting, as they allow integration with
|
|||
company and enterprise wide existing directory services.<p>
|
||||
You can find these modules at <htmlurl url="http://modules.apache.org">.
|
||||
|
||||
|
||||
|
||||
<sect>GUIs for Apache
|
||||
<p>Apache is configured thru text configuration files. This has advantages and
|
||||
disadvantages. Management can be done from any computer that has internet
|
||||
|
@ -257,7 +321,7 @@ in-depth information. Disclaimer: I am the main author of Comanche, so remember,
|
|||
there are no bugs, only undocumented features :)
|
||||
<item><url name="gui.apache.org" url="http://gui.apache.org">: GUI interfaces
|
||||
for Apache project. Programs with various degrees of development.
|
||||
<item><url name="Webmin" url="http://www.webmin.com/webmin/">: It is a nice
|
||||
<item><url name="Webmin" url="http://www.webmin.com/webmin/">: A nice
|
||||
web based interface.
|
||||
</itemize>
|
||||
|
||||
|
@ -284,7 +348,7 @@ source code of the modules included with Apache. Apache includes a simple one
|
|||
(mod_example.c) for that purpose.
|
||||
<p><bf>Writing Apache modules in other languages</bf>: There is a variety of Apache
|
||||
modules that enable third party languages to access the internal Apache API.
|
||||
The most popular is <ref name="mod_perl" id="modperl">.
|
||||
The most popular is <ref name="mod_perl" id="mod_perl">.
|
||||
<p>If you have any questions about the development of an Apache module you
|
||||
should join the Apache modules mailing list at <htmlurl url="http://modules.apache.org">.
|
||||
Remember to do your homework first, research past messages and check
|
||||
|
@ -293,11 +357,12 @@ same problem that you are experiencing and he got an useful response.
|
|||
<p>If you are interested in the development of core Apache itself, you should
|
||||
checkout the <url name="Apache development site" url="http://dev.apache.org">.
|
||||
|
||||
|
||||
<!-- <sect>Configuring Apache -->
|
||||
<sect>Apache books
|
||||
<p>
|
||||
A comprehensive list of Apache books can be found at<url
|
||||
name="http://www.apache.org/info/apache_books.html" url="here">.
|
||||
url="http://www.apache.org/info/apache_books.html" name="here">.
|
||||
<p>A couple of books
|
||||
that I personally recommend are:
|
||||
<itemize>
|
||||
|
@ -309,16 +374,28 @@ if you want to get started with Apache. Do not get fooled by the name. This is
|
|||
a comprehensive book packed with useful information.
|
||||
</itemize>
|
||||
|
||||
<sect> WebDAV
|
||||
<p>
|
||||
>From the <url name="WebDAV website" url="http://www.webdav.org">: <em>WebDAV stands for
|
||||
"Web-based Distributed Authoring and Versioning". It is a set of extensions to the HTTP protocol
|
||||
which allows users to collaboratively edit and manage files on remote web servers.</em>
|
||||
<p>It is the open standards equivalent of the MS FrontPage protocol, but it takes
|
||||
the idea several steps further. It enables other protocols to be built on top of it (See
|
||||
the <url name="Subversion website" url="http://subversion.tigris.org/"> for an example.
|
||||
|
||||
|
||||
|
||||
<sect>Java projects
|
||||
<p>
|
||||
For historical reasons, Java projects can be found both under the
|
||||
java.apache.org and jakarta.apache.org umbrellas. The final goal is that over
|
||||
time all Java pojects will move under the Jakarta umbrella.
|
||||
time all Java projects will move under the Jakarta umbrella.
|
||||
<p><em>The goal of the Jakarta Project is to provide commercial-quality
|
||||
server solutions based on the Java Platform that are developed in an
|
||||
open and cooperative fashion.</em>
|
||||
<p>The Java on Apache community is a very dynamic and active one, as shows
|
||||
the quantity and quality of its subprojects, which are described now.
|
||||
|
||||
<sect1>Ant
|
||||
<p>You can think of Ant as the Java equivalent of make. It is a big success
|
||||
with Java related projects. Developers can write Java instead of shell
|
||||
|
@ -327,6 +404,12 @@ Makefiles Ant has XML files.
|
|||
<!-- Example Ant makefile -->
|
||||
You can learn more about ANT <url name="here"
|
||||
url="http://jakarta.apache.org/ant/index.html">.
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>F19: Using Ant to build Java code
|
||||
</itemize>
|
||||
|
||||
<sect1>ORO and Regexp
|
||||
<p>ORO is a complete package that provides regular experession support for
|
||||
Java. It includes Perl5 regular expression support, glob expressions, etc.
|
||||
|
@ -380,6 +463,7 @@ url="http://jakarta.apache.org/tomcat/index.html">. The Tomcat project
|
|||
was started with a code donation from Sun Microsystems.
|
||||
|
||||
|
||||
|
||||
<sect1>Velocity
|
||||
<p><em>Velocity is a Java based template engine. It can be used as a
|
||||
stand-alone utility for generating source code, HTML, reports, or
|
||||
|
@ -432,12 +516,17 @@ page generation. He can think in more general traditional application terms.
|
|||
You can learn more about SPFC <url name="here"
|
||||
url="http://java.apache.org/spfc/index.html">
|
||||
</itemize>
|
||||
|
||||
<!-- Removed from java.apache.org
|
||||
|
||||
<sect1>mod_java
|
||||
<p>Is the Java equivalent of mod_perl. Allows access to the Apache internals
|
||||
from inside a JVM. This allows for increased flexibility and the possibility
|
||||
of writing Apache Modules directly in Java. Unfortunately, no code seems
|
||||
of writing Apache Modules directly in Java.
|
||||
Unfortunately, no code seems
|
||||
to be present at the moment. You can find more information <url
|
||||
name="here" url="http://java.apache.org/mod_java/index.html">.
|
||||
-->
|
||||
<sect1>Element Construction Set
|
||||
<p><em>Element Construction Set (ECS) is a JAVA API or generating elements for
|
||||
various markup languages it directly supports HTML 4.0 and XML, but can
|
||||
|
@ -468,7 +557,12 @@ url="http://java.apache.org/picoserver/index.html">.
|
|||
<sect1>Jetspeed
|
||||
<p><url name="Jetspeed" url="http://java.apache.org/jetspeed/site/overview.html">
|
||||
is a web based portal written in Java. It has a modular API that
|
||||
allows aggregation of differnt data sources (XML, SMTP, iCalendar)
|
||||
allows aggregation of different data sources (XML, SMTP, iCalendar)
|
||||
|
||||
<p>Related talk:
|
||||
<itemize>
|
||||
<item>TH11: Writing an enterprise information portal with JetSpeed
|
||||
</itemize>
|
||||
|
||||
<sect1>Turbine<label id="turbine">
|
||||
<p><em>Turbine is a servlet based framework that allows experienced Java developers
|
||||
|
@ -495,6 +589,18 @@ together technologies common to many open source projects like CVS and JavaDoc.
|
|||
The goal is to integrate source code and documentation to encourage code
|
||||
documentation and sharing. More information <url name="here" url="http://java.apache.org/alexandria/index.html">
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>W06: An introduction to Alexandria
|
||||
</itemize>
|
||||
|
||||
<sect1>Log4j
|
||||
<p>This package provides a logging framework that Java applications can use.
|
||||
It can be enabled at runtime without modifying the binary and has been designed
|
||||
with performance in mind. It can be found <url name="here"
|
||||
url="http://jakarta.apache.org/log4j/docs/index.html">
|
||||
|
||||
|
||||
<sect>XML projects
|
||||
<p>Directly from the Apache XML project website, its goals are:
|
||||
<itemize>
|
||||
|
@ -583,6 +689,8 @@ PDF, XML, WML, XHTML)</em>
|
|||
</itemize>
|
||||
You can learn more about Cocoon at the <url name="project homepage" url="http://xml.apache.org/cocoon/index.html">
|
||||
|
||||
|
||||
|
||||
<sect1>Xang
|
||||
<p>The goal of the Xang project is <em>make it easy for developers to build
|
||||
commercial quality XML aware applications for the Web.</em> The application
|
||||
|
@ -613,6 +721,35 @@ to other systems. On the other hand it eases interoperatibility, debugging and
|
|||
development of clients and servers for a variety of languages (C, Java,
|
||||
, Perl, Python, Tcl, etc.) since most modern languages have HTTP and XML
|
||||
modules. You can learn more at the <url name="Apache SOAP homepage" url="http://xml.apache.org/soap/">
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>W02: Rub-a-dub-dub-dubya: SOAP and the Web
|
||||
</itemize>
|
||||
|
||||
<sect1>Batik
|
||||
<p><em>Batik is a Java based toolkit for applications that want to use images in the
|
||||
<url name="Scalable Vector Graphics (SVG)" url="http://www.w3.org/TR/SVG/"> format for various
|
||||
purposes, such as viewing, generation or manipulation.</em>
|
||||
<p> It is XML centric and compliant with the W3C specification. It is a bit atypical from other Apache
|
||||
projects, in that it provides a graphical component. Batik provides hooks to extend the
|
||||
framework thru custom tags and it allows conversion from SVG to other formats like JPEG or PNG.
|
||||
<p><url name="Batik homepage" url="http://xml.apache.org/batik/index.html">
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>W14: Introduction to the Batik project.
|
||||
</itemize>
|
||||
|
||||
<sect1> Crimson
|
||||
<p> It is an alternative, Java-based, XML parser with support for XML 1.0 thru a variety
|
||||
of interfaces. It is the parser currently shipping in Sun products, and an intermediate
|
||||
step until the version 2 of Xerces is released.
|
||||
<p><url name="Crimson homepage" url="http://xml.apache.org/crimson/index.html">
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>TH08: Java API for XML processing (JAXP) version 1.1
|
||||
</itemize>
|
||||
|
||||
<sect1>Other XML projects
|
||||
<p>There are other projects based on Apache and XML that do not live under the
|
||||
Apache XML umbrella
|
||||
|
@ -624,8 +761,13 @@ Application Server for mod_perl and Apache. It allows separation of content and
|
|||
presentation.
|
||||
</itemize>
|
||||
|
||||
<p>Related talk
|
||||
<itemize>
|
||||
<item>TH04: AxKit - An XML Application server for Apache
|
||||
</itemize>
|
||||
|
||||
<sect>Perl
|
||||
<p>Perl and Apache are a powerful and popular combination. There are several projects
|
||||
<p>Perl and Apache make a powerful and popular combination. There are several projects
|
||||
that use these two technologies.
|
||||
<sect1>Embperl
|
||||
<p>Allows embedding of Perl in HTML pages. These pages are processed in the server
|
||||
|
@ -634,23 +776,26 @@ You can learn more <url name="here" url="http://perl.apache.org/embperl/index.ht
|
|||
<sect1>Mason
|
||||
<p>The <url name="Mason project" url="http://www.masonhq.com/"> embeds Perl in HTML
|
||||
with a reusable component model approach. It allows caching, templating, etc.
|
||||
<sect1>Mod_Perl<label id="modperl">
|
||||
<sect1>Mod_Perl<label id="mod_perl">
|
||||
<p>
|
||||
Mod_perl is one of the most veteran and successful Apache projects. It embeds a Perl interpreter
|
||||
in Apache and allows access to the web server internals from Perl. This allows for entire modules
|
||||
to be written in Perl or a mixture of Perl and C code.
|
||||
In the 1.3 Apache versions, one interpreter has to be embedded in each child, since the server is multiprocess based.
|
||||
In heavy traffic dynamic sites, the increased size could make a difference.
|
||||
Apache 2.0 is multithreaded, as recent versions of Perl are. The next generation of mod_perl takes advantage of this
|
||||
Apache 2.0 is multithreadeded, as recent versions of Perl are. The next generation of mod_perl takes advantage of this
|
||||
and allows for sharing of code, data and session state among interpreters. This results in a faster, leaner solution.
|
||||
<p>
|
||||
Make sure you check also <ref id="axkit" name="Axkit">
|
||||
|
||||
|
||||
|
||||
|
||||
<sect>PHP<label id="php">
|
||||
<p>From the <url name="PHP website" url="http://www.php.net"> website:
|
||||
<em>PHP is a server-side, cross-platform, HTML embedded scripting
|
||||
language.</em> PHP is a scripting language like Perl, Python or Tcl. It is
|
||||
the <url name="most popular module for Apache" url="http://www.securityspace.com/s_survey/data/man.200008/apachemods.html"> and this is due to a variety
|
||||
the <url name="most popular module for Apache" url="http://www.securityspace.com/s_survey/data/man.200102/apachemods.html"> and this is due to a variety
|
||||
of reasons:
|
||||
<itemize>
|
||||
<item>Learning curve is quite low
|
||||
|
@ -673,7 +818,7 @@ url="http://www.php.net">.
|
|||
</itemize>
|
||||
and many more. You only need to compile/use the modules you need.
|
||||
<p>PHP can be used with Apache, as an external CGI or with other webservers.
|
||||
It is crossplatform and it runs on most varieties of Unix and Windows.
|
||||
It is crossplatform and it runs on most flavors of Unix and Windows.
|
||||
<p>If you come from a Windows background, you probably have used Internet
|
||||
Information Server with Active Server Pages and MS-SQL Server. A common
|
||||
replacement in the Unix world for this trio is Apache with PHP and mySQL.
|
||||
|
@ -689,6 +834,7 @@ url="http://www.freebsd.org">, <url name="Solaris" url="http://www.sun.com">,
|
|||
<url name="Linux" url="http://www.linux.com"> or <url name="OpenBSD"
|
||||
url="http://www.openbsd.com">)
|
||||
|
||||
|
||||
<!-- examples of PHP code -->
|
||||
<sect>Python
|
||||
<p>
|
||||
|
@ -703,14 +849,25 @@ Both modules would be useful if you plan on writing Apache modules in Python
|
|||
or run existing Python CGIs faster. Mod Snake allows to embed Python in HTML
|
||||
, much like <ref name="PHP" id="php"> does.
|
||||
|
||||
<p>Related talk:
|
||||
<itemize>
|
||||
<item> F08: mod_snake: Boosting productivity with Python
|
||||
</itemize>
|
||||
|
||||
<sect>Tcl
|
||||
<p>The <url name="Tcl Apache project" url="http://tcl.apache.org"> integrates
|
||||
Tcl with the Apache webserver, like Mod_dtcl.
|
||||
Mod_Dtcl allows for embedding Tcl on HTML pages like
|
||||
<ref name="PHP" id="php"> does. Tcl is a lightweight, extensible
|
||||
Tcl with the Apache webserver. Tcl is a lightweight, extensible
|
||||
scripting language. You can learn more about Tcl <url
|
||||
url="http://dev.ajubasolutions.com/" name="here">.
|
||||
Other Tcl based Apache solutions are <url name="Neo Web Script" url="http://www.neosoft.com/neowebscript/"> and <url name="WebSH" url="http://websh.com/">
|
||||
There are several modules currently under the Apache Tcl umbrella:
|
||||
<itemize>
|
||||
<item><url name="Mod_dtcl" url="http://tcl.apache.org/mod_dtcl/"> allows for embedding Tcl on HTML pages like
|
||||
<ref name="PHP" id="php"> does.
|
||||
<item><url name="Neowebscript" url="http://tcl.apache.org/neowebscript/"> takes a similar approach
|
||||
<item><url name="Mod_tcl" url="http://www.fractal.net/mod_tcl.tm/"> takes an approach similar
|
||||
to mod_perl and runs both in 1.3.x and 2.x versions of Apache.
|
||||
</itemize>
|
||||
Other Tcl Apache project can be found at <url name="WebSH" url="http://websh.com/">.
|
||||
|
||||
<sect>Modules for other languages
|
||||
<p>This document have described modules for popular server side languages
|
||||
|
@ -731,6 +888,8 @@ number of processes and number of threads per process. Apache 2.0 introduces
|
|||
APR, the Apache Portable Runtime, which increases even more Apache's portability.
|
||||
Finally, layered I/O brings a new level of modularity to Apache development.
|
||||
|
||||
|
||||
|
||||
<sect>Migrating from Netscape (iPlanet) web servers
|
||||
<p>The bulk of the work may reside in converting custom modules from NSAPI to the Apache API.
|
||||
Nearly all the other server side technologies (Java, Perl, CGIs) should be portable with little
|
||||
|
@ -757,8 +916,13 @@ Apache for Windows supports also the ISAPI interface.
|
|||
IIS + ASP + MS-SQL server) the roughly equivalent (and highly popular) combination is Apache + PHP
|
||||
+ <url name="MySQl" url="http://www.mysql.com"> or <url name="PostgresSQL" url="http://www.postgresql.org">.
|
||||
You can learn more about PHP <ref name="here" id="php">
|
||||
<p>Support for Windows is greatly improved in the new 2.0 Apache version, still in alpha stage at the time of this writing.
|
||||
<p>Support for Windows is greatly improved in the new 2.0 Apache version, still in beta stage at the time of this writing.
|
||||
|
||||
|
||||
|
||||
<!--
|
||||
Ready to run Apaches
|
||||
-->
|
||||
<sect>Links
|
||||
<p>Additional Apache related resources
|
||||
<sect1>Websites
|
||||
|
@ -769,26 +933,27 @@ You can learn more about PHP <ref name="here" id="php">
|
|||
<item><url name="Apache today" url="http://www.apachetoday.com">
|
||||
<item><url name="Slashdot Apache section" url="http://slashdot.org/index.pl?section=apache">
|
||||
</itemize>
|
||||
|
||||
<sect1>Java application servers<label id="applicationservers">
|
||||
<p>
|
||||
These are open source application servers that build on or are known to play
|
||||
well with Apache.
|
||||
<itemize>
|
||||
<item><url name="Resin" url="http://www.caucho.com/">: Servlets, JSP, XSL
|
||||
<item><url name="Enhydra" url="http://www.enhydra.com">: Java/XML application
|
||||
<item><url name="Enhydra" url="http://www.enhydra.com/">: Java/XML application
|
||||
server.
|
||||
<item><url name="Locomotive" url="http://www.locomotive.or">: Servlets,
|
||||
<item><url name="Locomotive" url="http://www.locomotive.org/">: Servlets,
|
||||
load balancing, failover.
|
||||
<item><url name="JBoss" url="http://www.jboss.org/">: Enterprise Java Beans container, J2EE
|
||||
|
||||
</itemize>
|
||||
<sect>Contacting the author
|
||||
<p>You can contact me at <htmlurl url="ridruejo@apache.org">. I welcome suggestions
|
||||
and corrections, but please, please, do not send me messages asking me to
|
||||
troubleshoot your Apache installation. I just do not have the bandwidth and your
|
||||
mail will be most likely ignored. If you need support, consider:
|
||||
mail will be most likely ignored. If you need support:
|
||||
<itemize>
|
||||
<item>Check the error logs, read the docs, specially the <url name="FAQ" url="http://www.apache.org/docs/misc/FAQ.html">.
|
||||
<item>If you still do not find the solution, go for a walk. Afterwards read the docs,
|
||||
again.
|
||||
<item>Try comp.infosystems.www.servers.unix at <htmlurl url="http://www.deja.com">.
|
||||
Search for a similar problem.
|
||||
<item>If you are still stuck. Provide as much information as you can,
|
||||
|
@ -801,10 +966,11 @@ of course). If you are using Apache on Linux, your Linux vendor may have support
|
|||
plans that include Apache too.
|
||||
|
||||
<sect1>Translations
|
||||
<p>I encourage translations of this document. You probably should use
|
||||
<p>If you want to contribute a translation of this document you should use
|
||||
the SGML source. Check <htmlurl url="http://www.linuxdoc.org"> for info.
|
||||
Please drop me a note so I can make sure you get the most recent version
|
||||
|
||||
<!--<sect>Other web servers-->
|
||||
</article>
|
||||
|
||||
|
||||
|
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
<title> PLIP Install HOWTO
|
||||
<author>Gilles Lamiral, <tt>lamiral@mail.dotcom.fr</tt>
|
||||
<date>v1.27, 11 August 2000
|
||||
<date>v1.30, 13 April 2001
|
||||
|
||||
<abstract>
|
||||
|
||||
|
@ -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 <htmlurl
|
||||
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.
|
||||
|
||||
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:
|
||||
<newline><tt>/usr/src/linux/Documentation/networking/PLIP.txt</tt>
|
||||
<newline> on your <bf>source</bf> linux computer, Luke.
|
||||
|
||||
Alternatively, read my notes in section "Building your own cable".
|
||||
|
||||
<sect>Conventions
|
||||
<p>
|
||||
|
@ -378,12 +378,6 @@
|
|||
#
|
||||
</verb>
|
||||
|
||||
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 "<tt>$</tt>" in the remainder of this
|
||||
documentation "<tt>$</tt>", even if it should be "<tt>#</tt>". This
|
||||
is because "<tt>#</tt>" 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
|
||||
</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.
|
||||
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.
|
||||
|
||||
<sect>Network parameters
|
||||
<p>
|
||||
|
||||
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:
|
||||
<itemize>
|
||||
|
||||
|
@ -524,7 +519,7 @@ connected to the metallic DB-25 shell at one end only.
|
|||
</verb>
|
||||
|
||||
|
||||
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 <bf><tt>/etc/hosts</tt></bf>
|
||||
|
||||
<verb>
|
||||
|
@ -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
|
||||
</verb>
|
||||
|
||||
Lines with <tt>nfs</tt> or <tt>portmapper</tt> have to be there. NFS
|
||||
on tcp ? progress have been made !
|
||||
Lines with <tt>nfs</tt> or <tt>portmapper</tt> 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 <tt>portmap</tt>, <tt>mountd</tt>, <tt>nfs</tt>:
|
||||
|
||||
|
@ -804,12 +801,12 @@ connected to the metallic DB-25 shell at one end only.
|
|||
</verb>
|
||||
|
||||
<tt>/etc/rc.d/init.d/</tt> is <tt>/sbin/init.d/</tt> 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 <bf>source</bf> box
|
||||
and clean the test:
|
||||
and when the test is good remove the test directory:
|
||||
|
||||
<verb>
|
||||
$ mkdir /tmp/nfstest
|
||||
|
@ -885,8 +882,8 @@ connected to the metallic DB-25 shell at one end only.
|
|||
<bf>fips20.zip</bf> file) in <tt>/cdrom/debian/tools/fips15.zip</tt>
|
||||
(It supposes your cdrom is mounted on <bf>/cdrom</bf>)
|
||||
|
||||
I guess you are on a Unix world but you're not compelled to do
|
||||
so. Go in a good working place on the <bf>source</bf> computer:
|
||||
I guess you are on a Unix world but you're not compelled to be. Go
|
||||
in a good working place on the <bf>source</bf> computer:
|
||||
|
||||
<verb>
|
||||
$ 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,16 +926,20 @@ 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.
|
||||
|
||||
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:
|
||||
</verb>
|
||||
|
||||
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. <tt>mcopy</tt> is
|
||||
faster to type than <tt>mkdir, mount, cp, umount, rmdir</tt>.
|
||||
|
||||
Boot the <bf>target</bf> with the floppy. Run fips while reading the
|
||||
section "Using FIPS" in the file <bf>fips.doc</bf>
|
||||
|
||||
<bf>Do not forget</bf> to answer <bf>yes</bf> when fips ask for a
|
||||
<bf>Do not forget</bf> to answer <bf>yes</bf> 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 <bf>target</bf> 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 <ref
|
||||
id="INSTALL_FROM_A_DOS_PARTITION" name="Installing from a DOS
|
||||
partition">. 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.
|
|||
|
||||
<verb>
|
||||
$ mount -t iso9660 /dev/hdd /cdrom
|
||||
</verb>
|
||||
|
||||
The device for your CDROM may be /dev/hdb or /dev/hdc or another
|
||||
device (SCSI), depending on where is plugged your CDROM.
|
||||
|
||||
<verb>
|
||||
$ cd /cdrom/debian/dists/stable/main/disks-i386/current/
|
||||
</verb>
|
||||
|
||||
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
|
||||
"<tt>resc1440.bin</tt>" 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 <em>Installation-HOWTO</em>, 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
|
||||
<em>Installation-HOWTO</em>, especially if you have more than 1024
|
||||
cylinders and an old version of LILO.
|
||||
|
||||
If you previously ran the <tt>FIPS</tt> program, you see the
|
||||
<tt>hda1</tt> partition (<tt>DOSFAT16</tt>). Switch to the next free
|
||||
|
@ -1239,7 +1247,7 @@ connected to the metallic DB-25 shell at one end only.
|
|||
Select <tt><YES></tt> and press <tt><ENTER></tt>
|
||||
|
||||
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).
|
||||
|
||||
<verb>
|
||||
Next: Mount a Previously-Initialized Partition</verb>
|
||||
|
@ -1581,7 +1589,7 @@ connected to the metallic DB-25 shell at one end only.
|
|||
|
||||
Remove the floppy and press <tt><ENTER></tt>
|
||||
|
||||
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
|
||||
<tt>Ctrl-Alt-Del</tt>
|
||||
|
||||
|
@ -1671,30 +1679,32 @@ connected to the metallic DB-25 shell at one end only.
|
|||
|
||||
<item>Have fun.
|
||||
|
||||
<item>Mail me a feedback.
|
||||
<item>Mail me some feedback.
|
||||
|
||||
</itemize>
|
||||
|
||||
<sect>Installing Slackware, RedHat, Caldera
|
||||
<sect>Installing Slackware, Caldera
|
||||
<p>
|
||||
This section is written by Florent SAUNIER. <newline>
|
||||
sabetflo@freesurf.fr
|
||||
|
||||
Here, '&' is used for the root prompt, rather than '$'.
|
||||
<p>
|
||||
|
||||
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.
|
||||
|
||||
<sect1>Slakware installation
|
||||
<p>
|
||||
|
@ -1702,151 +1712,160 @@ connected to the metallic DB-25 shell at one end only.
|
|||
<item>1- Make 2 disks (boot and root) and prepare a plip disk
|
||||
<item>2- Install PLIP module
|
||||
<item>3- Create a NFS drive to use PLIP with
|
||||
<item>4- Launch the Slakware (or Caldera) Installation
|
||||
<Item>5- Drink all remainder of coffee and go to bed waiting completion of
|
||||
installation
|
||||
<item>4- Launch the Slackware (or Caldera) Installation
|
||||
<Item>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.
|
||||
</itemize>
|
||||
</p>
|
||||
|
||||
|
||||
<sect2>Making boot,root and plip disks
|
||||
<p>
|
||||
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.
|
||||
|
||||
<sect3> 1a- creating the boot and root disks.
|
||||
<p>
|
||||
|
||||
From ms-dos create the boot disk by typing:
|
||||
From DOS (PC-DOS, DR-DOS, FreeDOS, ...) create the boot disk by typing:
|
||||
<verb>
|
||||
rawrite bareapm.i
|
||||
</verb>
|
||||
then create the root disks:
|
||||
<verb>
|
||||
rawrite color.gz.a (if you are using color screen)
|
||||
rawrite color.gz.a (if you are using a color screen)
|
||||
</verb>
|
||||
|
||||
<sect3> 1b- Creating the PLIP disk
|
||||
<p>
|
||||
On a dos format disk copy the following file :
|
||||
On a DOS formated disk copy the following files:
|
||||
<itemize>
|
||||
<item>1- plip.o (object program for the plip tool)
|
||||
<item>2- parport_pc
|
||||
<item>3- parport
|
||||
</itemize>
|
||||
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
|
||||
<tt>/MODULES</tt>. The same applies to the Caldera
|
||||
installation. Run a "find" if you cannot find them.
|
||||
|
||||
<sect3> 1c- launching the installation.
|
||||
<p>
|
||||
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.
|
||||
</sect2>
|
||||
<sect2>2a- Install PLIP module
|
||||
<p>
|
||||
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:
|
||||
<verb>
|
||||
& 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
|
||||
</verb>
|
||||
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.
|
||||
<verb>
|
||||
& 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'
|
||||
</verb>
|
||||
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.
|
||||
</p></sect2>
|
||||
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)
|
||||
|
||||
|
||||
</sect2>
|
||||
<sect2>3a- Now create your NFS drive.
|
||||
|
||||
<p>From that point I have choosed to use the creation of a NFS drive
|
||||
<p>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: <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>
|
||||
& ping target
|
||||
</verb>
|
||||
then create your nfs drive:
|
||||
<verb>
|
||||
& cd /
|
||||
& mkdir nfsdrive
|
||||
mount -t nfs 192.168.0.2:/cdrom /nfstest
|
||||
</verb>
|
||||
<it>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</it>
|
||||
id="SLACKWARE_TARGET_IP_ADRESS_IFCONFIG">
|
||||
|
||||
Now everything is set up and you are ready to launch the Slakware
|
||||
<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>
|
||||
$ ping target
|
||||
</verb>
|
||||
then mount your nfs drive on the target:
|
||||
<verb>
|
||||
$ cd /
|
||||
$ mkdir nfstest
|
||||
$ mount -t nfs 192.168.0.2:/cdrom /nfstest
|
||||
</verb>
|
||||
<it>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</it>.
|
||||
|
||||
Now everything is set up and you are ready to launch the Slackware
|
||||
installation program, by typing "setup".
|
||||
|
||||
<bf>note:</bf>if you do not have enough memory, below 8mb
|
||||
setup will not being launched then, you will have to make a swap
|
||||
<bf>note:</bf>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
|
||||
<bf>& fdisk</bf>
|
||||
note your swap disk name eg /hda3
|
||||
quit fdisk with 'w'
|
||||
Once its done type:
|
||||
<verb>
|
||||
& mkswap -c /dev/hda3
|
||||
& swapon /dev/ha3
|
||||
First, create your disk partition with your swap by typing
|
||||
<verb>
|
||||
$ fdisk
|
||||
</verb>
|
||||
|
||||
Note which is your swap partition (e.g. /hda3), then quit fdisk with
|
||||
'w'. Once it's done, type:
|
||||
|
||||
<verb>
|
||||
$ mkswap -c /dev/hda3
|
||||
$ swapon /dev/ha3
|
||||
</verb>
|
||||
|
||||
Your swap is now set up.
|
||||
You may then launch the "setup" program.
|
||||
|
||||
</p></sect2>
|
||||
<sect2>4a- Installing Slakware
|
||||
<sect2>4a- Installing Slakware
|
||||
<p>
|
||||
the setup programm shows various menu:
|
||||
the setup programm shows various menu items:
|
||||
<itemize>
|
||||
<item>HELP - Help file
|
||||
<item>KEYMAP - Keyboard select (Azerty at least !!!)
|
||||
<item>KEYMAP - Keyboard select (Azerty at last !!!)
|
||||
<item>ADDSWAP - Create and select swap
|
||||
<item>TARGET - Select target
|
||||
<item>SOURCE - select the source
|
||||
<item>SELECT - Select pakages to install
|
||||
<item>CONFIGURE - Set up your linux system and make LILO
|
||||
<item>SELECT - Select packages to install
|
||||
<item>CONFIGURE - Set up your Linux system and make LILO
|
||||
<item>EXIT - bye bye setup
|
||||
</itemize>
|
||||
|
||||
|
@ -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
|
||||
<it>'/slakware' because your drive must point to your
|
||||
slakware CDROM directory</it>
|
||||
4e- Select the source. tricky stuff: choose "Installing from a
|
||||
drive", then type the drive so : /nfstest/slackware
|
||||
<it>'/slackware' because your drive must point to your slackware
|
||||
CDROM directory</it>
|
||||
|
||||
4f- Select packages to install
|
||||
|
||||
4g- Wait, Wait, Wait and Wait........
|
||||
</p>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1><bf> Caldera Installation</bf>
|
||||
<p>
|
||||
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
|
||||
<sect1>Caldera Installation
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</sect1>
|
||||
|
@ -1887,7 +1900,7 @@ connected to the metallic DB-25 shell at one end only.
|
|||
|
||||
<sect1>Troubleshooting
|
||||
<p>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.
|
||||
</p>
|
||||
</sect1>
|
||||
|
||||
|
@ -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".
|
||||
|
||||
<item>3- Validate, that the kernel loads the module and finds the
|
||||
<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".
|
||||
|
||||
|
@ -1960,7 +1973,7 @@ connected to the metallic DB-25 shell at one end only.
|
|||
<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
|
||||
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.
|
|||
|
||||
<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
|
||||
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</tt>
|
||||
|
||||
<item>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: <verb>
|
||||
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.
|
||||
|
||||
<sect>Installing RedHat 7.0
|
||||
<p>
|
||||
This section is written by <url name="Leonard den Ottolander"
|
||||
url="mailto:leonardjo@hetnet.nl">
|
||||
|
||||
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).
|
||||
|
||||
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:
|
||||
|
||||
<itemize>
|
||||
<item><p>
|
||||
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.
|
||||
<item><p>
|
||||
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.
|
||||
<item><p>
|
||||
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.
|
||||
<item><p>
|
||||
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.
|
||||
</itemize>
|
||||
|
||||
|
||||
|
||||
<sect> Installing from a DOS partition <label
|
||||
id="INSTALL_FROM_A_DOS_PARTITION">
|
||||
<sect1>Creating your own bootnet-plip disk
|
||||
<p>
|
||||
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!
|
||||
|
||||
You can use this section if you already have a DOS partition on
|
||||
your <bf>target</bf> computer. I think it is a faster installation
|
||||
method.
|
||||
<itemize>
|
||||
<item><p>
|
||||
1) Mount a copy of the standard bootnet disk and copy all files to
|
||||
a temporary directory:
|
||||
<verb>
|
||||
mount -o loop -t vfat /tmp/bootnet.img /mnt/bootnet
|
||||
cp -a /mnt/bootnet /tmp
|
||||
</verb>
|
||||
<item><p>
|
||||
2) Gunzip the initial ramdisk, mount it and copy all files to a
|
||||
temporary directory:
|
||||
<verb>
|
||||
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
|
||||
</verb>
|
||||
|
||||
<item><p>
|
||||
3) Gunzip and extract the modules directory with:
|
||||
<verb>
|
||||
cd /tmp
|
||||
zcat /tmp/initrd/modules/modules.cgz | cpio -ivd
|
||||
</verb>
|
||||
|
||||
<item><p>
|
||||
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.
|
||||
|
||||
<item><p>
|
||||
5) If you need additional space on your bootnet-plip disk, delete
|
||||
an unused module from the modules directory, fe:
|
||||
<verb>
|
||||
rm /tmp/2.2.16-22BOOT/old_tulip.o
|
||||
</verb>
|
||||
|
||||
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.
|
||||
|
||||
<item><p>
|
||||
6) Rebuild the modules archive:
|
||||
<verb>
|
||||
find /tmp/2.2.16-22BOOT | cpio -ov -H crc | gzip > \
|
||||
/tmp/initrd/modules/modules.cgz
|
||||
</verb>
|
||||
|
||||
<item><p>
|
||||
7) Insert a new modules dependency line into modules.dep saying
|
||||
that module "parport_pc" needs module "parport":
|
||||
<verb>
|
||||
echo "parport_pc: parport" >> /tmp/initrd/modules/modules.dep
|
||||
</verb>
|
||||
|
||||
<item><p>
|
||||
8) Insert entries for the parport_pc and plip modules into
|
||||
module-info. These entries should look like this:
|
||||
|
||||
<verb>
|
||||
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"
|
||||
</verb>
|
||||
|
||||
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).
|
||||
|
||||
<item><p>
|
||||
9) Copy the modified module files to the initial ramdisk:
|
||||
<verb>
|
||||
cp -a /tmp/initrd/modules/module* /mnt/initrd/modules
|
||||
</verb>
|
||||
|
||||
<item><p>
|
||||
10) Unmount and gzip the initial ramdisk and copy it to the disk
|
||||
image:
|
||||
<verb>
|
||||
umount /mnt/initrd
|
||||
gzip -9 /tmp/bootnet/initrd
|
||||
cp /tmp/bootnet/initrd.gz /mnt/bootnet/initrd.img
|
||||
umount /mnt/bootnet
|
||||
</verb>
|
||||
|
||||
<item><p>
|
||||
11) The file /tmp/bootnet.img is now your new
|
||||
bootnet-plip.img. You might want to clean up your temporary
|
||||
files:
|
||||
|
||||
<verb>
|
||||
rm -r /tmp/2.2.16-22BOOT
|
||||
rm -r /tmp/initrd
|
||||
rm -r /tmp/bootnet
|
||||
</verb>
|
||||
|
||||
</itemize>
|
||||
|
||||
|
||||
<sect> Installing from a DOS partition <label
|
||||
id="INSTALL_FROM_A_DOS_PARTITION">
|
||||
|
||||
<p>
|
||||
You can use this section if you already have a DOS partition on your
|
||||
<bf>target</bf> computer. I think it is a faster installation
|
||||
method.
|
||||
|
||||
Read the section 5.3.1 "Installing from a DOS partition" from
|
||||
<htmlurl
|
||||
|
@ -2046,11 +2217,11 @@ parport_pc
|
|||
url="file:///cdrom/dists/stable/main/disks-i386/current/ch-install-methods.html#s-install-drive"
|
||||
name="ch-install-methods.html">.
|
||||
|
||||
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 <htmlurl
|
||||
url="http://www.toms.net/rb/home.html" name="tomsrtbt">.
|
||||
The transfer is easy with the floppy-disc based Linux from
|
||||
<htmlurl url="http://www.toms.net/rb/home.html" name="tomsrtbt">.
|
||||
|
||||
Export the <bf>source</bf> cdrom drive via nfs.
|
||||
|
||||
|
@ -2098,10 +2269,10 @@ parport_pc
|
|||
C:\DEBIAN> install
|
||||
</verb>
|
||||
|
||||
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.
|
||||
|
||||
|
||||
<sect>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 <tt>modprobe</tt> commands if you don't use
|
||||
<tt>kerneld</tt> nor the <tt>kmod</tt> feature of new kernels 2.2.x
|
||||
<tt>kerneld</tt> or the <tt>kmod</tt> feature of new kernels 2.2.x
|
||||
|
||||
Create the symbolic links in the <tt>rc*.d</tt> 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.
|
||||
|
||||
|
||||
<sect>Need to compile a new kernel ?
|
||||
|
@ -2324,18 +2495,34 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
|
|||
$Id$
|
||||
|
||||
<descrip>
|
||||
|
||||
<tag>v1.30, 13 April 2001
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Added section "Installing RedHat 7.0". Thanks Leonard.
|
||||
</itemize>
|
||||
|
||||
<tag>v1.28, 18 December 2000
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Corrected more mistakes in my English. Thanks again Graham.
|
||||
</itemize>
|
||||
|
||||
|
||||
<tag>v1.27, 11 August 2000
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
|
||||
<p> <item>The SLIP line was not needed, SLIP is serial line
|
||||
<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> Corrected more mistakes in my English, though I know
|
||||
that more remain and new ones come every time I write a
|
||||
sentence...
|
||||
|
||||
<p> <item> 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.
|
||||
|
||||
<p> <item> never be obsolete paragraph in Introduction section.
|
||||
<p> <item> Removed obsolete paragraph from the "Introduction" section.
|
||||
|
||||
<p> <item> known translated version demand in the Introduction section.
|
||||
<p> <item> Added request for information about translations in
|
||||
the "Introduction" section.
|
||||
|
||||
<p> <item> Mentioned the what's new section at the top of the document.
|
||||
<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
|
||||
|
||||
|
@ -2369,14 +2558,11 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
|
|||
</p>
|
||||
</descrip>
|
||||
|
||||
|
||||
|
||||
<descrip>
|
||||
<tag>v1.22, 16 June 2000
|
||||
<p>
|
||||
<itemize>
|
||||
|
||||
<item>
|
||||
<item> 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
|
|||
</p>
|
||||
</descrip>
|
||||
|
||||
<descrip>
|
||||
<tag>
|
||||
Graham Bosworth <graham@bozikins.connectfree.co.uk>
|
||||
</tag>
|
||||
<p>
|
||||
Graham corrected my bad English all over the document. Several
|
||||
times.
|
||||
</descrip>
|
||||
|
||||
<descrip>
|
||||
<tag>Simon Forget <sforget@camelot.ca>
|
||||
</tag>
|
||||
|
@ -2488,7 +2683,7 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
|
|||
<tag>Andrew Clausen <clausen@gnu.org>
|
||||
</tag>
|
||||
<p>
|
||||
Andrew suggested me to talk about parted
|
||||
Andrew suggested that I talk about parted
|
||||
http://www.gnu.org/software/parted
|
||||
</p>
|
||||
</descrip>
|
||||
|
@ -2502,15 +2697,6 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
|
|||
</p>
|
||||
</descrip>
|
||||
|
||||
<descrip>
|
||||
<tag>
|
||||
Graham Bosworth <graham@bozikins.connectfree.co.uk>
|
||||
</tag>
|
||||
<p>
|
||||
Graham corrected my bad english all over the document.
|
||||
</p>
|
||||
</descrip>
|
||||
|
||||
<descrip>
|
||||
<tag>
|
||||
Tomas Pospisek <tpo@spin.ch>
|
||||
|
@ -2551,6 +2737,18 @@ post-install parport_pc echo 7 > /proc/parport/0/irq
|
|||
</p>
|
||||
</descrip>
|
||||
|
||||
<descrip>
|
||||
<tag>
|
||||
Leonard den Ottolander <leonardjo@hetnet.nl>
|
||||
</tag>
|
||||
<p>
|
||||
Leonard wrote the section called "Installing RedHat 7.x".
|
||||
|
||||
</p>
|
||||
</descrip>
|
||||
|
||||
|
||||
|
||||
|
||||
</article>
|
||||
|
||||
|
|
Loading…
Reference in New Issue