comp.sys.hp.hpux FAQ (Frequently Asked Questions) From: gcagle@delta9.mentorg.com (Greg Cagle) Subject: comp.sys.hp.hpux FAQ Date: 15 Apr 1994 15:47:38 GMT Keywords: FAQ Archive-name: hp-faq Last-modified: 1994/4/15 Version: 2.13 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. 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 ~biweekly, on the 15th and the last day of the month. This article is Copyright 1994 by Greg Cagle. 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, Mentor Graphics, or Hewlett-Packard. Refer to question 3.l 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. 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 Greg Cagle . ------------------------------ 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 1994 3.6 InterWorks Conference 1994 3.7 HP/Works 3.8 HP/Works Conferences 3.9 HP-UX publicly available software from InterWorks. 3.10 Anonymous FTP Sites for HP-UX, and UNIX related software. 3.11 Where can I get a demo CD with software for HP-UX? 3.12! HP-UX patch information and mailing list. 3.13 How can I send mail to an "hpdesk" address? 3.14 What are the known issues with porting BSD-based programs to HP-UX? 3.15 What periodicals are available that focus on HP-UX? 3.16 Books on HP-UX 4. THIRD PARTY VENDORS 4.1 Third party vendors for RAM. 4.2 Third party vendors for peripherals 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 Where did xline go at 9.x? 6.17 How can I get HP-VUE to not override colors? 6.18 How can I override the system default printer in vuepad? 6.19 How can I get the VUE 2.01 man page help index back? 7. OPERATING SYSTEM 7.1 Can I have filenames longer than 14 chars? 7.2 How can I tell what filesets 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 Where can I get SLIP for HP-UX? 7.24 How come I can't lock files across NFS after upgrading to 9.01? 7.25 What's a good strategy for clearing /tmp? 7.26 How can I change the timezone? 7.27 Is there an equivalent for getrusage()? 7.28! How can I look at what my system is doing? 7.29 How can I partition HP-UX disks? 7.30 How can I print man pages successfully? 7.31 How can I limit core files? 7.32 Can I put more than one backup on DDS with fbackup? 7.33 How can I load multiple patches on a machine at the same time? 7.34 How can I set up an HP-UX workstation as an X terminal? 7.35! What causes "Unable to initialize MI" when running Glance? 7.36 Where can I get pcnfsd on HP-UX? 7.37 Where can I get ppp for HP-UX? 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? 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.01? 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? ------------------------------ 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-faq This FAQ is also archived on the Interworks archive machine: ftp://iworks.ecn.uiowa.edu/comp.hp An HTML version of this document is available as: http://www.cis.ohio-state.edu/hypertext/faq/usenet/hp-faq/faq.html You can also get it by e-mail from mail-server@rtfm.mit.edu; send the text "send usenet/news.answers/hp-faq". 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. If all else fails, contact the maintainer (greg_cagle@mentorg.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 1994 For more information, please contact the INTEREX Conference Department at the above address. ------------------------------ Subject: 3.6 InterWorks Conference 1994 The next InterWorks conference is to be held 5/15/94 - 5/18/94 at the Buena Vista Palace in Walt Disney World Village, Buena Vista, Florida. ------------------------------ Subject: 3.7 HP/Works HP/Works is basically the UK equivalent of InterWorks - catering for users of HP workstations running both HP-UX and Domain/OS. Full membership details are avaiable from:- Helen Grainger, PO Box 47, Bicester, United Kingdom +44 (0)869 321080 or by e-mail to J.G.Owen@bham.ac.uk ------------------------------ Subject: 3.8 HP/Works Conferences The next conference (Spring) is 3/23 - 3/24 in Durham, England. The conference is a two-day event as follows: DAY ONE is a half day workshop/clinic with hands on tutorial sessions covering HP-UX and associated HP software products. Topics will include the use of GLANCE (including GPM, the new X-windows based interface), using NETDIST to update a group of workstations, a demonstration of the ATRIA software products and accessing HP's Bristol Supportline. DAY TWO is the main conference/AGM day and will include an update on the very latest information from HP, presentations on Management of Distributed Computer Systems & High Speed Networking - plus an Open Forum - your chance to ask senior HP representatives the things you really need to know Further details about the conference can be obtain from either Helen Grainger or by e-mail via j.g.owen@bham.ac.uk. ------------------------------ Subject: 3.9 HP-UX publicly available software from InterWorks. Dave Shaw maintains a library of publicly available HP-UX related software on behalf of the InterWorks User Group. He can be reached at (303)443-9413, or via e-mail at . The following text is provided by Dave. See the README mentioned below for details. There is an archive of UX-related software on the InterWorks library node (iworks.ecn.uiowa.edu--128.255.18.10). Note that everything is available via anonymous ftp in the comp.hp directory (ftp://iworks.ecn.uiowa.edu/comp.hp). The README there contains a complete list of the available software. Nearly all of it is also available on a CD for $75.00 ($85.00 outside the U.S.). For ordering information contact Carol Relph. All of the archive is suitable for the 700 series machines, and I have started to verify that. Executables are included in some packages. If 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.10 Anonymous FTP Sites for HP-UX, and UNIX related software. Site: ftp://iworks.ecn.uiowa.edu/comp.hp Address: 128.255.18.10 Contents: The InterWorks HP-UX Library in the directory "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.csc.liv.ac.uk Address: 138.253.42.172 Contents: Large number of packages ported to HP-UX 8.07 and 9.01 Here is an overview of ftp.csc.liv.ac.uk as of Sun 10 Apr 1994: (The 2 most recently installed packages in each category are in brackets) 54 packages in /hpux9/X11R5/Graphics (ImageMagick-2.3.7 xpm-3.4a) 43 packages in /hpux9/Games (xpilot-3.1.1 xpilot_sounds-3.1.0) 42 packages in /hpux9/X11R5/Misc (fvwm-1.21z xmailbox++-1.2) 32 packages in /hpux9/Networking (wuftpd-2.3 inn-1.4sec) 27 packages in /hpux8/Maths/Misc (octave-1.0 fudgit-2.34) 25 packages in /hpux8/X11R4/Misc (xsky-2.01 xvertext-5.0) 24 packages in /hpux9/Gnu (bulletin-01.94 indent-1.9.1) 23 packages in /hpux9/X11R5/Demos (xlockmore-1.2 xmountains-1.2) 21 packages in /hpux8/Games (xblockbuster-1.03 xyahtzee-1.01) 19 packages in /hpux9/X11R5/Networking (freeWAIS-0.3 xbrowser-1.2) 18 packages in /hpux8/Networking (netperf-1.7.1 tftpd-1.0) 17 packages in /hpux9/X11R5/Toolkits (libsx-1.0 wxLib-1.50) 16 packages in /hpux9/Text (ispell-3.1.04 dvips-5.55) 16 packages in /hpux9/Sysadmin (expect-5.6.3 lsof-2.32) 16 packages in /hpux8/X11R4/Demos (xball-3.0 xspringies-1.1) 15 packages in /hpux9/X11R5/Core (imake-5.03 imake-5.02) 15 packages in /hpux9/Misc (screen-3.5.4alpha pcomm-2.0.1) 15 packages in /hpux8/X11R4/XView3 (workman-1.2.1 workman-1.2) 14 packages in /hpux8/X11R4/Toolkits (andrew-5.1.part04 Wcl-2.5) 13 packages in /hpux9/Editors (nedit-3.0 xcoral-2.1) 13 packages in /hpux8/Maths/LinAlgebra (rlab.all-0.97d rlab-0.97d) 11 packages in /hpux8/Misc (gaps-5.11 csound-2.00b) 10 packages in /hpux9/Languages (swi-1.8.9 sgmls-1.1) 9 packages in /hpux9/Users (less-178.magic.2 pine-3.89) 8 packages in /hpux8/X11R4/Graphics (xv-2.21 xscribble-a6) 8 packages in /hpux8/X11R4/Core (MITlib-4.00 appres-1.5) 8 packages in /hpux8/Sysadmin (rpasd-2.0 pltools-2.0.2) 8 packages in /hpux8/Physics (asa-2.27 asa-2.15) 8 packages in /hpux8/Languages (gofer-2.28b scheme-7.1.3) 7 packages in /hpux8/X11R5 (XR5src-5.23.part01 XR5built-5.23) 7 packages in /hpux8/X11R4/Networking (adcmail-0.9 collage-1.0b) 7 packages in /hpux8/Text (tr2latex-2.2a TeX-3.14) 6 packages in /hpux8/NeuralNets (am-6.0 GAucsd-1.4) 5 packages in /hpux8/Users (xmodem-3.9 es-0.84) 4 packages in /hpux9/NeuralNets (snns-3.1 atree-2.0) ======================================= 584 packages in total The Liverpool archive supports a gopher server at gopher.csc.liv.ac.uk (138.253.42.174) and also a mail server at mail-server@csc.liv.ac.uk for users without access to anonymous FTP. Name: hpux.ask.uni-karlsruhe.de Address: 129.13.200.57 Contents: The official German mirror site of ftp.csc.liv.ac.uk Name: ftp.cae.wisc.edu Address: 144.92.4.15 Contents: The official US mirror site of ftp.csc.liv.ac.uk Name: hpux.cict.fr Address: 192.70.79.53 Contents: The official French mirror site of ftp.csc.liv.ac.uk The Interworks and Liverpool sites are now cooperating as follows: 1) The Liverpool archive will carry packages originating from and submitted to the Interworks site. These packages will be integrated into the existing structure of the archive. 2) Interworks will provide binaries for each of the packages on the Liverpool archive. These packages will be organized into a directory structure matching that of the Liverpool site. *** Note: This is not immediately available but should be up and running soon *** 3) Interworks will continue to provide complete packages (source+binaries) for the HP and user-contributed software in its library. Site: ftp://ftp.prz.tu-berlin.de Address: 130.149.62.68 Contents: Much of the Liverpool archive. Site: ftp://export.lcs.mit.edu Address: 18.24.0.12 Contents: The X Window System and contributed clients. Site: ftp://hpcvaaz.cv.hp.com Address: 15.255.72.15 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://ftpboi.external.hp.com Address: 192.6.71.2 Contents: Drivers for HP printers. Site: ftp://lut.fi/pub/hpux ftp://lut.fi/pub/unix/hp-ux Address: 157.24.10.8 Contents: Various Site: ftp://nic.funet.fi/pub/unix/arch/hpux Address: 128.214.6.100 Contents: Various Site: ftp://prep.ai.mit.edu Address: 18.71.0.38 Contents: The Free Software Foundation's GNU utilities, etc. Site: ftp://hybrid.irfu.se/pub Address: 130.238.30.23 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 Address: ? Contents: GNU stuff ported to HP-UX 9.x by Pierre Mathieu. Site: ftp://jazz.gsfc.nasa.gov Address: ? Contents: bathymetry, FFT, graph, pgplot, triangulation, sortroutine Site: ftp://jaguar.cs.utah.edu/dist Address: ? Contents: FSF compiler/assembler/debugger tools. Code usually has PA specific bugfixes/enhancements not yet in the official FSF releases. Source and binaries available. hpux-symtab.h has symbolic debug format documentation. hpgdb.patch has a gdb patch for HP compilers. Currently available in the "dist" directory: GDB 4.11.u2 - Last update 12/04/93 HPGDB 4.11.u2 - Last update 12/04/93 GAS 2.2.u2 - Last update 12/04/93 GCC 2.5.6.u4 - Last update 12/04/93 LIBG++ 2.5.2.u2 - Last update 12/04/93 Yes, you see gas-2.2; the first cut at a BFD based SOM assembler for the PA is ready for external use. Release notes are in README.gas. The prebuilt binaries can be retrieved all at once from hpuxbin.tar.Z, or in pieces from the hpuxbin directory. ------------------------------ Subject: 3.11 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. Be sure and check out the Drive demo. ------------------------------ Subject: 3.12! HP-UX patch information and mailing list. 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 (support.mayfield.hp.com,192.6.148.19) and down load 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. 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. Additionally, there is an HP-UX patch mailing list, run by Bart Muyzer . To SUBSCRIBE, send e-mail to: There is a discussion underway to change the focus of this list from patches to sysadmin; stay tuned for further developments. For reference, the latest patches for critical parts of 9.01 are: PHKL_2449 : s700 9.01 limit dynamic buffer cache allocation PHKL_3075 : s700 9.01 Fix for select() panic and memory leak PHKL_3985 : s700 9.01 kernel megapatch PHNE_3604 : s700_800 9.X fix for multiple rpc.lockd problems PHNE_3701 : s700_800 9.X automount(1M) patch including map entry fix PHNE_3424 : s700_800 9.X fix for multiple rpc.statd problems PHSS_3812 : s700 9.X /bin/ld fixes PHSS_3773 : s700 9.X ANSI C compiler patch revision A.09.63 PHSS_3779 : s700 9.X X11R5 Xserver March 1994 Periodic Patch Similar patches for 9.03 are: PHKL_2755 : s700 9.03 fix for dynamic buffer cache performance problem PHKL_3076 : s700 9.03 Fix for select() panic PHKL_3570 : s700 9.03 data segmentation fault when calling vfork() PHKL_3621 : s700 9.03 patch for NFS/symbolic links/fsync PHNE_3388 : s700_800 9.X corrects rpc.mountd problems PHNE_3424 : s700_800 9.X fix for multiple rpc.statd problems PHNE_3573 : s700 9.03 fixes multiple ARPA Transport defects PHNE_3604 : s700_800 9.X fix for multiple rpc.lockd problems PHSS_3773 : s700 9.X ANSI C compiler patch revision A.09.63 PHKL_3975 : s700 9.03 kernel megapatch with NFS readdir/seekdir fix PHSS_3812 : s700_800 9.X ld(1) patch PHSS_3779 : s700 9.X X11R5 Xserver March 1994 Periodic Patch ------------------------------ Subject: 3.13 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.14 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.15 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.16 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: 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 peripherals Vendor Products ------ -------- MDL Corporation Disk, tape, optical, jukebox, EISA expansion, RAID, others. 15301 NE 90th St. Redmond, WA 98052 FAX (206)861-6767 (800)800-3766 (206)861-6700 Modular Industrial MICHIL PS2 to HP-HIL converter. Allows standard PC keyboards Computers and mice to be connected to HP workstations. 615-499-0700 Joe Malley ITAC Systems, Inc. Supports Mouse-trak trackball for HP-HIL 3113 Benton St. Garland, Tx 75042 800-533-4822 yvonne@moustrak.com (Thanks to Mike Lampi, MDL, Jeff Dwork, AMD, and Walter Underwood, HP) ------------------------------ 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) ------------------------------ 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.10 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. ------------------------------ 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" In case in gets mangled, 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])); } (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? 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 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". (Thanks to Bill Morrison, HP) ------------------------------ 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 Where did xline go at 9.x? We don't know. The 9.03 Motif version of Glance Plus has what xline had (and more). ------------------------------ Subject: 6.17 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.18 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.19 How can I get the VUE 2.01 man page help index back? 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: 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 (Thanks to Ken Burke.) ------------------------------ Subject: 7.2 How can I tell what filesets 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 PHCO_3990 and PHNE_3686 allow configuration of the order of hostname resolution. For more detail, see the docs in PHNE_3686; the bottom line is that it's like Solaris 2.x. ------------------------------ 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 | grep $LOGNAME | wc -l` if [ $NUMLOGINS -lt 2 ] then cat /etc/copyright fi And, for /etc/csh.login: set NUMLOGINS=`/etc/last | grep $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, and Steve Dum, ) ------------------------------ Subject: 7.16 How can I turn off quota checking? The safe way is to use /etc/rmfn to remove the QUOTA fileset. ------------------------------ 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: 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 by PHSS_2199. The linker does not traverse shared library search paths itself. Patched by PHSS_3537. Various X11 problems have been reported including drawing problems and memory leaks. Get the latest X server (currently PHSS_3235). Various serious C compiler problems have been fixed with PHSS_3707. Memory leaks can occur and lock up a system; patch PHKL_3075 may fix it. catman will core dump; patch PHCO_2183 fixes it. 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. (Thanks to Rob Gardner, HP) ------------------------------ Subject: 7.23 Where can I get SLIP for HP-UX? On HP workstations, SLIP is called ppl and is a part of the LAN/9000 Link product (Thin coax hardware interface + Ethernet/802.3 driver + TCP/IP transport). Although conceptually a separate "product", the LAN/9000 Link is shipped as part of every HP workstation. (Thanks to Mike Taylor, HP) ------------------------------ Subject: 7.24 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.25 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.26 How can I change the timezone? Edit the entry in /etc/src.sh and /etc/src.csh, and reboot. ------------------------------ Subject: 7.27 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: 7.28! 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. (thanks to Doug Grumman ) ------------------------------ Subject: 7.29 How can I partition HP-UX disks? 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. # # 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) ------------------------------ Subject: 7.30 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.31 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. ------------------------------ Subject: 7.32 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, tt@math.jyu.fi) ------------------------------ Subject: 7.33 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.34 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.35! 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 Grumman ) ------------------------------ Subject: 7.36 Where can I get pcnfsd on HP-UX? It's part of the standard NFS distribution. ------------------------------ Subject: 7.37 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: 8. COMPILERS AND LINKERS ------------------------------ Subject: 8.1 What's a P-FIXUP error? Several questions on 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) ------------------------------ 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. (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. (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.01? For reasons too detailed to go into here, the major number for DDS drives has changed to 121 (from 54) at 9.01. ------------------------------ 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? From "man cent": The Series 700 cent driver supports six different handshake modes for data transfer. The last four bits of the minor number of the device special file specify which mode is used. The format of the device minor number is: 0xSEF00A where each letter represents a single hexadecimal digit as follows: 0x Preamble to a hexadecimal number. S Specifies the system bus module number ( 2 for core I/O). E Specifies the EISA slot number: ( always 0 for core I/O). F Specifies the function number. Always 6 for the Core I/O parallel interface. 00 Always 0. A Specifies the handshake mode. The handshake modes are: mode 1 Automatic handshaking using both nACK and BUSY. Minor number format: 0xSEF001. mode 2 Automatic handshaking using only BUSY. Minor number format: 0xSEF002. mode 3 Bidirectional read/write used for ScanJet. Minor number format: 0xSEF003. mode 4 Stream mode. Data is essentially transmitted to the peripheral without any handshaking protocol. Minor number format: 0xSEF004. mode 5 Pulsed mode using both ACK and BUSY for automatic handshaking. Similar to mode 1 except that the data strobe line, nSTROBE is pulsed for a fixed amount of time by the sender, then released. Minor number format: 0xSEF005. mode 6 Pulsed mode, using only BUSY for automatic handshaking. Similar to mode 1 except that the data strobe line, nSTROBE is pulsed for a fixed amount of time by the sender, then released. Minor number format: 0xSEF005. Modes 1 and 2 support most printers belonging to the *Jet series (LaserJet, DeskJet, QuietJet, etc.). ------------------------------ 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 SGI machine that made the tape is running Irix 4.0 and under, and that if it's 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 ) ------------------------------ Subject: 9.14 Is there a trackball for the 700? ITAC Systems supports a Mouse-trak trackball for HP-HIL (all 700s but the 712). The 712, of course, can use any PC-style trackball. (thanks to Jeff Dwork, AMD) -- Greg Cagle - Mentor Graphics Corporation - greg_cagle@mentorg.com "One ton tomato; I got a one ton tomato..."