> It seems that nroff had the ability to show underlined text very early
Pre-Unix roff had the .ul request. Thus I expect (but haven't checked)
that it was in Unix roff. It would be very surprising if nroff, which was
intended to be more capable that roff, didn't have some underlining
facility right from the start.
Doug
Unix was what the authors wanted for a productive computing environment,
not a bag of everything they thought somebody somewhere might want.
One objective, perhaps subliminal originally, was to make program
behavior easy to reason about. Thus pipes were accepted into research
Unix, but more general (and unruly) IPC mechanisms such as messages
and events never were.
The infrastructure had to be asynchronous. The whole point was to
surmount that difficult model and keep everyday programming simple.
User visibility of asynchrony was held to a minimum: fork(), signal(),
wait(). Signal() was there first and foremost to support SIGKILL; it
did not purport to provide a sound basis for asynchronous IPC.
The complexity of sigaction() is evidence that asynchrony remains
untamed 40 years on.
Doug
Hi All.
Here is BWK's contribution.
| Date: Thu, 24 Sep 2015 17:28:21 -0400 (EDT)
| From: Brian Kernighan <bwk(a)cs.princeton.edu>
| To: arnold(a)skeeve.com
| Subject: Re: please get out your flash light...
|
| Some answers interpolated, but lots remain mysteries...
|
| On Thu, 24 Sep 2015, arnold(a)skeeve.com wrote:
|
| > Hi. Can you shed some light?
| >
| >> From: Diomidis Spinellis <dds(a)aueb.gr>
| >> To: tuhs(a)minnie.tuhs.org
| >> Date: Thu, 24 Sep 2015 12:27:03 +0300
| >> Subject: [TUHS] Questions regarding early Unix contributors
| >>
| >> I found out that the book "Life with Unix" by Don Libes and Sandy
| >> Ressler has a seven page listing of Unix notables, and I'm using that to
| >> fill gaps in the contributors of the Unix history repository [1,2].
| >> Working through the list, the following questions came up.
| >>
| >> - Lorinda Cherry is credited with diction. But diction.c first appears
| >> in 4BSD and 2.10BSD. Did Lorinda Cherry implement it at Berkeley?
|
| Nina Macdonald, maybe? Lorinda worked with people in that group.
|
| >> - Is Chuck Haley listed in the book as the author of tar the same as
| >> Charles B. Haley who co-authored V7 usr/doc/{regen,security,setup}? He
| >> appears to have worked both at Bell labs (tar, usr/doc/*) and at
| >> Berkeley (ex, Pascal). Is this correct?
|
| I think so.
|
| >> - Andrew Koenig is credited with varargs. This is a four-line header
| >> file in V7. Did he actually write it?
| >>
| >> - Ted Dolotta is credited with the mm macros, but the document "Typing
| >> Documents with MM is written by by D. W. Smith and E. M. Piskorik. Did
| >> its authors only write the documentation? Did Ted Dolotta also write
| >> mmcheck?
|
| I don't think Ted wrote -mm; he might have been the manager of that
| group? Ask him: ted(a)dolotta.org
|
| >> Also, I'm missing the login identifiers for the following people. If
| >> anyone remembers them, please send me a note.
| >>
| >> Bell Labs, PWB, USG, USDL:
|
| ark
|
| >> Andrew Koenig
| >> Charles B. Haley
| >> Dick Haight
|
| Maybe rhaight, but don't quote me. Last address I have is from
| long ago: rhaight(a)jedi.accn.org
|
| >> Greg Chesson
|
| Can't remember whether it was grc or greg
|
| >> Herb Gellis
| >> Mark Rochkind
|
| You probably mean Marc J Rochkind. I think it was mmr, but
| ask him: rochkind(a)basepath.com
|
| >> Ted Dolotta
| >>
| >> BSD:
| >> Bill Reeves
| >> Charles B. Haley
| >> Colin L. Mc Master
| >> Chris Van Wyk
|
| Was Chris ever part of BSD? He was at Stanford, then Bell Labs,
| where he was cvw.
|
| >> Douglas Lanam
| >> David Willcox
| >> Eric Schienbrood
| >> Earl T. Cohen
| >> Herb Gellis
| >> Ivan Maltz
| >> Juan Porcar
| >> Len Edmondson
| >> Mark Rochkind
|
| See above
|
| >> Mike Tilson
| >> Olivier Roubine
| >> Peter Honeyman
|
| honey (remember honeydanber?
|
| >> R. Dowell
| >> Ross Harvey
| >> Robert Toxen
| >> Tom Duff
|
| td
|
| >> Ted Dolotta
| >> T. J. Kowalski
|
| frodo
|
| >> Finally, I've summarized all contributions allocated through file path
| >> regular expressions [3] into two tables ordered by author [4]. (The
| >> summary is auto-generated by taking the last significant part of each
| >> path regex.) If you want, please have a look at them and point out
| >> omissions and mistakes.
| >>
| >> I will try to commit all responses I receive with appropriate credit to
| >> the repository. (You can also submit a GitHub pull-request, if you prefer.)
| >>
| >> [1] https://github.com/dspinellis/unix-history-repo
| >> [2]
| >> http://www.dmst.aueb.gr/dds/pubs/conf/2015-MSR-Unix-History/html/Spi15c.pdf
| >> [3]
| >> https://github.com/dspinellis/unix-history-make/tree/master/src/author-path
| >> [4] http://istlab.dmst.aueb.gr/~dds/contributions.pdf
| >>
| >> Diomidis
| >> _______________________________________________
| >> TUHS mailing list
| >> TUHS(a)minnie.tuhs.org
| >> https://minnie.tuhs.org/mailman/listinfo/tuhs
I can assure you that Lorinda Cherry wrote most of the important
code in WWB, including style and diction. The idea for them
came from Bill Vesterman at Rutgers. Lorinda already had parts,
a real tour de force, which assigned parts of speech to words
in a text. Style was the killer app for parts and was running
within days of his approach to the labs wondering whether
such a thing could be built. Lorinda also wrote deroff, which
these tools of course needed. WWB per se was packaged by
USDL; I am sorry I can't remember the name of the guiding
spirit. So Lorinda's code detoured through there on its
way into research Unix.
Chris van Wyk was cvw. He was at Bell Labs, not BSD.
Chuck Haley is indeed Charles B. Haley.
Andy Koenig was ark.
A few scattered answers, some redundant with those of others:
-- Lorinda Cherry (llc) worked at Bell Labs. She wrote diction (and
the rest of the Writer's Workbench tools) there, in the early
1980s; if some people saw it first in BSD releases that is just
an accident of timing (too late for V7) and exposure (I'm pretty
sure it was available in the USG systems, which weren't generally
accessible until a year or two later).
Lorinda is one of the less-known members of the original Computer
Science Research Center who nevertheless wrote or co-wrote a lot
of things we now take for granted, like dc and bc and eqn and
libplot.
Checking some of this on the web, I came across an interesting
tidbit apparently derived from an interview with Lorinda:
http://www.princeton.edu/~hos/frs122/precis/cherry2.htm
I wholly endorse what she says about UNIX and the group it came from.
One fumble in the text: `Bob Ross' who liked to break programs is
surely really Bob Morris.
-- So far as I know, Tom Duff (td) was never at Berkeley. He's
originally from Toronto; attended U of T; was at Lucasfilm for a
while (he has a particular interest in graphics, though he is a
very sharp and subtle programmer in general); started at Bell Labs
in 1984, not long before I did. He left sometime in the 1990s,
lives in Berkeley CA, but works neither at UCB nor at Google but
at Pixar.
-- T. J. Kowalski (frodo) was at Bell Labs; when I was there he
worked in the research group down the hall (Acoustics, I think), with
whom Computer Science shared a lot of UNIX-releasted stuff. Ted is
well-known for his work on fsck, but did a lot of other stuff, including
being the first to get Research UNIX to work on the MicroVAX II. He
also had a high-quality mustache.
-- Andrew Koenig (ark) was part of the Computer Science group when
I was there in the latter 1980s. He was a early adopter of C++.
asd, the automatic-software distributor we used to keep the software
in sync on the 20-or-so systems that ran Research UNIX, was his work.
-- Mike Tilson was, I think, one of the founders of HCR (Human Computing
Resources), a UNIX-oriented software company based in Toronto in the
early 1980s. The company was later acquired by SCO, in the days when
SCO was still a technical company rather than a den of lawyers.
-- Peter Honeyman (honey) was never, I think, at Berkeley, though
he is certainly of the right character. In the 1980s he was variously
(sometimes concurrently?) working for some part of AT&T and at Princeton.
For many years now he has been in Ann Arbor MI at the University of
Michigan, where his still-crusty manner appears not to interfere with
his being a respected researcher and much-liked teacher.
Norman Wilson
Toronto ON
(Bell Labs Computing Science Research, 1984-1990)
I found out that the book "Life with Unix" by Don Libes and Sandy
Ressler has a seven page listing of Unix notables, and I'm using that to
fill gaps in the contributors of the Unix history repository [1,2].
Working through the list, the following questions came up.
- Lorinda Cherry is credited with diction. But diction.c first appears
in 4BSD and 2.10BSD. Did Lorinda Cherry implement it at Berkeley?
- Is Chuck Haley listed in the book as the author of tar the same as
Charles B. Haley who co-authored V7 usr/doc/{regen,security,setup}? He
appears to have worked both at Bell labs (tar, usr/doc/*) and at
Berkeley (ex, Pascal). Is this correct?
- Andrew Koenig is credited with varargs. This is a four-line header
file in V7. Did he actually write it?
- Ted Dolotta is credited with the mm macros, but the document "Typing
Documents with MM is written by by D. W. Smith and E. M. Piskorik. Did
its authors only write the documentation? Did Ted Dolotta also write
mmcheck?
Also, I'm missing the login identifiers for the following people. If
anyone remembers them, please send me a note.
Bell Labs, PWB, USG, USDL:
Andrew Koenig
Charles B. Haley
Dick Haight
Greg Chesson
Herb Gellis
Mark Rochkind
Ted Dolotta
BSD:
Bill Reeves
Charles B. Haley
Colin L. Mc Master
Chris Van Wyk
Douglas Lanam
David Willcox
Eric Schienbrood
Earl T. Cohen
Herb Gellis
Ivan Maltz
Juan Porcar
Len Edmondson
Mark Rochkind
Mike Tilson
Olivier Roubine
Peter Honeyman
R. Dowell
Ross Harvey
Robert Toxen
Tom Duff
Ted Dolotta
T. J. Kowalski
Finally, I've summarized all contributions allocated through file path
regular expressions [3] into two tables ordered by author [4]. (The
summary is auto-generated by taking the last significant part of each
path regex.) If you want, please have a look at them and point out
omissions and mistakes.
I will try to commit all responses I receive with appropriate credit to
the repository. (You can also submit a GitHub pull-request, if you prefer.)
[1] https://github.com/dspinellis/unix-history-repo
[2]
http://www.dmst.aueb.gr/dds/pubs/conf/2015-MSR-Unix-History/html/Spi15c.pdf
[3]
https://github.com/dspinellis/unix-history-make/tree/master/src/author-path
[4] http://istlab.dmst.aueb.gr/~dds/contributions.pdf
Diomidis
> From: Clem Cole
> Eric Schienbrood
> .. Noel might remember his MIT moniker
No, alas; and I tried 'finger Schienbrood(a)lcs.mit.edu' and got no result.
Maybe he was in some other part of MIT, not Tech Sq?
> From: Arnold Skeeve
> Here too I think stuff written at ATT got out through Berkeley. (SCCS)
That happened at MIT, too - we had SCCS quite early (my MIT V6 manual has
it), plus all sorts of other stuff (e.g. TROFF).
I think some of it may have come through Jon Sieber, who, while he was in high
school, had been part of (IIRC) a Scout troop which had some association with
Bell Labs, and continued to have contacts there after he became an MIT
undergrad.
Noel
> From: Peter Jeremy <peter(a)rulingia.com>
> Why were the original read(2) and write(2) system calls written to
> offer synchronous I/O only?
A very interesting question (to me, particularly, see below). I don't think
any of the Unix papers answer this question?
> It's relatively easy to create synchronous I/O functions given
> asynchronous I/O primitives but it's impossible to do the opposite.
Indeed, and I've seen operating systems (e.g. a real-time PDP-11 OS I worked
with a lot called MOS) that did that.
I actually did add asynchronous I/O to V6 UNIX, for use with very early
Internet networking software being done at MIT (in a user process). Actually,
it wasn't just asynchronous, it was _raw_ asynchronous I/O! (The networking
device was DMA, and the s/w did DMA directly into the user process' memory.)
The code also allowed more than one outstanding I/O request, too. (So the
input could be re-enabled on the device ASAP, without having to wake up a
process, have it run, do a new read call, etc.)
We didn't redo the whole Unix I/O system, to support/use asyn I/O throughout,
though; I just kind of warted it onto the side. (IIRC, it notified the user
process via a signal that the I/O had completed; the user software then had
to do an sgtty() call to get the transfer status, size, etc.)
Anyway, back to the original topic: I don't want to speculate (although I
could :-); perhaps someone who was around 'back then' can offer some insight?
If not, time for speculation! :-)
Noel
Why were the original read(2) and write(2) system calls written to offer
synchronous I/O only? It's relatively easy to create synchronous I/O
functions given asynchronous I/O primitives but it's impossible to do the
opposite.
Multics (at least) supported asynchronous I/O so the concept wasn't novel.
And any multi-tasking kernel has to support asynchronous I/O internally so
suitable code exists in the kernel.
--
Peter Jeremy
As I was dropping off to sleep last night, I wondered why the superuser
account on Unix is called root.
There's a hierarchy of directories and files beginning at the tree root /.
There's a hierarchy of processes rooted with init. But there's no hierarchy
of users, so why the moniker "root"?
Any ideas?
Cheers, Warren
> Did any Unix or Unix like OS ever zero fill on realloc?
> On zero fill, I doubt many did that. Many really early on when memory
> was small.
This sparks rminiscence. When I wrote an allocation strategy somewhat
more sophisticated than the original alloc(), I introduced realloc() and
changed the error return from -1 to the honest pointer value 0. The
latter change compelled a new name; "malloc" has been with us ever since.
To keep the per-byte cost of allocation low, malloc stuck with alloc's
nonzeroing policy. The minimal extra code to handle calls that triggered
sbrk had the startling property that five passes through the arena might
be required in some cases--not exactly scalable to giant virtual address
spaces!
It's odd that the later introduction of calloc() as a zeroing malloc()
has never been complemented by a similar variant of realloc().
> Am I the only one that remembers realloc() being buggy on some systems?
I've never met a particular realloc() bug, but realloc does inherit the
portability bug that Posix baked into malloc(). Rob Pike and I
requested that malloc(0) be required to return a pointer distinct from
any live pointer. Posix instead allowed an undefined choice between
that behavior and an error return, confounding it with the out-of-memory
indication. Maybe it's time to right the wrong and retire "malloc".
The name "alloc" might be recycled for it. It could also clear memory
and obsolete calloc().
Doug
Dave Horsfall:
Today is The Day of the Programmer, being the 0x100'th day of the year.
===
Are you sure you want to use that radix as your standard?
You risk putting a hex on our profession.
Norman Wilson
Toronto ON
> Today is The Day of the Programmer, being the 0x100'th day of the year.
Still further off topic, but it reminds me of a Y2K incident circa 1960.
Our IBM 7090 had been fitted with a homegrown time-of-day clock (no, big
blue did not build such into their machines back then). The most significant
bits of the clock registered the day of the year. On day 0x100 the clock
went negative and the system went wild.
Doug
Hi there,
we just restored our PDP-11/23+ rebulding a new PSU around a
normal PC PSU and creating the real time clock needed for some
OS.
we're wondering about what UNIX can eventually run on it :)
http://museo.freaknet.org/en/restauro-pdp1123plus/
bye,
Gabriele
--
[ ::::::::: 73 de IW9HGS : http://freaknet.org/asbesto ::::::::::: ]
[ Freaknet Medialab :: Poetry Hacklab : Dyne.Org :: Radio Cybernet ]
[ NON SCRIVERMI USANDO LETTERE ACCENTATE - NON MANDARMI ALLEGATI ]
[ *I DELETE* EMAIL > 100K, ATTACHMENTS, HTML, M$-WORD DOC and SPAM ]
Today is The Day of the Programmer, being the 0x100'th day of the year.
Take a bow, all programmers...
Did you know that it's an official professional holiday in Russia?
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
I'll support shark-culling when they have been observed walking on dry land.
On Thu, 10 Sep 2015, Norman Wilson wrote:
> #$%^&*\{{{
>
> NO CARRIER
>
> +++
> ATH
My favourite would be:
+++
(pause - this was necessary)
ATZ
I.e. a reset.
I think there were even worse ones in the Hayes codes, like ATH3 or
something. Dammit, but mental bit-rot is setting in.
Of course, I never did such an evil thing, your honour... Honest! Never!
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
I'll support shark-culling when they have been observed walking on dry land.
I've used realloc a lot, and never run into bugs. Maybe I've just
been lucky, or maybe it's that I probably didn't use it that much
until the latter 1980s, and then more with pukka Doug malloc code
than with the stuff floating around elsewhere.
Never mind that sometime around 1995 I found a subtle bug in the
pukka Doug malloc (not realloc): arena blew up badly when presented
with a certain pattern of alternating small and large allocs and frees,
produced by a pukka Brian awk regression test. I had a lot of (genuine)
fun tracking that down, writing some low-level tools to extract the
malloc and free calls and sizes and then a simulator in (what else?)
awk to test different fixes. Oh, for the days when UNIX was that
simple.
I've never heard before of a belief that the new memory belonging
to realloc is always cleared, except in conjunction with the utterly-
mistaken belief that that's true of malloc as well. I don't think it
was ever promised to be true, though it was probably true by accident
just often enough (just as often as with malloc) to fool the careless.
Norman Wilson
Toronto ON
I’ve just had a discussion with my boss about this and he claimed that it did at one point and I said it hasn’t in all the unix versions I’ve ever played with (v6, v7, sys III, V, BSD 2, 3, 4, SunOS and Solaris).
My question to this illustrious group is: Did any Unix or Unix like OS ever zero fill on realloc?
David
I never used realloc(), only malloc() and calloc().
Checking a few unixes I have access to all reallocs() seem to state
either nothing on contents of memory added or state explicitly
'undefined'.
The only function which zeroes allocated memory is calloc() it seems.
Unixes checks: SCO UNIX 3.2V4.2, Digital Unix 4.0G, Tru64 Unix V5.1B,
HP-UX 11.23, HP-UX 11.31
Cheers
On 9/11/15, tuhs-request(a)minnie.tuhs.org <tuhs-request(a)minnie.tuhs.org> wrote:
> Send TUHS mailing list submissions to
> tuhs(a)minnie.tuhs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://minnie.tuhs.org/mailman/listinfo/tuhs
> or, via email, send a message with subject or body 'help' to
> tuhs-request(a)minnie.tuhs.org
>
> You can reach the person managing the list at
> tuhs-owner(a)minnie.tuhs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of TUHS digest..."
>
>
> Today's Topics:
>
> 1. Did realloc ever zero the new memory? (David)
> 2. Re: Did realloc ever zero the new memory? (Jim Capp)
> 3. Re: Did realloc ever zero the new memory? (David)
> 4. Re: Did realloc ever zero the new memory? (Larry McVoy)
> 5. Re: Did realloc ever zero the new memory? (David)
> 6. Re: Did realloc ever zero the new memory? (Larry McVoy)
> 7. Re: Did realloc ever zero the new memory? (Clem Cole)
> 8. Re: Did realloc ever zero the new memory? (Dave Horsfall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 10 Sep 2015 12:52:45 -0700
> From: David <david(a)kdbarto.org>
> To: tuhs(a)minnie.tuhs.org
> Subject: [TUHS] Did realloc ever zero the new memory?
> Message-ID: <E798E102-2C50-4AB2-92CC-188D05AA951F(a)kdbarto.org>
> Content-Type: text/plain; charset=utf-8
>
> I?ve just had a discussion with my boss about this and he claimed that it
> did at one point and I said it hasn?t in all the unix versions I?ve ever
> played with (v6, v7, sys III, V, BSD 2, 3, 4, SunOS and Solaris).
>
> My question to this illustrious group is: Did any Unix or Unix like OS ever
> zero fill on realloc?
>
> David
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 10 Sep 2015 16:10:41 -0400 (EDT)
> From: Jim Capp <jcapp(a)anteil.com>
> To: david(a)kdbarto.org
> Cc: tuhs(a)minnie.tuhs.org
> Subject: Re: [TUHS] Did realloc ever zero the new memory?
> Message-ID: <5962857.12872.1441915841364.JavaMail.root@zimbraanteil>
> Content-Type: text/plain; charset="utf-8"
>
> On every system that I've ever used, I believe that realloc did not do a
> zero fill. There might have been a time when malloc did a zero fill, but I
> never counted on it. I always performed a memset or bzero after a malloc.
> I'm pretty sure that I counted on realloc to NOT perform a zero fill.
>
>
> $.02
>
>
>
> From: "David" <david(a)kdbarto.org>
> To: tuhs(a)minnie.tuhs.org
> Sent: Thursday, September 10, 2015 3:52:45 PM
> Subject: [TUHS] Did realloc ever zero the new memory?
>
> I?ve just had a discussion with my boss about this and he claimed that it
> did at one point and I said it hasn?t in all the unix versions I?ve ever
> played with (v6, v7, sys III, V, BSD 2, 3, 4, SunOS and Solaris).
>
> My question to this illustrious group is: Did any Unix or Unix like OS ever
> zero fill on realloc?
>
> David
>
> _______________________________________________
> TUHS mailing list
> TUHS(a)minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
Can't say much more, really...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Concerned about shark attacks? Then don't go swimming in their food bowl...
---------- Forwarded message ----------
From: Jim Haynes
Cc: greenkeys(a)mailman.qth.net
Subject: Re: [GreenKeys] Teletype Industrial Design
On Fri, 28 Aug 2015, Jack wrote:
> How were they still applying for patents in 1993?
>
> D332,465 (1993) Sokolowski
>
It was filed for in 1988 and was assigned to AT&T Bell Laboratories.
So I guess that was after what was left of Teletype had gone to
Naperville. And what was left of Bell Labs was still part of AT&T,
before the spinoff of Lucent in 1996.
Incidentally if you google for Bell Laboratories the first thing that
comes up is
Bell Laboratories - Home
www.belllabs.com/
An exclusive manufacturer of rodent control products, Bell Laboratories produces
the highest quality rodenticides and other rodent control products available to
...
Just stirring up the gene pool, so to speak... And who hasn't played
chess with a computer, and caught it cheating?
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer"
RIP Cecil the Lion; he was in pain for two days, thanks to some brave hunter.
---------- Forwarded message ----------
Date: Sat, 15 Aug 2015 16:49:19 -0400
From: Christian Gauger-Cosgrove
To: David Tumey
Cc: GREENKEYS BULLETIN BOARD <greenkeys(a)mailman.qth.net>
Subject: Re: [GreenKeys] TELETYPE Chess Anyone??
On 15 August 2015 at 16:37, David Tumey via GreenKeys
<greenkeys(a)mailman.qth.net> wrote:
> house. I got to play a game of Chess on a Model 33/PDP-?? and it totally
> blew my mind. I knew that I wanted that to be part of my current teletype
You know, the current version of the SIMH emulator can connect to
serial ports now. If you want I can help you setup SIMH's PDP-11
simulator running a PDP-11 UNIX which of course has chess you play. So
that it'll work on your TTY.
Only required information is: "What serial port is your Teletype's
current loop adapter connected?" and "What do you want to run? V6, V7,
Ultrix-11, RT-11 (V4, V5.3, V5.7), RSTS/E (V7, V10.1-L), RSX-11/M+,
DSM-11 (kill it with fire)? All of the above?"
Cheers,
Christian
--
Christian M. Gauger-Cosgrove
STCKON08DS0
Contact information available upon request.
______________________________________________________________
GreenKeys mailing list
Home: http://mailman.qth.net/mailman/listinfo/greenkeys
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:GreenKeys@mailman.qth.net
2002-to-present greenkeys archive: http://mailman.qth.net/pipermail/greenkeys/
1998-to-2001 greenkeys archive: http://mailman.qth.net/archive/greenkeys/greenkeys.html
Randy Guttery's 2001-to-2009 GreenKeys Search Tool: http://comcents.com/tty/greenkeyssearch.html
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Ah hah! My stray memory of `Not War?' must date from my TOPS-10 days.
I can't find a trace of the string `love' anywhere in any of the make
sources in Kirk's multi-CD compendium of historic BSD, so it certainly
can't have been from there.
Norman Wilson
Toronto ON