HP HOWTO Utilisation and Configuration Guide of HP Products under Linux Bruno Cornec Medasys Digital Systems Bruno.Cornec@medasys-digital-systems.fr Copyright 1997-2000 by Bruno Cornec This document describes the use of products available in [1]Hewlett-Packard (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. License This HOWTO is a free documentation thanks to [2]Medasys and [3]Hewlett-Packard for whom I do that job; you may redistribute and/or modify it under the terms of the [4]Diffusion License of Free Documents . This document is distributed hoping it will be useful, but without any guaranty; you're completely responsible of its use, and coulnd't complain in case it doesn't work, or even if it breaks the hardware. _________________________________________________________________ Table of Contents 1. [5]Introduction [6]Presentation [7]New versions of this document [8]Suggestions [9]Aknowledgements 2. [10]Presentation of Linux and Free Software [11]Some definitions [12]Free Software or Open Source software [13]Examples and counter-examples [14]Linux [15]Free software concepts [16]Free software philosophy [17]The choice of free software [18]Wrong ideas on free software [19]Real problems around free software [20]Linux and other operating systems [21]Linux and other proprietary Unix (HP-UX, Tru64, AIX, Solaris, Irix) [22]Linux and SCO [23]Linux and Windows NT 3. [24]Linux and HP products [25]Informations on HP products and Linux [26]General informations [27]Particular announces [28]HP hardware supported by Linux [29]Intel based computer range [30]The monitors range [31]PA-Risc based computer range [32]The IA-64 range [33]The printing product range [34]HP software available under Linux [35]HP softwares [36]Third party softwares linked to HP [37]Support of HP solutions under Linux [38]Training on HP Linux solutions 4. [39]Solutions and Sizing [40]Linux as file and print server [41]Linux as file server [42]Linux as print server [43]Internet/Intranet Linux server [44]Web Server [45]Mail Server [46]Firewall/Proxy/Web-Cache server [47]Linux as computing server [48]Linux as an office server 5. [49]Frequently Asked Questions (FAQ) 6. [50]References 7. [51]Contributors 8. [52]Future versions _________________________________________________________________ Chapter 1. Introduction Presentation This document is a guide on the use of products proposed by the hardware manufacturer [53]Hewlett-Packard (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. Opinions expressed here are those of the author, and don't commit both [54]Medasys or [55]Hewlett-Packard . 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 [56]Medasys or [57]Hewlett-Packard on these systems under Linux, as well as from myself. Neither [58]Medasys , nor [59]Hewlett-Packard , 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). _________________________________________________________________ New versions of this document New versions of this document will be announced regularly on the Usenet groups news:fr.comp.os.linux.annonces and news:comp.os.linux.annonces. They will also be updated on the various anonymous ftp sites which archive such informations, mainly ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Hypertext versions of this and other Linux HOWTO are available on many web sites, including http://metalab.unc.edu/LDP/HOWTO and http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO. Most Linux distributions on CD-ROM include the HOWTO, often under the /usr/doc, 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 http://www.medasys-digital-systems.fr/linux/HP-Howto/HP-HOWTO-EN 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. _________________________________________________________________ Suggestions 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 <[60]Bruno.Cornec@medasys-digital-systems.fr>, and I will try to incorporate them in a next revision. 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. 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 <[61]guylhem@rrremovethis.oeil.qc.ca>. _________________________________________________________________ Aknowledgements 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 news:comp.sys.hp.hpux with a [62]HTML version 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. Numerous people have contributed to this document and augmented its contents. You'll find the most complete possible list in the [63]Chapter 7. I would like to thank just now, without any particular order, those without whom this document would simply not exist : * Marc Hia Bali <[64]Marc_Hia-Balie@hp.com>, who ordered that document and accepted to make it a free documentation. * [65]Linus Torvalds, for the Linux project (without it, nothing would exist). * [66]Richard Stallman, for the GNU project (without it, nothing would exist either). * Nat Makarvitch <[67]nat@nataa.frmug.org>, For his work as translator and his advocacy conferences. * Xavier Cazin <[68]xc@itp.fr>, for his talent to convince me to use DocBook. * Eric Dumas <[69]dumas@Linux.EU.Org>, for the management of the french LDP. * Rmy Card <[70]Remy.Card@linux.org>, for ext2 and his love of electricity :-) * Ren Cougnenc, to have helped a lot of people to begin with Linux, including myself. * Dany Coffineau <[71]Dany.Coffineau@alcatel.fr>, for teachnig me Unix. * Franois Strobel <[72]Francois.Strobel@alcatel.fr>, for his peacefulness and legendary patience :-) * Frdric Dubuy <[73]Frederic.Dubuy@medasys-digital-systems.fr>, 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 ! * Alain Pascal <[74]pascal@montrouge.omnes.slb.com>, for the several tests made. * Pascal Lemonnier <[75]Pascal.Lemonnier@medasys-digital-systems.fr> typography expert who found a lot of typos. * Ralf S. Engelschall <[76]rse@engelschall.com>, who realised the [77]wml tool set, used to manage the languages of this document. * Cees de Groot <[78]cg@sgmltools.org>, who realised the [79]SGMLTools tools set, which allow to generate all the versions of this document from a single SGML source. * Norman Walsh <[80]ndw@nwalsh.com>, who realised the SGML DTD [81]DocBook. * James Clark <[82]jjc@jclark.com>, who realised the tool [83]Jade. * Cornec family<[84]cornec@victoria.frmug.org>, for his patience and his support. _________________________________________________________________ Chapter 2. Presentation of Linux and Free Software Some definitions Before going into more details in the presentation, it could be useful to give some definitions of terms and software mentionned in that HOWTO. _________________________________________________________________ Free Software or Open Source software A free software (or Open Source software) 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. 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) ... 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. [85]GNU project Web site You find there all of the informations on the GNU project, including the licenses produced (GPL and LGPL) and various discussions on free software. [86]Open Source project Web site This site proposes a new definition, a bit less restrictive, of free software - called here OpenSource Software - by well-known people. [87]FreeBSD project Web site Here are explained the advantages of the very open BSD license. _________________________________________________________________ Examples and counter-examples First of all, free software and freeware 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 "free" . A freeware is then free of charge, but not necessarily "free of sources". (As well, the shareware has nothing to do with free software). So examples of important and well-known free software are the Linux and FreeBSD operating systems, the [88]Apache Web server, the [89]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, ... _________________________________________________________________ Linux Linux is a free operating system, superset of the POSIX norm. "Linux" 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. 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 and PowerPC), Sparc, StrongArm, Mips. Without mention of the ports, operational or in process on PalmPilot, Itanium (ex-Merced), PA-Risc, Crusoe ... 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. 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). The current stable version is the version 2.2.14 (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. Numerous presentations of Linux are currently available. Among them, you should consult the one made by Michael Johnson at http://www.medasys-digital-systems.fr/mirror/linux/HOWTO/INFO-SHEET.ht ml. _________________________________________________________________ Linux technical characteristics The system offers the following technical characteristics : * Multi-tasking : executes several programs in pseudo-parallel. * Multi-users : many users acting on the same machine at the same time (without worrying on licenses). * Portable and interoperable : works on several hardware architectures. All the sources are available. Linux supports a lot of file systems, outside the native ext2 : Systme V, BSD, Sun, MS-DOS, VFAT, NTFS, Mac, HPFS, EFS, ISO9660. On the network side, it supports the following protocols TCP/IP v4 and v6, Appletalk, Netware (client and server), Lan Manager SMB (client and server), X-Window, NFS, PPP, SLIP, UUCP. * 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. * Security : protection of memory between processus: one user program can't compromise the whole system operation. * 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... _________________________________________________________________ Free software concepts 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. _________________________________________________________________ Free software philosophy 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. 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. The main ideas promoted by this movement and stated by Richard Stallman himself are : * 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. * 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 ? * 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. 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 [90]the section called The choice of free software. 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 : * [91]Linus Torvalds, conceptor of Linux. * [92]Richard Stallman, GNU project conceptor. * [93]Eric S. Raymond, writer of several and excellent articles, which inspired so many vocations. * [94]Larry Wall, author of Perl and of the patch tool, and philosopher. * Tim O'Reilly <[95]ask_tim@oreilly.com>, free software advocate and editor of several books dedicated to them. 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. 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. _________________________________________________________________ The choice of free software 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. Source code access This point is the most important of the choice, because it allows the undestanding, adaptation, correction, distribution, improvement of the software. Reliability 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. Portability 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. Universality 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. Performance 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 ([96]Apache Web Server and competitors , [97]SMB [98]SaMBa server vs Windows NT ...). Once more, there is no obligation to diffuse an application whose performances would be bad. Interoperability 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. Reactivity 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. 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. _________________________________________________________________ Marketing argumentation 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. Figure 2-1. Server operating system repartition in 1998 (IDC). [idc1998] 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 2-2. Server operating system repartition in 1999 (IDC). [idc1999] Dataquest [99]estimates on its side that Linux servers will represent, with 1.1 million of units, 14% of the servers sold in 2003. the Net itself produces marketing tools to demonstrate the superiority of free software. Two counters are regularly updated by [100]Netcraft, on web server software, and by [101]IOS Counter for the servers on Internet. Results, reproduced below, show the importance taken by [102]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 2-3. Web server software by Netcraft between 1995 and 2000. [netcraft] Figure 2-4. Repartition of Internet servers by IOS Counter in April 1999. [ioscounter] _________________________________________________________________ Financial argumentation 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. 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. 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 telnet) 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. 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. _________________________________________________________________ Technical argumentation This argumentation was already given in the previous sections. I think nevertheless that some notions may be explained with complementary informations. 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 uptime. 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. 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. 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. _________________________________________________________________ Solutions argumentation 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. 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 ( [103]Apache ), FTP server ([104]Wu-Ftpd), DNS server ([105]Bind), the E-Mail server ([106]Sendmail or [107]Postfix), the Usenet groups server([108]INN), the proxy server ([109]IPmasqadm), the firewall ([110]IP-Chains), Virtual Private Network ([111]OpenSSH, Linux kernel), the Cache server for the Web ([112]Squid) or also the Time server ([113]NTP) ... 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 [114]RFCs. 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 [115]NFS and [116]KNFS or also [117]Coda, for file sharing and of lpd for print service), Microsoft Windows type (use of [118]SaMBa , which allows also the use of local client printers) or MacIntosh type (use of [119]NetAtalk). All these software are provided in standard in a Linux distribution and don't need any modification at the client level to work. The other domains where a system such as Linux may bring solutions is the computation one, with support of [120]multi-processors, linked to the realisation of [121]clusters with multiple nodes with high-speed network interfaces (100 Mbit/s, [122]Gigabit or [123]Myrinet), those of data security with the support of HP NetRaid[124]Rem. 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 [125]HylaFAX or also as an archive/backup server with HP SureStore DAT or DLT libraries thanks to a commercial software like [126]Arkeia or at last as a database server with free solutions like [127]PostgreSQL,[128]MySQL or commercial like [129]Oracle, to speak only of these three. 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 ([130]Netscape) or textual ([131]lynx), a lot of graphical mail readers ([132]Kmail, [133]XFMail, ...) or textual ([134]mutt, [135]elm, ...). But you also have the whole panel of indispensable tools for a personal computer today as a PDF reader ([136]Acrobat Reader or [137]xpdf), image manipulation tools ([138]ImageMagick, [139]the Gimp, [140]RealPlayer tools ...), word processors ([141]LyX, [142]LaTeX, [143]SGMLTools, [144]Wordperfect, ...), commercial office suites ([145]ApplixWare, [146]StarOffice), sound management tools ([147]WavTools, [148]eplaymidi, [149]xmcd, ...), CD burning tools ([150]cdrecord, [151]BurnIT, ... with complements as [152]mkisofs, [153]cdparanoia), free and commercial emulators for various systems ([154]Wine, [155]Executor, [156]WABI, [157]DOSEmu, ...), compilers and interpretors for all the languages ([158]C, [159]C++, [160]Pascal, [161]Fortran, [162]Basic, [163]Tcl/Tk, [164]Perl, [165]Python, [166]Ada, [167]Eiffel, [168]Lisp, [169]Scheme, [170]Prolog...), including commercial versions ([171] PGI, ...), graphical environments ([172]Gnome, [173]KDE, [174]Motif, ...). 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. 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 [175]SGMLTools, [176]Jade and [177]DocBook, which allowed to generate from a single source the formats HTML, Txt, RTF, PostScript, and PDF. _________________________________________________________________ Service argumentation 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. 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 comp.os.linux.* or for the french speaking people under fr.comp.os.linux.*. 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. _________________________________________________________________ Wrong ideas on free software Advocating free software consists also to mention some generally accepted ideas concerning them and to fight them. "There is no support, no training" As seen previously, support is currently structuring itself. A firm like [178]RedHat provides today support for their solutions. Only in France, we may mention firms like [179]Medasys , [180]Atrid, [181]Alcove which assure support on free software. Likewise, always in France, training on free software may be given by [182]HP France, [183]Learning Tree, the [184]IUT de Vlizy, without mentioning generic network and Unix trainings (besides proposed also by the same organizations) which represent a fundamental base in a training course. "There is no documentation" There is a whole set of manuals, the [185]Linux Documentation Project made of FAQ (Frequently Asked Questions) and HOWTO, counting more than 300 documents around Linux, the main being [186]translated in french, 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. On the other side, the editors [187]O'Reilly and [188]SSC 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. "A free or nearly free product is a toy" 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. "Linux is difficult to install" 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. On the other hand, as before installing a server with Windows NT you have to verify its compatibilit with the [189]Hardware Compatibility List of Microsoft, for Linux it's also greatly recommended to verify the [190]Hardware HOWTO, and for HP machines to refer to this [191]page. "Free Software are not adequate for heavy tasks" 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 [192]Voila (France Telecom) or the engine [193]Deja among other prestigious references. As well, FreeBSD is used with success as the world biggest ftp server : [194]Walnut Creek CDROM server "What appeal do I have in case of problem with the editors ?" 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. _________________________________________________________________ Real problems around free software 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. 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 [195]RedHat , [196]SuSE, [197]Slackware, [198]enMandrake, [199]Turbo Linux, [200]Debian. 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. 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. 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. _________________________________________________________________ Linux and other operating systems 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. _________________________________________________________________ Linux and other proprietary Unix (HP-UX, Tru64, AIX, Solaris, Irix) 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. To be precise in the talk, we should consider manufacturers Unix solutions as split in stations and servers. 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. 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. 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. 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. _________________________________________________________________ Linux and SCO 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. _________________________________________________________________ Linux and Windows NT 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 [201]comparaison 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. 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. 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. _________________________________________________________________ Chapter 3. Linux and HP products To maintain such a chapter is an endless task :-). _________________________________________________________________ Informations on HP products and Linux General informations 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 http://www.hp.com/go/linux. In France, there is for a longer time a site on these themes, under the responsability of Jacques Misselis <[202]Jacques_Misselis@hp.com>, hosted by [203]l'Ecole Centrale de Lyon at the address http://hpwww.ec-lyon.fr/hpeduc/education. On the other side, the firm [204]Medasys , for which I work, put at disposition of the community a certain number of informations since 1997, available at http://www.medasys-digital-systems.fr/linux. This HOWTO is the result of this work. HP also realized a synthesis document (PDF format) concerning his position vis vis of Linux, the [205]White Paper HP Linux Strategy. HP is a member of [206]Linux International. _________________________________________________________________ Particular announces HP also communicates through its web site around Linux and free software. You'll find some links here. * FireHunter announce (10/06/1998) http://www.tmo.hp.com/tmo/press/English/PRTM0804813.html * Covision program announce (01/27/1999) http://www.hp.com/pressrel/jan99/27jan99b.htm * Linux support on NetServers and IA-64 announce (01/27/1999) http://www.hp.com/pressrel/jan99/27jan99.htm * PA-Risc port annouce (03/01/1999) http://www.hp.com/pressrel/mar99/01mar99e.htm * Informix HP association announce (03/02/1999) http://www.hp.com/pressrel/mar99/02mar99i.htm * Kayak Linux support (03/17/1999) http://www.hp.com/pressrel/mar99/17mar99e.htm * World Linux support announce (04/20/1999) http://www.hp.com/pressrel/apr99/20apr99a.htm * HP OpenView announces (05/17/1999) http://www.openview.hp.com/solutions/itsm/press/press.asp?docid=31 4 * Availability of Apache on HP 3000 (Summer/1999) http://www.businessservers.hp.com/falladvisor/sum99/Summer99/apach e.html * Visualize Linux support announce (06/21/1999) http://www.hp.com/pressrel/jun99/21jun99g.htm * Open Source Software commitment by HP (08/09/1999) http://internetsolutions.enterprise.hp.com/linux/news/PRelease4.ht ml * Aberdeen group analysis on HP position on free software (08/09/1999) http://internetsolutions.enterprise.hp.com/linux/news/aberdeen_whi te_paper.html * HP announces the certification of its DAT and DLT products under Linux (02/02/2000) http://www.hp.com/pressrel/feb00/02feb00c.htm * HP Brings Award-winning 3-D VISUALIZE Graphics to Linux Desktop (02/02/2000) http://internetsolutions.enterprise.hp.com/linux/feb02page.html * [207]Medasys chosen by Hewlett-Packard France Education/Research as Linux competence center http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux/educ_linux.ht ml * Hewlett-Packard France Education/Research announces commitment to Linux promotion http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux/hp_linux.html 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. _________________________________________________________________ HP hardware supported by Linux 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 2.2.14. A development kernel (version 2.3.x) is also available but doesn't offer any garantee of stability. _________________________________________________________________ Intel based computer range Page last updated the 15th of March 2000. 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. The [208]Linux Installation HOWTO 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). The [209]Linux Kernel HOWTO should be read to have details on kernel construction. I will just mention here points which are specific to HP hardware. 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. _________________________________________________________________ The desktop range (Brio, Vectra, Kayak) The following tables indicate the state of Linux support by these platforms : Table 3-1. Brio and Linux Machine Graphic Card Linux support Network Card Linux support SCSI Card Linux support Sound Card Linux support Tes-ted 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) S3 Trio 64V2 PCI Yes XFree 3.3.6[210]Rem. (SVGA) None N/A None N/A ??? ??? Yes Brio (D6810A, D6812A) ATI Rage Pro ZX AGP Yes XFree 3.3.6[211]Rem. (Mach 64) None N/A None N/A ??? ??? No Brio (D6638A, D6639A, D6640A, D6644A, D7901A, D7902A, D6645A, D6646A) Chipset BX[212]Rem. ATI Rage Pro ZX AGP Yes XFree 3.3.6[213]Rem. (Mach 64) None N/A None N/A ??? ??? No Brio (D5841A, D6516B) Matrox Millenium II PCI Yes XFree 3.3.6[214]Rem. (SVGA) None N/A None N/A ??? ??? No Brio (D6760A, D7671A, D6908A, D7930A, D7672A, D7925T, D6776A, D6769A, D6755A, D6895A, D6896A, D6897A, D7931A) Matrox Productiva G100 AGP[215]Rem. Yes XFree 3.3.6[216]Rem. (SVGA) None N/A None N/A ??? ??? No Brio BA (D7581A, D7584A, D7585A, D7587A, D7586A, D7591A, D7594A, D8411A) Sis 5595 AGP Yes XFree 3.3.6[217]Rem. in Frame Buffer mode (FBDEV)[218]Rem. None N/A None N/A Cirrus Logic CS 4614 ??? No Brio BAx (D7600A, D7603A, D7624A, D7625A, D7630A, D7610A)[219]Rem. Matrox Productiva G200 AGP Yes XFree 3.3.6[220]Rem. (SVGA) None N/A None N/A Cirrus Logic CS 4614 ??? Yes Brio BAx (D7605A)[221]Rem. Matrox Productiva G200 AGP Yes XFree 3.3.6[222]Rem. (SVGA) ??? ??? None N/A Cirrus Logic CS 4614 ??? No Brio BA400 (D8767A, D8769A, D8934A, D8935A, D8936A, D8943A, D8947A, D8952A, D8953A, D9720A, D9721A) Intel i810 AGP[223]Rem. Yes XFree 3.3.6[224]Rem. (XFCom i810) None N/A None N/A ??? ??? Yes Brio BA600 (D8773A, D8778A, D8788A, D8789A, D9070A, D9072A, D9080A, D9082A, D9085A, D9091A) Chipset BX[225]Rem. Matrox Productiva G200 AGP Yes XFree 3.3.6[226]Rem. (SVGA) None N/A None N/A Cirrus Logic CS 4614 ??? Yes Brio BA600 (D8774A, D9075A) Chipset BX[227]Rem. Matrox Productiva G200 AGP Yes XFree 3.3.6[228]Rem. (SVGA) ??? ??? None N/A Cirrus Logic CS 4614 ??? No Table 3-2. Vectra and Linux Machine Graphic Card Linux support Network Card Linux support SCSI Card Linux support Sound Card Linux support Tes-ted Vectra VE5 (D5592A, D5602A, D5603A, D5604A, D5606N, D5608A, D5612A, D5615A, D5618A, D5607A, D5617A) S3 Trio 64V2 PCI Yes XFree 3.3.6[229]Rem. (SVGA) None N/A None N/A ??? ??? Yes Vectra VE7 (D6530A, D6531A, D6533A, D6610A, D6611A, D6615A, D6616A, D6613A) ATI Rage II C AGP Yes XFree 3.3.6[230]Rem. (Mach 64) None N/A None N/A ??? ??? Yes Vectra VE7 (D6532A, D6612A, D6617A, D6618A) ATI Rage II C AGP Yes XFree 3.3.6[231]Rem. (Mach 64) 3Com 905B-TX 10/100 BT[232]Rem. Yes driver 3c59x[233]Rem. None N/A ??? ??? Yes Vectra VE8 (D6550A, D6560A, D6570A, D6554A, D6584A, D6540A, D6541A, D6544A, D6543A, D6578A, D6573A, D6574A, D6580A,D6581A, D6584A, D6583A, D6593A, D6597A, D6598A) Chipset BX[234]Rem. Matrox Productiva G100 AGP[235]Rem. Yes XFree 3.3.6[236]Rem. (SVGA) None N/A None N/A ??? ??? Yes Vectra VE8 (D6552N, D6562N, D6565N, D6542A, D6572A, D6575A, D6582A, D6595A, D6582A, D6585N, D6599A) Chipset BX[237]Rem. Matrox Productiva G100 AGP[238]Rem. Yes XFree 3.3.6[239]Rem. (SVGA) 3Com 905B-TX 10/100 BT[240]Rem. Yes driver 3c59x[241]Rem. None N/A ??? ??? Yes Vectra VEi7 (D8121A, D8123A, D8124A, D8126A, D8128A, D8129A, D8131A, D8133A, D8134A, D8136A, D8138A, D8139A, D8141A, D8143A, D8144A, D8145A, D8148A) Sis 5595 AGP Yes XFree 3.3.6[242]Rem. in Frame Buffer mode (FBDEV)[243]Rem. None N/A None N/A ??? ??? Yes Vectra VEi7 (D8122A, D8127N, D8132A, D8137A) Sis 5595 AGP Yes XFree 3.3.6[244]Rem. in Frame Buffer mode (FBDEV)[245]Rem. 3Com 905B-TX 10/100 BT[246]Rem. Yes driver 3c59x[247]Rem. None N/A ??? ??? No Vectra VEi8 (D8166A, D8168A, D8151A, D8153A, D8155A, D8169A, D8171A, D8173A, D8174A, D8181A, D8183A, D8184A, D8186A, D8188A, D9784A, D9786A, D9788A, D9793A) Matrox Productiva G200 AGP Yes XFree 3.3.6[248]Rem. (SVGA) None N/A None N/A ??? ??? No Vectra VEi8 (D8167N, D8152N, D8172N, D8182N, D8187N, D9787N) Matrox Productiva G200 AGP Yes XFree 3.3.6[249]Rem. (SVGA) 3Com 905B-TX 10/100 BT[250]Rem. Yes driver 3c59x[251]Rem. None N/A ??? ??? No Vectra VL5 (D4552A, D4543A, D4554A, D4555A, D4556A, D4557A, D4558A, D4559A, D4560A, D4567A, D4562A, D4563A, D4572A, D4574A, D4576A, D4579A, D4577A) S3 Trio 64V2 PCI Yes XFree 3.3.6[252]Rem. (SVGA) None N/A None N/A ??? ??? Yes Vectra VL6 Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[253]Rem. (SVGA) None N/A None N/A ??? ??? Yes Vectra VL6 Matrox Millenium II PCI Yes XFree 3.3.6[254]Rem. (SVGA) None N/A None N/A ??? ??? No Vectra VL7 (D5710A, D5711N, D5725A, D5720A, D5721N, D5731N, D5797N, D5737A, D5799N) Cirrus Logic GD 5465 AGP[255]Rem. Yes XFree 3.3.6[256]Rem. (SVGA) None N/A None N/A ??? ??? Yes Vectra VL7 (D5734N, D5729N, D5739N, D5728N, D5798N) Matrox Millenium II PCI Yes XFree 3.3.6[257]Rem. (SVGA) None N/A None N/A ??? ??? No Vectra VL7 (D5724N, D5796N) Cirrus Logic GD 5465 AGP[258]Rem. Yes XFree 3.3.6[259]Rem. (SVGA) AMD 79C971 KC 10/100 BT Yes driver pcnet32 None N/A ??? ??? No Vectra VL8 (D5880A, D5882A, D5890A, D5891A, D5893A, D5896A, D5898A, D5900A, D5902A, D6945A) Chipset BX[260]Rem. Matrox Productiva G100 AGP[261]Rem. Yes XFree 3.3.6[262]Rem. (SVGA) None N/A None N/A ??? ??? No Vectra VL8 (D5881A, D5883A, D5894A, D5888A, D5892A) Chipset BX[263]Rem. Matrox Productiva G100 AGP[264]Rem. Yes XFree 3.3.6[265]Rem. (SVGA) 3Com 905B-TX 10/100 BT[266]Rem. Yes driver 3c59x[267]Rem. None N/A ??? ??? No Vectra VL8 (D5887A) Chipset BX[268]Rem. Matrox Productiva G100 AGP[269]Rem. Yes XFree 3.3.6[270]Rem. (SVGA) 3Com 905B-TX 10/100 BT[271]Rem. Yes driver 3c59x[272]Rem. ??? ??? ??? ??? No Vectra VL8 (D6944A) Chipset BX[273]Rem. Matrox Millenium G200 AGP Yes XFree 3.3.6[274]Rem. (SVGA) None N/A None N/A ??? ??? No Vectra VL8 (D6940A, D6941A, D6942A) Chipset BX[275]Rem. Matrox Millenium G200 AGP Yes XFree 3.3.6[276]Rem. (SVGA) 3Com 905B-TX 10/100 BT[277]Rem. Yes driver 3c59x[278]Rem. None N/A ??? ??? No Vectra VL8 (D6943A) Chipset BX[279]Rem. Matrox Millenium G200 AGP Yes XFree 3.3.6[280]Rem. (SVGA) 3Com 905B-TX 10/100 BT[281]Rem. Yes driver 3c59x[282]Rem. Adaptec AIC 7880 UW PCI Yes driver aic7xxx ??? ??? Yes Vectra VLi8 (D7941A, D7943A, D7945A, D7948A, D7951A, D7953A, D7955A, D7961A, D7963A, D7965A, D7958A, D7968A, D7969A, D7973A, D7976A, D9460A, D9463A, D9467A, D9774A, D9810A) Matrox Millenium G200 AGP Yes XFree 3.3.6[283]Rem. (SVGA) None N/A None N/A Cirrus Logic CS 4614 ??? Yes 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) Matrox Millenium G200 AGP Yes XFree 3.3.6[284]Rem. (SVGA) 3Com 905C-TX 10/100 BT Yes driver 3c59x[285]Rem. None N/A Cirrus Logic CS 4614 ??? Yes Vectra VL600 (D9733A, D8643A, D9737A, D8647A) Chipset i820[286]Rem. Matrox Millenium G250 AGP ??? None N/A None N/A Cirrus Logic CS 4614 ??? No Vectra VL600 (D7543N, D8644N, D8648N, D9734N, D9738N) Chipset i820[287]Rem. Matrox Millenium G250 AGP ??? 3Com 905C-TX 10/100 BT Yes driver 3c59x[288]Rem. None N/A Cirrus Logic CS 4614 ??? No Vectra VL600 (D8635A, D8645A, D8649N, D8659N, D8669N, D8679N, D9735A, D9739N) Chipset i820[289]Rem. Matrox Millenium G400D AGP Yes XFree 3.3.6[290]Rem. (SVGA) 3Com 905C-TX 10/100 BT Yes driver 3c59x[291]Rem. None N/A Cirrus Logic CS 4614 ??? Yes Vectra XA (D3986A, D3989A, D3990A, D3991A, D3993A, D4770N, D4771N, D4773N, D4774N, D3994N, D3995N, D4776N) Matrox Millenium II PCI Yes XFree 3.3.6[292]Rem. (SVGA) AMD 79C971 KC 10/100 BT Yes driver pcnet32 None N/A ??? ??? No Vectra XA (D4777A) Matrox Millenium II PCI Yes XFree 3.3.6[293]Rem. (SVGA) AMD 79C971 KC 10/100 BT Yes driver pcnet32 Adaptec AIC 7880 UW PCI Yes driver aic7xxx ??? ??? Yes Table 3-3. Kayak and Linux Machine Graphic Card Linux support Network Card Linux support SCSI Card Linux support Sound Card Linux support Tes-ted Kayak XA (D4792A, D4795N) Cirrus Logic GD 5465 AGP[294]Rem. Yes XFree 3.3.6[295]Rem. (SVGA) None N/A None N/A ??? ??? No Kayak XA (D4807N, D4796N, D6491N, D6492N, D4806N, D4808N, D6493N) Cirrus Logic GD 5465 AGP[296]Rem. Yes XFree 3.3.6[297]Rem. (SVGA) AMD 79C971 KC 10/100 BT Yes driver pcnet32 None N/A ??? ??? Yes Kayak XA (D4798N, D6490N, D4799N, D4803N, D6494N) Cirrus Logic GD 5465 AGP[298]Rem. Yes XFree 3.3.6[299]Rem. (SVGA) AMD 79C974 KC 10/100 BT + SCSI Yes driver pcnet32 Symbios Logic 8751SP with network card Yes driver ncr-53c8xx[300]Rem. ??? ??? No Kayak XA (D4796S, D6493S) Matrox Millenium II AGP Yes XFree 3.3.6[301]Rem. (SVGA) None N/A None N/A ??? ??? No Kayak XA (D4803S) Matrox Millenium II AGP Yes XFree 3.3.6[302]Rem. (SVGA) AMD 79C974 KC 10/100 BT + SCSI Yes driver pcnet32 Symbios Logic 8751SP with network card Yes driver ncr-53c8xx[303]Rem. ??? ??? No Kayak XA (D6720N, D6721N, D6723N, D6726N, D6724N, D6730N, D6731N, D6735N, D6736N, D6738N, D6739N, D7994N) Matrox Millenium G200 AGP Yes XFree 3.3.6[304]Rem. (SVGA) None N/A None N/A ??? ??? No Kayak XA (D6722N, D6729N, D6734N) Elsa Gloria Synergy + AGP[305]Rem. Yes XFree 3.3.6[306]Rem. (3D Labs) None N/A None N/A ??? ??? Yes Kayak XA (D6725N, D6732N, D6737N, D7993N) Matrox Millenium G200 AGP Yes XFree 3.3.6[307]Rem. (SVGA) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[308]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[309]Rem. ??? ??? Yes Kayak XA (D6727N) Elsa Gloria Synergy + AGP[310]Rem. Yes XFree 3.3.6[311]Rem. (3D Labs) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[312]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[313]Rem. ??? ??? No Kayak XA (D6728N, D6733N) Accel Galaxy AGP Yes XFree 3.3.6[314]Rem. in Frame Buffer mode (FBDEV)[315]Rem. Not interesting None N/A None N/A ??? ??? No Kayak XA-s (D5751N, D5752N, D5753N, D5755N, D5754N, D5756N, D5759N) Chipset BX[316]Rem. Matrox Productiva G100 AGP[317]Rem. Yes XFree 3.3.6[318]Rem. (SVGA) None N/A None N/A ??? ??? No Kayak XA-s (D5757N, D5758N) Chipset BX[319]Rem. Matrox Productiva G100 AGP[320]Rem. Yes XFree 3.3.6[321]Rem. (SVGA) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[322]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[323]Rem. ??? ??? Yes Kayak XA-s (D5765N, D5763N, D5766N, D5769N, D7982N, D7986N, D7991N, D7987N) Chipset BX[324]Rem. Matrox Productiva G200 AGP Yes XFree 3.3.6[325]Rem. (SVGA) None N/A None N/A ??? ??? Yes Kayak XA-s (D5768N, D5767N) Chipset BX[326]Rem. Matrox Productiva G200 AGP Yes XFree 3.3.6[327]Rem. (SVGA) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[328]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[329]Rem. ??? ??? No Kayak XA-s (D5762N, D7984N, D7988N) Chipset BX[330]Rem. Elsa Gloria Synergy + AGP[331]Rem. Yes XFree 3.3.6[332]Rem. (3D Labs) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[333]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[334]Rem. ??? ??? Yes Kayak XA-s (D5764N, D7983N, D7989N) Chipset BX[335]Rem. Accel Galaxy AGP Yes XFree 3.3.6[336]Rem. in Frame Buffer mode (FBDEV)[337]Rem. Not interesting AMD 79C971 KC 10/100 BT + SCSI (D6692A)[338]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[339]Rem. ??? ??? No Kayak XA-s (D7990N) Chipset BX[340]Rem. Matrox Productiva G100 AGP[341]Rem. Yes XFree 3.3.6[342]Rem. (SVGA) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[343]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[344]Rem. ??? ??? No Kayak XA-s (D7992N) Chipset BX[345]Rem. Elsa Gloria Synergy II AGP Yes XFree 3.3.6[346]Rem. (SVGA) AMD 79C971 KC 10/100 BT + SCSI (D6692A)[347]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) Yes driver ncr-53c8xx[348]Rem. Analog Device 1816 Yes driver AD1816[349]Rem. Yes Kayak XM600 (D9531N, D9533N, D9535N, D9541N, D9549N, D9553N) Matrox Millenium G250 AGP ??? SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 None N/A Cirrus Logic CS 4614 ??? No Kayak XM600 (D8350N, D9554N, D9558N) [350]Rem. Matrox Millenium G250 AGP ??? SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 None N/A Cirrus Logic CS 4614 ??? No Kayak XM600 (D9536N, D9537N, D9538N, D9539N, D9544N, D9548N) Matrox Millenium G400D AGP Yes XFree 3.3.6[351]Rem. (SVGA) SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 None N/A Cirrus Logic CS 4614 ??? No Kayak XM600 (D9534N, D9540N, D9543N, D9546N) Elsa Gloria Synergy II AGP Yes XFree 3.3.6[352]Rem. (SVGA) SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[353]Rem. Cirrus Logic CS 4614 ??? Yes Kayak XM600 (D9545N, D8366N) 3DLabs Oxygen GVX1 AGP Yes XFree 3.3.6[354]Rem. in Frame Buffer mode (FBDEV)[355]Rem. SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[356]Rem. Cirrus Logic CS 4614 ??? No Kayak XU (D4691N, D4692N, D4695N, D4701N, D4693N, D4694N, D4702N, D4705N) Matrox Millenium II PCI Yes XFree 3.3.6[357]Rem. (SVGA) AMD 79C971 KC 10/100 BT Yes driver pcnet32 Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI Yes driver aic7xxx ??? ??? Yes Kayak XU (D5680N, D5682N, D5683N, D5684N) Chipset BX[358]Rem. Matrox Millenium II PCI Yes XFree 3.3.6[359]Rem. (SVGA) AMD 79C971 KC 10/100 BT Yes driver pcnet32 Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI Yes driver aic7xxx Analog Device 1816 Yes driver AD1816[360]Rem. Yes Kayak XU (D5702, D5704, D5686N, D6336N, D6348N, D8431N, D8920N) Matrox Millenium G200 AGP Yes XFree 3.3.6[361]Rem. (SVGA) AMD 79C972 10/100 BT + SCSI (D6692A)[362]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) + Adaptec AIC 7880 PCI Yes driver ncr53c8xx and driver aic7xxx ??? ??? Yes Kayak XU (D5687N, D6333N, D6334N, D8432N, D6345N, D8923N) Elsa Gloria Synergy + AGP[363]Rem. Yes XFree 3.3.6[364]Rem. (3D Labs) AMD 79C972 10/100 BT + SCSI (D6692A)[365]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) + Adaptec AIC 7880 PCI Yes driver ncr53c8xx and driver aic7xxx ??? ??? No Kayak XU (D6337N, D6346N) Accel Galaxy AGP Yes XFree 3.3.6[366]Rem. in Frame Buffer mode (FBDEV)[367]Rem. Not interesting AMD 79C972 10/100 BT + SCSI (D6692A)[368]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) + Adaptec AIC 7880 PCI Yes driver ncr53c8xx and driver aic7xxx ??? ??? No Kayak XU (D6347N) Matrox Productiva G100 AGP[369]Rem. Yes XFree 3.3.6[370]Rem. (SVGA) AMD 79C972 10/100 BT + SCSI (D6692A)[371]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) + Adaptec AIC 7880 PCI Yes driver ncr53c8xx and driver aic7xxx ??? ??? No Kayak XU (D8924N) Matrox Millenium G400D AGP Yes XFree 3.3.6[372]Rem. (SVGA) AMD 79C972 10/100 BT + SCSI (D6692A)[373]Rem. Yes driver pcnet32 Symbios Logic 53c875 with network card (D6692A) + Adaptec AIC 7880 PCI Yes driver ncr53c8xx and driver aic7xxx ??? ??? No Kayak XU800 (D8019N) [374]Rem. Matrox Millenium G250 AGP ??? SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 None N/A Cirrus Logic CS 4614 ??? No Kayak XU800 (D8021N) [375]Rem. Matrox Millenium G400D AGP Yes XFree 3.3.6[376]Rem. (SVGA) SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 None N/A Cirrus Logic CS 4614 ??? No Kayak XU800 (D8000N, D8001N) [377]Rem. [378]Rem. Matrox Millenium G250 AGP ??? SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[379]Rem. Cirrus Logic CS 4614 ??? No Kayak XU800 (D8002N, D8010N, D8016N) [380]Rem. Matrox Millenium G250 AGP ??? SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[381]Rem. Cirrus Logic CS 4614 ??? No Kayak XU800 (D8003N, D8006N, D8012N) [382]Rem. Matrox Millenium G400D AGP Yes XFree 3.3.6[383]Rem. (SVGA) SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[384]Rem. Cirrus Logic CS 4614 ??? Yes Kayak XU800 (D8007N, D8013N, D8020N, D8022N) [385]Rem. Elsa Gloria Synergy II AGP Yes XFree 3.3.6[386]Rem. (SVGA) SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[387]Rem. Cirrus Logic CS 4614 ??? No Kayak XU800 (D8009N, D8015N) [388]Rem. 3DLabs Oxygen GVX1 AGP Yes XFree 3.3.6[389]Rem. in Frame Buffer mode (FBDEV)[390]Rem. SMC 1211 TX EZ Card 10/100 BT Yes driver rtl8139 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[391]Rem. Cirrus Logic CS 4614 ??? No Kayak XW (D6475N) Elsa Gloria Synergy[392]Rem. Yes XFree 3.3.6[393]Rem. (3D Labs) AMD 79C971 KC 10/100 BT Yes driver pcnet32 Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI Yes driver aic7xxx ??? ??? No Kayak XW (D5505N, D5507N, D5509N) Accel Eclipse PCI Yes XFree 3.3.6[394]Rem. in Frame Buffer mode (FBDEV)[395]Rem. Not interesting AMD 79C971 KC 10/100 BT Yes driver pcnet32 Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI Yes driver aic7xxx ??? ??? No Kayak XW (D5510N, D5514N, D6485N) HP Fx-4 AGP No XFree 3.3.6[396]Rem. in Frame Buffer mode (FBDEV)[397]Rem. Not interesting AMD 79C971 KC 10/100 BT Yes driver pcnet32 Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI Yes driver aic7xxx ??? ??? No Kayak XW (D6480N, D6481N, D6482N) Chipset BX[398]Rem. Accel Eclipse PCI Yes XFree 3.3.6[399]Rem. in Frame Buffer mode (FBDEV)[400]Rem. Not interesting ??? ??? ??? ??? ??? ??? No Kayak XW (D6797N) HP Fx-6 AGP No XFree 3.3.6[401]Rem. in Frame Buffer mode (FBDEV)[402]Rem. Not interesting ??? ??? ??? ??? ??? ??? No Kayak XW (D6486N, D6487N, D6488N) Chipset BX[403]Rem. HP Fx-4 AGP No XFree 3.3.6[404]Rem. in Frame Buffer mode (FBDEV)[405]Rem. Not interesting ??? ??? ??? ??? ??? ??? No Table 3-4. Visualize and Linux Machine Graphic Card Linux support Network Card Linux support SCSI Card Linux support Sound Card Linux support Tes-ted Visualize P (A5015A) Chipset BX[406]Rem. Elsa Gloria Synergy + AGP[407]Rem. Yes XFree 3.3.6[408]Rem. (3D Labs) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[409]Rem. No Visualize P (A5015A) Chipset BX[410]Rem. Elsa Gloria Synergy II AGP Yes XFree 3.3.6[411]Rem. (SVGA) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[412]Rem. No Visualize P (A1296A) Chipset BX[413]Rem. Elsa Gloria Synergy II AGP Yes XFree 3.3.6[414]Rem. (SVGA) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[415]Rem. No Visualize X (A5014A) Chipset BX[416]Rem. Elsa Gloria Synergy + AGP[417]Rem. Yes XFree 3.3.6[418]Rem. (3D Labs) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[419]Rem. No Visualize X (A5014A) Chipset BX[420]Rem. Elsa Gloria Synergy II AGP Yes XFree 3.3.6[421]Rem. (SVGA) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[422]Rem. No Visualize X (A1297A) Chipset BX[423]Rem. Elsa Gloria Synergy + AGP[424]Rem. Yes XFree 3.3.6[425]Rem. (3D Labs) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[426]Rem. No Visualize X (A1280A) Elsa Gloria Synergy II AGP Yes XFree 3.3.6[427]Rem. (SVGA) ??? ??? ??? ??? Analog Device 1816 Yes driver AD1816[428]Rem. No A page dedictaed to these machines and their support under LInux is available at http://www.hp.com/visualize/support/technotes/linux _________________________________________________________________ Desktop computer accessories The following table provides all of the informations on the support for this hardware by Linux. Table 3-5. Desktop computer accessories Reference Card type Chipset Linux support Tes-ted D5480A FastRaid Card Adaptec ARO Raidport No No D6690A FastRaid Card Adaptec ARO Raidport No No D6951A SCSI Card Adaptec AIC 7880 UW PCI Yes driver aic7xxx Yes D9528A SCSI Card Symbios Logic 8952U Ultra2 Wide PCI ??? No D9529A SCSI Card ??? ??? No D6936A Network Card AMD 79C972 AKC 10/100 BT Yes driver pcnet32 Yes D7504A Network Card 3Com 905B-TX 10/100 BT[429]Rem. Yes driver 3c59x[430]Rem. Yes D7506A Network Card ??? ??? No D7508A Network Card ??? ??? No D7522A Network Card 3Com 905C-TX 10/100 BT Yes driver 3c59x[431]Rem. Yes D7531A Network Card Carte HP chipset RealTek Yes driver RealTek Yes D6657A Sound Card ??? ??? No D5183A Sound Card ??? ??? No CD-ROM, DVD and ZIP drives are supported by Linux kernel. Read the various HOWTO for their use, following the interface type. _________________________________________________________________ The portable range (OmniBook) The following table provides all of the informations on the support for this hardware by Linux. Table 3-6. OmniBook and Linux Machine Graphic Card Linux support Network Card Linux support SCSI Card Linux support Sound Card Linux support Tes-ted OmniBook 800 (F1360A) Neomagic MagicGraph 128XD NM2160 Yes XFree 3.3.6[432]Rem. (SVGA) None N/A SCSI Card Yes driver ncr-53c8xx[433]Rem. ??? ??? Yes OmniBook 2000 (F1356A, F1397A) Chips & Technologies CT65554 Yes XFree 3.3.6[434]Rem. (SVGA) None N/A None N/A ??? ??? No OmniBook Sojourn (F1430A) Neomagic MagicGraph 128XD NM2160 Yes XFree 3.3.6[435]Rem. (SVGA) None N/A None N/A ??? ??? No OmniBook XE (F1719W, F1720W, F1721W, F1722W) Silicon Motion LynxE SM810[436]Rem. Yes XFree 3.3.6[437]Rem. (SVGA) None N/A None N/A ??? ??? Yes OmniBook XE2 (F1664W, F1666W, F1666N, F1667W, F1667N, F1674W, F1675W, F1753W, F1756W, F1755W, F1755N, F1772W, F1774N, F1774W, F1775N, F1775W, F1962W) Silicon Motion LynxE SM810[438]Rem. Yes XFree 3.3.6[439]Rem. (SVGA) None N/A None N/A ??? ??? Yes OmniBook 2100 (F1584W, F1580W, F1581W, F1597W, F1598W, F1599W, F1600W, F1729W) Neomagic MagicGraph 128XD NM2160 Yes XFree 3.3.6[440]Rem. (SVGA) None N/A None N/A ??? ??? Yes OmniBook 900 (F1711W, F1712W, F1760W, F1711N, F1712N, F1765N) Neomagic MagicGraph 256AV NM2200 Yes XFree 3.3.6[441]Rem. (SVGA) None N/A None N/A ??? ??? Yes OmniBook 900 (F1769W, F1769N, F1769K, F1770W, F1770N, F1770K, F1979W, F1979N, F1979K, F1980W, F1980N, F1980K) ATI ??? None N/A None N/A ??? ??? No OmniBook 3000 (F1391A, F1392A, F1393A) Neomagic MagicGraph 128XD NM2160 Yes XFree 3.3.6[442]Rem. (SVGA) None N/A None N/A ??? ??? No OmniBook 3100 (F1582W) Neomagic MagicGraph 128XD NM2160 Yes XFree 3.3.6[443]Rem. (SVGA) None N/A None N/A ??? ??? No OmniBook 4100 (F1462W, F1463W, F1479W, F1464W, F1703W) Neomagic MagicGraph 128XD NM2160 Yes XFree 3.3.6[444]Rem. (SVGA) None N/A None N/A ??? ??? Yes OmniBook 4150 (F1629W, F1640W, F1641W, F1642W, F1629N, F1640N, F1641N, F1642N, F1647W, F1647N, F1648W, F1648N, F1663W, F1663N) Neomagic MagicGraph 256AV NM2200 Yes XFree 3.3.6[445]Rem. (SVGA) None N/A None N/A Crystal CS 4232 ??? Yes OmniBook 4150 (F1649W, F1649N, F1649K, F1650W, F1650N, F1650K, F1658W, F1658N, F1660W, F1660N, F1662W, F1662N, F1662K, F1976W, F1976N, F1976K, F1983W, F1983N, F1983K, F2000W, F2000N, F2000K, ) ATI ??? None N/A None N/A Crystal CS 4232 ??? Yes OmniBook 5700 (F1352A, F1353A, F1396A, F1354A, F1355A) Chips & Technologies CT65554 Yes XFree 3.3.6[446]Rem. (SVGA) None N/A None N/A ??? ??? Yes OmniBook 7100 (F1441W, F1442W) ATI Rage LT Pro Yes XFree 3.3.6[447]Rem. (Mach 64) None N/A None N/A ??? ??? Yes OmniBook 7150 (F1443W) ATI Rage LT Pro Yes XFree 3.3.6[448]Rem. (Mach 64) None N/A None N/A ??? ??? No _________________________________________________________________ Portable accessories The cards mentionned below are PCMCIA or PC-Card cards. The following table provides all of the informations on the support for this hardware by Linux. Table 3-7. Portable accessories Reference Card type Chipset Linux support Tes-ted F1623A Modem/Net Card Xircom CEM56-100 56Kb 10/100 BT Yes driver xirc2ps_cs Yes F1625A Modem Card ??? ??? No F1626A Network Card 3Com 3CXFE575BT 10/100 BT ??? No F1626B Network Card ??? ??? No F1643A Modem/Net Card ??? ??? No _________________________________________________________________ The server range (NetServer) A page on how Linux works on HP NetServer is available at http://www.netserver.hp.com/netserver/products/highlights_linux.asp An official compatibility matrix of HP NetServer with Linux and other operating systems is available at : http://netserver.hp.com/netserver/support/compatibility/drvmatrx.htm Official documents to help configuring NetServer under Linux [449]RedHat [450]5.2 and [451]6.0 are also available. The following table provides all of the informations on the support for this hardware by Linux. Table 3-8. NetServer and Linux Machine Graphic Card Linux support Network Card Linux support SCSI Card Linux support Sound Card Linux support Tes-ted NetServer E45 (D4973A, D4974A, D4975A, D4976A, D5971A) Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[452]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Adaptec AIC 2910bui (7860) PCI Yes driver aic7xxx None N/A No NetServer E50 (D6034A, D6033A, D6035A, D6031A, D6030A, D6032A) Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[453]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A Yes NetServer E55 (D9337A) ATI Rage II C AGP Yes XFree 3.3.6[454]Rem. (Mach 64) Intel S82093A / i82559 10/100 BT Yes driver eepro-100 Adaptec AIC 7895H PCI Yes driver aic7xxx None N/A No NetServer E60 (D7140A, D7142A, D7144A, D7146A, D7148A, D9123A, D9127A, D9128A, D9129A) ATI Rage II C AGP Yes XFree 3.3.6[455]Rem. (Mach 64) Intel S82093A / i82559 10/100 BT Yes driver eepro-100 Adaptec AIC 7895H PCI Yes driver aic7xxx None N/A Yes NetServer LC II (D4907A, D4909A, D5014A, D5015A, D5016A, D5969A, D5970A, D5959A, D5961A) Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[456]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A Yes NetServer LC 3 (D6123A, D7018A, D6125A, D7020A, D7028A, D7025A, D7126A, D8594A) Chipset BX[457]Rem. Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[458]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A Yes NetServer LC 2000 (D8514A, D8515A, D8519A, D8520A, D8524A, D8525A, D9162A, D9163A) Chipset i820[459]Rem. [460]Rem. ATI Rage II C AGP Yes XFree 3.3.6[461]Rem. (Mach 64) Intel S82093A / i82559 10/100 BT Yes driver eepro-100 2 Symbios Logic 53C897 PCI Yes driver ncr-53c8xx[462]Rem. None N/A Yes NetServer LD Pro (D4944A, D4946A, D4961A, D4962A) Trident TVGA 9000i Yes XFree 3.3.6[463]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A No NetServer LH Pro (D4979A, D4980A, D4981A, D4982A) Trident TVGA 9000i Yes XFree 3.3.6[464]Rem. (SVGA) None N/A 2 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A Yes NetServer LH II (D5017A, D5953A, D5021A, D5023A, D6047A, D6048A) Trident TVGA 9000i Yes XFree 3.3.6[465]Rem. (SVGA) None N/A 2 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A Yes NetServer LH 3 (D4998A, D5002A, D5000A, D5004A, D7033A, D7034A, D8503A, D8504A, D8567A, D8568A, D9343A, D9344A) Chipset BX[466]Rem. [467]Rem. Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[468]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 2 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[469]Rem. None N/A Yes NetServer LH 3000 (D8228A, D8230A, D8236A, D8238A, D8244A, D8246A, D9176A, D9178A) Chipset BX[470]Rem. [471]Rem. ??? ??? ??? ??? ??? ??? None N/A No NetServer LH 4 (D7092A, D7093A, D7094A, D7095A, D6971A, D6972A, D6973A, D6974A, D7103A, D7104A, D8552A, D8553A, D8556A, D8557A, D8560A, D8561A) Chipset BX[472]Rem. [473]Rem.[474]Rem. Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[475]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 2 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[476]Rem. None N/A Yes NetServer LH 6000 () Chipset BX[477]Rem. [478]Rem. [479]Rem. ATI Rage II C AGP Yes XFree 3.3.6[480]Rem. (Mach 64) Intel S82093A / i82559 10/100 BT Yes driver eepro-100 Adaptec AIC 7880 PCI + 2 Symbios Logic 53C896 PCI Yes driver aic7xxx and driver ncr53c8xx None N/A Yes NetServer LPr (D6130A, D6131A, D7171A, D9133A, D9348A, D9431A, D9434A) Chipset BX[481]Rem. Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[482]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[483]Rem. None N/A Yes Cluster NetServer LPr (D6131A, P1133A)[484]Rem. Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[485]Rem. (SVGA) Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Symbios Logic 53C895 PCI Yes driver ncr-53c8xx[486]Rem. None N/A No NetServer LXePro/LXPro (D4920B, D4925B, D6036A, D4311B, D4312B, D6037A, D4315B, D4958B, D6014A, D6015A, D4964B, D4898A, D6016A, D4899A, D6017A, D4900A, D6018A) Cirrus Logic GD 5424 PCI Yes XFree 3.3.6[487]Rem. (SVGA) None N/A 2 Adaptec AIC 7880 UW PCI Yes driver aic7xxx None N/A No NetServer LXr8 (D5028A) ? ? None N/A Symbios logic UW ? None N/A No NetServer LXr8000 (D6021A, D6022A, D6136A, D6137A, D7000A, D8256A, D8257A, D8258A, D8546A, D8548A) Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[488]Rem. (SVGA) None N/A 2 Symbios Logic 53C896 PCI Yes driver ncr-53c8xx[489]Rem. None N/A Yes NetServer LXr8500 (D8540A, D8542A, D9417A, D9418A) Cirrus Logic GD 5446 PCI Yes XFree 3.3.6[490]Rem. (SVGA) None N/A 2 Symbios Logic 53C896 PCI Yes driver ncr-53c8xx[491]Rem. None N/A No _________________________________________________________________ NetServers accessories The following table provides all of the informations on the support for this hardware by Linux. Table 3-9. NetServers accessories Reference Card type Chipset Linux support Tes-ted NetRaid 1 D4992A NetRaid Card AMI Megaraid (Raid 0, 1, 3, 5, 10, 50) Yes driver megaraid[492]Rem. Yes NetRaid 3 D4943A NetRaid Card AMI Megaraid (Raid 0, 1, 3, 5, 10, 50) Yes driver megaraid[493]Rem. Yes NetRaid 1Si D2140A NetRaid Card AMI Megaraid (Raid 0, 1, 3, 5, 10, 50) Yes driver megaraid[494]Rem. Yes NetRaid 3Si D5955A NetRaid Card AMI Megaraid (Raid 0, 1, 3, 5, 10, 50) Yes driver megaraid[495]Rem. Yes C1578B SCSI Card Adaptec AIC 7895H PCI Yes driver aic7xxx No C7430A SCSI Card Adaptec AIC 7880 UW PCI Yes driver aic7xxx No D5025A SCSI Card Adaptec AIC 7880 UW PCI Yes driver aic7xxx Yes D5252A SCSI Card Adaptec AIC 7880 UWD PCI Yes driver aic7xxx Yes D5013A, D5013B Network Card Intel i82557 / i82558 10/100 BT (D5013A/B) Yes driver eepro-100 Yes J2585B Network Card Carte 100VG (J2585B) Yes driver hp100 Yes D6977A Fibre Channel Card ??? ??? No D5246A Fibre Channel Card ??? ??? No D6028A Top Tools Card ??? Yes Yes _________________________________________________________________ Complementary informations Please refer to the [496]Hardware Howto and [497]Ethernet Howto for other details concerning the support of some hardware elements by Linux. For video chipsets support, a fundamental page is the one of [498]XFree86 with its supported [499]chipsets list and the new running developments by [500]Suse (Think, in that case, to download also [501]the configuration tool) and [502]RedHat at the following addresses : * ftp://ftp.medasys-digital-systems.fr/pub/linux/redhat.com/XBF * ftp://ftp.medasys-digital-systems.fr/pub/linux/redhat.com/XFCom Commercial servers are also available, as those of [503]X-Inside and [504]MetroLink Netvectra are not supported by Linux. _________________________________________________________________ Remarks XFree86 The latest version of XFree86 is the 3.3.6, available from our [505]mirror. Ncr53c8xx The latest version of the ncr53c8xx driver is available from the [506]reference site. 3C59x The latest version of the 3c59x driver is available from the [507]reference site. Sound Chipset AD1816 The latest version of the AD1816 driver is available from the [508]reference site. DOS models These models are delivered with MS-DOS only, in order to have a Linux Machine at the best price. G100 card 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 XF86Config : Option "no_accel". Section example : Section "Device" [...] VendorName "Matrox" VideoRam 4096 Option "no_accel" EndSection Silicon Motion LynxE card 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. 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. Intel i810 card (Informations provided by Frdric Dubuy <[509]Frederic.Dubuy@medasys-digital-systems.fr> and Anne-Marie Mahfouf <[510]a-m.mahfouf@lineone.net>) This card is only supported with a specific X server XFCom_i810 downloadable in both format [511]RPM or [512]tar.gz and a complementary module for the kernel agpgart, downloadable in both format [513]SRPM or [514]tar.gz. A detailed documentation on the installation is provided at http://www.linux-france.org/article/x/GuideIntel810/book1.html To summarize, once the X server installed, the module compiled and installed, it's sufficient to modify with the following parameters the file /etc/X11/XF86Config : Section "Device" [...] Identifier "i810" [...] EndSection [...] Section "Screen" [...] Driver "svga" Device "i810" [...] EndSection XU800 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 /etc/lilo.conf where xxx is your RAM in MB. LC 2000 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) LH 6000 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 :-) BX Chipset Intel BX Chipset (Memory Bus at 100 MHz) is supported by [515]kernels above 2.0.34/2.1.103. i820 Chipset Coppermine 0.18 m technology - 256 KB synchronous cache - Intel i820 Chipset BAx 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). FrameBuffer To use the FrameBuffer mode, please consult the following documents http://www.medasys-digital-systems.fr/linux/framebuffer.html and http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Fr amebuffer-HOWTO.html. Boot disk for 3Com card Creation of a custom RedHat 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.medasys-digital-systems.fr/pub/linux/networking/drivers/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: GD 5465 video card 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 XF86Config : Option "xaa_no_color_exp". Section example : Section "Device" [...] Identifier "CL-GD5465" VendorName "Cirrus" BoardName "GD5465" VideoRam 2048 Option "xaa_no_color_exp" EndSection Elsa Gloria Synergy card 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. + [516]Elsa web site + [517]OpenGL web site + [518]Mesa web site D6692A card 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 2.2.14) and the distribution with the complementary packages needed. HA Cluster To use a High Availability Custer under Linux, you need to use additional software, such as : + [519]RSF-1 (Commercial) + [520]Linux-HA project (free) and [521]ext3 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. NetRaid card These cards are equiped with an [522]AMI Megaraid chipset and may support the following Raid levels : 0, 1, 3, 5, 10, 30 and 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/2.2.14 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 [523]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. 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 2.2.14 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, LH6000 are equiped with an integrated card doing hardware checks. _________________________________________________________________ The monitors range The following table provides all of the informations on the support for this hardware by XFree86. Table 3-10. HP Monitors and Linux Reference Name Vert. F. (Hz) Hor. F. (kHz) Bandwidth (MHz) Resol Freq. (Hz) Tes-ted 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 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 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 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" HP 90 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 910 50-150 29-107 230 640x400, 640x480, 800x600, 1024x768, 1280x1024, 1600x1200 70, 60-85, 85, 75-85, 75-85, 75-85 No A4031A 20" 48-150 30-82 ??? ??? ??? Yes D2846A, A4576A 21" P1100 50-160 30-107 ??? ??? ??? No D2847A 21" P1110 50-180 29-121 300 ??? ??? Yes A4033A 21" 50-120 30-80 ??? ??? ??? Yes A1295A 24" Wide Aspect 50-160 30-96 ??? ??? ??? No D5061A 15,1" LCD HP ??? ??? 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 _________________________________________________________________ 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, ...). 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 [524]The Puffin Group and more precise informations on the status may be found on their [525]Web site. For the moment the work on the boot process is improved, a shell is launched... which dies rapidly :-) 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. 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 http://www.gr.opengroup.org/mklinux/hppa/mkpa-rel.html. _________________________________________________________________ The IA-64 range 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 ftp://ftp.kernel.org/pub/linux/kernel/ia64. More informations on this topic may be found on this page of the HP labs : http://devresource.hp.com/devresource/Topics/IA64/IA64.html or on the reference site http://www.linuxia64.org _________________________________________________________________ The printing product range General points 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. 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 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 [526]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 [527]SaMBa for the clients of Microsoft systems (Win9x ou WinNTx) or through [528]NetAtalk for the MacIntosh clients. At last, [529]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 file example smbprint provided with the [530]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 [531]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 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 -gx page size in pixels | -r pixels/inch resolution -sDEVICE= select device | -dBATCH exit after last file -sOutputFile= 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. 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 list of the HP printers support may be found on the following page : http://www.picante.com/~gtaylor/pht/printer_list.cgi?make=HP&format=fu ll. _________________________________________________________________ HP software available under Linux This section presents rapidly some HP applications which can be used under Linux. These are either commercial applications or freeware applications. _________________________________________________________________ HP softwares FireHunter This software targetted to the ISP manages services levels and is available for RedHat version 5.2 distributions. http://www.firehunter.com. HP Eloquence 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 http://www.hp-eloquence.com. HP WebJetAdmin 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 http://www.hp.com/go/webjetadmin. An RPM version is also available at ftp://ftp.medasys-digital-systems.fr/pub/linux/mds/redhat/RPMS/ i386/hpwebjet-5.6-1.i386.rpm. HP WebQoS 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 http://www.hp.com/go/webqos. HP OpenView 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 http://www.hp.com/storage/event/openview_hl.html). HP OpenMail 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 : http://www.ice.hp.com/cyc/om/00/cysearch.cgi?pattern=100-1417|1 00-1408|100-1333|100-0100. 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 of the informations concerning it are available on the page : http://www.e-speak.hp.com/. _________________________________________________________________ Third party softwares linked to HP GNUPro HP and [532]Cygnus Solutions have announced the 8th of March, 1999 a partnership to provide the GNUPro tools on all the HP machines, including Linux. _________________________________________________________________ Support of HP solutions under Linux HP proposes since May 1999 a [533]worldwide support offer on Linux. It's detailed on the page http://www.hp.com/pressrel/apr99/20apr99a.htm. 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 Third party firms also propose Linux and free software support on HP platforms : [534]Medasys Contact : Cdric Letailleur <[535]Cedric.Letailleur@medasys-digital-systems.fr> [536]Alcove Contact : Lucien Petit <[537]lucien.petit@alcove.fr> _________________________________________________________________ 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. _________________________________________________________________ Chapter 4. Solutions and Sizing This chapter proposes an help for sizing NetServers under Linux, depending on the different kinds 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 15 MB/s), * 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), * 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. 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). 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 a posteriori, rather than to add a new server. 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. 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. 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 (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. * 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. * 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 II 450). * Each X-Window user excuting a client on the server uses in average 2 MB. * It may be useful to add network cards on this type of machine to smooth the traffic, depending on the number of clients. _________________________________________________________________ Linux as file and print server 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 2 LVD SCSI at 80 MB/s, if the budget allows it, and 10.000 RPM disks. Table 4-1. Sizing of a file server Simultaneous users RAM size Disk size Machine example 1 - 100 312 Mo 27 Go E60 100 - 500 1 Go 117 Go LC2000 500 - 1000 2 Go 216 Go LH3000 _________________________________________________________________ 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 Mo 9 Go E60 100 - 500 1 Go 9 Go E60 500 - 1000 2 Go 9 Go LC2000 _________________________________________________________________ Internet/Intranet Linux server 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 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. Table 4-3. Sizing of a static Web server Simultaneous users RAM size Disk size Machine example 1 - 100 256 Mo 9 Go E60 100 - 500 1 Go 9 Go LC2000 Bi-processeur 500 - 1000 2 Go 9 Go LH4 Quadri-processeurs Table 4-4. Sizing of a dynamic Web server Simultaneous users RAM size Disk size Machine example 1 - 100 512 Mo 9 Go E60 100 - 500 2 Go 9 Go LC2000 Bi-processeur 500 - 1000 4 Go 18 Go LH6000 Quadri-processeur _________________________________________________________________ Mail Server 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. Table 4-5. Sizing of an e-mail server Simultaneous users RAM size Disk size Machine example 1 - 100 400 Mo 9 Go E60 100 - 500 2 Go 27 Go LC2000 Bi-processeur 500 - 1000 4 Go 54 Go LH6000 Quadri-processeur _________________________________________________________________ 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 Mo 9 Go E60 100 - 500 512 Mo 18 Go E60 500 - 1000 1 Go 27 Go E60 _________________________________________________________________ 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 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). _________________________________________________________________ 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 [538]Metaframe solutions of [539]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-7. Sizing of an office server Simultaneous users RAM size Disk size Machine example 1 - 10 512 Mo 9 Go E60 10 - 50 2 Go 9 Go LH4 Bi-processeurs 50 - 100 4 Go 18 Go LH6000 Quadri-processeurs _________________________________________________________________ Chapter 5. Frequently Asked Questions (FAQ) "How to have more than 1 GB of RAM on my NetServer ?" The following informations are adapted from the [540]page of Rik van Riel. They concern 2.0.x as well as 2.2.x kernels. 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 config. The maximum Ram managed in the i386 version was ported to 64 GB after 2.3.23. "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 1 GB. "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 kernel, you have to set it up during the make config. For more details, please consult the [541]SMP-HOWTO. "Is Linux Y2K compatible ?" Generally, Linux is Y2K compatible. For more informations please consult the [542]FAQ. _________________________________________________________________ Chapter 6. References I already mentioned the documentation files, installed typically under the directory /usr/src/linux/Documentation. They are a real gold mine of useful informations. 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 informations useful in link with our subject : * [543]Linux SCSI HOWTO * [544]Linux CD-Writing HOWTO * [545]Linux Hardware HOWTO * [546]Linux Distribution HOWTO * [547]Linux Kernel HOWTO * [548]Linux Sound HOWTO The following Usenet groups cover subjects linked to HP : * news:comp.sys.hp.hardware * news:comp.sys.hp.misc You may also consult the groups mentioned in [549]the section called Service argumentation in Chapter 2. On Internet, you may consult with a great benefit the following sites : Table 6-1. Web sites ofMedasys and 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 Medasys Linux http://www.medasys-digital-systems.fr/linux HP Support http://www.hp.com/pressrel/apr99/20apr99a.htm HP HOWTO http://www.medasys-digital-systems.fr/linux/HP-Howto/HP-HOWTO-EN/index .html Linux Pa-Risc (Puffin Group) http://thepuffingroup.com/parisc/software.html Linux IA64 http://www.linuxia64.org Linux IA64 (HP Labs) http://dtf.external.hp.com/dtf/swdev/1999/08/feature1_a.html HP RedHat certification http://bugzilla.redhat.com/certification/cert-report.php3?mod_company= Hewlett+Packard HP Utigroup http://www.hputigroup.com Table 6-2. Other fundamental sites on Linux and Open Source Software Subject URL Linux Weekly News - Summary of 1998 http://lwn.net/1999/features/1998timeline/ Linux Weekly News - Summary of 1999 http://lwn.net/1999/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 Source Exchange http://www.sourcexchange.com/ _________________________________________________________________ Chapter 7. Contributors I would like to thank especially all the people who contributed in any way to improve this HOWTO : * Pierre-Antoine Angelini <[550]angelini@ifsic.univ-rennes1.fr> * Stphane Bortzmeyer <[551]bortzmeyer@debian.org> * Jean-Bernard Chaffardon <[552]Jean-Bernard_Chaffardon@hp.com> * Khalil Chawoshi <[553]chawoshi@subatech.in2p3.fr> * Batrice Cornec <[554]beatrice@victoria.frmug.org> * Frdric Dubuy <[555]Frederic.Dubuy@medasys-digital-systems.fr> * Mark Eve <[556]Mark_Eve@hp.com> * Laurent Frey <[557]laurent.frey@iota.u-psud.fr> * Stein Roar Gjen <[558]stein.roar.gjoen@ks-t.no> * Yann Guillemot <[559]Yann.Guillemot@medasys-digital-systems.fr> * Marc Hia Bali <[560]Marc_Hia-Balie@hp.com> * Chris Holden <[561]chris.holden@gte.net> * Masanari Iida <[562]Masanari_Iida@hp.com> * Pascal Lemonnier <[563]Pascal.Lemonnier@medasys-digital-systems.fr> * Maciej Macowicz <[564]Maciej.Macowicz@epfl.ch> * Olivier Martinet <[565]Olivier_Martinet@hp.com> * David Mentr <[566]David.Mentre@irisa.fr> * Andreas Nierula <[567]A.Nierula@t-online.de> * Gilles Noisette <[568]Gilles_Noisette@hp.com> * Harry Page <[569]HARRY_PAGE@HP-NewZealand-om1.om.hp.com> * Alain Pascal <[570]pascal@montrouge.omnes.slb.com> * Fons Rademakers <[571]Fons.Rademakers@cern.ch> - his site : http://hp-linux.cern.ch * Dirk De Wachter<[572]Dirk.DeWachter@rug.ac.be> * Norman Walsh<[573]ndw@nwalsh.com> _________________________________________________________________ Chapter 8. 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.89 URLs verification in function of the language. Use of official addresses and paragraph on mirrors. Report of headers and footers on following pages (PS). 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). Revision of the version number (PS and HTML). Paragraph on Kayak Maxilife. Paragraph on Kayak Sound Paragraph on TX management Rethink the copyright in front of the LDP one and becoming an official HOWTO. Rework chapter 1 (put there history and new versions) Version 0.90 Rework the cluster part Paragraph on APM for portables Rework the printer paragraph Linux as a backup server (Arkeia) Remote Assistant - Remote Control. Management Glossary/Abbreviations Rework the example of the vaccine :-) Put the Argumementations in the TOC (HTML). Avoid titles in end of page (PS). Detail limitations of evolution from Unix to Linux Paragraph on HP as a free software user Version 0.91 Paragraph on network products Paragraph on scanners Management of the date with wml References Visible links 1. http://www.hp.com/ 2. http://www.medasys-digital-systems.fr/ 3. http://www.hp.com/ 4. http://pauillac.inria.fr/~lang/licence/v1/fddl.html 5. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#INTRODUCTION 6. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN59 7. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN70 8. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN82 9. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#REMERCIEMENTS 10. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#PRESENTATION 11. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN156 12. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN159 13. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN182 14. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN191 15. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN217 16. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN220 17. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CHOIX 18. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN419 19. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN472 20. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN484 21. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN487 22. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN495 23. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN498 24. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#LINUXHP 25. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN507 26. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN509 27. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN524 28. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN594 29. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN597 30. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3165 31. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3370 32. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3379 33. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3385 34. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3431 35. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3434 36. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3474 37. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3482 38. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3501 39. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#SIZING 40. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3543 41. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3545 42. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3577 43. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3609 44. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3611 45. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3672 46. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3704 47. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3736 48. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AEN3739 49. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FAQ 50. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#REFERENCES 51. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CONTRIBUTEURS 52. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#TODO 53. http://www.hp.com/ 54. http://www.medasys-digital-systems.fr/ 55. http://www.hp.com/ 56. http://www.medasys-digital-systems.fr/ 57. http://www.hp.com/ 58. http://www.medasys-digital-systems.fr/ 59. http://www.hp.com/ 60. mailto:Bruno.Cornec@medasys-digital-systems.fr 61. mailto:guylhem@rrremovethis.oeil.qc.ca 62. http://hpux.cict.fr/ 63. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CONTRIBUTEURS 64. mailto:Marc_Hia-Balie@hp.com 65. http://www.cs.helsinki.fi/~torvalds/ 66. http://www.gnu.org/people/rms.html 67. mailto:nat@nataa.frmug.org 68. mailto:xc@itp.fr 69. mailto:dumas@Linux.EU.Org 70. mailto:Remy.Card@linux.org 71. mailto:Dany.Coffineau@alcatel.fr 72. mailto:Francois.Strobel@alcatel.fr 73. mailto:Frederic.Dubuy@medasys-digital-systems.fr 74. mailto:pascal@montrouge.omnes.slb.com 75. mailto:Pascal.Lemonnier@medasys-digital-systems.fr 76. mailto:rse@engelschall.com 77. http://www.engelschall.com/sw/wml 78. mailto:cg@sgmltools.org 79. http://www.sgmltools.org/ 80. mailto:ndw@nwalsh.com 81. http://www.docbook.org/ 82. mailto:jjc@jclark.com 83. http://www.jclark.com/jade/ 84. mailto:cornec@victoria.frmug.org 85. http://www.gnu.org/ 86. http://www.opensource.org/ 87. http://www.freebsd.org/ 88. http://www.apache.org/ 89. http://www.samba.org/ 90. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CHOIX 91. http://www.cs.helsinki.fi/~torvalds/ 92. http://www.gnu.org/people/rms.html 93. http://www.tuxedo.org/~esr 94. http://kiev.wall.org/~larry 95. mailto:ask_tim@oreilly.com 96. http://www.apache.org/ 97. http://www.zdnet.com/sr/stories/news/0,4538,2196106,00.html 98. http://www.samba.org/ 99. http://gartner6.gartnerweb.com/dq/static/about/press/pr-b9939.html 100. http://www.netcraft.com/survey/ 101. http://www.leb.net/hzo/ioscount/index.html 102. http://www.apache.org/ 103. http://www.apache.org/ 104. http://www.landfield.com/wu-ftpd 105. http://www.isc.org/bind.html 106. http://www.sendmail.org/ 107. http://www.postfix.org/ 108. http://www.isc.org/inn.html 109. http://juanjox.linuxhq.com/ 110. http://www.rustcorp.com/linux/ipchains/ 111. http://www.openssh.com/ 112. http://squid.nlanr.net/Squid/ 113. http://www.eecis.udel.edu/~ntp 114. ftp://ftp.medasys-digital-systems.fr/pub/doc/IETF/rfc 115. ftp://ftp.mathematik.th-darmstadt.de/pub/linux/okir 116. ftp://ftp.kernel.org/pub/linux/devel/gcc/ 117. http://www.coda.cs.cmu.edu/ 118. http://www.samba.org/ 119. http://www.umich.edu/~rsug/netatalk 120. http://www.irisa.fr/prive/mentre/smp-faq/ 121. http://hp-linux.cern.ch/ 122. http://cesdis.gsfc.nasa.gov/linux/drivers/index.html#gigabit 123. http://lhpca.univ-lyon1.fr/myri.html 124. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 125. http://www.hylafax.org/ 126. http://www.arkeia.com/ 127. http://www.postgreSQL.org/ 128. http://www.mysql.org/ 129. http://platforms.oracle.com/linux/index_lin.htm 130. ftp://ftp.netscape.com/pub/communicator/ 131. http://www.cc.ukans.edu/about_lynx/about_lynx.html 132. http://www.geocities.com/SiliconValley/6702/kmail.html 133. http://burka.netvision.net.il/xfmail/xfmail.html 134. http://www.mutt.org/ 135. ftp://ftp.uu.net/networking/mail/elm 136. http://www.adobe.com/supportservice/custsupport/LIBRARY/acrunix.htm 137. http://www.foolabs.com/xpdf/ 138. http://www.wizards.dupont.com/cristy/ImageMagick.html 139. http://www.gimp.org/ 140. http://www.real.com/products/player/downloadrealplayer.html?wp=dl0899&src=dlbutton_all%E2%8C%A9=en#form 141. http://www.lyx.org/ 142. http://www.latex-project.org/ 143. http://www.sgmltools.org/ 144. http://linux.corel.com/linuxproducts_wp8.htm 145. http://www.applix.com/applixware/linux/main.cfm 146. http://www.stardivision.com/office/so5linux_body.html 147. ftp://ftp.medasys-digital-systems.fr/pub/linux/sunsite/apps/sound/players/wavtools-1.3.2.tar.gz 148. http://www.ueda.info.waseda.ac.jp/%7Esatoshi/midi/midi-e.html 149. http://metalab.unc.edu/tkan/xmcd 150. http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html 151. http://sunsite.auc.dk/BurnIT/ 152. http://www.ge.ucl.ac.uk/~jcpearso/mkisofs.html 153. http://www.xiph.org/paranoia/ 154. http://www.winehq.com/ 155. http://www.ardi.com/ 156. http://www.calderasystems.com/doc/wabi/wabi.html 157. http://www.dosemu.org/ 158. http://www.gnu.org/software/gcc/gcc.html 159. http://www.gnu.org/software/gcc/gcc.html 160. http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ 161. http://www.gnu.org/software/fortran/fortran.html 162. ftp://ftp.medasys-digital-systems.fr/pub/linux/sunsite/devel/lang/basic/qb2c-3.2k.tar.gz 163. http://www.scriptics.com/products/tcltk/ 164. http://www.perl.com/ 165. http://www.python.org/ 166. http://www.adahome.com/Resources/Compilers/GNAT.html 167. http://www.loria.fr/projets/SmallEiffel/ 168. http://clisp.cons.org/~haible/clisp.html 169. http://www.scheme.org/ 170. http://www.gnu.org/software/prolog/prolog.html 171. http://www.pgroup.com/prod_description.html 172. http://www.gnome.org/ 173. http://www.kde.org/ 174. http://www.opengroup.org/desktop/ 175. http://www.sgmltools.org/ 176. http://www.jclark.com/jade 177. http://www.oasis-open.org/docbook/ 178. http://www.redhat.com/ 179. http://www.medasys-digital-systems.fr/ 180. http://www.atrid.fr/ 181. http://www.alcove.fr/ 182. http://www.france.hp.com/formation 183. http://www.learningtree.com/fr/index.htm 184. http://form-continue.iut-velizy.uvsq.fr/ 185. http://www.linuxdoc.org/ 186. http://www.medasys-digital-systems.fr/mirror/linux/french/ldp 187. http://www.editions-oreilly.fr/ 188. http://www.ssc.com/ 189. http://www.microsoft.com/HCL 190. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Hardware-HOWTO.html 191. http://www.medasys-digital-systems.fr/linux/HP-Howto/HP-HOWTO-EN/hp-hardware.html 192. http://www.voila.fr/ 193. http://www.deja.com/ 194. ftp://ftp.cdrom.com/ 195. http://www.redhat.com/ 196. http://www.suse.de/ 197. http://www.slackware.com/ 198. http://www.linux-mandrake.com/ 199. http://www.turbolinux.com/ 200. http://www.debian.org/ 201. http://unix-vs-nt.org/kirch/ 202. mailto:Jacques_Misselis@hp.com 203. http://www.ec-lyon.fr/ 204. http://www.medasys-digital-systems.fr/ 205. http://www.medasys-digital-systems.fr/linux/HP-Howto/mirror/white-paper.pdf 206. http://www.li.org/ 207. http://www.medasys-digital-systems.fr/ 208. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Installation-HOWTO.html 209. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Kernel-HOWTO.html 210. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 211. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 212. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 213. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 214. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 215. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 216. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 217. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 218. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 219. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BAX 220. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 221. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BAX 222. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 223. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#I810 224. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 225. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 226. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 227. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 228. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 229. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 230. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 231. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 232. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 233. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 234. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 235. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 236. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 237. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 238. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 239. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 240. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 241. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 242. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 243. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 244. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 245. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 246. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 247. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 248. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 249. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 250. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 251. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 252. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 253. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 254. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 255. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CL5465 256. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 257. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 258. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CL5465 259. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 260. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 261. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 262. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 263. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 264. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 265. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 266. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 267. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 268. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 269. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 270. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 271. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 272. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 273. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 274. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 275. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 276. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 277. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 278. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 279. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 280. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 281. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 282. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 283. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 284. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 285. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 286. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#COPER 287. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#COPER 288. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 289. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#COPER 290. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 291. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 292. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 293. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 294. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CL5465 295. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 296. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CL5465 297. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 298. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CL5465 299. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 300. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 301. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 302. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 303. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 304. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 305. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 306. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 307. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 308. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 309. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 310. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 311. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 312. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 313. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 314. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 315. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 316. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 317. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 318. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 319. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 320. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 321. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 322. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 323. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 324. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 325. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 326. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 327. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 328. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 329. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 330. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 331. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 332. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 333. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 334. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 335. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 336. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 337. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 338. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 339. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 340. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 341. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 342. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 343. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 344. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 345. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 346. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 347. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 348. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 349. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 350. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MODDOS 351. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 352. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 353. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 354. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 355. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 356. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 357. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 358. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 359. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 360. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 361. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 362. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 363. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 364. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 365. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 366. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 367. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 368. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 369. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#G100 370. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 371. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 372. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 373. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MIXTE1 374. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 375. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 376. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 377. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 378. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#MODDOS 379. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 380. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 381. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 382. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 383. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 384. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 385. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 386. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 387. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 388. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XU800 389. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 390. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 391. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 392. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 393. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 394. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 395. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 396. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 397. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 398. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 399. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 400. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 401. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 402. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 403. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 404. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 405. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#FBDEV 406. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 407. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 408. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 409. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 410. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 411. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 412. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 413. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 414. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 415. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 416. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 417. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 418. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 419. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 420. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 421. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 422. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 423. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 424. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#ELSA 425. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 426. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 427. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 428. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#AD1816 429. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3COM 430. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 431. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#C3C59X 432. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 433. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 434. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 435. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 436. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#LYNXE 437. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 438. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#LYNXE 439. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 440. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 441. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 442. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 443. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 444. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 445. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 446. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 447. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 448. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 449. http://www.redhat.com/ 450. http://www.medasys-digital-systems.fr/linux/HP-Howto/mirror/netserver-rh5.2.pdf 451. http://www.medasys-digital-systems.fr/linux/HP-Howto/mirror/netserver-rh6.0.pdf 452. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 453. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 454. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 455. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 456. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 457. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 458. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 459. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#COPER 460. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#LC2000 461. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 462. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 463. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 464. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 465. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 466. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 467. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 468. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 469. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 470. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 471. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 472. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 473. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 474. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#LH4 475. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 476. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 477. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 478. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 479. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#LH6000 480. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 481. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#BX 482. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 483. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 484. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#CLUSTER 485. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 486. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 487. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 488. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 489. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 490. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#XFREE86 491. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NCR53C8XX 492. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 493. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 494. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 495. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#NETRAID 496. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Hardware-HOWTO.html 497. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Ethernet-HOWTO.html 498. http://www.xfree86.org/3.3.6/index.html 499. http://www.xfree86.org/cardlist.html 500. http://www.suse.de/XSuSE/XSuSE_E/index.html 501. ftp://ftp.medasys-digital-systems.fr/pub/linux/XSuSE/config/xsuseconfig.tgz 502. http://www.redhat.com/ 503. http://www.xig.com/ 504. http://www.metrolink.com/ 505. ftp://ftp.medasys-digital-systems.fr/pub/unix/XFree86/3.3.6 506. ftp://ftp.tux.org/pub/roudier 507. ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/test/3c59x.c 508. http://www.student.informatik.tu-darmstadt.de/~tek/projects/linux.html 509. mailto:Frederic.Dubuy@medasys-digital-systems.fr 510. mailto:a-m.mahfouf@lineone.net 511. ftp://download.intel.com/support/graphics/intel810/xfcom-i810-glibc2.1-1.0.0-rh60.i386.rpm 512. ftp://download.intel.com/support/graphics/intel810/xfcom-i810-glibc2.1-1.0.0.tar.gz 513. ftp://download.intel.com/support/graphics/intel810/i810gtt-0.1-5.src.rpm 514. ftp://download.intel.com/support/graphics/intel810/i810gtt-0.1-5.src.tar.gz 515. ftp://ftp.medasys-digital-systems.fr/pub/linux/kernel 516. http://www.elsa.de/EUROPE/PRODUCTS/CAD/SPECS/GLO_SYN.HTM 517. http://www.sgi.com/software/opengl 518. http://www.mesa3d.org/ 519. http://www.rsi.co.uk/products/rsf/rsf-linux.html 520. http://www.henge.com/~alanr/ha 521. ftp://ftp.medasys-digital-systems.fr/pub/linux/ext3 522. http://www.ami.com/ 523. ftp://ftp.medasys-digital-systems.fr/pub/linux/mds/redhat/images/lh3.img 524. http://www.thepuffingroup.com/ 525. http://www.thepuffingroup.com/parisc 526. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/mini/IP-Alias.html 527. http://www.samba.org/ 528. http://www.umich.edu/~rsug/netatalk 529. http://www.samba.org/ 530. http://www.samba.org/ 531. http://www.cs.wisc.edu/~ghost 532. http://www.cygnus.com/ 533. http://www.hp.com/ssg/linux 534. http://www.medasys-digital-systems.fr/ 535. mailto:Cedric.Letailleur@medasys-digital-systems.fr 536. http://www.alcove.fr/ 537. mailto:lucien.petit@alcove.fr 538. http://www.citrix.com/products/metaframe.asp 539. http://www.citrix.com/ 540. http://humbolt.geo.uu.nl/Linux-MM/more_than_1GB.html 541. http://www.irisa.fr/prive/mentre/smp-howto 542. http://www.linux.org/help/beginner/year2000.html 543. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/SCSI-HOWTO.html 544. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/CD-Writing-HOWTO.html 545. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Hardware-HOWTO.html 546. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Distribution-HOWTO.html 547. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Kernel-HOWTO.html 548. http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Sound-HOWTO.html 549. file://localhost/export/sunsite/users/gferg/howto/00HP-HOWTO.html#SERVICE 550. mailto:angelini@ifsic.univ-rennes1.fr 551. mailto:bortzmeyer@debian.org 552. mailto:Jean-Bernard_Chaffardon@hp.com 553. mailto:chawoshi@subatech.in2p3.fr 554. mailto:beatrice@victoria.frmug.org 555. mailto:Frederic.Dubuy@medasys-digital-systems.fr 556. mailto:Mark_Eve@hp.com 557. mailto:laurent.frey@iota.u-psud.fr 558. mailto:stein.roar.gjoen@ks-t.no 559. mailto:Yann.Guillemot@medasys-digital-systems.fr 560. mailto:Marc_Hia-Balie@hp.com 561. mailto:chris.holden@gte.net 562. mailto:Masanari_Iida@hp.com 563. mailto:Pascal.Lemonnier@medasys-digital-systems.fr 564. mailto:Maciej.Macowicz@epfl.ch 565. mailto:Olivier_Martinet@hp.com 566. mailto:David.Mentre@irisa.fr 567. mailto:A.Nierula@t-online.de 568. mailto:Gilles_Noisette@hp.com 569. mailto:HARRY_PAGE@HP-NewZealand-om1.om.hp.com 570. mailto:pascal@montrouge.omnes.slb.com 571. mailto:Fons.Rademakers@cern.ch 572. mailto:Dirk.DeWachter@rug.ac.be 573. mailto:ndw@nwalsh.com Hidden links: 574. http://www5.zdnet.com/products/content/pcmg/1709/305867.html