Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!labrea!Portia!ruf
From: ruf@Portia.Stanford.EDU (Erik Ruf)
Newsgroups: comp.sys.hp
Subject: HPUX 6.5 problems (long)
Message-ID: <1725@Portia.Stanford.EDU>
Date: 20 Apr 89 22:04:50 GMT
Sender: Erik Ruf <ruf@Portia.stanford.edu>
Reply-To: ruf@portia.Stanford.EDU (Erik Ruf)
Organization: Stanford University
Lines: 59

We just installed HP-UX 6.5 on our cluster of 7 350's and one 360,
and have run into a couple snags:

1.  It appears that the "-tostop" parameter to stty is ignored.  We
    have found this to be an inconvenience because some X programs
    (xterm, gnuemacs) generate a "job attempted tty output - Stopped"
    message when run in the background.  This can be fixed by redirecting
    their output to /dev/null, but doing this on each invocation
    (an fixing each and every one of out users' scripts) is a real pain.   
    Why won't "stty -tostop" do this for us?  Any why is xterm generating
    terminal output anyway?  I don't see any output outside of the
    xterm window...(xterm bug?  pty bug?)

2.  We have the 6.2 X10 release and the 6.5 X11 release, and installed
    both on our 6.5 root volume.  We are experiencing some problems with
    X10 (random bus errors, and missing symbols in libc.a) and don't know
    what to do.  Is the 6.2 X10 code supported under 6.5?  If not, is
    some form of X10 supported?  We have nontrivial amounts of X10-specific
    code which won't be ported to X11 anytime soon.  

    As far as the missing symbols are concerned, we get them when
    compiling gnuemacs18.51 for X10.  The symbols "flag_68010" and
    "flag_fpa" (and 2 or 3 others I can't remember) are not found.  The
    only references to these symbols are in libc.a (not our applications)
    so it must be a bug.  How could a system with undefined symbols get
    released?  Doesn't HP do any integrity checking?

    Actually, flag_68010 was missing in 6.2 also, but we hacked in a 
    dummy assembler file defining it to be the word 0xFFFFFFFF and 
    got things to work.   Now that 4 symbols are missing in 6.5, I don't
    think this sort of fix is appropriate.

    Also, did something change in the domain IPC?  We used to be able to
    start X10 without having to specify DISPLAY explicitly, but now if 
    we don't, it dies.  Doesn't knowe what local:0 means (I think it
    used to use unix:0).

3.  Some of our users claim to be having problems with tset.  I haven't
    confirmed the myself, but wonder of anyone out in net-land has
    has problems with it.

4.  Doing remsh from one cnode to another gives "stty - operation not
    supported" errors and then runs the command anyway.  What's the
    problem?

Advice (expecially from HP) would be appreciated.  We've had so many
X10 problems that we've temporarily gone back to 6.2, but the 6.5
job control would be nice...  Does anyone else out there have X10
going under 6.5?  Does anyone else have 6.5 up at all?

Erik Ruf
Center for Integrated Systems
Stanford University

ruf@dolores.stanford.edu
...{decwrl,ucbvax}!dolores.stanford.edu!ruf