From: Colin Wynd,colin@col.hp.com Reply-To: colin,colin@col.hp.com Newsgroup: comp.answers,comp.sys.hp.hpux,comp.sys.hp.misc,comp.sys.hp.apps,comp.sys.hp.hardware,news.answers Receive-Date: Mittwoch, 15-Mär-95 01:22:07 Creation-Date: Samstag, 11-Mär-95 17:15:45 Message-ID: 3jsls1$hjp@nonews.col.hp.com Date: 11 Mar 1995 17:15:45 GMT Subject: comp.sys.hp.hpux FAQ Organization: HP Colorado Springs Division Followup-To: comp.sys.hp.hpux X-Newsreader: TIN [version 1.2 PL1.4] UserFlags: Old ReadAccess GlobalFlags: Exported Link HardLink Archive-name: hp/hpux-faq Last-modified: 1995/03/15 Version: 4.6 comp.sys.hp.hpux FAQ (Frequently Asked Questions) Subject: 1. INTRODUCTION This article contains the answers to Frequently Asked Questions (FAQ) seen in the Internet newsgroup comp.sys.hp.hpux. Issues may also be discussed in comp.sys.hp.apps, comp.sys.hp.misc, and comp.sys.hp.hardware. Discussion in this document centers around Hewlett-Packard computer systems running the HP-UX operating system; the focus tends to be on the series 700 workstations, although topics are also applicable to series 800 machines, and to a lesser degree, series 300 and 400 machines. It is posted twice monthly, on the 1st and the 15th of the month. This article is Copyright 1994 by Colin Wynd. It may be freely redistributed in its entirety provided that this copyright notice is not removed. It may not be sold for profit or incorporated in commercial documents without the written permission of the copyright holder. Permission is expressly granted for this document to be made available for file transfer from installations offering unrestricted anonymous file transfer on the Internet. This article is provided as is without any express or implied warranty. The content of this article is the sole responsibility of the author and contributors, and does not necessarily represent their employers or Hewlett-Packard. Refer to question 3.1 for details on where to get this FAQ. This FAQ is written in "minimal digest format". You can skip from one section to the next by pressing ^G in many newsreaders, such as rn, trn and strn (but not nn). Network resources are pointed to in this document by URL (Uniform Resource Locator). A simplistic view of URL syntax: method://server[:port]/pathname Where "method" can commonly be any of [file|gopher|wais|news|ftp|http]. An example: a file is available via FTP at supportnet.mentorg.com and the pathname is pub/tmp/test. The URL is: ftp://supportnet.mentorg.com/pub/tmp/test Questions marked with a "+" are new to this issue, and questions with changes since the last issue are marked by a "!". Submissions, corrections, comments, input, complaints, attaboys, large amounts of money, etc., should be directed to Colin Wynd . ------------------------------ Subject: 2. TABLE OF CONTENTS 1. INTRODUCTION 2. TABLE OF CONTENTS 3. FINDING INFORMATION 3.1 Where can I get a copy of this FAQ file? 3.2 Courses on HP-UX 3.3 Interex, The International Association of HP Computer Users 3.4 InterWorks, The International HP Workstation Users Group 3.5 Interex HP Users Conferences 1995 3.6 InterWorks Conference 1995 3.7 HP/Works 3.8 HP/Works Conferences 3.9 Japanese HP Computer Users Association 3.10 German HP User Group 3.11 DutchWorks 3.12 HP-UX publicly available software from InterWorks. 3.13! Anonymous FTP Sites for HP-UX, and UNIX related software. 3.14 Where can I get a demo CD with software for HP-UX? 3.15 HP-UX patch information 3.16 How can I send mail to an "hpdesk" address? 3.17 What are the known issues with porting BSD-based programs to HP-UX? 3.18 What periodicals are available that focus on HP-UX? 3.19 Books on HP-UX 3.20 HP-UX Sysadmin Mailing List 3.21 HP-related WWW Sites 3.22 Is there any way to get rid of a frequent poster's posts? 3.23 HP 500 Mailing List 3.24 HP 3000 FAQ 3.25 What is HP's involvement in the HP-related newsgroups? 3.26 Who was the former maintainer of the FAQ? 3.27 Where do i get information on HP's Printers? 4. THIRD PARTY VENDORS 4.1 Third party vendors for RAM. 4.2 Third party vendors for other things 4.3 Do Seagate 9GB drives working with s700 and s800? 5. UTILITIES 5.1 ASCII to Postscript converter. 5.2 How do I make perl on HP-UX? 5.3! What is the status of the various gnu items on HP-UX? 6. X WINDOW SYSTEM, MOTIF, AND HP-VUE 6.1 X11 libraries (Athena, etc.) and utilities (imake, etc.). 6.2 How can I display an image on the root window with HP-VUE? 6.3 How do I get a scroll bar on hpterms? 6.4 How can I put a title in my hpterm titlebar? 6.5 How come my hpterms keep going away by themselves? 6.6 How come my HP X/Motif clients take a LONG time to display on a Sun? 6.7 How can I get my login stuff to work under HP-VUE? 6.8 How can I get console messages to go to an hpterm? 6.9 What happened to the vuewm key accelerators at VUE 3.0? 6.10 How come I can no longer disable the caps lock key with xmodmap? 6.11 How come vi behaves strangely in xterms at 9.01? 6.12 How do I disable HP-VUE? 6.13 What's a good termcap entry for hpterm? 6.14 My screen is wedged. What should I do? 6.15 How can I get an X client to come up in an alternate workspace? 6.16 How can I get HP-VUE to not override colors? 6.17 How can I override the system default printer in vuepad? 6.18 What about X11R6? 6.19 How can I set user-specific app-defaults in HP-VUE? 6.20 How can I get VUE to share colormap entries: 6.21+ How can I disallow root login at the console with VUE? 7. OPERATING SYSTEM 7.1 Can I have filenames longer than 14 chars? 7.2 How can I tell what products have been loaded on my system? 7.3 How do I safely remove software from my system? 7.4 What's the scoop on HP-UX 9.03/9.04? 7.5 How come HP-UX doesn't support NFS root access? 7.6 How can I change the order of hostname resolution? 7.7 How come the LOGnnnn files in /usr/adm keep growing and growing? 7.8 How come I can't lock mail or other files on a Sun? 7.9 Why are mail files in /usr/mail are owned by daemon instead of the recipient? 7.10 How can I tell if I need more than a 2-user license? 7.11 How can I tell what patches are in the kernel? 7.12 How come I have to hit return after control-d in the Korn shell? 7.13 How do I boot into single user mode? 7.14 How come my Korn shell login hangs? 7.15 How can I avoid those annoying copyright notices on login? 7.16 How can I turn off quota checking? 7.17 What are the issues with HP-UX 9.01? 7.18 Why does chown behave differently at 9.x? 7.19 How can I track log files and core files? 7.20 How much memory can a process use? 7.21 How come there's little discussion of DCE? 7.22 How can I make a ramdisk? 7.23 How come I can't lock files across NFS after upgrading to 9.01? 7.24 What's a good strategy for clearing /tmp? 7.25 How can I change the timezone? 7.26 How can I look at what my system is doing? 7.27 How can I partition HP-UX disks on 700s? 7.28 How can I print man pages successfully? 7.29 How can I limit core files? 7.30 Can I put more than one backup on DDS with fbackup? 7.31 How can I load multiple patches on a machine at the same time? 7.32 How can I set up an HP-UX workstation as an X terminal? 7.33 What causes "Unable to initialize MI" when running Glance? 7.34 How come I can't get all of my swap space? 7.35 How come I can't start my Aserver? 7.36 How can I get a daemon to successfully start from /etc/rc? 7.37 How come my /dev/null keeps getting blown away? 7.38 How can I track network packets? 7.39 How come my processes keep dying at 67M memory usage? 7.40 Is it possible to artificially limit the memory size? 7.41 How come my alt key combinations don't work in emacs X mode? 7.42 I can't get Flex LM based licensing to work. 7.43 How can I set up group-based FTP access? 7.44 How come my 700 doesn't perform as well as I expect? 7.45 How do I convert the uname string to the model string? 7.46 Why does ksh hang when my $HOME is NFS mounted? 7.47 Problem with ntalkd and it's handling on /etc/utmp. 7.48 How to get an MS-DOS floppy formatted using HP-UX? 7.49 How to get the MAC (station) address programmatically? 7.50 Is there a Transport Level Interface (TLI) interface to TCP on HP-UX? 7.51 How do you disable IP Forwarding? 7.52 Does HPUX 9.0 have support for threads? 7.53 How come the filenames on CD-ROM are in uppercase? 7.54 How come I can't type an '@' character? 7.55+ How come I can't get my machine into boot admin mode? 8. COMPILERS AND LINKERS 8.1 What's a P-FIXUP error? 8.2 Where is regcmp on HP-UX? 8.3 How come the default C compiler is brain-dead? 8.4 How do I deal with "too many defines"? 8.5 How come I get "_builtin_va_start" undefined when I build with gcc? 8.6 How can I tell if something was built debuggable? 8.7 Is there some kind of problem with using FLT_MIN in ANSI mode? 8.8 What's the deal with _INCLUDE_xxxx_SOURCE? 8.9 How come I need to explicitly specify -I/usr/include? 8.10 Is there an equivalent for getrusage()? 8.11 Why is syslog() call not doing what i want it to? 8.12! Is trace on HP-UX? 8.13+ How to get C programs automatically generate stack dumps? 9. HARDWARE AND PERIPHERALS 9.1 Are alternate keyboards available for HP workstations? 9.2 How can I play audio CDs on an HP workstation? 9.3 How can I enable the LAN interface on a 700? 9.4 How can I get an Exabyte to work on an HP? 9.5 Is there a "node ID" on 700s? 9.6 How can I get a stuck DDS tape out of the drive? 9.7 How can I use dump with a DDS tape? 9.8 What is the correct major number for DDS drives on 9.x? 9.9 How can I set up /dev/audio to point to the external jack on a 700? 9.10 How can I configure the parallel port handshake on a 700? 9.11 What are the specs of the audio hardware on the 700 series? 9.12 What are the various revisions of PA-RISC? 9.13 How do I read an SGI-written tar format DDS tape? 9.14 Is there a trackball for the 700? 9.15 Where can I get disktab entries for third party disks? 9.16 Do I need to terminate the internal SCSI on a 700? 9.17 What is the largest disk partition I can have? 9.18 How can I determine how much RAM I have non-interactively? 9.19 How can I turn off the lpspooler cover page? 9.20 Does HP support the RockRidge extensions for CDROM names? 10. LOOKING FOR... 10.1 Where did xline go at 9.x? 10.2 How about the VUE 2.01 man page help index? 10.3 Is there anything remotely like the Apollo DM available? 10.4 Where can I get SLIP for HP-UX? 10.5 Where can I get pcnfsd on HP-UX? 10.6 Where can I get ppp for HP-UX? 10.7 Where can I get STREAMS for HP-UX? 10.8 What about POSIX threads? 10.9 Where can I get Interviews for HP-UX? 10.10 Where can I get POP for HP-UX? 10.11 Where can I get sudo for HP-UX? 10.12 Where can I get ntalk for HP-UX? 10.13 Where can i get disktab entries for certain seagate drives? 11. HP-UX 10.0 INFORMATION 11.0 When will HP-UX 10.0 be released? 11.1 What functionality is in HP-UX 10.0 11.2 Can you have Multiple IP addresses on one interface? 11.3 What version of named is running at HP-UX 10.0? ------------------------------ Subject: 3. FINDING INFORMATION ------------------------------ Subject: 3.1 Where can I get a copy of this FAQ file? Many FAQs, including this one, are available via FTP on the Internet FAQ archive site: ftp://rtfm.mit.edu/pub/usenet/news.answers/hp/hpux-faq This FAQ is also archived on the Interworks archive machine: ftp://iworks.ecn.uiowa.edu/pub/comp.hp HTML versions of this document are available at: http://www.cis.ohio-state.edu/hypertext/faq/usenet/hp/hpux-faq/faq.html http://www.cae.wisc.edu/FAQ/ http://hpux.csc.liv.ac.uk/FAQ/ http://support.mayfield.hp.com http://hpubgon.norway.hp.com/Faq/ You can also get it by e-mail from ; send the text "send usenet/news.answers/hp/hpux-faq". Or from ; send the text: get hpux-admin HP_FAQ end The FAQ is also included with the InterWorks software CD-ROM, the Interex CSL, and the Walnut Creek Internet CD-ROM. Note that these versions were current when the respective distributions were frozen. A Japanese version of this document is available from CUA (HP Computer Users Association); send mail to . The original translation was done by Masataka Isoya. Subsequent translations have been done by Kumiko Abe. If all else fails, contact the maintainer (colin@col.hp.com). ------------------------------ Subject: 3.2 Courses on HP-UX Call the following numbers for information or the latest HP Education Catalog. U.S.: 1-800-HPCLASS {1-800-472-5277} Canada: (416)678-9430 ------------------------------ Subject: 3.3 Interex, The International Association of HP Computer Users Interex is the International Association of HP Computer Users and the largest HP user group in the world. The organization is more than 19 years old with thousands of members worldwide. It represents HP users of all kinds including HP9000, HP3000, HP1000, and Vectra PC's with annual conferences attracting vendors from all over the world. Interex publishes "Interact" for the HP3000 and Vectra PC user, "hp-ux/usr" for the HP9000 user and a realtime operating system newsletter for the HP1000 users. There are many regional users groups, many holding annual or semiannual conferences, and Interex has a collection of software (with sources) covering MPE, HP-UX and RTE called the Contributed Software Library. To contact Interex: (800) INT-EREX or (800) 468-3739 or: (408) 747-0227 fax: (408) 747-0947 email: ehrhardt@interex.org .. editor of hp-ux/usr magazine pubs@interex.org .. Circulation/advertising membership@interex.org .. membership inquiries cslhpux@interex.org .. contributed software library (hp-ux) Compuserve: 76376,1222 Address: Interex Interex (for US mail) 1192 Borregas Avenue. P.O. Box 3439 Sunnyvale, CA 94088 Sunnyvale, CA 94088-3439 ------------------------------ Subject: 3.4 InterWorks, The International HP Workstation Users Group InterWorks, formerly the Apollo Domain User's Society (ADUS), was formed to provide a users group specifically for HP _workstation_ users. The group publishes a quarterly newsletter, "The Works", holds an annual conference (see below), and maintains a library of HP-UX (and DOMAIN) software (see below). Membership is free; please contact Carol Relph for more information: Carol Relph Manager, Member Services InterWorks, Inc. c/o Hewlett-Packard Company Workstation Business Unit 300 Apollo Drive, Mailstop IWORKS Chelmsford, MA 01824-3623 (508)256-6600 E-Mail: relph_c@apollo.hp.com ------------------------------ Subject: 3.5 Interex HP Users Conferences 1995 The Denver conference is now over. Upcoming conferences include: IPROF (Interex Programmer's Forum) - April 5-8 1995 in Cupertino, Ca. Interex 1995 - August 13-17 1995 in Toronto, Ontario, Canada. Interex 1996 - August 4-8 in San Diego, CA. Interex 1997 - August 24-28 in Chicago, IL. ------------------------------ Subject: 3.6 InterWorks Conference 1995 The next InterWorks conference is to be held 5/7/95 - 5/12/95 at The Pointe at South Mountain in Phoenix, Arizona. ------------------------------ Subject: 3.7 HP/Works HP/Works is the HP/Apollo Workstation User Society in Europe. Based in the UK the Society supports all HP/Apollo workstation users - running the HP-UX or DOMAIN operating systems - throughout Europe. The Society aims to offer a high level of service to our members whilst continuously expanding the number of benefits available. Currently these benefits include: Two Major Conferences a Year Special Interest groups (SIGs) A quarterly newletter (PING) Contributed software libraries for both HP-UX and DOMAIN Introductory documentation and short courses Mailings of the latest product information and offers Contacts with outher European HP Computer Users For further information and a membership pack contact: Helen Grainger, PO Box 47, Bicester, United Kingdom +44 (0)869 321080 or by e-mail from helen@hpworks.demon.co.uk ------------------------------ Subject: 3.8 HP/Works Conferences 4th April 1995 - Sy, high impact declarations with exclamation points. These rules makes articles much easier for recipients to handle appropriately. 2e) Why should I bother with Subject, Summary, and Keyword headers? ------------------------------------------------------------------- Subject, Summary, and Keyword headers are scanned by many news reading programs, thus permitting readers to find your article easily. You will have your articles read more often if you select these carefully. 2f) How do I post test messages? -------------------------------- Do not post test messages to comp.groupware. There are special groups for testing. And tests should be as limited in their distribution as possible. This is basic information from "Guidelines for posting on Usenet". Posting of test messages inappropriately is considered abusive and will cause a loss of readership for your articles. 2g) What is the best way to post a follow-up message? ----------------------------------------------------- When you reply to a message, do not change the subject line or redirect follow-ups (unless you are changing the subject). Such changes make it harder for some news readers to follow the threads in a discussion. Include a "Summary" line which indicates specifically what your message says. This permits your article to be found even if it is a follow-up to an article with poorly chosen subject and keyword information. Never post a "me too" message or one that says you "agree" or "disagree" with the original post. Use e-mail for this type of response. Posted articles should contain information of interest to all readers, not just the original author. 2h) What should I do about inappropriate articles? -------------------------------------------------- Please, do not post responses to articles you feel are inappropriate or abusive. (If you can not resist, consider alt.flame as an alternative newsgroup for your article [it has greater readership than comp.groupware]). If the author is not saying anything worth reading, enter the name in your "kill" file, and then no more of your time will be wasted by that person. If you feel that the author is saying something worth reading, but in an inappropriate way, respond by mail. Tell the author what you think is incorrect about the article. If possible, suggest how to accomplish the objective in an appropriate way (e. g., post to another newsgroup). If you have responded to a person by mail a few times without the desired effect, and you feel that the group as a whole could benefit by a solution to the problem, only then should you post an article. The nature of your article should be a suggestion, if possible, of how such problems can be avoided in the future. 3a) Can more than one person use an account name for posting? ============================================================= Each name should have one and only one user. If an article is a joint product, indicate this at the beginning and end of the article. Some news reading programs allow certain names to be to be automatically selected. Help the reader by using the same name at all times. This will improve the chances that people will read your articles. 3b) What is the best way to sign an article? -------------------------------------------- The signature should include complete name, address, and telephone number (this allows quick verification in case forgery is suspected). E-mail addresses ought to be included in the signature in case headers get munged. Another nice feature is geographical coordinates, so the time zone can be determined (useful in telephoning). The signature should be limited to four lines as is suggested practice on Usenet. 4a) What is the proper setting for my distribution header? ========================================================== Set your distribution to "world". Comp.groupware is delivered to all continents. Do not limit your chances for feedback by restricting distribution. Restricted distribution can cause confusion when people read responses to articles they have not seen. f you take a package and find that you must build an executable (or do some porting) for your machine and/or OS level, I would appreciate hearing about your work and receiving a copy of the executable you built. Note that I have had very little involvement in the writing or packaging of any of the items on the list-- they are the result of the work of many other people. In particular, note that the available binaries have not been compiled by me. If you are concerned about running binaries compiled by someone else, build them yourself with the available source. Also note that individual authors may include text regarding the rights of others to use and distribute their code. Thanks to all the contributors. ------------------------------ Subject: 3.13! Anonymous FTP Sites for HP-UX, and UNIX related software. Site: ftp://iworks.ecn.uiowa.edu/pub/comp.hp Contents: The InterWorks HP-UX Library in the directory "pub/comp.hp" as described above. The iworks node also keeps the last 4-6 months of comp.sys.hp.hpux online (via an InterWorks member logon (see question 3.4 above). An archive going back to June 1990 is available-- contact the InterWorks librarian for details. Additionally, a large (~1300 line) "HP-UX Troubleshooting Guide" is available under the InterWorks member logon. Name: ftp://hpux.csc.liv.ac.uk Address: ftp://138.253.42.172 Contents: 785 packages ported to HP-UX 8.X and 9.X Here is an overview of hpux.csc.liv.ac.uk as of Fri 10 Mar 1995: (The 2 most recently installed packages in each category are in brackets) 58 packages in /hpux/X11/Misc (xautolock-1.10 xfm-1.3.1) 55 packages in /hpux/X11/Demos (t3d-1.0 xacursor-1.0) 50 packages in /hpux/X11/Viewers (xpaste-1.1 sced-0.61) 50 packages in /hpux/X11/Toolkits (tclgdbm-1.0 tclsql-1.1) 44 packages in /hpux/Gnu (hp2xx-3.2.0 ghostview-1.5) 41 packages in /hpux/Sysadmin (mmv-1.0 linkem-1.0) 39 packages in /hpux/X11/Graphics (xpm-3.4e spy-1.7) 36 packages in /hpux/Text (Xspell-1.00 tkispell-1.6p3) 36 packages in /hpux/Games/Arcade (xasteroids-4.0 xfred-1.0) 34 packages in /hpux/Misc (vgp-1.0 screen-3.6.1) 27 packages in /hpux/Maths/Misc (gap.README-3.3 eigen-1.01a) 25 packages in /hpux/Networking/Admin (xntp-3.4h vrfy-94.09.29) 24 packages in /hpux/X11/Core (xstdcmap-1.6 xmag-5.00) 24 packages in /hpux/Users (zorro-1.1p4 tkdiff-1.0b6) 23 packages in /hpux/X11/Networking (freeWAIS-0.3 xtachos-1.0) 23 packages in /hpux/Games/Board (xsol-1.0 gnuchess-4.0.74) 22 packages in /hpux/Networking/WWW (lynx-2.3.7 netscape-1.1b1.exp) 21 packages in /hpux/Languages (codecs-1.0 swi-1.8.9) 19 packages in /hpux/Editors (smedit-2.1 mxedit-2.4) 17 packages in /hpux/Networking/Mail (BCRMailHandler-3.14 xbuffy-3.1) 16 packages in /hpux/X11/Drawing (tgif-2.16.8 tgif-2.16.7) 15 packages in /hpux/X11/XView3 (xvnews-2.3 xview-3.2) 13 packages in /hpux/NeuralNets (NeoCognitron-1.0 xerion-3.0) 13 packages in /hpux/Games/Networking (xpilot-3.3.1 xpilot-3.3.0) 12 packages in /hpux/Maths/LinAlgebra (rlab-0.99i rlab.all-0.99i) 11 packages in /hpux/Networking/News (nestor-1.0p3 nntpclnt-1.6) 11 packages in /hpux/Networking/Misc (talk-3.0.2 lwho-2.00) 10 packages in /hpux/Networking/FTP (llnlxdir-0.9b5 llnlxftp-2.0.4) 9 packages in /hpux/Distributed (xpvm-1.0 condor-4.5) 8 packages in /hpux/Physics (asa-3.15 asa-3.20) ======================================= 786 packages in total Name: http://hpux.csc.liv.ac.uk/ or http://hpux.cae.wisc.edu/ or http://hpux.ask.uni-karlsruhe.de/ or http://hpux.cict.fr/ or http://hpux.ced.tudelft.nl/archive_intro.html Address: http://138.253.42.172/ or http://144.92.4.62/ or http://129.13.200.57/ or http://192.70.79.53/ or http://130.161.140.100/archive_intro.html Contents: WWW interface to the above HP-UX archive Name: gopher://hpux.csc.liv.ac.uk Address: gopher://138.253.42.172 Contents: Gopher interface to the above HP-UX archive Name: wais://hpux.csc.liv.ac.uk/hpux or Name: wais://hpux.cict.fr/hpux Address: wais://138.253.42.172/hpux or Address: wais://192.70.79.53/hpux Contents: WAIS interface to the above HP-UX archive There is also a mail server at mail-server@csc.liv.ac.uk for users without FTP. Name: ftp://hpux.ask.uni-karlsruhe.de Address: ftp://129.13.200.57 Contents: Official German HP-UX archive site (same as hpux.csc.liv.ac.uk) Name: ftp://hpux.cae.wisc.edu Address: ftp://144.92.4.62 Contents: Official US HP-UX archive site (same as hpux.csc.liv.ac.uk) Name: ftp://hpux.cict.fr Address: ftp://192.70.79.53 Contents: Official French HP-UX archive site (same as hpux.csc.liv.ac.uk) Name: ftp://hpux.ced.tudelft.nl Address: ftp://130.161.140.100 Contents: Official Netherlands HP-UX archive site (same as hpux.csc.liv.ac.uk) Site: ftp://ftp.prz.tu-berlin.de Contents: Much of the Liverpool archive. Site: ftp://export.lcs.mit.edu Contents: The X Window System and contributed clients. Site: ftp://hpcvaaz.cv.hp.com Contents: X Window System libraries and utilities. ftp://hpcvaaz.cv.hp.com/pub/700RX/released/b0502 contains the latest version of the 700RX software. There are subdirectories for HP-UX hosts, Solaris and SunOS. Site: ftp://ftp-boi.external.hp.com Contents: Drivers for HP printers. Site: ftp://lut.fi/pub/hpux ftp://lut.fi/pub/unix/hp-ux Contents: Various Site: ftp://nic.funet.fi/pub/unix/arch/hpux Contents: Various Site: ftp://prep.ai.mit.edu Contents: The Free Software Foundation's GNU utilities, etc. Site: ftp://hybrid.irfu.se/pub Contents: X11 archive and shared libraries, full imake support, and all missing .h files for both X11R4 and R5, dvi2pcl. Site: ftp://geod.emr.ca Contents: GNU stuff ported to HP-UX 9.x by Pierre Mathieu. Site: ftp://col.hp.com Contents: netperf, a network performance measurement tool. Site: ftp://jazz.gsfc.nasa.gov Contents: bathymetry, FFT, graph, pgplot, triangulation, sortroutine Site: ftp://support.mayfield.hp.com Contents: HP-UX patches available from FTP for SupportLine customers. Site: ftp://patch.external.hp.com Contents: European mirror of support.mayfield.hp.com Site: ftp://jaguar.cs.utah.edu/dist Currently available in the "dist" directory: gdb-4.13.u4 binutils-2.5.2.u4 gcc-2.6.3.u6 libg++-2.6.2.u2 There is no more "hpgdb", and "gas" is now bundled in the binutils. The prebuilt binaries can be retrieved all at once from hpuxbin.tar.Z, or in pieces from the hpuxbin directory. Site: ftp://ftp.cs.colorado.edu/pub/sysadmin/utilities/ Contents: sudo in cu-sudo.v1.3.1-beta9.tar.Z Site: ftp://ftp.amtp.cam.ac.uk/pub/HP Contents: ntalk in ntalk.tgz ------------------------------ Subject: 3.14 Where can I get a demo CD with software for HP-UX? See your friendly local HP sales rep to get a copy of the "Power On II" CD. CDs are available as Part Number 5962-6130E and will soon start shipping with every Series 700 workstation. Additionally, they were distributed to Interworks 94 attendees. Be sure and check out the Drive demo. This may no longer be available; people have reported problems getting it. (Thanks to Jackie Clement in WSG Outbound Marketing, HP) ------------------------------ Subject: 3.15 HP-UX patch information To determine what patches are installed: The standard patch installation will leave a directory in /system that is is name of the patch. For example, PHSS_3259 creates /system/PHSS_3259 $lsf /system/PHSS_3259 CDFinfo copyright customize* index new/ orig/ The orig directory contains the modules that were replaced by the patch and the new directory will contain any modules that were not installed for whatever reason. This can take up a lot of space, so you may want to archive this directory and remove the new and orig sub-directories. You may want to leave the customize file because it has a list of the modules replaced. To see the list do: grep Patch customize | grep -v \# Another place to look is in /etc/filesets: $ls /etc/filesets/PHSS* /etc/filesets/PHSS_1644 /etc/filesets/PHSS_2695 /etc/filesets/PHSS_3060 ... /etc/filesets/PHSS_2686 /etc/filesets/PHSS_3032 /etc/filesets/PHSS_3328 If someone has removed the /system/PHSS* directories and the PHSS* entries in /etc/filesets, there is no easy way to tell what patches are installed. You can tell if a given patch has been installed by comparing what(1) and sum(1) outputs with those given in the PHSS_nnnn.text file. Refer to question 7.11 about kernel patches. How to get patches: There are three ways to get patches. If you have a support contract you can call the Response Center (800-633-3600) and have the patches sent to you on magnetic media. If you have Basic support or Response Center support you can access the Support Line (ftp://support.mayfield.hp.com, ftp://192.6.148.19) and download patches via ftp, uucp, or kermit. The access can be modem or internet. Regardless of the support you have, you can get patches via e-mail via the SupportLine mail service. To get the user guide, send e-mail to , with "send guide" in the text portion of the message. No subject is required. The result is nroff-formatted; to get the plain ASCII version, use "send guide.txt". In addition to patches, you can also access online problem solving information, subscribe to mailing lists, and get documents. One interesting service is the obsolete patch map; to get it, send "send hp-ux_obs_patch_list" to the mail server. John Morris of the Atlanta Response Center posts a weekly list of new patches to comp.sys.hp.hpux on Mondays. It tells what's new and what patches are replaced by the new patches, along with sizes. ------------------------------ Subject: 3.16 How can I send mail to an "hpdesk" address? For a person whose DESK address is: JANE DOE /HP1234/XY Ignore the subentity (XY) and use the form: jane_doe@hp1234.desk.hp.com Send them a test message and tell them to make a note of the return address, as forming internet addresses on DESK is a little more complicated. If there is an X.400 system between you and the DESK person, what you get back may look like a very strange internet address, but it generally works. Notice the underscore between names. Names can be first_last or last_first, but first_last is easier to remember and get correct, especially if they have initials in their name as in fred_l_doe@hpatc1.desk.hp.com. Be sure that the DESK address they give you is exactly what is reported by DESK when they send a message to themselves or look at the distribution list on a piece of mail the recipient already has to verify the address. (Thanks to Bob Niland and Bill Hassell) ------------------------------ Subject: 3.17 What are the known issues with porting BSD-based programs to HP-UX? Mike Peterson periodically posts his list of BSD-HP tricks to comp.sys.hp.hpux. It is also archived on the iworks FTP site (mentioned above) as "hptricks". ------------------------------ Subject: 3.18 What periodicals are available that focus on HP-UX? o Interworks publishes The Works, a user group newsletter for Interworks members. o Interex publishes hp-ux/usr, an HP-UX focused newsletter. o HP Professional (The Magazine for Hewlett-Packard Enterprise Computing) This magazine covers MPE, HP-UX, PCs, peripherals and Networking for HP users. Its focus is on both commercial as well as technical computing. It is published by: Cardinal Business Media, Inc. 101 Witmer Road Horsham, PA 19044 (215) 957-1500 FAX: (215) 957-1050 email: simpson@cardinal.com (editor-in-chief) o The HP Chronicle (The Independent Newspaper for HP Computer Users) This tabloid-sized newspaper contains news from HP and other vendors of compatible hardware, software and peripherals. Published by: Publications and Communications, Inc 12416 Hymeadow Drive Austin, TX 8750-1896 (512) 250-9023 Fax: (512) 231-3900 email: {cs.utexas.edu, execu, texbell}!pcinews!wks Compuserve: 76011,307 MCI mail: PCI EasyLink: 62755060 o HP/Apollo Workstation A magazine that focuses specifically on HP/Apollo workstations. Published by PCI (same as HP Chronicle). o Open Systems Today (general Unix and other "open systems" weekly) has a regular "HP Focus" section. o Unix Review covers general Unix topics monthly. (Thanks to Bill Hassell, HP, for most of this) ------------------------------ Subject: 3.19 Books on HP-UX A recently published book on HP-UX system administration: 'The HP-UX System Administrator's "How To" Book' by Marty Poniatowski Prentice-Hall ISBN 0-13-099821-4 If you're serious about adminstering HP-UX workstations, get this book. Unfortunately, it fails to mention the Internet or this FAQ as alternate resources, but it does discuss Interworks and Interex. (Thanks to Mike Taylor, HP) ------------------------------ Subject: 3.20 HP-UX Sysadmin Mailing List Bart Muyzer runs an HP-UX system administration mailing list. To reach ALL MEMBERS of the list, send e-mail to ; to SUBSCRIBE, send mail to with in the body: subscribe hpux-admin e-mail address end The e-mail address is optional and, when left out, will be set to the contents of your "From: " line. To get a list of availabe commands, send a message containing help end to ." Problems, questions, suggestions and the like should go to the address "owner-hpux-admin@cv.ruu.nl". You can retrieve the charter from ; send a message containing: get hpux-admin hpux-admin-policy end A copy of the FAQ is available in the same way by sending: get hpux-admin HP_FAQ end (Thanks, Bart!) ------------------------------ Subject: 3.21 HP-related WWW Sites There are now several sites supporting WWW access on HP-related topics, including HP itself. The HP SupportLine World Wide Web service allows you to: o Resolve software problems by searching up-to-date support and problem- solving information; o Browse news and current announcements; and o Subscribe to automatically receive the latest Hewlett-Packard support information. The HP SupportLine World Wide Web service home page is located at URL: http://support.mayfield.hp.com The Hewlett-Packard World Wide Web home page (Access HP) is located at URL: http://www.hp.com Please forward all feedback about the HP SupportLine World Wide Web service to webmaster@support.mayfield.hp.com. Other HP-related WWW sites include: Site: http://hpwww.epfl.ch/HPUX/tools/disktab.html http://hpwww.epfl.ch/bench/bench.html http://hpwww.epfl.ch/ Or send mail to mailer@hpwww.epfl.ch to access disktab info. Contents: Contains many disktabs for non-HP disks Site: http://www.cis.ohio-state.edu/hypertext/faq/usenet/hp-faq/faq.html Contents: This FAQ. Site: http://hpux.csc.liv.ac.uk/FAQ/ Contents: This FAQ. Site: http://hpux.csc.liv.ac.uk/intro.html Contents: Interface to the Liverpool archive, including package descriptions, man pages and screen shots as well as the packages themselves. Also includes a WAIS server (wais://www.csc.liv.ac.uk/hpux) for searching HTML documents relating to the archive. Site: http://hpubgon.norway.hp.com/Faq/ Site: http://www.cae.wisc.edu/FAQ/ Contents: This FAQ. Site: http://www.cae.wisc.edu/intro.html Contents: Interface to the Wisconsin Liverpool archive mirror, including package descriptions, man pages and screen shots as well as the packages themselves. Site: http://www.cs.ruu.nl/hpux-admin-archive/ Contents: Archive for the hpux-admin mailing list. Site: http://www.eel.ufl.edu/~scot/tutor/ Contents: HP-UX 9.x Tutorial Site: http://www.cs.ruu.nl/hpux-admin-archive/index.html Contents: System Administrators Mailing List for HP-UX Site: http://hpwww.epfl.ch/ Contents: French speaking HP www support (some info also in english like benchmarks, disktab entries, etc...) Site: http://www.eel.ufl.edu/~sessiont/tutorial/tofc.html Contents: HP-VUE tutorial ------------------------------ Subject: 3.22 Is there any way to get rid of a frequent poster's posts? If you wish to remove a frequent poster's posts (ie Joe Bloggs) and most of the related followups and if you are running rn, put the following commands in your kill file: /Joe Bloggs/a:j /joeb@anyplace.com/a:j If you are using Gnus (an Emacs-based newsreader), type "M-k" in the Subject buffer of the relevant newsgroup to expose the killfile, insert these two lines into the killfile: (gnus-kill "From" "joeb@anyplace.com" '(gnus-summary-kill-thread nil)) (gnus-expunge "K") and then type "C-c C-c" in the killfile buffer. From then on, you will not see any thread trees rooted at an article from Joe Bloggs. ------------------------------ Subject: 3.23 HP 500 Mailing List There now exists a mailing list dedicated to the HP 9000 series 500 machine. To get on (or off) the list, send email to with the word subscribe in the subject line. (Thanks to Chris Osborn, ) ------------------------------ Subject: 3.24 HP 3000 FAQ There is a (slowly forming) HP3000 FAQ available by e-mail to faq@3k.com, gopher at gopher.3k.com, anonymous ftp at ftp.3k.com, or www at ftp://ftp.3k.com/3k.htm It contains a list of the products and vendor names. There is also a list of HP3000 vendors (on the above machines) with Internet e-mail access. (thanks to Chris Bartram, 3K Associates ) ------------------------------ Subject: 3.25 What is HP's involvement in the HP-related newsgroups? HP does not, to my knowledge, have a formal policy regarding employee involvement in the HP-related newsgroups. There is significant activity from HP employees, typically Response Center engineers and lab engineers. Much of the information in this document originally came from internal HP sources. ------------------------------ Subject: 3.26 Who was the former maintainer of the FAQ? Greg Cagle (gcagle@hpupora.nsr.hp.com) from Mentor Graphics was the FAQ maintainer until November 1994. All entries with no attribution are Greg's. Thanks for all the work maintaing the FAQ. ------------------------------ Subject: 3.27 Where do i get information on HP's Printers? You can access printer information and software from: Site: ftp://ftp-boi.external.hp.com Contents: Drivers for HP printers. There is a phone number for ordering printer drivers: (303) 339-7009 ------------------------------ Subject: 4. THIRD PARTY VENDORS ------------------------------ Subject: 4.1 Third party vendors for RAM. The following vendors are listed in alphabetical order. No guarantees are made regarding compatibility or relative merit of the vendors. Camintonn Clearpoint Research Corporation 22 Morgan 1000 E. Woodfield Road, Suite 102 Irvine, CA 92718 Schaumburg, IL 60173 (800) 843-8336 (708) 619-9227 (714) 454-6500 Concorde Technologies Dataram 7966 Arjons Dr. B-201 PO Box 7528 San Diego, CA 92126 Princeton, NJ 08543-7528 (800) 359-0282 (800) DATARAM (619) 578-3188 (800) 799-0071 Digitial Micronics Eventide 2075 Corte Del Nogal 1 Alsan Way Unit N Little Ferry, NJ 07643 Carlsbad, CA 92009 (201) 641-1200 Helios Systems Herstal Automation 1996 Lundy Ave 3171 West Twelve Mile Rd. San Jose, CA 95131 Berkley, MI 48072 (408) 432-0292 (313) 548-2001 (800) 366-0283 IEM Infotek Systems P.O. Box 1889 625 South Lincoln Fort Collins, CO 80522 Suite 204 (800) 321-4671 Steamboat Springs, CO 80487 (303) 221-3005 (800) 767-1084 Intelligent Interfaces ISA Ltd P.O. Box 1486 1-1-5 Sekiguchi Stone Mountain, GA 30086-1486 Bunkyo-Ku (800) 842-0888 Tokyo 112 Japan 81-3 (5261) 1160 US Office (Texas) (713) 493-9925 Kelly Computer Systems Kingston Technology Corporation 1101 San Antonio Rd. 17600 Newhope Street Mountain View, CA 94043 Fountain Valley, CA 92708 (415) 960-1010 (714) 435-2600 Martech Merida Systems 1151 W. Valley Blvd. (617) 933-6790 Alhambra, CA 91803-2493 (800) 582-3555 (818) 281-3555 MDL Corporation 15301 NE 90th St. Redmond, WA 98052 FAX (206)861-6767 (800)800-3766 (206)861-6700 Newport Digital R Squared 14731 Franklin Avenue 11211 E. Arapahoe Rd., Suite 200 Suite A Englewood, CO 80112 Tustin, CA 92680 (303) 799-9292 (714) 730-3644 (800) 777-3478 (Thanks to Roy McMorran ) ------------------------------ Subject: 4.2 Third party vendors for other things Vendor Product(s) ------ ---------- Andataco System integrator and peripheral reseller 10140 Mesa Rim Road San Diego, CA 92009 (619)453-9191 inquire@andataco.com Disk Emulation Systems, Inc. Solid-state disk emulators (SSDs) 3080 Oakmead Village Dr. Santa Clara, CA 95051 FAX: 408-727-5496 (408)727-5497 diskmsys@netcom.com IEM, Inc. Tapes (4mm, 8mm, QIC, 3480), disks, 1629 Blue Spruce Drive optical, floppy and backup software. Fort Collins, CO 80524 SCSI and HP-IB peripherals. Voice: (303)221-3005 FAX: (303)221-1909 email: info@iem.com Interphase Corporation High performance bus interfaces (EISA/FDDI, 13800 Senlac VME/ATM.) Dallas, Texas 75234 (214)919-9000 ITAC Systems, Inc. Supports Mouse-trak trackball for HP-HIL 3113 Benton St. Garland, Tx 75042 (800)533-4822 yvonne@moustrak.com MDL Corporation Disk, tape, optical, jukebox, EISA expansion, 15301 NE 90th St. RAID, others. Redmond, WA 98052 FAX (206)861-6767 (800)800-3766 (206)861-6700 Modular Industrial MICHIL PS2 to HP-HIL converter. Allows Computers standard PC keyboards and mice to be connected (615)499-0700 to HP workstations Joe Malley SBE EISA serial and SCSI boards. 4550 Norris Canyon Road San Ramon, CA 94583-1389 (510)355-2000 (800)925-2666 fax (510)355-2020 Workstation Solutions Data backup and recovery solutions. One Overlook Drive Amherst, NH 03031-2800 VOX: (603) 880-0080 FAX: (603) 880-0696 jimm@worksta.com (Jimm Parsons, Technical Services Manager) (Thanks to various contributors) ------------------------------ Subject: 4.3 Do Seagate 9GB drives working with s700 and s800? The s700's and s800's can't handle anything more than 4Gb (for the forseeable future including initial 10.0 release). Another vendor, MDL, sells 9Gb drives with a driver for HP-UX. MDL can be reached at: Michael Lampi lampi@mdlcorp.com MDL Corporation (206) 861-6700 15301 NE 90th Street (206) 861-6767 FAX Redmond, WA 98052 (800) 800-3766 Mosaic: http://www.halcyon.com/mdlcorp/ (thanks to Bill Hassell ) ------------------------------ Subject: 5. UTILITIES ------------------------------ Subject: 5.1 ASCII to Postscript converter. You can get an ASCII to Postscript converter from: ftp://ftp.uu.net/usenet/comp.sources.misc/volume10/a2ps3.Z Additionally, nenscript is available from various FTP sites. ------------------------------ Subject: 5.2 How do I make perl on HP-UX? Reply like this to Configure: 1. When it asks for optimization flags answer +O1 if you have HP-UX 7.05 or less -O if you have HP-UX 8.0 or later. 2. When it asks for additional flags to cc answer -DJMPCLOBBER 3. When it asks for additional libraries answer -lndbm -lm (ignore the other libraries Configure finds). You can also safely add -lBSD if you wan't BSD signal semantics. 4. When it asks if you wan't to use perl's malloc answer y If you have HP-UX 8.07 or later you may choose to answer no to this since that malloc is OK. 5. When perl asks on which boundarie a double must be aligned answer 8 if you are on a 9000/800 or 9000/700 series machine (HP-PA architecture). 2 otherwise (Motorola 68k architecture) NOTE: That an already compiled version of Perl 5.000 can be found on the Liverpool archive and its mirrors. ------------------------------ Subject: 5.3! What is the status of the various gnu items on HP-UX? Pierre Mathieu periodically posts a list to comp.sys.hp.hpux; the last revision is 2.3. Jeff Law of the University of Utah maintains an archive on jaguar.cs.utah.edu of the latest PA-RISC ported compiler tools; see question 3.13 above for details. ------------------------------ Subject: 6. X WINDOW SYSTEM, MOTIF, AND HP-VUE ------------------------------ Subject: 6.1 X11 libraries (Athena, etc.) and utilities (imake, etc.). As you may have noticed, HP does not ship a "full" set of X11 libraries and include files, and does not provide imake or associated tools. There is a HP maintained, but UNSUPPORTED, set of X11R4 libraries and utilities for the HP 9000 Series 300, 400, 700, and 800. You can get the libraries, include files, and config files (imake) via anonymous FTP from ftp://hpcvaaz.cv.hp.com/pub/MitX11R4/libs.s*00.tar.Z. This is also archived on the iworks node as mentioned above. HP has also submitted X11R5 sources to the iworks node as mentioned above. And, Bo Thide has X11R4 and R5 support available via anon. FTP as mentioned above. ------------------------------ Subject: 6.2 How can I display an image on the root window with HP-VUE? Set Vuewm*backdrop*image: none. Note that there is an explicit pick for this in the Style Manager with HP-VUE 3.0. When the backdrop is clear, you can use xloadimage, xsetroot, xv, or the like to display the image of your choice. ------------------------------ Subject: 6.3 How do I get a scroll bar on hpterms? Set the following resources: HPterm*scrollBar: TRUE HPterm*saveLines: 1024 or some other other arbitrarily large number. To do this interactively, use "hpterm -sb -sl 1024". You can also set these in an app-default file (/usr/lib/X11/app-defaults/HPterm). You can also set saveLines to something like "4s", which indicates four screens. If you want the VUE panel terminal icon produce hpterm's that have scroll bars, and also have their login shell run at the startup of the terminal. To do this you have to modify the default action of the VUE panel. The easiest way to do this on a system-wide basis is to edit the "/usr/vue/types/xclients.vf" file. Change the line that says "hpterm" to "hpterm -ls -sb -sl 400": /usr/vue/types/xclients.vf ACTION Hpterm TYPE COMMAND WINDOW-TYPE NO-STDIO EXEC-STRING hpterm -ls -sb -sl 400 DESCRIPTION The Hpterm action starts an hpterm terminal emulator. END (Thanks to Greg Cagle and John Kemp ) ------------------------------ Subject: 6.4 How can I put a title in my hpterm titlebar? Here is a two line program that you might find useful: /* Quick and dirty program to put argv[1] in the title bar of an hpterm Tom Arons March 1992 */ #include main(argc,argv) int argc; char **argv; { printf("\033&f0k%dD%s", strlen(argv[1]), argv[1]); printf("\033&f-1k%dD%s", strlen(argv[1]), argv[1]); } An alternative is: #!/bin/sh LENGTH=`strlen $1` echo "&f0k${LENGTH}D$1\c" That's ESC between the first quote and the f0k. strlen, in case you don't have it, comes from: #include main(argc, argv) int argc; int *argv[]; { if (argc != 2) exit(0); printf("%d\n", strlen(argv[1])); } To set the title in the icon: #!/bin/sh LENGTH=`strlen $1` echo "&f-1k${LENGTH}D$1\c" Where the & is ESC. (Thanks to Tom Arons and John T. Beck, HP.) ------------------------------ Subject: 6.5 How come my hpterms keep going away by themselves? You are probably using the C Shell (/bin/csh) and have autologout set (it is set to 60 minutes by default). Put an "unset autologout" in your ".cshrc". If you are using the korn shell it is probably due to the value set for the shell variable TMOUT. Set it to 0 (infinite timeout). (Thanks to Jim Sharpe for the Korn Shell information.) ------------------------------ Subject: 6.6 How come my HP X/Motif clients take a LONG time to display on a Sun? The problem is with the OW3 server. You can request OW3 patch 100444-35 (or whatever is the current replacement) from Sun to fix the problem. Supposedly this has been rolled into OW 3.0.1. A workaround is to set the X resource *useColorObj: False on the Sun. ------------------------------ Subject: 6.7 How can I get my login stuff to work under HP-VUE? Suggestion 1) The HP-VUE User's Guide suggests that people make a copy of /usr/vue/config/sys.vueprofile to ~/.vueprofile. This file contains a detailed set of comments about setting it up so that their .login/.profile will be sourced correctly (including details on making sure that tset(1)-like programs are only run when *NOT* in HP-VUE). Suggestion 2) When you login via VUE, VUE sources ~/.vueprofile *INSTEAD OF* your .login (csh), .profile (sh/ksh), and other startup files. Whatever actions are taken in ~/.vueprofile are persistent across any children started by VUE. Meaning that if you symbolic link ~/.vueprofile to your ~/.profile, then VUE will source your ~/.profile before starting the window system, and all children (hpterms/xterms and their interactive shells) will inherit this environment (prompt variables et al). Documentation indicates your ~/.vueprofile should contain either csh, or sh/ksh syntax, depending upon what your login shell is. When csh is my login shell, I set my ~/.vueprofile to contain only two lines: if ( -f /etc/csh.login ) source /etc/csh.login if ( -f ~/.cshrc ) source ~/.cshrc When sh/ksh is my login shell, I set my ~/.vueprofile to contain only two lines: test -f /etc/profile && . /etc/profile test -f ${HOME}/.profile && . ${HOME}/.profile So, before starting the window manager and any clients, VUE makes sure that all my shell startup files are sourced and all the variables I want in my shell environment are already there and waiting for me. (Thanks to David Masterson , and Steve Jumonville, HP) ------------------------------ Subject: 6.8 How can I get console messages to go to an hpterm? You can avoid console messages writing to your graphics planes and trashing your VUE session by starting an hpterm and designating it to receive console messages, and to de-iconify, when console messages are received. Put something like this in your "vue.session" file in ~/.vue/sessions/home. (line wrapped for readability): # Start up the Terminal Console as iconic, and raise it if any output vuesmcmd -cmd "hpterm -C -iconic -ls -sb -sl 256 -name Console -T Console -xrm *mapOnOutputDelay:\ 30 -xrm *mapOnOutput:\ True -xrm Console*clientFunctions:\ -close -xrm *workspaceList:\ all" (Thanks to Steve Jumonville, HP) ------------------------------ Subject: 6.9 What happened to the vuewm key accelerators at VUE 3.0? Well, we don't really know. Here's how to set them, though. Add an entry like this (you can, of course, customize it to your liking) to your $HOME/.vue/vuewmrc file: Menu VueWindowMenu { "Restore" _R AltF5 f.normalize "Move" _M AltF7 f.move "Size" _S AltF8 f.resize "Minimize" _n AltF9 f.minimize "Maximize" _x AltF10 f.maximize "Lower" _L AltF3 f.lower no-label f.separator "Occupy..." _O AltO f.workspace_presence "Occupy all" _a Alt ShiftO f.occupy_all no-label f.separator "Remove from WS" _e Alt Shift F4 f.remove "Close" _C AltF4 f.kill } And then add this resource: Vuewm*windowMenu: VueWindowMenu And restart the window manager. (Thanks to Bill Bennett, HP) ------------------------------ Subject: 6.10 How come I can no longer disable the caps lock key with xmodmap? A common activity in the past has been to disable the, shall we say, "placement challenged" caps lock key on the ITF keyboard using a simple xmodmap script. This no longer works consistently at X11R5/VUE 3.0; the best solution so far: In file ~/.vue/sessions/lite/vue.session: /usr/bin/X11/xmodmap - << EOF clear lock keycode 55 = Control_L keycode 86 = Caps_Lock keycode 39 = grave asciitilde guillemotleft guillemotright keycode 71 = Escape add Lock = Caps_Lock add Control = Control_L EOF This works until logout/login, when Caps Lock toggles the control feature, even though 'xmodmap -pm' shows that Lock has no assignments. You have to restart the server to reset completely, which can be automated by setting the value Vuelogin*terminateServer: True in the file /usr/vue/config/Xconfig. ------------------------------ Subject: 6.11 How come vi behaves strangely in xterms at 9.01? Apparantly initial invocation of xterm under csh does not set LINES/COLUMNS correctly, and vi doesn't handle that real well. One workaround is to put the following in .cshrc: if ( $?WINDOWID ) then set noglob;eval `/usr/bin/X11/resize`;unset noglob endif PHSS_2753 addresses this problem. (Thanks to Raymond Nijssen for the workaround.) ------------------------------ Subject: 6.12 How do I disable HP-VUE? There have been several recommendations on this base thread. Here is one that is documented for X terminals (it works for workstations too). This takes advantage of the fact that Vue sets several environment variables for the session, one of which is USER. Modify the /usr/lib/X11/vue/Vuelogin/Xsession (pre-9.0 HPUX) or the /usr/vue/config/Xsession (9.0 HPUX and later) file: 1) Go to the portion that contains the coment "Determine the startup if the user didn't specify one." -- approximately line 295 in an unaltered version of the file. 2) Add a following case statement to fit your needs. It should look something like: case $USER in martha | joe) startup=${HOME}/.x11start'' esac You can add as much or little intelligence to this as you like. The above assumes that the users' have a .x11start script in their home directory, that its permissions are correct, etc. You can build in a fallback machanism. For example, the script will check to see if the user has a .x11start script and if not, to fallback to /usr/lib/X11/sys.x11start. To see an example of this logic, do a more(1) on /usr/bin/x11start. The above case statement is documented in Ch 2 of the "HP 700/RX System Administrators Guide". Anoter method of disabling VUE assumes you have a .xsession file that starts up your initial xterms, other programs, and window manager. Replace your ~/.vueprofile with: #! /bin/sh exec sh $HOME/.xsession Note that the first line was needed, since /usr/lib/X11/vue/Vuelogin/Xsession looks for the shell it want to use. (Thanks to Bill Morrison, HP and John Bowe ) ------------------------------ Subject: 6.13 What's a good termcap entry for hpterm? Although it is not supported for hpterm use, the 262x entry in /etc/newconfig/termcap will work. (Thanks to Frank Slootweg, HP) ------------------------------ Subject: 6.14 My screen is wedged. What should I do? One thing you can try is to unplug the keyboard for ~5 seconds. Note that you will have to rerun xset -r to get autorepeat to work after doing this. (Thanks to Paul Liebert, HP.) ------------------------------ Subject: 6.15 How can I get an X client to come up in an alternate workspace? You can try: client -xrm "*workspaceList: " (Thanks to ) ------------------------------ Subject: 6.16 How can I get HP-VUE to not override colors? The Motif library on HP-UX has extra code added to make the default colors follow the color schemes that the user selects with the vuestyle controls. This extra code makes trouble for some applications which don't want this unique and unexpected behavior. You can prevent the entire color scheme mechanism from being used in an application by setting "*useColorObj: False" for the application before creating the first widget. This can be done by adding the resource to the application defaults, the fallback resources, or as an extra "-xrm" "*useColorObj: False" args pair in the argv and argc parameters passed to XtAppInitialize. If you set the resource in xrdb it would be best to set it for only specific applications like "MyApp*useColorObj: False". Setting the useColorObj resource could make programs core dump on some 8.0* systems. There is a patch that corrects the core dump. You can use the vue colors and prevent the specific difference between dialog colors vs. non-dialog colors by setting a resource that specifies the behavoir of the color scheme mechanism. To force the dialogs to use the same colors as the other windows set the following resources in your app_defaults file or fallback settings- *primaryColorSetId: 3 *secondaryColorSetId: 3 This sets the dialog or "secondary" colors to the same set as the primary colors. This is discussed in the "HP VUE 3.0 User's Guide" in chapter 26. (Thanks to Mike Stroyan, HP.) ------------------------------ Subject: 6.17 How can I override the system default printer in vuepad? cp /usr/vue/types/vuepad.vf $HOME/.vue/types Edit the file and change the ACTION PRINT_PR_VPAD to: # The PRINT_PR_VPAD action paginates its arguments using pr(1) and prints # them with lp(1). It uses arg 2 for a title. It then removes the temp # file. This action is used by the client vuepad. ACTION PRINT_PR_VPAD TYPE COMMAND WINDOW-TYPE NO-STDIO EXEC-HOST %LocalHost% EXEC-STRING /bin/sh -c "pr -h %Arg_2% %(File)Arg_1% | \ lp -d%"Printer:"%; rm %(File)Arg_1%" ^^^^^^^^^^^^^^ END This will cause a dialog box to appear to prompt you for a printer name. However, if you set LPDEST in your .vueprofile, then lp will use that value instead of the system default. (Thanks, Dan Mercer, ) ------------------------------ Subject: 6.18 What about X11R6? The basic core distribution of X11R6 is now installed on the Liverpool FTP archive. See section 3.12 for details. Current contents: XR6src-6.0.part0{1,2,3}.tar.gz XR6built-6.0.tar.gz Notes: - the binaries are designed to be installed in /usr/local/X11R6 (use a symbolic link, or grab the source if you want them elsewhere) - most libraries come with archive and shared versions (and the built binaries mostly use the .sl versions) - this is JUST the core distribution (xc/) - xc/test and xc/workInProgress aren't included in the built package (the source is present, but hasn't been looked at in the src packages) (Thanks to Dave Shield, Liverpool) ------------------------------ Subject: 6.19 How can I set user-specific app-defaults in HP-VUE? HP-VUE looks in the directory $HOME/.vue/app-defaults in addition to the default location (/usr/lib/X11/app-defaults). ------------------------------ Subject: 6.20 How can I get VUE to share colormap entries: VUE, by default, allocates several read/write colorcells in the default colormap so that it can change the VUE colors by just changing the colormap instead of re-writing all the pixels. Read/write colorcells are not sharable, and if you have the maximum number of colors selected in your VUE palette, quite a few are going to get soaked up and not be available for other color hogs like xv. If you can live with having to restart VUE whenever you change your palette, then set the following resource: *dynamicColor: False This will cause VUE to allocate read-only cells, which other apps can share. (thanks to Karl Schulz, HP ) ------------------------------ Subject: 6.21+ How can I disallow root login at the console with VUE? Configure your /usr/vue/config/Xstartup as something like this : if [ -f /etc/securetty ] && # pwget is an HP command which checks also for Yellow Pages. # exit code from awk is inverted (!) since sh's tests are... # === a more simple test would be [ "$USER" = root ] === pwget -n "$USER" | awk -F: '{ exit !($3 == 0) }'; then echo Root Login not allowed | /usr/lib/X11/ignition/text_dialog ERROR exit 1 fi if [ -f /etc/nologin ]; then exit 1 fi exit 0 See man vuelogin(1X) for more details. (Thanks to Cyrille Lefevre ) ------------------------------ Subject: 7. OPERATING SYSTEM ------------------------------ Subject: 7.1 Can I have filenames longer than 14 chars? Yes, change to long filenames using /etc/convertfs. You can't go back, though. Here's how to check if an existing filesystem has long filenames enabled: # tunefs -v /dev/rdsk/XXX | grep magic magic 95014 clean FS_OK time Tue Mar 23 14:13:01 1993 \__ if = 95014 then long filenames \__ if = 11954 then short filenames You can also look at this on a per directory basis with the POSIX command getconf: $ getconf NAME_MAX directory (Thanks to Ken Burke and Masataka Isoya ) ------------------------------ Subject: 7.2 How can I tell what products have been loaded on my system? Check the /etc/filesets directory. There is a file there for each fileset that has been loaded that summarizes the files in that fileset. This directory is used by the /etc/update, /etc/updist, /etc/netdistd, and /etc/rmfn utilities for loading and unloading software. ------------------------------ Subject: 7.3 How do I safely remove software from my system? The _only_ safe way to remove HP software is to use /etc/rmfn. ------------------------------ Subject: 7.4 What's the scoop on HP-UX 9.03/9.04? HP-UX 9.03 and 9.04 have now been officially released from HP and are available on request from your software support coordinator. Support is included for the 712 workstations, and many patches are included. ------------------------------ Subject: 7.5 How come HP-UX doesn't support NFS root access? HP-UX versions previous to 9.X do not support NFS root access to mounted file systems. This because they are at an old revision of NFS. You *can* hack your kernel to provide it, but it's dangerous, unsupported, and a security hole. 9.X supports full NFS 4.1 functionality, including NFS root. ------------------------------ Subject: 7.6 How can I change the order of hostname resolution? Patches exist for 9.x that allow hostname resolution along the lines of Solaris 2.x. See the latest patch listings for details. ------------------------------ Subject: 7.7 How come the LOGnnnn files in /usr/adm keep growing and growing? The LOGnnnn files in /usr/adm (8.x except 8.02) or /usr/adm/diag (8.02 and 9.0) are the diagnostic event log files. Most likely the files are growing for one of two reasons: either the diagnostics system was improperly installed, or there is an actual hardware problem on the system. (Thanks to Wayne Krone of HP) ------------------------------ Subject: 7.8 How come I can't lock mail or other files on a Sun? Believe it or not, Sun's lockd is broken at 4.1.x. The proper Sun patch number is Patch-ID# 100075-09, called the "lockd jumbo patch". ------------------------------ Subject: 7.9 Why are mail files in /usr/mail are owned by daemon instead of the recipient? The mail delivery agent /bin/rmail needs to be able to chown(2) these files. It cannot do so if you have removed the privilege CHOWN (see setprivgrp(1m); removing CHOWN is recommended to prevent cheating on disk quotas). To get around this, noting that /bin/rmail runs setgid to group mail, you can grant privilege CHOWN to group mail only by inserting the line "mail CHOWN" in /etc/privgroup. The change takes effect on the next reboot, or immediately if you execute the command "setprivgrp -f /etc/privgroup". (Thanks to Jim Richardson ) ------------------------------ Subject: 7.10 How can I tell if I need more than a 2-user license? There are several fundamental things to remember about HP-UX licensing: o Series 700 and Series 800 users are now counted the same way o Display console counts as one user o Each ASCII terminal counts as a user, regardless of how it is connected o The LAN connection counts as one user Ascii Terminals The simple rule to remember is any ASCII terminal that is logged in counts as a user. ASCII terminal connections can come in several different forms: o Direct-connected via a serial terminal multiplexer o Connected via Data Terminal Concentrators (DTCs) or via terminal servers o Personal Computers (PCs) acting in terminal emulation mode, whether connected via serial line or via Local Area Network (LAN) X-terminals and workstations When a customer buys an X-terminal or workstation from HP or from another vendor, HP acknowledges that the customer has also bought a single Unix license-to-use. Therefore, the customer has the right to an unlimited number of logins and terminal windows _over_the_LAN_ to a Series 700 or Series 800 from either X-terminals or workstations. These logins can be via X terminal windows (_hpterm_ and _xterm_), _telnet_, _rlogin_, or other means. PC's that use X-terminal emulation software such as XView each count the same as an X terminal. This is because the PC essentially becomes an X-terminal when it is running the X server software. Therefore, when a PC is running an X-terminal emulator, the PC has the right to an unlimited number of logins to an HP-UX system. Exceptions The policy of counting DTC users is new for the Series 700. Customers who purchased Series 700 systems prior to HP-UX 9.0 shipments (late calendar 1992) and use them as host systems for multiple DTC- connected terminals, may continue to use those configurations without buying a license upgrade. An update to HP-UX 9.0 will not lock out these configurations. (Thanks to Tony Hart, HP) ------------------------------ Subject: 7.11 How can I tell what patches are in the kernel? "what /hp-ux" will present you with patch strings, which you can compare with the strings called out in the patch text file. A typical patch string is: PATCH_8.07 nfs_vnops.c 1.15.61.4 92/01/10 PHKL_0736 PHKL_0942 which shows that PHKL_0942 has been applied to the kernel. ------------------------------ Subject: 7.12 How come I have to hit return after control-d in the Korn shell? You need to set the "viraw" option. ------------------------------ Subject: 7.13 How do I boot into single user mode? Press ESC to stop the auto-boot. When the list of boot devices is presented: b PX ISL (where X is your root disc) And at the ISL> prompt: ISL> hpux -iS disc(;0)/hp-ux The '-iS' are the flags to init which says come up single user. The rest of the command is what the bootprocess does automatically. (Thanks to Stuart Jarriel .) ------------------------------ Subject: 7.14 How come my Korn shell login hangs? This can happen if the user's home directory is across an NFS mount point; you can workaround the problem by completely unprotecting (chmod 777) .sh_history, or by pointing HISTFILE to somewhere local. ------------------------------ Subject: 7.15 How can I avoid those annoying copyright notices on login? The following code in /etc/profile prints the copyright notice the first time each user logs in: NUMLOGINS=`/etc/last -2 $LOGNAME | wc -l` if [ $NUMLOGINS -lt 2 ] then cat /etc/copyright fi And, for /etc/csh.login: set NUMLOGINS=`/etc/last -2 $LOGNAME | wc -l` if ( $NUMLOGINS<2 ) cat /etc/copyright (Actually, each user will get the copyright on their first login after each time the /etc/wtmp file is pruned, but that needn't be often.) (Thanks to Paul Gootherts , Steve Dum and John Pelan ) ------------------------------ Subject: 7.16 How can I turn off quota checking? Suggestions: 1] rmfn quota fileset. This will still allow you to keep using quotas, as long as the nfs-server still has quota enabled, and is exporting it with all the quota stuff turned on, even though the HP itself might not have it. Watch out tho, since this deletes /usr/bin/quota :) So make a copy, if you still want to have the ability to do "quota -v" and stuff around. 2] mv /usr/bin/quota /usr/bin/quota_check. cp /bin/true /usr/bin/quota. This will still make the login program do the quota-check, but at least it goes by very very quickly now (as opposed to actualy checking every single nfs-mount with quota, and so on.) Then, just run quota_check whenever you want. 3] rmfn quota fileset. cp /bin/login /bin/login.noquota. re-add the quota fileset. mv /bin/login.noquota /bin/login. This will basically giv eyou a copy of the /bin/login program, that just doesn't go off and call the quota-program. 4] Remove execute permissions for /usr/bin/quota as in: $ chmod -x /usr/bin/quota This prevents quota from running. It's also a self documenting flag in that a future system manager who tries to run /etc/quota will get the "cannot execute" error message. (thanks to Paul Hirose ) ------------------------------ Subject: 7.17 What are the issues with HP-UX 9.01? Some of the things that people have seen with HP-UX 9.01. Problems that have been patches are noted; see the latest patch catalog for specific patch numbers. rmfn of the NW-7XX fileset leaves behind an empty directory (/etc/conf/netware) and subsequent kernel builds (for patch install) fails until this directory is removed by hand. When the length of a macro expansion exceeds an unspecified size, cpp.ansi leaves some macros unexpanded in the output. Patched. The linker does not traverse shared library search paths itself. Patched. Various X11 problems have been reported including drawing problems and memory leaks. Get the latest X server. Various serious C compiler problems. Patched. Memory leaks can occur and lock up a system; patched. catman will core dump; patched. There has been some controversy over the implementation of the dynamic buffer cache at 9.01; people have been seeing situations where the cache has grown quite large and the syncer takes over the system swapping it out. You can limit the growth of the buffer cache to physical memory (default) with patch PHKL_2449, or you can disable it altogether with the "bufpages" kernel parameter; set bufpages to 10% of your physical memory, e.g. if you have an S700 with 16M of memory, set bufpages to: bufpages = 16,000 K physical ram / 4 K per page / 10 (percent ) = 400 (Thanks to various people, too numerous to mention.) ------------------------------ Subject: 7.18 Why does chown behave differently at 9.x? chown(2) on symbolic links now chown's the file which the link is pointing to instead of the link itself. If you want to go back to the olf behavior, you can set the 'hpux_aes_override' parameter to '1'. This can be done by modify /etc/master ('hpux_aes_override AES_OVERRIDE 1') and changing the dfile 'hpux_aes_override 1'. Or by adb'ing the kernel; adb -w /hp-ux /dev/kmem hpux_aes_override?W 1 # For the /hp-ux hpux_aes_override/W 1 # For the current kernel $q (Thanks to Trond Haugen, HP) ------------------------------ Subject: 7.19 How can I track log files and core files? At 9.x, SAM allows you to track all standard log files and trim them if desired. It will also find all core files on a file system and allow you to get rid of them. ------------------------------ Subject: 7.20 How much memory can a process use? The first limiter is probably swap space. The combined virtual data space of all running processes can't exceed swap size. Run /etc/swapinfo -t and look at the total line. That's all you have left. For FORTRAN programs: -------------------- 1) Increase the kernel's stack limit (maxssiz). You can do this with sam (Kernel Configuration-> Modify Operating System Parameters-> Process Parameters). The practical limit for user stacks is around 80 Mbytes. Your system probably has an 8 Mbyte limit. Try 16 Mbytes or 32 Mbytes depending on your expected use. Give sam a number that is a multiple of the 4096-byte pagesize. 2) Change your array allocation. HP FORTRAN allocates non-common, non-SAVE'd arrays on the process stack. Common blocks and SAVE'd variables are allocated in the process data segment (with much larger size limits). If your arrays are declared in the main program and passed to subroutines, you can just SAVE the big ones in the main program, or put them in a common block in the main program, or recompile with -K since -K puts all local variables in the data segment. (-K is a sledgehammer approach, but it gives you a quick indication that stack size is the issue.) 3) Make sure you have enough swap space. ------------------- (Thanks to Bob Montgomery, HP) ------------------------------ Subject: 7.21 How come there's little discussion of DCE? DCE (Distributed Computing Environment) is an OSF-based product. HP now ships a DCE product. Most of the discussion concerning DCE takes place in comp.unix.osf.misc. ------------------------------ Subject: 7.22 How can I make a ramdisk? THIS IS UNSUPPORTED. Make sure 'ram' is configured into your kernel, and then make device files with major 9 (both blcok and char), minor 0xVSSSSS, where V is the volume number, SSSSS is the number of sectors in the ram disk, and a sector is 256 bytes. For example, mknod /dev/ram1m c 9 0x101000 makes a 1 meg ram disk. Of course, you have to make a file system on it and mount it to make it useful: mkfs /dev/ram1m 1024 Note that you will have to make a block device also. This works for all 9.x systems (I did it on 9.05 - Greg). (Thanks to Rob Gardner, HP ) ------------------------------ Subject: 7.23 How come I can't lock files across NFS after upgrading to 9.01? You may need to replace your /etc/group with the 9.01 version: Upgraded 9.01/ Installed 8.07 version 9.01 version root::0: root::0:root other::1: other::1:root,hpdb bin::2: bin::2:root,bin sys::3: sys::3:root,uucp adm::4: adm::4:root,adm daemon::5: daemon::5:root,daemon mail::6: mail::6:root lp::7: lp::7:root,lp users::20: users::20:root nogroup:*:-2: (Thanks to Robin Strong ) ------------------------------ Subject: 7.24 What's a good strategy for clearing /tmp? Two suggestions (to be run from cron) are: find /tmp -depth -hidden -fsonly hfs -atime +1 -exec rm -rf {} \; The -depth option ensures no directory is removed before its contents, -fsonly hfs is because occasionally I've NFS-mounted stuff there and it's better to do the clearing in the machine where it's local, and -hidden is in case CDF's appear there for some reason. (Thanks to Tapani Tarvainen) for i in /tmp /usr/tmp do find $i -type f -atime +3 -print -exec rm -f {} \; find $i -type d -atime +3 -print -exec rmdir {} \; done (Thanks to Rich Jennings, HP) ------------------------------ Subject: 7.25 How can I change the timezone? Edit the entry in /etc/src.sh and /etc/src.csh, and reboot. ------------------------------ Subject: 7.26 How can I look at what my system is doing? The best tool for monitoring your system is HP GlancePlus. In the U.S. call (800) 237-3990 for a trial version. Outside the U.S. contact your HP sales representative. HP sells other performance tools as well including HP Performance Collection Software, HP PerfRX (for long-term performance analysis of a single system), and HP PerfView which runs under OpenView (for simultaneous monitoring of a network of systems including HP-UX, Sun Sparc, and IBM AIX). You can also use /usr/contrib/bin/monitor if it exists on your system, but it is not as accurate or reliable as GlancePlus, and is not an HP supported product. ------------------------------ Subject: 7.27 How can I partition HP-UX disks on 700s? Here is a sample file which lists the sdsadmin commands to partition a disk into 2 partitions. Note that this is specific to the M2654SA disk; your mileage may vary. The mediainit is probably not required if the vendor has formatted/verified the disk. It is not "supported" to partition the boot disk, and you have to go through some contortions to do it. Note also that in order to have several partitions on the root disk AND have swap, you must create another partition which you dedicate to swap. # # SDS configuration file for this node. # # To rebuild the /u1 and /news Fujitsu M2654SA disk partitions, do: # mediainit -v /dev/rdsk/c201d5s0 # sdsadmin -m -C /usr/local/etc/sdsadmin.config.u1news /dev/dsk/c201d5s0 # newfs -L -n -v -m 2 -i 16384 /dev/rdsk/c201d5s1 HP_M2654Su1x1-2 # newfs -L -n -v -m 2 -i 2048 /dev/rdsk/c201d5s2 HP_M2654Su1x1-2 # # Disk partitions: # # 1 /u1 145xxxx 1K blocks (/dev/dsk/c201d5s1, /dev/rdsk/c201d5s1) # 2 /news 55xxxx 1K blocks (/dev/dsk/c201d5s2, /dev/rdsk/c201d5s2) # - ----- ------- # 2006016 1K blocks # type M2654Su1x1-2 label u1_news partition 1 size 1450000K partition 2 size max (Thanks to Mike Petersen and Timothy Mooney ) ------------------------------ Subject: 7.28 How can I print man pages successfully? To get the italic and bold fonts from the man file on a Laserjet: zcat manfile.1 | nroff -man -Tlj | lpr ... On a PostScript printer ( you need the GNU groff): zcat manfile.1 | groff -man -Tps | lpr ... If your man file is a complex one including tables, pipe it through tbl. Some man pages like ioctl may need the HP macros: zcat manfile.1 | groff -t -e -C -M/usr/lib/tmac -man -Tps | lp ... (Thanks to Poul Moller, Markus Gyger) ------------------------------ Subject: 7.29 How can I limit core files? HP-UX has no built in function to limit core file generation from the standard shells; one way to limit core file generation is to create a directory called "core" with 000 permissions in the directory in which you expect a core dump to occur. Additionally, two programs are available (nocore and corelimit) that can be used as wrappers around other programs that you may expect to dump. And, some publicly available shells (tcsh, for example) allow core file limits. Or, you can place a link called "core" to /dev/null in the directory you expect the core dump to occur. Here is the source for corelimit (thanks to John Agosta, HP). It is completely unsupported; the Response Center will disavow all knowledge of you and your mission should you call them with a problem relating to this. Build it in the usual way (cc -o corelimit corelimit.c) and use it in the format of: "corelimit hpterm 0". This will limit the core file size of all children of the hpterm process to 0. #include #include #define RLIMIT_CORE 4 /* core file size */ main(argc, argv) int argc; char **argv; { int res; struct rlimit rlp; if (argc != 3) { fprintf(stderr, "%s: wrong number of parameters\n", argv[0]); fprintf(stderr, "\tformat: %s command core_size\n", argv[0]); exit(-1); } rlp.rlim_cur = atoi(argv[2]); res = setrlimit(RLIMIT_CORE, &rlp); if (res < 0) { perror("setrlimit: RLIMIT_CORE"); exit(-2); } system(argv[1]); } Or, you can edit /etc/vuerc to start all of VUE that way: at line 22 replace: exec $VUELOGIN $VL_ARGS /dev/null 2>&1 by: exec /usr/local/bin/nocore $VUELOGIN $VL_ARGS /dev/null 2>&1 (thanks to Jean-Claude Arnouil, ) ------------------------------ Subject: 7.30 Can I put more than one backup on DDS with fbackup? No. fbackup always rewinds the tape. Possible alternatives: (1) Stick with dump. (2) Use a pipe: instead of telling fbackup where the DAT is, let it send its output to stdout (-f -) and pipe it (thru remsh from the other machine) to the DAT, using no-rewind device. You'll lose fast search ability, though. (3) Turn your machines into a cluster served by the one with the DAT and do all backups there. Unfortunately clusters are not supported at hp-ux 10.0, so this is not a long-term solution. (4) Use NFS and mount the disks of the machine without DAT to the other and back them both up there. You'll have to mount 'em with root permissions and restoring a completely destroyed root disk will be messy. (5) Scream at HP until they fix fbackup. :-) (Thanks to Tapani Tarvainen, ) ------------------------------ Subject: 7.31 How can I load multiple patches on a machine at the same time? The easiest way to do it is to set up a netdist server by using /etc/updist to load all the patches you want into a netdist area, and then starting /etc/netdistd. ------------------------------ Subject: 7.32 How can I set up an HP-UX workstation as an X terminal? Install minimum OS with network and X11 (without motif or vue). Edit /etc/inittab, change the following lines init:2:initdefault: vue :34:respawn:/etc/vuerc # VUE validation and invocation to init:3:initdefault: vue :34:respawn:/usr/bin/X11/X -query HOSTNAME # X server startup Replace HOSTNAME by the name of the host running xdm, vuelogin or whatever. (thanks to Kay Marquardt, ) ------------------------------ Subject: 7.33 What causes "Unable to initialize MI" when running Glance? This error can occur for many different reasons but it indicates that the glance program had trouble starting the midaemon process. Further details are available in ~/glance.err and/or /usr/perf/log/`hostname`/midaemon.err. See man midaemon(1). Older revisions of HP GlancePlus (prior to B.09.00 for series 700/800 systems and prior to A.09.07 for series 300/400 systems) had a Known Problem in which it was occasionally necessary to issue the following command when the above error occurred: rm /usr/perf/databases/`hostname`/*.data Do NOT remove other files in the directory /usr/perf/databases/`hostname`/ because they may be required for other performance tools such as HP PerfRX or HP PerfView. This problem has been fixed in the current release of HP GlancePlus (versions B.09.00 or greater for s700/800). Please contact your HP Support Representative when you experience problems with HP software products. Your HP support contact will know how to obtain additional information to characterize your specific problem. Please note the product version (ie: "what /usr/perf/bin/glance") when reporting problems. (thanks to Doug Grumann ) ------------------------------ Subject: 7.34 How come I can't get all of my swap space? The default value of the kernel parameter "maxswapchunks" limits the swap accessible by the kernel to 512M; if you configure more swap, you need to increase maxswapchunks. ------------------------------ Subject: 7.35 How come I can't start my Aserver? Often this is because "localhost" isn't configured in DNS. Try: nslookup localhost If that command fails, you will want to have an entry added to your name servers for "localhost.your.particular.domain" pointing at 127.0.0.1. (thanks to rick jones, HP) ------------------------------ Subject: 7.36 How can I get a daemon to successfully start from /etc/rc? /etc/rc will kill all child processes on exit; daemons started from localrc() (for example) must have called setsid() and have been given time to daemonize (what a word!) themselves. If your system doesn't have the C compiler you can use a call to nohup to start the daemon instead of calling setsid(). (thanks to Mike Peterson, ) ------------------------------ Subject: 7.37 How come my /dev/null keeps getting blown away? Apparantly this can occur if root invokes the C compiler on a nonexistant file. ------------------------------ Subject: 7.38 How can I track network packets? ******************************************************* * * Network Tracing with nettl - for HPUX 8.x and up * ******************************************************* TRACING - trace all packets seen by the device driver on the HP nodes, except diskless packets. These packets are those packets sent by the node, or addressed to the node. 1. Start Trace - put data into 1MB trace file. The data will be stored in /tmp/raw.TRC0 and /tmp/raw.TRC1 The most recent data will always be in TRC0, when it fills up, TRC0 is renamed TRC1, and new logging continues in the TRC0 file. They fill up quickly! /etc/nettl -tn pduin pduout -e all -f /tmp/raw If neding to trace LOOPBACK interface as well, consider: /etc/nettl -tn pduin pduout loopback -e all -f /tmp/trace 2. Stop trace as soon as an event occurs! /etc/nettl -tf -e all 3. Format trace into a print file: /etc/netfmt -N -n -l -f /tmp/raw.TRC0 [ -c /tmp/filter ] > /tmp/fmt0 /etc/netfmt -N -n -l -f /tmp/raw.TRC1 [ -c /tmp/filter ] > /tmp/fmt1 -N - print in "nice" format (e.g. interpret) -n - print IP addresses, not hostnames -l - do not highlight fields (for hpterm) -f - optional, use a filter file (see "filtering", below) NOTE - netfmt takes a while to run! There will be plenty of info in the trace file - Interpretation may be necessary! 3a. Filtering. Create a filter file to tell netfmt what packets you are interested in seeing. E.g. only display packets to/from IP address 192.10.10.1: filter ip_saddr 192.10.10.1 filter ip_daddr 192.10.10.1 Filter out all put NFS packets (to/from UDP port 2049) filter udp_sport 2049 filter udp_dport 2049 Filter out all but TCP packets to/from port 25 (sendmail) filter tcp_sport 25 filter tcp_dport 25 Filter on ethernet addresses: filter dest 08-00-09-49-91-4a filter source 08-00-09-49-91-4a You can put these together (e.g. filter all NFS packets to/from IP addr) filter ip_saddr 192.10.10.1 filter ip_daddr 192.10.10.1 filter udp_sport 2049 filter udp_dport 2049 (thanks to Brian Hackley, ) ------------------------------ Subject: 7.39 How come my processes keep dying at 67M memory usage? You need to adjust the kernel parameter "maxdsiz"; by default the per process data space is limited to 67M. Adding physical memory and swap will have no effect until you modify the parameter. ------------------------------ Subject: 7.40 Is it possible to artificially limit the memory size? WARNING: this is non-standard, unsupported, and may change from release-to-release. For 9.01 and 9.03, there is a variable in the kernel called "soft_pages". The value is normally zero. If set to some number between 256 and the number of pages in your system, only that number of pages will be allocated as the physical memory in your system. To use this, first copy your kernel from /hp-ux to something else, so that you can recover, if necessary (this variable can be set to a small enough value that the system will be unbootable). Then to set up a, say, 16 MByte system, do: adb -w /hp-ux soft_pages?W 0D4096 or soft_pages?W 1000 Remember that the number of physical pages is not the only thing that goes into a minimum configuration---you also have to scale kernel parameters such as nproc and other tunables appropriately. ------------------------------ Subject: 7.41 How come my alt key combinations don't work in emacs X mode? Run the following through xmodmap: ! ! The following is modified from some code received from bjarne@hsr.no ! (Bjarne Steinsbo): ! keysym Alt_L = Meta_L keysym F12 = Multi_key clear mod1 add mod1 = Meta_L clear mod2 add mod2 = Alt_R Mode_switch ! This is magic! keysym Alt_R = Mode_switch The result is: - The left Alt key acts as the Meta key. - The right Alt key (Alt Gr) selects the extra characters Martin is talking about. (e.g. AltGr-o = o). - It is even possible to use both Alt keys together, resulting in Meta-versions of the extra characters. (Thanks to Geir Atle Storhaug ) ------------------------------ Subject: 7.42 I can't get Flex LM based licensing to work. For some reason, Flex licensing requires /dev/lan0 to have read and write permissions for everybody. This is somewhat insecure. One workaround is: 1. Create a new group call "lan0". 2. chgrp/chmod /dev/lan0 to look like this: crw-rw---- 1 root lan0 52 0x202000 May 20 1993 /dev/lan0 3. chgrp/chmod g+s on any binaries that need to access /dev/lan0. For example, for Interleaf, we did this to /interleaf/ileaf5/hp700/bin: -rwxr-sr-x 1 compsci lan0 5255168 Jan 29 1992 ileaf Note also that you may or may not get Flex licensing to work with the FDDI daughter card, particularly if there is no Ethernet card. Under 9.01, the Flex utility lmhostid would not return the LAN address from the FDDI daughter card. This may have been fixed at 9.03 or 9.05, but that has not been confirmed. Additionally, PHNE_4003 is supposed to fix the problem for 9.01. (Thanks to Richard Lloyd, Liverpool and Greg Vasquez, HP) ------------------------------ Subject: 7.43 How can I set up group-based FTP access? Here is how to set up ftp so that a group of users only have ftp access, they all have their own individual passwd, but they all access the same set of files (i.e., the system thinks they are all really the same ftp user). With only a slight change, you can have a group of users that only have ftp access, each with their own individual passwd, and access only to their own set of files (this is left as an exercise for the reader). 1) Set up anonymous ftp (assumed in later instructions to be at /users/ftp). 2) Add a user and group to /etc/passwd and /etc/group. For example, in /etc/passwd: ftpuser:*:1000:1000:FTP User:/users/ftp:/bin/false and in /etc/group: ftpgroup:*:1000:ftpuser Note that ftpuser login is disabled (a "*" in the password field). This allows various utilities (such as "ls") to recognize files that belong to an ftp user (particularly important for backups). To give each ftp user their own private access, set up a unique disabled user for each. 2) In /users/ftp/etc, you must have a group and passwd file, of the same format as their related system files. For example, in /users/ftp/etc/group add: ftpgroup:*:1000: and in /users/ftp/etc/passwd add: ftpuser:*:1000:1000:FTP User:/ftpusers:/bin/false Also, for each individual that you want to give access, add an additional entry. Note that these have passwords (see passwd(1) for instructions on setting passwords in this file). george:3RgfBzfnipJPQ:1000:1000:George Smith \ (FTP User):/ftpusers:/bin/false A few things to notice. "ftpuser" is disabled. "george" has the same uid, gid, and home directory that ftpuser has. "george" will login as george with his own password. To give each ftp user their own private access, add an entry that matches their /etc/passwd entry. 3) Under /users/ftp, create a directory "ftpusers". Make these directories with owner "ftpuser" and group "ftpgroup", with 770 permissions. This effectively prevents anonymous ftp access to this directories, since it is not world readable/writable. That's it. Users access the system via anonymous: $ ftp sysname Connected to sysname.whatever. 220 sysname FTP server Name (something:someuser): ftp 331 Guest login ok, send ident as password. Password: 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> Then, they use a sublogin to access their old files: ftp> user george 331 Password required for george. Password: 230 User george logged in. ftp> pwd 257 "/users/ftp/ftpusers" is current directory. ftp> Users are placed in whatever directory is specified as their home directory in /users/ftp/etc/passwd off /users/ftp. For example user "george" will be placed in /users/ftp + /ftpusers which is /users/ftp/ftpusers. To remove access, remove their passwd entry from /users/ftp/etc/passwd. This is all documented (though poorly) in the various ftp related man pages. (thanks to Aaron Friesen of HP and John Pelan ) ------------------------------ Subject: 7.44 How come my 700 doesn't perform as well as I expect? There are, of course, many answers to that question. Many people have noticed that HP's conservative choices in some configuration areas affect performance, especially relevant to Sun workstations. Two examples: fs_async kernel parameter. HP-UX by default makes all file system I/O synchronous. Sun, by contrast, defaults to asynchronous I/O and depends on the syncer. Setting this parameter to 1 can significantly increase write speeds, but at the risk of losing data in a system crash. You can change this parameter with SAM. SHARE_MAGIC vs. DEMAND_MAGIC. HP binaries by default are SHARE_MAGIC. This means that ALL pages needed are read in at invocation time. Sun, by contrast, implements demand paging by default, which speeds up the invocation time at the cost of page I/O later in process execution. You can change the behavior on HP binaries by using the chatr command. ------------------------------ Subject: 7.45 How do I convert the uname string to the model string? Here's the relationship for the most common HP-UX machines: Model number on the String returned outside of the box by uname -m ------------------- --------------- E25 --------------> 9000/806 E35 --------------> 9000/816 E45 --------------> 9000/826 E55 --------------> 9000/856 F10 --------------> 9000/807 F20 --------------> 9000/817 H20 --------------> 9000/827 F30 --------------> 9000/837 G30/H30 ----------> 9000/847 I30 --------------> 9000/857 G40/H40 ----------> 9000/867 I40 --------------> 9000/877 G50/H50 ----------> 9000/887 I50 --------------> 9000/897 G70/H70 ----------> 9000/887 I70 --------------> 9000/897 G60/H60 ----------> 9000/887 I60 --------------> 9000/897 T500 -------------> 9000/891 (Thanks to Wayne Krone (wk@cup.hp.com), and Colin Wynd (colin@col.hp.com)) ------------------------------ Subject: 7.46 Why does ksh hang when my $HOME is NFS mounted? On my 9.X HP-UX box, if a user's logon directory is NFS mounted and their start up program is ksh then ksh hangs. The problem is that ksh attempts to lock the HISTFILE. One workaround is to add the following to the .profile file for users (or correct the existing one): HISTFILE=/tmp/.sh_hist.$(whoami) export HISTFILE The latest NFS and Transport Patches fixes this problem. The patches should be installed on both the client and servers and the directories /etc/sm and /etc/sm.bak should also be removed after the installation of the patches. As of 20/Dec/1994 the patches are: s700 9.05 s800 9.04 --------------------------- ------------------------- PHNE_4879 (NFS mega patch) PHNE_4879 (NFS mega patch) PHKL_4937 (Kernel NFS patch) PHKL_3119 (Kernel NFS patch) PHNE_5010 (Xport mega-patch) PHNE_4838 (Xport mega-patch) (Thanks to Colin Wynd (colin@col.hp.com) and Allyn Fratkin (allyn@hp-sdd.sdd.hp.com)) ------------------------------ Subject: 7.47 Problem with ntalkd and it's handling on /etc/utmp. The current version of ntalkd (talkd is probably the same here), and it's handling of /etc/utmp is broken since it doesn't check the ut_type field. This causes it to send messages to logged out tty's rather than to those who are logged in on. The patch is easy luckily and also applies to most other unix's except really BSD4.2 ones and SunOS4. The patch is availalable on ftp.amtp.cam.ac.uk:/pub/HP/ntalk.tgz. (Thanks to Bill Hassell , Jon Peatfield ) ------------------------------ Subject: 7.48 How to get an MS-DOS floppy formatted using HP-UX? There is no HP-fully-supported way of getting an MS-DOS floppy formatted on HP-UX. (Once you have a PC-compatible floppy, the series of commands referenced in the dosif(4) manpage allow you to read and write the floppies). However, there is a workaround. Perform the basic mediainit with the -f16 switch (this causes the floppy to be formatted with the full 80 tracks, rather than HP's default safer-but-nonstandard 77+3spare tracks, 512-byte sectors, no sector skew: just like the most basic PC floppies). Then copy on the FAT, directory, label, and other such magic from an honest-to-goodness formatted-on-a-real-PC drive into the first N sectors. For sizes up to 1.44MB floppies, N=20 is more than enough; I don't have the values for the rarely used 2.88MB size (and I don't think the drives in the s700 handle that size anyway). This header magic should be copied off an honest-to-goodness PC floppy once with the command dd if=/dev/rfloppy of=/a/good/place/to/store/the/header bs=512 count=20 and then written back to each "cloned" floppy with the same command, reversing "if" and "of". (Slightly faster performance is possible using the variant: dd of=/dev/rfloppy if=/the/copied/header ibs=512 count=20 obs=9k conv=sync This causes floppy I/O to be done in multiples of 9kB, i.e. one cylinder at a time.) You should of course have two such headers, one for 720kB and one for 1.44MB floppies: lying to MS-DOS or the dos* utilities about the floppy capacity would be a bad idea. If you're writing a script to automate all this, you can determine the capacity of a floppy loaded in the drive using the following fragment of Korn shell: kbsize=$( diskinfo -b /dev/rfloppy 2>/dev/null ) if (( $? != 0 || $kbsize == 0 )) ; then print -u2 "$0: Wot, no media!?" rm -f core # 9.01s700 diskinfo coredumps exit 1 fi (Thanks to Stefek Zaba ) ------------------------------ Subject: 7.49 How to get the MAC (station) address programmatically? Here's some sample LLA code to do this. Note that you can use DLPI to do the same, and LLA in not supported in HP-UX 10.0. Sample DLPI code can be found on HPSL, the document id is CWA940907000. /* Here's some sample code that you can use to get your own station address (otherwise known as MAC address or LAN card address). Be sure to compile this with the -ln option, since the net_ntoa(3N) call is found in /usr/lib/libn.a. This program was compiled by doing: cc get.c -o get -g -ln */ #include #include #include main(argc, argv) int argc; char *argv[]; { struct fis s_fis; struct fis s_fis; int lanic; char *ascii[6]; if (argc < 2) { printf ("Usage: %s \n", argv[0]); exit (1); } lanic = open(argv[1], O_RDWR); if (lanic < 0) { perror("Error in opening %s", argv[1]); printf("Error = %d\n", lanic); exit(1); } else { s_fis.reqtype = LOCAL_ADDRESS; s_fis.vtype = INTEGERTYPE; ioctl(lanic, NETSTAT, &s_fis); net_ntoa(ascii, s_fis.value.s, 6); printf("Station address of %s is %s\n", argv[1], ascii); s_fis.reqtype = PERMANENT_ADDRESS; s_fis.vtype = INTEGERTYPE; ioctl(lanic, NETSTAT, &s_fis); net_ntoa(ascii, s_fis.value.s, 6); printf("Permanent Station address of %s is %s\n", argv[1], ascii); close(lanic); } } (Thanks to Colin Wynd ) ------------------------------ Subject: 7.50 Is there a Transport Level Interface (TLI) interface to TCP on HP-UX? In HP-UX 10.0 a special module has been created which provides XTI access over the BSD stack - TLI is not supported. TLI, for the most part after SVID 3 volume 5, has stopped evolving and is being replaced by XTI in most implementations. XTI is standardized by X/Open and the current versions from most vendors should be XPG4 compliant with some being branded as the branding test suites are made available by X/Open. Note the reason one needs a streams-based TCP is that both TLI and XTI rely upon a streams-based module, timod, to provide specific functionality within the kernel and this module needs to be pushed upon the transport stack. Since HP-UX uses a BSD transport which is not streams-based and is therefore incapable of having a streams-based module pushed upon it, one cannot run TLI/XTI directly upon it, and, hence, a special streams module was created to provide this functionality for HP-UX 10.0. (Thanks to Mike Krause ) ------------------------------ Subject: 7.51 How do you disable IP Forwarding? To accomplish what you want, use the following commands as root: adb -w /hp-ux /dev/kmem ipforwarding/W 0 ipforwarding?W 0 CTRL-D If you install a new kernel, you have to repeat these steps. NOTE: These commands disable IP forwarding completely: if the system is configured as a gateway, no IP forwarding will occur. This workaround is NOT supported. (Thanks to Colin Wynd (colin@col.hp.com) ------------------------------ Subject: 7.52 Does HPUX 9.0 have support for threads? As part of the DCE product, a user-space thread-package was shipped. This package is also part of 10.0. (Thanks to Mike Krause ) ------------------------------ Subject: 7.53 How come the filenames on CD-ROM are in uppercase? This is the ISO 9660 format stored on the CDROM. Filenames are in uppercase and have a version as well (ie ;1). If you would like lowercase names and no ;1 version, you'll have to translate the names. The usual hack is to create symbolic links. An alternative is to use a product called PFS from Young Minds, Inc. (Thanks to Bill Hassell ) ------------------------------ Subject: 7.54 How come I can't type an '@' character? If you do a 'stty -a' and you will see that your 'kill' character is set to '@'. You need to set your 'kill' character to be something other than the '@' character by doing something like 'stty kill '^U''. You should add this to your .profile or .cshrc file. (Thanks to Michael J. O'Connor ) ------------------------------ Subject: 7.55+ How come I can't get my machine into boot admin mode? When i reboot my workstation I do not get the "..push and hold the ESCAPE key to ..." - why? The machine is configured in secure boot mode. To get into boot admin mode you will need to remove all bootable media (i.e. disconnect disks, LAN, etc.) and then power on - the boot will fail and you can then get to boot admin and switch off secure boot mode. (Thanks to Julian Perry ) ------------------------------ Subject: 8. COMPILERS AND LINKERS ------------------------------ Subject: 8.1 What's a P-FIXUP error? Several questions in comp.sys.hp.hpux have involved the Gnu C compiler and the linker message below : gcc test_h.o -o test_h ../libg++.a -lm ld: R_DATA_ONE_SYMBOL fixup in file ../libg++.a(streambuf.o) for code unsat symbol "abort" - use P' fixup collect: /bin/ld returned 1 exit status This is caused by the code generator emitting assembly code in a data subspace to initialize a function pointer, equivalent to : .word foo where (in this case) foo() is an extern, and shared libraries are referenced by the executable being built (usually libc.sl). NOTE: This problem has been fixed in gcc-2.4.5.u5; if people are still running into this error, then: 1) They've got an old version of gas (pa-gas-1.36.u8 I belive is the first one do handle this correctly). 2) They're linking with a library built with some old combination of gcc and gas. The solution is to make sure gcc and gas are up-to-date and any libraries have been built with the latest gcc/gas combination. For a temporary workaround the option "-static" to gcc will suppress dynamic linking and thus avoids the error. (thanks to Carl Burch, HP for the original, and Jeff Law for the followup) ------------------------------ Subject: 8.2 Where is regcmp on HP-UX? RTFM - from man regcmp: regcmp and regex are kept in /lib/libPW.a, and are linked by using the -lc and -lPW options to the ld or cc command. See WARNINGS below. (thanks to Andre Srinivasan, ) ------------------------------ Subject: 8.3 How come the default C compiler is brain-dead? The C compiler shipped with HP-UX is intended only to rebuild the kernel with, not for program development. To get a "real" C compiler, you must buy the ANSI C program development bundle. ------------------------------ Subject: 8.4 How do I deal with "too many defines"? Use the "-Wp,-Hxxxxxxx" where xxxxxxxx is the number of bytes to add to cpp's table size. There is no equivalent in lint or cflow to the cc driver's -W flag to pass options to subprocesses like cpp. However, both lint and cflow invoke cpp via the cc driver, so you can achieve the same effect by setting the CCOPTS environment variable. For example, CCOPTS="-Wp,-H500000" export CCOPTS lint large_file.c ------------------------------ Subject: 8.5 How come I get "_builtin_va_start" undefined when I build with gcc? The and include files define va_start in terms of this function, which is built-in on the HP C compiler. If you're using GCC you should be picking up include files from the gcc library directory. These include files do the right thing for both GCC and HP C. More often than not these files were never installed, or someone has placed a copy of varargs.h/stdarg.h into /usr/local/include (gcc searches there *first*). When all else fails, you can replace the definition of va_start as follows, depending on whether you are using varargs or stdarg (K&R or ANSI, respectively). #include #ifdef __hppa #undef va_start #define va_start(a) ((a)=(char *)&va_alist+4) #endif #include #ifdef __hppa #undef va_start #define va_start(a,b) ((a)=(va_list)&(b)) #endif For , this replacement should always work. For , this replacement will work unless the last fixed parameter ("b" in the call to va_start) is a structure larger than 8 bytes. Large structures are passed by reference, with the callee responsible for copying the structure to a temporary area if it will be modified. In this case, "&b" will take the address of that temporary area instead of the position in the argument list, and va_next won't work. That's why HP uses a compiler built-in. (Thanks to Cary Coutant, HP for the original and Jeff Law for the followup) ------------------------------ Subject: 8.6 How can I tell if something was built debuggable? If the output of "/usr/contrib/bin/odump -spaces file.o" shows a space named $DEBUG$, then it was compiled with -g. (Thanks to Fran Litterio ) ------------------------------ Subject: 8.7 Is there some kind of problem with using FLT_MIN in ANSI mode? The C compiler dislikes this construct in ANSI mode: x = FLT_MIN; /* <---- warning here */ The problem is that the ANSI mode (_PROTOTYPES) version of FLT_MIN/FLT_MAX in end their constants with an F, which seems to upset the compiler. The workaround ? Temporarily undef _PROTOTYPES around the inclusion: #ifdef _PROTOTYPES #undef _PROTOTYPES #include #define _PROTOTYPES #else #include #endif (Thanks to Richard Lloyd of the Liverpool archive.) ------------------------------ Subject: 8.8 What's the deal with _INCLUDE_xxxx_SOURCE? The ANSI standard clearly states what identifiers it reserves, and says the rest are available to you, the programmer. Many "important things" like "ulong" are *not* specified by ANSI, so ANSI header files are not allowed by the standard to define them. Each standard supported by HP-UX (POSIX1, POSIX2, XPG2, XPG3, XPG4, AES, etc) has its own set of reserved identifiers and header files, and the convention is to require "-D_POSIX_SOURCE" (et al) to enabled their respective namespaces. Since HP could not predict what future standards would come along and claim more header files and identifiers, it proved much simpler to make the namespace as restrictive as possible unless "-D_HPUX_SOURCE" is specified. While this has turned into one the most frequently asked of FAQ's about HP-UX, at least once you learn this, you don't have to deal with inconsistencies again. Whereas, had we allowed all non-standard headers to define all non-standard symbols, you'd find identifiers randomly "disappearing" from headers over time as they were claimed by various standards. Also check the man page for "cc -Ae"; it enables the the HPUX_SOURCE namespace. (Thanks to Marc Sabatella, HP) ------------------------------ Subject: 8.9 How come I need to explicitly specify -I/usr/include? You have most likely not updated your C compiler correctly. Patches PHSS_3773 (A.09.63), 4061 (A.09.64) and 4151 (A.09.65) REQUIRE that you first install the C compiler from the April 1994 Application CD-ROM (A.09.61). (Thanks to Richard Lloyd) ------------------------------ Subject: 8.10 Is there an equivalent for getrusage()? From the BSD porting tricks document (thanks, Mike): #ifdef hpux #include #define getrusage(a, b) syscall(SYS_GETRUSAGE, a, b) #endif /* hpux */ ------------------------------ Subject: 8.11 Why is syslog() call not doing what i want it to? My program looks like: #include void main(int argc,char *argv[]) { syslog(LOG_EMERG,"This is an emergency message\n")); syslog(LOG_ALERT,"This is an alert message\n"); syslog(LOG_CRIT,"This is a critical message\n"); syslog(LOG_ERR,"This is an error message\n"); syslog(LOG_WARNING,"This is a warning\n"); syslog(LOG_NOTICE,"This is a notice\n"); syslog(LOG_INFO,"This is an informal message\n"); syslog(LOG_DEBUG,"This is a debug message\n"); } It does log all the messages to /usr/adm/syslog - why not? First of all, the LOG_EMERG cannot be used with user processes and should return -1 (if you check the return status). This is not documented in the man page! All the other message should appear, but you're /etc/syslog.conf file might not be configured correctly. To test it replace the /etc/syslog.conf with the following line: *.debug /usr/adm/syslog Then do: kill -HUP `cat /etc/syslog.pid` Then run the test program and then tail the /usr/adm/syslog file and you should see all the messages, ie: Nov 23 09:02:54 orca syslogd: restart Nov 23 09:02:58 orca syslog: This is an alert message Nov 23 09:02:58 orca syslog: This is a critical message Nov 23 09:02:58 orca syslog: This is an error message Nov 23 09:02:58 orca syslog: This is a warning Nov 23 09:02:58 orca syslog: This is a notice Nov 23 09:02:58 orca syslog: This is an informal message Nov 23 09:02:58 orca syslog: This is a debug message (Thanks to Colin Wynd) ------------------------------ Subject: 8.12! Is trace on HP-UX? Trace is available from Interworks ftp site (iworks.ecn.uiowa.edu). For those of you unfamiliar with trace, here's the README: trace prints out system call (and optionally kernel) traces of programs. It compiles and installs fairly easily. It should work fine on 700s running HP-UX 9.X, and probably not at all otherwise. To run the header file generation scripts, you'll need Perl 4.0pl36 or better, installed as /usr/local/bin/perl. If you have problems with "too much defining", uncomment HFLAGS in the Makefile. Older 9.X C compilers had broken a cpp utility. If you encounter undefined ioctls, just comment them out and send me mail about them and what version of HP-UX you're running. fixheader will make sure that nonexistent header files aren't included. trace needs to be installed setuid root so that users can run it. The KI code, provided in object format, is copyright Hewlett-Packard. The software is provided as is, subject to change without notice, and totally unsupported. (Thanks to Kartik Subbarao, HP) ------------------------------ Subject: 8.13+ How to get C programs automatically generate stack dumps? Here is how you get a C program automatically generate a stack dump when they abend: U_STACK_TRACE() is an undocumented function that resides in libcl.a. Set up the signal handling like this: #include extern void U_STACK_TRACE(); signal(SIGSEGV, U_STACK_TRACE); (Thanks to ) ------------------------------ Subject: 9. HARDWARE AND PERIPHERALS ------------------------------ Subject: 9.1 Are alternate keyboards available for HP workstations? Yes, HP has two keyboards available for their workstations and X Terminals. A1099B - Workstation style keyboard (Default on workstations.) A2205A - PC-101 style keyboard (Default on X Terminals.) The 712 supports any PC-type keyboard and mouse. ------------------------------ Subject: 9.2 How can I play audio CDs on an HP workstation? A contributed application ("xcd") exists that presents a X-window CD player front panel. xcd runs on HP-UX 7.0 and 8.0, on Series 300, 400 and 700, with either SCSI or HP-IB CD-ROM drives. The SCSI drives must be HP-supplied or Toshiba XM-3201B or XM-3301B. xcd does not yet officially work on HP-UX 9.0, but I've tried it and it seems to work just fine. Note that xcd plays only through the CD player's headphone jack and not through the workstation's speaker. xcd is available from the InterWorks workstation user group (see above), on their ftp site, CD-ROM, and via DDS tape. Note that source is not available. Additionally, two new programs that provide similar functionality have recently appeared, called xdp and xmcd. I use xmcd and it's great. (Thanks to Bob Niland and others) ------------------------------ Subject: 9.3 How can I enable the LAN interface on a 700? This can be problem when the LAN isn't connected at boot time. To resolve the problem, use the "reset" command in "landiag". ------------------------------ Subject: 9.4 How can I get an Exabyte to work on an HP? People have under HP-UX 8.07 used device files with major number 54, minor numbers 0x201202 and 0x201203 for /dev/rmt/2m and /dev/rmt/2mn, respectively, for low density. Other people had used 0x201242 and 0x201243. Note that with HP-UX 9.01, low density means 8200 format in 8500 drives. Major #54, minor numbers 0x201202 and 0x201203 are low density handles. With 8200 drives the density does not matter. Software compression control with 8505 drives will require a patch to HP-UX 9.01. Caveats: some Exabyte drives will not support a "dump" blocking factor greater than 64 from the HP. Others are apparently limited in the commands they will accept (e.g. TTI noted that their 8501 tape drive will not properly interface with the HP under all conditions; however, the TTI 8510 does interface correctly). TTI had a firmware problem which should be corrected in recent 8510s. Note that 8500 drives act as SCSI-2, while 8200s are SCSI-1. People appear to have been more successful with getting the 8500s to work with 9.01. Experience has also shown that you may need PHKL_2898. People have also reported that you need patch PHKL_2838 for HP_UX 9.x to get compression to work. (Thanks to Mike Peterson for much of this.) ------------------------------ Subject: 9.5 Is there a "node ID" on 700s? Yes. Most licensing systems (FlexLM and NetLS, for example), are driven from the LLA, available from /etc/lanscan or /usr/etc/netls/ls_targetid. There is also a CPU ID number that HP uses for /etc/update; it may be a transformation of the LLA, but this is not guaranteed to remain the case, and may be disturbed by replacement of the LAN board. Additionally, the LLA can be reset by a CE using the proper secret magic program. ------------------------------ Subject: 9.6 How can I get a stuck DDS tape out of the drive? 1) Power down your machine (remember shutdown!!! ;-)) 2) Open it up (you'll prob. need Torx screwdrivers). 3) on the side of the drive, you should see a small rectangular piece of plastic. gently pry it off... it should come off quite easily. 4) the aforementioned piece of plastic covers a hole, which houses a small dial. spinning this dial ejects the tape. 5) replace plastic piece, close machine... and bob's your uncle. p.s. the dial has very little torque (ie. the tape comes out quite slowly, but you can see it move. It'll take about 2-3 minutes of spinning before the tape comes out. (Thanks to Edlin Seebick.) ------------------------------ Subject: 9.7 How can I use dump with a DDS tape? dump was written to assume 9-track tapes, so some fudging has to be done for DDS tapes. The following has the info you need along with several alternatives for dump parameters. Approximate capacity of 60m DDS tape = 1.3G bytes Approximate DDS tape density = (1.3G bytes) / (60 m) = (550K bytes/in) dump assumes an inter-record gap (IRG) of 0.3 in for density = 6250, 0.7 in otherwise. dump uses a default blocking factor of 10 for density < 6250, 32 otherwise. ================ density = 550000 blocking factor = 32 (default) assumed IRG = 0.7 in Block length = (32K bytes/block) / (550K bytes/in) + (0.7 in) = (0.76 in) Effective tape length = (1.3G bytes) / (32K bytes/block) * (0.76 in/block) = (2511 ft) ================ density = 6250 blocking factor = 32 (default) assumed IRG = 0.3 in Block length = (32K bytes/block) / (6250 bytes/in) + (0.3 in) = (5.54 in) Effective tape length = (1.3G bytes) / (32K bytes/block) * (5.54 in/block) = (18325 ft) =============== density = 1600 blocking factor = 10 (default) assumed IRG = 0.7 in Block length = (10K bytes/block) / (1600 bytes/in) + (0.7 in) = (7.10 in) Effective tape length = (1.3G bytes) / (10K bytes/block) * (7.10 in/block) = (75113 ft) =============== density = 1600 blocking factor = 32 assumed IRG = 0.7 in Block length = (32K bytes/block) / (1600 bytes/in) + (0.7 in) = (21.18 in) Effective tape length = (1.3G bytes) / (32K bytes/block) * (21.18 in/block) = (70022 ft) (Thanks to Cary Coutant, HP.) ------------------------------ Subject: 9.8 What is the correct major number for DDS drives on 9.x? For reasons too detailed to go into here, the major number for DDS drives has changed to 121 (from 54) at 9.01. Note that 54 had partition support, while 121 does not, but has lun support. This only works for 700s. ------------------------------ Subject: 9.9 How can I set up /dev/audio to point to the external jack on a 700? Alter the /dev/audio device file as follows: crw-rw-rw- 1 root sys 57 0x208011 /dev/audio ; external jack crw-rw-rw- 1 root sys 57 0x208000 /dev/audio ; internal speaker The commands are: mknod /dev/audio c 57 0x2080?? <- replace ?? with 00 or 11 as shown above. (Thanks to Lou Kvitek.) ------------------------------ Subject: 9.10 How can I configure the parallel port handshake on a 700? Check out the man page for "cent". ------------------------------ Subject: 9.11 What are the specs of the audio hardware on the 700 series? This is a summary of the audio features supported by the models 715, 725, 735, and 755 workstations. The 705 and 710 also have audio, but the specs are not available. The 720, 730, and 750 models DO NOT have audio. Audio features Programmable sample rates (kHz): 8, 11.025, 16, 22.05,32, 44.1, 48 Programmable output attenuation: 0 to -96 dB in 1.5 dB steps Programmable input gain: 0 to 22.5 dB in 1.5 dB steps Input monitoring Coding formats: 16-bit linear, 8-bit mulaw, or A-law Audio inputs Line in (not on all models) Mono microphone with 1.5V phantom power (Editorial comment - a Sun microphone appears to work just fine.) Audio outputs Line out (not on all models) Headphone Mono speaker jacks Built-in mono speaker Audio CODEC Crystal CS4215 Typical specifications measured on a stock 715. Values will differ only slightly on other models. Frequency response 25 - 20,000 Hz Input Sensitivity/Impedance Line In 2.0 V(pk) / 47 kohms Microphone 22 mV(pk) / 1 kohm Output Impedance (nominal) Line out 619 ohms Headphone 118 ohms Speaker (ext) 11 ohms Max Output Level/Impedance Line Out 2.8 V (p-p) / 47 kohms Headphone 2.75 V (p-p) / 50 ohms Speaker (ext) 5.88 V (p-p) / 48 ohms Signal to Noise Line In 61 dB Line Out 65 dB Microphone 57 dB Headphone 61 dB Speaker (ext) 63 dB THD (at nominal load) Line In -75 dB Line Out -73 dB Microphone -73 dB Headphone -70 dB Speaker (ext) -68 dB (Thanks to Rocky Craig, HP) ------------------------------ Subject: 9.12 What are the various revisions of PA-RISC? PA-RISC 1.1 is an extension to the PA-RISC 1.0 architecture, and is fully backwards-compatible (i.e., *all* PA-RISC 1.0 programs will execute without change on PA-RISC 1.1 machines). The biggest difference is that PA-RISC 1.1 added 16 more floating-point registers, the ability to address each double-precision floating-point register as two single-precision registers, and a few new floating-point operations, so the floating-point performance is greatly improved. There were a few changes on the integer side, but nothing major. The first machines to be shipped with PA-RISC 1.1 CPUs were the first Series 700 machines (the "Snakes" series). Shortly after that, however, the "Nova" series of Series 800 (8x7) machines was introduced using the same PA-RISC 1.1 CPU. Since then, every new PA-RISC machine that HP has produced is based on the PA-RISC 1.1 architecture. Thus, all Series 700 machines are PA-RISC 1.1, and the newer Series 800 machines are PA-RISC 1.1. If you compile a program on a Series 700 machine, the compiler will generate PA-RISC 1.1 code by default, but if you compile a program on a Series 800 machine (even a newer 1.1 machine), the compiler will generate PA-RISC 1.0 code to ensure that the program will run within the entire 800 family. To force the compiler to generate PA-RISC 1.0 code, you use the +DA 1.0 compiler option. This is all you need to do, as long as you are careful not to link your code with any libraries that were compiled for PA-RISC 1.1. If *any* object module in your program is compiled for PA-RISC 1.1, your entire program will be marked as a PA-RISC 1.1 program. The "file" command will tell you which architecture is required to execute your program. Most system archive libraries that HP ships are compiled for PA-RISC 1.0; an exception is the math library, which is shipped in both forms (a PA-RISC 1.1 version is in /lib/pa1.1), although the 1.1 version contains a few entry points that are not available in the 1.0 version. The scheduling option, +DS xxx, does not affect the compatibility of the object code. It affects only how the optimizer schedules instructions that have long latencies, so it is usually to your advantage to schedule the code for the fastest machine currently shipping, even if you are generating 1.0 code. When compiling code on one platform for another platform, the thing you do have to worry about is the operating system release. In general you can compile a program on a Series 700 machine with +DA 1.0, and it will run correctly as long as the program will execute on the same or a later release of the OS as the one on which it was compiled. Thus, you cannot expect a program compiled on a 700 running 9.0 to run on an 800 running 8.0. (Thanks to Cary Coutant, HP) ------------------------------ Subject: 9.13 How do I read an SGI-written tar format DDS tape? The secret (at least in this case) is to byte-swap the tape before passing it to tar: dd if=/dev/rmt/0m conv=swab | tar -xvf - Byte swapping is believed to only be necessary if the device which created the tape was a swapping one. (Swapping tape devices are the default on IRIX 4, but not in IRIX 5). One can use /dev/nrtapens on either system to produce tapes which are not byte-swapped. If the SGI is running Irix 5.0x and above, a large (512k) block size is used: dd if=/dev/rmt/0m ibs=512k obs=10k| tar -xvf - (thanks to Paul Booth and Christian L Claiborn ) ------------------------------ Subject: 9.14 Is there a trackball for the 700? From the 'hp-ux/resource directory' published by Interex: "BKS manufactures and markets THE ORIGINAL HP M1309A HP-HIL Trackball. Plug-compatible with HP's standard 3-button HP-HIL mouse. BKS acquired manufacturing and marketing rights to this product from Hewlett-Packard in June 1993. Another 'no-problem' product from BKS--the specialists in hardware accessories for HP systems" BKS Electronique 20 Rue A. Berges/Z.1.DES 1LES Le Pont De Claix, France 38800 +33 76 98 30 99, FAX: +33 76 98 57 79 From the September 1994 issue of 'hp-ux/usr' magazine also published by Interex: "HP Serial MOUSE-TRAK now Available For 700 Series. No Quad Port Adapter Required. Call for information" ITAC Systems, Inc. 3113 Benton Street Garland, TX 75042 (800) 533-4822 FAX: (214)494-4159 yvonne@mousetrak.com (too many international distributors to type in) U.K., Norway, Germany, Switzerland, Denmark, Australia, Sweden, Seoul Korea, France, Israel ------------------------------ Subject: 9.15 Where can I get disktab entries for third party disks? Generally, the supplier should provide a disktab entry. Andataco does a good job of this. One place to try: http://hpwww.epfl.ch/HPUX/tools/disktab.html Additionally, Ion has set up a mail service; to access it, send e-mail to and respect the following syntax for the subject field: disktab table - returns the available disktab file disktab how - returns two methods to create a new disktab entry from scratch Send any comments, remarks, problems AND new tested disktab entries to Patch PHSS_4981 has the disktab entries for the following drives: Seagate ST32430WD, Seagate ST32430N, Seagate ST31230WD, Seagate ST31230N, HPC3324A, HPC3324W, HPC3325A, HPC3325W Seagate ST31200N, Seagate ST31200W, Seagate ST12400N, Seagate ST12400W, DEC DSP3107LS, DEC DSP3107LSW, DEC DSP3210S, DEC DSP3210SW, Quantum LPS1080S, Quantum LPS1080WD (thanks to Ion Cionca, and Colin Wynd ) ------------------------------ Subject: 9.16 Do I need to terminate the internal SCSI on a 700? According to some people, an unterminated internal SCSI on a 700 will cause interrupts which are ignored but slow down the machine. Terminate to be safe. ------------------------------ Subject: 9.17 What is the largest disk partition I can have? On a 700, you can get 2Gbytes, unless you have the SCSI patches that allow 3.7Gbytes. You can safely put any size disk on the system you want, but the OS will only allow you to access 2G (or 3.7G). At this time (13/Feb/1995) the patch is PHKL_3325. (thanks to Mike Lampi, MDL , and Seth LaForge ) ------------------------------ Subject: 9.18 How can I determine how much RAM I have non-interactively? Here is a short program that returns the RAM size: #include main() { struct pst_static buf; pstat(PSTAT_STATIC, &buf, sizeof(buf), 0, 0); printf("Physical RAM = %ldMB\n", buf.physical_memory/256); } If you are root, you can use adb as follows: echo "physmem/D" | adb /hp-ux /dev/kmem | tail -1 | \ awk '$2 > 0 { print $2 / 256 }' Or if /etc/dmesg is still current, you can grep it: /etc/dmesg | grep "real mem" | tail -1 | awk '$4 > 0 { print $4 / 1048576 }' (thanks to Richard Lloyd and Mike Frison ) ------------------------------ Subject: 9.19 How can I turn off the lpspooler cover page? 1) For one job/user only: Alias your "lp" command to "lp -onb" 2) For all the print jobs: Depending on the type of spooler script do either: a) Edit your /usr/spool/lp/interface/"printer name" file and comment out the banner page. Note that if you are using the JetAdmin tool the real script will be:- /usr/spool/lp/interface/model.orig/"printer name" b) The newer interface files (in /usr/spool/lp/interface/*) call /usr/lib/rlp and if your model script has that then insert the following line before the /usr/lib/rlp statement: BSDh="-h" The model script would now look something like:- ... shift; shift; shift; shift; shift #Added the no banner option here BSDh="-h" /usr/lib/rlp -I$requestid $BSDC $BSDJ $BSDT $BSDi $BSD1 $BSD2 ... ... (thanks to Dan Silva , and Daniel Wexler ) ------------------------------ Subject: 9.20 Does HP support the RockRidge extensions for CDROM names? No. That's why the filenames are all uppercase with the semicolon. ------------------------------ Subject: 10. LOOKING FOR... ------------------------------ Subject: 10.1 Where did xline go at 9.x? We don't know. The 9.x Motif version of Glance Plus has what xline had (and more). ------------------------------ Subject: 10.2 How about the VUE 2.01 man page help index? The man pages will show up in the index if you copy over pre-9.X copies of the files "/usr/lib/X11/vue/help/C/manpage.cat", and "/usr/lib/X11/vue/help/C/manpage/*". (Thanks, Mike Stroyan, HP) ------------------------------ Subject: 10.3 Is there anything remotely like the Apollo DM available? HP has a product called DMX which is somewhat like the DM. Enabling Technologies has a product called "ce" which seems to be a more faithful interpretation. Demo copies are available from ftp://ftp.std.com/ftp/vendors/ETG. ------------------------------ Subject: 10.4 Where can I get SLIP for HP-UX? On HP 9000 systems (both workstations and servers) SLIP is called ppl and is a part of the LAN/9000 Link product. (Thanks to Mike Taylor and Alec Henderson, HP) ------------------------------ Subject: 10.5 Where can I get pcnfsd on HP-UX? It's part of the standard NFS distribution. ------------------------------ Subject: 10.6 Where can I get ppp for HP-UX? Morningstar has a commercial implementation available. See ftp://ftp.morningstar.com for more details. (thanks to Cricket Liu, ) ------------------------------ Subject: 10.7 Where can I get STREAMS for HP-UX? STREAMS/UX is currently a separate product that can be purchased for use with HP-UX 9.x. STREAMS/UX is based on the OSF/1 STREAMS code (which in turn is based on STREAMS code from Mentat). You can obtain a STREAMS/UX datasheet from the HP FIRST fax-back service: 800-333-1917 or 208-344-4809, document 31502. HP currently plans to bundle it with 10.x. (thanks to Alec Henderson, HP) ------------------------------ Subject: 10.8 What about POSIX threads? POSIX user-space threads are currently available as part of the DCE product, which includes thread-safe C libraries. ------------------------------ Subject: 10.9 Where can I get Interviews for HP-UX? HP has a product called Interviews Plus. The product number is B2625A for Series 800 and B2626A for Series 700 systems. (Thanks to Rob Slotemaker, HP). ------------------------------ Subject: 10.10 Where can I get POP for HP-UX? pop3d is available from the Interworks archive site listed in 3.12. ------------------------------ Subject: 10.11 Where can I get sudo for HP-UX? CU sudo 1.3 and higher supports hpux. See section 3.13 for FTP sites. (Thanks to Todd Miller, ) ------------------------------ Subject: 10.12 Where can I get ntalk for HP-UX? See section 3.13 for an FTP site. ------------------------------ Subject: 10.13 Where can i get disktab entries for certain seagate drives? Patch PHSS_4981 has the disktab entries for the following drives: Seagate ST32430WD, Seagate ST32430N, Seagate ST31230WD, Seagate ST31230N, HPC3324A, HPC3324W, HPC3325A, HPC3325W Seagate ST31200N, Seagate ST31200W, Seagate ST12400N, Seagate ST12400W, DEC DSP3107LS, DEC DSP3107LSW, DEC DSP3210S, DEC DSP3210SW, Quantum LPS1080S, Quantum LPS1080WD ------------------------------ Subject: 11. HP-UX 10.0 INFORMATION ------------------------------ Subject: 11.0 When will HP-UX 10.0 be released? An announcement will be made on Feb 6th 1995. ------------------------------ Subject: 11.1 What functionality is in HP-UX 10.0 Here's the offical statement regarding 10.0 from HP: Introducing the HP-UX 10.0 New Business Release "HP suggests that you read the information provided in this document prior to making a decision on requesting the HP-UX 10.0 New Business Release." I. Introduction/Management Summary Dear Valued HP 9000 Customer: Hewlett-Packard is proud to announce HP-UX 10.0. HP-UX 10.0 is an Enterprise-Class Operating Environment that provides dramatically improved high-end performance scalability combined with the increased functionality for high availability, system management, security, and networking crucial to anticipate the growing demands of your Information Technology (IT) environment as you implement open enterprise computing. These enhancements are provided while maintaining our commitment to investment protection through binary compatibility for your applications-a commitment which has been maintained for the last eight years. Building on HP's strength in open systems solutions, HP-UX 10.0 provides: * Scalability with industry-dominating performance * Continued standards leadership together with a "SPEC1170 protected" environment * Enterprise systems management and security leadership * Broad, cost-effective high-availability solutions * Networking enhancements (for Internet connectivity among others) * Unrivaled investment protection In an effort to provide the introduction of the new HP-UX 10.0-based release in a smooth and organized manner, HP is offering a two-phased approach to ensure the appropriate attention and support are in place from HP and HP Channel Partners to best serve the interests of our customers. The first phase, the HP-UX 10.0 New Business Release, is a production quality release and is available now only on specific request. However, the second phase, the HP-UX 10.0 General Business Release, will be automatically shipped to you and is scheduled for mid-1995. The HP-UX 10.0 New Business Release is primarily designed to support projects requiring the purchase of new HP 9000 hardware systems. The New Business Release is also offered for dedicated development/test systems that can be used to evaluate HP-UX 10.0 prior to a later upgrade to the HP-UX 10.0 General Business Release of production-based HP-UX 9.0 systems within your environment. This release will support all currently orderable HP 9000 Server and Workstation systems, including the HP 9000 E/F/G/H/I/8x7/890/T500 Server models and the 712/715/725/735/742/743/745/747/748/755 Workstation models. New multi-processor Workstation and Server models will also be supported on the New Business Release as they become available. Other systems-not covered in the preceding lists-that you may have installed, will be supported on the subsequent HP-UX 10.0 General Business Release. For your reference, Series 800 systems are identified as HP 9000 Servers and Series 700 systems are identified as HP 9000 Workstations. HP-UX 10.0 General Business Release The HP-UX 10.0 General Business Release will be shipped automatically, for all systems that have current software support contracts, through the usual operating system update delivery process. The concept of the General Business Release has been introduced so that HP can offer its existing customers, running production HP-UX 9.0-based environments, the most complete solution possible-including applications-when HP-UX 10.0 is presented to you. HP has worked with many strategic application partners to ensure that they rapidly complete recertification on HP-UX 10.0. For example, leading database vendors such as Oracle, Sybase, and Informix expect to have products available on HP-UX 10.0 coincident with the New Business Release. By the HP-UX 10.0 General Business Release, HP's goal is for all key software application products (both HP and HP Channel Partner) to have completed recertification on HP-UX 10.0. At the General Business Release additional HP 9000 Workstation and Server models will be supported, a set of automated update tools made available and some utilities offered to ensure the smooth coexistence of HP-UX 9.0 and 10.0-based systems in the same environment. With the availability of this complete solution at the General Business Release, customers with existing HP-UX 9.0 production environments will be able to take advantage of the full functionality and benefits of HP-UX 10.0 at a pace that your own individual business needs dictate. HP-UX 10.0 represents a dramatic increase in value to our customers. As a fully Enterprise-Class Operating Environment, HP-UX 10.0 offers you the flexibility to scale across all your key business-critical requirements from engineering desktop to data center. HP-UX 10.0 is the firm foundation for providing you with a clear path to the 21st century for your open enterprise computing needs. We look forward to moving into the future with you. Sincerely, Mark Canepa Carol Mills Mark Solle General Manager General Manager General Manager Workstation Systems General Systems Software Services and Division Division Technology Division II. HP-UX 10.0 Overview The value of HP-UX 10.0 has been substantially enhanced with the inclusion of licenses for the DCE/9000 Executive, Streams/9000 and XTI/9000 over TCP/IP in addition to the existing licenses for ARPA/9000, TCP/IP, LAN/9000, NFS, NCS, NetLS, X.11, Motif and HP Visual User Environment (VUE). Many of these other products have also been substantially enhanced in this release. Scalability with industry-dominating performance - Symmetric Multi-Processor (SMP) scalability improvements - First release enabled for SMP Workstations - Compiler optimizations - Logical Volume Manager (LVM) software disk striping - Memory Mapped files for HP 9000 Servers - Dynamic Buffer Cache for HP 9000 Servers - SMP scaling for NFS * From the empowered engineering desktop to the enterprise business-critical server in the data center, HP-UX 10.0 now offers a single architectural solution scalable for OLTP, client/server and distributed computing environments beyond any other offering in the industry. Enhancements, which result in optimized Symmetric Multi-Processor (SMP) scaling and Input/Output (I/O) throughput, provide dramatic improvements in high-end performance and scalability on the HP 9000 Model T500 Server. HP-UX 10.0 will also be the first release that will support SMP-based HP 9000 Workstations. Additional compiler optimizations are available which can enhance performance by 10 to 20 percent. Memory Mapped files and Dynamic Buffer Cache become available on HP 9000 Servers for the first time, offering further optional I/O performance improvements. Improved tuning of NFS provides significant performance improvements for file servers on SMP-based systems. * HP believes that the OSF's Distributed Computing Environment (DCE) offers a strategic set of integrated services that allows distributed client/server applications to scale enterprise-wide. HP wants to ensure every HP 9000 platform can easily participate in these next generation enterprise-wide client/server applications and is therefore bundling the DCE Executive with HP-UX 10.0. The Executive contains core DCE services such as the Remote Procedure Call (RPC), POSIX 1003.1c threads, timing, and client services for the Cell Directory Service, Security Service, and Distributed File Service. Continued standards leadership together with a "SPEC1170 protected" environment - Smooth progression to SPEC1170 compliance - "Proprietary" UNIX features removed - New 4-byte Extended UNIX Code (EUC) support - Real-time API interface support - A "SPEC1170 protected" environment * HP-UX 10.0 builds on our early leadership compliance with XPG4 to add the majority of other API interface standards, defined in SPEC1170, that will allow HP-UX to become compliant with the future X/Open XPG4.2 standard. These include: - SVID 3 Level 1 APIs (which define the System V Release 4 [SVR4] implementation); - OSF AES compliance for the HP 9000 Servers (already available for HP 9000 Workstations on HP-UX 9.0); and - Networking APIs defined by SPEC1170. A second thrust of HP-UX 10.0 is to eliminate "proprietary" UNIX features from HP-UX and replace them with industry-standard functionality. Included here is: - a move to the SVR4 File System Directory Layout structure (easing multivendor system administration in heterogeneous environments since this layout is becoming a UNIX standard); - the replacement of HP's Distributed Update and Install (DUI) utility with Software Distributor-UX (a subset of the HP OpenView Software Distributor product and the submission to the POSIX 1387.2 standard for software management); and - the introduction of the multivendor, industry-standard NFS Diskless solution to replace HP Diskless (DUX). NFS Diskless availability is planned for the HP-UX 10.0 General Business Release in mid-1995. Finally, HP-UX 10.0 will offer an upgrade to NFS version 4.2 functionality, provide API interfaces defined in the POSIX 1003.1b real-time standard and offer 4-byte Extended UNIX Code (EUC) support for Asian language localization. * HP-UX 10.0 provides the basis for investment protection when upgrading to a future SPEC1170-compliant version of HP-UX. For the three APIs in HP-UX which may change format or function in a future SPEC1170-compliant version of HP-UX, HP has implemented a set of "parallel" APIs that act as a compatibility library for HP-UX 10.0. If in your particular environment, you do not envision wanting to make the changes required for SPEC1170 compliance when a fully SPEC1170 HP-UX becomes available, then during the life of HP-UX 10.0, your developers can make a simple edit and recompile to use these "parallel" APIs. These "parallel" APIs will not change form or function in a fully SPEC1170-compliant version of HP-UX, so there is a firm grounding for future investment protection through "SPEC1170 protection". Enterprise Systems Management and Security Leadership - SAM Administrator "Roles" - SAM ease-of-use enhancements - Security enhanced - HP PRM/9000 data center performance management - Software Distributor-UX - SVR4 File System Directory Layout - HP 9000 Server and Workstation HP-UX convergence * System Administration Manager (SAM) at HP-UX 10.0 will allow a lead system administrator to define a subset of administrative tasks that a non-root-user can perform. Using SAM "Roles", the lead administrator can assign tasks such as a system backup to a second administrator without the corresponding requirement to assign superuser capabilities to that administrator. This both reduces security exposure and allows customers to map administrative tasks to the structure and specialization of their own IT organizations. In addition, SAM now requires even less interaction from administrators performing certain tasks such as disk configuration. Finally, SAM can be customized to allow other tools and utilities to be launched through its interface and SAM logging can be displayed within a window as tasks are performed. * HP-UX 10.0 includes security enhancements from the U.S. Department of Defense B1 security specification in the areas of improved password management and log-in restrictions. There is a new password generation utility, a utility to screen user-generated passwords and a password aging function. Log-in restrictions can prevent access to an HP 9000 platform outside of specified hours, can limit the physical terminals from which log-ins will be accepted, and enforce rigorous authentication on system boot-up. These functions are optionally configurable through SAM. * HP Process Resource Manager/9000 is a new scheduler available on HP-UX 10.0 that allows you to dynamically set CPU allocations according to business priorities. Groups of users can be allocated a minimum percentage of available CPU cycles based on their mission priority. This "data center" class functionality facilitates the provision of service level agreements and offers a fair mechanism of allocating costs for any system serving different sets of application users. Furthermore, HP PRM is integrated through the GlancePlus GUI, allowing dynamic performance monitoring and management at the same time. * Software Distributor-UX (SD-UX) is now bundled with HP-UX 10.0 for software and operating system packaging, installation, distribution, and management. SD-UX provides significant software selection enhancements, which greatly improve software usability and delivery. In addition to installing software, SD-UX can be used to pull software from a central "depot" onto a remote system. All HP-UX operating system and software products will be installed using SD-UX as a replacement to DUI. * The SVR4 File System Directory Layout introduced at HP-UX 10.0 allows clear separation and grouping of files by functionality, defined by a common policy. This minimizes the potential for unintended overwriting of files, provides the solid foundation for diskless and client/server file sharing models, and simplifies multivendor administration. * HP-UX 10.0 also improves the efficiency of building and managing client/server applications and architectures by providing the same kernel, commands, libraries (common API and ABI) and system administration utilities across the full HP 9000 product line (Workstations and Servers). Broad, cost-effective high availability solutions - HP MC/ServiceGuard enterprise cluster - New HA Disk Arrays - HP-UX Memory Page Deallocation - Availability Management Service - Business Continuity Support - Logical Volume Manager (LVM) enhancements - A Journaled File System for HP-UX * With HP-UX 10.0, HP introduces a broad set of cost-effective solutions for high availability such as HP MC/ServiceGuard (Multi-Computer), an enterprise clustering solution which offers significantly faster basic system recovery time and greater flexibility than HP SwitchOver/UX, new High Availability Disk Arrays and HP-UX Memory Page Deallocation which helps minimize the likelihood of system failures due to memory errors. These product enhancements are supported by two new Mission-Critical support services: the Availability Management Service where HP provides recommendations on product and service requirements, and HP Business Continuity Support, which offers the highest levels of tailored support infrastructure focused on mission-critical environments. * The HP-UX Logical Volume Manager (LVM) on HP-UX 10.0 is enhanced to allow for the back-up of an off-line mirror from another system - eliminating planned downtime. LVM now supports both Fast and Wide SCSI and HP-FL disk arrays. Finally, LVM now supports dual I/O paths between disks and the system with automatic failover to the second I/O path. * The HP-UX 10.0 General Business Release will also include a Journaled File System (JFS) to accelerate the speed of recovery should a system failure occur. This file system performs an integrity check in seconds which can be favorably compared to the file system check 'fsck' offered with the standard UNIX file system. HP OnLineJFS will also be offered on the HP-UX 10.0 General Business Release. It allows manipulation of a Journaled File System without taking it off-line, eliminating the need for planned downtime. JFS expansion, backup, and disk defragmentation can all be achieved on-line using HP OnLineJFS. Networking Enhancements - ARPA Internet enhancements - TCP/IP enhancements - NFS Version 4.2 functionality - SNAplus enhancements - New TN3270 client product - Netware for UNIX enhancements * Networking the heterogeneous enterprise is easier with the HP-UX 10.0 operating environment as continued enhancements to ARPA (e.g.: Internet services such as GateD/OSPF, Bind 4.9.2, XNTP, MIME, and ESMTP), TCP/IP (e.g.: Dynamic Host Control Protocol for self-configuration, compression over serial links with C-SLIP and IP-Multicast support), SNA (e.g.: TN3270 support, CPI-C 1.2 API support, Winsock for PC clients, and SNA over 802.3), Netware for UNIX (dramatic performance enhancements), and NFS scaling on SMP systems are included in the portfolio of connectivity solutions. In addition, STREAMS and XTI for TCP/IP APIs are now bundled with HP-UX 10.0. Unrivaled Investment Protection - Binary Compatibility - Fast Transition Links - Coexistence utilities * HP continues to provide unrivaled investment protection by ensuring that HP-UX 10.0 provides binary compatibility from HP-UX 9.0 to the HP-UX 10.0 version of the operating system. A facility called Fast Transition Links, which is transparent to applications, makefiles and scripts, has been provided within HP-UX to provide compatibility for the move to the SVR4 File System Directory Layout. These Fast Transition Links incur negligible impact on overall system performance. At any time during the life of HP-UX 10.0, customers can then use part of the Analysis and Conversion tool functionality (described in the following section) to modify their files in order not to depend on the Fast Transition Link functionality. Utilities are also provided for HP-UX 9.0 and HP-UX 10.0-based systems to coexist and to lend flexibility in transitioning large and complex distributed environments to the HP-UX 10.0 release. These utilities are described in a following section. III. Support for the HP-UX 10.0 New Business Release The HP-UX 10.0 New Business Release is a production-quality release that is initially focused on: 1. New project opportunities requiring the enhanced functionality supported on HP-UX, as soon as your required application set (HP and HP Channel Partner) has been recertified on HP-UX 10.0. 2. Dedicated test or evaluation systems within your environment that can be used to prepare for a future production system upgrade to the HP-UX 10.0 General Business Release. The HP-UX 10.0 New Business Release is being actively recertified by thousands of HP Channel Partners, with key database partner availability coincident with the initial release. HP Channel Partners have had excellent results with the functionality, performance, and binary compatibility provided by the HP-UX 10.0 New Business Release. Hewlett-Packard recommends that support customers with existing installations, particularly those with production HP-UX 9.0 environments, wait to upgrade to HP-UX 10.0 at the HP-UX 10.0 General Business Release. At that time, we expect all key HP Channel Partner applications and HP applications to be available. In addition, until automated update tools become available at the HP-UX 10.0 General Business Release, the operating system must either be loaded through Instant Ignition (new systems) or a cold install process must be performed (for existing systems running HP-UX 9.X or new systems that are not Instant Ignition systems) for the HP-UX 10.0 New Business Release. For customers who choose to install the HP-UX 10.0 New Business Release, HP will provide support for new systems that use Instant Ignition or cold installs. A cold install requires saving a system's current configuration information (a recommended back-up procedure), installing the HP-UX 10.0 New Business Release, customizing your newly installed system and using the saved HP-UX 9.X configuration information, and carefully restoring filesets to the correct new new directory locations. The downtime required to conduct this cold install may take from 4 to 24 hours depending on the complexity of your system configuration, a period normally not available for production system environments. This compares with an expected 4 to 12 hours downtime for most customers using the automated update process at the HP-UX 10.0 General Business Release. With the HP-UX 10.0 General Business Release, in mid-1995, HP will offer an expanded suite of support services to assist those customers investigating, planning, or implementing the upgrade of their systems to HP-UX 10.0. In addition, Delta Training seminars will be available for 10.0. For further information, please contact your local sales office. Also, at the HP-UX 10.0 General Business Release, HP will introduce the Upgrade Assistance Service (UAS). This service will offer phone-based assistance from upgrade specialists and provides you with a comprehensive, custom upgrade plan. The Upgrade Assistance Service is delivered by HP's Response Centers and is designed to minimize upgrade planning time, system downtime, and post-upgrade time. Analysis, Conversion, and Interoperability Tools to assist you with HP-UX 10.0 HP-UX 10.0 offers Analysis tools that run on either HP-UX 9.0 or HP-UX 10.0, and that offer two key sets of functionality. The first set identifies the rare conditions where changes in HP-UX 9.0 software source code and scripts need to be performed to make them usable on the HP-UX 10.0 release base. Examples of these conditions include the detection of the use of obsoleted or modified APIs and commands (generally allowing compliance with additional industry standards). The second set identifies (and optionally in the case of source files, automatically converts) hard coded file path names used within applications, makefiles and scripts affected by the change to the new SVR4 File System Directory Layout. The Fast Transition Links provided in HP-UX 10.0 enable customers to delay making this second set of changes during the upgrade; these changes can now be scheduled during standard maintenance at any time during the life of HP-UX 10.0. HP will not, however, maintain support of Fast Transition Links beyond the life of HP-UX 10.0. The Analysis and Conversion Tools are available to assist those customers who wish to begin the evaluation and preparation for the HP-UX 10.0 General Business Release. The tools, which run on both HP-UX 9.0 and HP-UX 10.0, identify required changes in HP-UX 9.0 software source code and scripts to make them usable on HP-UX 10.0 either with or without Fast Transition Links. The specific Analysis tools included are: "prepare", a tool to manage changes to large collections of files; "analyzer", a tool that identifies path name, command option and system call changes required in source code, makefiles, shell scripts, documents, and text files; and "fnlookup", a tool that is used to look up the 9.0 and corresponding 10.0 location of files. All requested shipments of the HP-UX 10.0 New Business Release will include the Analysis and Conversion Tools. However, customers under an HP support contract who are interested in beginning the evaluation and preparation process before the HP-UX 10.0 General Business Release in mid-1995, may obtain these tools now. Please see the "Release Availability" section, located at the end of this document, for information on how to obtain these tools. Interoperability Tools will also be available on HP-UX 10.0. These tools will facilitate the administration of a mixed environment of HP-UX 10.0 systems and either PA-RISC-based HP-UX 9.0 systems or Series 300/400 systems. As with previous releases, these include the provision of an Interoperability "Cookbook" and Planning Guide (watch for information about availability, which is expected shortly after the New Business Release), remote SAM administration between HP-UX 9.0 and 10.0 systems and a utility to provide fpkg(DUI)-to-SD format conversion for application packages. Further coexistence tools are planned coincident with the HP-UX 10.0 General Business Release. SD-UX will be offered on HP-UX 9.0 and DUI (fpkg format) on HP-UX 10.0 so that customer or HP Channel Partner software packaged in either format can be installed on all systems in a mixed HP-UX 9.0/10.0 environment. HP is also planning to provide Interoperability Links. These allow a HP-UX 9.0 system to appear similar to a HP-UX 10.0 file system directory layout. Interoperability Links allow applications or scripts developed on HP-UX 10.0 to execute without changes on HP-UX 9.0-based systems. A pathname locator will keep a record of the core HP-UX old and renamed pathnames. Additionally, a tool is provided which allows the Series 300/400 workstations to be used as an X-Terminal to HP 9000 Workstations and to HP 9000 Servers running HP-UX 10.0-based releases. The Software Distributor Client (SD) will also be provided for the Series 300/400, thus allowing a "pull" of software from the SD depot. HP-UX 9.0 and 8.0 Release Support Since many of our customers are running HP-UX 9.0-based systems, HP will continue HP-UX 9.0 software application distributions for four distribution cycles beyond the HP-UX 10.0 General Business Release in mid-1995. HP 9000 Workstation customers can expect to receive specific hardware support enhancements for their HP-UX 9.0-based systems. Subsequent software releases of HP-UX 9.0 will support new uni-processor systems, new graphics hardware, new peripherals, and will contain defect fixes. These releases will continue through 1995, as necessary. HP 9000 Server customers may also anticipate small updates to HP-UX 9.04 to support new peripherals during 1995. Please note: With the release of HP-UX 10.0 New Business Release, HP-UX 8.0 support will be handled as in the past for superseded releases. HP will provide the normal level of support, however no additional or new software enhancements and software applications will be provided. HP-UX 8.0 products will become unavailable for customers ordering new systems and software products. Media Changes for HP-UX 10.0 In November, 1994 HP notified HP 9000 Workstation and HP 9000 Server customers of the intention to standardize on CD-ROM media for software delivery. Making it easier for you to do business with HP, and at a lower cost, are the main objectives of the CD-ROM program. CD-ROM offers numerous benefits including: all HP software in one media set; fast, simple delivery of software; easy installation and system administration; and access to numerous HP-UX applications and complementary software products. The HP-UX 10.0 New Business Release will be supported on CD-ROM, DDS, and QIC-525 (for HP 9000 Servers only) media. The HP-UX 10.0 General Business Release will provide support on 1600 bpi magnetic or HP 1/4-inch cartridge tape media, however, these media types are not provided with the HP-UX 10.0 New Business Release. HP 1/4-inch cartridge tape is supported as a backup media for both the HP-UX 10.0 New and General Business Release, however, the cold install media will not be provided. The support media will consist of the COPYUTIL utility (allows for disk images), with no HP-UX 10.0 General Business Release recovery kernel. Magnetic tape media will support cold installs, update, and support media on the HP-UX 10.0 General Business Release in mid-1995. Magnetic tape is supported as a backup media for both the HP-UX 10.0 New and General Business Release. The HP-UX 10.0 General Business Release will be the last supported release for HP 1/4-inch cartridge and 1600 bpi magnetic tape media. We encourage you to take advantage of the many benefits associated with CD-ROM media as you update your HP system and support investment. IV. HP-UX 10.0 Supported Hardware and Software New Business Release Supported Platforms The HP-UX 10.0 New Business Release will support the following, currently orderable HP 9000 Servers (formerly known as Series 800) and HP 9000 Workstation platforms (formerly known as Series 700). (Additional platforms will be supported on the HP-UX 10.0 General Business Release in mid-1995, see the next section): HP 9000 Servers --------------- Models Exx Models Fxx Models Gxx Models Hxx Models Ixx Models 8x7 Model T500 Model 890 HP 9000 Workstations -------------------- Model 712 Model 715 Model 725 Model 735 Model 742 Model 743 Model 745 Model 755 Model 747 Model 748 General Business Release Supported Platforms HP-UX 10.0 General Business Release, in mid-1995, will be supported on the following additional HP 9000 platforms: HP 9000 Servers --------------- Model 822 * Model 825 * Model 840 * Model 832 Model 835 Model 842 Model 845 Model 850 Model 852 Model 855 Model 860 Model 865 Model 870 HP 9000 Workstations -------------------- Model 705 Model 710 Model 720 Model 730 Model 750 * Note: a 16 MB card must be placed in the first memory slot to use HP-UX 10.0 for these systems. 8 MB memory cards are not supported in the first memory slot. HP-UX 10.0 Non-Supported Platforms HP-UX 10.0 and subsequent HP-UX 10.0-based releases will not support the platforms listed below. HP-UX 9.0 was the last operating system release to support the following HP 9000 platforms. HP 9000 Servers --------------- Model 635 Model 645 Model 808S Model 815S HP 9000 Workstations -------------------- Model 825CHX ** Model 825SRX ** Model 825TurboSRX ** Model 834CH ** Model 834SRX ** Model 834TurboSRX ** Model 835CHX ** Model 835SRX ** Model 835TurboSRX ** **Note: Graphics cards were not supported on these systems at HP-UX 9.0. HP 9000 Workstations--Series 300/400 ------------------------------------ Although Series 300/400 systems are not supported on the HP-UX 10.0-based releases, Interoperability Tools will be available on HP-UX 10.0 to facilitate the administration of a mixed environment of HP-UX 10.0 systems and either PA-RISC-based HP-UX 9.0 systems or Series 300/400 systems. Additionally, with the HP-UX 10.0 General Business Release, a new tool allows the Series 300/400 workstation to be used as an X-Terminal to HP 9000 Workstations and to HP 9000 Servers running HP-UX 10.0-based releases. The Software Distributor (SD-UX) Client will also be provided for the Series 300/400, thus allowing a "pull" of software from the SD depot. V. HP-UX Software Application Products Supported on the HP-UX 10.0 New Business Release The following HP-UX software application products are supported on the HP-UX 10.0 New Business Release. Product Numbers HP 9000 HP 9000 Product Description Workstations Servers ------------------- ------------ ------- 100vg AnyLan J2655AA N/A 100vg AnyLan J2645AA N/A C SoftBench End User Kit B4089BA B4090BA C SoftBench EUK Japanese B4089BJ B4090BJ C SoftBench LTU B3560BB B4085BB C++ LTU B3911AB B3913AB C++ Media/Documentation B3910AA B3912AA C++ SoftBench End User Kit B4092BA B4093BA C++ SoftBench EUK Japanese B4092BJ B4093BJ C++ SoftBench LTU B2617B B4087BB C/Ansi C Bundle LTU B3899AA B3901AA C/Ansi C Bundle B3898AA B3900AA COBOL Compiler LTU B2431AB B2434AB COBOL Compiler Media/Manuals B2431AA B2434AA COBOL Developers LTU B2430AB B2433AB COBOL Developers Media/Manuals B2430AA B2433AA COBOL Runtime LTU B2432AB B2435AB COBOL Runtime Media B2432AA B2435AA COBOL SoftBench Compiler EUK B4894BA B4895BA COBOL SoftBench Compiler LTU B4545BB B4018BB COBOL/C SoftBench End User Kit B4896BA B4897BA COBOL/C SoftBench LTU B4546BB B4021BB COBOL/C SoftBench Compiler EUK B4898BA B4899BA COBOL/C SoftBench Compiler LTU B4547BB B4024BB COBOL/C++ SoftBench Compiler EUK B4900BA B4901BA COBOL/C++ SoftBench Compiler LTU B4535BB B4537BB COBOL SoftBench End User Kit B4892BA B4893BA COBOL SoftBench LTU B4544BB B4015BB COBOL/C Bundle N/A B4891AB COBOL/C++ Bundle N/A B4890AB DCE Domestic Libraries B2915AA B3864AA DTC Manager/UX J2102A J2120A Dialog LTU B3454AB B3455AB Dialog Media/Manuals B3454AA B3455AA Encapsulator End User Kit B4097BA 4098BA Encapsulator EUK Japanese B4097BJ 4098BJ Encapsulator LTU B2606B 4095BB FDDI/9000 for Servers (S800) N/A J2157A FDDI/9000 for Model 755 A2654A N/A FDDI/9000 for Model 735 A2665A N/A FTAM/9000 J2163A B1033A Facetterm C1096A C1096A HP Enware Software B3651CA B3651BA HP FORTRAN LTU B3907AA B3909AA HP FORTRAN Media B3906AA B3908AA HP GlancePlus Motif B3691AA B3693AA HP GlancePlus Package B3699AA B3701AA HP Performance Collector B1806A B2663A HPNP J2374B J2374B MirrorDisk/UX B3949AA B2491A OTS/9000 J2160A 32070A PASCAL Compiler B3902AA B3904AA PASCAL Compiler LTU B3903AA B3905AA Phigs Developers Environment B3939A N/A Phigs Runtime Environment B3940A N/A Process Resource Manager LTU B3947AA B3835AA Process Resource Manager Media B3948AA B3834AA PowerShade B3941A N/A SNA+ 3179G J2230A J2224A SNA+ 3270 J2227A J2221A SNA+ API J2229A J2223A SNA+ Link J2226A J2220A SNA+ RJE J2228A J2222A MC/ServiceGuard LTU N/A B3935AA MC/ServiceGuard Media N/A B3936AA SwitchOver/UX N/A 92668A TN3270 LTU J2636AA J2636AA TN3270 Manuals J2656AA J2656AA TN3270 Media J2646AA J2646AA Token Ring/700 Workstations J2165A N/A Token Ring/712 A4011A N/A Token Ring/800 Servers N/A J2166A ToolBox LTU B3452AB B3453AB ToolBox Media/Manuals B3452AA B3453AA UEDK LTU B3392AA B3394AA UEDK Media/Manuals B3393AA B3395AA UIM/X.26 End User Kit B4904BA B4905BA UIM/X.26 EUK Japanese B4904BJ B4905BJ UIM/X.26 LSC End User Kit B1189B B1187B UIM/X.26 LTU B1183A B4550BB VT3K LTU J2140BA B1029CA VT3K Media/Manuals J2400AA J2399AA Visual Editor 3 B1517AB B1517AB Visual Editor 3 B1518AA B1519AA X.25/9000 Link J2159A 36960A Key: N/A= Not Applicable; EUK= End User Kit; LTU= License To Use HP plans to have all key HP software application products supported on HP-UX 10.0 no later than the HP-UX 10.0 General Business Release scheduled for mid-1995. VI. Release Availability HP suggests that you read the information provided in this document prior to making a decision on requesting the HP-UX 10.0 New Business Release. If you would like more information on the HP-UX 10.0 New Business Release, or would like to order the Analysis and Conversion Tools, please follow the appropriate contact method listed below to acquire this information: Geographic Region Contact Method ------------------------------------------------------------------------- U.S. and Canada HP SupportLine (HPSL) World Wide Web (WWW) Service ------------------------------------------ Using a WWW browser that utilizes the forms features you can access HPSL at the following URL: http://support.mayfield.hp.com Then select "New Products" in the "Support News" section. A news article will explain where to find the HP-UX 10.0 New Business Release information. For assistance, send a message to: webmaster@support.mayfield.hp.com HP SupportLine (HPSL) Electronic Mail (E-Mail) ---------------------------------------------- In the TEXT portion of a message sent to support@support.mayfield.hp.com: send new_products_list This will return a list of news articles which will contain one news article which explains where to find the HP-UX 10.0 New Business Release information. For a copy of the HPSL mail service user's guide, send the following in the TEXT portion of a message to support@support.mayfield.hp.com: send guide.txt For further assistance send an electronic mail message to support-feedback@support.mayfield.hp.com HP SupportLine (HPSL) Dial-Up Service ------------------------------------- Step 1. Dial the HP SupportLine telephone number, (415) 691-3680. (For the telephone number in all other countries, contact your local HP sales office or Response Center). Step 2. When your communications program indicates that you are connected, press RETURN. Depending on where you are located, you will have to perform a command before you are connected to one of the HPSL computers. In the U.S. (and Singapore) The system prompt, login: should appear. [In Europe, you would receive a DTC welcome message and a prompt, HPSL DTC> C patch In Asia-Pacific, you would receive a PAD, X.25, welcome message and a PAD prompt, @ should appear. Then enter: #CAM ] Step 3. At the system prompt, login:, log into HPSL by typing the following command: hpsl then press RETURN. Step 4. When prompted, type your system handle and password, each followed by pressing RETURN. If you do not know your system handle or password, use the HPSL assistance numbers which are listed after these instructions. Step 5. Press RETURN until the HPSL Top Menu screen is displayed. Then enter the "News Page" section, option 1, and select the "New Products" option. A news article will explain where to find the HP-UX 10.0 New Business Release information. Step 6. Type EXIT when you wish exit HPSL, the connection will be terminated. If you require HPSL assistance: ------------------------------ HP BasicLine Support customers: Call (415) 691-3888 (if you do not know your password or if you have access questions). HP ResponseLine, HP Premier Account Support (PAS), or HP Personalized System Support (PSS) customers: Call (800) 633-3600; log a call with the HP Response Center if you do not know your password or require HPSL assistance. or If you are still unable to access HPSL, through any of the methods provided, please send a fax to (404) 988-3991 to request the HP-UX 10.0 New Business Release information. Your fax must include: your name, company address, and phone number and indicate that you are requesting the information on HP-UX 10.0. In response, you will be mailed the HP-UX 10.0 New Business Release information. Latin America Call your Local HP Response Center Asia-Pacific Call your Local HP Response Center Europe, Middle East, Call your Local HP Sales Office and Africa OSF and Motif are trademarks of the Open Software Foundation in the U.S. and other countries. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/OPEN Company Limited. Technical information in this document is subject to change without notice. (c)Copyright Hewlett-Packard Company 1995. All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. ------------------------------ Subject: 11.2 Can you have Multiple IP addresses on one interface? HP ServiceGuard allows you to configure multiple IP addresses on one interface. First, all primary network interfaces must have "stationary" IP addresses "ifconfig"ed on them. Say for example, you have a system with 2 ethernet interfaces (one primary and one for backup) and 2 FDDI interfaces (one primary and one backup) and they are interfaces lan0, lan1, lan2 and lan3 respectively. Your /etc/rc.config.d/netconf file would have lan0 having an IP address/subnet, etc (say 15.13.169.15) and lan2 would have an IP address/subnet, etc (192.6.144.15) lan1 and lan3 would not be specified in the netconf file as they will not initially have any IP addresses on them. ServiceGuard has a "cmmodnet" command which will ADD IP addresses to existing interfaces. For example, to add a "Package IP" address to the ethernet lan you would: cmmodnet -a -i 15.13.169.16 15.13.143 Where -a is add -i 15.13.169.16 is the IP addrss to add and 15.13.143 is the subnet where to add it. The cmmodnet command (via the ioctl()s) then figures out that the SUBNET is currently on lan0 and magically you have 2 ip addresses on the same SUBNET. Both going through lan0. This feature is only currently available through the ServiceGuard product. ------------------------------ Subject: 11.3 What version of named is running at HP-UX 10.0? Version 4.8.3 is running at HP-UX 10.0. $ what /usr/sbin/named /usr/sbin/named: Copyright (c) 1986, 1989, 1990 Regents of the University of California named 4.8.3 Tue Nov 1 17:03:51 GMT 1994 ------------------------------ 12. s300/400 SPECIFIC INFORMATION ------------------------------ 12.1+ When will HPUX 9.10 be available? HP-UX 9.10 MR'd on 3/1/95. It will be shipped on April 17 1995 on DART 22. This release is the latest PCO in the 9.X stream for the 68k platform, and completely replaces the 9.03 release of last spring. This release provides: defect fixes, patch roll-up, selected enhancements, and additional peripheral support, while maintaining binary and script compatibility, providing improved interoperability with 10.0, and satisfying the top 10 customer requests as allowed. ------------------------------ -- Colin Wynd Email: colin@col.hp.com Regional Sales Engineer Phone: 719-531-4282 Network Test Division Fax: 719-531-4526 Hewlett-Packard Company Pager: 800-531-8888 pin: 801-4469 --------------------------------------------------------------------