Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!mel.dit.csiro.au!yarra!bacchus!matt From: matt@bacchus.esa.oz (Matt Atterbury) Newsgroups: comp.sys.apollo Subject: Re: Problem with bash from an xterm on Apollo Message-ID: Date: 16 Oct 90 00:10:31 GMT References: <1990Oct11.200712.12821@medtron.medtronic.com> <1917@tuvie> Sender: matt@bacchus.esa.oz Organization: Expert Solutions Australia. Lines: 35 In-reply-to: mike@tuvie's message of 15 Oct 90 13:24:08 GMT In article <1917@tuvie> mike@tuvie (Inst.f.Techn.Informatik) writes: In article matt@bacchus.esa.oz (Matt Atterbury) writes: ... No, it is not unnecessarily harsh on Apollo! I'm using the /bin/csh - so it seems to cause problems not only with bash!!! It's just like APollo's usual reaction - our OS is OK, your program is broken !!! If you believe HP/Apollo, just about any program there is, is broken !!! --- Describe the set-up completely. I haven't seen any articles in which you explain exactly what it is. I only saw your latest article which was a follow-up to a follow-up, and in that no mention of /bin/csh was made. Our set-up here is: Apollo DN3500 SR10.2, connected via Ethernet to SONY 1750 BSD4.3. Log onto Apollo (via DM pad, or xterm, or dial-up), rlogin to Sony, run bash on Sony and you lose output, but run /bin/sh or /bin/csh on the Sony and all is OK. Makes no difference what shell you are running on the Apollo. Now, my initial reaction was "gee, something's funny with bash!", not "this Apollo stuff is giving me the shits!". If you can describe what your set-up is, maybe we can all try to work out a possible cause + solution. -- ------------------------------------------------------------------------------- Matt Atterbury [matt@bacchus.esa.oz] Expert Solutions Australia, Melbourne UUCP: ...!uunet!munnari!matt@bacchus.esa.oz "klaatu barada nikto" ARPA: matt%bacchus.esa.oz.AU@uunet.UU.NET "life? don't talk to me about life!"