このページは大阪弁化フィルタによって翻訳生成されたんですわ。

These machines are equiped with a Pentium IV processor, supported by kernels 2.2.18/2.4.0 and above. The RedHat 7.0, Mandrake 7.2 and TurboLinux 6.1 distributions, e.g., can be installed correctly on this kind of machines.

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).

Boot disk for 3Com card

Creation of a custom RedHat 5.1 Boot disk

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 :

Log as root. Go in the home directory (~root) #cd ~ Put there the 3c59x.c source module for the 3Com card #ncftp ftp://ftp.scyld.com/pub/network/3c59x.c Compile it #gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -c 3c59x.c `[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS` put the RedHat 5.1 floppy boot disk in the drive you have to copy the initrd.img file from the floppy disk #mcopy a:initrd.img /tmp then uncompress it #gzip -cd /tmp/initrd.img > /tmp/initrd.ext2 Mount the "file" filesystem thus obtained #mount -t ext2 /tmp/initrd.ext2 /mnt/floppy -o loop uncompress the modules provided #gzip -cd /mnt/floppy/modules/modules.cgz > /tmp/modules.cpio extract the modules #cd /tmp ; mkdir modules ; cd modules ; cat /tmp/modules.cpio | cpio -i Copy the new updated module for the 3Com card #cp ~/3c59x.o . recreate the compressed cpio file #ls | cpio -o | gzip -c9 > ../newmodules.cgz replace the modules by their update #cp ../newmodules.cgz /mnt/floppy/modules/modules.cgz unmount the "file" filesystem #umount /mnt/floppy compress the "file" filesystem #gzip -c9 /tmp/initrd.ext2 > /tmp/initrd.img copy it on the floppy disk #mcopy /tmp/initrd.img a:

3Com 996/Broadcom 5700 card (10/100/1000BT)

This driver is provided with latest RedHat 7.1, 7.2/Mandrake 8.0, 8.1 distributions, as kernel patches, but isn't included yet in the standard 2.4 kernel.

Boot/Driver disk for RedHat distribution

To be able to boot with a RedHat distribution (>6.1), and to have the recognition of a peripheral non supported in standard in the distribution, you need to do the following :

Download the delopment toolkit to create driver disk for the RedHat distribution at the following address: http://people.redhat.com/dledford

Install the sources of the driver in a directory and follow the instructions of the README file of the kit to create the modules necessary for the various kernel of the distributions.

Log as root. (~root) put the RedHat floppy boot disk to modify in the drive you have to copy the initrd.img file from the floppy disk #mcopy a:initrd.img /tmp then uncompress it #gzip -cd /tmp/initrd.img > /tmp/initrd.ext2 Mount the "file" filesystem thus obtained #mount -t ext2 /tmp/initrd.ext2 /mnt/floppy -o loop create a temporary directory #cd /tmp ; mkdir modules ; cd modules uncompress and extract the modules provided #gzip -cd /mnt/floppy/modules/modules.cgz | cpio -ivdum Copy the new updated module. In case you add it, remove also other useless modules of the same size. #cp ~/.../mod_devel_kit/rhxx/modules/x.y.z-iBOOT/module.o x.y.z-iBOOT Also in case you add it, copy the modules needed for the installed kernel during reboot, and adapt the files pcitable, module-info and modules.dep by using the information provided in the development kit. #cp -a ~/.../mod_devel_kit/rhxx/modules/x.y.z-i ~/.../mod_devel_kit/rhxx/modules/x.y.z-ismp . #vi /mnt/floppy/modules/pcitable /mnt/floppy/modules/module-info /mnt/floppy/modules/modules.dep recreate the compressed cpio file #find * -print -depth | cpio -ov -H crc | gzip -c9 > /mnt/floppy/modules/modules.cgz unmount the "file" filesystem #umount /mnt/floppy compress the "file" filesystem #gzip -c9 /tmp/initrd.ext2 > /tmp/initrd.img copy it on the floppy disk #mcopy /tmp/initrd.img a:

LH 4

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.

This machine can not be installed correctly with RedHat 7.1 or Mandrake 8.0 distributions.

NetRaid card

These cards are equiped with an AMI Megaraid chipset and may support the following Raid levels : 0, 1, 3, 5, 10, 30 and 50.

AMI has recently sold his Megaraid division to LSILogic and information is now available from http://www.megaraid.lsilogic.com/

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/2.2.19/2.4.16 typically - don't use 2.0.37/38).

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 floppy disk . This floppy disk should be used as input to the rawrite tool, for example. It works for systems with less than 1 GB of memory.

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.

To avoid strange messages during the boot printed by the megaraid driver, it's necessary to recompile it with the option -DHP (before kernel 2.4.2) or -DMEGA_HP_FIX (after) or even nothing now (> 2.4.13).

For the RedHat 6.1 distribution, the megaraid driver provided by the kernel does support only the first logical drive. In order to obtain the others, please recompile a 2.2 standard kernel.

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, LH3000/6000 are equiped with an integrated card doing hardware checks.

In the driver provided by AMI there is a Raid management tool megamgr, usable within Linux, and equivalent to the tool included in the software embedded on the controler. It's downloadable from http://www.ami.com/support/prodsearch.cfm?InpProdID=17

In case of problem, old versions are available there http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/107.zip, http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/1e08.zip and http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/mega115.tgz,.

Kernel patches and utility to monitor logical/physical drives on MegaRAID (NetRAID) Adapters have been made by Katsuyuki Yumoto. "This can detect physical drive failure, send E-Mail and syslog it. NetRAID-1Si/3Si, embeded NetRAID and NetRAID-1M/2M are okay to use. Don't use this for NetRAID-4M." You'll find the code at this address http://www.jpn.hp.com/biz/products/pcserver/linux/tech/megascan-20011113.tar.gz. Use with care as the versions I tried have conducted to kernel panic.

The NetRaid 1Si card isn't recognized correctly by RedHat 7.2.

NetRaid 1M/2M models

In addition to what is mentionned above, these models require a 1.14 version of the megaraid driver to work correctly. You may find a version of the sources of this driver at this address http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/ami-mr114b.tar.gz.

A driver disk for the RedHat distribution is available at the following address for the versions 6.2 and 7.0.

To use a driver disk on a RedHat 6.2 distribution, you need to boot with the latest boot disk made by RedHat. Either by remaking a CD-ROM containing it, or by using it directly. It"s available at the following address ftp://ftp.redhat.com/pub/redhat/linux/updates/6.2/en/os/images/i386/boot-20000407.img

You'll have data corruption by using these cards with the standard kernel of the RedHat 7.1 distribution. You necessaraly need this driver disk to use it correctly. This has been seen with both H.01.07 and H.01.08 firmware. Sources of the patch required to make this card work correctly with kernels 2.4.x (x < 7) are available here http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/mega115hp.tgz. The same probl鑪e is true with the Mandrake 8.0, but the 8.1 has the right driver.

NetRaid 4M card

These cards are equiped with a StrongARM Chipset and correspond to the Adaptec card AAC-3642. A driver is available at http://domsch.com/linux. The RedHat 7.0 includes in standard the driver even if that release of the kernel doesn't handle it normaly. Information are also available on the HP Navigator L.19.00.

Second IDE bus

On these machines, when the second ide bus is probed by the kernel, there is a timeout, which doesn't hurt, but is useless. To avoid it, just add to your lilo.conf the following line :

append="ide1=noprobe"

Processors

To desactivate processors on a Linux server, you need to give an option during the boot to the kernel such as :

Lilo boot: linux maxcpus=3

where the number of processors given in option is less by one of the number of processors wanted. For example, here we activate 4 processors.

HA Cluster

To use a High Availability Custer under Linux, you need to use additional software, such as :

Multimedia keyboards

Some of the PCs provided by HP are equiped with a multimedia keyboard. You may use the additional keys thanks to the HotKeys daemon (Cf: http://freshmeat.net/projects/hotkeys/)

3.2.2. The monitors range

The following table provides all information on the support for this hardware by XFree86.

Table 3-14. HP Monitors and Linux

Reference	Name	Vert. F. (Hz)	Hor. F. (kHz)	Bandwidth (MHz)	Resol.	Freq. (Hz)	Tested
D2825A, D2825S	15" HP Ultra VGA 1024	50-110	31-54	65	640x400, 640x480, 800x600, 1024x768	70, 60-72-75-85, 60-72-75-85, 60	Yes
D2826A, D2826S	15" HP 50	50-120	31-54	65	640x400, 640x480, 800x600, 1024x768	70, 60-75-85, 60-75-85, 60	Yes
D2827A	15" HP 51	50-120	31-54	???	???	???	No
D2828A	15" HP 52	50-120	30-54	65	640x400, 640x480, 800x600, 1024x768	70, 60-75-85, 60-75-85, 60	No
D8897A	15" HP 55	???	30-54	???	???	???	No
P4795A	15" HP 56	???	30-54	???	???	???	No
D2832A	15" HP M500	50-120	30-70	110	640x400, 640x480, 800x600, 1024x768, 1280x1024	70, 60-75-85, 72-75-85, 70-75-85, 60	No
D2807A	17" Ultra 1280	50-160	30-64	???	???	???	Yes
D2837A	17" HP70	50-120	30-70	110	640x400, 640x480, 800x600, 1024x768, 1280x1024	70, 75-85, 75-85, 75-85, 60	Yes
D2838A	17" HP M700	50-160	30-86	???	???	???	No
D8906A	17" HP P700	50-160	30-86	140	???	???	No
D8907A	17" HP P720	???	30-85	???	???	???	No
D2840A	17" Ergo 1280	50-150	31-92	160	512x384, 640x480, 800x600, 1024x768, 1152x864, 1280x1024, 1440x1080, 1600x1200	85, 100, 100, 100, 100, 85, 72, 60	Yes
D8901A, D8902A	17" HP71	50-120	30-60	110	640x400, 640x480, 800x600, 1024x768, 1280x1024	70, 60, 75-85, 75-85, 60	No
D8904A, D8905A	17" HP72	???	30-70	???	???	???	No
D8900A	17" HP75	50-160	30-86 (30-64 real)	150	640x400, 640x480, 800x600, 1024x768, 1280x1024	70, 60-75-85, 75-85, 75-75-85, 75	Yes
D2842A, D2842W	19" HP90	50-200	30-96	203	640x400, 640x480, 800x600, 1024x768, 1280x1024, 1600x1200	70, 75-85, 75-85, 75-85, 75-85, 75	Yes
D8910A	19" HP P910	50-150	29-107	230	640x400, 640x480, 800x600, 1024x768, 1280x1024, 1600x1200	70, 60-85, 85, 75-85, 75-85, 75-85	No
D8911A	19" HP91	???	30-96	???	???	???	No
D8912A	19" HP P920	???	30-107	???	???	???	No
A4031A	20"	48-150	30-82	???	???	???	Yes
D2846A, A4576A	21" HP P1100	50-160	30-107	???	???	???	No
D2847A	21" P1110	50-180	29-121	300	???	???	Yes
D8915A	21" P1120	???	30-121	???	???	???	No
A4819A	21" P1130	???	???	???	???	???	No
A4033A	21"	50-120	30-80	???	???	???	Yes
A1295A	24" Wide Aspect	50-160	30-96	???	???	???	No
D5061A	15,1" LCD HP	???	???	N/A	???	???	No
D5062A	15" LCD HPL1510	???	??-75	N/A	???	???	No
D5063A	15" LCD HPL1520	???	???	N/A	???	???	No
D5064A	17" LCD HPL1720	???	???	N/A	???	???	No
D5065A	18,1" LCD HP L1800	56-85	30-80	N/A	640x350, 640x480, 720x400, 800x600, 832x624, 1024x768, 1152x870, 1152x900, 1280x1024	70, 60-75-85, 70, 60-75-85, 75, 60-75-85, 75, 66, 60-75	Yes
D5069A, D5069C, D5069J, D5069L	18" LCD HPL1810	???	??-75	N/A	???	???	No
P4829A	18" LCD HPL1820	???	???	N/A	???	???	No

3.2.3. PA-Risc based computer range

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, ...).

The initiative to port Linux on the PA-RISC architecture was taken during the Atlanta Linux exhibition in October 1998. HP has announced in February 1999 its sponsorship to to this port of Linux. 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 The Puffin Group bought by Linuxcare, and more precise information on the status may be found on the official Web site. In particular, interesting starting points may be found on http://www.parisc-linux.org/faq.html and http://www.parisc-linux.org/hw.html. Consult also ESIEE site (712 on Linux/PA) which participates actively to the port : http://mkhppa1.esiee.fr/en/ The last version is 0.9.3. It supports the following systems L1000, L2000, A500, A180, B, C, J, D, R, 742, 725, 735, 755, 705, 710, 720, 730, 750, 712, 715.

This version supports 32 and 64 bits modes, SMP (1-4 way), RAM up to 16 GB, HP-UX compatibility, X-Window, KDE, Gnome, 80% of Debian packages.

Debian has accepted PA-RISC as a supported architecture for the upcoming Debian GNU/Linux 3.0 (woody) stable release. http://www.debian.org/ports/hppa/.

Thomas Marteau has written a HOWTO on the way to boot concretely a Pa-Risc suystem. It's available at http://www.linuxdoc.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html.

FAQ is also available at http://dsportal.eservices.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,276,00.html.

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 information is at http://www.gr.opengroup.org/mklinux/hppa/mkpa-rel.html. Links to more parisc ports are at http://parisc.workstations.org/.

3.2.4. The IA-64 range

HP has developed in collaboration with Intel a new generation of 64 bits processors called Itanium (IA-64). The first processor of this new generation, called Itanium, was born in September 2001. The initial port of Linux on IA-64 was published the 2nd of february, 2000 and the sources of the project are available through ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64. This is the place of the latest sources for this project. More information on this topic may be found on these pages: http://www.hp.com/products1/linux/itanium/index.html (LSO), http://devresource.hp.com/devresource/Topics/IA64/IA64.html and http://www.hpl.hp.com/techreports/index.html (HP Labs) or on the reference site http://www.linuxia64.org

HP, as a founding member of the IA-64 Linux project, works on the port of the kernel, the initial version of gcc, gas, ld and emacs. Another major contribution of HP to this project is the availability of the software development kit available at http://www.software.hp.com/ia64linux. It allows to develop applications as well as kernel code on Linux/IA32 for IA64 platforms and moreover to test them through a simulator.

You may find some useful tools for IA-64 architecture on the ftp site of the HP labs.

Debian has accepted IA-64 as a supported architecture for the upcoming Debian GNU/Linux 3.0 (woody) stable release. Cf: http://www.debian.org/ports/ia64/. The IA-64 installer CD image is now available by either HTTP or FTP from these locations: http://gluck.debian.org/ia64/cd-20010810.iso.gz and ftp://gluck.debian.org/ia64/cd-20010810.iso.gz.

MandrakeSoft has announced that its Mandrake 8.1 for IA-64 version supports perfectly HP Itanium configurations as related on http://www.mandrakesoft.com/company/press/pr?n=/pr/products/1444en=en

The following key features which are all unique to IA-64 are described by St駱hane Eranian:

IA-64/EPIC goes beyond pure VLIW. Code is portable from one implementation to another. The timing dependencies are protected by stop bits. This allow unmodified code to run with no recompilation. Of course better performance is achieved by recompilation.
Very large register set: 128 floating point, 128 general registers.
Predication: a very elegant way of removing the cost of branch in if-then-else statments.
Speculation: a elegant mechanism to hide memory access latency by allowing load instructions to be hoisted from the location where they are needed without risking unwanted faults (like NULL pointer).
Register Stack Engine: a mechanism similar to the register window found a SPARC but much more powerful and dynamic. The window size varies on demand. Take advantage of the large register set and is used on function calls.
Hardware support for software pipelined-loop: this is the most powerful construct which takes advantages of : predication, large registers. This is a renaming scheme for general, floating point or predication registers which allows one to unroll loops without incuring the code expansion seen on other architectures.
All the multmedia-type instructions are support in IA-64 mode.
IA-32 hardware emulation: possibility to run unmodified Linux/ia32 applications on Linux/ia64 (requires some OS support).
On the system level: full 64 bit address space. Hardware walker to TLB misses.
Banked registers (16 of them) to help speed up interrupt processing.

St駱hane Eranian and David Mosberger will publish begining of 2002 a book called 'Design and implementation of the Linux/ia64 kernel' (Prentice Hall)

3.2.4.1. The IA64 server range

The following tables indicate the state of Linux support by these platforms :

Table 3-15. HP IA-64 Servers and Linux

Machine	Graphic Card	Linux support	Network Card	Linux support	SCSI Card	Linux support	Sound Card	Linux support	Tested
rx4610 (A6153A, A6447A)	ATI Rage 128 AGP 8MB	Yes XFree 4.1.0^Rem. (ati)	Intel S82093A / i82559 10/100 BT	Yes driver eepro100 or e100	Qlogic Ultra3 Wide PCI	Yes driver qla1280	None	N/A	RedHat 7.0, 7.1, Mandrake 8.0, 8.1

3.2.4.2. The IA64 workstation range

The following tables indicate the state of Linux support by these platforms :

Table 3-16. HP IA-64 Workstations and Linux

Machine	Graphic Card	Linux support	Network Card	Linux support	SCSI Card	Linux support	Sound Card	Linux support	Tested
i2000 (A7202A, A7203A)	nVidia Quadro2 Pro AGP	Yes XFree 4.1.0^Rem. (nv)	Intel PRO 10/100 BT	Yes driver eepro100 or e100	Qlogic Ultra3 Wide PCI	Yes driver qla1280	Cirrus Logic CS 4281	Yes driver Alsa^Rem.	RedHat 7.1, Mandrake 8.1

3.2.4.3. Complementary information

To boot Linux on this kind of machine, you need to type in the initial environment
Verify the correspondance between logical drives and peripherals Shell>map Go to the logical drive corresponding to the CD-ROM Shell>fs1: Boot the system fs1:>eli linux Install your distribution as usual The only difference is that you need to create a so-called 'EFI' partition of type FAT32 (Id:b) of around 128 MB. This partition will be mounted as /boot/efi later After the installation, reboot and redo the initial sequence, verifying again the correspondance (which may have changed because the CD-ROM isn't available anymore, the numbers indicating the order of detection of bootable devices) Shell>map Shell>fs0: Shell>dir Verify the name of the kernel to boot fs1:>eli linux-up To automize the boot, you need to remove all options from the EFI boot except the EFI Shell and create a file in the EFI partition (/boot/efi) called startup.nsh containing: fs0: eli linux-up fs0:
(From information provided by S. Eranian. Only mistakes are mine :-)

David Mosberger reports that recent versions (7.2) of Red Hat install a GPT partition and that you must enable the following two config options for the kernel to recognize them:
CONFIG_PARTITION_ADVANCED=y CONFIG_EFI_PARTITION=y

3.2.5. X Terminals

HP proposes now NCD X terminals to replace the Envizex/Entria range.

The HP X terminal range (Entria, Envizex) is usable with a Linux server. More over, a Linux server may be a boot server for X terminals. To do it, a certain number of operations are mandatory.

We suppose we have a HP-UX machine named hpux, on which is installed Enware, a Linux server, named linux and an X Terminal with MAC address 08:00:09:db:8d:1c. The gateway on the network is at IP address 192.168.1.254, and the DNS name server at 192.168.1.1.

Commands to do are :
Enware Home Directory hpux #cd /opt/hpxt/enware/xthome Creation of a tar archive of this software hpux #tar cvf ~ftp/en.tar * .??* Download of the tar archive linux #ftp hpux Connected to hpux. 220 hpux FTP server (Version wu-2.5.0(1) Wed Aug 25 12:50:08 EDT 1999) ready. Name (ftp:Root):ftp 331 Password required for ftp. Password:(type your mail address here) 230- [...] 230- 230 User ftp logged in. Access restrictions apply. ftp>lcd /tmp Local directory now /tmp ftp>get en.tar 200 PORT command successful. 150 Opening BINARY mode data connection for en.tar (57638340 bytes). 226 Transfer complete. 57638340 bytes received in [...] ftp>quit [...] Creation of the target directory on the linux machine linux #mkdir -p /tftpboot Go there linux #cd /tftpboot untar the archive linux #tar xvf /tmp/en.tar Launch the X Font Server working on port 7100 linux #/usr/X11R6/bin/xfs -port 7100 Creation of the bootpd configuration file linux #cat >> /etc/bootptab << EOF global.prof::sm=255.255.255.0::ds=192.168.1.1::gw=192.168.1.254::ht=ethernet::bf=bin/C3253A: # Adjust to your X-terminal tx1:hd=/tftpboot:tc=global.prof:ha=080009db8d1c:ip=192.168.1.100: EOF Install bootpd say from http://rpmfind.net linux #rpm -Uvh bootp-2.4.3-7.i386.rpm Verify the existence of such a line in /etc/inetd.conf, and restart if needed the server by killall -1 inetd linux #grep bootps /etc/inetd.conf bootps dgram udp wait root /usr/sbin/tcpd bootpd Now enkoy your X terminal by booting it

For a more detailed description, as well as the software related to that operation, consult also the page http://www.cb3rob.net/~sven/xterm.

3.2.6. The printing product range

3.2.6.1. General points

Printers may be connected directly to a machine through either a parallel port (generally), or a serial port, or even (more recently) through a 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.

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 /etc/printcap file. The name of the queue to use is then raw.

An example of /etc/printcap file allowing to access to a printer, equiped with such a box or card, named lj4000 on the network is given below :

# 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:

The configuration access to the box is done either through the WebJetAdmin tool provided also under Linux now, or by the telnet 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 :

#ifconfig eth0:0 192.0.0.1

and a route to that network (if not automatically created) typically by :
#route add -net 192.0.0.0

The access to the equipment is thus done simply by :
#telnet 192.0.0.192

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 IP Alias mini HOWTO may be useful if you don't understand the previous paragraph :-).

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 lpd service for the other Unix clients, through SaMBa for the clients of Microsoft systems (Win9x ou WinNTx) or through NetAtalk for the MacIntosh clients.

At last, SaMBa offers a tool, smbclient, 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 example file of smbprint provided with the SaMBa package and on the page http://www.medasys-digital-systems.fr/linux/samba-truc.html.

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 or 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 Ghostscript software authorizes the transformation of Postscript source in a great variety of output formats, as indicated by its invocation in the 'Available devices' part :

#gs -h
GNU Ghostscript 6.51 (2001-03-28)
Copyright (C) 2001 artofcode LLC, Benicia, 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<width>x<height>  page size in pixels   | -r<res>  pixels/inch resolution
 -sDEVICE=<devname>  select device         | -dBATCH  exit after last file
 -sOutputFile=<file> select output file: - for stdout, |command for pipe,
                                         embed %d or %ld for page #
Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PDF
Available devices:
   x11 bbox x11alpha x11cmyk x11gray2 x11gray4 x11mono bmpmono bmpgray
   bmpsep1 bmpsep8 bmp16 bmp256 bmp16m bmp32b deskjet djet500 laserjet
   ljetplus ljet2p ljet3 ljet3d ljet4 ljet4d lj5mono lj5gray cdeskjet
   cdjcolor cdjmono cdj550 pj pjxl pjxl300 uniprint omni bj10e bj200 bjc600
   bjc800 faxg3 faxg32d faxg4 pcxmono pcxgray pcx16 pcx256 pcx24b pcxcmyk
   pbm pbmraw pgm pgmraw pgnm pgnmraw pnm pnmraw ppm ppmraw pkm pkmraw pksm
   pksmraw tiffcrle tiffg3 tiffg32d tiffg4 tifflzw tiffpack tiff12nc
   tiff24nc psmono psgray psrgb bit bitrgb bitcmyk pngmono pnggray png16
   png256 png16m jpeg jpeggray pdfwrite pswrite epswrite pxlmono pxlcolor
   dmprt cdj880 ap3250 appledmp atx23 atx24 atx38 bmpa16 bmpa16m bmpa256
   bmpa32b bmpamono bmpasep1 bmpasep8 ccr cdj1600 cdj500 cdj670 cdj850
   cdj890 cdj970 cfax cgm24 cgm8 cgmmono cljet5pr coslw2p coslwxl cp50
   declj250 dfaxlow dfaxhigh djet500c dl2100 dnj650c eps9high eps9mid epson
   epsonc escp fs600 hl1250 hl7x0 ibmpro imagen inferno iwhi iwlo iwlq
   jetp3852 la50 la70 la75 la75plus lbp8 lj250 lj3100sw lj4dith ln03 lp2563
   lp8000 lq850 lxm5700m m8510 mgr4 mgr8 mgrgray2 mgrgray4 mgrgray8 mgrmono
   miff24 necp6 oce9050 oki182 okiibm paintjet photoex pjetxl plan9bm sgirgb
   r4081 sj48 st800 stcolor sunhmono t4693d2 t4693d4 t4693d8 tek4696 xes
   x11cmyk2 x11cmyk4 x11cmyk8 x11rg16x x11rg32x ljet4pjl lj4dithp dj505j
   picty180 pr201 pr150 pr1000 pr1000_4 jj100 bj10v bj10vh mag16 mag256
   mj700v2c mj500c mj6000c mj8000c fmpr fmlbp ml600 lbp310 lbp320 lips2p
   bjc880j lips4 lips4v escpage lp2000 npdl md50Mono md50Eco md1xMono hpijs
   DJ630 DJ6xx DJ6xxP DJ8xx DJ9xx DJ9xxVIP AP21xx hpdj md2k md5k stp lxm3200
   lx5000 lex7000 lex5700 lex3200 lex2050 gdi epl5800 epl2050 epl2050p
   alc8500 alc2000 cljet5 cljet5c nullpage
Search path:
   . : /usr/share/ghostscript/6.51/lib : /usr/share/ghostscript/6.51/vflib :
   /usr/share/ghostscript/fonts : /usr/share/fonts/default/ghostscript :
   /usr/share/fonts/default/Type1 : /usr/share/fonts/default/amspsfnt/pfb :
   /usr/share/fonts/default/cmpsfont/pfb
For more information, see /usr/share/doc/ghostscript-6.51/Use.htm.
Report bugs to bug-gs@ghostscript.com, using the form in Bug-form.htm.

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 http://www.cs.wisc.edu/~ghost/printer.html.

A ghostscript driver for supporting pcl3 is also available at http://home.t-online.de/home/Martin.Lottermoser/pcl3.html.

A list of HP printers supported may be found on the following pages : http://www.linuxprinting.org/printer_list.cgi?make=HP and http://hp.sourceforge.net/.

HP has published in April 2001 improved drivers to support inkjet printers. Cf: http://hpinkjet.sourceforge.net/.

3.2.6.2. Control codes

Ink or laser printers may be controled through control codes. The following table gives some of them :

Table 3-17. Printer Control codes

Code	Function
ESC&l1H	Tray 2
ESC&l2H	Manual tray, sheet
ESC&l3H	Manual tray, envelope
ESC&l4H	Tray 1
ESC&l5H	Tray 3
ESC&l7H	Automatic selection
ESC&l0O	Portrait
ESC&l1O	Landscape
ESC&l5A	A4
ESC(8U	HP Roman 8
ESC(10U	IBM PC-8 (CP437)
ESC(12U	IBM PC-850 (CP850)

Other control codes for PCL3 language are given on HP's Web site for deskjet and laserjet.

HP printers are of two kind of technologies : inkjet or laserjet which are detailed below.

3.2.6.2.1. Inkjet printers range (DeskJet)

Inkjet HP printers use either an own language for page description, or the PPA protocol, or also the Postscript or PCL language.

The reference site for InkJet printer is http://hpinkjet.sourceforge.net

For PPA printers, consult also http://sourceforge.net/projects/pnm2ppa

Note that most inkjet printers are limited to a 600x600 resolution when used from Unix/Linux.

3.2.6.2.2. The InkJet range

LaserJet HP printers use PCL or Postscript page description language.

The reference site for LaserJet printer is http://hp.sourceforge.net

3.2.7. Digital imaging product range

3.2.7.1. The scanners range (ScanJet)

The main tool available in Linux environment to manage scanners is SANE (Scanner Access Now Easy). This software provides in particular a driver for HP scanner management: hpbackend.

The following table provides all information on the support for this hardware by Linux.

Table 3-18. Scanners and Linux

Reference	Scanner	Interface	Linux support	Tested
C9195A	ScanJet Plus	HP Parallel Interface Card	SANE and driver	No
C1750A	ScanJet IIc	SCSI	SANE	No
C2500A, C2507A, C2508A, C2509A	ScanJet IICX	SCSI	SANE	No
C1790A, C1797A, C1798A, C1799A	ScanJet IIP	SCSI	SANE	No
C2520A, C2527A, C2528A, C2529A	ScanJet 3C	SCSI	SANE	No
C2570A	ScanJet 3P	SCSI	SANE	No
C2520B, C2527B, C2527D, C2528B, C2529B	ScanJet 4C	SCSI	SANE	No
C1130B	ScanJet 4P	SCSI	SANE	No
C5110A, C5116A, C5117A, C5119A	ScanJet 5P	SCSI	SANE	No
C5160A, C5167A	ScanJet 5S	???	???	No
	ScanJet 2100C	driver USB	???	No
C8500A	ScanJet 2200C	Parallel Port	???	No
C7167A	ScanJet 3200C	Parallel Port	???	No
C7680A	ScanJet 3300C	USB	SANE and driver USB	No
C7727A	ScanJet 3400C	Parallel Port or USB	SANE and driver PPSCSI or driver USB	No
C6290A, C6292A, C6293A, C7297A	ScanJet 4100C, Cse, Cxi	USB	SANE and driver USB	No
C7177A	ScanJet 4200C	USB	SANE and driver USB	No
C7737A	ScanJet 4300C	Parallel Port or USB	SANE and driver PPSCSI or driver USB	No
C9877A, C9887A	ScanJet 4400C	???	???	No
C5190A, C5192A, C5193A, C5197A	ScanJet 5100C, Cse, Cxi	Parallel Port	SANE and driver PPSCSI	No
C5190A, C7192A, C7193A	ScanJet 5200C	Parallel Port or USB	SANE and driver PPSCSI or driver USB	Yes
C7697A, C8477A	ScanJet 5300C, 5370C	Parallel Port or USB	SANE and driver PPSCSI or driver USB (driver hp5300)	No
C8517A, C9857A, C9867A	ScanJet 5400C	???	???	Yes
C6260A, C6266A, C6267A, C6269A	ScanJet 6100C	SCSI	SANE	No
C6270A, C6272A, C6273A, C6274A, C6275A, C7277A, C6278A	ScanJet 6200C, Cse, Cxi, 6250C	SCSI or USB	SANE or driver USB	Yes
C7677A, C7678A, C7679A	ScanJet 6300C, Cse, Cxi, 6350C, 6390C	SCSI or USB	SANE or driver USB	Yes
C7717A, C7718A, C7719A	ScanJet 7400C	???	???	Yes
C5100A	PhotoSmart PhotoScanner	SCSI	SANE	Yes

A FAQ dedicated to HP scanners support under Linux with SANE is available at the address : http://www.kirchgessner.net/sanehpfaq.html

Some usefull adresses for USB scanners should be consulted : http://www.buzzard.org.uk/jonathan/scanners-usb.html and http://www.qbik.ch/usb/devices/search_res.php3?pattern=hp

3.2.7.2. Digital photo cameras

To use these peripherals, you have to compile SCSI support with your kernel, and turn on mass storage device in USB support. Then mount the /dev/sdxx device as usual.

The following table provides all information on the support for this hardware by Linux.

Table 3-19. Cameras and Linux

Reference	Camera	Interface	Linux support	Tested
C8890A	PhotoSmart 215	driver USB	???	No
C8452A	PhotoSmart 315	driver USB	gPhoto	Yes
C8908A	PhotoSmart 612	driver USB	???	No
C6324A	PhotoSmart 618	driver USB	gPhoto	Yes
C8913A	PhotoSmart 715	driver USB	???	No
C6326A	PhotoSmart 912	driver USB	gPhoto	Yes

3.2.7.3. The Digital Sender

This product is a scanner, able to send the result of the digitalisation through e-mail, by sending the digitalised document as an attachement in PDF format. It may so well be used with a Linux (or other) mail server (sendmail, postfix, ...), as well as with clients reading their messages under Linux, providing they have a tool to display PDF file such as Acrobat Reader or xpdf.

The Digital Sender can also send images as black and white or colour TIFF files. The black and white images work fine, however, there is a problem with the coloured TIFF files. These are sent in an obsolete format which is not supported by libtiff, which is the basis of support for the TIFF format for nearly all Linux software. This means that you cannot directly open colour TIFF images created by the Digital Sender using Linux software (e.g. The GIMP, ImageMagick).

3.2.7.4. The CapShare

THere is an application for the Window Maker window manager to manage the CapShare. More information at http://www.netjunki.org/projects/index.php

3.2.8. All-in-one range (OfficeJet)

These products gather many functions : printing (all), scanning (all), copying (all), and faxing (some).

More information from their dedicated web site : http://hpoj.sourceforge.net/suplist.shtml

3.2.9. The Storage products range

3.2.9.1. Tape based products

Most HP SCSI tape drives (DAT 1, 2, 3, 4, DLT, LTO) work with Linux. the driver file to use is /dev/st0 for the first drive, /dev/st1, for the second...

More information may be found on the certification site http://www.linuxtapecert.org/

HP provides the tapeware software with its drives, including a Linux version.

Colorado Trakker 250 and 350 are supported with ftape (>= 4.02) T1000 should also work correctly. Colorado 5GB are supported with the paride driver.

3.2.9.1.1. HP libraries

Tools to manage such drives may be found on http://mtx.sourceforge.net/ or http://www.arkeia.com/ or http://www.strusel007.de/linux/changer.html. I had the chance to test models 6x24, 418, 718, 818 with arkeia without problem.

3.2.9.2. HP SureStore Virtual Array

These systems are supported in a mixed environment Windows NT/2K, HP-UX 11.0 and Linux. They are connected through Fibre Channel controlers to the SAN. Among all FC cards supported on Linux, HP supoprts those provided by Emulex and QLogic. HP sells a Linux version of the management software for these arrays. Supported models are VA7100 (A6183A), VA7400.

3.2.9.3. HP XP Storage Systems

Here are the configurations supported by HP for these Storage Systems:
Redhat 6.0/6.1 Qlogic QLA2100F or QLA2200F with driver V2.23 Private Loop or Direct Fibre Attach No boot support XP256 has to have firmware >= 44.14.00 Mode 00 For direct attach XP512/48 has to have firmware >= 11.22.00 Mode 00 For attachment to a switch XP512/48 has to have firmware >= 12.19.00 Redhat 6.2 Emulex LP8000 with driver V4.10g Private Loop or Direct Fibre Attach No boot support For attachment to a switch use Brocade 2400/2800 with firmware >= V2.1.9f) XP512/48 has to have firmware >= 12.19.00 Mode 00

Khalid Aziz reports that there may be a problem with XP512 support of Linux due to a hole in LUN numbers. If the LUNs were numbered continuously, you would see all LUNs. Some folks in HP have written patches for this. Essentially all that is needed is to add an entry in device_list[] in scsi_scan.c for the XP512 and set the flag BLIST_SPARSELUN. The entry would look something like:
{ "HP", "XP512", "*", BLIST_SPARSELUN}
The first field is the vendor name as reported by XP512 and second field is the model name as reported by XP512. These two need to match what XP512 returns in Inquiry command, exactly.

3.3. HP software and free software

This section presents rapidly some HP applications which can be used under Linux. These are either commercial applications or freeware applications.

It proposes also links to free software available for other operating systems (HP-UX, MPE/IX).

3.3.1. HP softwares under Linux

FireHunter

This commercial software targetted to the ISP manages services levels and is available for RedHat version 5.2 distributions. http://www.firehunter.com.

HP Eloquence

This commercial 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 information exist on the site http://www.hp-eloquence.com.

HP WebJetAdmin

This freeware 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 the fisrt time in 5.1 version in February 1999. Then were released version 5.6 in December 1999, 6.0 version in June 2000, 6.1 version in August 2000, 6.5 version in October 2001. You may download the latest version at ftp://ftp.hp.com/pub/networking/software/hpwebjet_linux.selfx. All information on this product are available from the addresses : http://www.hp.com/go/webjetadmin and http://www.hp.com/pond/wja/live/manual/html/wjacomp_linux.html.

The 5.6 version in RPM format is also available at http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/hpwebjet-5.6-1.i386.rpm.

HP WebQoS

This commercial 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 information exist on the site http://www.hp.com/go/webqos.

HP OpenView

This commercial software is a complete network management platform. An NNM (Network Node Manager) has been announced, as well as ITO. NNM and ITO agents are currently available for Linux. An Omniback client is available for Redhat 5.2 distributions (Cf http://www.hp.com/storage/event/openview_hl.html).

Precision from F. Lorrain: The Omniback II (A.03.50) client run without problem under debian potato (2.2r3) and Mandrake 7.2. But on debian, you need the libnns1-compat.

HP OpenMail

A version of this commercial mail and work group management tool is available since the first of september, 1999 under Linux. Till November the 13th, 2001, the software has been taken over by Samsung SDS. Informations concerning it are available on the page : http://www.openmail.com.

HP E-Speak

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 information concerning it are available on the page : http://www.e-speak.hp.com/.

HP MC Service Guard

This commercial software allows to manage a high availability cluster of applications. HP has announced the availability of this product for the 15th of November 2001. Complementary information exist on the site http://www.unixsolutions.hp.com/products/ha/prod/ar/mcsg.html. Reference : T1521A.

Plug-in Scheduler policies for Linux

This patch enables you to write and use loadable kernel modules to change your Linux machine's scheduler policies without rebooting. It's available at http://resourcemanagement.unixsolutions.hp.com/WaRM/schedpolicy.html.

PRM for Linux

This commercial tool allows you to monitor CPU ressources on your machine by partitioning it. http://resourcemanagement.unixsolutions.hp.com/WaRM/prm_linux/index.html.

HP TopTools Agent for Linux

This freeware is a DMI agent increasing the ease of management of HP Machines under Linux. Downlaodable from http://hp-linux.org/toptools and http://www.hp.com/toptools/download/server_agents.html.

dummynet

This free software is FTP server perf measurement tool. Downloadable at ftp://ftp.cup.hp.com/dist/networking/tools/dummynet/.

netperf

This free software is a perf measurement tool for benchmarks. Downlaodable from ftp://ftp.cup.hp.com/dist/networking/benchmarks/netperf.

hp-lx (aka Trusted Linux aka Secure Linux)

This commercial software is a modified version of a RedHat distribution, containing kernel patches and daemons (GPL), as well as a set of management commands (commercial) allowing you to create jail compartments to execute applications, running so in an absolute secure environment. The software also controls file access, inter-process and network communications, ... More information on http://www.hp.com/security/products/linux/.

Chai Server

This free software is an embedded Web-based application server. More information on https://devnet.hp.com/projects/csopen/.

Jupiter/Kelvin

Kelvin is an application programming interface (API) project dedicated for the interactive visualization of large geometric models. http://www.gris.uni-tuebingen.de/~bartz/kelvin/.

Service Control Manager

This commercial software is a secure single-point of adminstration for both Linux and HP-UX multi-system environments. http://www.hp.com/products1/linux/software/scm.html.

HP AS (Bluestone)

This commercial software is a service-oriented application server. http://www.bluestone.com.

3.3.2. Third party softwares linked to HP for Linux

GNUPro: HP and Cygnus Solutions have announced the 8th of March, 1999 a partnership to provide the GNUPro tools on all the HP machines, including Linux.
Arkeia: Arkeia is a network backup solution supporting perfectly all HP storage peripherals (autoloader, libraries, ...)

3.3.3. Free softwares under HP-UX

Numerous free software for HP-UX are available at http://hpux.cs.utah.edu/. HP hosts also a certain number of free software tools for HP-UX at http://h21007.www2.hp.com/dspp/tech/tech_TechTypeListingPage_IDX/1,1704,10312,00.html

Hp proposes also tools to help porting Linux applications to HP-UX. Cf: http://devresource.hp.com/LPK/ and http://devresource.hp.com/STKL/index.html.

An open source version of hpterm may be found on http://sourceforge.net/projects/hpterm/.

KDE 2.1 s also available for HP-UX.

3.3.4. Free softwares under MPE/IX

Numerous free software for MPE/IX are available at http://jazz.external.hp.com/src

An HP700/92 terminal emulator is available at http://www.aics-research.com/qcterm/

3.4. Support of HP solutions under Linux

HP proposes since May 1999 a worldwide support offer on Linux. 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

HP proposes since 2001 a "Mission Critical support" contract for his Linux customers.

HP has also online ressources to help people using Linux with its products :

Online Linux incidents: http://hp3.m0.net/m/s.asp?H1409133998X725229
Linux training courses: http://hp3.m0.net/m/s.asp?H1409133998X725230
Linux discussion Forum: http://hp3.m0.net/m/s.asp?H1409133998X725231

>Sylvain.Berge@medasys.fr>

Atrid

Contact : Bruno Deschandelliers <B.Deschandelliers@atrid.fr>

Alcove

Contact : Lucien Petit <Lucien.Petit@alcove.fr>

Andago

Contact : <info@andago.com>

3.5. Training on HP Linux solutions

HP proposes since June 1999 a worldwide training offer on Linux. It's detailed on the page http://education.hp.com/curr-linux.htm. The detail of all the training courses for France is available at : http://www.france.hp.com/formation/f_linux_00.html.

3.6. HP as an Open Source Software user and contributor

HP doesn't make a lot of noise in the free software world, even if it is an actor and also a user for its own IT infrastructure. For example, all the incoming mail in HP goes through PostFix servers
#dig hp.com -t mx | grep MX ;; hp.com, type = MX, class = IN hp.com. 21m28s IN MX 50 cossmtp.hp.com. hp.com. 21m28s IN MX 50 palsmtp.hp.com. hp.com. 21m28s IN MX 20 postal.agilent.com. hp.com. 21m28s IN MX 10 envelope.hp.com. hp.com. 21m28s IN MX 10 letter.hp.com. hp.com. 21m28s IN MX 20 stamp.agilent.com. hp.com. 21m28s IN MX 30 cossmtpx.hp.com. hp.com. 21m28s IN MX 50 atlsmtp.hp.com. #telnet envelope.hp.com 25 Trying 192.151.10.4... Connected to envelope.hp.com. Escape character is '^]'. 220 envelope.hp.com ESMTP Postfix QUIT 221 Bye Connection closed by foreign host. #telnet letter.hp.com 25 Trying 192.151.10.3... Connected to letter.hp.com. Escape character is '^]'. 220 letter.hp.com ESMTP Postfix QUIT 221 Bye Connection closed by foreign host. #telnet postal.agilent.com 25 Trying 192.6.9.3... Connected to postal.agilent.com. Escape character is '^]'. 220 postal.agilent.com ESMTP Postfix QUIT 221 Bye Connection closed by foreign host.

Identically, for its institutional Web server, HP uses Apache as more than 15 millions of other sites.
#wget -S http://www.hp.com/ --15:09:45-- http://www.hp.com:80/ => `index.html.1' Connecting to www.hp.com:80... connected! HTTP request sent, awaiting response... 200 OK 2 Date: Fri, 05 May 2000 13:12:25 GMT 3 Server: Apache/1.3.9 (Unix) mod_fastcgi/2.2.2 [...]

Agilent (old-HP branch) uses also the free software Perl for CAD as related at http://perl.oreilly.com/news/agilent_0300.html

HP also worked on the improvement of the proxy-cache Squid , as related at http://www.hpl.hp.com/techreports/1999/HPL-1999-142.html

In another domain, HP produces also documents to help convincing to the use of Open Soure Software, as this HP Labs report available on http://lib.hpl.hp.com/techpubs/2001/HPL-2001-233.html

A lot of HP people work on open source projects. They deserve a particular notice because, as in every open source project, their tenacious and constant comportment make these projects alive. Among them:

David Mosberger and St駱hane Eranian: Port of the Linux kernel on IA-64 http://www.linuxia64.org/.
Grant Grundler, John S. Marvin and Paul Bame: Major contributor of the Linux kernel port on Pa-Risc http://www.parisc-linux.org/.
Jean Tourrilhes: Wireless Tools for Linux http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html.
John H. Oleinik and David Suffield: Projet HP imprimante jet d'encre http://hpinkjet.sourceforge.net/.
Dann Frazier: System Imager http://www.systemimager.org.
Peter Mellquist: SNMP++ http://rosegarden.external.hp.com/snmp++.

Chapter 4. Solutions and Sizing

This chapter proposes an help for sizing NetServers under Linux, depending on the different kind of use.

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.

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.

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.

You have to look particularly at the following points :

The number and the speed of disks (the I/O rate of 10.000 rpm disks may go up to 20 MB/s, and 25 for 15.000 rpm disks),
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, and latest B model up to 160 MB/s),
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 performances drop significantly.

You have also to be suspicious of the extensible functions of machines. Indeed, it's often better for a customer to add a new server, rather than to increase 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, powerful and to reuse the old one for secondary tasks (secondary DNS, ...) or to split processes from the other one. 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).

In the same kind of ideas, you have to examine closely the choice between a bi-processors and two mono-processors machines. 2 different systems imply 2 disk controlers, 2 disks set, 2 separate RAM busses thus better 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-processor model, in communications at the system level. This question should mainly be considered for the addition of a processor (necesseraly obsolete) on a machine a posteriori, rather than to add a new server.

On memory aspects, Linux can manage today up to 64 GB in stable kernels. 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 forced to swap (which drop performances dramatically). The minimum RAM size provided on the NetServers (128 ou 256 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 processes 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 processes 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.

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 at least in that case the resources needed to give the services.

Some generic rules have to be considered :

We consider that the number of simultaneous users is the same as half the whole number of users on the server.
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 (128 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.
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).
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 (up to 8 disks).
Except in particular cases (computing server), the amount of swap is the same as the amount of RAM.
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 III 933).
Each X-Window user excuting a client on the server uses in average 2 MB.
It may be useful to add network cards in this type of machine to smooth the traffic, depending on the number of clients. Using the bonding option provided by the Linux kernel may also be very useful.

You may also consult the linux performance tuning document provided by Adrian Likins

4.1. Linux as file and print server

4.1.1. Linux as file server

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 3 LVD SCSI at 160 MB/s, if the budget allows it, and 15.000 RPM disks.

Table 4-1. Sizing of a file server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	312 MB	27 GB	E800
100 - 500	1 GB	117 GB	LC2000
500 - 1000	2 GB	216 GB	LH3000

4.1.2. Linux as print server

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.

Table 4-2. Sizing of a print server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	312 MB	9 GB	E800
100 - 500	1 GB	9 GB	E800
500 - 1000	2 GB	9 GB	LC2000

4.2. Internet/Intranet Linux server

4.2.1. Web Server

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 perl, 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. With Apache 2.0 and the support of threads, it will become even more obvious. 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.

Table 4-3. Sizing of a static Web server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	256 MB	9 GB	E800
100 - 500	1 GB	9 GB	LC2000 Bi-processor
500 - 1000	2 GB	9 GB	LH6000 Quadri-processor

Table 4-4. Sizing of a dynamic Web server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	512 MB	9 GB	E800
100 - 500	2 GB	9 GB	LC2000 Bi-processor
500 - 1000	4 GB	18 GB	LH6000 Quadri-processor

4.2.2. Mail Server

Generally, this machine is used as both SMTP (sending and reception of messages) and POP/IMAP server (keeper of messages and manager of client accesses). The SMTP Mail service uses 2 MB of RAM per user. The POP/IMAP 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.

Table 4-5. Sizing of an e-mail server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	400 MB	9 GB	E800
100 - 500	2 GB	27 GB	LC2000 Bi-processor
500 - 1000	4 GB	54 GB	LH6000 Quadri-processor

4.2.3. Firewall/Proxy/Web-Cache server

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.

Table 4-6. Sizing of a Firewall/Proxy/Web-Cache server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	128 MB	9 GB	E800
100 - 500	512 MB	18 GB	E800
500 - 1000	1 GB	27 GB	E800

4.2.4. Directory server

Generally, this machine use a software like OpenLDAP to fulfill its goals. The LDAP service uses 1 MB of RAM and 10 kB of RAM per user. The disk space needed is of the same kind, so 10 kB per user. Processor resources used are moderated.

Table 4-7. Sizing of a LDAP server

Simultaneous users	RAM size	Disk size	Machine example
1 - 100	64 MB	9 GB	E800
100 - 500	64 MB	9 GB	E800
500 - 1000	128 MB	9 GB	E800

4.3. Linux as computing server

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, Dolphin or Gigabit products. Typically, a LP1000 2*PIII 1.4GHz 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). The new IA-64 Itanium family seems also to bring a better compromise for price/performances for that environment.

This is by the way not the only approach as shown by the i-cluster project. Cf: http://www.hpl.hp.com/techreports/2001/HPL-2001-206.html

4.4. Linux as an office server

This kind of server is for the moment rare in the free software world. It's more frequent in Microsoft world, by association with Metaframe solutions of Citrix. 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.

Table 4-8. Sizing of an office server

Simultaneous users	RAM size	Disk size	Machine example
1 - 10	512 MB	9 GB	E800
10 - 50	2 GB	9 GB	LC2000 Bi-processor
50 - 100	4 GB	18 GB	LH6000 Quadri-processor

Chapter 5. Frequently Asked Questions (FAQ)

5.1. "What's new in kernel 2.2 ?"
5.2. "What's new in kernel 2.4 ?"
5.3. "How to have more than 1 GB of RAM on my NetServer ?"
5.4. "How to have more than 128 MB of swap on my NetServer ?"
5.5. "How to use the other procesors of my NetServer ?"
5.6. "Is Linux Y2K compatible ?"
5.7. "How to increase the number of processes managed by the kernel ?"
5.8. "How to increase the number of loopback devices managed by the kernel ?"
5.9. "How to have files bigger than 2 GB on ext2 ?"

5.1. "What's new in kernel 2.2 ?"

Read Wonderful World of Linux 2.2 or the same in french.

5.2. "What's new in kernel 2.4 ?"

Read Wonderful World of Linux 2.4.

5.3. "How to have more than 1 GB of RAM on my NetServer ?"

The following information are adapted from the page of Rik van Riel. They concern 2.0.x as well as 2.2.x kernels, and 2.4.x.

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.

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 /usr/src/linux/include/asm-i386/page.h and /usr/src/linux/arch/i386/vmlinux.lds.

From 2.0.37 and 2.2.12 kernels on, the patch was integrated in the kernel and may be activated when doing a make {menu,x}config.

The maximum Ram managed in the i386 version was ported to 64 GB after 2.3.23.

5.4. "How to have more than 128 MB of swap on my NetServer ?"

Up to the version 2.8x of the util-linux package, the mkswap 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 2 GB and to 8 partitions.

5.5. "How to use the other procesors of my NetServer ?"

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 or 2.4.x kernel, you have to set it up during the make {menu,x}config. For more details, please consult the SMP-HOWTO.

5.6. "Is Linux Y2K compatible ?"

Generally, Linux is Y2K compatible. For more information please consult the FAQ.

5.7. "How to increase the number of processes managed by the kernel ?"

For 2.2.x kernels, you need to edit the file /usr/src/linux/include/linux/tasks.h, modify the value of the constant NR_TASKS (512 by default) and set it to a value which doesn't exceed 4092 or 4090 if APM is configured. It could be useful to set MAX_TASKS_PER_USER at the same time to an appropriate value. Then recompile the kernel as usual.

5.8. "How to increase the number of loopback devices managed by the kernel ?"

You need to edit the file /usr/src/linux/drivers/block/loop.c, For 2.2.x kernels, you need to modify the value of the constant MAXLOOP (8 by default). For 2.4.x kernels, you need to modify the value of the static int max_loop variable. Then recompile the kernel as usual.

5.9. "How to have files bigger than 2 GB on ext2 ?"

You need to have a kernel 2.4.x, glibc 2.1.3 at least and that all necessary tools have been recompiled. Look at http://www.suse.de/~aj/linux_lfs.html

Chapter 6. Customer References

Here is a list of HP/Linux references:

Amazon: Mix of HP-UX and Linux solutions as related on http://www.zdnetindia.com/techzone/linuxcentre/stories/42345.html.
Checkpoint: HP Secure OS for Linux (aka Trusted linux).
Side Effects: Port of their software Houdini on Linux.
Nothing Real: Port of their software Shake on Linux.
Boeing: Linux and HP clusters help Boeing R&D reduce costs as related on http://www.hp.com/products1/linux/infolibrary/boeing.html.
ViaWest: a hp/Linux ISP as related on http://www.hp.com/products1/linux/infolibrary/viawest.html.
Israel Aircraft Industry: a hp/Linux performance cluster user as related on http://www.hp.com/products1/linux/infolibrary/israel.html.
SpeedEra: a hp/Linux ISP as related on http://www.hp.com/products1/linux/infolibrary/speedera.html.
Dreamworks: The Shreck movie realised on HP netserver/Linux as related on http://www.zdnet.com/zdnn/stories/news/0,4586,2761566,00.html.
Cern: Performance cluster realised with HP netserver/Linux as related on http://hp-linux.cern.ch.

Chapter 7. References

I already mentioned the documentation files, installed typically under the directory /usr/src/linux/Documentation. They are a real gold mine of useful information.

The following FAQ (Frequently Asked Questions) are periodically posted in the group news:news.answers and archived on FTP servers like ftp://rtfm.mit.edu :

FAQ of the group news:comp.os.linux.announce
FAQ of the group news:comp.sys.hp.hpux

A lot of other Linux HOWTO contain information useful related to our subject :

The following Usenet groups cover subjects related to HP :

You may also consult the groups mentioned in Section 2.2.2.5.

On Internet, you may consult with a great benefit the following sites :

Table 7-1. Web sites of HP

Subject	URL
HP Linux Portal	http://www.hp.com/go/linux
HP and Linux	http://www.hp-linux.org
HP France Education Linux	http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux/educ_linux.html
HP Support	http://www.hp.com/hps/support/h_linux.htm
HP HOWTO	http://www.HyPer-Linux.org/HP-HOWTO/current/index.html
Linux Pa-Risc (Puffin Group)	http://www.parisc-linux.org
Linux Pa-Risc (ESIEE)	http://mkhppa1.esiee.fr/en/
PA-RISC/Linux Boot HOWTO	http://mkhppa1.esiee.fr/parisc-linux-boot/parisc-linux-boot/index.html
Linux and HP Labs	http://www.hpl.hp.com/research/comp_systems.html#Linux Technology
Linux IA64	http://www.linuxia64.org
Linux IA64 (HP Labs)	http://dtf.external.hp.com/dtf/swdev/1999/08/feature1_a.html
HP embedded software developer's network	http://devnet.hp.com
HP printer drivers	http://hp.sourceforge.net/
HP RedHat certification	http://bugzilla.redhat.com/certification/cert-report.php3?mod_company=Hewlett+Packard
HP Linuxcare certification	http://www.linuxcare.com/labs/certs/C1F5.epl
SAP HP Netserver certification	http://www.sap.com/solutions/technology/linux/hp-hw.htm
HP Utigroup	http://www.hputigroup.com

Table 7-2. Other fundamental sites on Linux and Open Source Software

Subject	URL
Linux Documentation Project	http://www.linuxdoc.org
Linux Weekly News - Summary of 1998	http://lwn.net/1999/features/1998timeline/
Linux Weekly News - Summary of 1999	http://lwn.net/1999/features/Timeline/
Linux Weekly News - Summary of 2000	http://lwn.net/2000/features/Timeline/
IOS Counter	http://www.leb.net/hzo/ioscount/index.html
Comparaison MS-Windows NT Server 4.0 -- Unix	http://www.linux-france.com/article/these/unix-vs-nt/unix-vs-nt.html
Netcraft studies	http://www.netcraft.com/survey/
L'AFUL (Association)	http://www.aful.org
APRIL (Association)	http://www.april.org
Linux Center	http://www.linux-center.org
Linux France	http://www.linux-france.com/
Linux Journal	http://www.linuxjournal.com
Linux Gazette	http://www.linuxgazette.com/
Linux Magazine France	http://www.linuxmag-france.com/
Linux Start	http://linuxstart.com/index.html
Da Linux French Page	http://linuxfr.org/news/
RedHat Hardware support	http://www.redhat.com/cgi-bin/support
Mandrake Hardware support for HP	http://www.linux-mandrake.com/fr/hardware.php3?F_FAMILY=all&F_MANUFACTURER=HP&F_STATUS=all&F_SEARCH=TRUE
Mobilix : Linux Mobile	http://mobilix.org/
Linmodems	http://linmodems.org/
Notebook HQ : Linux Mobile	http://www.linux-notebook.org/laptops/
Developers Servers	http://www.linuxmama.com/dev-server.html
IA-64 project leader Web site at Cern	http://sverre.home.cern.ch/sverre/SJ.html
IA-64 Intel Web site	http://developer.intel.com/design/itanium/index.htm
Medasys Linux	http://www.medasys-digital-systems.fr/linux

Chapter 8. Contributors

I would like to thank especially all the people who contributed in any way to improve this HOWTO :

Pierre-Antoine Angelini <angelini@ifsic.univ-rennes1.fr>
Khalid Aziz <Khalid_Aziz@hp.com>
Sarah Barclay <Sarah_Barclay@hp.com>
Tim Bell <bhat@trinity.unimelb.edu.au>
Jeroen ten Berge >
Nancy Blachman <nancy@blachman.org>
St駱hane Bortzmeyer <bortzmeyer@debian.org>
Brendan Burns<bburns@wso.williams.edu>
Emmanuel Carras<emmanuel_carras@hp.com>
Kevin Carson<kevin_carson@hp.com>
Jean-Bernard Chaffardon <Jean-Bernard_Chaffardon@hp.com>
Khalil Chawoshi <chawoshi@subatech.in2p3.fr>
B饌trice Cornec <beatrice@victoria.frmug.org>
S饕astien Cottalorda <sebastien.cottalorda@mageos.com>
Nug Csigas <nug@sch.bme.hu>
Philippe Depouilly <Philippe.Depouilly@math.u-bordeaux.fr> - his site : http://www.math.u-bordeaux.fr/~depouill
Ludovic Didierlaurent <ludovic_didierlaurent@hp.com>
Fr馘駻ic Dubuy <F.Dubuy@atrid.fr>
Michael Dwyer <mdwyer@alumbre-tech.com>
St駱hane Eranian <Stephane_Eranian@hp.com>
Mark Eve <Mark_Eve@hp.com>
Greg Ferguson <gferg@hoop.timonium.sgi.com>
Laurent Frey <laurent.frey@iota.u-psud.fr>
Bertrand Gambier <Bertrand.Gambier@medasys-digital-systems.fr>
Bdale Garbee <Bdale_Garbee@hp.com>
Wilson Gardiner <Wilson_Gardiner@hp.com>
Stein Roar Gj?n <stein.roar.gjoen@ks-t.no>
Grant Grundler <grundler@cup.hp.com>
J駻駑ie Guillaume <jno@sasi.fr>
Yann Guillemot <Marc_Hia-Balie@hp.com>
Jesse Don Hickson III <theme@montana.com>
Chris Holden <chris.holden@gte.net>
Keith Hopkins <keith_hopkins@hp.com>
Masanari Iida <Masanari_Iida@hp.com>
Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>
Bruce Kives <Bruce_Kives@hp.com>
Fabrice Lorrain <Fabrice.Lorrain@univ-mlv.fr>
Pascal Lemonnier <Pascal.Lemonnier@medasys.fr>
Qing Liu <qliu@club-internet.fr>
Maciej Macowicz <Maciej.Macowicz@epfl.ch>
Olivier Martinet <Olivier_Martinet@hp.com>
Mad Matt <madmatt@bits.bris.ac.uk> - his site : http://www.bits.bris.ac.uk/madmatt/laptop.shtml
Lee Mayes <Lee_Mayes@hp.com>
David.Mentre@irisa.fr>
Jacques Misselis <Jacques.Misselis@hp.com>
Oliver Neukum <520047054719-0001@t-online.de>
Andreas Nierula <A.Nierula@t-online.de>
Robert J. Niland <robert_niland@hp.com>
Gilles Noisette <Gilles_Noisette@hp.com>
Harry Page <HARRY_PAGE@HP-NewZealand-om1.om.hp.com>
Luis Pais <Luis_Pais@hp.com>
Alain Pascal <pascal@montrouge.omnes.slb.com>
David Paschal <paschal@rcsis.com>
Luis Peromarta <Luis_Peromarta@hp.com>
Daryl Poe <Daryl_Poe@hp.com>
Thomas Pornin <Thomas.Pornin@ens.fr>
Karthik Prabhakar <karthik_prabhakar@hp.com>
Fons Rademakers <Fons.Rademakers@cern.ch> - his site : http://hp-linux.cern.ch
Gallig Renaud<Gallig_Renaud@hp.com>
Valerie Rice<Valerie_Rice@hp.com>
Lane Rollins <laner@teleport.com>
Hester van Rooyen <reception@geo.co.za>
Eric Rueda <Eric_Rueda@hp.com>
Klamer Schutte <Schutte@fel.tno.nl>
Thierry Simonnet <t.simonnet@esiee.fr>
Chuck Slivkoff <charles_slivkoff@hp.com>
Junichi Shimoda <junichi_shimoda@hp.com>
Tech Support <support@ami.com>
Nicolas Thomas <Nicolas_Thomas@hp.com>
Dirk De Wachter <Dirk.DeWachter@rug.ac.be>
Norman Walsh <ndw@nwalsh.com>
Hans Witvliet <Hans.Witvliet@Alcatel.nl>
Tony White <tony@ycs.com.au>
Yuthay Yean <Yuthay.Yean@medasys.fr>

Chapter 9. Future versions

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 !

Version 0.95

Images path.

Better management of the size of tables (PS).

Place of the footer (PS).

One line paragraph management.

Management of the size of papers, margins and images (PS).

Paragraph on TX/e-vectra management

Rework the printer paragraph

Info script to pass on machines and create a new entry

Integrate LinuxCare certif

Version 0.96

URLs verification in function of the language. Use of official addresses and paragraph on mirrors.

Rework the cluster part

Paragraph on APM for mobiles computer

Linux as a backup server (Arkeia)

Remote Assistant - Remote Control. Management

Put the Argumementations in the TOC (HTML).

Avoid titles in end of page (PS).

Paragraph on network products

Version 0.97

Detail limitations of evolution from Unix to Linux

Rework the example of the vaccine :-)

Rework chapter 1 (put there history and new versions)

Glossary/Abbreviations