HDTenEightyP/NetNews huggingface dataset:
From: dog.ee.lbl.gov!network.ucsd.edu!sdd.hp.com!caen!destroyer!ubc-cs!unixg.ubc.ca!physics.ubc.ca!unruh@ucbvax.Berkeley.EDU  (William Unruh)
Subject: Update: monitors on 2500
Organization: University of British Columbia, Vancouver, B.C., Canada
Distribution: fj
Date: Fri, 14 Aug 1992 23:49:54 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

As I stated earlier the monitors on my 2500 ( 15") blew. After ttrying
to repare them I went to the Surplus equip store on campus here and
found they had some 19" monitors from some old 3500 on sale- no cables.
They work! And the cable that worked was a cheap $6.00 IBM Monochrome
monitor extention cable. They were a bit dim, but after some
trepedation, I tweaked the sub threshold(?)  pot inside a tiny amount
and now they are fine. How does the 2500 Know tht there is a high res
monitor attached to the system rather than a 1024X800? ( What weas
interesting was that if I drove it via a Sun Mono cable, It would come
up in low res mode- Teh sun cable has 2-7-8 shorted together. Do they as
someone suggested use one of the lines (2or 7) to tell which monitor it
is?
And why did the monitor sync at low res since both the hor and vert are
rather different between the two. Are they really multisyncs in
disguise, or would they burn out driven at the low res mode?
Bill Unruh
unruh@physics.ubc.ca
Newsgroups: fj.mail-lists.apollo
From: gregp@greece.seri.philips.nl (Greg Pritchett)
Subject: Re: Node ID from C
Originator: news@phcoms.seri.philips.nl
Reply-To: gregp@scs.philips.nl
Organization: SERI-CEN Network Services, Philips C&P, Eindhoven, The Netherlands
X-Newsreader: Tin 1.1 PL4
Distribution: fj
Date: Mon, 17 Aug 1992 07:40:20 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

I have used the following in the past. Unfortunately, it's not
documented ( or supported ! ) . It used to work on a flat 10.0
and I've just tested it on a 10.3.5 machine , so I guess it will
work on your 10.3. Hope this helps . . . 

extern std_$call void msg_$get_my_node();

main ()

{
long node_id;

msg_$get_my_node ( node_id );

printf ("Node id %X\n", node_id );

}

==============================================================================
|                                                                            |
|  Greg Pritchett                     _/_/_/_/ _/_/_/_/ _/_/_/_/  _/_/_/_/   |
|  Central Systems Support Group     _/       _/       _/        _/          |
|  Philips Semiconductors Ltd       _/       _/_/_/_/ _/_/_/_/  _/  _/_/     |
|  Southampton                     _/             _/       _/  _/    _/      |
|  United Kingdom                 _/_/_/_/ _/_/_/_/ _/_/_/_/  _/_/_/_/       |
|  email : Being changed at the moment                                       |
|  tel   : +44 703 316385                                                    |
|  fax   : +44 703 316305                                                    |
|                                                                            |
==============================================================================
Newsgroups: fj.mail-lists.apollo
From: David Krowitz <krowitz@quake.mit.edu>
        cs.utexas.edu!torn!cunews!nrcnet0!bnrgate!bwdls61!bnr.ca!awhitton@uunet.uu.net
Subject: Re: DN10K's for sale
Organization: Electrotechnical Laboratory, Tsukuba Science City
Distribution: fj
Date: Sat, 22 Aug 1992 15:28:20 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

Huh? $5000 for a DN10K to HP750 trade in? They told us at
an InterWorks board meee
meeting that they were going to offer a 40% discount on a
HP750 to DN10K owners, plus you got to keep the DN10K so 
that you could make a gradual transition to the new machine.

What gives?

== Dave Krowitz
Newsgroups: fj.mail-lists.apollo
From: David Krowitz <krowitz@quake.mit.edu>
        tulane!darwin.sura.net!zaphod.mps.ohio-state.edu!rphroy!caen!news-server!disser@ames.arc.nasa.gov
Subject: Re:  Unable to open a stream to the SIO line
Organization: Electrotechnical Laboratory, Tsukuba Science City
Distribution: fj
Date: Sat, 22 Aug 1992 15:26:07 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

Sigh! Try the command "/etc/mkdev /dev sio" to rebuild
your /dev/sio and /dev/tty devices. They get hung sometimes
(perhaps they are closed improperly, I don't know, and I'm
*real* tired of having to manually clear the errors).

== Dave Krowitz
Newsgroups: fj.mail-lists.apollo
From: van-bc!nwnexus!ole!ssc!eskimo!lorc!lowen@uunet.uu.net  (Lamar Owen)
Subject: FAQ??  Where can get...
Organization: LORC Enterprises
Distribution: fj
Date: Mon, 10 Aug 1992 19:42:33 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

Subject says it: I'm looking for a copy of the comp.sys.apollo FAQ list.  
Where is this thing archived?  Available via e-mail?  Who had been keeping it
up?  


--

Lamar Owen, Systems Consultant, GE Lighting Systems, Hendersonville, NC
***********************************************************************
 Opinions expressed herein are the author's and do not reflect policy
   or opinions of the General Electric Company or its subsidiaries.
***********************************************************************
Newsgroups: fj.mail-lists.apollo
From: thompson@pan.ssec.honeywell.com ((jt) John Thompson)
Subject: re: Is the /install dir necessary?
Organization: Electrotechnical Laboratory, Tsukuba Science City
Distribution: fj
Date: Tue, 18 Aug 1992 13:59:41 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>



> This directory takes up alot of disk space and we were wondering
> If it is necessary

Ummmm.  I guess that depends on whether you want to have software or not.
The /install directory contains (by my count) three main sections --

    /install/baseline           A dir for info on what's been installed

    /install/doc                A dir with release notes for s/w

    /install/ri.?*              A whole bunch of directories related to 
    /install/toc                the installation of software.  The biggest
    /install/templates          chunk here is the ri.?* dirs, which are
    /install/tools              the packages that you have for your network.
    /install/minst
    /install/help
    <etc>


The baseline directory is essential for s/w loading.  You can remove all but
the last baseline.xxx file (they're numerically ascending, constantly growing
log files).

The doc directory can be removed, or better yet, linked off to an <AA> node
(where you install software tapes to).  Every time you load a tape into the
authorized-area, it'll put release notes and other such stuff there.  When
you install software from the <AA>, it tries to copy any notes over to the
destination system.  If it's linked, it warns you and doesn't copy anything.

The <other-stuff> directories are absotively, posilutely essential.  If
you've been loading O/S after O/S after O/S, you might have multiple
versions of some packages, and that can get big and wasteful, but as a general
rule, don't delete any package that you have installed somewhere, or want to
install somewhere.  If you haven't already, read the manual on installing
software w/ RAI tools.  Read up on hard-linking the installation.

-- jt --
John Thompson
Design Services Engineer / Sys-Admin
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

What do I know?  I'm just a Token Administrator.
*************************************************************************
* This e-mail correspondence is a work of fiction.  Any similarity      *
* between the views presented and actual views, personal or corporate,  *
* living, dead, or still to be conceived, is pure coincidence.          *
*************************************************************************
Newsgroups: fj.mail-lists.apollo
From: yale.edu!jvnc.net!darwin.sura.net!mips!mips!munnari.oz.au!metro!usage!csdvax.csd.unsw.edu.au!u2116318@yale-bulldog.arpa
Subject: X11r5 server needed for apollo(68k)
Organization: University of New South Wales
Distribution: fj
Date: Thu, 13 Aug 1992 23:18:08 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

does anyone have a ready complied X11r5 
server for apollo (68k)? due to the very very
limit disk space , I'm not able to install 
the server. can some one mail it to me 

thanks in advance
From: lnz@lucid.com (Leonard N. Zubkoff)
Newsgroups: fj.mail-lists.apollo
Subject: Re: dumping executable images?
Date: 18 Aug 92 00:46:28 GMT
	<1992Aug12.194910.9716@lucid.com> <MEHLHAFF.92Aug17002028@soda.soda.Berkeley.EDU>
Distribution: fj
Organization: Lucid, Inc.
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

The SR10.4 and Emacs 18.58 version of my patches is now in final testing and
should be available in a few days.

		Leonard
Newsgroups: fj.mail-lists.apollo
From: haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!caravan.ksu.ksu.edu!news@ames.arc.nasa.gov  (Brian Gregory Howard)
Subject: Re: Post OS installations: what do YOU do?
Organization: Kansas State University
Distribution: fj
Date: Thu, 20 Aug 1992 19:33:59 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:

>In article <1992Aug15.222958.27644@edsi.plexus.COM> chuck@edsi.plexus.COM (Chuck Tomasi) writes:
>>Over the last couple of years I have evolved a script to take care of a
>>machine once the OS and patches have been installed.  It started out
>>with a few site specific links and has grown to include patches to rc

>This one also started the same way, and is augmented by ~20 pages
>of nroff'ed notes on stuff I must do manually after an install.

Here I thought I was the only one who spent the time scripting/debugging sys-
admin "utilities".  As a student here at KSU, I've spent the last 3 years making
mid semester life easier by investing time during the summer writing sys-admin
utilities.  I finally got so many of them that I created a menu based system
(kind of like HP's SAM or IBM's SMIT) called SSU.  Now that everyone is buying
SUNs, I am sssllloowwly converting SSU to SUNOS.

One nifty thing about SSU is its ability to configure for a given system.  Each
system has a configuration file which notes whether it is discless, has user
files and so on.  This information is used to set a number of pre defined
environmental variables before calling a configuration/installation script. The
config/insall script (I currently use the C-shell) then may use the environment
variables to check for os type (10.2 or 10.3), version of X windows ..... it
makes the scripting more portable - and sometimes, more of a pain!

I can also use the configuration files to dump important information such as
CPU serial number, IP address, node ID and other items.

			Happy coding///scripting


				Brian G. Howard
				brian@grace.ecc.ksu.edu
				xx123yyy@matt.ksu.edu
Newsgroups: fj.mail-lists.apollo
From: mk@apollo.hp.com (Mike Kong)
Subject: Re: NCS 2.0 and previous versions
Organization: Hewlett-Packard Corporation, Chelmsford, MA
Distribution: fj
Date: Mon, 17 Aug 1992 16:53:11 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

In article <1992Aug14.153441.8481@ucc.su.OZ.AU> wonga@chem.su.oz.au writes:
>I'm a bit confused about running NCS 2.0 in a network with older versions
>of NCS (i.e. 1.5.1). Are there any special flags for either 'llbd/rpcd'
>or 'glbd' in either the 2.0 or 1.5.1 versions?

Options for these daemons are documented in their man pages, which you can
read online or in Managing NCS Software (Order Number D-11895-E).

You'll probably never need to use any options for llbd or rpcd.

For glbd, you might sometimes need

  -create -first
    when you create your very first glbd

  -family
    to override the default protocol family for replication when you
    create your very first glbd

  -create -from
    when you create replicas of the glbd

  -change_family
    when you want to change the protocol family used by your glbds for
    replication

but you'll probably never need

  -listen
    which restricts the families on which a glbd listens for lookup or
    registration requests (and has nothing to do with the family used
    for replication)

>If the default protocol for 'glbd' in NCS 2.0 is ip, does that mean I 
>have to run the older 'glbd' **specifically** with the ip family?

I'm not sure what you mean by this question, but maybe the following
will help.

If you have old glbds running now and replicating via DDS, then there
are two ways to make new glbds interoperate with the old ones:

[A] To make all glbds replicate via IP, first use "-change_family"
    to change the replication family for all of your old glbds, then
    specify an IP hostname when you create a new glbd (e.g., start
    the new glbd with "-create -from ip:foo").  See Section 5.1.7
    of Managing NCS Software.

[B] To make all glbds replicate via DDS, specify a DDS hostname	
    when you create a new glbd (e.g., start the new glbd with
    "-create -from dds://foo").

For most configurations, I'd recommend [A], which might make future
additions of glbd replicas easier.

After you've done either A or B, you won't need to use any options
when you restart glbds, because they'll know what family to use.

See Managing NCS Software for details.

Mike Kong
Distributed Object Computing Program
Hewlett-Packard Company
Newsgroups: fj.mail-lists.apollo
From: elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!destroyer!ubc-cs!unixg.ubc.ca!physics.ubc.ca!unruh@lll-winken.llnl.gov  (William Unruh)
Subject: Apollo 2500 dead?
Organization: University of British Columbia, Vancouver, B.C., Canada
Distribution: fj
Date: Wed, 19 Aug 1992 16:35:01 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>


One of our 4 Apollo 2500 seems to be very sick. First it's scsi died-
large large numvber of reseeks. Then the ethernet seemed to have died-
trying to boot off another machine, it will start a load, and then die
in the middle of it. Finally I got it to load the self tests from it's
own sick disk, (having had it die in the middle of th load from another
machine 10 times) but it never got anywhere- it frooze before it said
memory test, the first item on the self test. So, is it scrap, or is
there something simple I could try first?
Bill Unruh
unruh@physics.ubc.ca
Newsgroups: fj.mail-lists.apollo
From: Frank Bonnet <bonnetf@apo.esiee.fr>
Subject: Re: advice on backup systems
Organization: Electrotechnical Laboratory, Tsukuba Science City
Distribution: fj
Date: Tue, 18 Aug 1992 06:33:35 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>


We use here an 8mm Exabyte which is now supported at SR10.4 by all the
Domain_os commands rbak,wbak,tar ... 

We use it now since few months without troubles.

The speed is not very fast, it's about 100 Mb/hour with a normal load
on the ATR , it is connected to my DN2500 which has 12Mb of memory so
I perform backups nightly ...

We have now a 4mm DAT for our 710's but I haven't tested it at this 
time.

+------------------------------------------------------------------------------+
| bonnetf@apo.esiee.fr                     |                                   |
| Frank Bonnet                             | Surfing ...                       |
| E.S.I.E.E                                |                                   |
| BP99 93162 Noisy le Grand cedex.FRANCE.  | the rest is details !             |
| Fax   : 33 1 45 92 66 99                 |                                   |
+------------------------------------------------------------------------------+
Newsgroups: fj.mail-lists.apollo
From: wupost!usc!sdd.hp.com!hpscdc!cupnews0.cup.hp.com!hppad.waterloo.hp.com!hart@gumby.wisc.edu  (Tony Hart)
Subject: Re: Logging out from X-Terminals
Organization: HP Panacom Div Waterloo ON Canada
Distribution: fj
Date: Tue, 11 Aug 1992 21:35:11 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

fred@cv.ruu.nl (Fred Appelman) writes:
: In <BsIw2M.3Gr@waterloo.hp.com> hart@waterloo.hp.com (Tony Hart) writes:
: >Strictly speaking, if you use 'vuelogin' you should configure it so that the 
: >HP VUE environment does NOT come up on the X terminal. Legally, you need to
: >purchase a right-to-use license for each non-HP X terminal running HP VUE. 
: >This may be a consideration if your company has corporate guidelines WRT to
: >licensed software.
: >
: >BTW, this is not a problem for HP 700/RX X stations; each comes with a free
: >right-to-use license for HP VUE.
: 
: Do I understand this correct? Does this mean that HP VUE is sold under the
: condition that the graphical output is displayed only on HP platforms?
: The software is running on a HP platform, I can understand that you need
: a license for that. But that you need an additional license to display
: the output on e.g. a Tektronix X terminal is new for me. 

I tried to post a followup but apparently our newsreader was broken. For the
benefit of others (I've already sent private e-mail to Fred), here's the
scoop:

The version of HP VUE which is included with HP-UX is for a SINGLE workstation
user. Additional users (e.g. X terminals) need a per-seat license. A free 
license certificate is shipped with each HP 700/RX X terminal; users of VUE
on non-HP terminals (e.g. NCD, Tektronix) are legally obligated to purchase
a right-to-use license.

When you think about it, this is no different from third-party applications
such as FrameMaker, which run on a host platform but can be displayed on 
X terminals. Unlike many of these packages, HP VUE does not use a license 
server but works on the "honor system" instead. It is assumed that most users
are honest and will purchase the required right-to-use licenses.

To the best of my knowledge, 'mwm' as shipped with HP-UX does not have per-seat
licensing requirements and can be used freely.

Tony Hart,
Panacom Automation Division,
Hewlett-Packard (Canada) Ltd.

Standard Disclaimer:
All opinions expressed are my own and do not represent an official statement of
the Hewlett-Packard Company.
Newsgroups: fj.mail-lists.apollo
From: eru.mt.luth.se!lunic!sunic!mcsun!dxcern!a-op-wc7!pschenk@bloom-beacon.mit.edu  (Paul Schenk)
Subject: Re: Apollo 2500 dead?
Organization: CERN European Lab for Particle Physics
Distribution: fj
Date: Wed, 19 Aug 1992 18:50:52 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

I find it a bit suprising that the machine will not boot diskless
from another node. Does it get partway (ie: does it show some byte count
and then die, or at least find its partner)? If so, and your running
10.3, I would bet that you are seeing the netman bug that made the 
diskless boot hang if there was a broadcast packet on the segment.
Try to apply the patch to the partner node and try again.

Ciao,
Casper

Paul Schenk       |   University of Victoria
                  |   CERN PPE / OPAL
pschenk%cernapo@cernvax.cern.ch <- Pref.
pschenk@cernvm.cern.ch
schenk@uvvm.bitnet
" I have never seen anything fill up a vacuum so fast and still suck "
                          -Rob Pike on X
Newsgroups: fj.mail-lists.apollo
From: cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!rpi!utcsri!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system@ucbvax.Berkeley.EDU  (System Admin (Mike Peterson))
Subject: Re: problem with writing large files from Fortran
Organization: University of Toronto Chemistry Department
Distribution: fj
Date: Fri, 14 Aug 1992 17:38:35 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

In article <5a8e0403.1bc5b@pisa.citi.umich.edu> Antonio Hernandez <AVH@IBMA.ipp-garching.mpg.de> writes:
>All this is very strange because here in Germany I do not seem to have
>any problem with the size of the problem: Right now I am running a
>very large case that handles I/O files of 300Mb each!. Is there a
>problem with the RS.10.2.p operating system? or with the way it
>handles swapping, because the /etc/swap command do not even exist under
>RS.10.1.p operating system at the MPA machine. Is there a hardware probl

There was a problem with the VME disk controller firmware under heavy
I/O load (which your application may hit), but the result of the
problem was always a crash with status 00270005 on our system.

We have run many application like this on our DN10000 (we do molecular
structure calcs too), but don't recall a problem like that where the
system continued to operate except for the one process. There are many
ways to crash/hang your system, especially with the older versions
of Domain/OS and the original VME disk controllers and Ethernet cards.
Are you sure you aren't running out of disk space -- on the older
SR10.x.p, that would cause exactly the behaviour you are seeing: the
process would hang waiting for disk space and would not be killed.
-- 
What are the chances that any computer system will ever "work" properly?
... and Slim just left town. -*- Mike Peterson, SysAdmin, U/Toronto Chemistry
Newsgroups: fj.mail-lists.apollo
From: agate!spool.mu.edu!cserver!edsi!chuck@ucbvax.Berkeley.EDU  (Chuck Tomasi)
Subject: Post OS installations: what do YOU do?
Organization: Enterprise Data Systems Incorporated, Appleton WI
Distribution: fj
Date: Sat, 15 Aug 1992 22:29:58 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

Over the last couple of years I have evolved a script to take care of a
machine once the OS and patches have been installed.  It started out
with a few site specific links and has grown to include patches to rc
files, extreme conditional checking, and lots more.  I'm curious to know
how many other sites have a post_os (or some other named) script and
what it includes.  Would you be willing to post it here (commented of
course to help readability) or a synopsis of what you do?

I'll post mine when I get back to work on Monday.
-- 
Chuck Tomasi             |     "Mom, it's Data.  I heard you know
chuck@edsi.plexus.COM    |      how to turn him on." 
spool!cserver!edsi!chuck |                    -Wesley  "Datalore"
------<Enterprise Data Systems Incorporated, Appleton Wisconsin>------
Newsgroups: fj.mail-lists.apollo
From: eru.mt.luth.se!lunic!sunic!ugle.unit.no!DAHLS%FHYDRA.FYSEL.UNIT.NO@bloom-beacon.mit.edu  (Joern Yngve Dahl-Stamnes)
Subject: DPCI 5.1.1 release notes
Organization: University of Trondheim, NORWAY
Distribution: fj
Date: Thu, 13 Aug 1992 13:31:45 GMT
Return-Path: <apollo-list-errors@srvr1.engin.umich.edu>

Hello.

Someone on this list told me that the last version of DPCI is 5.1.1.
Can you or someone else *please* mail me the release notes from the
distribution media to me?

Thanks.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+
* I went back to my mother,           * Joern Yngve Dahl-Stamnes           *
* I said, "I'm crazy ma, help me!"    * University of Trondheim            *
* She said, "I know how it feels son, * The Norwegian Institute of Tech.   *
* 'cause it runs in the family."      * Division of Physical Electronics   *
*       - The Who, Quadrophenia       * e-mail: dahls@fhydra.dnet.unit.no  *
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+
Newsgroups: fj.mail-lists.apollo