HDTenEightyP/NetNews huggingface dataset:
From: mjones@bk-kgnaix11.aix.kingston.ibm.com (Mike Jones)
Newsgroups: comp.unix.misc
Subject: Re:  The need for an assembler (was: Favorite CPU)
Date: 8 Sep 92 21:22:36 GMT
Reply-To: mjones@donald.aix.kingston.ibm.com
Organization: IBM, Kingston NY


In article <Bu6svH.31J@hatch.socal.com!, richg@hatch.socal.com (Rich Greenberg) writes:
| In article <liam.06m7@durie.amigans.gen.nz> liam@durie.amigans.gen.nz (Liam Greenwood) writes:
| >   O.K. then, the above code put onto some machines say... RS/6000, some
| >IBM PC or clone therof, Amiga, NCR Tower, Unisys 1100/2200, U6000, some
| >CP/M machine, really anything with a K&R C or ANSI C compiler. Compile it
| >and it will run. Please show us the code to do this on the above list of
| >machines in assembler.
| OK, here is some assembler code that will run on every member (except
| the 360/20) of IBM's 360, 370, 303x, 43xx, 308x, 3090, 9370, and 390 series 
| of mainframes, plus the compatables from Amdahl, Hitachi et al that are 
| running any flavor of OS (PCP, *MFT*, MVT, VS1, SVS, and MVS/*),  
| or are running in CMS under the control of VM (any flavor):
|  
| 	HELLO    CSECT
| 	         SAVE   (14,12)
| 	         LR     12,15
| 	         USING  HELLO,12
| 	         WTO    'Hello World.'
| 	         SR     15,15
| 	         RETURN (14,12)
| 	         END    HELLO

Nice. He posts a list of machines using a variety of processors from a
variety of manufacturers, and you run back a list of IBM and IBM-compatible
processors all from the same family. I notice that you don't claim that your
code will run on the System/36 or /38, the AS/400, the System/88, or the IBM
PC or PS/2. Besides, I tell you unequivocally that this code will not run
on any S/390 that happens to be running AIX/ESA. NeXT?

   Mike Jones  |  AIX/ESA Development  |  mjones@donald.aix.kingston.ibm.com

Quayle stumbled in response to a question about his opinion of the Holocaust.
He said it was "an obscene period in our nation's history." Then, trying to
clarify his remark, Quayle said he meant "this century's history" and added a
confusing comment.  "We all lived in this century, I didn't live in this
century," he said.
From: eluyten@rc1.vub.ac.be (Eric Luyten)
Newsgroups: comp.unix.misc
Subject: Re: Help: *.tar.Z
Date: 10 Sep 92 16:39:37 GMT
Distribution: world
Organization: Brussels Free Universities (VUB/ULB), Belgium
Keywords: tar

In article <BuByFs.AzE@unx.sas.com>, sasmob@chewy.unx.sas.com (Mark C. Burhans) writes:
|> 
|> First, put the filename.tar.Z in it's own directory; and 'cd' into that
|> directory; you never know what the heck is in those things.<GRIN>

tar files can contain absolute filenames (starting with '/'), resulting in files being
created *OUTSIDE* your current working directory. Some versions of tar have an 's'
flag to have that '/' stripped before actually extracting the file.

|> Second, uncompress that puppy:
|>   uncompress filename.tar
|> Third, untar that rascal:
|>   tar -xfo filename.tar

First, look what's in it.

tar tvf filename.tar | more                                  (t stands for 'table')

|> You *will* need to use those switches (-xfo)!  Why?
|>   -x    ------ Extract files
|>   -f    ------ Data is in a file, not on tape.
|>   -o    ------ Data that is extracted is now owned by *me*.  This one is
|>                extremely important when you realize you've untarred a
|>                subdirectory that has read-only permission and it belongs
|>                to some user name JES8234abq and in this read-only
|>                directory is a read-only file named 'hermit' that also
|>                belongs to JES8234abq and is 2.31 Megabytes!!!

In most cases where I found myself confronted with this problem, the directory
gets created, is not owned by you, and unless 'others' have write permission, the
2.31 MB file will not be created. The directory can be removed by yourself, as
you presumably have write permission in the directory where you invoked tar.

|> Now you have all these new files along with the original filename.tar.
|> Whether these files are 'executables' or not should be explained in an
|> untarred README-type file.

Or use the 'file' command.

|> ---Mark C. Burhans---sasmob@chewy.unx.sas.com---919/677-8001 ext 7324
|> SAS Institute, Inc., USA, SAS Campus Drive, Cary, NC 27513.

Eric.
From: sasmob@chewy.unx.sas.com (Mark C. Burhans)
Newsgroups: comp.unix.misc
Subject: Re: Help: *.tar.Z
Date: 9 Sep 92 21:31:04 GMT
Organization: SAS Institute Inc.
Originator: sasmob@chewy.unx.sas.com


In article <4SEP199214143882@envmsa.eas.asu.edu>, marbun@envmsa.eas.asu.edu (Marbun,Leo P) writes:
|> Hi,
|> 
|> I was trying to get some programs from anonymous ftp sites, and found out
|> that most files for unix are under *.tar.Z name. Please let me know how
|> to make the files executable? Do I need a tar.Z archiver? I can't seem to

First, put the filename.tar.Z in it's own directory; and 'cd' into that
directory; you never know what the heck is in those things.<GRIN>

Second, uncompress that puppy:
  uncompress filename.tar

Note:  The .Z extension is assumed with uncompress

At this point, filename.tar.Z no longer exists.  We now have a
filename.tar to untar.

Third, untar that rascal:
  tar -xfo filename.tar

You *will* need to use those switches (-xfo)!  Why?
  -x    ------ Extract files
  -f    ------ Data is in a file, not on tape.
  -o    ------ Data that is extracted is now owned by *me*.  This one is
               extremely important when you realize you've untarred a
               subdirectory that has read-only permission and it belongs
               to some user name JES8234abq and in this read-only
               directory is a read-only file named 'hermit' that also
               belongs to JES8234abq and is 2.31 Megabytes!!!

Note:  The entire name of the tarred file must be provided.  It is
convention that .tar is used to signify a tarred file.  'tar' does not
put the .tar extension there.  In contrast, 'compress' appends a .Z to the
file.


Now you have all these new files along with the original filename.tar.
Whether these files are 'executables' or not should be explained in an
untarred README-type file.
-- 
---Mark C. Burhans---sasmob@chewy.unx.sas.com---919/677-8001 ext 7324
SAS Institute, Inc., USA, SAS Campus Drive, Cary, NC 27513.
"If you want a resume, I'll put it in writing.  It's only good for a day
and the contents are frightening."  -- Lyrics by Harry Connick, Jr.
 
Newsgroups: comp.unix.misc
From: c-amb@math.utah.edu (Mark B. Alston)
Subject: Re: Help: *.tar.Z
Date: Sat, 5 Sep 1992 17:23:27 GMT
Organization: Department of Mathematics, University of Utah


Marbun,Leo P (marbun@envmsa.eas.asu.edu) wrote:
>: Hi,
>: 
>: I was trying to get some programs from anonymous ftp sites, and found out
>: that most files for unix are under *.tar.Z name. Please let me know how
>: to make the files executable? Do I need a tar.Z archiver? I can't seem to
>: find it in the ftp site. Let me know where I could get the proper archiver
>: (Unix that I run is Ultrix version).
>: 
>:
> Thanks.
>: 
>: Leo.
>: 
>
>Those files are both compressed and tar-ed, I believe.  You need to first
>run ucompress on them (the Z suffix indicates that they were lastly 
>compressed), and then un-archive them using tar.
>
>-Chris
>
>--
>Christopher Edler				Hewlett-Packard Company	
>cedler@boi.hp.com				Boise, Idaho USA
>

Or, if your tar supports it, you can add the 'z' flag to your tar
command.  This tells tar to uncompress the file before untaring it.
The command line I use most is 'tar zxvf <filename>' "z" to uncompress
the file, "x" to tell tar that I am eXtracting the files in the
archive, "v" to get a Verbose report, and "f" to tell tar that the
next thing I type is the archives filename.
--
--------------------------------------------------------
  Mark Alston        
  c-amb@math.utah.edu
       
"Never knew a decent man who liked mathematics."
			- Bonnie Abbzug-Sarvis
			  Hayduke Lives!
---------------------------------------------------------

Newsgroups: comp.unix.misc,comp.sys.sun.admin
From: mills@ccu.umanitoba.ca (Gary Mills)
Subject: Re: yp (nis) map changes - how do they happen
Keywords: passwd yp nis
Organization: University of Manitoba, Winnipeg, Canada
Date: Sun, 6 Sep 1992 02:42:42 GMT

[comp.sys.sun.admin added; hi Tony]
In <1992Aug30.131151.13011@jupiter.sun.csd.unb.ca> jaf@jupiter.sun.csd.unb.ca (J Anthony Fitzgerald) writes:

>This brings up another question for me.  What locking mechanism (if any) does
>yppasswdd use for the password file.

It uses a lockfile with a name derived by appending ``.ptmp'' to the name
of your NIS passwd base file.  The locking is apparently done around the
edit of the file, but not around the NIS make.

>I have been concerned because of the possibility of yppasswdd updating the
>password file between the time the script reads in the password and group
>files and the rewriting of those files after applying changes.  I have been
>assuming that the yppasswdd changes would be quietly lost.  It would be
>quite simple to add a perl flock call to the script but I would like to be
>assured that this would fix any potential problem.  So far, the scripts seem
>to have caused no problem, but it might be a simple case of no one ever having
>used yppasswd while the script was running.

In this case, you might want to just kill and restart yppasswd before and
after you run the script.  You could also have the script create, and
respect the same lockfile.  However, some versions of yppasswdd will exit
ungracefully if they discover that somebody else has created the lockfile.

There is some danger of corrupting the NIS base file if both yppasswdd and
your script attempt to update it at the same time.  In addition, if two
users change their password at the same time, both makes running at the
same time will surely corrupt the NIS password maps.  Usually, one of them
becomes empty.  This can also happen if a human or your script does the
make at the same time as a user changes his password.  There is no locking
in the Makefile to protect against this.

I fixed this under 4.1.2 by finding a version of yppasswdd, from one of
the 4.1.1 C2 security patches, that waits when the lockfile is present,
and by adding locking to the Makefile.  When I refered the problem to Sun,
the response was that it's a known bug, and is not fixed.
-- 
-Gary Mills-         -Networking Group-          -U of M Computer Services-
From: etxmesa@eos.ericsson.se (Michael Salmon)
Newsgroups: comp.unix.misc
Subject: Re: man macro manual?
Date: 7 Sep 92 10:13:14 GMT
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB

In article <Bu6z2u.3tq@mtholyoke.edu>, jbotz@mtholyoke.edu (Jurgen Botz) writes:
|> Where can I find a manual for the tmac.an macros?  Does it exist or
|> is being able to figure them out a requirement for being qualified
|> to write man pages?

Try:
 eos6c02 ~ 43 > man 7 man

MAN(7)       ENVIRONMENTS, TABLES, AND TROFF MACROS        MAN(7)

NAME
     man - macros to format Reference Manual pages

SYNOPSIS
     nroff -man filename...

     troff -man filename...

DESCRIPTION
     These macros are used to lay out the reference pages in this
     manual.   Note:  if  filename  contains  format  input for a
     preprocessor, the commands shown above must be piped through
     the appropriate preprocessor.  This is handled automatically
     by man(1).  See Conventions.


-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm
From: daw@vivanet.UUCP (David Wolf)
Newsgroups: comp.unix.misc
Subject: Re: Reading 60MB tapes on a 150MB drive?
Keywords: Cartridge, Tape
Date: 4 Sep 92 22:55:55 GMT
Reply-To: daw@vivanet.UUCP (David Wolf)
Organization: VIVATRON Corporation

In article <16@thomson.UUCP> sat@thomson.UUCP (Scott Thomson) writes:
>I have a Wangtek 5150 cartridge tape drive.  It can read and write
>150MB and 250MB tapes.  I was wondering if it can read 60MB tapes?
>I know it will not write 60MB tapes, but will it read them?
>
>Specifically, I would like to get the tape upgrade kit for SCO ODT 2.0
>but I don't know what tape format it is sent on.  I am assuming 60MB tape
>and that most 1/4 inch cartridge tape drives can read 60MB tapes.  However,
>I just don't know for sure.
>
YES, larger tape drive do read the lower capacity tapes.  SCO ODT 2.0 tapes
can be read in your new tape drive.

David Wolf
VIVATRON Corporation                       Voice: 800-836-UNIX
Rochester, New York, USA                     Fax: 716-272-7627
SCO Advanced Product Center                email: uunet!vivanet!daw
*******************************************************************

Newsgroups: comp.unix.misc
From: ellis@nova.gmi.edu (Stew Ellis)
Subject: Re: How to add a suffix to a bunch of files?
Organization: GMI Engineering&Management Institute, Flint, MI
Date: Sat, 5 Sep 1992 13:49:27 GMT

jdell@nefertiti.mit.edu (John Ellithorpe) writes:

>On Thu, 3 Sep 1992 21:36:46 GMT, dchin@tamar.msc.cornell.edu (David W. Chin) said:

>> I have occasion to add suffices on a whole bunch of files, like a .1 suffix on
>> all files in cat1 (just an example).  What's an elegant way to do it?
>> The one I thought of was:

>> #!/bin/sh
>> cd cat1
>> for X in `ls -1`
>> 	do
>> 	eval "mv $X $X.1"
>> 	done

>If you are in some variant of csh, I personally use tcsh 6.02

>% foreach file (*)
>foreach> mv $file $file.1
>foreach> end

>And that's it.  Pretty much just as good as the Bourne shell version.

>John
>--

>===============================================================================
>John Ellithorpe                           | Internet: jdell@maggie.mit.edu
>Dept. of Physics, Rm 26-349               | Phone   : (617) 253-3074  Office
>Massachusetts Institute of Technology     |           (617) 253-3072  Lab
>Cambridge, MA  02139                      |           (617) 236-4910  Home
>===============================================================================

(I hope Mr sef of the net bandwidth police doesn't jump my ass for including
too much of the previous posters' messages) :-|

What is the point of the eval statement in the sh version?  I thought the
point|advantage of using eval was to keep something in the context of the
current shell.  I do not see why that is necessary here.  Is this cheaper
somehow?  It seems much more straightforward to simply mv it rather than eval
the mv, the way the csh example above does.
--
--                                                        ___________________
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765  /   _____  ______ 
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.   /        / /  /  / /
  Flint, MI 48504      ellis@nova.gmi.edu              /________/ /  /  / /
From: huang2@husc8.harvard.edu (Howard Huang)
Newsgroups: comp.unix.misc
Subject: Re: NFS Protocol Specification
Date: 13 Sep 92 07:25:48 GMT
Article-I.D.: husc8.HUANG2.92Sep13002548
Organization: Harvard Arts and Sciences Computer Services, Cambridge, MA
In-reply-to: vander@flab.fujitsu.co.jp's message of 9 Sep 92 02:47:44 GMT

vander@flab.fujitsu.co.jp (Mike van der Velden) writes:

   I'm looking for the latest version of the NFS Protocol Specification.

A copy of version 3 of the specification is on ftp.uu.net, under 
networking/ip/nfs/NFS.spec.Z.

--
Howard C. Huang
hhuang@teton.mitre.org
Newsgroups: comp.unix.misc
From: geert@gouldnl.encore.nl (Geert Lindemulder)
Subject: termcap entry for a Tandem TS530 Series Terminal
Organization: Gouldnl Field Service
Date: Mon, 7 Sep 1992 13:16:30 GMT

Dear network readers ,

This morning we received a Tandem TS530 Series Terminal.
We tried to connect this to our gould powernode pn6040 with
a utx 2.1b operating system.
Unfortunately our system does not have an entry, for this kind
of terminal in the termcap file.
Did anyone of you ever had to connect one of these terminal to his
unix system.
I am very interested in any number of termcap lines , before i
start searching in the terminal manual to edit a termcap entry myself. 

regards , Geert Lindemulder 
Encore Computer Nederland B.V.
Maarssenbroek , Nederland
Email : glindemulder@encore.nl
Xref: sparky comp.unix.misc:3663 comp.unix.questions:11062
From: rz64938@mystic.d50.lilly.com (David W. Crumbacher)
Newsgroups: comp.unix.misc,comp.unix.questions
Subject: Checking if a process exists
Date: 14 Sep 92 20:06:53 GMT
Reply-To: rz64938@mystic.d50.lilly.com (David W. Crumbacher)
Distribution: world,local


Is there a way in C to determine if a certain process is running?

Thanks.
--
+--------------------------------------------------------------+---------+
| David W. Crumbacher            |  e-mail: dwc@lilly.com      |         |
| Scientific Information Systems |  Phone : (317) 276-5345     |    o    |
| Lilly Research Laboratories    |  FAX   : (317) 276-4127     |   (     |
| Eli Lilly and Company          |  These are my own opinions, |   [\.   |
| Indianapolis, Indiana 46285    |  not my employer's.         |         |
|            *** Please respond to dwc@lilly.com ***           |         |
+--------------------------------------------------------------+---------+
Xref: sparky comp.unix.misc:3664 comp.protocols.nfs:2326
From: thurlow@convex.com (Robert Thurlow)
Newsgroups: comp.unix.misc,comp.protocols.nfs
Subject: Re: NFS Protocol Specification
Date: 14 Sep 92 22:49:01 GMT
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

In <HUANG2.92Sep13002548@husc8.harvard.edu> huang2@husc8.harvard.edu (Howard Huang) writes:

>vander@flab.fujitsu.co.jp (Mike van der Velden) writes:

>   I'm looking for the latest version of the NFS Protocol Specification.

>A copy of version 3 of the specification is on ftp.uu.net, under 
>networking/ip/nfs/NFS.spec.Z.

Burn this copy!  It is something like four years old and has absolutely
no value except to those who are interested in some of the history of
how protocol turns happen (or don't happen, if you're cynical }:-).  A
later "Version 3 spec" (the Postscript protocol) is even more fun from
that viewpoint.

The version 2 protocol is the only one people have implemented, and the
only one worth seriously considering.  Looking at this will only get you
confused, seriously, because it has so many bad ideas.

Rob T
--
Rob Thurlow, thurlow@convex.com
Across the evening sky, all the birds are leaving
But how can they know it's time for them to go?		- Sandy Denny
Newsgroups: comp.unix.misc
From: rreiner@nexus.yorku.ca (Richard Reiner)
Subject: Re: How to add a suffix to a bunch of files?
Organization: York University
Date: Sat, 5 Sep 1992 14:41:43 GMT

On Thu, 3 Sep 1992 21:36:46 GMT, dchin@tamar.msc.cornell.edu (David W. Chin) said:

>I have occasion to add suffices on a whole bunch of files, like a .1 suffix on
>all files in cat1 (just an example).  What's an elegant way to do it?

Easy sh and csh solutions have been given, but it's worth pointing out
that the program mmv (available in all the usual places) excels at
this kind of stuff.  In fact, it is much more general.  For instance,
you can do

    mmv '*foo*bar*' '#2fiz#3bat#1#2'

The #<digit> expressions in the target name work as you'd expect: #1
is replaced with whatever matched the first '*' in the source, etc.;
and each can be used as many times as one likes.  A very useful tool.

So the solution to the present problem, using mmv, is just

    mmv '*' '#1.1'


-- 
Richard Reiner........rreiner@nexus.yorku.ca........416-538-3947

Learning, n.  The kind of ignorance distinguishing the studious.
  -- Ambrose Bierce, _The Devil's Dictionary_.
Newsgroups: comp.unix.misc
From: datta@cs.uwp.edu (David Datta)
Subject: Looking for a talk that can 'answer'
Organization: University of Wisconsin - Parkside
X-Newsreader: Tin 1.1 PL5
Date: Thu, 10 Sep 1992 00:49:57 GMT

I am looking for a talk program that can "lookup" a current request and 
simply connect to it.
-- 
-Dave datta@cs.uwp.edu: Man made machines make music for the man.  Now
machines make music while the man makes plans. A second generation, a
generation lost. While the man prepares for the holocaust.- A Flock of Seagulls
Newsgroups: comp.unix.misc
From: cedler@boi.hp.com (Chris Edler)
Subject: Re: Help: *.tar.Z
Date: Sat, 5 Sep 1992 05:22:14 GMT
Organization: Hewlett-Packard / Boise, Idaho
X-Newsreader: Tin 1.1.3 PL5

Marbun,Leo P (marbun@envmsa.eas.asu.edu) wrote:
: Hi,
: 
: I was trying to get some programs from anonymous ftp sites, and found out
: that most files for unix are under *.tar.Z name. Please let me know how
: to make the files executable? Do I need a tar.Z archiver? I can't seem to
: find it in the ftp site. Let me know where I could get the proper archiver
: (Unix that I run is Ultrix version).
: 
: Thanks.
: 
: Leo.
: 

Those files are both compressed and tar-ed, I believe.  You need to first
run ucompress on them (the Z suffix indicates that they were lastly 
compressed), and then un-archive them using tar.

-Chris

--
Christopher Edler				Hewlett-Packard Company	
cedler@boi.hp.com				Boise, Idaho USA
Newsgroups: comp.unix.misc,comp.unix.questions
From: zilla@ccrl.nj.nec.com (John Lewis)
Subject: UNIX is TM?
Organization: C&C Research Labs, NEC USA, Princeton, N.J.
Date: Mon, 14 Sep 92 00:29:58 GMT

I need to mention the word "Unix" in a paper.  One of the reviewers
repeated that 
- UNIX must be capitalized
- UNIX must modify a noun
- UNIX is a trademark of UNIX System Laboratories Inc. and must be
  footnoted as such.
In checking this out, the first paper I found, from someone at Sun,
spelled it as Unix (not capitalized) and did not mention any trademark.

================

I want to refer to unix as the supposedly open o/s, not some proprietary
version.  Presumably if UNIX is a trademark, then 'Unix' may be used
to refer to the general concept, possibly including Mach and other flavors.

Is this correct?  What should I do (other than just deleting the reference?)


================
NOTE my return address is zilla@ccrl.nj.nec.com, 
not zilla@.nj.nec.com as our Pnews reports

thanks, j.p.lewis/nec research
Newsgroups: comp.unix.misc
From: sofkaski@tnclus.tele.nokia.fi
Subject: Date and time to workstation network
Organization: Nokia Telecommunications.
Date: Mon, 14 Sep 1992 11:37:06 GMT


        Does anybody some HW and/or SW solution to set accurate
        date and time to a unix workstation network from an outside
        reference ?

        Jyrki Kaski
        Nokia Telecommunications
        email: sofkaski@tnclus.tele.nokia.fi
Newsgroups: comp.unix.misc