Nebula 1994 June

home *** CD-ROM | disk | FTP | other *** search

/ Nebula 1994 June / NEBULA_SE.ISO / Documents / FAQ / HP-faq < prev next >

Wrap

Internet Message Format | 1993-08-18 | 62.4 KB

Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!gatech!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!news.mentorg.com!hpcan240.mentorg.com!dracula!gcagle From: gcagle@dracula.mentorg.com (Greg Cagle) Newsgroups: comp.sys.hp,news.answers,comp.answers Subject: comp.sys.hp FAQ Followup-To: comp.sys.hp Date: 17 Aug 1993 21:17:35 GMT Organization: Mentor Graphics Lines: 1474 Approved: news-answers-request@MIT.Edu Distribution: world Message-ID: <24rhtf$j1h@hpcan240.mentorg.com> Reply-To: greg_cagle@mentorg.com NNTP-Posting-Host: dracula.mentorg.com Xref: senator-bedfellow.mit.edu comp.sys.hp:36178 news.answers:11503 comp.answers:1651 Archive-name: hp-faq Last-modified: 1993/8/17 Version: 2.2 comp.sys.hp FAQ (Frequently Asked Questions) -------------------------------------------- This article contains the answers to some Frequently Asked Questions (FAQ) often seen in the USENET newsgroup comp.sys.hp. Discussion in this document centers around Hewlett-Packard PA-RISC computer systems running the HP-UX operating system; the focus tends to be on the series 700 workstations. It is posted monthly, on or about the 15th. Many FAQs, including this one, are available via FTP on the archive site rtfm.mit.edu in the directory pub/usenet/news.answers. The name under which this FAQ is archived appears in the Archive-nameline above (hp-faq). 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, etc., should be directed to Greg Cagle <greg_cagle@mentorg.com>. Disclaimer: ----------- The content of this article is the sole responsibility of the author and contributors, and does not necessarily represent their employers or Hewlett-Packard. TABLE OF CONTENTS: ------------------ Section 1: FINDING INFORMATION 1.1) Where can I get a copy of this FAQ file? 1.2) Courses on HP-UX. 1.3) Interex, The International Association of HP Computer Users. 1.4) InterWorks, The International HP Workstation Users Group. 1.5) Interex HP Users Conferences 1993. 1.6) InterWorks Conferences 1993. 1.7) HP-UX publicly available software from InterWorks. 1.8) Anonymous FTP Sites for HP-UX, and UNIX related software. 1.9) Where can I get a "Demo CD" with software for HP-UX? 1.10) HP-UX patch availability and mailing list. 1.11) How can I send mail to an "hpdesk" address? 1.12) What are the known issues with porting BSD based programs to HP-UX? 1.13)! Who is this George Carter, and how do I get rid of his posts? Section 2: THIRD PARTY VENDORS 2.1) Third party vendors for RAM. 2.2) Third party vendors for peripherals. Section 3: UTILITIES 3.1) ASCII to Postscript converter. 3.2) How do I make Perl on HP-UX? 3.3) What is the status of the various gnu items on HP-UX? Section 4: X WINDOW SYSTEM, OSF/MOTIF, AND HP-VUE 4.1) X11 Libraries (Athena, etc.) and utilities (imake, etc.). 4.2) How can I display an image on the root window with HP-VUE? 4.3) How do I get a scroll bar on hpterms? 4.4) How can I put a title in my hpterm titlebar? 4.5) How come my hpterms keep going away by themselves? 4.6) How come my HP X/Motif clients take a LONG time to display on a Sun? 4.7) How can I get my login stuff to work under HP-VUE? 4.8) How can I get console messages to an hpterm? 4.9) What happened to the vuewm key accelerators at VUE 3.0? 4.10) How come I can no longer disable the caps lock key with xmodmap? 4.11) How come vi behaves strangely in xterms at 9.01? 4.12) How do I disable HP-VUE? 4.13) What's a good termcap entry for hpterm? 4.14) My screen is wedged. What should I do? 4.15) How can I get an X client to come up in an alternate workspace? Section 5: OPERATING SYSTEM 5.1) Can I have filenames longer than 14 chars? 5.2) How can I tell what filesets have been loaded on my system? 5.3) How do I safely remove software from my system? 5.4) What's the scoop on HP-UX 9.0/9.01? 5.5) How come HP-UX doesn't support root NFS access? 5.6) Can I get HP-UX to try DNS before NIS? 5.7) How come the LOGnnnn files in /usr/adm keep growing and growing? 5.8) How come I can't lock mail or other files on a Sun? 5.9) What are the known issues with HP-UX 8.07? 5.10) Why are mail files in /usr/mail are owned by daemon instead of the recipient? 5.11) How can I tell if I need more than a 2-user license? 5.12) How can I tell what patches are loaded in the kernel? 5.13) How come I have to hit return after a control-d in the Korn shell? 5.14) How do I boot into single user mode? 5.15) How come my Korn shell login hangs? 5.16) How can I avoid those annoying copyright notices on login? 5.17) How can I turn off quota checking? 5.18) What are the issues with HP-UX 9.01? 5.19) Why does chown behave differently at 9.01? 5.20) How can I track log files and core files? 5.21) How much memory can a process use? 5.22)+ How come there's little discussion of DCE? Section 6: COMPILERS AND LINKERS 6.1) What's a P-FIXUP error mean? 6.2) Where is regcmp on HP-UX? 6.3) How come the default C compiler is brain dead? 6.4) How do I deal with "too many defines"? 6.5) How come I get "_builtin_va_start" undefined when I build with gcc? 6.6) How can I tell if something was built debuggable? Section 7: HARDWARE AND PERIPHERALS 7.1) Are alternate keyboards available for HP workstations? 7.2) How can I play audio CDs on an HP workstation? 7.3) How can I enable the LAN interface on a 700? 7.4) How can I get an Exabyte to work on an HP? 7.5) Is there a "node ID" on a 700? 7.6) How can I get a stuck DDS tape out of the drive? 7.7) How can I use dump with a DDS tape? 7.8) What is the correct major number for DDS drives on 9.01? -------------------------------------------------------------------------------- Subject: FINDING INFORMATION -------------------------------------------------------------------------------- 1.1) Where can I get a copy of this FAQ file? The comp.sys.hp FAQ file is posted approximately monthly to the comp.sys.hp, news.answers, and comp.answers newsgroups. It is archived on rtfm.mit.edu in the pub/usenet directory, and also on the InterWorks archive machine (see below), in the comp.hp directory. -------------------------------------------------------------------------------- 1.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 -------------------------------------------------------------------------------- 1.3) Interex, The International Association of HP Computer Users. Interex 585 Maude Court Sunnyvale, CA 94088-3839 USA The focus here is on mainframes and servers, although workstation activities are increasing. -------------------------------------------------------------------------------- 1.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 -------------------------------------------------------------------------------- 1.5) Interex HP Users Conferences 1993. Interex '93 is scheduled for September 19-23, 1993 at the Moscone Center in San Francisco. For more information, please contact the INTEREX Conference Department. INTEREX Conference Department 585 Maude Court P.O. Box 3439 Sunnyvale, CA 94088-3439, USA (800)INTEREX (U.S. & Canada only) (408)738-4848 Telex: 4971527 Fax: (408)736-2156 -------------------------------------------------------------------------------- 1.6) InterWorks Conferences 1993. The next InterWorks conference is the System Administration conference, to be held November 7-10 in Chicago at the Marriott. -------------------------------------------------------------------------------- 1.7) 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. Dave Shaw can be reached at (303)443-9413, or via E-Mail at librarian@iworks.ecn.uiowa.edu. The following is provided by Dave Shaw, the InterWorks Librarian. I've deleted the specific package descriptions (getting too long!) see the README mentioned below for details - Greg] 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 "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. -------------------------------------------------------------------------------- 1.8) Anonymous FTP Sites for HP-UX, and UNIX related software. Name: iworks.ecn.uiowa.edu 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 online (via an InterWorks member logon (see question #5 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 Sat 10 Jul 1993: (The 2 most recently installed packages in each category are in brackets) 42 packages in /hpux8/X11R4/Misc (xsky-2.01 xsky-2.0) 36 packages in /hpux8/Games (xboing-1.00b xblockbuster-1.03) 34 packages in /hpux8/Networking (c_news-2.May.92 mm-2.5) 28 packages in /hpux8/X11R4/Graphics (xv-2.21 toybox-pre1.3) 23 packages in /hpux8/Gnu (texinfo-3.1 gs_fonts-2.6.1) 21 packages in /hpux8/X11R4/Demos (xfractint-2.00 xball-3.0) 18 packages in /hpux8/X11R4/Toolkits (xf-2.2 xtpanel-2.23) 17 packages in /hpux9/X11R5/Graphics (xpaint-2.1.0 plotmtv-1.32) 16 packages in /hpux8/X11R4/Networking (adcmail-0.9 wais-8b4) 16 packages in /hpux8/Misc (pvm-3.1 gaps-5.11) 15 packages in /hpux8/X11R4/XView3 (workman-1.0.2 workman-1.0.1) 14 packages in /hpux8/Users (xmodem-3.9 elm-2.4.22) 14 packages in /hpux8/Maths/Misc (cdflib-23.Jun.93 ranlib.f-22.Jun93) 14 packages in /hpux8/Maths/LinAlgebra (rlab-0.85 rlab.all-28.Jun.93) 12 packages in /hpux9/Gnu (readline-1.1 grep-2.0) 12 packages in /hpux9/Games (xpilot-3.0.0 xsokoban-3.2) 12 packages in /hpux8/Text (dvips-5.516 tr2latex-2.2a) 12 packages in /hpux8/Sysadmin (rpasd-2.0 expect-4.7.1) 12 packages in /hpux8/Languages (swi-1.6.17 gofer-2.28b) 11 packages in /hpux8/Maths/Gap (anupq-1.0 nq-1.0) 10 packages in /hpux9/X11R5/Misc (tkman-1.4 xlatex-3.3) 10 packages in /hpux8/NeuralNets (som_pak-1.2 snns-2.0) 8 packages in /hpux9/X11R5/Demos (xscreensaver-1.17 xscreensaver-1.16) 8 packages in /hpux9/Sysadmin (top-3.0 xmps-1.2) 8 packages in /hpux8/X11R4/Core (MITlib-4.00 appres-1.5) 8 packages in /hpux8/Physics (asa-1.33 asa-1.31) 7 packages in /hpux9/X11R5/Toolkits (Xew-1.4 tk-3.2) 7 packages in /hpux8/X11R5 (XR5src-5.23.part01 XR5built-5.23) 7 packages in /hpux8/Editors (mxedit-2.02 jetedit-1.22) 6 packages in /hpux9/Editors (emacs-19.16 mxedit-2.1) 5 packages in /hpux9/X11R5/Networking (xmosaic-1.2 xarchie-2.0.7) 5 packages in /hpux9/Text (bibview-2.0 bibview-1.4) 5 packages in /hpux9/Networking (xntp-3.1 ircII-2.29) 4 packages in /hpux9/X11R5/Core (twm-5.00 imake-5.01) 3 packages in /hpux9/Misc (eep-1.9 rplay-3.0.2) 3 packages in /hpux9/Languages (swi-1.6.18 f2c-93.04.28) 1 packages in /hpux9/Users (tcsh-6.04) ======================================= 484 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 Name: ftp.prz.tu-berlin.de Address: 130.149.62.68 Contents: Much of the Liverpool archive. Name: export.lcs.mit.edu Address: 18.24.0.12 Contents: The X Window System and contributed clients. Name: hpcvaaz.cv.hp.com Address: 15.255.72.15 Contents: X Window System libraries and utilities. Name: lut.fi Address: 157.24.10.8 Contents: Various in /pub/hpux and /pub/unix/hp-ux Name: nic.funet.fi Address: 128.214.6.100 Contents: Various in /pub/unix/arch/hpux Name: prep.ai.mit.edu Address: 18.71.0.38 Contents: The Free Software Foundation's GNU utilities, etc. Name: hybrid.irfu.se 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 in /pub. Name: geod.emr.ca Address: ? Contents: GNU stuff ported to HP-UX 8.x by Pierre Mathieu. -------------------------------------------------------------------------------- 1.9) Where can I get a "Demo CD" with software for HP-UX? HP is putting together a new version of LaserPro, which will be available shortly. -------------------------------------------------------------------------------- 1.10) HP-UX patch information and mailing list. In order to get HP-UX OS patches, you must be on HP software support. You can get them by calling the Response Center, or by using the "hpsl" tool on support.mayfield.hp.com. It will allow you to FTP patches, generally a subset of the full list. The Atlanta Response Center has a patch mail server: If you know the name of the patch needed, Email to hprc_patch@hprc.atl.hp.com with the subject of the message stated as "patch phkl_9999 rchandle" where phkl_9999 is the patch name, and rchandle is the Response Center system identifier. It will automatically be emailed back to you. A list of frequently accessed patches may be obtained at any time by emailing to hprc_patch@hprc.atl.hp.com with the subject of the message stated as "p-list rchandle" where rchandle is your Response Center system identifier. It will automatically be emailed back to you. Additionally, there is an HP-UX patch mailing list. Here is the announcement from Bart Muyzer <bartm@cv.ruu.nl>: This is the official announcement of the "HP Patch Descriptions Mailing List". In short, the purpose of the mailing list is this: 1. If somebody receives a patch from HP, he/she can post the *description* of that patch to the mailing list. 2. Other members now know that a patch exists and can ask HP for "patch xxxx" if they think they have a problem . 3. The patches itself are *never* posted!!!!!!!! 4. This list only exists as long as HP itself doesn't supply a list of available patches. To reach ALL MEMBERS of the list, send e-mail to: hpux-patch@cv.ruu.nl This is what you might want to do if you receive a new patch :-) To SUBSCRIBE, send e-mail to: hpux-patch-request@cv.ruu.nl PLEASE! Include your e-mail address in the message. Not all mailers generate proper return addresses. Problems, questions, suggestions and the like should go to this address too. To ease searching for a patch to a specific problem, I've started to write a set of tools which I loosely call "pltools". Currently, there's one script (written in PERL) called plfind, that searches through an unofficial list of patch descriptions according to user supplied queries. Updates to this list and to the tools are posted on a semi-regular base. Also, each new member of the list receives the current distribution upon subscription. The pltools-distribution is also available through anonymus FTP from ftp.csc.liv.ac.uk [138.253.42.172], directory /hpux/Sysadmin, file pltools-2.0.0.tar.Z. -------------------------------------------------------------------------------- 1.11) 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. [ Thanks to Bob Niland, late of HP, for this information. ] -------------------------------------------------------------------------------- 1.12) What are the known issues with porting BSD-based programs to HP-UX? Mike Peterson <system@alchemy.chem.utoronto.ca> periodically posts his list of BSD-HP tricks to comp.sys.hp. -------------------------------------------------------------------------------- 1.13) Who is this George Carter and how do I get rid of his posts? George Carter is an ex-HP employee who makes frequent postings to comp.sys.hp concerning HP business practices. If you wish to remove his posts and most of the related followups, then if you are running rn, put the following commands in your kill file: /George Carter/a:j /gcarter@infoserv.com/a:j -------------------------------------------------------------------------------- Subject: THIRD PARTY VENDORS -------------------------------------------------------------------------------- 2.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 <mcmorran@ll.mit.edu> for the info on RAM suppliers. ] -------------------------------------------------------------------------------- 2.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 -------------------------------------------------------------------------------- Subject: UTILITIES -------------------------------------------------------------------------------- 3.1) ASCII to Postscript converter. You can get an ASCII to Postscript converter from ftp.uu.net in the file /usenet/comp.sources.misc/volume10/a2ps3.Z. -------------------------------------------------------------------------------- 3.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) -------------------------------------------------------------------------------- 3.3) What is the status of the various gnu items on HP-UX? Pierre Mathieu <mathieu@geod.emr.ca> periodically posts a list to comp.sys.hp; the last revision is 1.4. -------------------------------------------------------------------------------- Subject: X WINDOW SYSTEM, OSF/MOTIF, AND HP-VUE -------------------------------------------------------------------------------- 4.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 hpcvaaz.cv.hp.com (15.255.72.15) in the directory 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. -------------------------------------------------------------------------------- 4.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. -------------------------------------------------------------------------------- 4.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. -------------------------------------------------------------------------------- 4.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 <string.h> 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 <stdio.h> main(argc, argv) int argc; int *argv[]; { if (argc != 2) exit(0); printf("%d\n", strlen(argv[1])); } [ Thanks to Tom Arons <arons@ash.eecs.ucdavis.edu> and John T. Beck, HP. ] -------------------------------------------------------------------------------- 4.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 <jms@spatial.com> for the Korn Shell information. ] -------------------------------------------------------------------------------- 4.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. -------------------------------------------------------------------------------- 4.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] -------------------------------------------------------------------------------- 4.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 under your ~/.vue directory (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] -------------------------------------------------------------------------------- 4.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 Alt<Key>F5 f.normalize "Move" _M Alt<Key>F7 f.move "Size" _S Alt<Key>F8 f.resize "Minimize" _n Alt<Key>F9 f.minimize "Maximize" _x Alt<Key>F10 f.maximize "Lower" _L Alt<Key>F3 f.lower no-label f.separator "Occupy..." _O Alt<Key>O f.workspace_presence "Occupy all" _a Alt Shift<Key>O f.occupy_all no-label f.separator "Remove from WS" _e Alt Shift <Key>F4 f.remove "Close" _C Alt<Key>F4 f.kill } And then add this resource: Vuewm*windowMenu: VueWindowMenu And restart the window manager. [ Thanks to Bill Bennett, HP] -------------------------------------------------------------------------------- 4.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. -------------------------------------------------------------------------------- 4.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. ] -------------------------------------------------------------------------------- 4.12) How do I disable HP-VUE? One solution is to create your own startup script in a file, say, ~/.Xsession, then modify your ~/.vueprofile so that ~/.Xsession gets executed AND MAKE SURE IT NEVER FALLS THROUGH TO VUE, i.e. use exec to start your script. You can use .vueprofile also to make sure your .cshrc is read, environment set etc. An example: #!/bin/csh # this may be redundant source $home/.cshrc if ( -f $HOME/.Xsession ) then # read clients from file exec /bin/sh $HOME/.Xsession else if ( -f $HOME/.Xdefaults ) then xrdb -merge .Xdefaults endif exec xterm endif # never reached !!! On a system wide basis, you could do something like this: In /usr/lib/X11/vue/Vuelogin/Xsession: -------------------------------------- # # determine startup mechanism... # if [ -x $HOME/.vuesession ]; then startup=$HOME/.vuesession else if [ -x $VUESESSION ]; then startup=$VUESESSION else ..... ------------------------------------------------------ Now if the file ~/.vuesession exists vuelogin will start this. ~/.vuesession: -------------- #!/bin/sh /usr/local/bin/xscreensaver -lock & /usr/bin/X11/xphoon & /usr/bin/X11/xbiff -geometry +0+0 & /usr/bin/X11/mwm & exec /usr/bin/X11/xterm -C -name "console" -geometry +0-0 ------------------------------------------------ When the last client exits the session terminates. [ Thanks to Andreas Stolcke and Neal Becker. ] -------------------------------------------------------------------------------- 4.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. ] -------------------------------------------------------------------------------- 4.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. ] -------------------------------------------------------------------------------- 4.15) How can I get an X client to come up in an alternate workspace? You can try: client -xrm "*workspaceList: <name>" [ Thanks to finger@rz.uni-karlsruhe.de] -------------------------------------------------------------------------------- Subject: OPERATING SYSTEM -------------------------------------------------------------------------------- 5.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. ] -------------------------------------------------------------------------------- 5.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. -------------------------------------------------------------------------------- 5.3) How do I safely remove software from my system? The _only_ safe way to remove HP software is to use /etc/rmfn. -------------------------------------------------------------------------------- 5.4) What's the scoop on HP-UX 9.0/9.01? HP-UX 9.0 and 9.01 have now officially released from HP. 9.0 for 700s was a transition release intended to support early shipments of 715 hardware. The 9.01 Release Notes state that 9.0 and 9.01 have the same API and ABI. They also state that 9.01 is required for the 725, 735/755, 747i w/VME, 745i w/EISA, 742rt and 742i, PA-RISC upgrades for 425s and t, 1G, 2G, and 525M add-on disks, and CRX48Z graphics. 9.01 also includes a software workaround for a low-probability bug in the PA7100 processor, support fast/wide SCSI, has a new version of IOMAP, and a new version of Imageview. -------------------------------------------------------------------------------- 5.5) How come HP-UX doesn't support NFS root access? HP-UX versions previous to 9.0/9.01 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.0/9.01 supports full NFS 4.1 functionality, including NFS root. -------------------------------------------------------------------------------- 5.6) Can I get HP-UX to try DNS ahead of NIS? if the address is the local node's IP add., then NIS or /etc/hosts is used because the IP is reachable and named is not running. if the address is the name server's IP add., if the address is reachable but named is not running, then NIS or /etc/hosts is used (the same reason) if the address is not reachable (eg the node is down) then at 7.0 NIS or /etc/hosts is used; at 8.0 resolution fails at 9.x resolution fails. It is not clear why "resolution fails" at 8.x and 9.x. If there are more than one IP address in resolv.conf, no NIS or /etc/hosts fallback will be used after all addresses are tried and failed. As for additional configuration ... the answer is NO, you can't get it to try NIS before DNS. [ Thanks to Jim O'Shea at the Atlanta RC for this information. ] [ Thanks to James Thomas, nmsu.edu for addition 9.x info. ] -------------------------------------------------------------------------------- 5.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. Kernel drivers send data to the diagnostic system when certain events, usually hw/sw problems, occur. The diagnostic daemons (DIAGMON, DEMLOG, MEMLOGP, DIAGINIT) log the data to these files. There is also a MEMLOG file in the same directories to which MEMLOGP logs memory errors. HP Support uses the logged data to diagnose problems and to predict hardware failure. If the LOGnnnn files are growing (other than creating a new 40 byte file each time the system reboots) then something is wrong with the system. Often what is wrong is that the diagnostics system was improperly installed. Check that the following files exist for each node: /etc/mknod /dev/config c 69 0x000000 /etc/mknod /dev/dmem c 27 0x000000 There are a number of other device files (see /system/CORE-DIAG/customize) but I don't believe they are needed for the logging aspect of diagnostics. If you examine the contents of the log files that may give a clue as to what's wrong. However, the output is intended for HP Support and factory consumption and may not be very intelligible to customers. To examine a log file: $ sysdiag DUI> logtool LOGTOOL> list log=nnnn LOGTOOL> exit DUI> exit where nnnn is the numeric part of the /usr/adm/diag/LOGnnnn file name. The utility logtool is safe to use as far as I know but don't run any other utilities at the DUI prompt--you could easily adversely affect your system. If you have a support contract I recommend you get them to review your log files. There is an extensive help command within sysdiag and logtool. If you want to turn off diagnostic logging just remove execution permission for the file /usr/diag/bin/DIAGINIT. Note that if you do this and your system has a problem later, not having the records logged to diagnostics by the kernel will hamper resolution of the problem. Existing log files can be deleted at the cost of losing the data they contain. The highest numbered log file is the active log file and should not be deleted. There is a sysdiag(1M) man page. As of 9.0 there is a diaginit(1M) man page which documents the various daemons. [ Thanks to Wayne Krone of HP. ] -------------------------------------------------------------------------------- 5.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". -------------------------------------------------------------------------------- 5.9) What are the known issues with HP-UX 8.07? abs() is defined in two places for C++, stdlib.h and math.h. the IDL includes do not support C++ (fixed with patch PHNE_0974). PostScript printing from Datebook (week or month) fails. Datebook "View Year" display font is goofy looking and doesn't line up. statd can hang when accessing Apollo objects (fixed with PHNE_0690). automounter crashes when -hosts is specified (fixed with PHNE_0936). virtual memory performance problems (fixed with PHKL_1065). -------------------------------------------------------------------------------- 5.10) 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 <jimr@maths.su.oz.au> for this submission. ] -------------------------------------------------------------------------------- 5.11) 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] -------------------------------------------------------------------------------- 5.12) 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. -------------------------------------------------------------------------------- 5.13) How come I have to hit return after control-d in the Korn shell? You need to set the "viraw" option. -------------------------------------------------------------------------------- 5.14) 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 <stuart@TIVOLI.COM>.] -------------------------------------------------------------------------------- 5.15) 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. -------------------------------------------------------------------------------- 5.16) 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 (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, pdg@cup.hp.com] -------------------------------------------------------------------------------- 5.17) How can I turn off quota checking? You can disable the quota binary from executing: chmod -x /usr/bin/quota This disables quotas for 8.x systems; for 9.x systems you need to also disable edquota: chmod -x /etc/edquota [Thanks to Eric Hamilton, hamilton@cup.hp.com] -------------------------------------------------------------------------------- 5.18) 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_2187. Various X11 problems have been reported including drawing problems and memory leaks. Get the latest X server (currently PHSS_2541). Various serious C compiler problems have been fixed with PHSS_2653. Memory leaks can occur and lock up a system; patch PHKL_2348 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 disable the dbc 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 You can also set a kernel parameter called "dbc_ceiling" that limits the growth of the buffer cache. Following is a script from Dave Lechtenberg of HP to do that: -------------- cut here ---------------- #!/bin/ksh # # Usage: setdbc dbc_ceiling_value_in_mbytes # # Sets dbc_ceiling value in kernel file (/hp-ux). You must be super-user # to run this command. After running this command, the system must be # rebooted to make changes take effect. # if [ $# = 0 ] then echo "Usage: $0 dbc_ceiling_value_in_mbytes" exit 1 fi whoami | grep -q root if [ $? -ne 0 ] then echo "Error: You must be super-user to run this command" exit 1 fi # max_mem is physical memory limit on the system max_mem=$(echo "mem_ptr/D" | adb /hp-ux /dev/kmem | awk '{ print $2 }' | sed '/^$/d') max_mem=$(expr $max_mem / 1048576) dbc_ceiling=$1 if [ $dbc_ceiling -gt $max_mem ] then echo "Error: dbc_ceiling cannot be greater than physical memory limit" exit 1 else dbc_ceiling=$(expr $dbc_ceiling "*" 256) hexval=$(echo $dbc_ceiling | awk '{printf "0x%x\n",$1}') echo "dbc_ceiling?W $hexval" | adb -w /hp-ux > /dev/null echo "The system must be rebooted to make changes take effect." fi ----------------- cut here --------------------- [ Thanks to various people, too numerous to mention. ] -------------------------------------------------------------------------------- 5.19) Why does chown behave differently at 9.01? 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] -------------------------------------------------------------------------------- 5.20) How can I track log files and core files? At 9.01, 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. -------------------------------------------------------------------------------- 5.21) 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. ] -------------------------------------------------------------------------------- 5.22)+ 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: COMPILERS AND LINKERS -------------------------------------------------------------------------------- 6.1) What's a P-FIXUP error? Several questions on comp.sys.hp lately 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). The linker is being helpful by pointing out a fatal error waiting to happen, as function pointers are different in the presence of shared libraries. A different fixup is needed to generate the kind of procedure label that can be called. This is explained under "Procedure Labels" in Chapter 7 of "Programming on HP-UX" (Part # B2355-90026 E0892) and at the end of "Expressions" in Chapter 1 of the Assembly Language Reference Manual (Part # 92432-90001 E0191). There are two ways to fix this : 1) Change the code generation to the equivalent of : .word P%foo or 2) Link the program using the "-a archive" linker option. The easiest way to do this is via the LDOPTS environment variable : setenv LDOPTS "-a archive" - or - LDOPTS="-a archive"; export LDOPTS The first fixes the problem directly, generating an R_DATA_PLABEL fixup which is unambiguous whether shared libraries are present or not. The second puts you back in time to the situation before shared libraries were added to HP-UX. Without shared libraries HP-UX drew no distinction between code addresses and procedure labels - an ambiguity that the P% fixup syntax resolves. The reason the linker can't just fix this situation is that there are cases where code addresses are implicitly or explicitly desired, cases that are part of the motivation for having an assembler to begin with. Unfortunately, in this case a message designed to be helpful to an errant assembly programmer is instead a symptom of an out-of-date code generator, and is too low-level to help the people seeing it. The other alternative (letting the program segmentation violate at runtime with no warning) would be more likely to result in the user blaming the Gnu code generator instead of HP's linker, but otherwise very little more satisfying. [thanks to Carl Burch, HP] --------------------------------------------------------------------------- 6.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. ... WARNINGS regcmp and regex are kept in /lib/libPW.a. Unfortunately, /lib/libPW.a also contains some functions that have the same names as functions contained in the default C library, /lib/libc.a. To prevent unexpected results due to these name conflicts, always search libc before searching libPW. This is done with the ld (or cc) command line option sequence -lc -lPW which satisifies all standard C functions from libc then searches libPW for the regcmp and regex functions (there is also an implied -lc following the explicit -lPW to satisfy any additional C functions required by regcmp and regex). User programs that use regcmp might run out of memory if regcmp is called iteratively without freeing vectors that are no longer required. [thanks to Andre Srinivasan, <andre@cs.pitt.edu>] -------------------------------------------------------------------------------- 6.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. -------------------------------------------------------------------------------- 6.4) How to I deal with "too many defines"? Use the "-Wp,-Hxxxxxxx" where xxxxxxxx is the number of bytes to add to cpp's table size. -------------------------------------------------------------------------------- 6.5) How come I get "_builtin_va_start" undefined when I build with gcc? The <varargs.h> and <stdarg.h> include files define va_start in terms of this function, which is built-in on the HP C compiler. 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 <varargs.h> #ifdef __hppa #undef va_start #define va_start(a) ((a)=(char *)&va_alist+4) #endif #include <stdarg.h> #ifdef __hppa #undef va_start #define va_start(a,b) ((a)=(va_list)&(b)) #endif For <varargs.h>, this replacement should always work. For <stdarg.h>, 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. ] -------------------------------------------------------------------------------- 6.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, Centerline. ] -------------------------------------------------------------------------------- Subject: HARDWARE AND PERIPHERALS -------------------------------------------------------------------------------- 7.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.) --------------------------------------------------------------------------------- 7.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. [ Thanks to Bob Niland, late of HP. ] --------------------------------------------------------------------------------- 7.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". -------------------------------------------------------------------------------- 7.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. -------------------------------------------------------------------------------- 7.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. -------------------------------------------------------------------------------- 7.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. ] -------------------------------------------------------------------------------- 7.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. ] -------------------------------------------------------------------------------- 7.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. -------------------------------------------------------------------------------- -- Greg Cagle | greg_cagle@mentorg.com | "Bar-har!" Mentor Graphics Corporation |