NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/sys/hp/14742

Internet Message Format | 1993-01-11 | 56.0 KB

Xref: sparky comp.sys.hp:14742 news.answers:5151
Newsgroups: comp.sys.hp,news.answers
Path: sparky!uunet!news.mentorg.com!dracula!gcagle
From: [e-mail] (Greg Cagle)
Subject: comp.sys.hp FAQ
Message-ID: <[e-mail]>
Sender: gcagle@dracula (Greg Cagle)
Approved: [e-mail]
Date: Mon, 11 Jan 1993 22:26:53 GMT
Reply-To: [e-mail]
Nntp-Posting-Host: dracula.mentorg.com
Organization: Mentor Graphics
Keywords: faq
Followup-To: comp.sys.hp
Lines: 1335

Archive-name: hp-faq
Last-modified: 1992/1/11
Version: 1.6

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 relating to Hewlett-Packard
computer systems running the HP-UX operating system on all platforms,
although the focus tends to be on the series 700 workstations. It
is posted approximately monthly.

Questions marked with a "+" are new to this issue, and questions with changes
since the last issue are marked by a "!".

If you would like to make any submissions or corrections to the FAQ,
contact Greg Cagle <[e-mail]>.

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:
------------------
FINDING INFORMATION
  1)   Where can I get a copy of this FAQ file?
  2)   Courses on HP-UX.
  3)   INTEREX, The International Association of HP Computer Users.
  4)   InterWorks, The International HP Workstation Users Group.
  5)   INTEREX HP Users Conference 1993.
  6)   InterWorks Conference 1993.
  7)   HP-UX publicly available software from InterWorks.
  8)!  Anonymous FTP Sites for HP-UX, and UNIX related software.
  9)   Where can I get a "Demo CD" with software for HP-UX?
 10)!  HP-UX patch availability, summary catalog, and mailing list.
 11)   How can I send mail to an "hpdesk" address?
 12)   What are the known issues with porting BSD based programs to HP-UX?
THIRD PARTY VENDORS
  1)   Third party vendors for RAM.
UTILITIES
  1)   ASCII to Postscript converter.
  2)   How do I make Perl on HP-UX?
  3)   What is the status of the various gnu items on HP-UX?
X WINDOW SYSTEM, OSF/MOTIF, AND HP-VUE
  1)   X11R4 Libraries (Athena, etc.) and utilities (imake, etc.).
  2)   How can I display an image on the root window with HP-VUE.
  3)!  How do I get a scroll bar on hpterms?
  4)   How can I put a title in my hpterm titlebar?
  5)   How come my hpterms keep going away by themselves?
  6)!  How come my HP X/Motif clients take a LONG time to display on a Sun?
OPERATING SYSTEM
  1)   Can I have filenames longer than 14 chars?
  2)   How can I tell what filesets have been loaded on my system?
  3)   How do I safely remove software from my system?
  4)   What's the scoop on HP-UX 9.0?
  5)   How come HP-UX doesn't support root NFS access?
  6)   Can I get HP-UX to try DNS before NIS?
  7)   How come the LOGnnnn files in /usr/adm keep growing and growing?
  8)   How come I can't lock mail or other files on a Sun?
  9)   What are the known issues with HP-UX 8.07?
 10)   Why are mail files in /usr/mail are owned by daemon instead of the
       recipient?
 11)   How can I tell if I need more than a 2-user license?
 12)+  How can I tell what patches are loaded in the kernel?
 13)+  How come I have to hit return after a control-d in the Korn shell?
 14)+  How do I boot into single user mode?
COMPILERS AND LINKERS
  1)   What's a P-FIXUP error mean?
  2)   Where is regcmp on HP-UX?
  3)   How come the default C compiler is brain dead?
HARDWARE AND PERIPHERALS
  1)   Are alternate keyboards available for HP workstations?
  2)!  How can I play audio CDs on an HP workstation?
  3)   How can I enable the LAN interface on a 700?
--------------------------------------------------------------------------------
Subject:  FINDING INFORMATION
--------------------------------------------------------------------------------
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
and news.answers newsgroups. It is archived on pit-manager.mit.edu
in the pub/usenet directory, and also on the InterWorks archive machine
(see below), in the comp.hp directory.
--------------------------------------------------------------------------------
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:  [phone]
--------------------------------------------------------------------------------
3)  INTEREX, The International Association of HP Computer Users.

INTEREX
585 Maude Court
Sunnyvale, CA  94088-3839 USA
--------------------------------------------------------------------------------
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
[phone]
E-Mail:  [e-mail]
--------------------------------------------------------------------------------
5)  INTEREX HP Users Conference 1993.

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)
[phone]
Telex:  4971527
Fax:  [phone]
--------------------------------------------------------------------------------
6)  InterWorks Conference 1993.

InterWorks and Hewlett-Packard's Workstation Systems Group invite all
HP Workstation System Users to InterWorks '93, which is scheduled for
April 25-28, 1993 at the Pointe Hotel on South Mountain in Phoenix, AZ.
This 3-day informational and educational forum boasts technical breakout
and focus group sessions, R&D directive sessions, tutorials, Q&A sessions,
a Tech Lab and Vendor Exhibit Show, Software Library, 1-on-1 desks, and pre
and post conference educational training seminars. It's an opportunity to
get answers to all workstation-related questions in a casual, informal
environment. For more information, contact Andrea Woloski, InterWorks
Manager at 508/436-5213 or e-mail Andrea at [e-mail].

(P.S.: Anyone interested in presenting a paper and receiving a reduced
conference registration fee should contact us promptly -- the Call for
Papers deadline is January 15!)
--------------------------------------------------------------------------------
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
  [phone], or via E-Mail at [e-mail].
  The following is provided by Dave Shaw, the InterWorks Librarian. This
  is the last full list he posted (#10) plus the latest updates (to #14).
  I've removed the detailed descriptions for space; see the README
  mentioned below for details. ]

The following is a list of new (or updated) entries (since my last posting),
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 the following is also available on a CD for
$75.00. For ordering information contact Carol Relph.

All the following 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.

     bytes
    810479     C-News.tar.Z
     80589     EasyEdit.tar.Z
    643301     Elm2.3.tar.Z
  18531320     GNUEmacs.tar.Z
    736543     GNUmake-3.62.tar.Z
    236715     GNUtar-1.10.tar.Z
    982443     ImageMagick.tar.Z
   2508135     MH.tar.Z
    226233     NNTP.tar.Z
         ?     Scheme
    117115     SOS.tar.Z
  12387119     TeX3.14.tar.Z
  27043840     TeXSRC.tar
   1620992     X11R4.stuff
  39399777     X11R5_source.tar.Z
    258885     acm.2.4.tar.Z
    282312     amd-5.2.tar.Z
    508089     amd5.3-beta1.tar.Z
    109753     arc-5.21e.hp.tar.Z
     91373     bzonec.hp.tar.Z
     52252     calls.tar.Z
     25898     capslock.Z
     37852     cproto.tar.Z
    342135     dtrek.tar.Z
    210935     ee.tar.Z
    197225     expect3.tar.Z
    167878     ezedit.tar.Z
    367653     flex-2.3.7.tar.Z
    122813     ftpd.tar.Z
  14010135     gcc-2.2.2.tar.Z
   3141289     ghostscript-2.4+fonts.hp.tar.Z
    163840     ghostview-1.3-hp300bin.tar
    235520     ghostview-1.3-hp700bin.tar
    172103     ghostview.tar.Z
    799047     gnuplot.tar.Z
   1342487     groff-1.06.tar.Z
   2105453     groff1.06_s300.tar.Z
   3007377     groff1.06_s700.tar.Z
               GUI_classic
     16288     hd.tar.Z
     12444     io.benchmark.tar.Z
     25481     lc.tar.Z
    165961     less177magic.tar.Z
     75707     lharc102a.tar.Z
     40968     lsof.tar.Z
    111139     mkid2.tar.Z
     16803     mkptypes.tar.Z
     36043     mmv.tar.Z
     54598     monitor_8.0x-s300.tar.Z
     74555     monitor_8.0x-s700.tar.Z
     56968     nenscript.tar.Z
   1448256     nethack3pl10.tar.Z
       960     nocore.c
     42152     ntalk.tar.Z
    578051     p2c-1.20.hpux.tar.Z
     74049     pang.tar.Z
    112671     patch-2.0.12u7.tar.Z
   3023333     pbmplus10dec91_tar.Z
   2596635     perl-4.035-HP700-8.05.tar.Z
   3102139     pine3.03.tar.Z
    479055     plp.hp.tar.Z
     85219     popper-1.7.HP.tar.Z
    479921     prog_dev_tools.tar.Z
   1504044     ray4.6_tar.Z
      1956     renice.tar.Z
      6781     resize-hp.c.Z
    177838     spider.tar.Z
     34498     spy.tar.Z
     13588     ssh-1.3.tar.Z
    545729     tcl6.2.tar.Z
    774801     tcsh-6.02.tar.Z
    114403     timed.tar.Z
    653844     tk1.4.tar.Z
    409001     tn3270.hpux.tar.Z
    154350     top-3.0.tar.Z
     32182     traceroute_1.17.tar.Z
    568713     transfig.tar.Z
    109985     unzip4.1.tar.Z
   2469994     urt-3.0_tar.Z
   1851392     urt-img.tar
    139653     x3270-1.2.tar.Z
   9518721     x8.0s300.tar.Z
  11358550     x8.0s800.tar.Z
  12356454     x8.0s700.tar.Z
     74773     xcalc_tar.Z
     41128     xcalendar.tar.Z
    180779     xcd.tar.Z
     33461     xdaliclock.tar.Z
      9609     xdiff.tar.Z
     40323     xdtree.tar.Z
    167194     xdvi-2.15.tar.Z
    539041     xfig.tar.Z
    988465     xfig-2.1.tar.Z
   1644635     xfract104_tar.Z
   1045507     xgo.tar.Z
     61385     xmahjon.hp.tar.Z
    140077     xmc.tar.Z
         ?     xmgr
    208953     xmps.1.01.tar.Z
     19682     xneko.hp700.bin.Z
   1240970     xntp.tar.Z
     71333     xperf.tar.Z
    762406     xntp.hp.tar.Z
    179658     xpilot.tar.Z
    357865     xrn-6.17.tar.Z
     77453     xstones.tar.Z
     39714     xswarm.2.3.tar.Z
     56846     xtalk.tar.Z
   2847307     xv-2.21.tar.Z
     80833     xwebster_motif_tar.Z
     33380     ytalk.tar.Z
      8431     zutils.tar.Z
--------------------------------------------------------------------------------
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 amount of stuff in directory /hpux.

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:   ?
Contents:  X11R4 libs, utilities, config files in X11R5, dvi2pcl in /pub.
--------------------------------------------------------------------------------
9) Where can I get a "Demo CD" with software for HP-UX?

HP has a free "Demo CD" called LaserPro that contains demo versions of several
software products for HP-UX in addition to some publicly available software
such as emacs, epoch, and xcd.  Call 1-800-323-1846 ext. 200, or in
Massachusetts call 1-800-847-1011 ext 200.
--------------------------------------------------------------------------------
10) HP-UX patch information and mailing list.

Here is the unofficial HP-UX patch summary list (last update, 12/14/92):

Summary of HP-UX 700 series OS patches.

HP-UX 8.0x
----------
PHSS_0369 - X server, superseded by PHSS_1060.
PHSS_0393 - 08.63 C compiler (8.05 only). This is superseded by
    the standard C compiler in 8.07.
PHSS_0417 - fixes for glbd and netncsrc (8.05 only).
PHCO_0505 - cron problems (8.05 only).
PHCO_0538 - memory use, DDS/MO, and more for fbackup/frecover.
    Supersedes PHCO_0472.
PHSS_0560 - bitmap CRX problems (8.05 only).
PHSS_0574 - X server, superseded by PHSS_1060.
PHNE_0690 - rpc.statd (8.05 and 8.07). This is a statd that doesn't
    bog the net trying to talk to Apollos.
PHNE_0724 - automounter that doesn't core dump when -hosts
    is used (8.07 only). Superseded by PHNE_0936.
PHNE_0734 - patch for SIO support. Allows selection of the trigger level
    on the serial port.
PHKL_0743 - kernel patch to "restore traditional vfork() semantics".
PHSS_0779 - Regularly-scheduled cumulative patch for Motif/X11
PHSS_0780 - Regularly-scheduled cumulative patch for Motif/X11
PHSS_0784 - X server, xterm.
PHSS_0788 - S700/Performance enhancement for CRX-24Z shared driver.
PHSS_0803 - 08.56 linker (8.05 and 8.07).
PHSS_0806 - X server, superseded by PHSS_1060.
PHNE_0818 - fix for rpc.lockd to avoid crashing and multiple locks.
PHKL_0836 - kernel patch that allows the automounter to be restarted
    without hanging (8.07 only). Superseded by PHKL_1102.
PHKL_0876 - kernel patch that increases the number of NFS request
    buffers. Circumvents a large proportion of automounter hangs.
    Superseded by PHKL_1102.
PHNE_0899 - Latest update to TTY subsystem.
PHKL_0900 - virtual memory performance patch. Superseded by PHKL_1065.
PHKL_0901 - GCLOCK_BLOCKSIG ioctl can cause graphics process hang.
PHKL_0902 - GCLOCK_BLOCKSIG ioctl can cause graphics process hang.
PHSS_0904 - Another X server. Superseded by PHSS_1060.
PHNE_0936 - automounter, supersedes PHNE_0724.
PHKL_0942 - NFS kernel patch, supersedes PHKL_0836, PHKL_0876. Superseded by
    PHKL_1102.
PHSS_0945 - fix for data corruption problem on internal 660 and 1.3 disks.
PHNE_0974 - patch for C++ IDL includes.
PHNE_0985 - fixes to the tty subsystem.
PHNE_1009 - Fixes socket/port disappearance
PHNE_1010 - on -e hangs
PHNE_1044 - fixes sendmail problems with long address lists.
PHSS_1060 - Latest X server. Supersedes all previous ones.
PHKL_1065 - supersedes PHKL_0900, adds fix for "node lockup" problem.
PHNE_1070 - lan2 driver fixes for udp problems.
PHKL_1102 - NFS rollup patch. Supersedes PHKL_0836, PHKL_0876, PHKL_0942.
PHCO_1131 - fixes for the pathname,memory,SCSI magtape related problems
PHCO_1138 - elm fixes. 8.05 and earlier only.
PHSS_1183 - Motif patch.
PHKL_1193 - kernel DMEM protection fault, file locking, nfs, diskless
PHKL_1194 - SDS fixes for C2425 disk arrays.
PHNE_1222 - ypmatch case insensitive matching.
PHSS_1263 - various Omniback fixes.
PHSS_1231 - X server.
PHNE_1268 - EISA X25 card crash fix.
PHSS_1301 - scopeux patch.
PHSS_1304 - more scopeux patches.
PHSS_1305 - X server.
PHNE_1330 - rpc.statd, update to PHNE_0690.
PHSS_1331 - X server.
PHSS_1334 - libsbrr.a and .sl.
PHSS_1342 - X server.
PHC0_1343 - curses patch to fix typeahead.
PHSS_1349 - Starbase patch for CRX24[Z]
PHSS_1354 - Starbase patch for device independent polyhedron_with_data.
PHNE_1360 - ypbind that only accepts ypset from local host
PHSS_1378 - Motif 1.1.2 and X patches.
PHCO_1423 - avoid unnecessary stat calls by ls.
PHSS_1495 - various VUE patches.
PHCO_1502 - fix for grep -f/-x.
PHNE_1525 - gated EGP update packet fix.
PHSS_1589 - glance/MI patch, conflict with Oracle.
PHSS_1590 - same?
PHCO_1611 - fbackup/frecover patch, supersedes PHCO_1131.
PHKL_1602 - NFS mega-patch. Supersedes: PHKL_0736,PHKL_0836,PHKL_0876,PHKL_0942,PHKL_1102.
PHCO_1624 - curses 8-bit character fix.
PHSS_1628 - xterm inverse video problem. Supersedes PHSS_0784.
PHSS_1634 - TVRX fix for SDRC.
PHKL_1637 - NFS memory leak patch for 8.05.
PHSS_1638 - Motif 1.2 internationalization locale problem.
PHKL_1649 - absolute cursor position on ITE fix.
PHSS_1651 - more scope ux patches.
PHNE_1654 - X.400 megapatch.
PHSS_1657 - Xt problems. Replaces PHSS_1510, requires PHSS_0956.
PHSS_1660 - hpterm periodic patch. Replaces PHSS_1186, PHSS_0529.
PHCO_1666 - ksh loop when SIGHUP trapped and window closed.
PHSS_1679 - xterm periodic patch. Replaces PHSS_1628, PHSS_0784.
PHNE_1682 - X.400 fixes.
PHKL_1696 - Diskless cluster panic "Premature end of packet"
PHNE_1710 - x.29 fixes.
PHSS_1727 - phigs/PVRX fix.

9.0/9.01 patches
----------------
PHCO_1539 - Bourne shell problem with Kanji.
PHSS_1627 - C compiler fixes (includes fixes to optimizer).
PHSS_1644 - NLIO fixes.
PHCO_1689 - getpwnam problem with NIS-exluded names.
PHSS_1699 - Timber graphics core dump.
PHKL_1745 - diskless STREAMS support.

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.
As of 1/11/93, the following patches are available on 192.6.148.19 or
support.mayfield.hp.com:

PHCO_1790 PHNE_1492 PHSS_1777 PHNE_1707 PHCO_1013 PHSS_1819 PHCO_1792
PHSS_1495 PHSS_0961 PHSS_0417 PHKL_1017 PHCO_1611 PHSS_1628 PHKL_1147
PHSS_1508 PHCO_1558 PHNE_1029 PHSS_0803 PHNE_1239 PHNE_1074 PHNE_0723
PHNE_0550 PHNE_0479 PHNE_0469 PHNE_0437 PHCO_1423 PHNE_1010 PHKL_1193
PHNE_0818 PHNE_1070 PHNE_1330 PHNE_1009 PHNE_0936 PHKL_1011 PHSS_1305
PHSS_0560 PHNE_0899 PHKL_0901 PHKL_0743 PHCO_0505 PHKL_1065 PHKL_0902
PHSS_1819

Additionally, there is an HP-UX patch mailing list. Here is the announcement
from Bart Muyzer <[e-mail]>:

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 subscribe, send e-mail to:
    [e-mail]
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 reach all members of the list, send e-mail to:
    [e-mail]
This is what you might want to do if you receive a new patch :-)

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'a one perl-script,
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.
--------------------------------------------------------------------------------
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:
  [e-mail]

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 <[e-mail]> for this information. ]
--------------------------------------------------------------------------------
12) What are the known issues with porting BSD-based programs to HP-UX?

Mike Peterson <[e-mail]> periodically posts
his list of BSD-HP tricks to comp.sys.hp.
--------------------------------------------------------------------------------
Subject:  THIRD PARTY VENDORS
--------------------------------------------------------------------------------
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
[phone]                     [phone]
[phone]

Concorde Technologies              Dataram
7966 Arjons Dr. B-201              PO Box 7528
San Diego, CA 92126                Princeton, NJ 08543-7528
[phone]                     (800) DATARAM
[phone]                     [phone]

Digitial Micronics                 Eventide
2075 Corte Del Nogal               1 Alsan Way
Unit N                             Little Ferry, NJ 07643
Carlsbad, CA 92009                 [phone]

Helios Systems                     Herstal Automation
1996 Lundy Ave                     3171 West Twelve Mile Rd.
San Jose, CA 95131                 Berkley, MI 48072
[phone]                     [phone]
[phone]

IEM                                Infotek Systems
P.O. Box 1889                      625 South Lincoln
Fort Collins, CO 80522             Suite 204
[phone]                     Steamboat Springs, CO 80487
[phone]                     [phone]

Intelligent Interfaces             ISA Ltd
P.O. Box 1486                      1-1-5 Sekiguchi
Stone Mountain, GA 30086-1486      Bunkyo-Ku
[phone]                     Tokyo 112 Japan
                                   81-3 (5261) 1160
                                   US Office (Texas)
                                   [phone]

Kelly Computer Systems             Kingston Technology Corporation
1101 San Antonio Rd.               17600 Newhope Street
Mountain View, CA 94043            Fountain Valley, CA 92708
[phone]                     [phone]

Martech                            Merida Systems
1151 W. Valley Blvd.               [phone]
Alhambra, CA 91803-2493
[phone]
[phone]

Newport Digital                    R Squared
14731 Franklin Avenue              11211 E. Arapahoe Rd., Suite 200
Suite A                            Englewood, CO 80112
Tustin, CA 92680                   [phone]
[phone]                     [phone]

[ Thanks to Roy McMorran <[e-mail]> for the info on RAM suppliers. ]
--------------------------------------------------------------------------------
Subject:  UTILITIES
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
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)  What is the status of the various gnu items on HP-UX?

Here's a summary for HP-UX 8.07 from Pierre Mathieu <[e-mail]>:

This is revision 1.1 of the list.

For those who may be interested in getting the GNU products for the
HP9000 Series 700 systems HP-UX 8.07 (and possibly other OS version 8.0x),
here is a list of the results I (and others) have obtained with the
packages available at prep.ai.mit.edu.

All of the results are based on compilation with GCC 2.3.1 and
not on the use of the HP C compiler. A section is included
in the list for applications that did not compile with
GCC but did with HP C.

The last part of the listing contains the applications I can't get to
compile. If you got them to compile with GCC 2.3.1 and can send
me fixes, I'll include them in this list.

Note: To compile GCC 2.3.1 with debugging support, you must have the
      UTAH GAS 1.36 version from jaguar.cs.utah.edu: pa-gas.u3.tar.Z.
      It is also recommended that you get the GCC 2.3.1 package
      gcc-2.3.1.u2.tar.Z from jaguar.

Note also that for most of the products that fail to compile below, the fault
lies with the compiled package and not with GCC 2.3.1. Some of these packages
are getting a bit out of date. ;-)

Furthermore, note that all the packages tested below are available from
my archive site at geod.emr.ca (132.156.33.33) in the /pub/gnu directory
and in the /pub/hp directory for HP specific items including jaguar
packages and HP specific patch kits.


GNU products that compile fine:
------------------------------
bison-1.19
c-torture-test     (a few warnings, but nothing serious)
cpio-2.1
diff-2.0
emacs-18.58
emacs-18.59        (had troubles with installation although it compiles OK)
fileutils-3.4
find-3.7
flex-2.3.7
fontutils-0.6
gas-1.36.utah      (from jaguar.cs.utah.edu pa-gas.u3.tar.Z)
gcc-2.3.1          (from jaguar.cs.utah.edu gcc-2.3.1.u2.tar.Z)
gdb-4.6            (with pa-gdb-4.6.tar.Z patches from jaguar.cs.utah.edu)
ghostscript-2.5.2  (and fonts)
ghostview-1.4
gmp-1.2
gnugo-1.1
gptx-0.2
grep-1.6
groff-1.06
hello-1.1
indent-1.6
ispell-eeadfa-p0+9 (available from our site geod.emr.ca in /pub/hp)
libg++-2.2         (with Bart Muyzer's ([e-mail]) patches from
                    /pub/hp/libg++-2.2.patches.shar in our site geod.emr.ca)
patch-2.0.12u8
perl-4.035
sed-1.11
shellutils-1.8
tar-1.10
tar-1.11           (executable is buggy; dumps a lot of stuff to screen)
termcap-1.1
texi2roff-2.0
texinfo-2.16
textutils-1.3
xinfo-1.01.01

GNU products that compile fine with notes:
-----------------------------------------
1) rcs-5.6

Paul Eggert ([e-mail]) adds:
"Note that you must set has_mmap to 0 manually in
rcs/src/conf.h to work around a kernel bug in HP-UX 8.07 that
causes the kernel to crash whenever you use RCS on NFSed files.
HP patch PHKL_0942 fixes this kernel bug."

GNU products that don't support (yet?) HP9000/700:
-------------------------------------------------
dld-3.2.3
gas-1.38.1
gdb-4.7
glibc-1.05

GNU products that don't compile because another product doesn't:
---------------------------------------------------------------
autoconf-1.2    (m4-1.0)

GNU products not yet examined (don't have time right now):
---------------------------------------------------------
ae
f2c-3.2.90
finger-1.37
gnuchess-4.0
gnuplot-3.2
ms-0.06
mtools-2.0.7
nihcl-2.2
smalltalk-1.1.1
tile-forth-2.1
xboard-2.0

GNU products not examined (and I don't plan to):
-----------------------------------------------
button.3.00
dirent
elvis-1.6       (fine on PC; don't care on HP)
fax-3.2.1       (don't have a FAX modem)
fgrep-1.1       (too old to be interesting)
iostream-0.50
ispell-2.0.02   (use ispell-eeadfa-p0+9 instead)
malloc-0.1
oleo-0.03.2     (too old to be interesting)
readline-1.1    (GDB 4.6 readline lib compiles just fine)
uucp-1.03       (UUCP on HP is Honey-Danber)
vh-1.3

Other non-GNU products that compile:
-----------------------------------

GNU products that don't compile with GCC 2.3.1 but do with HP C:
---------------------------------------------------------------
bash-1.12
bc-1.02
binutils-2.0
m4-1.0
screen-3.2b
time-1.4
tput-1.0

GNU products that compile with easy fixes:
-----------------------------------------
cperf-2.1
cvs-1.3
make-3.62

GNU products that don't compile:
-------------------------------
A - getopt problems:
1) bash-1.12
2) bc-1.02
3) m4-1.0
4) tput-1.0

B - Others:

1) binutils-2.0
2) gawk-2.14
3) gdbm-1.5
4) graphics-0.17
5) screen-3.2b
6) time-1.4
--------------------------------------------------------------------------------
Subject:  X WINDOW SYSTEM, OSF/MOTIF, AND HP-VUE
--------------------------------------------------------------------------------
1)  X11R4 Libraries (Athena, etc.) and utilities (imake, etc.).

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.
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
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).
--------------------------------------------------------------------------------
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]);
}

[ Thanks to Tom Arons <[e-mail]> for this item. ]
--------------------------------------------------------------------------------
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 <[e-mail]> for the Korn Shell information. ]
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
Subject:  OPERATING SYSTEM
--------------------------------------------------------------------------------
1)  Can I have filenames longer than 14 chars?

Yes, change to long filenames using /etc/convertfs. You can't
go back, though.
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
3) How do I safely remove software from my system?

The _only_ safe way to remove HP software is to use /etc/rmfn.
--------------------------------------------------------------------------------
4) What's the scoop on HP-UX 9.0?

[ Thanks to Larry Thompson for this information ]

|> Here's some information I promised awhile back that I finally got approved
|> through channels (probably because most of this is known by now). This
|> should not be taken as the final OFFICAL statement on what the differences
|> are with 9.0 or all of the differences between the s700 and s800. I think
|> this is fairly good list of features.
|>
|> This was written by the folks who did s700. You will probably notice a slight
|> favoritism toward the s700 features.
|>
|> Anyway I hope someone finds this interesting. (Please don't mail me asking
|> for any follow up info. Getting permission to post this was hard enough.)
|>
|> Oh yeah,
|>
|> #include <STD_DISLAIMERS> :-)
|>
|> This is not an offical statement by the Hewlett-Packard Company. It is posted
|> with permission from management for the information of our users who read this
|> notes group and who's inputs and comments we value greatly.
|>
|>                               HP-UX 9.0 Differences
|>
|> -------------------------------------------------------------------------------
|>
|> Major S700/9.0 (IF3) kernel features not in S800/9.0MU
|>
|>      SW disk striping
|>      Industry standard I/O drivers
|>      AT&T style configuration
|>      DUX:  There is no diskless capability on 800/9.0MU.  DUX is supported on
|>            S700, S400 and S300 only.  A S700 will not boot a S800 and a S800
|>            will not boot a S700, S400 or S300.  Note: DUX is not MP-safe.
|>      Graphics support:(bitmap displays, etc.)  Graphics is not supported
|>            on S800/9.0MU. HP 9000 models 835,845 have been obsoleted.  Note:
|>            MP-safe graphics does not yet exist.
|>      OSF AES Level2 compliant:  mmap, iomap,vfork, poll(2) and Berkeley timer
|>            commands in S700/9.0 but not in S800/9.0MU.
|>      Memory mapped Files:  mmap is only supported in S700/9.0. There are
|>            several calls in libc for memory mapping. Using mmap in S700/9.0
|>            wipes out binary compatibility to S800/9.0MU.  Note: MP-safe mmap
|>            does not yet exist.
|>      iomap(7): iomap is an OSF1 feature and an administrative difference that
|>            is supported in the S700/9.0 but is not supported in the S800/9.0MU.
|>            It doesn't effect binary compatibility.
|>      vfork:  vfork is turned on, it was turned off in 8.0.  If used, it will
|>            provide greater performance on the S700/9.0. However, using
|>            vfork in the S700/9.0 wipes out binary
|>            compatibility with the S800/9.0MU.
|>      poll(2): The use of poll will wipe out binary compatibility between the
|>            S700/9.0 and the S800/9.0MU. NOTE: poll will be available with the
|>            S800 Streams product on the 9.0 HTR, Q1 '93.
|>      Berkeley Timers:  New command formats to obtain time-of-day, date, etc.
|>            Code using the new command format won't work on S800/9.0MU, only on
|>            the S700/9.0.
|>      Fast Symlinks: Fast Symlinks are an OSF1 feature providing greater
|>            performance on the S700/9.0.  It is an administrative difference
|>            that is not supported on the S800/9.0MU. It doesn't effect binary
|>            compatibility.
|>      User Virtual Address Space = 1.9GB:  The default user virtual address
|>            space on both the S700/9.0 and S800/9.0MU is 900MB (up from 640MB in
|>            the 8.x releases).  However, there is  new linker option, on the
|>            S700/9.0 only, that expands the user virtual address space to 1.9GB.
|>      Dynamic Buffer Cache: Dynamic buffer cache is a performance feature and an
|>            administrative difference that will not effect binary compatibility.
|>      SCSI immediate report enabled:  A S700/9.0 disk performance feature that
|>            is not supported in the S800/9.0MU.  It will effect binary
|>            compatibility.
|>      EISA I/O,VME I/O support
|>      Advise:  ISU product only for Apollo Domain
|>
|> Major S800/9.0MU kernel features not in S700/9.0
|>
|>      LVM
|>      Powerfail
|>      MP
|>      SVID3 features(labelit, sadp, sysdef, volcopy)
|>      Disk mirroring (datapair)
|>      Switchover
|>      SAR
|>      Hard disk partitions
|>      BSD style config (uxgen)
|>      Autoconfig
|>      mpctl (MP system call)
|>      Remote access port
|>      DBsend/DBreceive
|>      Async disk I/O (Sybase)
|>      Fairshare scheduler
|>      AT&T specials (e.g. datakit)
|>      HP-FL
|>      NIO, CIO HP-IB
|>      DTC
|>      CS-80 Disk support
|> -------------------------------------------------------------------------------
|>
|> Other 9.0 and 9.0MU differences besides kernel features.
|>
|> New Math libraries:  libm, libM, libcl and libvec all have new versions, PA1.1.
|>           The old versions, PA1.0, are still supported.  PA1.1 gives more
|>           precise results than PA1.0(a.k.a. "different results in some cases").
|>           Plus, the system defaults are different:
|>           S700/9.0 has PA1.1 as a default with PA1.0 as an option and
|>           S800/9.0MU has PA1.0 as the default with PA1.1 as the option.
|>           If reproducing results in applications from release to release is
|>           more important than performance, then PA1.0 should be used.
|>
|> cksum(1) utility: The CRC checksum polynomial has changed in both 9.0 and 9.0MU.
|>           This results in a different number than calculated with older
|>           versions.  Any application using cksum may be impacted.  Also the
|>           cksum output is now - checksum, number of octets and pathname to
|>           standard output.  In previous versions, the number of blocks were
|>           reported, not the number of octets.  Any application using the number
|>           of blocks that was output along with the checksum will be impacted.
|>           Blocks = # of Octets/512(Block size).
|>
|> X11 R5 Server:   The X11 R5 server is only supported on the S700 (also S300
|>           & S400).  The X11 R5 server is not supported on S800 systems.
|>
|>
|> -------------------------------------------------------------------------------
|>
|> HP-UX kernel release stream comparisons
|> ========================================
|>
|>                 WSBU                            GSY
|>                 ----                            ---
|> Design
|> center:         Technical workload              Commercial workload
|>                   tuning                          tuning
|>
|>                 Small # of                      Large # of
|>                 processes                       processes
|>
|>                 Medium/large processes          Small/medium size processes
|>
|>                 I/O & interactive               OLTP
|>                   performance                     performance
|>
|>                 Low-end size                    High-end scalability
|>                 Graphical EOU                   Terminal EOU
|>
|>                 Very sensitive to               Less sensitive to
|>                  support costs (high volume)     support costs (moderate vol)
|>
|>                 Technical applications          Commercial applications
|>                   & non-OLTP commercial
|>
|>                 Peer-to-peer client-server      PC-to-mainframe client-server
--------------------------------------------------------------------------------
5) How come HP-UX doesn't support NFS root access?

HP-UX versions previous to 9.0 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 supports full NFS 4.1 functionality, including NFS root.
--------------------------------------------------------------------------------
6) Can I get HP-UX to try DNS ahead of NIS?

This is the "standard" answer given from the Response Center:

     If there is only one IP address in resolv.conf and
        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.

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.

In other word, if they only configure one IP address in resolv.conf and are
running 7.0, they should be ok.

As for additional configuration ... the answer is NO, you can't get it
to try NIS before DNS etc ...

[ Thanks to Jim O'Shea at the Atlanta RC for this information. ]
--------------------------------------------------------------------------------
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. ]
--------------------------------------------------------------------------------
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".
--------------------------------------------------------------------------------
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).
--------------------------------------------------------------------------------
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 <[e-mail]> for this submission. ]
--------------------------------------------------------------------------------
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]
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
13) How come I have to hit return after control-d in the Korn shell?

You need to set the "viraw" option.
--------------------------------------------------------------------------------
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 <[e-mail]>.]
--------------------------------------------------------------------------------
Subject:  COMPILERS AND LINKERS
--------------------------------------------------------------------------------
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]
---------------------------------------------------------------------------
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, <[e-mail]>]
--------------------------------------------------------------------------------
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:  HARDWARE AND PERIPHERALS
--------------------------------------------------------------------------------
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.)
---------------------------------------------------------------------------------
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 DAT tape."

Bob Niland of HP has volunteered to supply xcd via email. To get it from him:

1. To supply Bob with at least one known-valid email address.
   Don't rely on the return path - it often fails.

2. To indicate whether you want the MC68000 (Series 300/400) and/or
   PA-RISC (Series 700) version of xcd.  xcd does not work on Series 800,
   due to lack of SCSI pass-thru and low-level HP-IB command capability.

3. Make sure your mail path won't choke on 200+Kbyte shar files.

Note that source is not available.

For readers in Europe: XCD is available as a contributed application
on the "LaserPro" cdrom disc.

Copies can be obtained freely through your local HP Sales office.
Ask for the "LPO" department.

[ Thanks to Bob Niland of HP. ]
---------------------------------------------------------------------------------
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".

--
Greg Cagle | [e-mail]
Mentor Graphics Corporation