Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!milano!bigtex!pmafire!dave
From: dave@pmafire.UUCP (Dave Remien)
Newsgroups: comp.sys.hp
Subject: Re: Monitor 6.5
Keywords: monitor.o
Message-ID: <814@pmafire.UUCP>
Date: 13 Oct 89 00:55:51 GMT
References: <1306@oce-rd1.oce.nl> <101950055@hpcvlx.cv.hp.com>
Reply-To: dave@pmafire.UUCP (Dave Remien)
Distribution: na
Organization: WINCO, INEL, Idaho
Lines: 27

In article <101950055@hpcvlx.cv.hp.com> tomg@hpcvlx.cv.hp.com (Thomas J. Gilg) writes:
>Around here, I've always had to compile copies using our source license.
>I would assume SE's do the same thing.  I suspect `monitor` only works
>"perfectly" when compiled on the machine its to be used for, and maybe
>thats why a single /usr/contrib/bin/monitor copy isn't possible.
>Some of the things monitor can provide seem awfully kernel/system
>dependent.

Our SE gets it from the contrib tape, as a monitor.o, which is then
linked.

It'll usually tell you if it won't work with some new rev of your OS.

If you've got monitor for an 800, you'll notice that the older monitor
(from 2.1 land I think) works with the 3.0 and 3.1 kernels, but the
process (t) screen is often confused about the command line for a given
process. (It's amusing to see user root followed by =+<>"~$@#$% or so).

Haven't seen a later monitor for the 800. Haven't seen a contrib tape
for it either, now that I think about it. Wasn't the contrib tape for
800's supposed to be out about a year ago? 

Hmm, HP?
-- 
Dave Remien - WINCO Computer Eng. Group -{uunet | bigtex}!pmafire!dave- 
I certainly, absolutely, positively, don't speak for Westinghouse. And I
don't think I want to.			"Dave Barry for President"