Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!
bloom-beacon!mit-eddie!killer!vector!rpp386!jfh
From: j...@rpp386.UUCP (John F. Haugh II)
Newsgroups: news.admin,news.sysadmin,comp.sources.wanted,comp.sources.d,comp.unix.xenix
Subject: Please remove PD-YACC sources from your machine IMMEDIATELY
Message-ID: <3532@rpp386.UUCP>
Date: 3 Jul 88 17:04:34 GMT
Organization: Big "D" Home for Wayward Hackers
Lines: 84
[ Sorry for the wide posting. This really is very important ]
Below is a copy of a letter which was received recently from AT&T. This
letter explains the status of the ``Public Domain'' YACC which I
recently posted about. Because of the incredible speed (heavy sarcasm)
with which the USMail delivers letters, I didn't receive the delivery
notice until last week. You should receive this posting before O. L.
Wilson receives his signed and dated letter back via U. S. Mail.
One interesting thing about this letter, the city in the address was
listed as Renner, which is the same city South Western Bell thinks I
live in for billing purposes. Renner ceased to exist several years ago
when Dallas annexed it. How do you think AT&T found out where I live?
Frightening isn't it? Especially when you consider the correct address
is given in the UUCP maps? ;-) ;-) ;-).
Immediately after the letter is a list of systems which may have
received a copy of YACC via anonymous UUCP. Please check that your
system is not listed, and if it is, that you do not have a copy of this
software on your machine. Unfortunately I don't have the logs going
back this far, but if your machine is listed, it has been in contact
with rpp386 at some time during the period when YACC was available.
Some of the machines are within the AT&T system, please, I don't have
time to check the organization each machine belongs to. If you are an
AT&T source licensee, you obviously don't have to worry. I think ...
Also, the system names have been truncated to seven characters, courtesy
of UUCP and the R_stat file. If you system name matches one listed
below to seven characters, please consider your system to have been
included in the list below.
Thanks,
- John.
--
Dear Mr. Haugh:
There was a netnews article on April 19, 1988 announcing
that you had a list of files that [ are ] public domain. One
of the files listed [ was ] YACC. YACC is not public domain
software. The software is AT&T's intellectual property
obtainable by licensing only.
We must have your assurance that you have ceased
distributing copies of YACC and that you have destroyed all
copies in your possession.
You may certify that you have ceased making and/or
distributing copies of YACC and that you have destroyed all
copies of the software in your possession by signing and
dating the attached copy of this letter in the spaces
provided therefor and returning such copy to us. If we
receive such signed and dated copy within thirty (30) days,
we will consider the matter closed.
Very truly yours,
(signed) O L Wilson
--
FCPS IrsXeni ajmsys alice aquinas arcoexr atina atlpyr
base16 basis bbussc bby-bc bellboy bigtex bms-at boake2
bpa bradley brave brcbkly brspyr1 bsadrc camber catuc
ccd700 cesbws cimcor cline01 cloud9 cocktri cognos comdesi
convex coplex corpane cp1 crdos1 crlabs cronus csccat
daisy dalsqnt daver deincr dhPC-AT dhpcat didsgn entropy
fasolt fbmtl fmsrl5 fmsrl7 frito ganglio gcfast gort
grc gsg gunnix happym hombre hpxcnca htsrmx htwoo
jarsun1 jassys jlsoft jmdst joshua killer kontron lan000
ldcx25 lngnck loci lotus madnix magnus marob mcl
merk mipseas mjbtn mmd2 mpuls1 mpx1 ninja nsacray
obiwan oncoast ontenv otishq ozdaltx pigs pollux qetzal
raider rcf reason redwood rush sauron schen sherpa1
sialis simon skipnyc smergol soft21 spdyne spked srhqla
stanton sulaco swlabs t9103 tau-cet tegan tester texsun
tness5 tness7 top toplog ttdcl1 u-word ucmsa upcjsd
uxcmb validea vector vijit viusys warble watabox wiuaz
wybbs xenix28 xenix38 xnxcws yak ssc cdes wjt3pc
xxx spsspyr swbatl hrsw2 infopro ucmdal tanelor mrmarx
akinsol oss410 celerit elan rocky ateng n0atp ptisea
comnet3 dms-at heaven csiris imsys sfkwj motown banana
mp386 dsix2
--
John F. Haugh II +--------- Cute Chocolate Quote ---------
HASA, "S" Division | "USENET should not be confused with
UUCP: killer!rpp386!jfh | something that matters, like CHOCOLATE"
DOMAIN: j...@rpp386.uucp | -- with my apologizes
Path: utzoo!attcan!uunet!husc6!mailrus!ames!killer!csccat!loci
From: l...@csccat.UUCP (Chuck Brunow)
Newsgroups: news.admin,news.sysadmin,comp.sources.wanted,comp.sources.d,
comp.unix.xenix
Subject: Re: Please remove PD-YACC sources from your machine IMMEDIATELY
Keywords: Loose cannon
Message-ID: <1327@csccat.UUCP>
Date: 4 Jul 88 07:20:01 GMT
References: <3532@rpp386.UUCP>
Reply-To: c...@loci.uucp (CLBrunow)
Followup-To: news.sysadmin
Organization: Loci Products
Lines: 62
In article <3...@rpp386.UUCP> j...@rpp386.UUCP (John F. Haugh II) writes:
>[ Sorry for the wide posting. This really is very important ]
This is an incredible botch!
>
>Below is a copy of a letter which was received recently from AT&T. This
>letter explains the status of the ``Public Domain'' YACC which I
>recently posted about.
BTW, you checked his copyright?
>
>Immediately after the letter is a list of systems which may have
>received a copy of YACC via anonymous UUCP. Please check that your
>system is not listed, and if it is, that you do not have a copy of this
>software on your machine.
I checked. It is. I don't. But why am I listed with the entire
who's who? Did I have anything whatsoever to do with this mess?
NO! And I really don't like lists like this a bit.
> Unfortunately I don't have the logs going
>back this far, but if your machine is listed, it has been in contact
>with rpp386 at some time during the period when YACC was available.
Why the confession? Actions speak louder still. This is an
ignorant hachet-job you call administration. I wouldn't care
if you'd leave me out of it, but you want to play at name-dropping,
"oooo look kiddies, all these connections", and link everyone with
your foul-up.
>Some of the machines are within the AT&T system, please, I don't have
>time to check the organization each machine belongs to. If you are an
>AT&T source licensee, you obviously don't have to worry. I think ...
>Also, the system names have been truncated to seven characters, courtesy
>of UUCP and the R_stat file. If you system name matches one listed
>below to seven characters, please consider your system to have been
>included in the list below.
>
Just what are you trying to say? Everyone who has access by
any means (anon uucp, PC Pursuit) is touched. Why do you
feel compelled to be so grandious? Did your dog die or something?
>Thanks,
>- John.
>DOMAIN: j...@rpp386.uucp | -- with my apologizes
In the recent past, you have posted personal attacks against
other SA's, issued groups and threatened more in areas yet
unresolved, and now this jesture. Are you sure you can handle
a great big 386 all by yourself? Maybe you need training wheels?
Why do you keep changing your names? Are you
embarrassed to go by one name and live with what you say?
Are you getting set-up to pull a bone-head JJ stunt?
Why don't you just tell us what's next so we can avoid the
rush to dis-connect.
--
CLBrunow - KA5SOF
Loci Products, POB 833846-131, Richardson, Texas 75083
c...@loci.uucp, l...@killer.uucp, l...@csccat.uucp
Path: utzoo!attcan!uunet!husc6!cmcl2!nrl-cmf!ames!killer!vector!rpp386!jfh
From: j...@rpp386.UUCP (John F. Haugh II)
Newsgroups: comp.sources.d,comp.unix.xenix,news.admin
Subject: Re: Please remove PD-YACC sources from your machine IMMEDIATELY
Summary: Why so upset, Chuck?
Keywords: have you ever seen me really pissed off?
Message-ID: <3577@rpp386.UUCP>
Date: 5 Jul 88 14:51:44 GMT
References: <3532@rpp386.UUCP> <1327@csccat.UUCP>
Reply-To: c...@loci.uucp
Organization: Toy Machine Guns for Tots
Lines: 101
Name: Evil Dictator of the Dog Universe
In article <1...@csccat.UUCP>, l...@csccat.UUCP (Chuck Brunow) writes:
> In article <3...@rpp386.UUCP> j...@rpp386.UUCP (John F. Haugh II) writes:
> >[ Sorry for the wide posting. This really is very important ]
>
> This is an incredible botch!
why? you managed to see it. i suspect most of the systems on that
list will have someone there who managed to see it. in particular,
since those groups are where the instructions for accessing the system
are posted.
> BTW, you checked his copyright?
i don't think mr. wilson will mind one bit. i would even go so far as
saying it would be in at&t's best interest for that letter to be broadcast.
> >Immediately after the letter is a list of systems which may have
> >received a copy of YACC via anonymous UUCP.
>
> I checked. It is. I don't. But why am I listed with the entire
> who's who? Did I have anything whatsoever to do with this mess?
> NO! And I really don't like lists like this a bit.
have you had access to this machine? yes. could you have picked up the
sources? yes. have you been notified to remove them? yes. i think
i covered my ass pretty well. and i don't care if you don't like it.
> I wouldn't care
> if you'd leave me out of it, but you want to play at name-dropping,
> "oooo look kiddies, all these connections", and link everyone with
> your foul-up.
no, but if you'd like me to play ``oooo look kiddies, all these connections'',
i could post a few dozen more names. by nature this system has gobs of
connections. did anyone not know that??? is anyone amazed??? does anyone
really care???
> Just what are you trying to say? Everyone who has access by
> any means (anon uucp, PC Pursuit) is touched. Why do you
> feel compelled to be so grandious? Did your dog die or something?
i thought it was obvious. but then you have been trying to bully the net
about with your recent arrival anyhow. and no, i don't own a dog. are
you trying to out do even my reputation?
> Are you sure you can handle
> a great big 386 all by yourself? Maybe you need training wheels?
well, i don't know. let's see what you have.
#N loci
#S AT&T 7300 ; Unix SysV, v3.0
#O Loci Products
#C Charles L. Brunow
hummm. are you sure you can handle a four year old obsolete 68010?
and what exactly was the clock rate on that unix-pc of yours? maybe
we should discuss MIPS. and what was the baud rate on that modem?
something like 1200? please, don't be a complete asshole, chuck.
your assholeyness starts to show when you attack a man's computer
and dog. next are we going to play `` my brother can beat up your
brother '', or are you just going to take your ball and go home?
> Why do you keep changing your names?
because i feel like it.
> Are you
> embarrassed to go by one name and live with what you say?
nope. would you like me to repeat something i said?
> Are you getting set-up to pull a bone-head JJ stunt?
hummm. i feel it in my bones ... a bone-head jj stunt ..... hmmmmmm.
> Why don't you just tell us what's next so we can avoid the
> rush to dis-connect.
nope. you've already been disconnected. i don't think you have any
more worries. i suspect you will also discover that you can't get
connected. even using the anonymous uucp login. i will also soon
be working on an anti-loci program. i was going to use it just for
keeping obnoxious fools out of here, but i suppose i can add loci.uucp
to the list.
> CLBrunow - KA5SOF
> Loci Products, POB 833846-131, Richardson, Texas 75083
> c...@loci.uucp, l...@killer.uucp, l...@csccat.uucp
remember that name boys and girls. would you buy a product from this
bozo? and may the russian woodpecker infest your radio shack and set
up permanent residence in your earphone. oh, yes, since we are obviously
trading insults, may all of your cq's go unanswered.
- john.
--
John F. Haugh II +--------- Cute Chocolate Quote ---------
HASA, "S" Division | "USENET should not be confused with
UUCP: killer!rpp386!jfh | something that matters, like CHOCOLATE"
DOMAIN: j...@rpp386.uucp | -- with my apologizes
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!
mailrus!ames!killer!pollux!dalsqnt!rpp386!jfh
From: j...@rpp386.UUCP (John F. Haugh II)
Newsgroups: news.admin,comp.sources.wanted,comp.sources.d
Subject: Re: Please remove PD-YACC sources from your machine IMMEDIATELY
Summary: BISON will show up Real Soon Now(tm)
Message-ID: <3593@rpp386.UUCP>
Date: 6 Jul 88 00:29:22 GMT
References: <3532@rpp386.UUCP>
Organization: Big "D" Home for Wayward Hackers
Lines: 18
Arg. Some people have written to express their dismay at the removal of
YACC. I have obtained the GNU BISON sources and will soon have them up
and running here. If you aren't familiar with GNU, it is a YACC
replacement. My understanding is that BISON is better than YACC. You
will get to be the judge.
Also, the story continues. The YACC in question was the DECUS YACC. If
you have any information concerning licensing restrictions on that YACC,
please let me know. I am sending a tape containing the source off to
AT&T for their inspection but would still appreciate a second opinion.
- John.
--
John F. Haugh II +--------- Cute Chocolate Quote ---------
HASA, "S" Division | "USENET should not be confused with
UUCP: killer!rpp386!jfh | something that matters, like CHOCOLATE"
DOMAIN: j...@rpp386.uucp | -- with my apologizes
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!
mailrus!ames!killer!pollux!dalsqnt!rpp386!jfh
From: j...@rpp386.UUCP (John F. Haugh II)
Newsgroups: comp.org.decus
Subject: What is the status of DECUS YACC?
Message-ID: <3594@rpp386.UUCP>
Date: 6 Jul 88 00:30:54 GMT
Organization: Big "D" Home for Wayward Hackers
Lines: 12
Greetings NetLanders.
I have received a letter from AT&T claiming that the DECUS YACC is
property of AT&T. Could any of you clue me in on the exact ownership
and copying restrictions on it?
- John.
--
John F. Haugh II +--------- Cute Chocolate Quote ---------
HASA, "S" Division | "USENET should not be confused with
UUCP: killer!rpp386!jfh | something that matters, like CHOCOLATE"
DOMAIN: j...@rpp386.uucp | -- with my apologizes