HDTenEightyP/NetNews huggingface dataset:
From: jdevlin@pollux.usc.edu (Joseph T. Devlin)
Newsgroups: comp.sys.hp
Subject: File questions
Date: 27 Jul 1992 15:49:28 -0700
Organization: University of Southern California, Los Angeles, CA
Distribution: usa
NNTP-Posting-Host: pollux.usc.edu
Keywords: Disk space

  I was poking around trying to save some disk space here and
there and ran across a couple of files I don't recognize (and
which I didn't find documentation for in a cursory search.) I
was wondering whether anyone could tell me what the following
are?

  o All the files in /etc/audio.  It was my understanding that
the 730s (what I'm using) don't even have sound capabilities.
Do I need any of these files?  I certainly won't be using audio
stuff.

  o What are files preceded by a hash?  (ie /etc/#updist)  In all
cases that I found a file preceded by a single hash I found that
I had a file of the same name minus the hash.  Do I need both? I
know that emacs stores buffers as #<buffer>#.

  o The files in /usr/lib/veedemo.  I couldn't figure out what this
is.

  I'd love to free up the space these are taking but will deleting
them cause me unforseen problems?  Are there other things that HP
provided initially that folks commonly remove for space reasons?
  One other thing, I heard HP provides a CD with the man pages 
available on it to free up that space.  Is there any truth to this?

  Thanks a bunch - I appreciate the help!

							- Joe

*************************************************************************
Joseph Devlin                      * email: jdevlin@pollux.usc.edu
University of Southern California  *
Department of Computer science     * "The axon does not think.
Los Angeles, CA 90089              *  It just ax."  George Bishop
*************************************************************************


Newsgroups: comp.sys.hp
From: gcagle@dracula.mentorg.com (Greg Cagle)
Subject: Re: File questions
Originator: gcagle@dracula.mentorg.com
Date: Tue, 28 Jul 1992 14:17:59 GMT
Distribution: usa
Organization: Mentor Graphics 
Keywords: Disk space
Followup-To: 


In article <l78vboINNb7p@pollux.usc.edu>, jdevlin@pollux.usc.edu (Joseph T. Devlin) writes:
|>   I was poking around trying to save some disk space here and
|> there and ran across a couple of files I don't recognize (and
|> which I didn't find documentation for in a cursory search.) I
|> was wondering whether anyone could tell me what the following
|> are?
|> 
|>   o All the files in /etc/audio.  It was my understanding that
|> the 730s (what I'm using) don't even have sound capabilities.
|> Do I need any of these files?  I certainly won't be using audio
|> stuff.

You can use /etc/rmfn to delete the AUDIO fileset to remove that
stuff cleanly. You're right, you don't need that stuff on a 730.

|>   o What are files preceded by a hash?  (ie /etc/#updist)  In all
|> cases that I found a file preceded by a single hash I found that
|> I had a file of the same name minus the hash.  Do I need both? I
|> know that emacs stores buffers as #<buffer>#.

Those are old files that got replaced by newer versions at some point.
You may safely get rid of them.
 
|>   o The files in /usr/lib/veedemo.  I couldn't figure out what this
|> is.

It's a demo of HP-VEE. You can get rid of it (unless you like demos).
Use /etc/rmfn to get rid of VEEDEMO-HELP and VEEDEMO-MAIN.

|>   I'd love to free up the space these are taking but will deleting
|> them cause me unforseen problems?  Are there other things that HP
|> provided initially that folks commonly remove for space reasons?
|>   One other thing, I heard HP provides a CD with the man pages 
|> available on it to free up that space.  Is there any truth to this?

You're probably talking about LaserROM; it not only has man pages but
the (almost) full documentation set.

- Greg
-- 
Greg Cagle               "I spilled spot remover on my dog.
Mentor Graphics           Now he's gone."
greg_cagle@mentorg.com
From: philipp@ulysse.enst.fr (Philippe-Andre Prindeville)
Newsgroups: comp.sys.hp
Subject: Re: D/A interface board in hp720???
Date: 26 Jul 92 20:51:28 GMT
Reply-To: philipp@ulysse.UUCP (Philippe-Andre Prindeville)
Organization: Telecom Paris, France

In article <7371167@hpfcso.FC.HP.COM> rdg@hpfcso.FC.HP.COM (Rob Gardner) writes:
>
>> I need to somehow hook up a D/A (16-bit) to my hp720 so I can play
>> audio.  (We are doing speech processing research).  We bought EISA
>> option to help make this possible.  HP has not been able to help me
>> figure out how to do this.  Does anyone know?
>
>You plug the card into your EISA slot. Then you order 98577-90013, which
>is the HPUX Driver Development Guide, and write a driver to make your
>D/A card talk. After several months of frustration, you post questions
>to comp.sys.hp.

Seems I will be doing this myself sometime soon.  HP, in it's infinite
wisdom, put audio hardware on the low-end stations (the 710s and 705s)
but not on the high-end hardware (>=720).

We have a multi-media project here, and as soon as my 3 Sound Blaster
Pro cards come in, and the aforementioned doc, *and* I find IP
multicasting for HP-UX 8.05, I will have voice-conferencing locally.

Which reminds me: why did they have to bastardized the netinet code
so that you can't patch it yourself from Berkeley code?  I don't see
the wisdom in this.  I would _love_ to drop in Steve Deering's code.

-Philip

P.S.	You can ask me in 2-3 months if I have a working driver for the
	Sound Blaster Pro.  With a bit of luck, it will even be compatible
	with the Audio programming libraries.
From: markb@spock.dis.cccd.edu (Mark Bixby)
Newsgroups: comp.sys.hp
Subject: Any utility showing sockets and their processes?
Date: 29 Jul 92 21:52:28 GMT
Organization: Coast Community College District, Costa Mesa, CA

The netstat -a command lists information about all active sockets.  Is there
any HPUX command or contributed utility that will list all active sockets, along
with the processes that are connected to them within the local host?
-- 
Mark Bixby                         Internet: markb@spock.dis.cccd.edu
Coast Community College District   1370 Adams Avenue
District Information Services      Costa Mesa, CA, USA  92626
Technical Support                  (714) 432-5064
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
From: philipp@ulysse.enst.fr (Philippe-Andre Prindeville)
Newsgroups: comp.sys.hp
Subject: Re: windows unexpectedly dying - why and how to fix it ? (flame)
Date: 26 Jul 92 20:54:06 GMT
Reply-To: philipp@ulysse.UUCP (Philippe-Andre Prindeville)
Organization: Telecom Paris, France

>Sounds like the old csh autologout thing. unset autologout 
>or autologout=0 is what you want to do.

Which brings us to the question:  why does there login set autologout
by default?  Why don't they just put a line like "set autologout=60"
into /etc/csh.login where it is obvious and can safely be commented
out (like those $%&%^ copyright notices).

-Philip
From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC)
Newsgroups: comp.sys.hp
Subject: Re: Exabyte tape drives on Series 700 ?
Date: 27 Jul 92 09:42:30 GMT
Organization: Hewlett-Packard, The Netherlands

Eric Bushnell (eric@csi6.med.ge.com) writes:

> Yes, it [Exabyte tape drive, FS] seems to work, with the exception of
> tar. I've tried an older 8200 with a 710 running 8.07.
[deleted]
> Tar, however, does not work quite right. It appears to write archives, but
> indexing them and extracting them is buggy.

  Another customer had a similar problem (on 9000/700 8.07, details
about Exabyte unknown). Besides us, he called his Exabyte supplier. They
installed a new PROM in the drive and he is happyly tar-ing away.

>					      I believe it was Michael Lampi
> (credit where it's due)
> who identified the problem with tar as being a bogus attempt to write a filemark
> after reading.

  Without exact details it is hard to tell, but probably the problem is
in the driver instead of in tar. See SR # 4701056382 in file
/etc/newconfig/807KNOWN_PROB, fixed in 9.0.

Frank Slootweg, HP, Dutch Customer Response Center
Newsgroups: comp.sys.hp
From: gcagle@dracula.mentorg.com (Greg Cagle)
Subject: Re: software version determination 
Originator: gcagle@dracula.mentorg.com
Date: Wed, 22 Jul 1992 14:40:09 GMT
Organization: Mentor Graphics 
Keywords: 
Followup-To: 


In article <1992Jul22.123553.10230@eagle.lerc.nasa.gov>, edsver4@convx1.lerc.nasa.gov (Jane R. Kramer) writes:
|> 
|> Can anyone tell me how to determine on-line, the current version of software
|> such as FORTRAN or C?  Thanks.
|> 

The easiest way is to use what:

# what /usr/bin/f77
/usr/bin/f77:
        HP-UX Fortran/9000s700 09/19/91 B2408A.08.07

# what /bin/cc
/bin/cc:
        HP92453-01 A.08.71 HP C Compiler

#

- Greg
-- 
Greg Cagle               "It's just the same, only different."
Mentor Graphics          
greg_cagle@mentorg.com
Newsgroups: comp.sys.hp
From: houten@pttnwb.nl (K. van Houten)
Subject: 700 Single user boot (WAS: HP9000/400 and long file names)
Organization: PTT Telecom b.v. The Netherlands
Date: Thu, 23 Jul 1992 09:06:12 GMT

In article <JEFF.92Jul22204449@dsndata.uucp>, jeff@dsndata.uucp (Jeff Minnig) writes:
 [ stuff deleted ... ]
|> 
|> Of course, on a 700, you can just isl into single user mode to begin
|> with.
|> 

I've tried that, the same way as on a 800 machine, but failed.
What is the magic boot command from ISL to boot a 730 in single user?

-- 
Karel van Houten, 		DOMAIN:	houten@pttnwb.nl
PTT Telecom b.v.		UUCP:	uunet!mcsun!sun4nl!pttdis!houten
's-Gravenhage, The Netherlands	VOICE:	+31 70 3434947
Xref: sparky comp.sys.hp:8527 comp.sys.novell:6024 comp.os.msdos.misc:4507 comp.protocols.tcp-ip.ibmpc:4411
From: hensel@fuhainf.fernuni-hagen.de (Uwe Hensel)
Newsgroups: comp.sys.hp,comp.sys.novell,comp.os.msdos.misc,comp.protocols.tcp-ip.ibmpc
Subject: Novell-Netware-NFS and HP-UX and NCSA-TCP/IP
Date: 24 Jul 92 17:29:40 GMT
Followup-To: poster
Organization: FernUniversitaet Hagen, W-Germany

Hello folx !


We are running one Novell-Server with a lot of diskless clients booting over
IPX. On the Server we use Novell-Netware NFS to connect to a HP9000/847.
The PC-Clients should connect to the HP9000 using NCSA-Telnet.

We got a few problems with this configuration and maybe someone out there can
give me a hint to correct them.

1) While printing from HP/UX to the Netware-Queues after each job one
blank page is ejected from the printers? I use Novell line-printer filter and
the remote model from HP/UX for remote printer.

2) While trying to print from DOS-Clients via Netware-Queues all files are
spooled in the HP spooling system without error messages and show up in the
lpstat command, but the files were never printed and end up in the spooling
system?

3) On the PC-Clients we want to run NCSA-Telnet for connecting to the HP/UX
and do VT102 Terminal-Emulation. At first all goes fine but within half an
hour the speed slows down and at the end I got the Novell-shell error message 
"Can't read from Network " and the PC dies...
We use Netware-Shell 3.26 with SK-Boards and their IPX and IPDRV.
Can this be a memory Problem ?
I used NCSA Version 2.3.0.3 but I got Version 2.3.0.5 today. Maybe this
problem is fixed with the new version ?

4) Is there a possibility to run NCSA under Windows with using the graphics
features. Whenever I return to Program-Manager while having started a graphical
application under HP/UX the PC crashes ?


Maybe someone can help me with one or more of these problems ?

Thanx in advance
		Uwe


Because I haven't the chance to read news daily, would you please respond
by email and I would summarize the answers, if there's an interrest.

Paper-Mail: Uwe Hensel
	    Wilhelmshoeherstr. 58
	    5828 Ennepetal 1
	    Phone (0049) 02333/71405

E-Mail    : hensel@dhafeu61.bitnet
	    hensel@fernuni-hagen.de
            hensel@fernuni-hagen.dbp.de  <--- X.400 MHS

From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC)
Date: Wed, 22 Jul 1992 14:31:51 GMT
Subject: Re: HP1000/RTE question: How to read data to DOS/UNIX?
Organization: Hewlett-Packard, The Netherlands
Newsgroups: comp.sys.hp

  First of all: I suggest you call your HP support and/or sales people.
They should be able to answer these questions.

> Here are my questions:
> 
> o Does anyone know of a way to get this data out of the machine?

  Of course! :-) Read on.

> o Is there a program out there that will read RTE formatted disks
>   (which are on 3.5" high-density diskettes) from a PC under DOS?

  I assume that the RTE-A system has a harddisk besides the 3.5"
diskette drive. If so then you can use an RTE-A program (I think it is
called TF. Ask an RTE support person.) which can convert the files to
UNIX tar(1) format (your "Subject: " line says "How to read data to
DOS/UNIX?". What happened to the UNIX system? :-) Is it an HP UNIX
system?). tar(1) is available on all UNIX systems and there are tar(1)
clones for PCs (see comp.binaries.ibm.pc.archives for information on the
SIMTEL archives). Make sure that the diskette drive on the RTE-A system
can write in standard 720KB or 1.44MB format (HP made 3.5" inch drives
before they were used on PCs, so there are HP drives which are not
compatible with the PC standard).

> o Is there any way to hook a PC up to the HP1000 and simply capture
>   an ASCII representation of the data files with a terminal emulator?

  Yes. For example with HP's AdvanceLink terminal emulator for the PC.
Contact your HP sales rep or PC dealer.

> Thanks for any and all help I can get on this.

  You are welcome.

Frank Slootweg, 15 years of RTE and 9 years of HP-UX, HP, Dutch CRC
From: wk@cup.hp.com (Wayne Krone)
Newsgroups: comp.sys.hp
Subject: Re: /usr/adm/diag ?
Date: 24 Jul 92 23:32:56 GMT
Article-I.D.: cup.Brx2qx.FKs
Distribution: usa
Organization: HP-UX Kernel Lab, Cupertino
X-Newsreader: Tin 1.1 PL3

marc@marcal.uucp (Marc Veeneman) writes:
: wk@cup.hp.com (Wayne Krone) writes:
: 
: >Have HP Support review the log files.
: 
: Is there software on the system that'll interpret them? Why

Run:

$ sysdiag
DUI >logtool
LOGTOOL>list log=NNNN
LOGTOOL>exit
DUI >exit

where NNNN is the numeric part of the log file name.  Type "help" and
"help COMMAND" (where COMMAND is one of the commands shown by "help") to
get more info.

However, the data dumped out often requires knowledge of SCSI protocol
or such to interpret which is why I suggested contacting HP Support.

logtool is safe (as far as I know) but the other diagnostic utilities
available via sysdiag can mess up your system if misused.

:                                                      Or is a
: LOGnnnn file always a sign of some impending disaster?

Not necessarily.  For example, a non-empty log file (log files 40 bytes
long are empty) might have a record from a disk which properly handled a
bad sector by reallocating it.  But if a disk has very many such records
then it should be examined for possible repair/replacement.
Newsgroups: comp.sys.hp
From: ohl@ips105.desy.de (Thorsten Ohl)
Subject: Re: HP PA-RISC gdb 4.6 support is available
Organization: Deutsches Elektronen-Synchrotron, Hamburg, Germany.
Date: Thu, 30 Jul 1992 02:07:56 GMT

>>>>> On 29 Jul 92 17:31:44 MDT, lepreau%mancos.cs.utah.edu@cs.utah.edu (Jay Lepreau) said:

Jay> This builds and works on PA-RISC systems running BSD and HP-UX 8.05.
Jay> Maybe more, but they've been tested a bit.

Before I try it: gdb-4.5 used to *panic* HP-UX 8.0[57].  Has this been
fixed?  Iff so, is it understood which part of HP-UX was responsible
or did you have to work around several HP-UX bugs?

Inquiring mind wants to know ...
--
////// Thorsten Ohl, DESY (-T-), Notkestr. 85, W-2000 Hamburg 52, F.R.G.
///////// net: ohl@crunch.ikp.physik.th-darmstadt.de, ohl@gnu.ai.mit.edu
//////////////////////// voice: +49-40-8998-3699,  fax: +49-40-8998-3282
From: mjs@hpfcso.FC.HP.COM (Marc Sabatella)
Newsgroups: comp.sys.hp
Subject: Re: Mkdir in fork
Date: 30 Jul 92 16:43:33 GMT
Organization: Hewlett-Packard, Fort Collins, CO, USA

In comp.sys.hp, a866700@hp9000.csc.cuhk.hk (Wong Siu To) writes:

> 			execve ("/bin/mkdir", argv, envp);
> 			/*
> 			 *  The execve() failed!
> 			 */
> 			printf ("Utility [nqsmkdirs]:  Unable to execve() ");
> 			printf ("mkdir program.\n");
> 			printf ("Utility [nqsmkdirs]:  Reason: %s.\n",
> 				sys_errlist [errno]);

A guess - the intervening printf's may be resetting "errno" to 0 after the
failed execve.  Try saving the value of errno before printing your messages,
or print errno in the first printf call after the failed execve.

--------------
Marc Sabatella (marc@hpmonk.fc.hp.com)
Disclaimers:
	2 + 2 = 3, for suitably small values of 2
	Bill (H.) and Dave (P.) may not always agree with me
Newsgroups: comp.sys.hp
From: shenkin@avogadro.barnard.columbia.edu (Peter S. Shenkin)
Subject: Re: Inhibiting core dumps on HP7xx
Organization: Dept. of Chem, Barnard College, Columbia U, New York
Date: Sun, 26 Jul 1992 02:23:33 GMT
X-Posted-From: avogadro.barnard.columbia.edu
X-Posted-Through: sol.ctr.columbia.edu

In article <1992Jul25.124640.7267@resonex.com> zenon@resonex.com (Zenon Fortuna) writes:
>In article <Brwwx9.CyL@ef2007.efhd.ford.com> Mike O'Connor <mjo@fmsrl7.srl.ford.com> writes:
>>In article <7371168@hpfcso.FC.HP.COM> acmeyer@hpfcso.FC.HP.COM (Alan
>>C. Meyer) writes:
>>
>>:In comp.sys.hp, elwin@gamma.phys.clemson.edu (Lawrence E. Brown) writes:
>>:
>>:> I'm very tired of frequent dumps of 10-40Meg core files every
>>:> time I have a floating exception somewhere in my code (mostly
>>:> Fortran some C).  Is there any way to prevent core dumps in
>>:> HPUX8.0x on an HP700 series machine? 
>> (omitted example of the nocore.c code)
>
>I see two other ways to protect against the core dumps:
>
>Method 1 (brutal)
>
> - produce an empty file named "core" in the directory, in which you run
>   your application
> - change the mode of this file to 444
>
> This will protect against creation of core (for non-superuser users)

Old UNIX trick for all systems:  create a DIRECTORY called core in the
local directory;  this will not be overwritten by any program trying
to dump core, no matter who's running it.  (I thought everybody knew
this one....)

	-P.
-- 
************************f*u*cn*rd*ths*u*cn*gt*a*gd*jb*************************
Peter S. Shenkin, Department of Chemistry, Barnard College, New York, NY 10027
(212)854-1418    shenkin@avogadro.barnard.columbia.edu   shenkin@cunixf.BITNET
******************** The singular of "media" is "medium". ********************
From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC)
Newsgroups: comp.sys.hp
Subject: Re: How to operate 750 serial ports at 57600 baud?
Date: 27 Jul 92 11:50:22 GMT
Organization: Hewlett-Packard, The Netherlands

raymond@es.ele.tue.nl (Raymond Nijssen) writes:

> We're trying to connect a high-speed modem to our 9000/750.
> 
> The modem is capable of running at 57600 baud, but the 750 (running 8.05)
> builtin ports seem to be capable of running at 57600 and up, but
> the software (stty, [uu]getty) seems to be limited to at most 38400 baud.
> 
> Do I miss something?
> Your help would be appreciated.

  From termio(7) :

>  DEPENDENCIES
[deleted]
>       Series 700
>            Built-in serial ports on the Series 700 machines support the
>            following additional baud rate settings: 57600, 115200, 230400,
>            and 460800 baud.  An RS-232-to-RS-422 converter may be required
>            to achieve actual throughput at these baud rates (because RS-232
>            only specifies up to 19200 baud).

  I don't know if there are any limitations in stty(1). In any case it
is easy to write a little C program to set the baud rate and use stty(1)
for the rest. See termio(7) for the required ioctl's.

  There is no need for uugetty(1m) on HP systems. We only supply it for
compatibility reasons. See "Terminal port access interlock" in modem(7)
as to why uugetty(1m) is not needed. I don't know if getty(1m) can
handle 57600 baud, just try it.

Frank Slootweg, HP, Dutch Customer Response Center
Newsgroups: comp.sys.hp
From: gcagle@dracula.mentorg.com (Greg Cagle)
Subject: Re: Re: trouble with HP-UX software support : solution idea
Originator: gcagle@dracula.mentorg.com
Date: Mon, 27 Jul 1992 19:26:04 GMT
Organization: Mentor Graphics 
Keywords: 
Followup-To: 


In article <Bs1w1u.D87@ef2007.efhd.ford.com>, mjo@ef2007.efhd.ford.com (Mike O'Connor) writes:
|> Sorry if I seem a bit cynical, but this isn't that much different from
|> vaporware promises.  It would be nice to see a LIST of patches freely
|> accessible.  Will this involve a three-year survey to determine the
|> ramifications of the elaborations of the machinations of the
|> aspirations of Hewlett-Packard news?  There are people out there with
|> problems NOW, who have to make purchasing decisions based on what they
|> have in their hands *TODAY*.  I wouldn't want to be a customer who
|> bought support playing a shell game with HP regarding patches.  The
|> description of the patch tends to help in identifying the problem, if
|> nothing else.  I realize that Greg Cagle, gcagle@mentorg.com is
|> posting some sort of "list of patches" and this is a great service on
|> his part.  However, I think this falls more properly in the realm of
|> HP and support.
|> 
|> 					...Mike
|> 
|> (Yes, these are my views.  Yes, the HP SE I deal with has done a good
|> job, IMHO.  No, this isn't necessarily reflective of Ford Motor Co.)

I agree. I started posting my list after I went to the InterWorks
sysadmin conference and realized that a lot of people didn't have the
same access to information that I have (for whatever reason). I wish
HP would own up to just sending the list that SEs get to the customer
base. I wonder if they're stuck in "mainframe mode" and don't really
realize the needs of the workstation market.

- Greg
-- 
Greg Cagle               "Like, Burgerville, man."
Mentor Graphics          
greg_cagle@mentorg.com
Newsgroups: comp.sys.hp
From: mjo@ef2007.efhd.ford.com (Mike O'Connor)
Subject: Re: Best Mail User Interface
X-Disclaimer: Not an official spokesperson for Ford OPEO
Reply-To: Mike O'Connor <mjo@fmsrl7.srl.ford.com>
Organization: International Affairs, Overseas Engineering, "Fordz"
Date: Wed, 22 Jul 1992 20:01:22 GMT

In article <1992Jul22.150132.16245@maccs.dcss.mcmaster.ca>
khindria@maccs.dcss.mcmaster.ca (Vivek Khindria (CSU)) writes:

:       You may consider Pine+Pico as an alternative to elm+vi for casual users.

:In article <1992Jul22.130859.7760@news.nd.edu> mandell@bach.helios.nd.edu (Dan Mandell) writes:
:>We are setting up HP 9000/827S system to serve as academic 

The last time I checked, pine and/or pico was not ported to the HP.

-- 
 Michael J. O'Connor           |  Internet:  mjo@fmsrl7.srl.ford.com
 Ford Motor Company, OPEO      |  UUCP:      ...!{backbone}!fmsrl7!mjo
 20000 Rotunda, Bldg. 1-3001   |  Phone:     +1 (313) 248-1260
 Dearborn, MI  48121           |  Fax:       +1 (313) 323-6277
From: lou@hpkslx.mayfield.HP.COM (Lou Kvitek)
Date: Fri, 24 Jul 1992 23:26:03 GMT
Subject: Re: Re: trouble with HP-UX software support : solution idea
Organization: HP Response Center Lab
Newsgroups: comp.sys.hp



Ok, some clarification.  This proactive patching project is
still only in investigation phase.  No commitments have
been made as to deliverables yet.  That includes what will
be available and when.

Keep the comments flowing, we're watching.  And watch for
news some time in the future as to our plans.

Sorry if your expectations may have been set too early.
From: myawn@hpcupt3.cup.hp.com (Mike Yawn)
Date: Mon, 27 Jul 1992 15:24:08 GMT
Subject: Re: HP MPE NetIPC <-> BSD sockets?
Organization: Hewlett Packard, Cupertino