diff --git a/LDP/howto/docbook/HOWTO-HOWTO.sgml b/LDP/howto/docbook/HOWTO-HOWTO.sgml deleted file mode 100644 index d0c676fc..00000000 --- a/LDP/howto/docbook/HOWTO-HOWTO.sgml +++ /dev/null @@ -1,1077 +0,0 @@ - -]> - - -
- - - HOWTO-HOWTO - - - v1.9 30 May, 2000 - - - Mark Komarinski - - - - List the tools, procedures, and hints to get HOWTO authors up to speed and writing. - - - - - - Introduction - - - - History - - - This document was started on Aug 26, 1999 by Mark F. Komarinski after two day's worth of frustration getting tools to work. If even one LDP author is helped by this, then I did my job. - - - - - New versions - - - The newest version of this can be found on my homepage http://www.cgipc.com/˜markk/in its SGML source. Other versions may be found in different formats at the LDP homepage http://www.linuxdoc.org/. - - - - - Comments - - - Comments on this HOWTO may be directed to the author (markk@linuxdoc.org). - - - - - Version History - - - v1.9 (May 30, 2000) - - - - - PSGML informaton added from Mark Craig - - - - - Differences between HOWTO and mini-HOWTO started - - - - - - - Copyrights and Trademarks - - - (c) 1999-2000 Mark F. Komarinski - - - This manual may be reproduced in whole or in part, without fee, subject to the following restrictions: - - - - - The copyright notice above and this permission notice must be preserved complete on all complete or partial copies - - - - - Any translation or derived work must be approved by the author in writing before distribution. - - - - - If you distribute this work in part, instructions for obtaining the complete version of this manual must be included, and a means for obtaining a complete version provided. - - - - - Small portions may be reproduced as illustrations for reviews or quotes in other works without this permission notice if proper citation is given. Exceptions to these rules may be granted for academic purposes: Write to the author and ask. These restrictions are here to protect us as authors, not to restrict you as learners and educators. Any source code (aside from the SGML this document was written in) in this document is placed under the GNU General Public License, available via anonymous FTP from the GNU archive. - - - - - - - Acknowledgements and Thanks - - - Thanks to everyone that gave comments as I was writing this. This includes Deb Richardson, Daniel Barlow, Greg Ferguson, Mark Craig and other members of the ldp-discuss list. Some sections I got from the HOWTO Index (available at many LDP locations) and the sgmltools documentation. The sections on network access to CVS was partially written by Serek (ser@serek.arch.pwr.wroc.pl). Sections on DocBook were written by Jorge Godoy (godoy@conectiva.com.br). A great deal of thanks to both of them for their help. - - - - - - Background on the LDP and SGML - - - - The LDP - - - The Linux Documentation Project (LDP) was started to provide new users a way of getting information quickly about a particular subject. It not only contains a series of books on administration, networking, and programming, but has a large number of smaller works on individual subjects, written by those who have used it. If you want to find out about printing, you get the Printing HOWTO. If you want to do find out if your Ethernet card works with Linux, grab the Ethernet HOWTO, and so on. At first, many of these works were in text or HTML. As time went on, there had to be a better way of managing these documents. One that would let you read it from a web page, a text file on a CD-ROM, or even your hand-held PDA. The answer, as it turns out, is SGML. - - - - - SGML - - - The Standard Generalized Markup Language (SGML) is a language that is based on embedding codes within a document. In this way, its similar to HTML, but there is where any similarities end. The power of SGML is that unlike WYSIWYG (What You See Is What You Get), you don't define things like colors, or font sizes, or even some kinds of formatting. Instead, you define elements (paragraph, section, numbered list) and let the SGML processor and the end program worry about placement, colors, fonts, and so on. HTML does the same thing, and is actually a subset of SGML. SGML has really two parts that make it up. First is the Structure, which is what is commonly called the DTD, or Document Type Definition. The DTD defines the relationship between each of the elements. The DocBook DTD, used to create this document, is an example of this. The DTD gives a common look and feel to each document that's created using the DTD. Second is the Content, which is what gets rendered by the SGML processor and is eventually seen by the user. This paragraph is content, but so would a graphic image, table, numbered list, and so on. Content is surrounded by tags to separate out each element. - - - - - Why SGML instead of HTML or other formats? - - - SGML provides for more than just formatting. You can automatically build indexes, table of contents, and links within the document or to outside. The Jade and OpenJade packages also lets you export (I'll call it render from here on) SGML to LaTeX, info, text, HTML, and RTF. From these basic formats, you can then create other formats such as MS Word, PostScript, PDF and so on. Programs like LyX allow you to write in TeX format, then export it as SGML and render from SGML to whatever you chose. In the end, SGML is more concerned about the way elements work instead of the way they look. A big distinction, and one that will let you write faster, since you don't have to worry about placement of paragraphs, font sizes, font types, and so on. - - - - - The tools - - - In this section, I'll go over some of the tools that you'll need or want to use to create your own LDP documentation. I'll describe them here, and better define them later on, along with how to install them. If you use some other tool to assist in writing LDP, please let me know and I'll add a blurb here for it. - - - - Jade - - - Required unless you use openjade - ftp://ftp.jclark.com/pub/jade/jade-1.2.1.tar.gz - - - Jade is the front-end processor for SGML. It uses the DSSSL and DocBook DTD to perform the verification and rendering from SGML into the target format. - - - - - OpenJade - - - Replacement for Jade - http://openjade.sourceforge.net/ - - - An extension of Jade written by the DSSSL community (see below for what a DSSSL is). Some applications require jade, but are being updated to support either software package. - - - - - DSSSL - - - Required - http://nwalsh.com/docbook/dsssl/db152.zip - - - The Document Style Semantics and Specification Language tells jade how to render a SGML document into print or online form. The DSSSL is what converts a title tag into an <H1> tag in HTML, or bold, 14 point Times Roman for RTF, for example. Documentation for DSSSL is located at http://nwalsh.com/docbook/dsssl/db152d.zip. Note that modifying the DSSSL doesn't modify DocBook itself. It merely changes the way the rendered text looks. The LDP uses a modified DSSSL that provides for a table of contents. - - - - - DocBook DTD (version 3.1) - - - Required - http://www.oasis-open.org/docbook/sgml/3.1/docbk31.zip - - - The DocBook DTD defines the tags and structure of a DocBook SGML document. Modifying the DTD, such as adding a new tag, doesn't make it DocBook anymore. - - - - - sgmltools-lite - - - Highly Recommended - http://sgmltools-lite.sourceforge.net/ - - - This is the successor to the sgmltools project, which has officially been disbanded for over a year. Since then, Cees de Groot has created a slightly different project, which acts as a wrapper to the jade SGML processor. It hides much of the ugliness of syntax. This author was able to install the old sgmltools package followed by the sgmltools-lite and could format this document quite easily. There's even a man page for sgmltools showing syntax. - - - - - TeX - - - Optional - - - TeX (rhymes with blech!) is the markup language of choice for many, including those in the mathematics world. I still remember many Calculus exams that were written in TeX. It is also one of the first markup languages that is still around (the other being the *roff formats used in man pages). TeX actually follows some of the same concepts that SGML does. However, TeX renders its files into DVI (Device Independent) that can then be rendered into another format. Unfortunately, DVI can't be easily converted into anything other than printer languages (PostScript, PCL), making it hard to use to generate HTML. TeX is installed or is available with most Linux distributions. TeX is available on almost all distributions as LaTeX or TeTeX. Either should work for you. - - - - - LyX - - - Optional - http://www.lyx.org/ - - - LyX provides the power of writing SGML with the ease-of-use of a regular word processor. It's not a WYSIWYG program, but more WYSIWYM (What You See Is What You Mean) application, since what you see on the screen isn't necessarily what happens after the SGML processor is done with it. The display that LyX provides is similar to, but not exactly like, what the output from jade would look like. However, it's close enough for you to see the flow of the document. Sections and subsections are numbered and put in bold, and different fonts are used to signify things like <code> or <url> tags. Most tags are hidden from the main LyX window while you edit, since LyX writes in TeX, then exports the TeX to SGML. - - - - - Emacs (PSGML) - - - Optional - http://www.lysator.liu.se/~lenst/about_psgml/ - - - Emacs has an SGML writing mode called psgml. Anyone with experience writing in this mode is welcome to e-mail the author of this document. psgml is a major mode in Emacs designed for editing SGML and XML documents. It provides "syntax highlighting" or "pretty printing" features that make SGML tag stand out, a way to insert "tags" other than typing them by hand, and the ability to validate your document while writing. For users of Emacs, it's a great way to go, and many believe it to allow more versatility than any other SGML documentation tool. It works with DocBook, LinuxDoc and other DTDs equally well. - - - - - WordPerfect 2000 - - - Not recommended - http://www.corel.com/ - - - WordPerfect 2000 for the MS Windows platform has limited support for SGML and DocBook 3.0. WordPerfect 2000 for Linux has no SGML capabilities. - - - - - DocBook: The Definitive Guide - - - Optional (but recommended) - http://www.docbook.org/ - - - This book was released by O'Reilly in October 1999, and is a great reference to DocBook. I have not found it to be a great practical book, and much of the emphasis is on XML, but the DocBook tags for version 3.1 are all listed in a handy format. You can pick it up at the book vendor of choice. The entire book is also available online at the above URL. - - - - - Aspell - - - Optional - http://aspell.sourceforge.net/ - - - This spell checking application can work around SGML tags, and only spell check the content within the tags. Default spell checkers like ispell will try to spellcheck the tags, causing errors at every new tag. - - - - - Cygnus DocBook Tools - - - Optional (may be Red Hat specific) - http://www.redhat.com/ - - - Red Hat distributes three packages, possibly starting with 6.2, that include DocBook support and some tools. They provide for only rendering to HTML and PDF, but they're easily installed if you have Red Hat, allowing you to focus more on writing than wrestling with the tools. TeTex 0.9, Jade, and Jadetex must be installed first. - - - - - - - Getting Started with DocBook - - - This section covers the new method of writing LDP documentation, using the DocBook 3.1 DTD. We'll cover getting, installing, and using tools, along with an introduction to DocBook tags. Since there are over 300 DocBook tags, we won't cover them all here. Really interested readers can go to http://www.docbook.org for more information. - - - - For New Authors - - - If you are a new to the LDP and want to pick up an unmaintained HOWTO or write a new HOWTO or mini-HOWTO document, contact the HOWTO coordinator at ldp-discuss@lists.linuxdoc.org. This is to make sure the HOWTO coordinator can know who is working on what documentation. Also note that all HOWTO submissions must be in SGML format using the DocBook 3.1 DTD. The mini-HOWTO submissions may be made in either SGML or HTML formats, but only SGML-formatted submissions will be included in printed versions of the HOWTOs. - - - - Should I write a HOWTO or mini-HOWTO? - - - The LDP has two sets of HOWTOs. The larger HOWTOs are always written in SGML (either DocBook or LinuxDoc - but DocBook is preferred). HOWTOs are usually large in scope, and longer than two or three printed pages. The mini-HOWTOs are smaller in scope, can be submitted in SGML or HTML, and take up only two or three printed pages. - - - - - - Mailing Lists - - - There are a few mailing lists to subscribe to so you can take part in how the LDP works. First is ldp-discuss@lists.linuxdoc.org, which is the main discussion group of the LDP. To subscribe, send a message with the subject reading "subscribe" to ldp-discuss-request@lists.linuxdoc.org. To unsubscribe, send an e-mail with the subject of "unsubscribe" to ldp-discuss-request@lists.linuxdoc.org. - - - - - Downloading and installing the tools - - - - Manual using jade/openjade - - - This is the quick and dirty way that should work for all distributions, no matter what distribution you're using. - - - - - Create a base directory to store everything such as /usr/local/sgml. We'll call this $_toolroot form here on. - - - - - Install Jade, DocBook DTD, and DSSSL such that the base of each is under $_toolroot (creating $_toolroot/jade-1.2.1, $_toolroot/dtd, $_toolroot/dssl) - - - - - You'll need to set the SGML_CATALOG_FILES environment variable to the catalogs that you have under $_toolroot. You can do this with the command: $ENV{'SGML_CATALOG_FILES'} = “$_toolroot/dtd/docbook.cat;$_toolroot/dsssl/docbook/catalog;$_toolroot/jade-1.2.1/dsssl/catalog” - - - - - Now you can start using Jade. To create individual HTML files: $_toolroot/jade-1.2.1/jade/jade -t sgml -i html -d $_toolroot/dsssl/docbook/html/docbook.dsl howto.sgml - - - - - To create one large HTML file, add -V nochunks to the jade command. - - - - - - - sgmltools - - - Unlike previous versions of sgmltools, you will require sgmltools version 2.x for use with DocBook. Since the backend programs have all changed, you'll also need to forget the sgml2xxx style of programs (sorry). Since most major distributions ship with sgml 1.x, you'll need to remove the sgml 1.x package and install either a 2.0 version, or a CVS version. To get the latest CVS source code version, you can use the following set of commands: - - -CVSROOT=:pserver:cvs@cvs.sgmltools.org:/home/cvs -export CVSROOT -cvs login -cvs -z6 get sgmltools - - - The CVS password is 'cvs'. Once downloaded, You can just use - - -./compile -make -make install - - - to install sgmltools. For Red Hat-based systems (using RPM) you can use the rpmfind command to get the latest sgmltools. The rpmfind program is available at http://www.rpmfind.net/. Make sure you get sgmltools and not sgml-tools, as the latter is sgml-tools 1.0.9. For Debian-based systems, apt-get will retrieve the right package for you: - - -# apt-get install sgmltools - - - As with the RedHat, be sure to get sgmltools and not sgml-tools. - - - - - Cygnus DocBook Tools - - - These tools are provided with Red Hat 6.2. Make sure the following packages are installed: - - - - - sgml-common - - - - - docbook - - - - - stylesheets - - - - - Red Hat has the latest version on their web site: http://www.redhat.com/support/errata/RHBA-2000022-01.html. - - - Download/get/sneakernet the RPMs to your machine and install in the usual manner (become root, then rpm -Uvh filename). Once the RPMs are installed, you can use the following commands to render DocBook: - - -db2html filename - - - Renders DocBook into HTML. A subdirectory with the filename (minus the .sgml extension) is created and the HTML files are placed there. - - -db2pdf filename - - - Renders DocBook into a PDF file. - - - - - - Writing SGML by hand - - - Must of this is covered by Jorge Godoy's Using DocBook document. Those interested can read it at http://metalab.unc.edu/godoy/using-docbook/using-docbook.html for writing DocBook using your favorite text editor. - - - - - Writing SGML using LyX - - - - New documents - - - You can easily start a new HOWTO using LyX. Use the File->New from template... menu command to bring up the template listings. Select Templates on the right side of the screen, then select docbook_template.lyx in the file listing. Select OK, and you'll have a new document. Fill in the items, such as title, abstract, and author name, then start writing. - - - - - Existing documents - - - If you have an already-existing LyX, TeX, or text document, you can import it into LyX with the File->import command. Once the file is imported, go to Layout->Document... In the popup window, under Style, select SGML (DocBook Article). You'll be asked if you want to convert all text over, and say Yes. You will need to reapply most tags, but it's a fairly simple matter of selecting text and changing the style. Many LyX functions have a keyboard shortcut to assist you. - - - - - Exporting documents to SGML - - - Once your document is written or converted, save it in LyX format. This will allow you to edit future versions easily. Then, go to File->Export->as DocBook... and the file will be exported in DocBook. - - - - - - Writing SGML using PSGML - - - - Introduction - - - If you have installed a recent distribution, you may already have PSGML installed for use with Emacs. To check, start Emacs and look for the PSGML documentation (C-h i m psgml). - - - From here on, we assume you have PSGML installed for use with a recent version of GNU Emacs. If that all went by too fast for you, see the free chapter from Bob Ducharme's SGML CD book: http://www.snee.com/bob/sgmlfree/. - - - - - Updating your .emacs to use PSGML - - - If you want GNU Emacs to enter PSGML mode when you open a .sgml file and be ready for SGML editing, make sure PSGML can find the DocBook DTD. If your distribution already had PSGML set up for use with GNU Emacs, you probably do not have to do anything to get this to work. Otherwise, you may need to set an environment varialbe that tells PSGML where to look for the SGML catalog (the list of DTDs). - - - For example: - - -bash$ export SGML_CATALOG_FILES=/usr/lib/sgml/catalog - - - Then add something like the following to your .emacs file: - - -;; ******************************************************************* ;; set up psgml mode... -;; use psgml-mode instead of emacs native sgml-mode ;; (autoload 'sgml-mode "psgml" "Major mode to edit SGML files." t ) -(setq auto-mode-alist (append (list '("\\.sgm$" . sgml-mode) '("\\.sgml$" . sgml-mode)) auto-mode-alist)) -;; set some psgml variables (setq sgml-auto-activate-dtd t) (setq sgml-omittag-transparent t) (setq sgml-balanced-tag-edit t) (setq sgml-auto-insert-required-elements t) (setq sgml-live-element-indicator t) (setq sgml-indent-step nil) -;; create faces to assign to markup categories (make-face 'sgml-comment-face) (make-face 'sgml-start-tag-face) (make-face 'sgml-end-tag-face) (make-face 'sgml-entity-face) (make-face 'sgml-doctype-face) ; DOCTYPE data (make-face 'sgml-ignored-face) ; data ignored by PSGML (make-face 'sgml-ms-start-face) ; marked sections start (make-face 'sgml-ms-end-face) ; end of marked sections (make-face 'sgml-pi-face) ; processing instructions (make-face 'sgml-sgml-face) ; the SGML declaration (make-face 'sgml-shortref-face) ; short references -;; view a list of available colors with the emacs-lisp command: ;; ;; list-colors-display ;; ;; please assign your own groovy colors, because these are pretty bad (set-face-foreground 'sgml-comment-face "coral") ;(set-face-background 'sgml-comment-face "cornflowerblue") (set-face-foreground 'sgml-start-tag-face "slateblue") ;(set-face-background 'sgml-start-tag-face "cornflowerblue") (set-face-foreground 'sgml-end-tag-face "slateblue") ;(set-face-background 'sgml-end-tag-face "cornflowerblue") (set-face-foreground 'sgml-entity-face "lavender") ;(set-face-background 'sgml-entity-face "cornflowerblue") (set-face-foreground 'sgml-doctype-face "lavender") ;(set-face-background 'sgml-doctype-face "cornflowerblue") (set-face-foreground 'sgml-ignored-face "cornflowerblue") ;(set-face-background 'sgml-ignored-face "cornflowerblue") (set-face-foreground 'sgml-ms-start-face "coral") ;(set-face-background 'sgml-ms-start-face "cornflowerblue") (set-face-foreground 'sgml-ms-end-face "coral") ;(set-face-background 'sgml-ms-end-face "cornflowerblue") (set-face-foreground 'sgml-pi-face "coral") ;(set-face-background 'sgml-pi-face "cornflowerblue") (set-face-foreground 'sgml-sgml-face "coral") ;(set-face-background 'sgml-sgml-face "cornflowerblue") (set-face-foreground 'sgml-shortref-face "coral") ;(set-face-background 'sgml-shortref-face "cornflowerblue") -;; assign faces to markup categories (setq sgml-markup-faces '((comment . sgml-comment-face) (start-tag . sgml-start-tag-face) (end-tag . sgml-end-tag-face) (entity . sgml-entity-face) (doctype . sgml-doctype-face) (ignored . sgml-ignored-face) (ms-start . sgml-ms-start-face) (ms-end . sgml-ms-end-face) (pi . sgml-pi-face) (sgml . sgml-sgml-face) (shortref . sgml-shortref-face))) -;; tell PSGML to pay attention to face settings (setq sgml-set-face t) -;; ...done setting up psgml-mode. ;; ******************************************************************* - - - Then restart Emacs - - - - - SGML Smoke Test - - - Try the following smoke test. Start a new file, /tmp/test.sgml for example, and enter the following: - - - -]> -]]> - - - Enter C-c C-p. If Emacs manages to parse your DTD, you will see Parsing prolog...done in the minibuffer. Try C-c C-e RETURN to insert a <test> element. If things are working correctly, you should see the following in Emacs: - - - -]> - -]]> - - - - - Writing a New HOWTO in DocBook - - - Start a new file for your HOWTO and enter the following: - - - ]]> - - - Enter C-c C-p and hold your breath. If everything goes as planned, you will see Emacs chewing for a few seconds and then Parsing prolog...done in the minibuffer. - - - At this point, enter C-c C-e RETURN to insert an <article> element and proceed to write your HOWTO. - - - - - Quick Reference for Emacs with PSGML - - - See Nik Clayton's primer for FreeBSD documentation: http://www.freebsd.org/tutorials/docproj-primer/psgml-mode.html - - - - - - - Getting Started with LinuxDoc - - - This section shows how to get involved in writing your own LDP documentation. Getting and setting up the tools, making contact with the LDP in general, and distributing what you know to all the Linux users out there. - - - - For New Authors - - - If you are a new to the LDP and want to pick up an unmaintained HOWTO or write a new HOWTO or mini-HOWTO document, contact the HOWTO coordinator at ldp-discuss@lists.linuxdoc.org. This is to make sure the HOWTO coordinator can know who is working on what documentation. Also note that all HOWTO submissions must be in SGML format (using DocBook or LinuxDoc DTD). The mini-HOWTO submissions may be made in either SGML or HTML formats, but only SGML-formatted submissions will be included in printed versions of the HOWTOs. - - - - - Mailing Lists - - - There are a few mailing lists to subscribe to so you can take part in how the LDP works. First is ldp-discuss@lists.linuxdoc.org, which is the main discussion group of the LDP. To subscribe, send a message with the subject reading "subscribe" to ldp-discuss-request@lists.linuxdoc.org. To unsubscribe, send an e-mail with the subject of "unsubscribe" to ldp-discuss-request@lists.linuxdoc.org. - - - - - Downloading and installing the tools - - - - sgmltools - - - Download the sgmltools package from http://www.sgmltools.org/, or directly from your distribution. The source files from sgmltools.org is in source code format, so you will have to compile the source code for your machine. Using a pre-built package for your distribution is easier, as you don't have to compile it and potentially run into compilation issues (that is, if you're not a coder). With RedHat, the sgmltools is included with the distribution. If not, you can download it from ftp.redhat.com or any of its mirrors as part of the main distribution. If you're using Debian, it too has sgmltools in the standard distribution. If you don't have the package installed, you can use the apt-get command to download and install the package for you: - - -# apt-get install sgml-tools - - - For more information on the Debian package, you can look at http://www.debian.org/Packages/stable/text/sgml-tools.html If compiling from source, all you need to do is: - - -# tar -zxvf sgmltools-x.x.x.tar.gz -# cd sgmltools-x.x.x -# ./configure -# make -# make install - - - Replace sgmltools-x.x.x with the actual version of the sgmltools package you're using. The current version as of this writing that supports LinuxDoc is 1.0.9. The version that supports DocBook is 2.0.2. Both are available at the above web site. Once the tools are installed, you have a number of commands available to you. - - - - - sgmlcheck file.sgml- Checks the syntax of a given document. - - - - - sgml2html file.sgml- Converts an SGML file into HTML. Creates a file.html file that contains the Table Of Contents, then creates file-x.html files where x is the section number. - - - - - sgml2rtf file.sgml- Converts an SGML file into Rich Text Format (RTF). Creates two files, the first being file.rtf that contains the TOC, and a file-0.rtf that contains all the sections. - - - - - sgml2txt file.sgml- Converts an SGML file into ASCII text. The TOC and all sections are all put into file.txt. - - - - - sgml2info file.sgml- Blah SGML blah INFO, used by the info command. All output is sent to file.info. - - - - - sgml2latex file.sgml- Blah SGML blah TeX. - - - - - sgml2lyx file.sgml- SGML yadda LyX graphical editor. This is great if you have pre-generated SGML files and want to convert them for use in LyX. - - - - - - - - Writing SGML by hand - - - Much like HTML, you can write SGML by hand, once you know all the markup codes you want to use. This section will go over as many of these codes as possible, along with practical examples of each. A nice place to start would be the SGML source for this document, which is available at the web site in the Introduction. As the SGML may be processed differently depending on the file format you go to, I'll try to list some things to know about as you're writing. - - - - Starting out - - - To start a new document, create a new file in your favorite ASCII editor and start with this: <!doctype linuxdoc system> This defines the document type (LinuxDoc in our case) that the SGML processor will use when it renders the file in an output format. Nothing is rendered from this tag. Next you need to enclose the rest of your work in <article> and </article> tags. This signifies the start of the content (or article, eh?). If you're familiar with HTML, this is similar to enclosing all your content with <html> and </html>. - - - - - Header information - - - The first part of the content should contain general information about the rest of the content. This would be similar to the first few pages of a book, where you have a title page (title of the work, author, date of publication, table of contents, and so on). The title of the content is enclosed in <title> and </title> tags. The author is specified in <author> and </author> tags. The date uses <date> and </date>. The two remaining sections are the <abstract> and </abstract> tags, which provide an executive summary of what the content is about, and the <toc> tag, which specifies the location of the table of contents. The TOC is automatically generated by the SGML processor. We'll get into sections later on. Now, how does it all look together? Taking a nice bit of SGML code (that is, what was used to create this document) you'll see: - - -<!doctype linuxdoc system> -<!-- LinuxDoc file was created by LyX 1.0 (C) 1995-1999 by <markk> Tue Dec 14 15:24:03 1999--> -<article> -<title>HOWTO HOWTO </title> -<author>Mark F. Komarinski </author> -<date>v1.1, 14 December 1999 </date> -<abstract>List the tools, procedures, and hints to get HOWTO authors up to speed writing. </abstract> -<toc> - - - This bit of content created the main page you see when you look at this document in RTF or HTML format, listing all the information on one page. - - - - - Sections - - - In order to build the Table of Contents, you need to have something to build with. Sections in the case of SGML is the same as chapters in traditional publishing. You have multiple sections, and each section can have a subsection, and each of those can have a subsection and so on. Starting your document with sections is great as it lets you create an outline of the major topics you want to cover. You can then break down these major sections into gradually smaller sections, until you have a nugget of information you can write about in a few short paragraphs. In writing this document, I actually started this way. Sections are one of the few sets of SGML tags that don't require to be closed. That is, there is no </sect> tag. Nor do you have to worry about numbering. The SGML processor will handle it all when you render the SGML into something else. Sections are started with <sect> tags. A new section is started with each <sect> tag. The first section is numbered 1. Creating subsections (like 1.1) is done with the <sect1> tag. It also starts with 1. Sub subsections (1.1.1) is done with the <sect2> tag, and also starts with 1. When the SGML processor comes across the <toc> tag, it runs through the rest of the document and builds the Table Of Contents based on the number of section tags within it. Sections are numbered and listed in the TOC and then used in the rest of the document. Sub subsections (1.1.1) do not show up in the TOC, but are put in emphasized text if possible. - - - - - Normal paragraphs - - - Writing paragraphs of content is just like in HTML. Use a <p> tag to specify a new line, and start writing. SGML will ignore whitespace such as tabs, multiple spaces, and newlines. When SGML comes across a <p> tag, it starts a new paragraph. Proper SGML has you put in a </p> to end the paragraph. - - - - - Enhanced Text - - - Every now and then you need a touch of text to stand out from the others. Either to highlight code or to list a command name. The first (emphasizing text) is done with <em> and </em> tags. Typewriter text (the second example) is done with <tt> and </tt> tags. - - - - - Lists - - - There are two forms of doing lists under SGML. First is an enumerated list, where each item in the list is numbered (like sections) starting with 1. 1. This is the first entry in the enumerated list. 2. This is the second. 3. Third. The code for the above list looks like this: <enum> <item>This is the first entry in the enumerated list. <item>This is the second. <item>Third. </enum> The <enum> tag specifies that the following items are going to be enumerated. The other method of writing lists is itemized, where each item merely has a star, or circle, or dot, or some other method of itemizing each item. - - - - - This is the first entry in the itemized list - - - - - This is the second - - - - - Third - - - - - The above code looks like this in raw SGML: - - -<itemize> -<item>This is the first entry in the itemized list -<item>This is the second -<item>Third -</itemize> - - - As you can see, the <item> tag is the same for enumerated and itemized lists. A third form of lists is the description lists. This has a term being described, and the phrase that describes it. LDP The Linux Documentation Project SGML Standard Generalized Markup Language The code to create the above descriptions is: <descrip> <tag>LDP</tag>The Linux Documentation Project <tag>SGML</tag>Standard Generalized Markup Language </descrip> This isn't quite the same as itemized or enumerated lists, but you have the entire list surrounded by a tag (<descrip> and </descrip>) and each item in the line that is a word being defined is enclosed in <tag> and </tag>. The remainder of the line is taken to be the definition of the word. - - - - - Verbatim text - - - Sometimes you just need to print some text the way you write it. For this, you can use the <verb> and </verb> tags to enclose a paragraph in verbatim mode. Spaces, carriage returns, and other literal text (including special characters) are preserved until the </verb>. This is verbatim text. - - - - - URLs - - - Also in SGML is the ability to handle Universal Resource Locators (URL) of any kind. Note that this would only work when exported to HTML mode, but other formats may use them as well. A URL doesn't have an end tag, but puts its information within the <url> tag itself. Here is a URL that points to the LDP homepage: http://www.linuxdoc.org/. And here's the code to create it: <url url="http://www.linuxdoc.org/" name="http://www.linuxdoc.org/"> The url=\"{}http://www.linuxdoc.org/\"{} tells the browser where to go, while the contents of the name=\"{}http://www.linuxdoc.org/\"{} tells the browser what to print out to the screen. In this case, the two are similar, but I could create a URL tag that looks like this: <url url="http://www.linuxdoc.org/" name="LDP"> And then looks on the page like this: LDP. However, good form suggests that you duplicate the URL in the name portion. The reason for this is if you're using something like Text or RTF output, the above tag would have no meaning. you wouldn't know what URL to use. - - - - - References - - - While URLs are great for linking to content outside the LDP document you're working on, it's not that great for linking within the content itself. For this, you use the <label> and <ref> tags. The <label> tag creates a point in the document where you want to refer back to later on, almost like a bookmark. Creating the <label> is easy. Find the point where you want to refer back to later on, and insert the following: <label id="Introduction"> You have now created a point in the content that you can refer to later on as "Introduction". This label actually appears in this SGML work at the front of the document. When you want to refer back to that point later on (say the section called Introduction (here)), you insert the following SGML: <ref id="Introduction" name="here"> and the SGML will know to put in a link called "here" (see above) that links back to the location of the Introduction section. The other part of references is indexing. Since LDP documentation is usually published on paper as a large collection of documents, there needs to be a way of building the index at the back of the book, based on words and subjects. - - - - - Special characters - - - Much like HTML, you will need to escape many non-alphanumeric characters to prevent the SGML processor from interpreting them as SGML code. Here's a list of the SGML codes used. More are listed in the sgmltools User's Guide located at http://www.sgmltools.org/guide/guide.html. - - - - - Use &amp; for the ampersand (&) - - - - - Use &lt; for a left bracket (<) - - - - - Use &gt; for a right bracket (>) - - - - - Use &etago; for a left bracket with a slash (</) - - - - - Use &dollar; for a dollar sign ($) - - - - - Use &num; for a hash (#) - - - - - Use &percnt; for a percent (%) - - - - - Use &tilde; for a tilde (˜) - - - - - Use " and " for quotes, or use &dquot for - - - - - Use &shy; for a soft hyphen (that is, an indication that this is a good place to break a word for horizontal justification). - - - - - - - - - CVS - - - The LDP is in the process of providing CVS access to authors. There are a few good reasons for using CVS: - - - - - CVS will keep an off-site backup of your documents. In the event that you hand over a document to another author, they can just retrieve the document from CVS and continue on. In the event you need to go back to a previous version of a document, you can retrieve it as well. - - - - - It's great if you have many people working on the same document. You can have CVS tell you what changes were made while you were editing your copy by another author, and integrate those changes in. - - - - - Keeps a log of what changes were made. These logs (and a date stamp) can be placed automatically inside the document when you use some special tags that get processed before the SGML processor. - - - - - Can provide for a way for a program to automatically update the LDP web site with new documentation as it's written and submitted. This is not in place yet, but is a potential goal. - - - - - If you're completely new to CVS, there are a few web pages you may want to look at which can help you out: - - - - - http://www.sourcegear.com/CVS/Docs/blandy - - - - - https://wroclaw.art.pl/~ser/docs/cvs.html - - - - - - Getting a CVS account - - - First you'll need to get an account at the LDP's CVS Repository. This is pretty much the root directory that is used by CVS, with various projects (HOWTOs, mini HOWTOs, etc.) created as subdirectories of that. - - - You will need to create a hashed password and userid for your account. The hashed password allows you to send an encrypted password to the CVS group without them needing to know your password. You can do this with the following command, from bash (or sh): - - -$ echo put_your_password_here | perl -e "print crypt(<>, join '',('.', '/', 0..9, 'A'..'Z', 'a'..'z')[rand 64, rand 64]),\"\n\"" - - - Take the output of this command, and send it with your proposed userid to cvsadmin@cvslist.linuxdoc.org. Your unique CVSROOT will be created and you'll get an e-mail with a response. When you get your response, log into your CVSROOT and make sure everything is set up properly: - - -$ export CVSROOT=:pserver:your_userid@cvs.linuxdoc.org:/cvsroot -$ cvs -d $CVSROOT login - - - (Replace the CVSROOT with what you were sent in the response e-mail). - - - You will be asked for your password, and then given access to the CVS Repository in read-write mode. Once you've used cvs login once and have been given access to the system, your password is stored in .cvsroot and you will not have to use cvs login again. Just set the CVSROOT and continue on. You can get the entire linuxdoc repository with this command: - - -$ cvs get LDP - - - Or you can get the SGML source for your own document with these commands: - - -$ cvs get howto/YOUR-HOWTO.sgml -$ cvs get minihowto/YOURDOC.sgml - - - Also available is The Commit List, which is an e-mail sent for each change anywhere in the repository. Note that this is a high-volume list. You can subscribe by sending an empty e-mail to commits-subscribe@cvslist.linuxdoc.org. You can unsubscribe by sending an empty e-mail to commits-unsubscribe@cvslist.linuxdoc.org. - - - - - Other CVS repository notes - - - - Anonymous CVS access - - - Anonymous CVS access (read-only) is available: - - -$ cvs -d :pserver:cvs@anoncvs.linuxdoc.org:/cvsroot login - - - As a password, use cvs. You can then get linuxdoc modules as above. Note that changes to the anoncvs site may be a half an hour behind the main site. - - - - - CVS Files via web - - - You can access the CVS repository via the web at http://cvsweb.linuxdoc.org/index.cgi/linuxdoc. - - - - - Graphical access to CVS - - - There are graphical interfaces to CVS, and you can get a list of them at http://freshmeat.net/appindex. Search for CVS. - - - - - - Updating files and CVS - - - CVS has a special tag that you can use to automatically insert the date and version directly into the document. This is called $Id$. By including this tag in your document, you can have that automatically change each time you change the file, allowing the revision mark to increment each time. - - - When you're ready to upload changes to the CVS server, use the command cvs ci -m "comment" YOUR-HOWTO.sgml. The -m "comment" isn't necessary, but if you don't include it, you'll be brought into the editor (usually vi, or whatever your EDITOR environment variable is) and be given the chance to add a comment about the changes. - - - You can follow more of the CVS discussion on the ldp-discuss list. For the time being, LDP submissions should still be sent to ldp-submit. - - - - - - Distributing your documentation - - - - Before you distribute - - - Before you distribute your code to millions of potential readers there are a few things you should do. - - - First, be sure to spell-check your document. Most utilities that you would use to write SGML have plug-ins to perform a spell check. If not, there's always the aspell program. - - - Second, get someone to review your documentation for comments and factual correctness. The documentation that is published by the LDP needs to be as factually correct as possible, as there are millions of Linux users that may be reading it. If you're part of a larger mailing list talking about the subject, ask others from the list to help you out. - - - Third, create a web site where you can distribute your documentation. This isn't required, but is helpful for people to find the original location of your document. - - - - Validate your SGML code - - - Using sgmltools, or really the nsgmls command, you can validate your .sgml code against the DTD to make sure there aren't any errors. - - -nsgmls -s HOWTO-HOWTO.sgml - - - If there are no issues, you'll just get your command prompt back. - - - - - - Copyright and Licensing issues - - - In order for an LDP document to be accepted by the LDP, it must be licensed to allow for free (as in beer) distribution and publishing. As an author, you may retain the copyright and add other restrictions (for example, you must approve any translations or derivative works). A sample license is available at http://www.linuxdoc.org/COPYRIGHT.html. If you choose to use the boilerplate copyright, simply copy it into your source code under a section called "Copyright and Licenses" or similar. Also include a copyright statement of your own (since you still own it). If you are a new maintainer for an already-existing HOWTO, you must include the previous copyright statements of the previous author(s) and the dates they maintained that document. - - - - - Submission to LDP - - - Once your LDP document has been reviewed by a few people and you took into account their comments, you can release your document to the LDP. Send an e-mail with the SGML source code as an attachment (you may gzip it if you like) to ldp-submit@lists.linuxdoc.org. - - - Be sure to include the name of your HOWTO in the subject line, and use the body to outline changes you've made and attach your HOWTO. This allows the maintainers to do their jobs faster, so you don't have to wait for your HOWTO to be updated on the LDP web site. If you don't hear anything in 7 calendar days, please follow up with an e-mail to make sure things are still in process. - - - - - Style guides - - - This section contains notes on conventions that the LDP has agreed to in order to give all LDP documents a similar look and feel. You should keep these guides in mind when writing. - - - - Date formats - - - The <date> tag in your header should be in the following format: - - -v1.0, 21 April 2000 - - - - - - - FAQs about the LDP - - - - I want to help the LDP. How can I do this? - - - The easiest way is to find something and document it. Also check the unmaintained HOWTOs and see if there is a subject there that you know about and can continue documenting. - - - - - I want to publish a collection of LDP documents in a book. How is the LDP content licensed? - - - Please see http://www.linuxdoc.org/COPYRIGHT.html. Note that this is only a guideline to authors. - - - - - I found an error in an LDP document. Can I fix it? - - - Contact the author of the document, or the LDP coordinator at ldp-discuss@lists.linuxdoc.organd mention the problem and how you think it needs to be fixed. - - - - - -
diff --git a/LDP/howto/docbook/HP-HOWTO.sgml b/LDP/howto/docbook/HP-HOWTO.sgml deleted file mode 100644 index 454ebecd..00000000 --- a/LDP/howto/docbook/HP-HOWTO.sgml +++ /dev/null @@ -1,6559 +0,0 @@ - - - - - - - - - - - - - - - - - &ref; -'> - - &tabi; Linux. -'> - &tabi; XFree86. -'> - Linux support -'> - Tes-ted -'> - - - - - - - - - - - - - -Machine -Graphic Card -&celpec; -&celnet; -&celpec; -&celscsi; -&celpec; -&celson; -&celpec; -&celtest; - - -'> - - - - - - - -Simultaneous users -RAM size -Disk size -Machine example - - -'> - - - - - - - - - - - -&celref; -Name -Vert. F. (Hz) -Hor. F. (kHz) -Bandwidth (MHz) -Resol -Freq. (Hz) -&celtest; - - -'> - - - - - - - - -&celref; -Card type -Chipset -&celpec; -&celtest; - - -'> - - - - - -Subject -URL - - -'> - Rem. -'> - Rem. -'> - Rem. -'> - Rem. -'> - Rem. -'> - Rem. -'> - Rem. -'> - Rem. -'> - &oui; &xfree86; (SVGA) -'> - &oui; &xfree86; (S3) -'> - S3 Trio 64V2 PCI -&celsvga; -'> - Matrox Millenium II PCI -&celsvga; -'> - Matrox Millenium II AGP -&celsvga; -'> - Matrox Productiva G100 AGPRem. -&celsvga; -'> - Matrox Productiva G200 AGP -&celsvga; -'> - Matrox Millenium G200 AGP -&celsvga; -'> - Matrox Millenium G250 AGP -&celbof; -'> - Matrox Millenium G400D AGP -&celsvga; -'> - ATI Rage II C AGP -&oui; &xfree86; (Mach 64) -'> - ATI Rage Pro ZX AGP -&oui; &xfree86; (Mach 64) -'> - ATI Rage LT Pro -&oui; &xfree86; (Mach 64) -'> - ATI -&celbof; -'> - Sis 5595 AGP -&oui; &fb; -'> - Cirrus Logic GD 5424 PCI -&oui; &xfree86; (SVGA) -'> - Cirrus Logic GD 5446 PCI -&celsvga; -'> - Cirrus Logic GD 5465 AGPRem. -&oui; &xfree86; (SVGA) -'> - Elsa Gloria SynergyRem. -&oui; &xfree86; (3D Labs) -'> - Elsa Gloria Synergy + AGPRem. -&oui; &xfree86; (3D Labs) -'> - Elsa Gloria Synergy II AGP -&oui; &xfree86; (SVGA) -'> - 3DLabs Oxygen GVX1 AGP -&oui; &fb; -'> - Neomagic MagicGraph 128XD NM2160 -&celsvga; -'> - Neomagic MagicGraph 256AV NM2200 -&celsvga; -'> - Chips & Technologies CT65554 -&celsvga; -'> - Silicon Motion LynxE SM810Rem. -&celsvga; -'> - Accel Eclipse PCI -&oui; &fb; &nointer; -'> - Accel Galaxy AGP -&oui; &fb; &nointer; -'> - HP Fx-4 AGP -&non; &fb; &nointer; -'> - HP Fx-6 AGP -&non; &fb; &nointer; -'> - Intel i810 AGPRem. -&oui; &xfree86; (XFCom i810) -'> - Trident TVGA 9000i -&celsvga; -'> - Intel i82557 / i82558 10/100 BT (D5013A/B) -&oui; &pilote; eepro-100 -'> - Intel S82093A / i82559 10/100 BT -&oui; &pilote; eepro-100 -'> - Carte 100VG (J2585B) -&oui; &pilote; hp100 -'> - Carte HP chipset RealTek -&oui; &pilote; RealTek -'> - &oui; &pilote; 3c59xRem. -'> - - 3Com 905B-TX 10/100 BTRem. -&celpilote3com; -'> - 3Com 905C-TX 10/100 BT -&celpilote3com; -'> - &oui; &pilote; pcnet32 -'> - AMD 79C971 KC 10/100 BT -&celpcnet; -'> - AMD 79C972 AKC 10/100 BT -&celpcnet; -'> - SMC 1211 TX EZ Card 10/100 BT -&oui; &pilote; rtl8139 -'> - AMI Megaraid (Raid 0, 1, 3, 5, 10, 50) -&oui; &pilote; megaraidRem. -'> - &oui; &pilote; ncr-53c8xxRem. -'> - AMD 79C971 KC 10/100 BT + SCSI (D6692A)Rem. -&celpcnet; -Symbios Logic 53c875 &avec; &net; (D6692A) -&celncr53; -'> - AMD 79C974 KC 10/100 BT + SCSI -&celpcnet; -Symbios Logic 8751SP &avec; &net; -&celncr53; -'> - Adaptec ARO Raidport -&celnon; -'> - Adaptec AIC 7860 PCI + Adaptec AIC 7880 UW PCI -&oui; &pilote; aic7xxx -'> - Adaptec AIC 7880 UW PCI -&oui; &pilote; aic7xxx -'> - Adaptec AIC 7880 UWD PCI -&oui; &pilote; aic7xxx -'> - 2 Adaptec AIC 7880 UW PCI -&oui; &pilote; aic7xxx -'> - Adaptec AIC 7895H PCI -&oui; &pilote; aic7xxx -'> - Adaptec AIC 2910bui (7860) PCI -&oui; &pilote; aic7xxx -'> - Adaptec AIC 7880 PCI + Symbios Logic 53C876 -&oui; &pilote; aic7xxx &et; &pilote; ncr53c8xx -'> - Symbios Logic 8952U Ultra2 Wide PCI -&celbof; -'> - Symbios Logic 53C895 PCI -&celncr53; -'> - 2 Symbios Logic 53C895 PCI -&celncr53; -'> - Adaptec AIC 7880 PCI + 2 Symbios Logic 53C896 PCI -&oui; &pilote; aic7xxx &et; &pilote; ncr53c8xx -'> - AMD 79C972 10/100 BT + SCSI (D6692A)Rem. -&celpcnet; -Symbios Logic 53c875 &avec; &net; (D6692A) + Adaptec AIC 7880 PCI -&oui; &pilote; ncr53c8xx &et; &pilote; aic7xxx -'> - 2 Symbios Logic 53C896 PCI -&celncr53; -'> - 2 Symbios Logic 53C897 PCI -&celncr53; -'> - Cirrus Logic CS 4614 -&celbof; -'> - Crystal CS 4232 -&celbof; -'> - Analog Device 1816 -&oui; &pilote; AD1816Rem. -'> - Xircom CEM56-100 56Kb 10/100 BT -&oui; &pilote; xirc2ps_cs -'> - 3Com 3CXFE575BT 10/100 BT -&celbof; -'> - Network Card -'> - Sound Card -'> - SCSI Card -'> - Modem Card -'> - Modem/Net Card -'> - FastRaid Card -'> - NetRaid Card -'> - Top Tools Card -'> - Fibre Channel Card -'> - &aucune; -N/A -'> - N/A -'> - ??? -'> - - &non; -'> - &oui; -'> - RedHat -'> - Hewlett-Packard -'> - Medasys -'> - SaMBa -'> - Apache -'> -]> - - - - -HP HOWTO - - - - -Utilisation and Configuration Guide of HP Products under Linux - - - - - - -in its latest version the -&curdate; (Version &curver;) - - - -This document describes the use of products available in &HP; (HP) catalog with Linux and some free software. -It gives the state of the support for hardware, software to use, answers to some frequently asked questions and gives elements of sizing. -The goals are to offer a general view of free software functions and their use at best with HP products; as well as to make new users of HP products rapidly operational and also to allow others to choose their products knowing facts. - - - - -Bruno -Cornec - -Medasys Digital Systems -
Bruno.Cornec@medasys-digital-systems.fr
- - - -1997-2000 -Bruno Cornec - - -License - - - - - - -This HOWTO is a free documentation thanks to &Medasys; and &HP; for whom I do that job; you may redistribute and/or modify it under the terms of the - - - - -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. - - - - - - 0.8 - - - -The 25th of July, 1999 - - -Bruno Cornec - - -First version publically available - - - - 0.85 - - - -The 7th of September, 1999 - - -Bruno Cornec - -Docbook 3.1. - - -Monitors section. -A lot of typos corrected -Numerous links added -Makefile rewritten. - - - - 0.86 - - - -The 27th of September, 1999 - - -Bruno Cornec - - - -August and September 1999 machines. -DSSSL 1.45 + own StyleSheet. -Makefile adapted. - - - - - 0.87 - - - -The 19th of January, 2000 - - -Bruno Cornec - -Informations on new machines Oct 1999-Jan 2000. -ENTITY for Apache, RedHat, Samba, ... -Use of an own DSSSL and DTD. - - - - - - 0.88 - - - -The 15th of March, 2000 - - -Bruno Cornec - -Informations on new machines Feb-Mar 2000. -English translation. - - - - - - - - - - - -Introduction - - -Presentation - - - - -This document is a guide on the use of products proposed by the hardware manufacturer - - &HP; (HP) - - -under Linux. -It's a quick reference guide, covering all what you need to know to size, install and configure your products under Linux, or which complementary software will be usefull for their use. -Frequently Asked Questions find answers, and references are given concerning other sources of information related to HP technologies and applications. - - - - - -Opinions expressed here are those of the author, and don't commit both - -&Medasys; &ou; &HP;. - - -Informations are provided in the aim to be useful to the readers. -However, there can't be, through this document, any warranty of any kind either from &Medasys; &ou; &HP; on these systems under Linux, as well as from myself. -Neither &Medasys;, nor &HP;, nor the author could be responsible for any problem caused by the use of these informations. -However, software editors don't garantee you a lot either (re-read the contracts). - - -New versions of this document - - - -New versions of this document will be announced regularly on the Usenet groups - -news:fr.comp.os.linux.annonces &et; 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 - -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 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 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 - -. - - -I would like to thank just now, without any particular order, those without whom this document would simply not exist : - - - - -Marc Hia Balié Marc_Hia-Balie@hp.com, - - -who ordered that document and accepted to make it a free documentation. - - - - -Linus Torvalds, - - -for the Linux project (without it, nothing would exist). - - - - - -Richard Stallman, - - -for the GNU project (without it, nothing would exist either). - - - - - -Nat Makarévitch nat@nataa.frmug.org, - - -For his work as translator and his advocacy conferences. - - - - - -Xavier Cazin xc@itp.fr, - - -for his talent to convince me to use DocBook. - - - - - -Eric Dumas dumas@Linux.EU.Org, - - -for the management of the french LDP. - - - - - -Rémy Card 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 Dany.Coffineau@alcatel.fr, - - -for teachnig me Unix. - - - - - -François Strobel Francois.Strobel@alcatel.fr, - - -for his peacefulness and legendary patience :-) - - - - -Frédéric Dubuy 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 pascal@montrouge.omnes.slb.com, - - -for the several tests made. - - - - -Pascal Lemonnier Pascal.Lemonnier@medasys-digital-systems.fr - - -typography expert who found a lot of typos. - - - -Ralf S. Engelschall rse@engelschall.com, - - -who realised the - -wml - - - tool set, used to manage the languages of this document. - - - -Cees de Groot cg@sgmltools.org, - - -who realised the - -SGMLTools - - -tools set, which allow to generate all the versions of this document from a single SGML source. - - - -Norman Walsh ndw@nwalsh.com, - - -who realised the SGML DTD - -DocBook. - - -James Clark jjc@jclark.com, - - -who realised the tool - -Jade. - - - - Cornec familycornec@victoria.frmug.org, - - -for his patience and his support. - - - - - - - - - - - - -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. - - - -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. - - - - -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. - - - - - - -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 &Apache; Web server, the &Samba; SMB server, GNU C and C++ compilers ... -A contrario, examples of well-known freeware are the Internet Explorer browser, the Eudora Light mail reader, ... - - - - - -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 &et; 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 &curker; (this last number may evolve following the rythm of corrections). -Development has on the other side begun again with a 2.3 version currently in code freeze. - - - - - - -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.html. - - - -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 : - -Système V, BSD, Sun, MS-DOS, VFAT, NTFS, Mac, HPFS, EFS, ISO9660. - - -On the network side, it supports the following protocols - -TCP/IP v4 &et; v6, Appletalk, Netware (client &et; server), Lan Manager SMB (client &et; server), X-Window, NFS, PPP, SLIP, UUCP. - - - - - - -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 - - . - - - - - -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 : - - - - - - -Linus Torvalds, - - -conceptor of Linux. - - - - - -Richard Stallman, - - -GNU project conceptor. - - - - - - -Eric S. Raymond, - - -writer of several and excellent articles, which inspired so many vocations. - - - - - -Larry Wall, - - -author of Perl and of the patch tool, and philosopher. - - - - - -Tim O'Reilly 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 - - (&Apache; Web Server and competitors, SMB &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. - - - -
- - - -Server operating system repartition in 1998 (IDC). - - - -
- - - - -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. - -
- - - -Server operating system repartition in 1999 (IDC). - - - -
- - - - - - - Dataquest 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 - -Netcraft, - - -on web server software, and by - -IOS Counter - - -for the servers on Internet. -Results, reproduced below, show the importance taken by &Apache; with more than 6 millions of operational sites, crushing the competition, as well as the free operating systems Linux and *BSD which dominate the world of Internet servers. - -
- - - -Web server software by Netcraft between 1995 and 2000. - - - -
-
- - - -Repartition of Internet servers by IOS Counter in April 1999. - - - -
- - - - - - - -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 (&Apache;), FTP server (Wu-Ftpd), DNS server (Bind), the E-Mail server (Sendmail &ou; Postfix), the Usenet groups server(INN), the proxy server (IPmasqadm), the firewall (IP-Chains), Virtual Private Network (OpenSSH, Linux kernel), the Cache server for the Web (Squid) or also the Time server (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 - -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 - -NFS &et; KNFS &ou; also Coda, - - -for file sharing and of - - lpd - - -for print service), Microsoft Windows type (use of - -&Samba;, - - -which allows also the use of local client printers) or MacIntosh type (use of - -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 - -multi-processors, - - -linked to the realisation of - -clusters with multiple nodes - - -with high-speed network interfaces - - (100 Mbit/s, Gigabit &ou; Myrinet), - - -those of data security with the support of - -HP NetRaidRem. - - -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 - -HylaFAX - - -or also as an archive/backup server with HP SureStore DAT or DLT libraries thanks to a commercial software like - -Arkeia - - -or at last as a database server with free solutions like - -PostgreSQL,MySQL &ou; commercial like 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 - - (Netscape) &ou; textual (lynx), - - -a lot of graphical mail readers - - (Kmail, XFMail, ...) &ou; textual (mutt, elm, ...). - - -But you also have the whole panel of indispensable tools for a personal computer today as a PDF reader - - (Acrobat Reader &ou; xpdf), - - -image manipulation tools - - (ImageMagick, the Gimp, RealPlayer tools ...), - - -word processors - - (LyX, LaTeX, SGMLTools, Wordperfect, ...), - - -commercial office suites - - (ApplixWare, StarOffice), - - -sound management tools - - (WavTools, eplaymidi, xmcd, ...), - - -CD burning tools - - (cdrecord, BurnIT, ... with complements as mkisofs, cdparanoia), - - -free and commercial emulators for various systems - - (Wine, Executor, WABI, DOSEmu, ...), - - -compilers and interpretors for all the languages - - (C, C++, Pascal, Fortran, Basic, Tcl/Tk, Perl, Python, Ada, Eiffel, Lisp, Scheme, Prolog...), - - -including commercial versions ( - - PGI, ...), - - -graphical environments - - (Gnome, KDE, 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 - - SGMLTools, Jade &et; DocBook, - - -which allowed to generate from a single source the formats - - HTML, Txt, RTF, PostScript, &et; 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 &RedHat; provides today support for their solutions. -Only in France, we may mention firms like - -&Medasys;, Atrid, Alcove - - -which assure support on free software. -Likewise, always in France, training on free software may be given by - -HP France, Learning Tree, the IUT de Vélizy, - - -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 Linux Documentation Project made of FAQ (Frequently Asked Questions) and HOWTO, counting more than 300 documents around Linux, the main being - - 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 - -O'Reilly &et; 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 - -Hardware Compatibility List - - -of Microsoft, for Linux it's also greatly recommended to verify the - -Hardware HOWTO, - - -and for HP machines to refer to this - -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 - -Voila (France Telecom) or the engine Deja - - -among other prestigious references. -As well, FreeBSD is used with success as the world biggest ftp server : - -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 - -&RedHat;, SuSE, Slackware, enMandrake, Turbo Linux, 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 &et; 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 &et; 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 &et; 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 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. - - - - - - - - - - - -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 Jacques_Misselis@hp.com, hosted by l'Ecole Centrale de Lyon at the address http://hpwww.ec-lyon.fr/hpeduc/education. - - - - -On the other side, the firm - -&Medasys;, - - -for which I work, put at disposition of the community a certain number of informations since 1997, available at - -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 - -White Paper HP Linux Strategy. - - - - -HP is a member of - -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=314 - - - - - - -Availability of Apache on HP 3000 (Summer/1999) - - - -http://www.businessservers.hp.com/falladvisor/sum99/Summer99/apache.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.html - - - - - - -Aberdeen group analysis on HP position on free software (08/09/1999) - - - -http://internetsolutions.enterprise.hp.com/linux/news/aberdeen_white_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 - - - - -&Medasys; - - -chosen by Hewlett-Packard France Education/Research as Linux competence center - - - -http://hpwww.ec-lyon.fr/hpeduc/education/offre/linux/educ_linux.html - - - - - - -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 &curker;. 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 - -&curdate;. - - - - - -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 - -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 - -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 : - - - - -Brio &et; Linux -&tabmach; - - -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) -&cels3triov2; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Brio (D6810A, D6812A) -&celatipro; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Brio (D6638A, D6639A, D6640A, D6644A, D7901A, D7902A, D6645A, D6646A) &chipbx; -&celatipro; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Brio (D5841A, D6516B) -&celmilii; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Brio (D6760A, D7671A, D6908A, D7930A, D7672A, D7925T, D6776A, D6769A, D6755A, D6895A, D6896A, D6897A, D7931A) -&celmilg100; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - - -Brio BA (D7581A, D7584A, D7585A, D7587A, D7586A, D7591A, D7594A, D8411A) -&celsisagp; -&celsans; -&celsans; -&celcs4614; -&celnon; - - - -Brio BAx (D7600A, D7603A, D7624A, D7625A, D7630A, D7610A)Rem. -&celmilp200; -&celsans; -&celsans; -&celcs4614; -&celoui; - - - -Brio BAx (D7605A)Rem. -&celmilp200; -&celinconnu; -&celsans; -&celcs4614; -&celnon; - - - -Brio BA400 (D8767A, D8769A, D8934A, D8935A, D8936A, D8943A, D8947A, D8952A, D8953A, D9720A, D9721A) -&celi810; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Brio BA600 (D8773A, D8778A, D8788A, D8789A, D9070A, D9072A, D9080A, D9082A, D9085A, D9091A)&chipbx; -&celmilp200; -&celsans; -&celsans; -&celcs4614; -&celoui; - - - -Brio BA600 (D8774A, D9075A)&chipbx; -&celmilp200; -&celinconnu; -&celsans; -&celcs4614; -&celnon; - - - - -
- - -Vectra &et; Linux -&tabmach; - - -Vectra VE5 (D5592A, D5602A, D5603A, D5604A, D5606N, D5608A, D5612A, D5615A, D5618A, D5607A, D5617A) -&cels3triov2; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VE7 (D6530A, D6531A, D6533A, D6610A, D6611A, D6615A, D6616A, D6613A) -&celati2c; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VE7 (D6532A, D6612A, D6617A, D6618A) -&celati2c; -&cel3com; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VE8 (D6550A, D6560A, D6570A, D6554A, D6584A, D6540A, D6541A, D6544A, D6543A, D6578A, D6573A, D6574A, D6580A,D6581A, D6584A, D6583A, D6593A, D6597A, D6598A) &chipbx; -&celmilg100; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VE8 (D6552N, D6562N, D6565N, D6542A, D6572A, D6575A, D6582A, D6595A, D6582A, D6585N, D6599A) &chipbx; -&celmilg100; -&cel3com; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VEi7 (D8121A, D8123A, D8124A, D8126A, D8128A, D8129A, D8131A, D8133A, D8134A, D8136A, D8138A, D8139A, D8141A, D8143A, D8144A, D8145A, D8148A) -&celsisagp; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VEi7 (D8122A, D8127N, D8132A, D8137A) -&celsisagp; -&cel3com; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VEi8 (D8166A, D8168A, D8151A, D8153A, D8155A, D8169A, D8171A, D8173A, D8174A, D8181A, D8183A, D8184A, D8186A, D8188A, D9784A, D9786A, D9788A, D9793A) -&celmilp200; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VEi8 (D8167N, D8152N, D8172N, D8182N, D8187N, D9787N) -&celmilp200; -&cel3com; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL5 (D4552A, D4543A, D4554A, D4555A, D4556A, D4557A, D4558A, D4559A, D4560A, D4567A, D4562A, D4563A, D4572A, D4574A, D4576A, D4579A, D4577A) -&cels3triov2; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VL6 -&celcl5446; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VL6 -&celmilii; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL7 (D5710A, D5711N, D5725A, D5720A, D5721N, D5731N, D5797N, D5737A, D5799N) -&celcl5465; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Vectra VL7 (D5734N, D5729N, D5739N, D5728N, D5798N) -&celmilii; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL7 (D5724N, D5796N) -&celcl5465; -&celamd; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL8 (D5880A, D5882A, D5890A, D5891A, D5893A, D5896A, D5898A, D5900A, D5902A, D6945A) &chipbx; -&celmilg100; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL8 (D5881A, D5883A, D5894A, D5888A, D5892A) &chipbx; -&celmilg100; -&cel3com; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL8 (D5887A) &chipbx; -&celmilg100; -&cel3com; -&celinconnu; -&celinconnu; -&celnon; - - - -Vectra VL8 (D6944A) &chipbx; -&celmilg200; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL8 (D6940A, D6941A, D6942A) &chipbx; -&celmilg200; -&cel3com; -&celsans; -&celinconnu; -&celnon; - - - -Vectra VL8 (D6943A) &chipbx; -&celmilg200; -&cel3com; -&celaic7880; -&celinconnu; -&celoui; - - - -Vectra VLi8 (D7941A, D7943A, D7945A, D7948A, D7951A, D7953A, D7955A, D7961A, D7963A, D7965A, D7958A, D7968A, D7969A, D7973A, D7976A, D9460A, D9463A, D9467A, D9774A, D9810A) -&celmilg200; -&celsans; -&celsans; -&celcs4614; -&celoui; - - - -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) -&celmilg200; -&cel3com905c; -&celsans; -&celcs4614; -&celoui; - - - -Vectra VL600 (D9733A, D8643A, D9737A, D8647A) &coper; -&celmilg250; -&celsans; -&celsans; -&celcs4614; -&celnon; - - - -Vectra VL600 (D7543N, D8644N, D8648N, D9734N, D9738N) &coper; -&celmilg250; -&cel3com905c; -&celsans; -&celcs4614; -&celnon; - - - -Vectra VL600 (D8635A, D8645A, D8649N, D8659N, D8669N, D8679N, D9735A, D9739N) &coper; -&celmilg400; -&cel3com905c; -&celsans; -&celcs4614; -&celoui; - - - -Vectra XA (D3986A, D3989A, D3990A, D3991A, D3993A, D4770N, D4771N, -D4773N, D4774N, D3994N, D3995N, D4776N) -&celmilii; -&celamd; -&celsans; -&celinconnu; -&celnon; - - - -Vectra XA (D4777A) -&celmilii; -&celamd; -&celaic7880; -&celinconnu; -&celoui; - - - - -
- - -Kayak &et; Linux -&tabmach; - - - -Kayak XA (D4792A, D4795N) -&celcl5465; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Kayak XA (D4807N, D4796N, D6491N, D6492N, D4806N, D4808N, D6493N) -&celcl5465; -&celamd; -&celsans; -&celinconnu; -&celoui; - - - -Kayak XA (D4798N, D6490N, D4799N, D4803N, D6494N) -&celcl5465; -&celmixte2; -&celinconnu; -&celnon; - - - -Kayak XA (D4796S, D6493S) -&celmiliiagp; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Kayak XA (D4803S) -&celmiliiagp; -&celmixte2; -&celinconnu; -&celnon; - - - -Kayak XA (D6720N, D6721N, D6723N, D6726N, D6724N, D6730N, D6731N, D6735N, D6736N, D6738N, D6739N, D7994N) -&celmilg200; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Kayak XA (D6722N, D6729N, D6734N) -&celelsap; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Kayak XA (D6725N, D6732N, D6737N, D7993N) -&celmilg200; -&celmixte1; -&celinconnu; -&celoui; - - - -Kayak XA (D6727N) -&celelsap; -&celmixte1; -&celinconnu; -&celnon; - - - -Kayak XA (D6728N, D6733N) -&celaccelg; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Kayak XA-s (D5751N, D5752N, D5753N, D5755N, D5754N, D5756N, D5759N) &chipbx; -&celmilg100; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -Kayak XA-s (D5757N, D5758N) &chipbx; -&celmilg100; -&celmixte1; -&celinconnu; -&celoui; - - - -Kayak XA-s (D5765N, D5763N, D5766N, D5769N, D7982N, D7986N, D7991N, D7987N) &chipbx; -&celmilp200; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -Kayak XA-s (D5768N, D5767N) &chipbx; -&celmilp200; -&celmixte1; -&celinconnu; -&celnon; - - - -Kayak XA-s (D5762N, D7984N, D7988N) &chipbx; -&celelsap; -&celmixte1; -&celinconnu; -&celoui; - - - -Kayak XA-s (D5764N, D7983N, D7989N) &chipbx; -&celaccelg; -&celmixte1; -&celinconnu; -&celnon; - - - -Kayak XA-s (D7990N) &chipbx; -&celmilg100; -&celmixte1; -&celinconnu; -&celnon; - - - - -Kayak XA-s (D7992N) &chipbx; -&celelsaii; -&celmixte1; -&celad1816; -&celoui; - - - -Kayak XM600 (D9531N, D9533N, D9535N, D9541N, D9549N, D9553N) -&celmilg250; -&celsmc1211; -&celsans; -&celcs4614; -&celnon; - - - -Kayak XM600 (D8350N, D9554N, D9558N) &moddos; -&celmilg250; -&celsmc1211; -&celsans; -&celcs4614; -&celnon; - - - -Kayak XM600 (D9536N, D9537N, D9538N, D9539N, D9544N, D9548N) -&celmilg400; -&celsmc1211; -&celsans; -&celcs4614; -&celnon; - - - -Kayak XM600 (D9534N, D9540N, D9543N, D9546N) -&celelsaii; -&celsmc1211; -&cel53c895; -&celcs4614; -&celoui; - - - -Kayak XM600 (D9545N, D8366N) -&celgvx1; -&celsmc1211; -&cel53c895; -&celcs4614; -&celnon; - - - -Kayak XU (D4691N, D4692N, D4695N, D4701N, D4693N, D4694N, D4702N, D4705N) -&celmilii; -&celamd; -&celaic6080; -&celinconnu; -&celoui; - - - -Kayak XU (D5680N, D5682N, D5683N, D5684N) &chipbx; -&celmilii; -&celamd; -&celaic6080; -&celad1816; -&celoui; - - - -Kayak XU (D5702, D5704, D5686N, D6336N, D6348N, D8431N, D8920N) -&celmilg200; -&celaic-mixte; -&celinconnu; -&celoui; - - - -Kayak XU (D5687N, D6333N, D6334N, D8432N, D6345N, D8923N) -&celelsap; -&celaic-mixte; -&celinconnu; -&celnon; - - - -Kayak XU (D6337N, D6346N) -&celaccelg; -&celaic-mixte; -&celinconnu; -&celnon; - - - -Kayak XU (D6347N) -&celmilg100; -&celaic-mixte; -&celinconnu; -&celnon; - - - -Kayak XU (D8924N) -&celmilg400; -&celaic-mixte; -&celinconnu; -&celnon; - - - -Kayak XU800 (D8019N) &xu800; -&celmilg250; -&celsmc1211; -&celsans; -&celcs4614; -&celnon; - - - -Kayak XU800 (D8021N) &xu800; -&celmilg400; -&celsmc1211; -&celsans; -&celcs4614; -&celnon; - - - -Kayak XU800 (D8000N, D8001N) &xu800; &moddos; -&celmilg250; -&celsmc1211; -&cel53c895; -&celcs4614; -&celnon; - - - -Kayak XU800 (D8002N, D8010N, D8016N) &xu800; -&celmilg250; -&celsmc1211; -&cel53c895; -&celcs4614; -&celnon; - - - -Kayak XU800 (D8003N, D8006N, D8012N) &xu800; -&celmilg400; -&celsmc1211; -&cel53c895; -&celcs4614; -&celoui; - - - -Kayak XU800 (D8007N, D8013N, D8020N, D8022N) &xu800; -&celelsaii; -&celsmc1211; -&cel53c895; -&celcs4614; -&celnon; - - - -Kayak XU800 (D8009N, D8015N) &xu800; -&celgvx1; -&celsmc1211; -&cel53c895; -&celcs4614; -&celnon; - - - -Kayak XW (D6475N) -&celelsa; -&celamd; -&celaic6080; -&celinconnu; -&celnon; - - - -Kayak XW (D5505N, D5507N, D5509N) -&celaccele; -&celamd; -&celaic6080; -&celinconnu; -&celnon; - - - -Kayak XW (D5510N, D5514N, D6485N) -&celfx4; -&celamd; -&celaic6080; -&celinconnu; -&celnon; - - - -Kayak XW (D6480N, D6481N, D6482N) &chipbx; -&celaccele; -&celinconnu; -&celinconnu; -&celinconnu; -&celnon; - - - -Kayak XW (D6797N) -&celfx6; -&celinconnu; -&celinconnu; -&celinconnu; -&celnon; - - - -Kayak XW (D6486N, D6487N, D6488N) &chipbx; -&celfx4; -&celinconnu; -&celinconnu; -&celinconnu; -&celnon; - - - - -
- -Visualize &et; Linux -&tabmach; - - - -Visualize P (A5015A) &chipbx; -&celelsap; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - -Visualize P (A5015A) &chipbx; -&celelsaii; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - -Visualize P (A1296A) &chipbx; -&celelsaii; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - -Visualize X (A5014A) &chipbx; -&celelsap; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - -Visualize X (A5014A) &chipbx; -&celelsaii; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - -Visualize X (A1297A) &chipbx; -&celelsap; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - -Visualize X (A1280A) -&celelsaii; -&celinconnu; -&celinconnu; -&celad1816; -&celnon; - - - - - -
- - - - -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 - -&tabintrol; - - -Desktop computer accessories -&tabopt; - - - -D5480A -&celfastr; -&celaicaro; -&celnon; - - - -D6690A -&celfastr; -&celaicaro; -&celnon; - - - -D6951A -&celscsi; -&celaic7880; -&celoui; - - - -D9528A -&celscsi; -&celsym8952; -&celnon; - - - -D9529A -&celscsi; -&celinconnu; -&celnon; - - - -D6936A -&celnet; -&celamd2; -&celoui; - - - -D7504A -&celnet; -&cel3com; -&celoui; - - - -D7506A -&celnet; -&celinconnu; -&celnon; - - - -D7508A -&celnet; -&celinconnu; -&celnon; - - - -D7522A -&celnet; -&cel3com905c; -&celoui; - - - -D7531A -&celnet; -&celrealtek; -&celoui; - - - -D6657A -&celson; -&celinconnu; -&celnon; - - - -D5183A -&celson; -&celinconnu; -&celnon; - - - - -
- - - - -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) - - - -&tabintrol; - - -OmniBook &et; Linux -&tabmach; - - - -OmniBook 800 (F1360A) -&celneo128; -&celsans; -&celscsi; -&celncr53; -&celinconnu; -&celoui; - - - -OmniBook 2000 (F1356A, F1397A) -&celct65554; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -OmniBook Sojourn (F1430A) -&celneo128; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -OmniBook XE (F1719W, F1720W, F1721W, F1722W) -&cellynxe; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook XE2 (F1664W, F1666W, F1666N, F1667W, F1667N, F1674W, F1675W, F1753W, F1756W, F1755W, F1755N, F1772W, F1774N, F1774W, F1775N, F1775W, F1962W) -&cellynxe; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook 2100 (F1584W, F1580W, F1581W, F1597W, F1598W, F1599W, F1600W, F1729W) -&celneo128; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook 900 (F1711W, F1712W, F1760W, F1711N, F1712N, F1765N) -&celneo256; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook 900 (F1769W, F1769N, F1769K, F1770W, F1770N, F1770K, F1979W, F1979N, F1979K, F1980W, F1980N, F1980K) -&celatiport; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -OmniBook 3000 (F1391A, F1392A, F1393A) -&celneo128; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -OmniBook 3100 (F1582W) -&celneo128; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -OmniBook 4100 (F1462W, F1463W, F1479W, F1464W, F1703W) -&celneo128; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook 4150 (F1629W, F1640W, F1641W, F1642W, F1629N, F1640N, F1641N, F1642N, F1647W, F1647N, F1648W, F1648N, F1663W, F1663N) -&celneo256; -&celsans; -&celsans; -&celcs4232; -&celoui; - - - -OmniBook 4150 (F1649W, F1649N, F1649K, F1650W, F1650N, F1650K, F1658W, F1658N, F1660W, F1660N, F1662W, F1662N, F1662K, F1976W, F1976N, F1976K, F1983W, F1983N, F1983K, F2000W, F2000N, F2000K, ) -&celatiport; -&celsans; -&celsans; -&celcs4232; -&celoui; - - - -OmniBook 5700 (F1352A, F1353A, F1396A, F1354A, F1355A) -&celct65554; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook 7100 (F1441W, F1442W) -&celatiltpro; -&celsans; -&celsans; -&celinconnu; -&celoui; - - - -OmniBook 7150 (F1443W) -&celatiltpro; -&celsans; -&celsans; -&celinconnu; -&celnon; - - - -
- - - -Portable accessories - - - - -The cards mentionned below are PCMCIA or PC-Card cards. - - - -&tabintrol; - - -Portable accessories -&tabopt; - - - -F1623A -&celcombo; -&celxirc56; -&celoui; - - - -F1625A -&celmodem; -&celinconnu; -&celnon; - - - -F1626A -&celnet; -&cel3c575; -&celnon; - - - -F1626B -&celnet; -&celinconnu; -&celnon; - - - -F1643A -&celcombo; -&celinconnu; -&celnon; - - - - -
- - - - -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 - - &RedHat; 5.2 &et; 6.0 - - -are also available. - - - -&tabintrol; - - -NetServer &et; Linux -&tabmach; - - - -NetServer E45 (D4973A, D4974A, D4975A, D4976A, D5971A) -&celcl5446; -&cel5013; -&celaic2910; -&celsans; -&celnon; - - - -NetServer E50 (D6034A, D6033A, D6035A, D6031A, D6030A, D6032A) -&celcl5446; -&cel5013; -&celaic7880; -&celsans; -&celoui; - - - -NetServer E55 (D9337A) -&celati2c; -&cel5013i; -&celaic7895; -&celsans; -&celnon; - - - -NetServer E60 (D7140A, D7142A, D7144A, D7146A, D7148A, D9123A, D9127A, D9128A, D9129A) -&celati2c; -&cel5013i; -&celaic7895; -&celsans; -&celoui; - - - -NetServer LC II (D4907A, D4909A, D5014A, D5015A, D5016A, D5969A, D5970A, D5959A, D5961A) -&celcl5446; -&cel5013; -&celaic7880; -&celsans; -&celoui; - - - -NetServer LC 3 (D6123A, D7018A, D6125A, D7020A, D7028A, D7025A, D7126A, D8594A) &chipbx; -&celcl5446; -&cel5013; -&celaic7880; -&celsans; -&celoui; - - - -NetServer LC 2000 (D8514A, D8515A, D8519A, D8520A, D8524A, D8525A, D9162A, D9163A) &coper; &lc2000; -&celati2c; -&cel5013i; -&cel53c897x2; -&celsans; -&celoui; - - - -NetServer LD Pro (D4944A, D4946A, D4961A, D4962A) -&celt9000; -&cel5013; -&celaic7880; -&celsans; -&celnon; - - - -NetServer LH Pro (D4979A, D4980A, D4981A, D4982A) -&celt9000; -&celsans; -&celaic7880x2; -&celsans; -&celoui; - - - -NetServer LH II (D5017A, D5953A, D5021A, D5023A, D6047A, D6048A) -&celt9000; -&celsans; -&celaic7880x2; -&celsans; -&celoui; - - - -NetServer LH 3 (D4998A, D5002A, D5000A, D5004A, D7033A, D7034A, D8503A, D8504A, D8567A, D8568A, D9343A, D9344A) &chipbx;Rem. -&celcl5446; -&cel5013; -&cel53c895x2; -&celsans; -&celoui; - - - -NetServer LH 3000 (D8228A, D8230A, D8236A, D8238A, D8244A, D8246A, D9176A, D9178A) &chipbx;Rem. -&celinconnu; -&celinconnu; -&celinconnu; -&celsans; -&celnon; - - - - -NetServer LH 4 (D7092A, D7093A, D7094A, D7095A, D6971A, D6972A, D6973A, D6974A, D7103A, D7104A, D8552A, D8553A, D8556A, D8557A, D8560A, D8561A) &chipbx; Rem.Rem. -&celcl5446; -&cel5013; -&cel53c895x2; -&celsans; -&celoui; - - - -NetServer LH 6000 () &chipbx;Rem. &lh6000; -&celati2c; -&cel5013i; -&celaic-53c896x2; -&celsans; -&celoui; - - - - -NetServer LPr (D6130A, D6131A, D7171A, D9133A, D9348A, D9431A, D9434A) &chipbx; -&celcl5446; -&cel5013; -&cel53c895; -&celsans; -&celoui; - - - -Cluster NetServer LPr (D6131A, P1133A)Rem. -&celcl5446; -&cel5013; -&cel53c895; -&celsans; -&celnon; - - - -NetServer LXePro/LXPro (D4920B, D4925B, D6036A, D4311B, D4312B, D6037A, -D4315B, D4958B, D6014A, D6015A, D4964B, D4898A, D6016A, D4899A, D6017A, -D4900A, D6018A) -&celcl5424; -&celsans; -&celaic7880x2; -&celsans; -&celnon; - - - -NetServer LXr8 (D5028A) -? -? -&celsans; -Symbios logic UW -? -&celsans; -&celnon; - - - -NetServer LXr8000 (D6021A, D6022A, D6136A, D6137A, D7000A, D8256A, D8257A, D8258A, D8546A, D8548A) -&celcl5446; -&celsans; -&cel53c896x2; -&celsans; -&celoui; - - - -NetServer LXr8500 (D8540A, D8542A, D9417A, D9418A) -&celcl5446; -&celsans; -&cel53c896x2; -&celsans; -&celnon; - - - - -
- - - -NetServers accessories - -&tabintrol; - - -NetServers accessories -&tabopt; - - - -NetRaid 1 D4992A -&celnetr; -&celnetraid; -&celoui; - - - -NetRaid 3 D4943A -&celnetr; -&celnetraid; -&celoui; - - - -NetRaid 1Si D2140A -&celnetr; -&celnetraid; -&celoui; - - - -NetRaid 3Si D5955A -&celnetr; -&celnetraid; -&celoui; - - - -C1578B -&celscsi; -&celaic7895; -&celnon; - - - -C7430A -&celscsi; -&celaic7880; -&celnon; - - - -D5025A -&celscsi; -&celaic7880; -&celoui; - - - -D5252A -&celscsi; -&celaic7880D; -&celoui; - - - -D5013A, D5013B -&celnet; -&cel5013; -&celoui; - - - -J2585B -&celnet; -&celhp100; -&celoui; - - - -D6977A -&celfc; -&celinconnu; -&celnon; - - - -D5246A -&celfc; -&celinconnu; -&celnon; - - - -D6028A -&celtopt; -&celbof; -&celoui; -&celoui; - - - - -
- - - - -Complementary informations - - - - -Please refer to the - -Hardware Howto &et; 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 - -XFree86 - - -with its supported - - chipsets - - -list and the new running developments by - -Suse - - -(Think, in that case, to download also - -the configuration tool) &et; &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 - -X-Inside &et; MetroLink - - - - - -Netvectra are not supported by Linux. - - - - -Remarks - -XFree86 - - - - -The latest version of XFree86 is the 3.3.6, available from our - - mirror. - - -Ncr53c8xx - - - - -The latest version of the ncr53c8xx driver is available from the - - reference site. - - - -3C59x - - - - -The latest version of the 3c59x driver is available from the - - reference site. - - - -Sound Chipset AD1816 - - - - -The latest version of the AD1816 driver is available from the - - 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 Frédéric Dubuy Frederic.Dubuy@medasys-digital-systems.fr &et; Anne-Marie Mahfouf a-m.mahfouf@lineone.net) - - - - -This card is only supported with a specific X server XFCom_i810 downloadable in both format - -RPM &ou; tar.gz - - -and a complementary module for the kernel agpgart, downloadable in both format - -SRPM &ou; 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 - -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 &et; http://www.medasys-digital-systems.fr/mirror/linux/LDP/HOWTO/Framebuffer-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. - - - - -Elsa web site - - - - -OpenGL web site - - - - -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 &curker;) 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 : - - - - -RSF-1 (Commercial) - - - - -Linux-HA project (free) &et; 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 - -AMI Megaraid - - -chipset and may support the following Raid levels : - -0, 1, 3, 5, 10, 30 &et; 50. - - -Some NetRaid cards, as well as the chipset integrated on the LH3 and LH4 mother boards are supported by recent version of the Linux kernel (2.0.36/&curker; typically - don't use 2.0.37/38). - - - - - -For the RedHat 5.2 distribution, it's not possible to install the system on this type of controler, because it's not detected by the installation program. You have to use a specific - -floppy disk - - -. This floppy disk should be used as input to the rawrite tool, for example. It works for systems with less than 1 GB of memory. - - - - - -For the RedHat 6.0 distribution, you have to manually declare the existence of this card as a supplementary SCSI adapter, in order to use it directly during the installation. The megaraid driver isn't automatically detected. - - - - - -To avoid strange messages during the boot printed by the megaraid driver, it's necessary to recompile it with the option -DHP. - - - - - -For the RedHat 6.1 distribution, the megaraid driver provided by the kernel does support on ly the first logical drive. In order to obtain the others, please recompile a &curker; standard kernel. - - - - - -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 - -&tabintrox; - - -HP Monitors &et; Linux -&tabmon; - - - -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 -&celoui; - - - -D2826A, D2826S -15" HP 50 -50-120 -31-54 -65 -640x400, 640x480, 800x600, 1024x768 -70, 60-75-85, 60-75-85, 60 -&celoui; - - - -D2827A -15" HP 51 -50-120 -31-54 -&celbof; -&celbof; -&celbof; -&celnon; - - - -D2828A -15" HP 52 -50-120 -30-54 -65 -640x400, 640x480, 800x600, 1024x768 -70, 60-75-85, 60-75-85, 60 -&celnon; - - - -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 -&celnon; - - - -D2807A -17" Ultra 1280 -50-160 -30-64 -&celbof; -&celbof; -&celbof; -&celoui; - - - -D2837A -17" HP70 -50-120 -30-70 -110 -640x400, 640x480, 800x600, 1024x768, 1280x1024 -70, 75-85, 75-85, 75-85, 60 -&celoui; - - - -D2838A -17" HP M700 -50-160 -30-86 -&celbof; -&celbof; -&celbof; -&celnon; - - - -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 -&celoui; - - - -D8901A, D8902A -17" HP71 -50-120 -30-60 -110 -640x400, 640x480, 800x600, 1024x768, 1280x1024 -70, 60, 75-85, 75-85, 60 -&celnon; - - - -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 -&celoui; - - - -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 -&celoui; - - - -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 -&celnon; - - - -A4031A -20" -48-150 -30-82 -&celbof; -&celbof; -&celbof; -&celoui; - - - -D2846A, A4576A -21" P1100 -50-160 -30-107 -&celbof; -&celbof; -&celbof; -&celnon; - - - -D2847A -21" P1110 -50-180 -29-121 -300 -&celbof; -&celbof; -&celoui; - - - -A4033A -21" -50-120 -30-80 -&celbof; -&celbof; -&celbof; -&celoui; - - - -A1295A -24" Wide Aspect -50-160 -30-96 -&celbof; -&celbof; -&celbof; -&celnon; - - - -D5061A -15,1" LCD HP -&celbof; -&celbof; -&celna; -&celbof; -&celbof; -&celnon; - - - -D5065A -18,1" LCD HP L1800 -56-85 -30-80 -&celna; -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 -&celoui; - - - - -
- - - - -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 - -The Puffin Group - - -and more precise informations on the status may be found on their - -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 - -IP Alias mini HOWTO - - -may be useful if you don't understand the previous paragraph :-). - - - - - -It is of course possible to access through the network to an HP printer attached and declared directly on a Linux machine, thanks to the - -lpd - - -service for the other Unix clients, through - -&Samba; - - -for the clients of Microsoft systems (Win9x ou WinNTx) or through - -NetAtalk - - -for the MacIntosh clients. - - - - - -At last, - -&Samba; - offers a tool, smbclient, - - -which allows to print from a Unix/Linux machine to a printer wired directly on a Microsoft based PC, without any need to use a JetDirect system. -All the details useful to realize this operation are described in the file example - -smbprint provided with the &Samba; package and on the page http://www.medasys-digital-systems.fr/linux/samba-truc.html. - - - - -Communication between a Linux machine and a printer needs also, outside a network dialog, a discussion with an exchange language between the two elements. -There are a lot of languages of that sort, such as - -PCL, Postscript &ou; HPGL. - - -To be able to print correctly, the tool providing the datas to print has to generate code known by the printer. -Filters exist which allow to easily transform an output in one given format to another one. -Thus the - -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 - -g<width>x<height> page size in pixels | -r<res> pixels/inch resolution - -sDEVICE=<devname> select device | -dBATCH exit after last file - -sOutputFile=<file> select output file: - for stdout, |command for pipe, - embed %d or %ld for page # -Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PDF -Available devices: - x11 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=full. - - - - - - - - - - -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|100-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 &et; 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 - -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 : - - - - -&Medasys; - - -Contact : Cédric Letailleur Cedric.Letailleur@medasys-digital-systems.fr - - - - -Alcove - - -Contact : Lucien Petit 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. - - - - - - - - - - -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. - - - - -Sizing of a file server -&tabsize; - - - 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. - - - -Sizing of a print server -&tabsize; - - - 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. - - - -Sizing of a static Web server -&tabsize; - - - 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 - - - -
- - -Sizing of a dynamic Web server -&tabsize; - - - 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. - - - -Sizing of an e-mail server -&tabsize; - - - 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. - - - -Sizing of a Firewall/Proxy/Web-Cache server -&tabsize; - - - 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 - -Metaframe solutions of Citrix. - - -An office server needs 50 MB of RAM per user. -Intrinsically, this machine has no requirements in term of disk, if it's not at the same time a file server. -Processor resources used are important, thus it could be useful to consider the increase in frequency and the addition of processors, because this type of traffic could be quite well done in parallel. - - - -Sizing of an office server -&tabsize; - - - 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 - - - -
- - - - - - - - -Frequently Asked Questions (FAQ) - - - - -"How to have more than 1 GB of RAM on my NetServer ?" - - - - -The following informations are adapted from the - -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 &et; /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 - -SMP-HOWTO. - - - - - -"Is Linux Y2K compatible ?" - - - - -Generally, Linux is Y2K compatible. -For more informations please consult the - -FAQ. - - - - - - - - - - -&ref;s - - - - - -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 &et; 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 : - - - - - - -Linux SCSI HOWTO - - - - -Linux CD-Writing HOWTO - - - - -Linux Hardware HOWTO - - - - -Linux Distribution HOWTO - - - - -Linux Kernel HOWTO - - - - -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 - -. - - - - - -On Internet, you may consult with a great benefit the following sites : - - - -Web sites ofMedasys &et; HP -&tabref; - - - -HP Linux Portal -http://www.hp.com/go/linux - - -HP &et; 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 - - - - -
- - -Other fundamental sites on Linux and Open Source Software -&tabref; - - - -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/ - - - - - -
- - - - - - - - -Contributors - - - - - -I would like to thank especially all the people who contributed in any way to improve this HOWTO : - - - - -Pierre-Antoine Angelini angelini@ifsic.univ-rennes1.fr - - -Stéphane Bortzmeyer bortzmeyer@debian.org - - -Jean-Bernard Chaffardon Jean-Bernard_Chaffardon@hp.com - - -Khalil Chawoshi chawoshi@subatech.in2p3.fr - - -Béatrice Cornec beatrice@victoria.frmug.org - - -Frédéric Dubuy Frederic.Dubuy@medasys-digital-systems.fr - - -Mark Eve Mark_Eve@hp.com - - -Laurent Frey laurent.frey@iota.u-psud.fr - - -Stein Roar Gjøen stein.roar.gjoen@ks-t.no - - -Yann Guillemot Yann.Guillemot@medasys-digital-systems.fr - - -Marc Hia Balié Marc_Hia-Balie@hp.com - - -Chris Holden chris.holden@gte.net - - -Masanari Iida Masanari_Iida@hp.com - - -Pascal Lemonnier Pascal.Lemonnier@medasys-digital-systems.fr - - -Maciej Macowicz Maciej.Macowicz@epfl.ch - - -Olivier Martinet Olivier_Martinet@hp.com - - -David Mentré David.Mentre@irisa.fr - - -Andreas Nierula A.Nierula@t-online.de - - -Gilles Noisette Gilles_Noisette@hp.com - - -Harry Page HARRY_PAGE@HP-NewZealand-om1.om.hp.com - - -Alain Pascal pascal@montrouge.omnes.slb.com - - -Fons Rademakers Fons.Rademakers@cern.ch - his site : http://hp-linux.cern.ch - - -Dirk De WachterDirk.DeWachter@rug.ac.be - - -Norman Walshndw@nwalsh.com - - - - - - - - -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 - - - - - - - - diff --git a/LDP/howto/docbook/HP-HOWTO.sgml.tar b/LDP/howto/docbook/HP-HOWTO.sgml.tar deleted file mode 100644 index 04f630c1..00000000 Binary files a/LDP/howto/docbook/HP-HOWTO.sgml.tar and /dev/null differ