LDP/LDP/howto/docbook/HP-HOWTO.sgml

6560 lines
169 KiB
Plaintext
Raw Blame History

<!-- HP-HOWTO -->
<!-- Chercher les ??? et les remplacer -->
<!DOCTYPE BOOK PUBLIC "-//HP-HOWTO//DTD DocBook V3.1-Based Extension//EN" [
<!ENTITY curdate "15th of March 2000">
<!ENTITY curver "0.88">
<!ENTITY curker "2.2.14">
<!ENTITY oui "Yes">
<!ENTITY non "No">
<!ENTITY aucune "None">
<!ENTITY et "and">
<!ENTITY ou "or">
<!ENTITY avec "with">
<!ENTITY ref "Reference">
<!ENTITY net "network card">
<!ENTITY pilote "driver">
<!ENTITY nointer "Not interesting">
<!ENTITY celref '
<entry>&ref;</entry>
'>
<!ENTITY tabi "The following table provides all of the informations on the support for this hardware by ">
<!ENTITY tabintrol '
<para>&tabi; Linux.</para>
'>
<!ENTITY tabintrox '
<para>&tabi; XFree86.</para>
'>
<!ENTITY celpec '
<entry>Linux support</entry>
'>
<!ENTITY celtest '
<entry>Tes-ted</entry>
'>
<!ENTITY tabmach '
<Tgroup ALIGN="char" CHAROFF="50" COLS="10">
<Colspec ALIGN="left" COLNUM="1" COLSEP="1" COLWIDTH="5*">
<Colspec ALIGN="left" COLNUM="2" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="3" COLSEP="1" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="4" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="5" COLSEP="1" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="6" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="7" COLSEP="1" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="8" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="9" COLSEP="1" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="10" COLSEP="0" COLWIDTH="1*">
<Thead>
<row>
<entry>Machine</entry>
<entry>Graphic Card</entry>
&celpec;
&celnet;
&celpec;
&celscsi;
&celpec;
&celson;
&celpec;
&celtest;
</row>
</Thead>
'>
<!ENTITY tabsize '
<Tgroup ALIGN="char" CHAROFF="50" COLS="4">
<Colspec ALIGN="left" COLNUM="1" COLSEP="1" COLWIDTH="8*">
<Colspec ALIGN="left" COLNUM="2" COLSEP="1" COLWIDTH="4*">
<Colspec ALIGN="left" COLNUM="3" COLSEP="1" COLWIDTH="4*">
<Colspec ALIGN="left" COLNUM="4" COLSEP="1" COLWIDTH="4*">
<Thead>
<row>
<entry>Simultaneous users</entry>
<entry>RAM size</entry>
<entry>Disk size</entry>
<entry>Machine example</entry>
</row>
</Thead>
'>
<!ENTITY tabmon '
<Tgroup ALIGN="char" CHAROFF="50" COLS="8">
<Colspec ALIGN="left" COLNUM="1" COLSEP="1" COLWIDTH="3*">
<Colspec ALIGN="left" COLNUM="2" COLSEP="1" COLWIDTH="5*">
<Colspec ALIGN="left" COLNUM="3" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="4" COLSEP="1" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="5" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="6" COLSEP="0" COLWIDTH="3*">
<Colspec ALIGN="left" COLNUM="7" COLSEP="1" COLWIDTH="3*">
<Colspec ALIGN="left" COLNUM="8" COLSEP="0" COLWIDTH="2*">
<Thead>
<row>
&celref;
<entry>Name</entry>
<entry>Vert. F. (Hz)</entry>
<entry>Hor. F. (kHz)</entry>
<entry>Bandwidth (MHz)</entry>
<entry>Resol</entry>
<entry>Freq. (Hz)</entry>
&celtest;
</row>
</Thead>
'>
<!ENTITY tabopt '
<Tgroup ALIGN="char" CHAROFF="50" COLS="5">
<Colspec ALIGN="left" COLNUM="1" COLSEP="1" COLWIDTH="4*">
<Colspec ALIGN="left" COLNUM="2" COLSEP="1" COLWIDTH="4*">
<Colspec ALIGN="left" COLNUM="3" COLSEP="0" COLWIDTH="4*">
<Colspec ALIGN="left" COLNUM="4" COLSEP="1" COLWIDTH="4*">
<Colspec ALIGN="left" COLNUM="5" COLSEP="0" COLWIDTH="2*">
<Thead>
<row>
&celref;
<entry>Card type</entry>
<entry>Chipset</entry>
&celpec;
&celtest;
</row>
</Thead>
'>
<!ENTITY tabref '
<Tgroup ALIGN="char" CHAROFF="50" COLS="2">
<Colspec ALIGN="left" COLNUM="1" COLSEP="0" COLWIDTH="2*">
<Colspec ALIGN="left" COLNUM="2" COLSEP="0" COLWIDTH="4*">
<Thead>
<row>
<entry>Subject</entry>
<entry>URL</entry>
</row>
</Thead>
'>
<!ENTITY chipbx '
Chipset BX<superscript><Link LinkEnd="bx">Rem.</link></superscript>
'>
<!ENTITY xu800 '
<superscript><Link LinkEnd="xu800">Rem.</link></superscript>
'>
<!ENTITY moddos '
<superscript><Link LinkEnd="moddos">Rem.</link></superscript>
'>
<!ENTITY lc2000 '
<superscript><Link LinkEnd="lc2000">Rem.</link></superscript>
'>
<!ENTITY lh6000 '
<superscript><Link LinkEnd="lh6000">Rem.</link></superscript>
'>
<!ENTITY coper '
Chipset i820<superscript><Link LinkEnd="coper">Rem.</link></superscript>
'>
<!ENTITY xfree86 '
XFree 3.3.6<superscript><Link LinkEnd="xfree86">Rem.</link></superscript>
'>
<!ENTITY fb '
&xfree86; in Frame Buffer mode (FBDEV)<superscript><Link LinkEnd="fbdev">Rem.</link></superscript>
'>
<!ENTITY celsvga '
<entry>&oui; &xfree86; (SVGA)</entry>
'>
<!ENTITY cels3 '
<entry>&oui; &xfree86; (S3)</entry>
'>
<!ENTITY cels3triov2 '
<entry>S3 Trio 64V2 PCI</entry>
&celsvga;
'>
<!ENTITY celmilii '
<entry>Matrox Millenium II PCI</entry>
&celsvga;
'>
<!ENTITY celmiliiagp '
<entry>Matrox Millenium II AGP</entry>
&celsvga;
'>
<!ENTITY celmilg100 '
<entry>Matrox Productiva G100 AGP<superscript><link LinkEnd="g100">Rem.</link></superscript></entry>
&celsvga;
'>
<!ENTITY celmilp200 '
<entry>Matrox Productiva G200 AGP</entry>
&celsvga;
'>
<!ENTITY celmilg200 '
<entry>Matrox Millenium G200 AGP</entry>
&celsvga;
'>
<!ENTITY celmilg250 '
<entry>Matrox Millenium G250 AGP</entry>
&celbof;
'>
<!ENTITY celmilg400 '
<entry>Matrox Millenium G400D AGP</entry>
&celsvga;
'>
<!ENTITY celati2c '
<entry>ATI Rage II C AGP</entry>
<entry>&oui; &xfree86; (Mach 64)</entry>
'>
<!ENTITY celatipro '
<entry>ATI Rage Pro ZX AGP</entry>
<entry>&oui; &xfree86; (Mach 64)</entry>
'>
<!ENTITY celatiltpro '
<entry>ATI Rage LT Pro</entry>
<entry>&oui; &xfree86; (Mach 64)</entry>
'>
<!ENTITY celatiport '
<entry>ATI</entry>
&celbof;
'>
<!ENTITY celsisagp '
<entry>Sis 5595 AGP</entry>
<entry>&oui; &fb;</entry>
'>
<!ENTITY celcl5424 '
<entry>Cirrus Logic GD 5424 PCI</entry>
<entry>&oui; &xfree86; (SVGA)</entry>
'>
<!ENTITY celcl5446 '
<entry>Cirrus Logic GD 5446 PCI</entry>
&celsvga;
'>
<!ENTITY celcl5465 '
<entry>Cirrus Logic GD 5465 AGP<superscript><Link LinkEnd="cl5465">Rem.</link></superscript></entry>
<entry>&oui; &xfree86; (SVGA)</entry>
'>
<!ENTITY celelsa '
<entry>Elsa Gloria Synergy<superscript><Link LinkEnd="elsa">Rem.</link></superscript></entry>
<entry>&oui; &xfree86; (3D Labs)</entry>
'>
<!ENTITY celelsap '
<entry>Elsa Gloria Synergy + AGP<superscript><Link LinkEnd="elsa">Rem.</link></superscript></entry>
<entry>&oui; &xfree86; (3D Labs)</entry>
'>
<!ENTITY celelsaii '
<entry>Elsa Gloria Synergy II AGP</entry>
<entry>&oui; &xfree86; (SVGA)</entry>
'>
<!ENTITY celgvx1 '
<entry>3DLabs Oxygen GVX1 AGP</entry>
<entry>&oui; &fb;</entry>
'>
<!ENTITY celneo128 '
<entry>Neomagic MagicGraph 128XD NM2160</entry>
&celsvga;
'>
<!ENTITY celneo256 '
<entry>Neomagic MagicGraph 256AV NM2200</entry>
&celsvga;
'>
<!ENTITY celct65554 '
<entry>Chips & Technologies CT65554</entry>
&celsvga;
'>
<!ENTITY cellynxe '
<entry>Silicon Motion LynxE SM810<superscript><link LinkEnd="lynxe">Rem.</link></superscript></entry>
&celsvga;
'>
<!ENTITY celaccele '
<entry>Accel Eclipse PCI</entry>
<entry>&oui; &fb; &nointer;</entry>
'>
<!ENTITY celaccelg '
<entry>Accel Galaxy AGP</entry>
<entry>&oui; &fb; &nointer;</entry>
'>
<!ENTITY celfx4 '
<entry>HP Fx-4 AGP</entry>
<entry>&non; &fb; &nointer;</entry>
'>
<!ENTITY celfx6 '
<entry>HP Fx-6 AGP</entry>
<entry>&non; &fb; &nointer;</entry>
'>
<!ENTITY celi810 '
<entry>Intel i810 AGP<superscript><link LinkEnd="i810">Rem.</link></superscript></entry>
<entry>&oui; &xfree86; (XFCom i810)</entry>
'>
<!ENTITY celt9000 '
<entry>Trident TVGA 9000i</entry>
&celsvga;
'>
<!ENTITY cel5013 '
<entry>Intel i82557 / i82558 10/100 BT (D5013A/B)</entry>
<entry>&oui; &pilote; eepro-100</entry>
'>
<!ENTITY cel5013i '
<entry>Intel S82093A / i82559 10/100 BT</entry>
<entry>&oui; &pilote; eepro-100</entry>
'>
<!ENTITY celhp100 '
<entry>Carte 100VG (J2585B)</entry>
<entry>&oui; &pilote; hp100</entry>
'>
<!ENTITY celrealtek '
<entry>Carte HP chipset RealTek</entry>
<entry>&oui; &pilote; RealTek</entry>
'>
<!ENTITY celpilote3com '
<entry>&oui; &pilote; 3c59x<superscript><Link LinkEnd="c3c59x">Rem.</link></superscript></entry>
'>
<!ENTITY cel3com '
<entry>3Com 905B-TX 10/100 BT<superscript><Link LinkEnd="c3com">Rem.</link></superscript></entry>
&celpilote3com;
'>
<!ENTITY cel3com905c '
<entry>3Com 905C-TX 10/100 BT</entry>
&celpilote3com;
'>
<!ENTITY celpcnet '
<entry>&oui; &pilote; pcnet32</entry>
'>
<!ENTITY celamd '
<entry>AMD 79C971 KC 10/100 BT</entry>
&celpcnet;
'>
<!ENTITY celamd2 '
<entry>AMD 79C972 AKC 10/100 BT</entry>
&celpcnet;
'>
<!ENTITY celsmc1211 '
<entry>SMC 1211 TX EZ Card 10/100 BT</entry>
<entry>&oui; &pilote; rtl8139</entry>
'>
<!ENTITY celnetraid '
<entry>AMI Megaraid (Raid 0, 1, 3, 5, 10, 50)</entry>
<entry>&oui; &pilote; megaraid<superscript><Link LinkEnd="netraid">Rem.</link></superscript></entry>
'>
<!ENTITY celncr53 '
<entry>&oui; &pilote; ncr-53c8xx<superscript><Link LinkEnd="ncr53c8xx">Rem.</link></superscript></entry>
'>
<!ENTITY celmixte1 '
<entry>AMD 79C971 KC 10/100 BT + SCSI (D6692A)<superscript><Link LinkEnd="mixte1">Rem.</link></superscript></entry>
&celpcnet;
<entry>Symbios Logic 53c875 &avec; &net; (D6692A)</entry>
&celncr53;
'>
<!ENTITY celmixte2 '
<entry>AMD 79C974 KC 10/100 BT + SCSI</entry>
&celpcnet;
<entry>Symbios Logic 8751SP &avec; &net;</entry>
&celncr53;
'>
<!ENTITY celaicaro '
<entry>Adaptec ARO Raidport</entry>
&celnon;
'>
<!ENTITY celaic6080 '
<entry>Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI</entry>
<entry>&oui; &pilote; aic7xxx</entry>
'>
<!ENTITY celaic7880 '
<entry>Adaptec AIC 7880 UW PCI</entry>
<entry>&oui; &pilote; aic7xxx</entry>
'>
<!ENTITY celaic7880D '
<entry>Adaptec AIC 7880 UWD PCI</entry>
<entry>&oui; &pilote; aic7xxx</entry>
'>
<!ENTITY celaic7880x2 '
<entry>2 Adaptec AIC 7880 UW PCI</entry>
<entry>&oui; &pilote; aic7xxx</entry>
'>
<!ENTITY celaic7895 '
<entry>Adaptec AIC 7895H PCI</entry>
<entry>&oui; &pilote; aic7xxx</entry>
'>
<!ENTITY celaic2910 '
<entry>Adaptec AIC 2910bui (7860) PCI</entry>
<entry>&oui; &pilote; aic7xxx</entry>
'>
<!ENTITY celaic-ncr '
<entry>Adaptec AIC 7880 PCI + Symbios Logic 53C876</entry>
<entry>&oui; &pilote; aic7xxx &et; &pilote; ncr53c8xx</entry>
'>
<!ENTITY celsym8952 '
<entry>Symbios Logic 8952U Ultra2 Wide PCI</entry>
&celbof;
'>
<!ENTITY cel53c895 '
<entry>Symbios Logic 53C895 PCI</entry>
&celncr53;
'>
<!ENTITY cel53c895x2 '
<entry>2 Symbios Logic 53C895 PCI</entry>
&celncr53;
'>
<!ENTITY celaic-53c896x2 '
<entry>Adaptec AIC 7880 PCI + 2 Symbios Logic 53C896 PCI</entry>
<entry>&oui; &pilote; aic7xxx &et; &pilote; ncr53c8xx</entry>
'>
<!ENTITY celaic-mixte '
<entry>AMD 79C972 10/100 BT + SCSI (D6692A)<superscript><Link LinkEnd="mixte1">Rem.</link></superscript></entry>
&celpcnet;
<entry>Symbios Logic 53c875 &avec; &net; (D6692A) + Adaptec AIC 7880 PCI</entry>
<entry>&oui; &pilote; ncr53c8xx &et; &pilote; aic7xxx</entry>
'>
<!ENTITY cel53c896x2 '
<entry>2 Symbios Logic 53C896 PCI</entry>
&celncr53;
'>
<!ENTITY cel53c897x2 '
<entry>2 Symbios Logic 53C897 PCI</entry>
&celncr53;
'>
<!ENTITY celcs4614 '
<entry>Cirrus Logic CS 4614</entry>
&celbof;
'>
<!ENTITY celcs4232 '
<entry>Crystal CS 4232</entry>
&celbof;
'>
<!ENTITY celad1816 '
<entry>Analog Device 1816</entry>
<entry>&oui; &pilote; AD1816<superscript><Link LinkEnd="ad1816">Rem.</link></superscript></entry>
'>
<!ENTITY celxirc56 '
<entry>Xircom CEM56-100 56Kb 10/100 BT</entry>
<entry>&oui; &pilote; xirc2ps_cs</entry>
'>
<!ENTITY cel3c575 '
<entry>3Com 3CXFE575BT 10/100 BT</entry>
&celbof;
'>
<!ENTITY celnet '
<entry>Network Card</entry>
'>
<!ENTITY celson '
<entry>Sound Card</entry>
'>
<!ENTITY celscsi '
<entry>SCSI Card</entry>
'>
<!ENTITY celmodem '
<entry>Modem Card</entry>
'>
<!ENTITY celcombo '
<entry>Modem/Net Card</entry>
'>
<!ENTITY celfastr '
<entry>FastRaid Card</entry>
'>
<!ENTITY celnetr '
<entry>NetRaid Card</entry>
'>
<!ENTITY celtopt '
<entry>Top Tools Card</entry>
'>
<!ENTITY celfc '
<entry>Fibre Channel Card</entry>
'>
<!ENTITY celsans '
<entry>&aucune;</entry>
<entry>N/A</entry>
'>
<!ENTITY celna '
<entry>N/A</entry>
'>
<!ENTITY celbof '
<entry>???</entry>
'>
<!ENTITY celinconnu '
&celbof;
&celbof;
'>
<!ENTITY celnon '
<entry>&non;</entry>
'>
<!ENTITY celoui '
<entry>&oui;</entry>
'>
<!ENTITY RedHat '
<ulink url="http://www.redhat.com">RedHat</ulink>
'>
<!ENTITY HP '
<ulink url="http://www.hp.com">Hewlett-Packard</ulink>
'>
<!ENTITY Medasys '
<ulink url="http://www.medasys-digital-systems.fr">Medasys</ulink>
'>
<!ENTITY Samba '
<ulink url="http://www.samba.org">SaMBa</ulink>
'>
<!ENTITY Apache '
<ulink url="http://www.apache.org">Apache</ulink>
'>
]>
<book>
<?html-filename index.html>
<bookinfo>
<title>HP HOWTO</title>
<graphic fileref="images/hp" align="center"></graphic>
<subtitle>
Utilisation and Configuration Guide of HP Products under Linux
</subtitle>
<!--
<authorgroup>
<othercredit><authorblurb>
<para>
<address>
<street>Espace Technologique de St Aubin</street>
<city>Gif sur Yvette</city>
<postcode> 91193</postcode>
</address>
</para>
</authorblurb></othercredit>
</authorgroup>
-->
<pubdate>
in its latest version the
&curdate; (Version &curver;)</pubdate>
<abstract><para>
This document describes the use of products available in &HP; (HP) catalog with Linux and some free software.
It gives the state of the support for hardware, software to use, answers to some frequently asked questions and gives elements of sizing.
The goals are to offer a general view of free software functions and their use at best with HP products; as well as to make new users of HP products rapidly operational and also to allow others to choose their products knowing facts.
</para></abstract>
<!-- <graphic fileref="images/hp-howto" scale="25" align="center"></graphic> -->
<author>
<firstname>Bruno</firstname>
<surname>Cornec</surname>
<affiliation>
<orgname>Medasys Digital Systems</orgname>
<address><email>Bruno.Cornec@medasys-digital-systems.fr</email></address>
</affiliation>
</author>
<copyright>
<year>1997-2000</year>
<holder role="mailto:Bruno.Cornec@medasys-digital-systems.fr">Bruno Cornec</holder>
</copyright>
<legalnotice>
<title>License</title>
<para>
<!-- <emphasis>Legal Notice</emphasis> -->
</para>
<para>
This HOWTO is a free documentation thanks to &Medasys; and &HP; for whom I do that job; you may redistribute and/or modify it under the terms of the
<ulink url="http://pauillac.inria.fr/~lang/licence/v1/fddl.html">
Diffusion License of Free Documents
</ulink>.</para>
<para>
This document is distributed hoping it will be useful, but <emphasis>without any guaranty</emphasis>; you're completely responsible of its use, and coulnd't complain in case it doesn't work, or even if it breaks the hardware.
</para>
</legalnotice>
<revhistory>
<revision>
<revnumber> 0.8 </revnumber>
<date>
-
The 25th of July, 1999 -
</date>
<authorinitials>Bruno Cornec</authorinitials>
<revremark>
First version publically available
</revremark>
</revision>
<revision>
<revnumber> 0.85 </revnumber>
<date>
-
The 7th of September, 1999 -
</date>
<authorinitials>Bruno Cornec</authorinitials>
<revremark>
Docbook 3.1.
Monitors section.
A lot of typos corrected
Numerous links added
Makefile rewritten.
</revremark>
</revision>
<revision>
<revnumber> 0.86 </revnumber>
<date>
-
The 27th of September, 1999 -
</date>
<authorinitials>Bruno Cornec</authorinitials>
<revremark>
August and September 1999 machines.
DSSSL 1.45 + own StyleSheet.
Makefile adapted.
</revremark>
</revision>
<revision>
<revnumber> 0.87 </revnumber>
<date>
-
The 19th of January, 2000 -
</date>
<authorinitials>Bruno Cornec</authorinitials>
<revremark>
Informations on new machines Oct 1999-Jan 2000.
ENTITY for Apache, RedHat, Samba, ...
Use of an own DSSSL and DTD.
<!--
<para></para>
<para></para>
<para></para>
-->
</revremark>
</revision>
<revision>
<revnumber> 0.88 </revnumber>
<date>
-
The 15th of March, 2000 -
</date>
<authorinitials>Bruno Cornec</authorinitials>
<revremark>
Informations on new machines Feb-Mar 2000.
English translation.
</revremark>
</revision>
</revhistory>
</bookinfo>
<toc></toc>
<lot></lot>
<chapter id="introduction">
<?html-filename intro.html>
<title>Introduction</title>
<sect1>
<title>Presentation</title>
<para>
This document is a guide on the use of products proposed by the hardware manufacturer
&HP; (HP)
under Linux.
It's a quick reference guide, covering all what you need to know to size, install and configure your products under Linux, or which complementary software will be usefull for their use.
Frequently Asked Questions find answers, and references are given concerning other sources of information related to HP technologies and applications.
</para>
<para>
Opinions expressed here are those of the author, and don't commit both
&Medasys; &ou; &HP;.
Informations are provided in the aim to be useful to the readers.
However, there can't be, through this document, any warranty of any kind either from &Medasys; &ou; &HP; on these systems under Linux, as well as from myself.
Neither &Medasys;, nor &HP;, nor the author could be responsible for any problem caused by the use of these informations.
However, software editors don't garantee you a lot either (re-read the contracts).
</para>
<sect2><title>New versions of this document</title>
<para>
New versions of this document will be announced regularly on the Usenet groups
<urlsgml>news:fr.comp.os.linux.annonces</urlsgml> &et; <urlsgml>news:comp.os.linux.annonces</urlsgml>.
They will also be updated on the various anonymous ftp sites which archive such informations, mainly <urlsgml>ftp://metalab.unc.edu/pub/Linux/docs/HOWTO</urlsgml>.
</para>
<para>
Hypertext versions of this and other Linux HOWTO are available on many web sites, including <urlsgml>http://metalab.unc.edu/LDP/HOWTO</urlsgml> and <urlsgml>http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO</urlsgml>.
Most Linux distributions on CD-ROM include the HOWTO, often under the
<filename>/usr/doc</filename>,
directory, and you can also buy printed copies from several vendors.
Sometimes the HOWTO available from CD-ROM vendors, ftp sites or printed format are out of date.
If the date on this HOWTO is more than 6 months in the past, then a newer copy is probably available on the Internet.
The site of reference for this HOWTO is
<urlsgml>http://www.medasys-digital-systems.fr/linux/HP-Howto/HP-HOWTO-EN</urlsgml>
</para>
<para>
If you make a translation of this document into another language, please let me know so that I can include a reference to it here.
</para>
</sect2>
<sect2><title>Suggestions</title>
<para>
I rely on you, the reader, to make this HOWTO useful.
If you have any suggestions, corrections, or congratulations :-) don't hesitate to send them to me
<email>Bruno.Cornec@medasys-digital-systems.fr</email>,
and I will try to incorporate them in a next revision.
</para>
<para>
I am also willing to answer general questions on HP hardware and software with Linux, as best I can.
Before doing so, please read all of the information in this HOWTO, and then send me detailed information about the problem.
</para>
<para>
If you publish this document on a CD-ROM or in hardcopy form, a complimentary copy would be appreciated; mail me for my postal address. Also consider making a donation to the Linux Documentation Project to help support free documentation for Linux. Contact the Linux HOWTO coordinator,
Guylhem AZNAR <email>guylhem@rrremovethis.oeil.qc.ca</email>.
</para>
</sect2>
</sect1>
<sect1 id=remerciements>
<?html-filename thanks.html>
<title>Aknowledgements</title>
<para>
Most of the informations provided here come from research made in HP documentations, files provided with Linux kernel sources, the FAQ of the
Usenet newsgroup <urlsgml>news:comp.sys.hp.hpux</urlsgml> with a <ulink url="http://hpux.cict.fr">HTML version</ulink>
available on all mirror sites like the CICT, our experience as an HP VAR, a lot of tests and deployments realised, and remarks from Linux users.
</para>
<para>
Numerous people have contributed to this document and augmented its contents. You'll find the most complete possible list in the
<xref linkend="contributeurs">.
I would like to thank just now, without any particular order, those without whom this document would simply not exist :
</para>
<ItemizedList Mark="bullet" Spacing="Compact">
<ListItem><para>
Marc Hia Bali<6C> <email>Marc_Hia-Balie@hp.com</email>,
who ordered that document and accepted to make it a free documentation.
</para></ListItem>
<listitem>
<para>
<ulink url="http://www.cs.helsinki.fi/~torvalds/">Linus Torvalds</ulink>,
for the Linux project (without it, nothing would exist).
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.gnu.org/people/rms.html">Richard Stallman</ulink>,
for the GNU project (without it, nothing would exist either).
</para>
</listitem>
<listitem>
<para>
Nat Makar<61>vitch <email>nat@nataa.frmug.org</email>,
For his work as translator and his advocacy conferences.
</para>
</listitem>
<listitem>
<para>
Xavier Cazin <email>xc@itp.fr</email>,
for his talent to convince me to use DocBook.
</para>
</listitem>
<listitem>
<para>
Eric Dumas <email>dumas@Linux.EU.Org</email>,
for the management of the french LDP.
</para>
</listitem>
<listitem>
<para>
R<EFBFBD>my Card <email>Remy.Card@linux.org</email>,
for ext2 and his love of electricity :-)
</para>
</listitem>
<listitem>
<para>
Ren<EFBFBD> Cougnenc,
to have helped a lot of people to begin with Linux, including myself.
</para>
</listitem>
<listitem>
<para>
Dany Coffineau <email>Dany.Coffineau@alcatel.fr</email>,
for teachnig me Unix.
</para>
</listitem>
<listitem>
<para>
Fran<EFBFBD>ois Strobel <email>Francois.Strobel@alcatel.fr</email>,
for his peacefulness and legendary patience :-)
</para>
</listitem>
<ListItem><para>
Fr<EFBFBD>d<EFBFBD>ric Dubuy <email>Frederic.Dubuy@medasys-digital-systems.fr</email>,
who contributed to the writing of that document and took all the work I coulnd't achieve, while I was writing it. Without saying he's also the graphist of the logo !
</para></ListItem>
<listitem>
<para>
Alain Pascal <email>pascal@montrouge.omnes.slb.com</email>,
for the several tests made.
</para>
</listitem>
<ListItem><para>
Pascal Lemonnier <email>Pascal.Lemonnier@medasys-digital-systems.fr</email>
typography expert who found a lot of typos.
</para></ListItem>
<ListItem><para>
Ralf S. Engelschall <email>rse@engelschall.com</email>,
who realised the
<ulink url="http://www.engelschall.com/sw/wml">wml</ulink>
tool set, used to manage the languages of this document.
</para></ListItem>
<ListItem><para>
Cees de Groot <email>cg@sgmltools.org</email>,
who realised the
<ulink url="http://www.sgmltools.org">SGMLTools</ulink>
tools set, which allow to generate all the versions of this document from a single SGML source.
</para></ListItem>
<ListItem><para>
Norman Walsh <email>ndw@nwalsh.com</email>,
who realised the SGML DTD
<ulink url="http://www.docbook.org">DocBook</ulink>.
</para></ListItem>
<ListItem><para>
James Clark <email>jjc@jclark.com</email>,
who realised the tool
<ulink url="http://www.jclark.com/jade/">Jade</ulink>.
</para></ListItem>
<listitem>
<para>
Cornec family<email>cornec@victoria.frmug.org</email>,
for his patience and his support.
</para>
</listitem>
</ItemizedList>
</sect1>
</chapter>
<chapter id="Presentation">
<?html-filename presentation.html>
<title>
Presentation of Linux and Free Software
</title>
<sect1><title>
Some definitions
</title>
<para>
Before going into more details in the presentation, it could be useful to give some definitions of terms and software mentionned in that HOWTO.
</para>
<sect2><title>
Free Software or Open Source software
</title>
<para>
A <firstterm>free software (or Open Source software)</firstterm>
is a software distributed with its source code, allowing its study, its transmission, its adaptation. The problem, in english, is the use of free, which has both meanings of "at no cost" and "without constraint". Here, it's the second use which has to be considered, hence the use of Open Source. To remember, think of free as speech, not beer.
</para>
<para>
Depending on the licenses used for its development, the constraints for users of such a software are various.
The most open licenses (like the BSD one) allow code appropriation by third parties, including the resell of the resulting software (with or without modification) in commercial products, without any problem, and without owing something else to the originators than the mention of their copyright.
Other licenses (like the GNU Public License or GPL) force every modified GPL software to be free GPL software itself ; this doesn't allow the use of such programs in a commercial one.
Many other licenses exist, more or less open: the Artistic License (perl), the NPL one (mozilla), the QPL one (Qt) ...
</para>
<para>
A vast majority of free software is today under the GPL license, even if the BSD world takes always a great place, however less visible, mainly in the press.
</para>
<variablelist>
<varlistentry><term><ulink url="http://www.gnu.org">GNU project Web site</ulink></term>
<listitem>
<para>
You find there all of the informations on the GNU project, including the licenses produced (GPL and LGPL) and various discussions on free software.
</para>
</listitem>
</varlistentry>
<varlistentry><term><ulink url="http://www.opensource.org">Open Source project Web site</ulink></term>
<listitem>
<para>
This site proposes a new definition, a bit less restrictive, of free software - called here OpenSource Software - by well-known people.
</para>
</listitem>
</varlistentry>
</variablelist>
<variablelist>
<varlistentry><term><ulink url="http://www.freebsd.org/">FreeBSD project Web site</ulink></term>
<listitem>
<para>
Here are explained the advantages of the very open BSD license.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2><title>
Examples and counter-examples
</title>
<para>
First of all, free software and <firstterm>freeware</firstterm> shouldn't be mixed up. A freeware is not necessarily a software provided with its sources, on the contrary of a free software.
On the other side, on the contrary of a freeware, you may be charged to obtain a free software (it's not in contradiction with the licensed used).
The ambiguity, as stated before, comes from the word
<quote>free</quote>
.
A freeware is then free of charge, but not necessarily "free of sources".
(As well, the <firstterm>shareware</firstterm> has nothing to do with free software).
</para>
<para>
So examples of important and well-known free software are the Linux and FreeBSD operating systems, the &Apache; Web server, the &Samba; SMB server, GNU C and C++ compilers ...
A contrario, examples of well-known freeware are the Internet Explorer browser, the Eudora Light mail reader, ...
</para>
</sect2>
<sect2><title>
Linux
</title>
<para>
Linux
is a free operating system, superset of the POSIX norm.
<quote>Linux</quote>
points out the kernel alone.
By extension, the name is also given to distributions based on that kernel plus a set of tools from the GNU project.
</para>
<para>
Linux is by consequence a Unix system, except that it doesn't use any proprietary code and is furnished under the GPL license, implying the availability of the sources.
As every Unix system, it is multi-tasks, multi-users.
It's also extremely portable, and it is available officialy today on processors such as
Intel (i386 to Pentium III), Alpha, Motorola (680x0 &et; PowerPC), Sparc, StrongArm, Mips.
Without mention of the ports, operational or in process on
PalmPilot, Itanium (ex-Merced), PA-Risc, Crusoe ...
</para>
<para>
The system is today perfectly stable and mature.
Versions "x.y.z" of the Linux kernel, where "y" is an even number, are stable and only bug corrections are generaly applied when "z" augments.
Versions "x.y.z" of the Linux kernel, where "y" is an odd number, are development versions which may be instable and are reserved to developers or intrepids.
</para>
<para>
From time to time, when the kernel development stabilizes a "freeze" is announced to furnish a new "stable" version (even), and the development goes on on a new version (odd).
</para>
<para>
The current stable version is the version &curker; (this last number may evolve following the rythm of corrections).
Development has on the other side begun again with a 2.3 version currently in code freeze.
</para>
<para>
Numerous presentations of Linux are currently available. Among them, you should consult the one made by Michael Johnson at
<urlsgml>http://www.medasys-digital-systems.fr/mirror/linux/HOWTO/INFO-SHEET.html</urlsgml>.
</para>
<sect3><title>
Linux technical characteristics
</title>
<para>
The system offers the following technical characteristics :
</para>
<itemizedlist mark="bullet">
<listitem>
<para>
Multi-tasking : executes several programs in pseudo-parallel.
</para>
</listitem>
<listitem>
<para>
Multi-users : many users acting on the same machine at the same time (without worrying on licenses).
</para>
</listitem>
<listitem>
<para>
Portable and interoperable : works on several hardware architectures.
All the sources are available.
Linux supports a lot of file systems, outside the native ext2 :
Syst<EFBFBD>me V, BSD, Sun, MS-DOS, VFAT, NTFS, Mac, HPFS, EFS, ISO9660.
On the network side, it supports the following protocols
TCP/IP v4 &et; v6, Appletalk, Netware (client &et; server), Lan Manager SMB (client &et; server), X-Window, NFS, PPP, SLIP, UUCP.
</para>
</listitem>
<listitem>
<para>
Performant architecture : modular kernel, built at will, execution in protect mode on 80x86 processors, page load on demand, page share between executables when reading, virtual memory with swap on disk, use of a dynamical disk cache in memory, dynamic libraries, process management, pseudo terminals, virtual consoles.
</para>
</listitem>
<listitem>
<para>
Security : protection of memory between processus: one user program can't compromise the whole system operation.
</para>
</listitem>
<listitem>
<para>
Respect of norms and standards : Posix, with System V and BSD extensions.
Support of COFF and ELF binaries.
Binary compatibility with SCO, SVR3/4 through the iBCS2 module.
Native Language Support as well as national keyboards, fonts...
</para>
</listitem>
</itemizedlist>
</sect3>
</sect2>
</sect1>
<sect1>
<?html-filename concepts.html>
<title>
Free software concepts
</title>
<para>
Once the definitions are given, it is important to stay on at ideas promoted by the free software movement.
It's important as well to clear some wrong ideas hawked on these software.
This section gives then a various set of elements in favour of the introduction of free software and ends on the real problems remaining to solve.
</para>
<sect2><title>
Free software philosophy
</title>
<para>
In fact, the philosophy promoted by the free software movement is not that different from the one proposed by the scientific movement till a long time already: to put in common ideas and collective knowledge to allow the progression of the research and the growth of this knowledge.
The knowledge of the human genome is one of the examples of such a collaborative work.
</para>
<para>
The computer engineering environement, and especially the software one, seems to have turn away till the last 20 years from these base concepts of the scientific world.
It prefers on the contrary to keep the customer captive instead of giving him the informations needed to exploit his computing environement the best he can.
That's indeed following such a problem at the begining of the 80's that Richard Stallman, who was doing researches in artificial intelligence at the MIT, decided to create the GNU project.
This project is the foundation of the current free software movement.
</para>
<para>
The main ideas promoted by this movement and stated by Richard Stallman himself are :
</para>
<itemizedlist mark="bullet">
<listitem>
<para>
Liberty: every user should be free to copy, diffuse, modify a program, either to share it with others, or to adapt it to his own needs.
As well, he should be able to analyse it to understand, imitate, improve, verify its operations, as well as every scientific result is published and seen by the peers for verification, study, understanding and realisation of derived works.
Could you imagine a vaccine against the liver cancer that another laboratory couldn't derive to make a vaccine against the pancres cancer.
</para>
</listitem>
<listitem>
<para>
Equality: every person should have the same rights on the software.
Thus the provider isn't priviledged and can't keep customers to whom he furnished his work captive.
Could you think that only the producer of our vaccine could use it ?
</para>
</listitem>
<listitem>
<para>
Fraternity: this mode of working encourages the whole computer engineering community to cooperate and thus to produce software more and more reliable and useful to all.
Could you imagine that a discovery like the vaccine above couldn't help everyone and favour other discoveries.
</para>
</listitem>
</itemizedlist>
<para>
More over the utopy of these ideas, we can find other reasons which allowed free software to spread so widely today.
They are detailed in
<xref linkend="choix">.
</para>
<para>
The free software movement materializes itself also through a community of people.
That community, informal meeting of personnalities, is heterogeneous in its contents, actions, ideas, even if all share the same belief in the freedom of the software.
That community created for itself the tools needed to its communication : Internet and Usenet.
And these communication tools are based of course on a lot of free software to work.
Among the outstanding persons of this movement, we can present :
</para>
<itemizedlist mark="bullet">
<listitem>
<para>
<ulink url="http://www.cs.helsinki.fi/~torvalds/">Linus Torvalds</ulink>,
conceptor of Linux.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.gnu.org/people/rms.html">Richard Stallman</ulink>,
GNU project conceptor.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.tuxedo.org/~esr">Eric S. Raymond</ulink>,
writer of several and excellent articles, which inspired so many vocations.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://kiev.wall.org/~larry">Larry Wall</ulink>,
author of Perl and of the patch tool, and philosopher.
</para>
</listitem>
<listitem>
<para>
Tim O'Reilly <email>ask_tim@oreilly.com</email>,
free software advocate and editor of several books dedicated to them.
</para>
</listitem>
</itemizedlist>
<para>
All these personalities are, above all, excellent computer engineers, which allows them to be recognized as major actors of the free software movement.
Their human and communication qualities are also strong characteristics of their nature.
In any case they aren't considered for their power, but for their knowledge.
</para>
<para>
Of course, the free software community is built of thousands of programmers, whose complete list would be too tedious.
All share the will of producing useful work, free, and to be recognized for their technical qualities above all.
</para>
</sect2>
<sect2 id="choix"><title>
The choice of free software
</title>
<para>
To use free software to bring solutions in a computing environment is a choice.
First, it is in favour of a plurality of solutions, mainly in the personal computer world which tends to be monopolistic.
Then, the choice is made, and that's what is finally important, on the own qualities of free software, which are detailed just below.
</para>
<variablelist>
<varlistentry><term>Source code access</term>
<listitem><para>
This point is the most important of the choice, because it allows the undestanding, adaptation, correction, distribution, improvement of the software.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Reliability</term>
<listitem>
<para>
That quality is derived from the previous one: the free software is the combined result of the experience and the intelligence of all the participants.
Its reliability increases then as time passes, with all the corrections which are made.
More over, no marketing pression obliges the software's producer to deliver it to its customers before it is in a satisfactory state.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Portability</term>
<listitem>
<para>
This quality is not intrinsic to free software, but is very often seen in a free software.
Indeed if a softawre meets success, it will necessarily be adapted to other environments than those initialy considered.
Thus by increasing its disponibility, its portability and reliability are also increased.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Universality</term>
<listitem>
<para>
One essential quality of free software is the character naturaly universal of the data format used.
Even if they don't follow standards, the availibility of the source code assures the user that he will understand them, and more over be able to write any filter needed to the reuse of data or their exchange with other software.
This allows also users to stabilize their environment, because they are not obliged to migrate in case of incompatibility of data formats in their applications.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Performance</term>
<listitem>
<para>
Resulting from a lot of examinations, the use of algorithms coming from advanced research works, as well as tested by various usages, free software have good performances by nature.
Frequently large portions of code are rewritten to allow the reuse of the original ideas with a better code and thus to increase performance.
Several tests made by various organisms tend to prove it also
(<ulink url="http://www5.zdnet.com/products/content/pcmg/1709/305867.html">&Apache; Web Server and competitors</ulink>, <ulink url="http://www.zdnet.com/sr/stories/news/0,4538,2196106,00.html">SMB &Samba; server vs Windows NT</ulink> ...).
Once more, there is no obligation to diffuse an application whose performances would be bad.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Interoperability</term>
<listitem>
<para>
Historically, Unix environment was always a ferment for interoperability with other systems (big or medium size systems, as well as personal computers).
The support in Linux, for example, of a lot of network protocols, filesystem formats, and even binary compatibility modes assures a good interoperability.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Reactivity</term>
<listitem>
<para>
When considering the more and more longer development cycles of the software editors, the reactivity brought by the free software movement is interesting for a lot of sites, concerned by the rapid obtention of corrections to a given problem.
Thus, during the recent discoveries of IP problems (ping of the death,...), patches were always available within the next 3 days.
And above that, only the patch correcting the hole found was delivered. There were no functionality added, which could have create other instabilities.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
Independantly of its qualities, it's possible to give other reasons of various nature, in favor of free software, depending on the type of the person met.
</para>
<sect3><title>
Marketing argumentation
</title>
<para>
Studies from IDC bring to light the irresistible rise of Linux as a server operating system.
In 1998, Linux is credited with 17% of market share, with an increase of 212%, which is the most important in that domain.
The following graphics give the whole market share repartition.
</para>
<para>
<figure id="idc1998">
<title>
Server operating system repartition in 1998 (IDC).
</title>
<graphic fileref="images/idc1998" align="center" scale="75" width="20cm"></graphic>
</figure>
</para>
<para>
This was confirmed in 1999 with a market share climbing to 24% and an ancrease of 93%, always more than four times the increase of the follower.
<figure id="idc1999">
<title>
Server operating system repartition in 1999 (IDC).
</title>
<graphic fileref="images/idc1999" align="center" scale="75" width="20cm"></graphic>
</figure>
</para>
<para>
Dataquest <ulink url="http://gartner6.gartnerweb.com/dq/static/about/press/pr-b9939.html">estimates</ulink>
on its side that Linux servers will represent, with 1.1 million of units, 14% of the servers sold in 2003.
</para>
<para>
the Net itself produces marketing tools to demonstrate the superiority of free software.
Two counters are regularly updated by
<ulink url="http://www.netcraft.com/survey/">Netcraft</ulink>,
on web server software, and by
<ulink url="http://www.leb.net/hzo/ioscount/index.html">IOS Counter</ulink>
for the servers on Internet.
Results, reproduced below, show the importance taken by &Apache; with more than 6 millions of operational sites, crushing the competition, as well as the free operating systems Linux and *BSD which dominate the world of Internet servers.
<figure id="netcraft">
<title>
Web server software by Netcraft between 1995 and 2000.
</title>
<graphic fileref="images/netcraft" scale="70"></graphic>
</figure>
<figure id="ioscounter">
<title>
Repartition of Internet servers by IOS Counter in April 1999.
</title>
<graphic fileref="images/ioscounter" align="center" scale="50"></graphic>
</figure>
</para>
</sect3>
<sect3><title>
Financial argumentation
</title>
<para>
Financial arguments also speaks for free software.
And first the price to aquire them is low.
Low, because it's never zero.
Even if you can find it on Internet, you have to consider the costs related to that link.
However costs are greatly less expensive than for commercial software.
So a RedHat 6.1 Linux distribution, delivered with more than 1200 software packages, costs about 60 USD when you have to pay more than 800 USD to obtain Windows NT server, delivered only with IIS.
</para>
<para>
On the other side, free software don't have the notion of license by user or by supplmentary service. Thus there is no additional cost when you have to increase the use of these software in your entity.
That's of course not the case with commercial software whose economical logic is often based on the number of licenses.
</para>
<para>
Free software bring in addition a better mastering of the TCO (Total Cost of Ownership), mentionned so frequently in the massive deployment of personal computers.
Thus administration costs are reduced because systems like Linux or FreeBSD, as Unix, are managed completely remotely, either through command line orders (with <command>telnet</command>) or in graphical mode by using X-Window.
More over, we benefit from a true multi-users mode, improving these management operations.
Always in this domain, it's also possible to do remote management, either through the own hardware capacities (as the Remote Assistant card integrated in most HP NetServers), or by doing a remote connexion (through modem, ISDN adapter or a permanent link) thanks to the native protocol PPP and secure connexion systems as tunneling or ssh.
This managemnt could even be realised by an external entity, in outsourcing.
</para>
<para>
At last, the costs due to the hardware themselves could be controled; on one side, if by chance free software don't meet the needs, it's always possible to buy then commercial software solutions to cover the rest.
On the other side, solutions based on free software have good performances by nature, and can use hardware platforms which would be considered as obsolete, if installed following the standard criterias of other operating systems or applications.
It's so possible to use "old" hardware, mainly to model. It's then possible to invest, with a fine knowledge, when puting the solution in operation, if needed.
The power increase may naturaly take place progressively.
</para>
</sect3>
<sect3><title>
Technical argumentation
</title>
<para>
This argumentation was already given in the previous sections.
I think nevertheless that some notions may be explained with complementary informations.
</para>
<para>
So concerning the reliability aspects of free software based solutions, it's important to note that it implies an operational running time very high (standard characteristic of Unix systems in general).
This is mesured by the command
<command>uptime</command>.
One of Medasys and HP customers, Saint Michel Hospital, has a Vectra VL5 acting as router under Linux since more than 300 days.
And that's not a isolated case.
</para>
<para>
Respect of standards and norms, as well as the extreme portability of free software assures also to applications developed on these platforms the same qualities.
And notably, if after their use, the performances or services brought by free software based architectures were insufficient, it would be easy to migrate to machines offering more performances and capacities of evolution, as the HP 9000 systems, running HP-UX.
</para>
<para>
At last a development plan centered around performances implies a modularity, such as it's possible to resize the system kernel nearest to the capacities of the hardware or to use dynamically loaded modules following the needs.
A packages installation may vary from 40 GB for a minimal system up to many GB for a complete distribution.
The system linearity allow also the support of multi-processors machines (SMP) (tested up to 32 processors on a Sparc machine).
The system modularity allows also to obtain an operational system on a 1.44 MB floppy disk, either to realize a minimal repair environment, or to provide a perfectly operational router.
The world of embedded systems shows besides more and more interest for systems such as Linux, because above it's modularity, source availability makes communication with dedicated peripherals easier (acquisition cards, sonde, ...) and entities as Cern or Thomson already use such solutions.
</para>
</sect3>
<sect3><title>
Solutions argumentation
</title>
<para>
That argumentation is probably the most important of all, because it's useless to have free software if it's not to make something useful with it or to offer solutions to demands of entities willing to use it.
In which sectors free softawre may bring solutions today ? Well, you have to admit it's in nearly all the sectors of enterprise computing.
</para>
<para>
Historically, Open Source Software were used to realise Internet/Intranet servers, because their growth was following the one of the Net.
It's so possible to cover all aspects linked to the Internet, from the
Web server (&Apache;), FTP server (<ulink url="http://www.landfield.com/wu-ftpd">Wu-Ftpd</ulink>), DNS server (<ulink url="http://www.isc.org/bind.html">Bind</ulink>), the E-Mail server (<ulink url="http://www.sendmail.org">Sendmail</ulink> &ou; <ulink url="http://www.postfix.org">Postfix</ulink>), the Usenet groups server(<ulink url="http://www.isc.org/inn.html">INN</ulink>), the proxy server (<ulink url="http://juanjox.linuxhq.com/">IPmasqadm</ulink>), the firewall (<ulink url="http://www.rustcorp.com/linux/ipchains/">IP-Chains</ulink>), Virtual Private Network (<ulink url="http://www.openssh.com/">OpenSSH</ulink>, Linux kernel), the Cache server for the Web (<ulink url="http://squid.nlanr.net/Squid/">Squid</ulink>) or also the Time server (<ulink url="http://www.eecis.udel.edu/~ntp">NTP</ulink>) ...
All these software are available in standard in a Linux distribution.
The client computer should be equiped with the software corresponding to the application used (mail reader, news reader, web browser, ...) whatever its operating system.
The choice of the client is free, as all these tools respect the standards decreed in the
<ulink url="ftp://ftp.medasys-digital-systems.fr/pub/doc/IETF/rfc">RFCs</ulink>.
</para>
<para>
The second preferential domain for free software is the file and print server domain.
For these services, clients may be multiple: Unix type (use of
<ulink url="ftp://ftp.mathematik.th-darmstadt.de/pub/linux/okir">NFS</ulink> &et; <ulink url="ftp://ftp.kernel.org/pub/linux/devel/gcc/">KNFS</ulink> &ou; also <ulink url="http://www.coda.cs.cmu.edu">Coda</ulink>,
for file sharing and of
<command>lpd</command>
for print service), Microsoft Windows type (use of
&Samba;,
which allows also the use of local client printers) or MacIntosh type (use of
<ulink url="http://www.umich.edu/~rsug/netatalk">NetAtalk</ulink>).
All these software are provided in standard in a Linux distribution and don't need any modification at the client level to work.
</para>
<para>
The other domains where a system such as Linux may bring solutions is the computation one, with support of
<ulink url="http://www.irisa.fr/prive/mentre/smp-faq/">multi-processors</ulink>,
linked to the realisation of
<ulink url="http://hp-linux.cern.ch/">clusters with multiple nodes</ulink>
with high-speed network interfaces
(100 Mbit/s, <ulink url="http://cesdis.gsfc.nasa.gov/linux/drivers/index.html#gigabit">Gigabit</ulink> &ou; <ulink url="http://lhpca.univ-lyon1.fr/myri.html">Myrinet</ulink>),
those of data security with the support of
HP NetRaid<superscript><Link LinkEnd="netraid">Rem.</link></superscript>
cards, allowing Raid level of 0, 1, 3, 5, 10, 50, and HotSpare disks, managed by the harware, those of centralized fax server, with a free software like
<ulink url="http://www.hylafax.org">HylaFAX</ulink>
or also as an archive/backup server with HP SureStore DAT or DLT libraries thanks to a commercial software like
<ulink url="http://www.arkeia.com">Arkeia</ulink>
or at last as a database server with free solutions like
<ulink url="http://www.postgreSQL.org/">PostgreSQL</ulink>,<ulink url="http://www.mysql.org/">MySQL</ulink> &ou; commercial like <ulink url="http://platforms.oracle.com/linux/index_lin.htm">Oracle</ulink>,
to speak only of these three.
</para>
<para>
On the client side, even if it's less highlighted for the moment, possibilities to use solutions based on free or commercial software are numerous.
There also the Internet part is the main one, with tools like graphical web browsers
(<ulink url="ftp://ftp.netscape.com/pub/communicator/">Netscape)</ulink> &ou; textual (<ulink url="http://www.cc.ukans.edu/about_lynx/about_lynx.html">lynx</ulink>),
a lot of graphical mail readers
(<ulink url="http://www.geocities.com/SiliconValley/6702/kmail.html">Kmail</ulink>, <ulink url="http://burka.netvision.net.il/xfmail/xfmail.html">XFMail</ulink>, ...) &ou; textual (<ulink url="http://www.mutt.org/">mutt</ulink>, <ulink url="ftp://ftp.uu.net/networking/mail/elm">elm</ulink>, ...).
But you also have the whole panel of indispensable tools for a personal computer today as a PDF reader
(<ulink url="http://www.adobe.com/supportservice/custsupport/LIBRARY/acrunix.htm">Acrobat Reader</ulink> &ou; <ulink url="http://www.foolabs.com/xpdf/">xpdf</ulink>),
image manipulation tools
(<ulink url="http://www.wizards.dupont.com/cristy/ImageMagick.html">ImageMagick</ulink>, <ulink url="http://www.gimp.org/">the Gimp</ulink>, <ulink url="http://www.real.com/products/player/downloadrealplayer.html?wp=dl0899&amp;src=dlbutton_all&lang=en#form">RealPlayer tools</ulink> ...),
word processors
(<ulink url="http://www.lyx.org">LyX</ulink>, <ulink url="http://www.latex-project.org">LaTeX</ulink>, <ulink url="http://www.sgmltools.org">SGMLTools</ulink>, <ulink url="http://linux.corel.com/linuxproducts_wp8.htm">Wordperfect</ulink>, ...),
commercial office suites
(<ulink url="http://www.applix.com/applixware/linux/main.cfm">ApplixWare</ulink>, <ulink url="http://www.stardivision.com/office/so5linux_body.html">StarOffice</ulink>),
sound management tools
(<ulink url="ftp://ftp.medasys-digital-systems.fr/pub/linux/sunsite/apps/sound/players/wavtools-1.3.2.tar.gz">WavTools</ulink>, <ulink url="http://www.ueda.info.waseda.ac.jp/%7Esatoshi/midi/midi-e.html">eplaymidi</ulink>, <ulink url="http://metalab.unc.edu/tkan/xmcd">xmcd</ulink>, ...),
CD burning tools
(<ulink url="http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html">cdrecord</ulink>, <ulink url="http://sunsite.auc.dk/BurnIT/">BurnIT</ulink>, ... with complements as <ulink url="http://www.ge.ucl.ac.uk/~jcpearso/mkisofs.html">mkisofs</ulink>, <ulink url="http://www.xiph.org/paranoia/">cdparanoia</ulink>),
free and commercial emulators for various systems
(<ulink url="http://www.winehq.com/">Wine</ulink>, <ulink url="http://www.ardi.com/">Executor</ulink>, <ulink url="http://www.calderasystems.com/doc/wabi/wabi.html">WABI</ulink>, <ulink url="http://www.dosemu.org">DOSEmu</ulink>, ...),
compilers and interpretors for all the languages
(<ulink url="http://www.gnu.org/software/gcc/gcc.html">C</ulink>, <ulink url="http://www.gnu.org/software/gcc/gcc.html">C++</ulink>, <ulink url="http://agnes.dida.physik.uni-essen.de/~gnu-pascal/">Pascal</ulink>, <ulink url="http://www.gnu.org/software/fortran/fortran.html">Fortran</ulink>, <ulink url="ftp://ftp.medasys-digital-systems.fr/pub/linux/sunsite/devel/lang/basic/qb2c-3.2k.tar.gz">Basic</ulink>, <ulink url="http://www.scriptics.com/products/tcltk/">Tcl/Tk</ulink>, <ulink url="http://www.perl.com/">Perl</ulink>, <ulink url="http://www.python.org/">Python</ulink>, <ulink url="http://www.adahome.com/Resources/Compilers/GNAT.html">Ada</ulink>, <ulink url="http://www.loria.fr/projets/SmallEiffel/">Eiffel</ulink>, <ulink url="http://clisp.cons.org/~haible/clisp.html">Lisp</ulink>, <ulink url="http://www.scheme.org/">Scheme</ulink>, <ulink url="http://www.gnu.org/software/prolog/prolog.html">Prolog</ulink>...),
including commercial versions (<ulink url="http://www.pgroup.com/prod_description.html">
PGI</ulink>, ...),
graphical environments
(<ulink url="http://www.gnome.org">Gnome</ulink>, <ulink url="http://www.kde.org">KDE</ulink>, <ulink url="http://www.opengroup.org/desktop/">Motif</ulink>, ...).
The evolution of these last tools indicates that the 2000's may be the years where Linux and free software will break through at their turn on the client.
</para>
<para>
I want to mention that this document was realized on an HP Brio BAx equiped only with a Linux distribution, with the help of tools like
<ulink url="http://www.sgmltools.org/">SGMLTools</ulink>, <ulink url="http://www.jclark.com/jade">Jade</ulink> &et; <ulink url="http://www.oasis-open.org/docbook/">DocBook</ulink>,
which allowed to generate from a single source the formats
HTML, Txt, RTF, PostScript, &et; PDF.
</para>
</sect3>
<sect3 id="service"><title>
Service argumentation
</title>
<para>
This one was for a long time a blocking point to the expansion of free software in the firms.
It's not the case today.
Many service providers or hardware manufacturers, like HP, control today these solutions and propose support around them.
</para>
<para id="newsgroups">
Other sources of informations are also available, in abundance, through several web sites dedicated to these solutions, specialised mailing-lists, and various Usenet groups, such as for Linux, the international groups under
<command>comp.os.linux.*</command>
or for the french speaking people under
<command>fr.comp.os.linux.*</command>.
</para>
<para>
Concerning competences, more and more young engineers or academics finish their learning cycle being trained to the use of free applications and operating systems.
This wealth of competences arrives now on the labour market and will contribute to increase the movement of generalisation of these tools.
At last, many firms have internaly ignored competences. In fact, their employees often install this software at home, and have a good mastering, usable when arrives the deployment of the software in their professional structure.
</para>
</sect3>
</sect2>
<sect2><title>
Wrong ideas on free software
</title>
<para>
Advocating free software consists also to mention some generally accepted ideas concerning them and to fight them.
</para>
<variablelist>
<varlistentry><term><emphasis>"There is no support, no training"</emphasis></term>
<listitem>
<para>
As seen previously, support is currently structuring itself.
A firm like &RedHat; provides today support for their solutions.
Only in France, we may mention firms like
&Medasys;, <ulink url="http://www.atrid.fr">Atrid</ulink>, <ulink url="http://www.alcove.fr">Alcove</ulink>
which assure support on free software.
Likewise, always in France, training on free software may be given by
<ulink url="http://www.france.hp.com/formation">HP France</ulink>, <ulink url="http://www.learningtree.com/fr/index.htm">Learning Tree</ulink>, the <ulink url="http://form-continue.iut-velizy.uvsq.fr/">IUT de V<>lizy</ulink>,
without mentioning generic network and Unix trainings (besides proposed also by the same organizations) which represent a fundamental base in a training course.
</para>
</listitem>
</varlistentry>
<varlistentry><term><emphasis>"There is no documentation"</emphasis></term>
<listitem>
<para>
There is a whole set of manuals, the <ulink url="http://www.linuxdoc.org">Linux Documentation Project</ulink> made of FAQ (Frequently Asked Questions) and HOWTO, counting more than 300 documents around Linux, the main being
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/french/ldp">translated in french</ulink>,
available as free documentation.
This documentation has a various quality, more or less up to date, following the subjects, certainly but it makes a corpus allowing to apprehend alone a Linux distribution and all its components.
For myself, I always found in it everything I needed to do my job with free software.
And, in case of complementary informations, a lot of web sites and Usenet groups may again bring some of the elements needed.
And without counting the innumerable manual pages available on line.
</para>
<para>
On the other side, the editors
<ulink url="http://www.editions-oreilly.fr">O'Reilly</ulink> &et; <ulink url="http://www.ssc.com">SSC</ulink>
have specialised in providing books around free software, written generaly by the writers of the software themselves.
Their books are considered as reference books in their respective domains.
</para>
</listitem>
</varlistentry>
<varlistentry><term><emphasis>"A free or nearly free product is a toy"</emphasis></term>
<listitem>
<para>
You should always make a difference between free (as speech) and free (as beer).
Too many freeware in Microsoft environment are in fact toys and of poor quality.
It's absolutely not the case for free software, as stated in the previous sections.
Remember just that they are reliable by construction.
</para>
</listitem>
</varlistentry>
<varlistentry><term><emphasis>"Linux is difficult to install"</emphasis></term>
<listitem>
<para>
Linux is a professional operating system.
At that title, it requires competences to install it, as well as any other professional operating system, like the other Unix or Windows NT for example.
But it isn't more difficult to install than those either, mainly thanks to distributions as
RedHat 6.1, Mandrake 7.0, ...
You need about 30 minutes to realize a complete installation of such distributions, so quite the same as for HP-UX and noticeably less than for Windows NT Server.
</para>
<para>
On the other hand, as before installing a server with Windows NT you have to verify its compatibilit<69> with the
<ulink url="http://www.microsoft.com/HCL">Hardware Compatibility List</ulink>
of Microsoft, for Linux it's also greatly recommended to verify the
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Hardware-HOWTO.html">Hardware HOWTO, </ulink>
and for HP machines to refer to this
<ulink url="http://www.medasys-digital-systems.fr/linux/HP-Howto/HP-HOWTO-EN/hp-hardware.html">page</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry><term><emphasis>"Free Software are not adequate for heavy tasks"</emphasis></term>
<listitem>
<para>
This is less and less true and this criticism will be obsolete with the next versions of the Linux kernel which will include a journalised filesystem, allowing a true application cluster.
But already Linux authorises the use of multi-processors, several nodes to realise computation clusters.
And don't forget it's used by the portal
<ulink url="http://www.voila.fr">Voila</ulink> (France Telecom) or the engine <ulink url="http://www.deja.com">Deja</ulink>
among other prestigious references.
As well, FreeBSD is used with success as the world biggest ftp server :
<ulink url="ftp://ftp.cdrom.com">Walnut Creek CDROM server</ulink>
</para>
</listitem>
</varlistentry>
<varlistentry><term><emphasis>"What appeal do I have in case of problem with the editors ?"</emphasis></term>
<listitem>
<para>
There is no appeal, because software licences deny all responsabilities for the writers, in case of problem.
But, in reality developers are always ready to help in case of problem and try to correct as soon as possible the bugs encountered (for the F00F bug of the pentium, a patch for the Linux kernel was published within 3 days, for example).
On the other side, commercial editors guarantee very badly users against problems other than packaging errors. please read the notes furnished with your software to judge.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2><title>
Real problems around free software
</title>
<para>
It would not be honest to negate certain remaining problems linked to free software.
Some have begun to disappear, other are inherent to the system, other at last will take time to diappear.
</para>
<para>
The first problem, inherent to the model of free software, is the multiplicity of tools and distributions available.
So, if you want to setup a mail server, you have to choose between
Sendmail, Exim, PostFix, Qmail, Smail.
As well if you want to install Linux, you may choose between the distributions
&RedHat;, <ulink url="http://www.suse.de">SuSE</ulink>, <ulink url="http://www.slackware.com">Slackware</ulink>, <ulink url="http://www.linux-mandrake.com/">enMandrake</ulink>, <ulink url="http://www.turbolinux.com">Turbo Linux</ulink>, <ulink url="http://www.debian.org">Debian</ulink>.
This represents often a problem for the newcomer, but the esperienced user will always prefer to have a large choice he will confront to his particularities and to his experience.
As long as an actor respects the rules by freeing his code (it's the case of the rpm and deb formats for example), there is little risk from the comunity point of view.
</para>
<para>
The second problem, inherent also to the free software birth, is the necessity to have strong Unix and Internet competences, to manage such solutions.
The power available through these systems is proportional to the competence of their administrators.
And that will stay true even with the growth of more and more grahical solutions to manage them.
On the other side, you capitalize the investment in time to learn their functions and that doesn't disappear, because you don't have to re-learn eveything from one version to the other.
Don't forget that systems you use daily seem to be simple, uniquely because you passed enough time to learn them.
For Internet competences, it's a statement of the obvious to say that this investment isn't lost.
At last, even with the work of translators to provide informations in french and other languages, a good knowledge in technical english is definitively a plus.
</para>
<para>
The last problem met in the implementation of free software solutions is to suceed in convincing some mnagers to go against the prevailing opinion.
The aim of this part is precisely to give all sorts of argumentations to achieve that goal, but you need each time to show conviction to get his way in the end.
As soon as these solutions will be adopted by big firms principaly, resistances will disappear.
</para>
</sect2>
</sect1>
<sect1>
<?html-filename linux-vs-os.html>
<title>
Linux and other operating systems
</title>
<para>
The aim is not to examine completely or to compare the functions of the various operating systems available.
It's more upon looking at the respective positions of Linux in comparaison with other systems.
Only systems having a sufficient representation on the market are considered.
</para>
<sect2><title>
Linux &et; other proprietary Unix (HP-UX, Tru64, AIX, Solaris, Irix)
</title>
<para>
The situation taken by all the hardware manufacturers place Linux today in the entry level (when it's taken in account) and their own Unix system in the middle and high level.
Reality is sometimes more cruel than the situation wanted by the marketing department :-). Technically, a Linux distribution has no cause to be envious of the manufacturers Unix solutions, except for the moment the set of commercial applications.
And we can often see that users dope their workstations with free software to complete their usage.
</para>
<para>
To be precise in the talk, we should consider manufacturers Unix solutions as split in stations and servers.
</para>
<para>
On the station side, there's no doubt in my mind: for a customer, the only reason today to buy one is linked to the availability of a software or a hardware which wouldn't exist in the free environment, or due to intrinsic performances of the machine.
In the first case, we can see that this argument should have a short life time, because logically every software editor (except maybe hardware manufacturers) and every hardware manufacturer has interest in porting their applications or allowing the use of their hardware on all the major environments in the market.
As shown by Oracle, Informix, Sybase, ... Linux becomes today one of the major environments.
In the second case, the difference in term of performances between the Linux dominant platform (IA-32) and the other competitors decreases and should even disappear with the availability of the IA-64 architecture, which seems to be adopted largely by a majority of actors.
More over, Linux is often available natively on the processors of these actors
(Sparc, Mips, PowerPC, 68xxx, Alpha, Crusoe, PA-Risc to come).
I think Linux may represent the famous unique and standard Unix that everybody dreamed of from a long time, without succeeding to impose it (the open and free characteristics brought by Linux are not without influence on that).
I think that at the end hardware manufacturer Unix workstations will be restricted to some niches such as high end computation, virtual reality, ... and that as long as solutions are not available on a free environment.
Linux offers all the functional qualities of the other Unix systems, and thus of the workstation, on a more various hardware platform and potentially at a better price, if on PCs.
So it is the natural choice of every computer engineer with a strong Unix culture (old customer of the workstation) who will prefer that solution to the migration to a Microsoft system typically.
</para>
<para>
On the server side, in addtion to the points mentionned previously for the stations, problems are more complex.
Ram, disks, processors capacities, extensions of every kind make them difficultly repleacable by machines with a IA-32 architecture for example.
More over, certain solutions such as high availability clusters for example are not already in production in a Linux environment.
The other brake is often linked to investments already done around software solutions deployed on these servers.
Whatever their natural life time is much higher than those of the stations.
Changes will thus be made more slowly in that domain.
Here we can consider rightly Linux solutions as an entry/middle level solutions, when hardware manufacturer Unix servers are the middle/high level.
The introduction of Linux in place of these machines will begin only with a massive availability of applications, mainly in the management sector.
</para>
<para>
The advantages of the hardware manufacturer solutions, explaining why they are so often chosen when applications are critical, are linked to the homogeneity of the solution (hardware and software mastered by the same entity, which can't invoke a third party in case of problem), and to the support and maintenance garantees furnished.
</para>
<para>
Finally, there is not so much antagonism between these systems, because they are full cousins.
Their association allows today to computer teams "pro-Unix" to have solutions from start to finish, without having to lose in functions, as it's so often the case with other operating systems available for personal computers.
</para>
</sect2>
<sect2><title>
Linux &et; SCO
</title>
<para>
The comparaison between Linux and the SCO systems seems to me quite unbalanced.
First, all the previous points are vaild here also.
More over, SCO isn't a hardware manufacturer, so the homogeneity advantage disappears.
the IA-32 Intel platform is supported by both systems, so cost is identical.
On the other hand, the software solution has a disproportionate cost (few software provided in the base install, thus a lot of expenses to extend, as well as to increase the number of users).
Having to manage one OpenServer, I can say that performances are far beyond those of a Linux system.
More over, its conception is older, abounds of symbolic links which makes management complex.
The hardware supported by SCO is less numerous than those Linux supports.
Only stay as an advantage the installed base and the set of applications available. But for how long ?
Besides the fact that SCO choose Monterey (AIX based) for the IA-64 port seems significant for the future reserved to OpenServer or UnixWare.
</para>
</sect2>
<sect2><title>
Linux &et; Windows NT
</title>
<para>
The comparaison is here more difficult, because Windows NT isn't an open system, as the precedings, which is already redhibitory for certain users.
An excellent <ulink url="http://unix-vs-nt.org/kirch/">comparaison</ulink> was made by John Kirch between Unix and Windows NT Server.
I recommend to people searching to have an enlightened opinion on this subject to read it; it's updated regularly and was written by a specialist of both Microsoft and Unix operating systems.
Financially, obvious advantage for the free software.
And it's more obvious, as for SCO, if you consider the set of complementary software you need to use a server.
The author evaluates the difference from 1 to 100 all the same !
Technically, either on the functions provided or on the reliability, the administration, the performances, the hardware supported, and more over the security, Unix systems and particularly free systems outperform what is proposed by Windows NT.
The fact to have a GUI non independant from the kernel contributes greatly to the instability of NT, because it's more difficult to avoid errors in a GUI (there is no mastering possible of the user comportment in front of it) rather than in a kernel.
</para>
<para>
Which are the real advantages of Windows NT ?: the marketing power of Microsoft which persuades the world that computers equal Windows and which leans on the enormous installed base; its office applications (a monopolistic situation on the market) only available in this environment; the confusion maintained between the various flavours of Windows (95/98, NT, 2000), and between the server and client functions; its agreements with the biggest hardware manufacturers which often oblige them to provide a Microsoft system with their platforms; its technological initiatives to occupy the market in first, based on proprietary code and that often without respect of known or documented standards.
</para>
<para>
The lack of hegemony in the servers sector is the best reason to hope that a plurality of solutions may exist in the future for computers users, also at the desktop.
</para>
</sect2>
</sect1>
</chapter>
<chapter id="LinuxHP">
<?html-filename hp-products.html>
<title>
Linux and HP products
</title>
<para>
To maintain such a chapter is an endless task :-).
</para>
<sect1><title>
Informations
on HP products and Linux
</title>
<sect2><title>
General informations
</title>
<para>
HP became recently concious of the importance taken by Linux and free software in general and on its machines particularly.
Thus a web site dedicated to Linux in HP environment is now available at
<urlsgml>http://www.hp.com/go/linux</urlsgml>.
</para>
<para>
In France, there is for a longer time a site on these themes, under the responsability of
Jacques Misselis <email>Jacques_Misselis@hp.com</email>, hosted by <ulink url="http://www.ec-lyon.fr">l'Ecole Centrale de Lyon</ulink> at the address <urlsgml>http://hpwww.ec-lyon.fr/hpeduc/education</urlsgml>.
</para>
<para>
On the other side, the firm
&Medasys;,
for which I work, put at disposition of the community a certain number of informations since 1997, available at
<urlsgml>http://www.medasys-digital-systems.fr/linux</urlsgml>.
This HOWTO is the result of this work.
</para>
<para>
HP also realized a synthesis document (PDF format) concerning his position vis <20> vis of Linux, the
<ulink url="http://www.medasys-digital-systems.fr/linux/HP-Howto/mirror/white-paper.pdf">White Paper HP Linux Strategy</ulink>.
</para>
<para>
HP is a member of
<ulink url="http://www.li.org">Linux International</ulink>.
</para>
</sect2>
<sect2><title>
Particular announces
</title>
<para>
HP also communicates through its web site around Linux and free software.
You'll find some links here.
</para>
<ItemizedList>
<listitem>
<para>
FireHunter announce (10/06/1998)
</para>
<para><urlsgml>http://www.tmo.hp.com/tmo/press/English/PRTM0804813.html</urlsgml></para>
</listitem>
<listitem>
<para>
Covision program announce (01/27/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/jan99/27jan99b.htm</urlsgml>
</para>
</listitem>
<listitem>
<para>
Linux support on NetServers and IA-64 announce (01/27/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/jan99/27jan99.htm</urlsgml>
</para>
</listitem>
<listitem>
<para>
PA-Risc port annouce (03/01/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/mar99/01mar99e.htm</urlsgml>
</para>
</listitem>
<listitem>
<para>
Informix HP association announce (03/02/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/mar99/02mar99i.htm</urlsgml>
</para>
</listitem>
<listitem>
<para>
Kayak Linux support (03/17/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/mar99/17mar99e.htm</urlsgml>
<!-- <urlsgml>http://interactive.medical.hp.com/smartfriend/cgi-bin/sfem.pl?EML10026=15126</urlsgml> -->
</para>
</listitem>
<listitem>
<para>
World Linux support announce (04/20/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/apr99/20apr99a.htm</urlsgml>
</para>
</listitem>
<listitem>
<para>
HP OpenView announces (05/17/1999)
</para>
<para>
<urlsgml>http://www.openview.hp.com/solutions/itsm/press/press.asp?docid=314</urlsgml>
</para>
</listitem>
<listitem>
<para>
Availability of Apache on HP 3000 (Summer/1999)
</para>
<para>
<urlsgml>http://www.businessservers.hp.com/falladvisor/sum99/Summer99/apache.html</urlsgml>
</para>
</listitem>
<listitem>
<para>
Visualize Linux support announce (06/21/1999)
</para>
<para>
<urlsgml>http://www.hp.com/pressrel/jun99/21jun99g.htm</urlsgml>
</para>
</listitem>
<listitem>
<para>
Open Source Software commitment by HP (08/09/1999)
</para>
<para>
<urlsgml>http://internetsolutions.enterprise.hp.com/linux/news/PRelease4.html</urlsgml>
</para>
</listitem>
<listitem>
<para>
Aberdeen group analysis on HP position on free software (08/09/1999)
</para>
<para>
<urlsgml>http://internetsolutions.enterprise.hp.com/linux/news/aberdeen_white_paper.html</urlsgml>
</para>
</listitem>
<listitem>
<para>
HP announces the certification of its DAT and DLT products under Linux
(02/02/2000)</para>
<para>
<urlsgml>http://www.hp.com/pressrel/feb00/02feb00c.htm</urlsgml>
<!-- http://search.hp.com/redirect.html?url=http%3A//www.internetsolutions.enterprise.hp.com/linux/news/HP_cert_release.html&qt=DAT+certification+on+linux&hit=1 -->
</para>
</listitem> <listitem>
<para>
HP Brings Award-winning 3-D VISUALIZE Graphics to Linux Desktop
(02/02/2000)</para>
<para>
<urlsgml>http://internetsolutions.enterprise.hp.com/linux/feb02page.html</urlsgml>
</para>
</listitem>
<listitem>
<para>
&Medasys;
chosen by Hewlett-Packard France Education/Research as Linux competence center
</para>
<para>
<urlsgml>http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux/educ_linux.html</urlsgml>
</para>
</listitem>
<listitem>
<para>
Hewlett-Packard France Education/Research announces commitment to Linux promotion
</para>
<para>
<urlsgml>http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux/hp_linux.html
</urlsgml>
</para>
</listitem>
<!--
<listitem>
<para>
<ulink url=""></ulink>
</para>
</listitem>
-->
</ItemizedList>
<para>
HP France
has also published an article on Linux and free software in its May 1999 issue of HP Computer News, an article on HP Linux support in the September 1999 issue, and an article on Linux RedHat solutions on HP Visualize workstation in the November 1999 issue.
</para>
</sect2>
</sect1>
<sect1>
<?html-filename hp-hardware.html>
<title>
HP hardware supported by Linux
</title>
<para>
This section presents HP hardware supported today by Linux. Informations are based on the latest stable version of the Linux kernel, which is currently version &curker;. A development kernel (version 2.3.x) is also available but doesn't offer any garantee of stability.
</para>
<sect2>
<title>
Intel based computer range
</title>
<para>
Page last updated the
&curdate;.
</para>
<para>
That computer range is today the main set of HP machines supported by Linux, and that till many years.
In case you didn't already do it before, some preliminaty readings are recommended before to try to install Linux on these platforms.
</para>
<para>
The
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Installation-HOWTO.html">Linux Installation HOWTO</ulink>
contains a great number of informations to install Linux. If you bought linux on a CD-ROM, chances are that installation instructions are provided with it (the little booklet inside the disk case, and/or files on the CD).
</para>
<para>
The
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Kernel-HOWTO.html">Linux Kernel HOWTO</ulink>
should be read to have details on kernel construction.
I will just mention here points which are specific to HP hardware.
</para>
<para>
Outside particular indication, Linux support means during the installation of a RedHat 6.1 distribution. In special cases, a kernel rebuild will be necessary to support completely some hardware elements. You should note that what is true for one distribution is generally true for another, as these functions are linked to the kernel or the XFree86 server, and not to the distribution itself.
</para>
<sect3>
<title>
The desktop range (Brio, Vectra, Kayak)
</title>
<para>
The following tables indicate the state of Linux support by these platforms :
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Brio &et; Linux</Title>
&tabmach;
<tbody>
<row>
<entry>Brio (D5522A, D5526A, D5857A, D6665A, D5838A, D5848A, D6514A, D5527A, D5528A, D6666A, D6675A, D5849A, D5839A, D5859A, D6666A, D6510A, D6515A, D6667A, D5840A, D5861A, D6668A, D5840C, D5841A, D6516B)</entry>
&cels3triov2;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Brio (D6810A, D6812A)</entry>
&celatipro;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Brio (D6638A, D6639A, D6640A, D6644A, D7901A, D7902A, D6645A, D6646A) &chipbx;</entry>
&celatipro;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Brio (D5841A, D6516B)</entry>
&celmilii;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Brio (D6760A, D7671A, D6908A, D7930A, D7672A, D7925T, D6776A, D6769A, D6755A, D6895A, D6896A, D6897A, D7931A)</entry>
&celmilg100;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Brio BA (D7581A, D7584A, D7585A, D7587A, D7586A, D7591A, D7594A, D8411A)</entry>
&celsisagp;
&celsans;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Brio BAx (D7600A, D7603A, D7624A, D7625A, D7630A, D7610A)<superscript><Link LinkEnd="bax">Rem.</link></superscript></entry>
&celmilp200;
&celsans;
&celsans;
&celcs4614;
&celoui;
</row>
<row>
<entry>Brio BAx (D7605A)<superscript><Link LinkEnd="bax">Rem.</link></superscript></entry>
&celmilp200;
&celinconnu;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Brio BA400 (D8767A, D8769A, D8934A, D8935A, D8936A, D8943A, D8947A, D8952A, D8953A, D9720A, D9721A)</entry>
&celi810;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Brio BA600 (D8773A, D8778A, D8788A, D8789A, D9070A, D9072A, D9080A, D9082A, D9085A, D9091A)&chipbx;</entry>
&celmilp200;
&celsans;
&celsans;
&celcs4614;
&celoui;
</row>
<row>
<entry>Brio BA600 (D8774A, D9075A)&chipbx;</entry>
&celmilp200;
&celinconnu;
&celsans;
&celcs4614;
&celnon;
</row>
</tbody>
</Tgroup>
</Table>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Vectra &et; Linux</Title>
&tabmach;
<tbody>
<row>
<entry>Vectra VE5 (D5592A, D5602A, D5603A, D5604A, D5606N, D5608A, D5612A, D5615A, D5618A, D5607A, D5617A)</entry>
&cels3triov2;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VE7 (D6530A, D6531A, D6533A, D6610A, D6611A, D6615A, D6616A, D6613A)</entry>
&celati2c;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VE7 (D6532A, D6612A, D6617A, D6618A)</entry>
&celati2c;
&cel3com;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VE8 (D6550A, D6560A, D6570A, D6554A, D6584A, D6540A, D6541A, D6544A, D6543A, D6578A, D6573A, D6574A, D6580A,D6581A, D6584A, D6583A, D6593A, D6597A, D6598A) &chipbx;</entry>
&celmilg100;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VE8 (D6552N, D6562N, D6565N, D6542A, D6572A, D6575A, D6582A, D6595A, D6582A, D6585N, D6599A) &chipbx;</entry>
&celmilg100;
&cel3com;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VEi7 (D8121A, D8123A, D8124A, D8126A, D8128A, D8129A, D8131A, D8133A, D8134A, D8136A, D8138A, D8139A, D8141A, D8143A, D8144A, D8145A, D8148A)</entry>
&celsisagp;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VEi7 (D8122A, D8127N, D8132A, D8137A)</entry>
&celsisagp;
&cel3com;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VEi8 (D8166A, D8168A, D8151A, D8153A, D8155A, D8169A, D8171A, D8173A, D8174A, D8181A, D8183A, D8184A, D8186A, D8188A, D9784A, D9786A, D9788A, D9793A)</entry>
&celmilp200;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VEi8 (D8167N, D8152N, D8172N, D8182N, D8187N, D9787N)</entry>
&celmilp200;
&cel3com;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL5 (D4552A, D4543A, D4554A, D4555A, D4556A, D4557A, D4558A, D4559A, D4560A, D4567A, D4562A, D4563A, D4572A, D4574A, D4576A, D4579A, D4577A)</entry>
&cels3triov2;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VL6</entry>
&celcl5446;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VL6</entry>
&celmilii;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL7 (D5710A, D5711N, D5725A, D5720A, D5721N, D5731N, D5797N, D5737A, D5799N)</entry>
&celcl5465;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VL7 (D5734N, D5729N, D5739N, D5728N, D5798N)</entry>
&celmilii;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL7 (D5724N, D5796N)</entry>
&celcl5465;
&celamd;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL8 (D5880A, D5882A, D5890A, D5891A, D5893A, D5896A, D5898A, D5900A, D5902A, D6945A) &chipbx;</entry>
&celmilg100;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL8 (D5881A, D5883A, D5894A, D5888A, D5892A) &chipbx;</entry>
&celmilg100;
&cel3com;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL8 (D5887A) &chipbx;</entry>
&celmilg100;
&cel3com;
&celinconnu;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL8 (D6944A) &chipbx;</entry>
&celmilg200;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL8 (D6940A, D6941A, D6942A) &chipbx;</entry>
&celmilg200;
&cel3com;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra VL8 (D6943A) &chipbx;</entry>
&celmilg200;
&cel3com;
&celaic7880;
&celinconnu;
&celoui;
</row>
<row>
<entry>Vectra VLi8 (D7941A, D7943A, D7945A, D7948A, D7951A, D7953A, D7955A, D7961A, D7963A, D7965A, D7958A, D7968A, D7969A, D7973A, D7976A, D9460A, D9463A, D9467A, D9774A, D9810A)</entry>
&celmilg200;
&celsans;
&celsans;
&celcs4614;
&celoui;
</row>
<row>
<entry>Vectra VLi8 (D7826A, D7836A, D7837A, D7846A, D7847A, D7848A, D7856A, D7857A, D7866A, D7867N, D7876A, D7877N, D7942A, D7949A, D7952A, D7959A, D7962A, D7969A, D7972A, D8696A, D8697A, D8950A, D9456A, D9457N, D9461A, D9462A, D9770N, D9771N, D9775A, D9779N, D9809A)</entry>
&celmilg200;
&cel3com905c;
&celsans;
&celcs4614;
&celoui;
</row>
<row>
<entry>Vectra VL600 (D9733A, D8643A, D9737A, D8647A) &coper;</entry>
&celmilg250;
&celsans;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Vectra VL600 (D7543N, D8644N, D8648N, D9734N, D9738N) &coper;</entry>
&celmilg250;
&cel3com905c;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Vectra VL600 (D8635A, D8645A, D8649N, D8659N, D8669N, D8679N, D9735A, D9739N) &coper;</entry>
&celmilg400;
&cel3com905c;
&celsans;
&celcs4614;
&celoui;
</row>
<row>
<entry>Vectra XA (D3986A, D3989A, D3990A, D3991A, D3993A, D4770N, D4771N,
D4773N, D4774N, D3994N, D3995N, D4776N)</entry>
&celmilii;
&celamd;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Vectra XA (D4777A)</entry>
&celmilii;
&celamd;
&celaic7880;
&celinconnu;
&celoui;
</row>
</tbody>
</Tgroup>
</Table>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Kayak &et; Linux</Title>
&tabmach;
<tbody>
<row>
<entry>Kayak XA (D4792A, D4795N)</entry>
&celcl5465;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA (D4807N, D4796N, D6491N, D6492N, D4806N, D4808N, D6493N)</entry>
&celcl5465;
&celamd;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XA (D4798N, D6490N, D4799N, D4803N, D6494N)</entry>
&celcl5465;
&celmixte2;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA (D4796S, D6493S)</entry>
&celmiliiagp;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA (D4803S)</entry>
&celmiliiagp;
&celmixte2;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA (D6720N, D6721N, D6723N, D6726N, D6724N, D6730N, D6731N, D6735N, D6736N, D6738N, D6739N, D7994N)</entry>
&celmilg200;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA (D6722N, D6729N, D6734N)</entry>
&celelsap;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XA (D6725N, D6732N, D6737N, D7993N)</entry>
&celmilg200;
&celmixte1;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XA (D6727N)</entry>
&celelsap;
&celmixte1;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA (D6728N, D6733N)</entry>
&celaccelg;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA-s (D5751N, D5752N, D5753N, D5755N, D5754N, D5756N, D5759N) &chipbx;</entry>
&celmilg100;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA-s (D5757N, D5758N) &chipbx;</entry>
&celmilg100;
&celmixte1;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XA-s (D5765N, D5763N, D5766N, D5769N, D7982N, D7986N, D7991N, D7987N) &chipbx;</entry>
&celmilp200;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XA-s (D5768N, D5767N) &chipbx;</entry>
&celmilp200;
&celmixte1;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA-s (D5762N, D7984N, D7988N) &chipbx;</entry>
&celelsap;
&celmixte1;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XA-s (D5764N, D7983N, D7989N) &chipbx;</entry>
&celaccelg;
&celmixte1;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA-s (D7990N) &chipbx;</entry>
&celmilg100;
&celmixte1;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XA-s (D7992N) &chipbx;</entry>
&celelsaii;
&celmixte1;
&celad1816;
&celoui;
</row>
<row>
<entry>Kayak XM600 (D9531N, D9533N, D9535N, D9541N, D9549N, D9553N)</entry>
&celmilg250;
&celsmc1211;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XM600 (D8350N, D9554N, D9558N) &moddos;</entry>
&celmilg250;
&celsmc1211;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XM600 (D9536N, D9537N, D9538N, D9539N, D9544N, D9548N)</entry>
&celmilg400;
&celsmc1211;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XM600 (D9534N, D9540N, D9543N, D9546N)</entry>
&celelsaii;
&celsmc1211;
&cel53c895;
&celcs4614;
&celoui;
</row>
<row>
<entry>Kayak XM600 (D9545N, D8366N)</entry>
&celgvx1;
&celsmc1211;
&cel53c895;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XU (D4691N, D4692N, D4695N, D4701N, D4693N, D4694N, D4702N, D4705N)</entry>
&celmilii;
&celamd;
&celaic6080;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XU (D5680N, D5682N, D5683N, D5684N) &chipbx;</entry>
&celmilii;
&celamd;
&celaic6080;
&celad1816;
&celoui;
</row>
<row>
<entry>Kayak XU (D5702, D5704, D5686N, D6336N, D6348N, D8431N, D8920N)</entry>
&celmilg200;
&celaic-mixte;
&celinconnu;
&celoui;
</row>
<row>
<entry>Kayak XU (D5687N, D6333N, D6334N, D8432N, D6345N, D8923N)</entry>
&celelsap;
&celaic-mixte;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XU (D6337N, D6346N)</entry>
&celaccelg;
&celaic-mixte;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XU (D6347N)</entry>
&celmilg100;
&celaic-mixte;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XU (D8924N)</entry>
&celmilg400;
&celaic-mixte;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XU800 (D8019N) &xu800;</entry>
&celmilg250;
&celsmc1211;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XU800 (D8021N) &xu800;</entry>
&celmilg400;
&celsmc1211;
&celsans;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XU800 (D8000N, D8001N) &xu800; &moddos;</entry>
&celmilg250;
&celsmc1211;
&cel53c895;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XU800 (D8002N, D8010N, D8016N) &xu800;</entry>
&celmilg250;
&celsmc1211;
&cel53c895;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XU800 (D8003N, D8006N, D8012N) &xu800;</entry>
&celmilg400;
&celsmc1211;
&cel53c895;
&celcs4614;
&celoui;
</row>
<row>
<entry>Kayak XU800 (D8007N, D8013N, D8020N, D8022N) &xu800;</entry>
&celelsaii;
&celsmc1211;
&cel53c895;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XU800 (D8009N, D8015N) &xu800;</entry>
&celgvx1;
&celsmc1211;
&cel53c895;
&celcs4614;
&celnon;
</row>
<row>
<entry>Kayak XW (D6475N)</entry>
&celelsa;
&celamd;
&celaic6080;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XW (D5505N, D5507N, D5509N)</entry>
&celaccele;
&celamd;
&celaic6080;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XW (D5510N, D5514N, D6485N)</entry>
&celfx4;
&celamd;
&celaic6080;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XW (D6480N, D6481N, D6482N) &chipbx;</entry>
&celaccele;
&celinconnu;
&celinconnu;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XW (D6797N)</entry>
&celfx6;
&celinconnu;
&celinconnu;
&celinconnu;
&celnon;
</row>
<row>
<entry>Kayak XW (D6486N, D6487N, D6488N) &chipbx;</entry>
&celfx4;
&celinconnu;
&celinconnu;
&celinconnu;
&celnon;
</row>
</tbody>
</Tgroup>
</Table>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Visualize &et; Linux</Title>
&tabmach;
<tbody>
<row>
<entry>Visualize P (A5015A) &chipbx;</entry>
&celelsap;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<row>
<entry>Visualize P (A5015A) &chipbx;</entry>
&celelsaii;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<row>
<entry>Visualize P (A1296A) &chipbx;</entry>
&celelsaii;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<row>
<entry>Visualize X (A5014A) &chipbx;</entry>
&celelsap;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<row>
<entry>Visualize X (A5014A) &chipbx;</entry>
&celelsaii;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<row>
<entry>Visualize X (A1297A) &chipbx;</entry>
&celelsap;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<row>
<entry>Visualize X (A1280A)</entry>
&celelsaii;
&celinconnu;
&celinconnu;
&celad1816;
&celnon;
</row>
<!-- P600 : A5984A -->
</tbody>
</Tgroup>
</Table>
<para>
A page dedictaed to these machines and their support under LInux is available at
<urlsgml>http://www.hp.com/visualize/support/technotes/linux</urlsgml>
</para>
</sect3>
<sect3>
<title>Desktop computer accessories</title>
&tabintrol;
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Desktop computer accessories</Title>
&tabopt;
<tbody>
<row>
<entry>D5480A</entry>
&celfastr;
&celaicaro;
&celnon;
</row>
<row>
<entry>D6690A</entry>
&celfastr;
&celaicaro;
&celnon;
</row>
<row>
<entry>D6951A</entry>
&celscsi;
&celaic7880;
&celoui;
</row>
<row>
<entry>D9528A</entry>
&celscsi;
&celsym8952;
&celnon;
</row>
<row>
<entry>D9529A</entry>
&celscsi;
&celinconnu;
&celnon;
</row>
<row>
<entry>D6936A</entry>
&celnet;
&celamd2;
&celoui;
</row>
<row>
<entry>D7504A</entry>
&celnet;
&cel3com;
&celoui;
</row>
<row>
<entry>D7506A</entry>
&celnet;
&celinconnu;
&celnon;
</row>
<row>
<entry>D7508A</entry>
&celnet;
&celinconnu;
&celnon;
</row>
<row>
<entry>D7522A</entry>
&celnet;
&cel3com905c;
&celoui;
</row>
<row>
<entry>D7531A</entry>
&celnet;
&celrealtek;
&celoui;
</row>
<row>
<entry>D6657A</entry>
&celson;
&celinconnu;
&celnon;
</row>
<row>
<entry>D5183A</entry>
&celson;
&celinconnu;
&celnon;
</row>
</tbody>
</Tgroup>
</Table>
<para>
CD-ROM, DVD and ZIP drives are supported by Linux kernel. Read the various HOWTO for their use, following the interface type.
</para>
</sect3>
<sect3>
<title>The portable range (OmniBook)</title>
<!--
Pour la prise en charge l'APM ...
-->
&tabintrol;
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>OmniBook &et; Linux</Title>
&tabmach;
<tbody>
<row>
<entry>OmniBook 800 (F1360A)</entry>
&celneo128;
&celsans;
&celscsi;
&celncr53;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 2000 (F1356A, F1397A)</entry>
&celct65554;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>OmniBook Sojourn (F1430A)</entry>
&celneo128;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>OmniBook XE (F1719W, F1720W, F1721W, F1722W)</entry>
&cellynxe;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook XE2 (F1664W, F1666W, F1666N, F1667W, F1667N, F1674W, F1675W, F1753W, F1756W, F1755W, F1755N, F1772W, F1774N, F1774W, F1775N, F1775W, F1962W)</entry>
&cellynxe;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 2100 (F1584W, F1580W, F1581W, F1597W, F1598W, F1599W, F1600W, F1729W)</entry>
&celneo128;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 900 (F1711W, F1712W, F1760W, F1711N, F1712N, F1765N)</entry>
&celneo256;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 900 (F1769W, F1769N, F1769K, F1770W, F1770N, F1770K, F1979W, F1979N, F1979K, F1980W, F1980N, F1980K)</entry>
&celatiport;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>OmniBook 3000 (F1391A, F1392A, F1393A)</entry>
&celneo128;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>OmniBook 3100 (F1582W)</entry>
&celneo128;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
<row>
<entry>OmniBook 4100 (F1462W, F1463W, F1479W, F1464W, F1703W)</entry>
&celneo128;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 4150 (F1629W, F1640W, F1641W, F1642W, F1629N, F1640N, F1641N, F1642N, F1647W, F1647N, F1648W, F1648N, F1663W, F1663N)</entry>
&celneo256;
&celsans;
&celsans;
&celcs4232;
&celoui;
</row>
<row>
<entry>OmniBook 4150 (F1649W, F1649N, F1649K, F1650W, F1650N, F1650K, F1658W, F1658N, F1660W, F1660N, F1662W, F1662N, F1662K, F1976W, F1976N, F1976K, F1983W, F1983N, F1983K, F2000W, F2000N, F2000K, )</entry>
&celatiport;
&celsans;
&celsans;
&celcs4232;
&celoui;
</row>
<row>
<entry>OmniBook 5700 (F1352A, F1353A, F1396A, F1354A, F1355A)</entry>
&celct65554;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 7100 (F1441W, F1442W)</entry>
&celatiltpro;
&celsans;
&celsans;
&celinconnu;
&celoui;
</row>
<row>
<entry>OmniBook 7150 (F1443W)</entry>
&celatiltpro;
&celsans;
&celsans;
&celinconnu;
&celnon;
</row>
</tbody>
</Tgroup>
</Table>
</sect3>
<sect3>
<title>Portable accessories</title>
<para>
The cards mentionned below are PCMCIA or PC-Card cards.
</para>
&tabintrol;
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Portable accessories</Title>
&tabopt;
<tbody>
<row>
<entry>F1623A</entry>
&celcombo;
&celxirc56;
&celoui;
</row>
<row>
<entry>F1625A</entry>
&celmodem;
&celinconnu;
&celnon;
</row>
<row>
<entry>F1626A</entry>
&celnet;
&cel3c575;
&celnon;
</row>
<row>
<entry>F1626B</entry>
&celnet;
&celinconnu;
&celnon;
</row>
<row>
<entry>F1643A</entry>
&celcombo;
&celinconnu;
&celnon;
</row>
</tbody>
</Tgroup>
</Table>
</sect3>
<sect3>
<title>The server range (NetServer)
</title>
<para>
A page on how Linux works on HP NetServer is available at
<urlsgml>http://www.netserver.hp.com/netserver/products/highlights_linux.asp</urlsgml>
</para>
<para>
An official compatibility matrix of HP NetServer with Linux and other operating systems is available at :
<urlsgml>http://netserver.hp.com/netserver/support/compatibility/drvmatrx.htm</urlsgml>
</para>
<para>
Official documents to help configuring NetServer under Linux
&RedHat; <ulink url="http://www.medasys-digital-systems.fr/linux/HP-Howto/mirror/netserver-rh5.2.pdf">5.2</ulink> &et; <ulink url="http://www.medasys-digital-systems.fr/linux/HP-Howto/mirror/netserver-rh6.0.pdf">6.0</ulink>
are also available.
</para>
&tabintrol;
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>NetServer &et; Linux</Title>
&tabmach;
<tbody>
<row>
<entry>NetServer E45 (D4973A, D4974A, D4975A, D4976A, D5971A)</entry>
&celcl5446;
&cel5013;
&celaic2910;
&celsans;
&celnon;
</row>
<row>
<entry>NetServer E50 (D6034A, D6033A, D6035A, D6031A, D6030A, D6032A)</entry>
&celcl5446;
&cel5013;
&celaic7880;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer E55 (D9337A)</entry>
&celati2c;
&cel5013i;
&celaic7895;
&celsans;
&celnon;
</row>
<row>
<entry>NetServer E60 (D7140A, D7142A, D7144A, D7146A, D7148A, D9123A, D9127A, D9128A, D9129A)</entry>
&celati2c;
&cel5013i;
&celaic7895;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LC II (D4907A, D4909A, D5014A, D5015A, D5016A, D5969A, D5970A, D5959A, D5961A)</entry>
&celcl5446;
&cel5013;
&celaic7880;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LC 3 (D6123A, D7018A, D6125A, D7020A, D7028A, D7025A, D7126A, D8594A) &chipbx;</entry>
&celcl5446;
&cel5013;
&celaic7880;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LC 2000 (D8514A, D8515A, D8519A, D8520A, D8524A, D8525A, D9162A, D9163A) &coper; &lc2000;</entry>
&celati2c;
&cel5013i;
&cel53c897x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LD Pro (D4944A, D4946A, D4961A, D4962A)</entry>
&celt9000;
&cel5013;
&celaic7880;
&celsans;
&celnon;
</row>
<row>
<entry>NetServer LH Pro (D4979A, D4980A, D4981A, D4982A)</entry>
&celt9000;
&celsans;
&celaic7880x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LH II (D5017A, D5953A, D5021A, D5023A, D6047A, D6048A)</entry>
&celt9000;
&celsans;
&celaic7880x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LH 3 (D4998A, D5002A, D5000A, D5004A, D7033A, D7034A, D8503A, D8504A, D8567A, D8568A, D9343A, D9344A) &chipbx;<superscript><Link LinkEnd="netraid">Rem.</link></superscript></entry>
&celcl5446;
&cel5013;
&cel53c895x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LH 3000 (D8228A, D8230A, D8236A, D8238A, D8244A, D8246A, D9176A, D9178A) &chipbx;<superscript><Link LinkEnd="netraid">Rem.</link></superscript></entry>
&celinconnu;
&celinconnu;
&celinconnu;
&celsans;
&celnon;
</row>
<row>
<entry>NetServer LH 4 (D7092A, D7093A, D7094A, D7095A, D6971A, D6972A, D6973A, D6974A, D7103A, D7104A, D8552A, D8553A, D8556A, D8557A, D8560A, D8561A) &chipbx; <superscript><Link LinkEnd="netraid">Rem.</link></superscript><superscript><Link LinkEnd="lh4">Rem.</link></superscript></entry>
&celcl5446;
&cel5013;
&cel53c895x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LH 6000 () &chipbx;<superscript><Link LinkEnd="netraid">Rem.</link></superscript> &lh6000;</entry>
&celati2c;
&cel5013i;
&celaic-53c896x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LPr (D6130A, D6131A, D7171A, D9133A, D9348A, D9431A, D9434A) &chipbx;</entry>
&celcl5446;
&cel5013;
&cel53c895;
&celsans;
&celoui;
</row>
<row>
<entry>Cluster NetServer LPr (D6131A, P1133A)<superscript><Link LinkEnd="cluster">Rem.</link></superscript></entry>
&celcl5446;
&cel5013;
&cel53c895;
&celsans;
&celnon;
</row>
<row>
<entry>NetServer LXePro/LXPro (D4920B, D4925B, D6036A, D4311B, D4312B, D6037A,
D4315B, D4958B, D6014A, D6015A, D4964B, D4898A, D6016A, D4899A, D6017A,
D4900A, D6018A)</entry>
&celcl5424;
&celsans;
&celaic7880x2;
&celsans;
&celnon;
</row>
<row>
<entry>NetServer LXr8 (D5028A)</entry>
<entry>?</entry>
<entry>?</entry>
&celsans;
<entry>Symbios logic UW</entry>
<entry>?</entry>
&celsans;
&celnon;
</row>
<row>
<entry>NetServer LXr8000 (D6021A, D6022A, D6136A, D6137A, D7000A, D8256A, D8257A, D8258A, D8546A, D8548A)</entry>
&celcl5446;
&celsans;
&cel53c896x2;
&celsans;
&celoui;
</row>
<row>
<entry>NetServer LXr8500 (D8540A, D8542A, D9417A, D9418A)</entry>
&celcl5446;
&celsans;
&cel53c896x2;
&celsans;
&celnon;
</row>
</tbody>
</Tgroup>
</Table>
</sect3>
<sect3>
<title>NetServers accessories</title>
&tabintrol;
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>NetServers accessories</Title>
&tabopt;
<tbody>
<row>
<entry>NetRaid 1 D4992A</entry>
&celnetr;
&celnetraid;
&celoui;
</row>
<row>
<entry>NetRaid 3 D4943A</entry>
&celnetr;
&celnetraid;
&celoui;
</row>
<row>
<entry>NetRaid 1Si D2140A</entry>
&celnetr;
&celnetraid;
&celoui;
</row>
<row>
<entry>NetRaid 3Si D5955A</entry>
&celnetr;
&celnetraid;
&celoui;
</row>
<row>
<entry>C1578B</entry>
&celscsi;
&celaic7895;
&celnon;
</row>
<row>
<entry>C7430A</entry>
&celscsi;
&celaic7880;
&celnon;
</row>
<row>
<entry>D5025A</entry>
&celscsi;
&celaic7880;
&celoui;
</row>
<row>
<entry>D5252A</entry>
&celscsi;
&celaic7880D;
&celoui;
</row>
<row>
<entry>D5013A, D5013B</entry>
&celnet;
&cel5013;
&celoui;
</row>
<row>
<entry>J2585B</entry>
&celnet;
&celhp100;
&celoui;
</row>
<row>
<entry>D6977A</entry>
&celfc;
&celinconnu;
&celnon;
</row>
<row>
<entry>D5246A</entry>
&celfc;
&celinconnu;
&celnon;
</row>
<row>
<entry>D6028A</entry>
&celtopt;
&celbof;
&celoui;
&celoui;
</row>
</tbody>
</Tgroup>
</Table>
</sect3>
<sect3>
<title>Complementary informations</title>
<para>
Please refer to the
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Hardware-HOWTO.html">Hardware Howto</ulink> &et; <ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Ethernet-HOWTO.html">Ethernet Howto</ulink>
for other details concerning the support of some hardware elements by Linux.
</para>
<para>
For video chipsets support, a fundamental page is the one of
<ulink url="http://www.xfree86.org/3.3.6/index.html">XFree86</ulink>
with its supported
<ulink url="http://www.xfree86.org/cardlist.html">chipsets</ulink>
list and the new running developments by
<ulink url="http://www.suse.de/XSuSE/XSuSE_E/index.html">Suse</ulink>
(Think, in that case, to download also
<ulink url="ftp://ftp.medasys-digital-systems.fr/pub/linux/XSuSE/config/xsuseconfig.tgz">the configuration tool</ulink>) &et; &RedHat; at the following addresses :
</para>
<ItemizedList>
<listitem>
<para>
<urlsgml>ftp://ftp.medasys-digital-systems.fr/pub/linux/redhat.com/XBF</urlsgml>
</para>
</listitem>
<listitem>
<para>
<urlsgml>ftp://ftp.medasys-digital-systems.fr/pub/linux/redhat.com/XFCom</urlsgml>
</para>
</listitem>
</ItemizedList>
<para>
Commercial servers are also available, as those of
<ulink url="http://www.xig.com/">X-Inside</ulink> &et; <ulink url="http://www.metrolink.com/">MetroLink</ulink>
</para>
<para>
Netvectra are not supported by Linux.
</para>
<sect4>
<!--<Note>--><Title>Remarks</Title>
<variablelist>
<varlistentry id="xfree86"><term>XFree86</term>
<listitem>
<para>
The latest version of XFree86 is the 3.3.6, available from our
<ulink url="ftp://ftp.medasys-digital-systems.fr/pub/unix/XFree86/3.3.6">mirror</ulink>.</para>
</listitem>
</varlistentry>
<varlistentry id="ncr53c8xx"><term>Ncr53c8xx</term>
<listitem>
<para>
The latest version of the ncr53c8xx driver is available from the
<ulink url="ftp://ftp.tux.org/pub/roudier">reference site</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry id="c3c59x"><term>3C59x</term>
<listitem>
<para>
The latest version of the 3c59x driver is available from the
<ulink url="ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/test/3c59x.c">reference site</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry id="ad1816"><term>Sound Chipset AD1816</term>
<listitem>
<para>
The latest version of the AD1816 driver is available from the
<ulink url="http://www.student.informatik.tu-darmstadt.de/~tek/projects/linux.html">reference site</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry id="moddos"><term>DOS models</term>
<listitem>
<para>
These models are delivered with MS-DOS only, in order to have a Linux Machine at the best price.
</para>
</listitem>
</varlistentry>
<varlistentry id="g100"><term>G100 card</term>
<listitem>
<para>
To use the MGA G100 AGP card, with a version of XFree86 before the 3.3.2 one, you have to use an option in the file
<filename>XF86Config</filename> : Option "no_accel".
</para>
<para>
Section example :
<ProgramListing>
Section "Device"
[...]
VendorName "Matrox"
VideoRam 4096
Option "no_accel"
EndSection
</ProgramListing>
</para>
</listitem>
</varlistentry>
<varlistentry id="lynxe"><term>Silicon Motion LynxE card</term>
<listitem>
<para>
This card is only supported from the 3.3.6 version of XFree86. Nevertheless, even in that version, this is a preliminary support, which isn't as stable as the Frame Buffer mode.
</para>
<para>
On the other hand, to be able to install a RedHat 6.1 version, you should do that in text mode, because the server provided (3.3.5) doesn't support this card.
</para>
</listitem>
</varlistentry>
<varlistentry id="i810"><term>Intel i810 card</term>
<listitem>
<para>
(Informations provided by Fr<46>d<EFBFBD>ric Dubuy <email>Frederic.Dubuy@medasys-digital-systems.fr</email> &et; Anne-Marie Mahfouf <email>a-m.mahfouf@lineone.net</email>)
</para>
<para>
This card is only supported with a specific X server XFCom_i810 downloadable in both format
<ulink url="ftp://download.intel.com/support/graphics/intel810/xfcom-i810-glibc2.1-1.0.0-rh60.i386.rpm">RPM</ulink> &ou; <ulink url="ftp://download.intel.com/support/graphics/intel810/xfcom-i810-glibc2.1-1.0.0.tar.gz">tar.gz</ulink>
and a complementary module for the kernel agpgart, downloadable in both format
<ulink url="ftp://download.intel.com/support/graphics/intel810/i810gtt-0.1-5.src.rpm">SRPM</ulink> &ou; <ulink url="ftp://download.intel.com/support/graphics/intel810/i810gtt-0.1-5.src.tar.gz">tar.gz</ulink>.
</para>
<para>
A detailed documentation on the installation is provided at
<urlsgml>http://www.linux-france.org/article/x/GuideIntel810/book1.html</urlsgml>
</para>
<para>
To summarize, once the X server installed, the module compiled and installed, it's sufficient to modify with the following parameters the file
<filename>/etc/X11/XF86Config</filename> :
<ProgramListing>
Section "Device"
[...]
Identifier "i810"
[...]
EndSection
[...]
Section "Screen"
[...]
Driver "svga"
Device "i810"
[...]
EndSection
</ProgramListing>
</para>
</listitem>
</varlistentry>
<varlistentry id="xu800"><term>XU800</term>
<listitem>
<para>
On that machine, the Bios doesn't give the right amount of memory which is in the machine to Linux. You need to use a line such as
append="mem=xxxM" at the begining of <filename>/etc/lilo.conf</filename>
where xxx is your RAM in MB.
</para>
</listitem>
</varlistentry>
<varlistentry id="lc2000"><term>LC 2000</term>
<listitem>
<para>
In order to use the native SCSI controler you need to disable in the Bios the option "Reserve PCI Bus Numbers", in the menu PCI Device Setting.
(Indication of GILLYNN COUCH)
</para>
</listitem>
</varlistentry>
<varlistentry id="lh6000"><term>LH 6000</term>
<listitem>
<para>
In order to use the native SCSI controler you need to desactivate in the Bios
the "reserver PCI Bus #s", in the menu PCI Device Setting.
The PS/2 system doesn't seem to be operational on the machine we tested. On the other side, through the network, the system is perfectly operational in a 6-processors mode :-)
</para>
</listitem>
</varlistentry>
<varlistentry Id="bx"><term>BX Chipset</term>
<listitem>
<para>
Intel BX Chipset (Memory Bus at 100 MHz) is supported by
<ulink url="ftp://ftp.medasys-digital-systems.fr/pub/linux/kernel">kernels</ulink> above 2.0.34/2.1.103.
</para>
</listitem>
</varlistentry>
<varlistentry Id="coper"><term>i820 Chipset</term>
<listitem>
<para>
Coppermine 0.18 <20>m technology - 256 KB synchronous cache - Intel i820 Chipset
</para>
</listitem>
</varlistentry>
<varlistentry Id="bax"><term>BAx</term>
<listitem>
<para>
Attention, the XF86_SVGA server works correctly with this mother board embedded version only above XFree86 3.3.5, due to the use of different frequencies (In particular, use the updates for
RedHat 5.2/6.0).</para>
</listitem>
</varlistentry>
<varlistentry Id="fbdev"><term>FrameBuffer</term>
<listitem>
<para>
To use the FrameBuffer mode, please consult the following documents
<urlsgml>http://www.medasys-digital-systems.fr/linux/framebuffer.html</urlsgml> &et; <urlsgml>http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Framebuffer-HOWTO.html</urlsgml>.
</para>
</listitem>
</varlistentry>
<varlistentry Id="c3com"><term>Boot disk for 3Com card</term>
<listitem>
<para>
<emphasis>Creation of a custom RedHat Boot disk</emphasis>
</para>
<para>
To be able to boot with the RedHat 5.1 boot disk, and to have the support of the 3C905B-TX card, you need to do the following :
</para>
<para>
<screen>
# Log as root. Go in the home directory (~root)
<prompt>#</prompt><userinput>cd ~</userinput>
# Put there the 3c59x.c source module for the 3Com card
<prompt>#</prompt><userinput>ncftp ftp://ftp.medasys-digital-systems.fr/pub/linux/networking/drivers/3c59x.c</userinput>
# Compile it
<prompt>#</prompt><userinput>gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -c 3c59x.c `[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`</userinput>
# put the RedHat 5.1 floppy boot disk in the drive
# you have to copy the initrd.img file from the floppy disk
<prompt>#</prompt><userinput>mcopy a:initrd.img /tmp</userinput>
# then uncompress it
<prompt>#</prompt><userinput>gzip -cd /tmp/initrd.img > /tmp/initrd.ext2</userinput>
# Mount the "file" filesystem thus obtained
<prompt>#</prompt><userinput>mount -t ext2 /tmp/initrd.ext2 /mnt/floppy -o loop</userinput>
# uncompress the modules provided
<prompt>#</prompt><userinput>gzip -cd /mnt/floppy/modules/modules.cgz > /tmp/modules.cpio</userinput>
# extract the modules
<prompt>#</prompt><userinput>cd /tmp ; mkdir modules ;
cd modules ; cat /tmp/modules.cpio | cpio -i</userinput>
# Copy the new updated module for the 3Com card
<prompt>#</prompt><userinput>cp ~/3c59x.o .</userinput>
# recreate the compressed cpio file
<prompt>#</prompt><userinput>ls | cpio -o | gzip -c9 > ../newmodules.cgz</userinput>
# replace the modules by their update
<prompt>#</prompt><userinput>cp ../newmodules.cgz /mnt/floppy/modules/modules.cgz</userinput>
# unmount the "file" filesystem
<prompt>#</prompt><userinput>umount /mnt/floppy</userinput>
# compress the "file" filesystem
<prompt>#</prompt><userinput>gzip -c9 /tmp/initrd.ext2 > /tmp/initrd.img</userinput>
# copy it on the floppy disk
<prompt>#</prompt><userinput>mcopy /tmp/initrd.img a:</userinput>
</screen>
</para>
</listitem>
</varlistentry>
<varlistentry Id="cl5465"><term>GD 5465 video card</term>
<listitem>
<para>
To use a Cirrus Logic GD 5465 AGP card, with a version below Xfree86 3.3.3, you have to use an option in the file
<filename>XF86Config</filename> : Option "xaa_no_color_exp".
</para>
<para>
Section example :
<ProgramListing>
Section "Device"
[...]
Identifier "CL-GD5465"
VendorName "Cirrus"
BoardName "GD5465"
VideoRam 2048
Option "xaa_no_color_exp"
EndSection
</ProgramListing>
</para>
</listitem>
</varlistentry>
<varlistentry Id="elsa"><term>Elsa Gloria Synergy card</term>
<listitem>
<para>
Specifications of that card should be consulted on Elsa web site.
This card is equiped with an hardware OpenGL accelerator.
Under Linux, there is an OpenGL compatible layer called Mesa.
This layer begins to support hardware accelerators, and among them the 3DLabs chipset which is on Elsa Gloria cards.
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
<ulink url="http://www.elsa.de/EUROPE/PRODUCTS/CAD/SPECS/GLO_SYN.HTM">Elsa web site</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.sgi.com/software/opengl">OpenGL web site</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.mesa3d.org/">Mesa web site</ulink>
</para>
</listitem>
</ItemizedList>
</para>
</listitem>
</varlistentry>
<varlistentry Id="mixte1"><term>D6692A card</term>
<listitem>
<para>
To use the D6692A card, you need to use a 2.1.122 kernel at least.
Previous kernels didn't handled correctly the shared IRQ between the network and SCSI parts of the card. In particular, a standard RedHat 5.2 version doesn't allow to the network part to be supported. You have to update your kernel with a recent one (preferably &curker;) and the distribution with the complementary packages needed.
</para>
</listitem>
</varlistentry>
<varlistentry Id="cluster"><term>HA Cluster</term>
<listitem>
<para>
To use a High Availability Custer under Linux, you need to use additional software, such as :
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
<ulink url="http://www.rsi.co.uk/products/rsf/rsf-linux.html">RSF-1 (Commercial)</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.henge.com/~alanr/ha">Linux-HA project (free)</ulink> &et; <ulink url="ftp://ftp.medasys-digital-systems.fr/pub/linux/ext3">ext3</ulink>
</para>
</listitem>
</ItemizedList>
</para>
</listitem>
</varlistentry>
<varlistentry Id="lh4"><term>LH 4</term>
<listitem>
<para>
The LH4 doesn't seem to work correctly when not in Raid. Even with the latest Bios available at the time of the test (16.00), the problem remains. If you desactivate the Raid management, during the boot, the ncr53c8xx driver in Linux detects 4 controlers instead of 2 and boot doesn't end. To avoid that, you have to activate the Raid in the Bios and use each of the disk in Raid0 mode, which is quite the same as the solution without Raid at all.
</para>
</listitem>
</varlistentry>
<varlistentry Id="netraid"><term>NetRaid card</term>
<listitem>
<para>
These cards are equiped with an
<ulink url="http://www.ami.com">AMI</ulink> Megaraid
chipset and may support the following Raid levels :
0, 1, 3, 5, 10, 30 &et; 50.
Some NetRaid cards, as well as the chipset integrated on the LH3 and LH4 mother boards are supported by recent version of the Linux kernel (2.0.36/&curker; typically - don't use 2.0.37/38).
</para>
<para>
For the RedHat 5.2 distribution, it's not possible to install the system on this type of controler, because it's not detected by the installation program. You have to use a specific
<ulink url="ftp://ftp.medasys-digital-systems.fr/pub/linux/mds/redhat/images/lh3.img">floppy disk</ulink>
. This floppy disk should be used as input to the <command>rawrite</command> tool, for example. It works for systems with less than 1 GB of memory.
</para>
<para>
For the RedHat 6.0 distribution, you have to manually declare the existence of this card as a supplementary SCSI adapter, in order to use it directly during the installation. The megaraid driver isn't automatically detected.
</para>
<para>
To avoid strange messages during the boot printed by the megaraid driver, it's necessary to recompile it with the option -DHP.
</para>
<para>
For the RedHat 6.1 distribution, the megaraid driver provided by the kernel does support on ly the first logical drive. In order to obtain the others, please recompile a &curker; standard kernel.
</para>
<para>
You have to note that the integrated card of the LH3/4 realises a software parity checks and performs thus less efficiently than the NetRaid daughter cards. On the other side, LH6000 are equiped with an integrated card doing hardware checks.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect4>
<!-- Onduleurs APC
http://www.apcc.com/products/management/pcp_linux.cfm
-->
</sect3>
</sect2>
<sect2>
<title>The monitors range</title>
&tabintrox;
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>HP Monitors &et; Linux</Title>
&tabmon;
<tbody>
<row>
<entry>D2825A, D2825S</entry>
<entry>15" HP Ultra VGA 1024</entry>
<entry>50-110</entry>
<entry>31-54</entry>
<entry>65</entry>
<entry>640x400, 640x480, 800x600, 1024x768</entry>
<entry>70, 60-72-75-85, 60-72-75-85, 60</entry>
&celoui;
</row>
<row>
<entry>D2826A, D2826S</entry>
<entry>15" HP 50</entry>
<entry>50-120</entry>
<entry>31-54</entry>
<entry>65</entry>
<entry>640x400, 640x480, 800x600, 1024x768</entry>
<entry>70, 60-75-85, 60-75-85, 60</entry>
&celoui;
</row>
<row>
<entry>D2827A</entry>
<entry>15" HP 51</entry>
<entry>50-120</entry>
<entry>31-54</entry>
&celbof;
&celbof;
&celbof;
&celnon;
</row>
<row>
<entry>D2828A</entry>
<entry>15" HP 52</entry>
<entry>50-120</entry>
<entry>30-54</entry>
<entry>65</entry>
<entry>640x400, 640x480, 800x600, 1024x768</entry>
<entry>70, 60-75-85, 60-75-85, 60</entry>
&celnon;
</row>
<row>
<entry>D2832A</entry>
<entry>15" HP M500</entry>
<entry>50-120</entry>
<entry>30-70</entry>
<entry>110</entry>
<entry>640x400, 640x480, 800x600, 1024x768, 1280x1024</entry>
<entry>70, 60-75-85, 72-75-85, 70-75-85, 60</entry>
&celnon;
</row>
<row>
<entry>D2807A</entry>
<entry>17" Ultra 1280</entry>
<entry>50-160</entry>
<entry>30-64</entry>
&celbof;
&celbof;
&celbof;
&celoui;
</row>
<row>
<entry>D2837A</entry>
<entry>17" HP70</entry>
<entry>50-120</entry>
<entry>30-70</entry>
<entry>110</entry>
<entry>640x400, 640x480, 800x600, 1024x768, 1280x1024</entry>
<entry>70, 75-85, 75-85, 75-85, 60</entry>
&celoui;
</row>
<row>
<entry>D2838A</entry>
<entry>17" HP M700</entry>
<entry>50-160</entry>
<entry>30-86</entry>
&celbof;
&celbof;
&celbof;
&celnon;
</row>
<row>
<entry>D2840A</entry>
<entry>17" Ergo 1280</entry>
<entry>50-150</entry>
<entry>31-92</entry>
<entry>160</entry>
<entry>512x384, 640x480, 800x600, 1024x768, 1152x864, 1280x1024, 1440x1080, 1600x1200</entry>
<entry>85, 100, 100, 100, 100, 85, 72, 60</entry>
&celoui;
</row>
<row>
<entry>D8901A, D8902A</entry>
<entry>17" HP71</entry>
<entry>50-120</entry>
<entry>30-60</entry>
<entry>110</entry>
<entry>640x400, 640x480, 800x600, 1024x768, 1280x1024</entry>
<entry>70, 60, 75-85, 75-85, 60</entry>
&celnon;
</row>
<row>
<entry>D8900A</entry>
<entry>17" HP75</entry>
<entry>50-160</entry>
<entry>30-86 (30-64 real)</entry>
<entry>150</entry>
<entry>640x400, 640x480, 800x600, 1024x768, 1280x1024</entry>
<entry>70, 60-75-85, 75-85, 75-75-85, 75</entry>
&celoui;
</row>
<row>
<entry>D2842A, D2842W</entry>
<entry>19" HP 90</entry>
<entry>50-200</entry>
<entry>30-96</entry>
<entry>203</entry>
<entry>640x400, 640x480, 800x600, 1024x768, 1280x1024, 1600x1200</entry>
<entry>70, 75-85, 75-85, 75-85, 75-85, 75</entry>
&celoui;
</row>
<row>
<entry>D8910A</entry>
<entry>19" HP 910</entry>
<entry>50-150</entry>
<entry>29-107</entry>
<entry>230</entry>
<entry>640x400, 640x480, 800x600, 1024x768, 1280x1024, 1600x1200</entry>
<entry>70, 60-85, 85, 75-85, 75-85, 75-85</entry>
&celnon;
</row>
<row>
<entry>A4031A</entry>
<entry>20"</entry>
<entry>48-150</entry>
<entry>30-82</entry>
&celbof;
&celbof;
&celbof;
&celoui;
</row>
<row>
<entry>D2846A, A4576A</entry>
<entry>21" P1100</entry>
<entry>50-160</entry>
<entry>30-107</entry>
&celbof;
&celbof;
&celbof;
&celnon;
</row>
<row>
<entry>D2847A</entry>
<entry>21" P1110</entry>
<entry>50-180</entry>
<entry>29-121</entry>
<entry>300</entry>
&celbof;
&celbof;
&celoui;
</row>
<row>
<entry>A4033A</entry>
<entry>21"</entry>
<entry>50-120</entry>
<entry>30-80</entry>
&celbof;
&celbof;
&celbof;
&celoui;
</row>
<row>
<entry>A1295A</entry>
<entry>24" Wide Aspect</entry>
<entry>50-160</entry>
<entry>30-96</entry>
&celbof;
&celbof;
&celbof;
&celnon;
</row>
<row>
<entry>D5061A</entry>
<entry>15,1" LCD HP</entry>
&celbof;
&celbof;
&celna;
&celbof;
&celbof;
&celnon;
</row>
<row>
<entry>D5065A</entry>
<entry>18,1" LCD HP L1800</entry>
<entry>56-85</entry>
<entry>30-80</entry>
&celna;
<entry>640x350, 640x480, 720x400, 800x600, 832x624, 1024x768, 1152x870, 1152x900, 1280x1024</entry>
<entry>70, 60-75-85, 70, 60-75-85, 75, 60-75-85, 75, 66, 60-75</entry>
&celoui;
</row>
</tbody>
</Tgroup>
</Table>
</sect2>
<sect2>
<title>
PA-Risc based computer range
</title>
<para>
The PA-Risc range is achitectured around a processor designed and realised by HP. First versions were produced in 1987. Currently the versions are named
PA-8000 (8200, 8500, ...).</para>
<para>
HP has announced at the begining of 1999 its intention to contribute to the port of Linux on its PA-Risc architecture. This port is a native one, which is different from a preceding project which used MkLinux on machines based on PA-7200.
The work is currently done with
<ulink url="http://www.thepuffingroup.com">The Puffin Group</ulink>
and more precise informations on the status may be found on their
<ulink url="http://www.thepuffingroup.com/parisc">Web site</ulink>.
For the moment the work on the boot process is improved, a shell is launched... which dies rapidly :-)
</para>
<para>
The first machine concerned by the port is the A Class server. Tests are also done on 712 and 715. Other people begin also to work on PA-2.0 machines.
</para>
<para>
There is on the other side for these machines a Linux project based on the MkLinux micro-kernel. This project as developped within OSF.
The web site mentionning informations is at
<urlsgml>http://www.gr.opengroup.org/mklinux/hppa/mkpa-rel.html</urlsgml>.
</para>
</sect2>
<sect2>
<title>
The IA-64 range
</title>
<para>
HP is developping in collaboration with Intel a new generation of 64 bits processors called IA-64. The first processor of this new generation, called Itanium, should be there during 2000.
The initial port of Linux on IA-64 was published the 2nd of february, 2000 and the sources of the project are available through
<urlsgml>ftp://ftp.kernel.org/pub/linux/kernel/ia64</urlsgml>.
More informations on this topic may be found on this page of the HP labs :
<!--<urlsgml>http://dtf.external.hp.com/dtf/swdev/1999/08/feature1_a.html</urlsgml>.-->
<urlsgml>http://devresource.hp.com/devresource/Topics/IA64/IA64.html</urlsgml>
or on the reference site
<urlsgml>http://www.linuxia64.org</urlsgml>
</para>
</sect2>
<!--
<sect2>
<title>
X Terminals
</title>
<para>
</para>
<para>
</para>
<para>
<screen>
<prompt>hpux #</prompt><userinput>cd /opt/hpxt/enware/xthome</userinput>
# Enware Home Directory
<prompt>hpux #</prompt><userinput>tar cvf ~ftp/en.tar * .??*</userinput>
# Creation of a tar archive from this software
<prompt>hpux #</prompt><userinput>ftp linux</userinput>
Connected to linux.
220 linux FTP server (Version wu-2.5.0(1) Wed Aug 25 12:50:08 EDT 1999) ready.
<prompt>Name (ftp:Root):</prompt><userinput>ftp</userinput>
331 Password required for ftp.
<prompt>Password:</prompt><userinput>(type your password here)</userinput>
230-
[...]
230-
230 User ftp logged in. Access restrictions apply.
<prompt>ftp></prompt><userinput>lcd /tmp</userinput>
Local directory now /tmp
<prompt>ftp></prompt><userinput>get en.tar</userinput>
200 PORT command successful.
150 Opening ASCII mode data connection for en.tar (57638340 bytes).
226 Transfer complete.
57638340 bytes received in [...]
<prompt>ftp></prompt><userinput>quit</userinput>
[...]
# Download of the tar archive
<prompt>linux #</prompt><userinput>mkdir -p /tftpboot</userinput>
# Creation of the target directory on the linux machine
<prompt>linux #</prompt><userinput>cd /tftpboot</userinput>
# Go there
<prompt>linux #</prompt><userinput>tar xvf /tmp/en.tar</userinput>
# untar the archive
<prompt>linux #</prompt><userinput>/usr/X11R6/bin/xfs -port 7100</userinput>
# Launch the X Font Server working on port 7100
<prompt>linux #</prompt><userinput></userinput>
# Launch the X Font Server working on port 7100
global.prof:\
:sm=255.255.255.0:\
:ds=192.168.64.5:\
:gw=192.168.64.253:\
:ht=ethernet:\
:bf=bin/C3253A:
tx1:hd=/tftpboot:tc=global.prof:ha=080009db8d1c:ip=192.168.64.157:
/ftp/pub1/linux/sunsite/system/network/boot.net/bootpd-2.4.tar.gz
</screen>
</para>
</sect2>
-->
<sect2>
<title>
The printing product range
</title>
<sect3>
<title>
General points
</title>
<para>
Printers may be connected either directly to a machine through a parallel port (generally), or a serial port, or even more recently through an USB port.
They may also be directly wired to the network, for a global access; this is done thanks to a card put in a slot of the printer, or through the connexion of the parallel port of the printer to a sharing network box.
</para>
<para>
HP provides such boxes, called JetDirect, which allow thus to share personnal printers on the network, directly, without going through a machine.
They exist for various network topologies (10 BT, 10/100 BT, Localtalk, 10B2) and offer the ability to access to the printer directly from machine which like Linux support the LPD protocol, by using a remote printer in the <filename>printcap</filename> file. The name of the queue to use is then
<filename>raw</filename>.
</para>
<para>
An example of <filename>/etc/printcap</filename> file allowing to access to a printer, equiped with such a box or card, named lj4000 on the network is given below :
</para>
<screen>
# REMOTE POSTSCRIPT 1200x1200 a4 {} PostScript Default {}
lj4000:\
:sd=/var/spool/lpd/lj4000:\
:rm=lj4000:\
:rp=raw:\
:if=/var/spool/lpd/lj4000/filter:
:mx#0:\
:sh:\
</screen>
<para>
The configuration access to the box is done either through the
WebJetAdmin<xref linkend="WebJetAdmin">
tool provided also under Linux now, or by the
<command>telnet</command>
command. The default address of these products is 192.0.0.192. To connect to them initially, you just have to add an IP alias on your network interface, typically by :
</para>
<screen>
<prompt>#</prompt><userinput>ifconfig eth0:0 192.0.0.1</userinput>
</screen>
<para>
and a route to that network (if not automatically created) typically by :
<screen>
<prompt>#</prompt><userinput>route add -net 192.0.0.0</userinput>
</screen>
</para>
<para>
The access to the equipment is thus done simply by :
<screen>
<prompt>#</prompt><userinput>telnet 192.0.0.192</userinput>
</screen>
</para>
<para>
Please pay attention to have only one such equipment on the network, at the same time, or you'll have duplicate IP addresses, which always causes problems. Note that HP manageable network equipments also use the same default address.
The reading of the
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/mini/IP-Alias.html">IP Alias mini HOWTO</ulink>
may be useful if you don't understand the previous paragraph :-).
</para>
<para>
It is of course possible to access through the network to an HP printer attached and declared directly on a Linux machine, thanks to the
<command>lpd</command>
service for the other Unix clients, through
&Samba;
for the clients of Microsoft systems (Win9x ou WinNTx) or through
<ulink url="http://www.umich.edu/~rsug/netatalk">NetAtalk</ulink>
for the MacIntosh clients.
</para>
<para>
At last,
&Samba;
offers a tool, <command>smbclient</command>,
which allows to print from a Unix/Linux machine to a printer wired directly on a Microsoft based PC, without any need to use a JetDirect system.
All the details useful to realize this operation are described in the file example
<command>smbprint</command> provided with the &Samba; package and on the page <urlsgml>http://www.medasys-digital-systems.fr/linux/samba-truc.html</urlsgml>.
</para>
<para>
Communication between a Linux machine and a printer needs also, outside a network dialog, a discussion with an exchange language between the two elements.
There are a lot of languages of that sort, such as
PCL, Postscript &ou; HPGL.
To be able to print correctly, the tool providing the datas to print has to generate code known by the printer.
Filters exist which allow to easily transform an output in one given format to another one.
Thus the
<ulink url="http://www.cs.wisc.edu/~ghost">Ghostscript</ulink>
software authorizes the transformation of Postscript source in a great variety of output formats, as indicated by its invocation in the 'Available devices' part :
</para>
<screen>
<prompt>#</prompt><userinput>gs -h</userinput>
GNU Ghostscript 5.10 (1998-12-17)
Copyright (C) 1997 Aladdin Enterprises, Menlo Park, CA. All rights reserved.
Usage: gs [switches] [file1.ps file2.ps ...]
Most frequently used switches: (you can use # in place of =)
-dNOPAUSE no pause after page | -q `quiet', fewer messages
-g&lt;width&gt;x&lt;height&gt; page size in pixels | -r&lt;res&gt; pixels/inch resolution
-sDEVICE=&lt;devname&gt; select device | -dBATCH exit after last file
-sOutputFile=&lt;file&gt; select output file: - for stdout, |command for pipe,
embed %d or %ld for page #
Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PDF
Available devices:
x11 x11alpha x11cmyk x11gray2 x11mono ap3250 imagen iwhi iwlo iwlq la50
la70 la75 la75plus lbp8 ln03 lj250 lj4dith lp2563 m8510 necp6 oce9050
r4081 sj48 st800 stcolor t4693d2 t4693d4 t4693d8 tek4696 xes deskjet
djet500 djet500c dnj650c laserjet ljetplus ljet2p ljet3 ljet3d ljet4
cdeskjet cdjcolor cdjmono cdj500 cdj550 paintjet pj pjxl pjxl300 uniprint
bj10e bj200 bjc600 bjc800 epson eps9mid eps9high epsonc ibmpro jetp3852
dfaxhigh dfaxlow faxg3 faxg32d faxg4 cp50 pcxmono pcxgray pcx16 pcx256
pcx24b pcxcmyk pbm pbmraw pgm pgmraw pgnm pgnmraw pnm pnmraw ppm ppmraw
tiffcrle tiffg3 tiffg32d tiffg4 tifflzw tiffpack tiff12nc tiff24nc psmono
psgray bit bitrgb bitcmyk pngmono pnggray png16 png256 png16m jpeg
jpeggray pdfwrite pswrite epswrite pxlmono pxlcolor nullpage
Search path:
. : /usr/share/ghostscript/5.10 : /usr/share/fonts/default/ghostscript :
/usr/share/fonts/default/Type1
For more information, see /usr/doc/ghostscript-5.10/use.txt.
Report bugs to ghost@aladdin.com; use the form in bug-form.txt.
</screen>
<para>
This represents only the output formats compiled in the program.
Other are also available.
You may find a complete list of all the printers known by this software at
<urlsgml>http://www.cs.wisc.edu/~ghost/printer.html</urlsgml>.
</para>
<para>
A list of the HP printers support may be found on the following page :
<urlsgml>http://www.picante.com/~gtaylor/pht/printer_list.cgi?make=HP&amp;format=full</urlsgml>.
</para>
<!--
Les imprimantes chez HP se r<>partissent en deux cat<61>gories de technologies : jet d'encre et laser qui sont d<>taill<6C>es ci-apr<70>s.
<sect3>La gamme imprimantes jet d'encre (DeskJet)<p>
Les imprimantes HP <20> technologie jet d'encre utilisent soit un langage de description de page propre, soit le protocole PPA, soit encore le langage Postscript.
Pour les PPA voir l'URL : http://www.httptech.com/ppa/
http://www.interactive.hp.com/cgi-bin/cspt/cds/dlvr.pl?lid=features&fid=bpd06898&pid=hpdeskjet27794
<sect3>La gamme imprimantes laser (LaserJet)<p>
<sect3>La gamme traceurs (DesignJet)<p>
<sect2>
<title>La gamme des produits r<>seaux <label id="ref192"></title>
L'ensemble des produits r<>seaux HP administrables au niveau SNMP est g<>rable depuis des machines Linux via la commande <command>telnet</command>.
Les mod<6F>les concern<72>s par cette section sont :
Les Hubs 10 BT J3134A, J3135A, J3301A, J3303A
Les Hubs 10 BT J2610B,J2611B + module de supervision J3133A
Les Switching Hubs 10 BT J3201A, J3203A, J3205A
Les Switching Hubs 10 BT J3200A, J3202A, J3204A + module de supervision J3210A
Les Hubs 10/100 BT J3288M, J3289M
Les Hubs 100VG J2415A + module de supervision J2414B
Les Switchs 10/100 BT J3175A, J3177A + module de supervision J3178A
Les Switchs 10/100 BT J3298A, J3299A, J3245A, J3100B, J4120A, J4093A, J4121A, J4110A
Les Routing Switchs 10/100 BT J4139A, J4138A + module de supervision J4141A, ou J4144A ou J4146A
Pour les mod<6F>les les plus r<>cents (tels les Switchs 4000M par exemple), il est <20>galement possible de les administrer via un navigateur compatible Java depuis sa machine Linux en le faisant pointer directement sur l'adresse de l'<27>quipement. Ceux-ci disposent en effet d'un serveur Web interne facilitant leur administration.
Il n'existe pas pour le moment de version HP TopTools pour Linux.
<sect2>La gamme des tout en un<p>
Ces produits r<>unissent plusieurs fonctions : impression (tous), num<75>risation (tous), copie (tous) et fax (certains).
<sect2>La gamme des produits de stockage<p>
<sect3>Les Produits <20> base Optique<p>
<sect4>Les lecteurs de CD-ROMs<p>
<sect4>Les graveurs de CDs<p>
Cf : http://lcdx00.wm.lc.ehu.es/~svet/hp7200.html
<sect4>Les tours de CD-ROMs/DVD-ROMs<p>
<sect4>Les librairies magn<67>to-optiques<p>
<sect3>Les Produits <20> base de Bandes<p>
<sect4>Les lecteurs Colorado<p>
<sect4>Les lecteurs SureStore<p>
<sect4>Les librairies SureStore<p>
<sect2>La gamme des produits de num<75>risation<p>
<sect3>La gamme des scanners (ScanJet)<p>
Le principal outil disponible en environnement Linux pour la gestion des scanners est <ulink url="http://www.mostang.com/sane">SANE</ulink> (Scanner Access Now Easy). Ce logiciel fournit en particulier deux outils en aval pour la gestion des scanners HP: sane-hp et sane-scsi.
Tir<EFBFBD> de la documentation de cet outil, on dispose des informations de prise en charge suivantes :
<descrip>
Model: Product id: Interface:
========== =========== ==========
ScanJet Plus C9195A HP Parallel Interface Card
ScanJet IIc C1750A 3226 SCSI
ScanJet IIcx C2500A 3332 SCSI
ScanJet IIp C1790A SCSI
ScanJet 3C C2520A 3503 SCSI
ScanJet 4C C2520A SCSI
ScanJet 6100C C2520A 3644 SCSI
ScanJet 6200C C6277A SCSI
ScanJet 6250C C6278A SCSI
ScanJet 3P C2570A 3406 SCSI
ScanJet 4P C1130A 3540 SCSI
ScanJet 5P C5110A SCSI
PhotoSmart C5100A R029, R030, R032 SCSI
</descrip>
Les scanners HP reli<6C>s au port parall<6C>le ne sont pas pris en charge.
Les scanners HP reli<6C>s au port USB ne sont pas pris en charge.
<sect3>Les autres produits de num<75>risation<p>
D'autres produits permettent de transformer des donn<6E>es analogiques en donn<6E>es num<75>riques.
<sect4>Le Digital Sender<p>
Ce produit est un num<75>riseur, capable d'envoyer le r<>sultat de la num<75>risation par courrier <20>lectronique, en attachant le document num<75>ris<69> comme pi<70>ce jointe au format PDF. Il peut donc tout <20> fait ^etre utilis<69> conjointement avec un serveur de mail (sendmail, postfix...) sous Linux (ou autre), ainsi que des clients lisants leurs messages depuis Linux, sous r<>serve qu'ils disposent d'un outil d'affichage des fichiers au format PDF tels que <ulink url="http://www.adobe.com/...">Acrobat Reader</ulink> ou <ulink url="http://www.aimnet.com/~derekn/xpdf/">xpdf</ulink>.
<sect4>Le CapShare<p>
Je n'ai pas d'informations sur ce produit et son fonctionnement dans un environnement Linux pour le moment.
<sect2>La gamme des ordinateurs de poche<p>
Ces machines ne sont pas actuellement op<6F>rationnelles en liaison avec des machines Linux.
-->
</sect3>
</sect2>
</sect1>
<sect1>
<?html-filename hp-software.html>
<title>
HP software available under Linux
</title>
<para>
This section presents rapidly some HP applications which can be used under Linux.
These are either commercial applications or freeware applications.
</para>
<sect2>
<title>
HP softwares
</title>
<variablelist>
<varlistentry><term>FireHunter</term>
<listitem>
<para>
This software targetted to the ISP manages services levels and is available for RedHat version 5.2 distributions.
<urlsgml>http://www.firehunter.com</urlsgml>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>HP Eloquence</term>
<listitem>
<para>
This software is an IDE for management applications for small business firms and is available under Linux since 1997.
A lot of distributions are supported by a third party firm to which HP has given the support.
Complementary informations exist on the site
<urlsgml>http://www.hp-eloquence.com</urlsgml>.
</para>
</listitem>
</varlistentry>
<varlistentry id="WebJetAdmin"><term>HP WebJetAdmin</term>
<listitem>
<para>
This software allows to manage HP network printers through the installation of a service on a Linux server, and is accessible from any browser running on any client machine.
HP has announced the availability of this product in its 5.1 version in February 1999.
You may download it at
<urlsgml>http://www.hp.com/go/webjetadmin</urlsgml>.
</para>
<para>
An RPM version is also available at
<urlsgml>ftp://ftp.medasys-digital-systems.fr/pub/linux/mds/redhat/RPMS/i386/hpwebjet-5.6-1.i386.rpm</urlsgml>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>HP WebQoS</term>
<listitem>
<para>
This software allows to manage Internet Quality of Service by stabilizing performances during high loads, by optimizing used resources, and by managing priorities at applications and users levels.
HP has announced the availability of this product during summer 1999.
Complementary informations exist on the site
<urlsgml>http://www.hp.com/go/webqos</urlsgml>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>HP OpenView</term>
<listitem>
<para>
This software is a complete network management platform.
An NNM (Network Node Manager) has been announced, as well as ITO.
An Omniback client is available for Redhat 5.2 distributions
(Cf <urlsgml>http://www.hp.com/storage/event/openview_hl.html</urlsgml>).
</para>
</listitem>
</varlistentry>
<varlistentry><term>HP OpenMail</term>
<listitem>
<para>
A version of this mail and work group management tool is available since the first of september, 1999. Informations concerning it are available on the page :
<urlsgml>http://www.ice.hp.com/cyc/om/00/cysearch.cgi?pattern=100-1417|100-1408|100-1333|100-0100</urlsgml>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>HP E-Speak</term>
<listitem>
<para>
E-Speak, the open software platform for creating, composing, mediating, managing, and accessing Internet-based e-services. E-speak allows a resource (computing device, application, or data content) to be virtualized and re-deployed as an Internet-based e-service. All of the informations concerning it are available on the page :
<urlsgml>http://www.e-speak.hp.com/</urlsgml>.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2>
<title>
Third party softwares linked to HP
</title>
<variablelist>
<varlistentry><term>GNUPro</term>
<listitem>
<para>
HP &et; <ulink url="http://www.cygnus.com">Cygnus Solutions</ulink>
have announced the 8th of March, 1999 a partnership to provide the GNUPro tools on all the HP machines, including Linux.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>
<sect1>
<?html-filename hp-solutions.html>
<title>
Support of HP solutions under Linux
</title>
<para>
HP
proposes since May 1999 a
<ulink url="http://www.hp.com/ssg/linux">worldwide support offer</ulink>
on Linux. It's detailed on the page
<urlsgml>http://www.hp.com/pressrel/apr99/20apr99a.htm</urlsgml>.
This offer includes up to the possibility to answer 24x7, in a delay of 2 hours after taking the call.
The reference of this product is : HP LNXIA32A
</para>
<para>
Third party firms also propose Linux and free software support on HP platforms :
</para>
<variablelist>
<varlistentry><term>&Medasys;</term>
<listitem>
<para>
Contact : C<>dric Letailleur <email>Cedric.Letailleur@medasys-digital-systems.fr</email>
</para>
</listitem>
</varlistentry>
<varlistentry><term><ulink url="http://www.alcove.fr">Alcove</ulink></term>
<listitem>
<para>
Contact : Lucien Petit <email>lucien.petit@alcove.fr</email>
</para>
</listitem>
</varlistentry>
<!--
<varlistentry><term><ulink url="http://www.xxx.fr">xxx</ulink></term>
<listitem>
<para>
</para>
</listitem>
</varlistentry>
-->
</variablelist>
</sect1>
<sect1>
<?html-filename hp-training.html>
<title>
Training on HP Linux solutions
</title>
<para>
HP proposes since June 1999 a worldwide training offer on Linux. It's detailed on the page
<urlsgml>http://education.hp.com/curr-linux.htm</urlsgml>.
The detail of all the training courses for France is available at :
<urlsgml>http://www.france.hp.com/formation/f_linux_00.html</urlsgml>.
</para>
</sect1>
</chapter>
<chapter id="Sizing">
<?html-filename sizing.html>
<title>
Solutions and Sizing
</title>
<para>
This chapter proposes an help for sizing NetServers under Linux, depending on the different kinds of use.
</para>
<para>
You have to consider that exercise as a bit perilous.
Indeed, only the reality allows to test such previsions.
Nevertheless, using the experience acquired by deploying solutions in the past, we can give some useful rules.
</para>
<para>
We may apply a certain number of rules valid for the sizing of classical Unix servers, considering that CISC systems (the majority in Linux environment) need 2.5 less times resources in memory than RISC systems, due to the fact that binaries used are smaller (Intel platforms are for the moment 32 bits architectures). This has also influences on disk and swap space.
</para>
<para>
It's obvious you have to consider, whatever the system, bottlenecks of the solution put in place, because they will determine the weakest link in the chain.
</para>
<para>
You have to look particularly at the following points :
</para>
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
The number and the speed of disks (the I/O rate of 10.000 rpm disks may go up to 15 MB/s),
</para>
</listitem>
<listitem>
<para>
The number and the speed of SCSI controlers (the I/O rate of Ultra2 LVD of the LC2000 - LH3/4/3000/6000 may go up to 80 MB/s),
</para>
</listitem>
<listitem>
<para>
The addition of a supplementary SCSI card supported, when adding slow peripherals (DAT, DLT, CD writer ...) in order to avoid that the controler slow down in compatible mode, and that I/O performanes drop significantly.
</para>
</listitem>
</ItemizedList>
<para>
You have also to be suspicious of the extensible functions of machines.
Indeed, it's often preferable for a customer to add a new server, rather than to augment the capacities of the one in place.
The first reason is a financial one, on one side, because the costs of add-ons on an already old system may be near those of a new system, whose prices are becoming cheaper and cheaper. And the same for maintenance.
On the other hand, technically, it could be more interesting to benefit from the latest technologies to obtain a machine more equilibrate and powerful.
For example, when Ultra2 LVD was introduced, it was more interesting to buy a new server to benefit from the 80 MB/s SCSI bus speed, rather than to update a server which had 40 MB/s Ultra Wide SCSI.
This implies that it's interesting to size correctly the server, from the begining, for the whole forseeable period of life of its use (typically 3 years nowadays).
</para>
<para>
In the same kind of ideas, you have to examine closely the choice between a bi-processors and two mono-processor machines. 2 different systems imply 2 disk controlers, 2 disks set, 2 separate RAM busses thus best performances, but more administration.
On the other hand, a unique system renders it easier, allows for a quicker communication between processors, which could be necessary for certain applications, but makes the environment more fragile (more downtime in case of an hardware problem).
In fact, there are more losses intrinsically on a multi-processors model, in communications at the system level.
This question should mainly be considered for the addition of a processor (necesseraly obsolete) on a machine
<emphasis>a posteriori</emphasis>,
rather than to add a new server.
</para>
<para>
On memory aspects, Linux can't manage today more than 2 GB in stable kernels.
But Linux takes the maximum from the memory you give to it, mainly by the constitution of a cache disk which improves greatly system performances.
You may thus oversize the quantity of RAM installed, because it's preferable to a situation where the server would be obliged to swap (which drop performances dramatically).
The minimum RAM size provided on the NetServers (64 or 128 MB) matches perfectly a normal use of a system, and doesn't need any particular addition. You have to take in account that there is no graphical environment used on production servers.
Concerning the swap, under Linux, it comes in addition to the RAM to give the complete virtual memory available for the server.
As a base rule, it's recommanded to give the same amount of swap space as the amount of RAM, to allow the system to put on disk nearly all the running processus in case of need. But the rule which exists for System V Unix (such as HP-UX) consisting of reserving twice the amount of RAM for swap isn't useful under Linux.
You may note that Linux may swap certain inactive processus to free the maximum RAM possible. So having a system whose swap is partially used isn't necesseraly a proof of lack of memory, nor lack of performances.
</para>
<para>
You'll find below recommandations depending of the type of use made by the HP NetServer under Linux.
It's possible to cumulate several functions on the same server.
You'll take care to add in that case the resources needed to give the services.
</para>
<para>
Some generic rules have to be considered :
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
We consider that the number of simultaneous users is the same as half the whole number of users on the server.
</para>
</listitem>
<listitem>
<para>
The minimal RAM size needed for a usable Linux server is 32 MB, which is less than the minimum amount of RAM available on the NetServers (64 MB).
In case you use X-Window with KDE or Gnome on this machine, you need to have 64 MB in supplement, thus 96 MB as a minimum.
</para>
</listitem>
<listitem>
<para>
The minimal disk size needed for a usable Linux server is 2 GB, which is less than the minimum amount of disk available on the NetServers (9 GB).
</para>
</listitem>
<listitem>
<para>
In case of use of Raid 1, you have to double the amount of disk space useful to obtain the disk space needed. In case of use of Raid 5, you need to add 1 disk to obtain the disk space needed.
</para>
</listitem>
<listitem>
<para>
Except in particular cases (computing server), the amount of swap is the same as the amount of RAM.
</para>
</listitem>
<listitem>
<para>
The minimal processor needed for a usable Linux server is a Pentium 133, which is less than the minimum processor available on the NetServers (Pentium II 450).
</para>
</listitem>
<listitem>
<para>
Each X-Window user excuting a client on the server uses in average 2 MB.
</para>
</listitem>
<listitem>
<para>
It may be useful to add network cards on this type of machine to smooth the traffic, depending on the number of clients.
</para>
</listitem>
</ItemizedList>
</para>
<sect1><title>
Linux as file and print server
</title>
<sect2><title>
Linux as file server
</title>
<para>
The sharing service uses 2 MB of RAM, and 2 more MB per share. In case of a unique share (users space for example), it leads to a 2 MB consumption per user.
In the proposed case, we estimate that each user has 100 MB of disk space on the server, with an evolution to 200 MB 3 years later.
Processor resources used are relativeley small, an entry level model will be sufficient from that point of view.
We will priviledge the I/O speed with Ultra 2 LVD SCSI at 80 MB/s, if the budget allows it, and 10.000 RPM disks.
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of a file server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 100</entry>
<entry>312 Mo</entry>
<entry>27 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>100 - 500</entry>
<entry>1 Go</entry>
<entry>117 Go</entry>
<entry>LC2000</entry>
</row>
<row>
<entry>500 - 1000</entry>
<entry>2 Go</entry>
<entry>216 Go</entry>
<entry>LH3000</entry>
</row>
</tbody>
</Tgroup>
</Table>
</sect2>
<sect2><title>
Linux as print server
</title>
<para>
The sharing service uses 2 MB of RAM, and 2 more MB per printer shared. In case of a unique share (One printer per user typically), it leads to a 2 MB consumption per user.
In the proposed case, we estimate that each user prints simultaneously files of 5 MB in average, thus we need to have that space available on the server.
Processor resources used are relativeley small, an entry level model will be sufficient from that point of view.
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of a print server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 100</entry>
<entry>312 Mo</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>100 - 500</entry>
<entry>1 Go</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>500 - 1000</entry>
<entry>2 Go</entry>
<entry>9 Go</entry>
<entry>LC2000</entry>
</row>
</tbody>
</Tgroup>
</Table>
</sect2>
</sect1>
<sect1>
<?html-filename linux-intranet.html>
<title>
Internet/Intranet Linux server
</title>
<sect2><title>
Web Server
</title>
<para>
The Web service uses 2.5 MB of RAM, in static mode (simple HTML pages) and 5 MB of RAM in dynamic mode (HTML pages generated from per, php, ...) per user.
The disk space needed is function of the nature of the server, knowing that most of the consumption comes from images.
Processor resources used are important, thus it could be useful to consider the increase in frequency and the addition of processors, because this type of traffic could be quite well done in parallel.
We will priviledge also the I/O speed with Ultra 2 LVD SCSI at 80 MB/s, if the budget allows it, and 10.000 RPM disks.
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of a static Web server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 100</entry>
<entry>256 Mo</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>100 - 500</entry>
<entry>1 Go</entry>
<entry>9 Go</entry>
<entry>LC2000 Bi-processeur</entry>
</row>
<row>
<entry>500 - 1000</entry>
<entry>2 Go</entry>
<entry>9 Go</entry>
<entry>LH4 Quadri-processeurs</entry>
</row>
</tbody>
</Tgroup>
</Table>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of a dynamic Web server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 100</entry>
<entry>512 Mo</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>100 - 500</entry>
<entry>2 Go</entry>
<entry>9 Go</entry>
<entry>LC2000 Bi-processeur</entry>
</row>
<row>
<entry>500 - 1000</entry>
<entry>4 Go</entry>
<entry>18 Go</entry>
<entry>LH6000 Quadri-processeur</entry>
</row>
</tbody>
</Tgroup>
</Table>
</sect2>
<sect2><title>
Mail Server
</title>
<para>
Generally, this machine is used as both SMTP (sending and reception of messages) and POP server (keeper of messages and manager of client accesses).
The SMTP Mail service uses 2 MB of RAM per user.
The POP Mail service uses 2 MB of RAM per user.
The disk space needed becomes more and more important as long as attachments (images, various documents) take the greatest place in exchanges via e-mail. We consider in that case that an average mail box size is 50 MB.
Processor resources used are important, thus it could be useful to consider the increase in frequency and the addition of processors, because this type of traffic could be quite well done in parallel.
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of an e-mail server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 100</entry>
<entry>400 Mo</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>100 - 500</entry>
<entry>2 Go</entry>
<entry>27 Go</entry>
<entry>LC2000 Bi-processeur</entry>
</row>
<row>
<entry>500 - 1000</entry>
<entry>4 Go</entry>
<entry>54 Go</entry>
<entry>LH6000 Quadri-processeur</entry>
</row>
</tbody>
</Tgroup>
</Table>
</sect2>
<sect2><title>
Firewall/Proxy/Web-Cache server
</title>
<para>
Generally, this machine is both a Firewall server, a proxy (in both directions) and a cache for the Web because all requests go through it.
The Firewall service uses 1 MB of RAM.
The Proxy service uses 0.3 MB per incoming relay.
The Web cache service uses 0.5 MB per user.
The disk space needed is function of the parameters of the cache Web server. In that case, we consider 20 MB per user.
Processor resources used are important, due to the analysis of IP packets. Thus it could be useful to consider the increase in frequency.
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of a Firewall/Proxy/Web-Cache server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 100</entry>
<entry>128 Mo</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>100 - 500</entry>
<entry>512 Mo</entry>
<entry>18 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>500 - 1000</entry>
<entry>1 Go</entry>
<entry>27 Go</entry>
<entry>E60</entry>
</row>
</tbody>
</Tgroup>
</Table>
</sect2>
</sect1>
<!--
<sect1><title>
Linux comme serveur de base de donn<6E>es
</title>
</sect1>
-->
<!--
<sect1><title>
Linux comme serveur de sauvegarde
</title>
</sect1>
-->
<sect1>
<?html-filename linux-computing.html>
<title>
Linux as computing server
</title>
<para>
Generally, this machine is extremely stressed, mainly on the processor and RAM aspects.
Sometimes this is combined with intensive I/O needs.
We thus equip such a machine with high-end processors (nowadays Pentium III Xeon) with the greatest level 2 cache possible (nowadays 2 MB).
In RAM, we would tend to reach the maximum possible, thus 4 GB.
For this type of server, we should adapt the swap such as it covers all the needs in memory required by the computing codes to execute.
There is often no specific constraint on network performances, except in case of a computing cluster, in which case we may consider to equip the machines with 100 Mb/s cards with a switch between them, even with Myrinet or Gigabit products.
Typically, an LH4 2*PIII 550MHz 1 GB/2*9GB is the target of this type of server.
The choice is extremely variable depending on the nature of the computation to do.
We should underline that there are processors, such as PA-Risc, much more performant in floating point computation than today Intel processors (up to 6 times).
</para>
</sect1>
<sect1>
<?html-filename linux-desktop.html>
<title>
Linux as an office server
</title>
<para>
This kind of server is for the moment rare in the free software world. It's more frequent in Microsoft world, by association with
<ulink url="http://www.citrix.com/products/metaframe.asp">Metaframe</ulink> solutions of <ulink url="http://www.citrix.com/">Citrix</ulink>.
An office server needs 50 MB of RAM per user.
Intrinsically, this machine has no requirements in term of disk, if it's not at the same time a file server.
Processor resources used are important, thus it could be useful to consider the increase in frequency and the addition of processors, because this type of traffic could be quite well done in parallel.
</para>
<Table COLSEP="0" FRAME="all" ROWSEP="1"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Sizing of an office server</Title>
&tabsize;
<tbody>
<row>
<entry> 1 - 10</entry>
<entry>512 Mo</entry>
<entry>9 Go</entry>
<entry>E60</entry>
</row>
<row>
<entry>10 - 50</entry>
<entry>2 Go</entry>
<entry>9 Go</entry>
<entry>LH4 Bi-processeurs</entry>
</row>
<row>
<entry>50 - 100</entry>
<entry>4 Go</entry>
<entry>18 Go</entry>
<entry>LH6000 Quadri-processeurs</entry>
</row>
</tbody>
</Tgroup>
</Table>
</sect1>
</chapter>
<!--
<chapter id="Perspectives">
<title>
Perspectives
</title>
</chapter>
-->
<chapter id="FAQ">
<?html-filename faq.html>
<Title>
Frequently Asked Questions (FAQ)
</title>
<VariableList>
<varlistentry>
<term id="r2Go"><emphasis>"How to have more than 1 GB of RAM on my NetServer ?"</emphasis></term>
<listitem>
<para>
The following informations are adapted from the
<ulink url="http://humbolt.geo.uu.nl/Linux-MM/more_than_1GB.html">page</ulink> of Rik van Riel.
They concern 2.0.x as well as 2.2.x kernels.
</para>
<para>
First of all, the IA32 Intel architecture is limited by construction in its memory management to 4 GB.
Space which should be divided into virtual memory and physical memory.
Which means that if you choose to recognize more RAM, the maximum size for a program decreases.
</para>
<para>
But Linux can't manage more than 1 GB by default.
To go above that, in fact up to 2 GB today, because Linux can't manage more memory for the moment, you need to modify 2 files provided with kernel sources and recompile it.
Those 2 sources are
<filename>/usr/src/linux/include/asm-i386/page.h</filename> &et; <filename>/usr/src/linux/arch/i386/vmlinux.lds</filename>.
</para>
<para>
From 2.0.37 and 2.2.12 kernels on, the patch was integrated in the kernel and may be activated when doing a
<command>make config</command>.</para>
<para>
The maximum Ram managed in the i386 version was ported to 64 GB after 2.3.23.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis>"How to have more than 128 MB of swap on my NetServer ?"</emphasis></term>
<listitem>
<para>
Up to the version 2.8x of the util-linux package, the
<command>mkswap</command>
command could create swap partitions only up to 128 MB maximum.
You then had to create as much partitions as necessary.
Till the 2.9 version, included in standard in RedHat 6.0 and following distributions, it's possible to create directly swap partitions up to 1 GB.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis>"How to use the other procesors of my NetServer ?"</emphasis></term>
<listitem>
<para>
Multi-processing is supported by Linux operationnaly till the 2.0 version of the kernel.
For a 2.0.x kernel, you have to recompile it and set up the SMP variable in the Makefile to 1.
For a 2.2.x kernel, you have to set it up during the
<command>make config</command>.
For more details, please consult the
<ulink url="http://www.irisa.fr/prive/mentre/smp-howto">SMP-HOWTO</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis>"Is Linux Y2K compatible ?"</emphasis></term>
<listitem>
<para>
Generally, Linux is Y2K compatible.
For more informations please consult the
<ulink url="http://www.linux.org/help/beginner/year2000.html">FAQ</ulink>.
</para>
</listitem>
</varlistentry>
</variablelist>
</chapter>
<chapter id="References">
<?html-filename references.html>
<Title>
&ref;s
</title>
<para>
I already mentioned the documentation files, installed typically under the directory
<filename>/usr/src/linux/Documentation</filename>.
They are a real gold mine of useful informations.
</para>
<para>
The following FAQ (Frequently Asked Questions) are periodically posted in the group
<urlsgml>news:news.answers</urlsgml> &et; archived on FTP servers like <urlsgml>ftp://rtfm.mit.edu</urlsgml> :
</para>
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
FAQ of the group <urlsgml>news:comp.os.linux.announce</urlsgml>
</para>
</listitem>
<listitem>
<para>
FAQ of the group <urlsgml>news:comp.sys.hp.hpux</urlsgml>
</para>
</listitem>
</ItemizedList>
<para>
A lot of other Linux HOWTO contain informations useful in link with our subject :
</para>
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/SCSI-HOWTO.html">Linux SCSI HOWTO</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/CD-Writing-HOWTO.html">Linux CD-Writing HOWTO</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Hardware-HOWTO.html">Linux Hardware HOWTO</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Distribution-HOWTO.html">Linux Distribution HOWTO</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Kernel-HOWTO.html">Linux Kernel HOWTO</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Sound-HOWTO.html">Linux Sound HOWTO</ulink>
</para>
</listitem>
</ItemizedList>
<para>
The following Usenet groups cover subjects linked to HP :
</para>
<ItemizedList Mark="bullet" Spacing="Compact">
<listitem>
<para>
<urlsgml>news:comp.sys.hp.hardware</urlsgml>
</para>
</listitem>
<listitem>
<para>
<urlsgml>news:comp.sys.hp.misc</urlsgml>
</para>
</listitem>
</ItemizedList>
<para>
You may also consult the groups mentioned in
<xref linkend="service">.
</para>
<para>
On Internet, you may consult with a great benefit the following sites :
<Table COLSEP="0" FRAME="none" ROWSEP="0"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Web sites ofMedasys &et; HP</Title>
&tabref;
<tbody>
<row>
<entry>HP Linux Portal</entry>
<entry><urlsgml>http://www.hp.com/go/linux</urlsgml></entry>
</row>
<row>
<entry>HP &et; Linux</entry>
<entry><urlsgml>http://www.hp-linux.org</urlsgml></entry>
</row>
<row>
<entry>HP France Education Linux</entry>
<entry><urlsgml>http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux</urlsgml></entry>
</row>
<row>
<entry>Medasys Linux</entry>
<entry><urlsgml>http://www.medasys-digital-systems.fr/linux</urlsgml></entry>
</row>
<row>
<entry>HP Support</entry>
<entry><urlsgml>http://www.hp.com/pressrel/apr99/20apr99a.htm</urlsgml></entry>
</row>
<row>
<entry>HP HOWTO</entry>
<entry><urlsgml>http://www.medasys-digital-systems.fr/linux/HP-Howto/HP-HOWTO-EN/index.html</urlsgml></entry>
</row>
<row>
<entry>Linux Pa-Risc (Puffin Group)</entry>
<entry><urlsgml>http://thepuffingroup.com/parisc/software.html</urlsgml></entry>
</row>
<row>
<entry>Linux IA64</entry>
<entry><urlsgml>http://www.linuxia64.org</urlsgml></entry>
</row>
<row>
<entry>Linux IA64 (HP Labs)</entry>
<entry><urlsgml>http://dtf.external.hp.com/dtf/swdev/1999/08/feature1_a.html</urlsgml></entry>
</row>
<row>
<entry>HP RedHat certification</entry>
<entry><urlsgml>http://bugzilla.redhat.com/certification/cert-report.php3?mod_company=Hewlett+Packard</urlsgml></entry>
</row>
<row>
<entry>HP Utigroup</entry>
<entry><urlsgml>http://www.hputigroup.com</urlsgml></entry>
</row>
</tbody>
</Tgroup>
</Table>
<Table COLSEP="0" FRAME="none" ROWSEP="0"
SHORTENTRY="0" TOCENTRY="1" ORIENT="LAND" PGWIDE="1">
<Title>Other fundamental sites on Linux and Open Source Software</Title>
&tabref;
<tbody>
<row>
<entry>Linux Weekly News - Summary of 1998</entry>
<entry><urlsgml>http://lwn.net/1999/features/1998timeline/</urlsgml></entry>
</row>
<row>
<entry>Linux Weekly News - Summary of 1999</entry>
<entry><urlsgml>http://lwn.net/1999/features/Timeline/</urlsgml></entry>
</row>
<row>
<entry>IOS Counter</entry>
<entry><urlsgml>http://www.leb.net/hzo/ioscount/index.html</urlsgml></entry>
</row>
<row>
<entry>Comparaison MS-Windows NT Server 4.0 -- Unix</entry>
<entry><urlsgml>http://www.linux-france.com/article/these/unix-vs-nt/unix-vs-nt.html</urlsgml></entry>
</row>
<row>
<entry>Netcraft studies</entry>
<entry><urlsgml>http://www.netcraft.com/survey/</urlsgml></entry>
</row>
<row>
<entry>L'AFUL (Association)</entry>
<entry><urlsgml>http://www.aful.org</urlsgml></entry>
</row>
<row>
<entry>APRIL (Association)</entry>
<entry><urlsgml>http://www.april.org</urlsgml></entry>
</row>
<row>
<entry>Linux Center</entry>
<entry><urlsgml>http://www.linux-center.org</urlsgml></entry>
</row>
<row>
<entry>Linux France</entry>
<entry><urlsgml>http://www.linux-france.com/</urlsgml></entry>
</row>
<row>
<entry>Linux Journal</entry>
<entry><urlsgml>http://www.linuxjournal.com</urlsgml></entry>
</row>
<row>
<entry>Linux Gazette</entry>
<entry><urlsgml>http://www.linuxgazette.com/</urlsgml></entry>
</row>
<row>
<entry>Linux Magazine France</entry>
<entry><urlsgml>http://www.linuxmag-france.com/</urlsgml></entry>
</row>
<row>
<entry>Linux Start</entry>
<entry><urlsgml>http://linuxstart.com/index.html</urlsgml></entry>
</row>
<row>
<entry>Da Linux French Page</entry>
<entry><urlsgml>http://linuxfr.org/news/</urlsgml></entry>
</row>
<row>
<entry>RedHat Hardware support</entry>
<entry><urlsgml>http://www.redhat.com/cgi-bin/support</urlsgml></entry>
</row>
<row>
<entry>Source Exchange</entry>
<entry><urlsgml>http://www.sourcexchange.com/</urlsgml></entry>
</row>
<!--
<row>
<entry>FAQ on Open Source Software in french government</entry>
<entry><urlsgml>http://www.redhat.com/cgi-bin/support</urlsgml></entry>
</row>
-->
</tbody>
</Tgroup>
</Table>
<!--
Info-sheet + les auteurs
Tribune libre
Interview de Stallman
-->
</para>
</chapter>
<chapter id="contributeurs">
<?html-filename contributeurs.html>
<Title>
Contributors
</title>
<para>
I would like to thank especially all the people who contributed in any way to improve this HOWTO :
</para>
<ItemizedList>
<listitem><para>
Pierre-Antoine Angelini <email>angelini@ifsic.univ-rennes1.fr</email>
</para></listitem>
<listitem><para>
St<EFBFBD>phane Bortzmeyer <email>bortzmeyer@debian.org</email>
</para></listitem>
<listitem><para>
Jean-Bernard Chaffardon <email>Jean-Bernard_Chaffardon@hp.com</email>
</para></listitem>
<listitem><para>
Khalil Chawoshi <email>chawoshi@subatech.in2p3.fr</email>
</para></listitem>
<listitem><para>
B<EFBFBD>atrice Cornec <email>beatrice@victoria.frmug.org</email>
</para></listitem>
<listitem><para>
Fr<EFBFBD>d<EFBFBD>ric Dubuy <email>Frederic.Dubuy@medasys-digital-systems.fr</email>
</para></listitem>
<listitem><para>
Mark Eve <email>Mark_Eve@hp.com</email>
</para></listitem>
<listitem><para>
Laurent Frey <email>laurent.frey@iota.u-psud.fr</email>
</para></listitem>
<listitem><para>
Stein Roar Gj<47>en <email>stein.roar.gjoen@ks-t.no</email>
</para></listitem>
<listitem><para>
Yann Guillemot <email>Yann.Guillemot@medasys-digital-systems.fr</email>
</para></listitem>
<listitem><para>
Marc Hia Bali<6C> <email>Marc_Hia-Balie@hp.com</email>
</para></listitem>
<listitem><para>
Chris Holden <email>chris.holden@gte.net</email>
</para></listitem>
<listitem><para>
Masanari Iida <email>Masanari_Iida@hp.com</email>
</para></listitem>
<listitem><para>
Pascal Lemonnier <email>Pascal.Lemonnier@medasys-digital-systems.fr</email>
</para></listitem>
<listitem><para>
Maciej Macowicz <email>Maciej.Macowicz@epfl.ch</email>
</para></listitem>
<listitem><para>
Olivier Martinet <email>Olivier_Martinet@hp.com</email>
</para></listitem>
<listitem><para>
David Mentr<74> <email>David.Mentre@irisa.fr</email>
</para></listitem>
<listitem><para>
Andreas Nierula <email>A.Nierula@t-online.de</email>
</para></listitem>
<listitem><para>
Gilles Noisette <email>Gilles_Noisette@hp.com</email>
</para></listitem>
<listitem><para>
Harry Page <email>HARRY_PAGE@HP-NewZealand-om1.om.hp.com</email>
</para></listitem>
<listitem><para>
Alain Pascal <email>pascal@montrouge.omnes.slb.com</email>
</para></listitem>
<listitem><para>
Fons Rademakers <email>Fons.Rademakers@cern.ch</email> - his site : <urlsgml>http://hp-linux.cern.ch</urlsgml>
</para></listitem>
<listitem><para>
Dirk De Wachter<email>Dirk.DeWachter@rug.ac.be</email>
</para></listitem>
<listitem><para>
Norman Walsh<email>ndw@nwalsh.com</email>
</para></listitem>
</ItemizedList>
</chapter>
<chapter id="todo">
<?html-filename todo.html>
<Title>
Future versions
</title>
<para>
This chapter gives indications on elements which should be taken in account in future versions of this document. It should be taken more as a reminder for the author, than as an engagement of what he will really do !
</para>
<VariableList>
<varlistentry>
<term><emphasis>Version 0.89</emphasis></term>
<listitem>
<para>URLs verification in function of the language. Use of official addresses and paragraph on mirrors.</para>
<para>Report of headers and footers on following pages (PS).</para>
<para>Better management of the size of tables (PS).</para>
<para>Place of the footer (PS).</para>
<para>One line paragraph management.</para>
<para>Management of the size of papers, margins and images (PS).</para>
<para>Revision of the version number (PS and HTML).</para>
<para>Paragraph on Kayak Maxilife.</para>
<para>Paragraph on Kayak Sound</para>
<para>Paragraph on TX management</para>
<para>Rethink the copyright in front of the LDP one and becoming an official HOWTO.</para>
<para>Rework chapter 1 (put there history and new versions)</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis>Version 0.90</emphasis></term>
<listitem>
<para>Rework the cluster part</para>
<para>Paragraph on APM for portables</para>
<para>Rework the printer paragraph</para>
<para>Linux as a backup server (Arkeia)</para>
<para>Remote Assistant - Remote Control. Management</para>
<para>Glossary/Abbreviations</para>
<para>Rework the example of the vaccine :-)</para>
<para>Put the Argumementations in the TOC (HTML).</para>
<para>Avoid titles in end of page (PS).</para>
<para>Detail limitations of evolution from Unix to Linux</para>
<para>Paragraph on HP as a free software user</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis>Version 0.91</emphasis></term>
<listitem>
<para>Paragraph on network products</para>
<para>Paragraph on scanners</para>
<para>Management of the date with wml</para>
</listitem>
</varlistentry>
</VariableList>
</chapter>
</book>