When I get back to a keyboard I thought maybe it would be nice to share
some Greg stories, I have enough of them. So I'll try and do that.
If anyone wants to do that in person, USENIX ATC is next
week and would be an appropriate venue. Perhaps a Greg
Chesson Memorial BOF?
Norman Wilson
Toronto ON
Much to my surprise I see there isn't a WIKI page on Greg Chesson yet?
Maybe some of his friends get get together on submit one ?
Cheers,
rudi
On 6/30/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. We've lost Greg Chesson (Dave Horsfall)
> 2. Re: We've lost Greg Chesson (Clem Cole)
> 3. Re: We've lost Greg Chesson (Larry McVoy)
> 4. Re: We've lost Greg Chesson (Larry McVoy)
> 5. Re: We've lost Greg Chesson (Mary Ann Horton)
> 6. Re: We've lost Greg Chesson (Norman Wilson)
> 7. Re: We've lost Greg Chesson (Dave Horsfall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 29 Jun 2015 17:30:16 +1000 (EST)
> From: Dave Horsfall <dave(a)horsfall.org>
> To: The Eunuchs Hysterical Society <tuhs(a)tuhs.org>
> Subject: [TUHS] We've lost Greg Chesson
> Message-ID: <alpine.BSF.2.11.1506291728540.96902(a)aneurin.horsfall.org>
> Content-Type: text/plain; charset="utf-8"
>
> Haven't found any more info...
>
> --
> Dave Horsfall (VK2KFU) "Those who don't understand security will suffer"
> http://www.horsfall.org/ It's just a silly little web site, that's all...
>
> ---------- Forwarded message ----------
> Date: Sun, 28 Jun 2015 18:50:42 -0400
> From: Dave Farber
> To: ip <ip(a)listbox.com>
> Subject: [IP] Death of Greg Chesson
>
> ---------- Forwarded message ----------
> From: "Lauren Weinstein"
> Date: Jun 28, 2015 6:43 PM
> Subject: Death of Greg Chesson
> To: <dave(a)farber.net>
> Cc:
>
>
> Dave, fyi.
>
> https://plus.google.com/u/0/+LaurenWeinstein/posts/bRdbj1B1qQG
>
> --Lauren--
> Lauren Weinstein (lauren(a)vortex.com) http://www.vortex.com/lauren
> Founder:
> ?- Network Neutrality Squad: http://www.nnsquad.org
> ?- PRIVACY Forum: http://www.vortex.com/privacy-info
> Co-Founder: People For Internet Responsibility:
> http://www.pfir.org/pfir-info
> Member: ACM Committee on Computers and Public Policy
> Lauren's Blog: http://lauren.vortex.com
> Google+: http://google.com/+LaurenWeinstein
> Twitter: http://twitter.com/laurenweinstein
> Tel: +1 (818) 225-2800 / Skype: vortex.com
>
> Archives [feed-icon-10x10.jpg] | Modify Your Subscription | Unsubscribe Now
> [listbox-logo-small.png]
>
> ------------------------------
>
> Message: 2
> Date: Mon, 29 Jun 2015 07:44:58 -0500
> From: Clem Cole <clemc(a)ccc.com>
> To: Dave Horsfall <dave(a)horsfall.org>
> Cc: The Eunuchs Hysterical Society <tuhs(a)tuhs.org>
> Subject: Re: [TUHS] We've lost Greg Chesson
> Message-ID:
> <CAC20D2MqtPfMe_SdkCfFFthF_5Rth8y2Q6U2xm-ZgbkAA0tQZg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Greg had been sick for a while. Sad loss.
> Clem
>
> On Mon, Jun 29, 2015 at 2:30 AM, Dave Horsfall <dave(a)horsfall.org> wrote:
>
>> Haven't found any more info...
>>
>> --
>> Dave Horsfall (VK2KFU) "Those who don't understand security will
>> suffer"
>> http://www.horsfall.org/ It's just a silly little web site, that's
>> all...
>>
>> ---------- Forwarded message ----------
>> Date: Sun, 28 Jun 2015 18:50:42 -0400
>> From: Dave Farber
>> To: ip <ip(a)listbox.com>
>> Subject: [IP] Death of Greg Chesson
>>
>> ---------- Forwarded message ----------
>> From: "Lauren Weinstein"
>> Date: Jun 28, 2015 6:43 PM
>> Subject: Death of Greg Chesson
>> To: <dave(a)farber.net>
>> Cc:
>>
>>
>> Dave, fyi.
>>
>> https://plus.google.com/u/0/+LaurenWeinstein/posts/bRdbj1B1qQG
>>
>> --Lauren--
>> Lauren Weinstein (lauren(a)vortex.com) http://www.vortex.com/lauren
>> Founder:
>> - Network Neutrality Squad: http://www.nnsquad.org
>> - PRIVACY Forum: http://www.vortex.com/privacy-info
>> Co-Founder: People For Internet Responsibility:
>> http://www.pfir.org/pfir-info
>> Member: ACM Committee on Computers and Public Policy
>> Lauren's Blog: http://lauren.vortex.com
>> Google+: http://google.com/+LaurenWeinstein
>> Twitter: http://twitter.com/laurenweinstein
>> Tel: +1 (818) 225-2800 / Skype: vortex.com
>>
>> Archives [feed-icon-10x10.jpg] | Modify Your Subscription | Unsubscribe
>> Now
>> [listbox-logo-small.png]
>> _______________________________________________
>> TUHS mailing list
>> TUHS(a)minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>>
>
---------- Forwarded message ----------
Subject: Re: [GreenKeys] Replacing Chad, was: Black tape
On Sun, 21 Jun 2015, Jones, Douglas W wrote:
> The flaws in the Votomatic were a bit subtle, but in retrospect, if you
> read the patents for the IBM Portapunch (the direct predecessor of the
> Votomatic) and for the Votomatic, you find that the flaw that was its
> eventual downfall -- at least in the public's mind -- is fully
> documented in the patents. Of course IBM's (and later CESI's, after IBM
> walked away from the Votomatic in the late 1960s) salesmen never
> mentioned those flaws.
Portapunch? Arrgghh!
We had to put up with that Satan-spawn in our University days... Only 40
columns wide, it had specific encodings for FORTRAN words, and it was just
as well that FORTRAN ignored white space (I know this for a fact, when I
fed a deck into a "real" card reader one time).
Being but mere impecunious Uni students and having to actually buy the
things, we resorted to fixing mis-punches by literally sticky-taping the
chads back.
For some reason, the computer operators (IBM 360/50) hated us...
I really do hope that the inventor of Portapunch is still having holes
punched through him with a paper-clip.
Anyone got Plan 9 4th edition manuals or Inferno Manuals? I will be
interested to buy them. Vitanuova used to sell them, but their payment
system is down for years now and has been brought up to Charles many
times, but it seem to be still down, so there is no way to buy it from
them.
--
Ramakrishnan
Hi All.
As mentioned a few weeks ago, I have a full set of the O'Reilly X11 books
from the early 90s.
I'm willing to send them on to a better home for the cost of mailing
from Israel.
One person said they were interested but didn't follow up with me, so
I'm again offering to the list. First one to get back to me wins. :-)
Thanks,
Arnold
Prompted by another thread, I decided to share about some of my
experience with providing printed BSD manuals.
I was given a 4.4BSD set with the understanding that I would work on
preparing new print editions using NetBSD. It was a significant
undertaking. I ended up just doing Section 8 System. Here is a summary
of what I did:
- Build the NetBSD distribution (which gets the manual pages generated
or at least put in place).
- Manual clean up, like remove a link to manual page that wasn't needed
and remove a duplicated manual (in two sub-sections).
- Learned about permuted index (the long KWIC index cross-reference).
Generated a list of characters and terms to ignore for building my
permuted index. Wrote script to generate it, including converting to
LaTeX using longtable. This resulted in 2937 entries and was 68 pages in
printed book.
- Create list of all an section 8 pages, pruned for duplicate inodes.
- Also have a list of 40 filenames of other manpages to include in the
man8 book. These are system maintenance procedures or commands that are
in wrong section or could be section 8 (or weren't installed). (Examples
are ipftest, pkg_admin, postsuper.)
- Generate a sorted list of all the manuals.
- Look for any missing manual pages. Script to check for libexec or sbin
tools not in man8, such as supfilesrv or supscan is really supservers.8
and missing kdigest.8. Get those files in place as needed. I cannot
remember now, but I think I may have wrote some missing manuals or got
others to submit some (officially).
- Script to make sure all man pages are in order. This found some
duplicate manual pages with different inodes, wrong man macro DT values,
wrong filename, wrong sections, etc. Some of these were reported
upstream or fixed.
- Script to create the book as a single huge postscript file, then a
PDF. Reviewed the possible ROFF related errors and warnings.
(On 2009-10-23, it was 1304 pdf pages from 572 manuals.)
- Script to figure out licenses. This was substantial! It looked for
copyright patterns in manual source, excluded junk formatting like
revision control markers, include some extra licenses that weren't
included in the manpage itself (like GPL2). Then another script to
generate LaTeX from the copyrights and licenses. It removed duplicate
license statements and sorted the copyrights. So some license
statements had many copyrights using the same license verbiage.
This represented 620 copyrighted files with approximately 683 copyright
lines and 109 different licenses. Yes 109! That resulted in
approximately 68 printed pages, pages 1461 through 1529. This didn't
duplicate any license verbiage. (I just realized that was the same
length as my permuted index.)
A few things to note: Some authors chose to use different names for
different copyright statements. Some authors used their names or
assigned the copyright to the project. Some licenses included software
or authors names instead of generic terms. Many BSD style licenses were
slightly changed with different grammar, etc. Many contributors created
own license or reworded someone else's existing license text. As an
example: "If it breaks then you get to keep both pieces." :)
The four most common license statements represented 113 "THE REGENTS AND
CONTRIBUTORS" manuals, 75 "THE NETBSD FOUNDATION, INC." manuals, and 35
"IBM" (aka Postfix) manuals, and 30 generic "THE AUTHOR AND
CONTRIBUTORS" manuals.
I found many were missing licenses. I hunted down original authors,
looked in CVS history, etc to help resolve some of these. I also
reported about still missing licenses to the project. We will assume
they meant it is open source and can be distributed since nobody has
complained for years (even prior to my printed work) :)
- Generated a list of required advertising acknowledgments in LaTeX to
import into one printed book (and for webpage).
- Split my long PDF into two volumes. Used LaTeX pdfpages package and
includepdf to include the generated PDFs. I made sure the page numbers
continued in the second book from end of previous volume. (After
printing, I realized a mistake where the second volume had odd numbers
on left pages, but order is still correct, so I assume nobody else
noticed.)
Historically, the System Manager's Manual (SMM) also included other
system installation and administration documentation (in addition to the
manual pages). My work didn't include that documentation (some of which
was unmaintained since 4.4BSD in 1993 and covers some software and
features that are no longer included with NetBSD). That could be another
project.
I only did the SMM / manual section 8. I realized if I did all manuals,
my book set would be well over ten thousand printed pages. The amount of
work and initial printing costs would not be worth it with the little
money it could bring in. It was certainly a learning experience, plus
some benefit such as cleanup of some mandoc/roff code, filename renames,
copyright/license additions, and manual pages added.
Jeremy C. Reed
echo 'EhZ[h ^jjf0%%h[[Zc[Z_W$d[j%Xeeai%ZW[ced#]dk#f[d]k_d%' | \
tr '#-~' '\-.-{'
I recently came across this:
http://www.cs.princeton.edu/~bwk/202
It's been there for a while but I hadn't noticed it. It describes the
trials and tribulations of getting the Mergenthaler 202 up and running
at Bell Labs and is very interesting reading.
I have already requested that they archive their work with TUHS and
gotten a positve response about this from David Brailsford. In the
meantime, it's fun reading!
Enjoy,
Arnold
I noticed that the assembly source file for blackjack is missing from
the source tree so I tried to recreate it, so far unsuccessfully.
My first idea was to grab bj.s from 2.11BSD and assemble it the Unix
v5 as command. That seems to generate a bunch of errors. Also other
assembly source files don't seem to have .even in them.
Another idea would be generate the source code from the executable
itself, but there doesn't seem to be a disassembler for early Unix.
It's possible that v5 bj.s was printed out somewhere but so far no
luck finding it.
Mark
