TUHS

tuhs@tuhs.org

28 participants
6556 discussions

by Dave Horsfall

So me, being an uber-geek, tried it on a few boxen again... On the Mac: ozzie:~ dave$ make love make: *** No rule to make target `love'. Stop. Boring... On FreeBSD: aneurin% make love Not war. Thank you for keeping the faith! And on my tame penguin: dave@debbie:~$ make love -bash: make: command not found Sigh... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." Watson never said: "I think there is a world market for maybe five computers."

10 years

Re: [TUHS] Make love

by Nemo

On 30 July 2015 at 17:11, Norman Wilson <norman(a)oclsc.org> wrote: > My vague memory is that the original make, e.g. in V7, printed > `Don't know how to make love.' This was not a special case: > `don't know how to make XXX' was the normal message. > > There was a variant make that printed > Not war? > if asked to make love without explicit instructions. I thought > that appeared in 3BSD or 4BSD, but I could be mistaken. On Solaris 10, /usr/css/bin/make reports: make: Fatal error: Don't know how to make target `love' N.

10 years

Re: [TUHS] Make love

by Norman Wilson

My vague memory is that the original make, e.g. in V7, printed `Don't know how to make love.' This was not a special case: `don't know how to make XXX' was the normal message. There was a variant make that printed Not war? if asked to make love without explicit instructions. I thought that appeared in 3BSD or 4BSD, but I could be mistaken. Norman Wilson Toronto ON

10 years

/usr/games/factor

by Dave Horsfall

I recall playing with this on the -11, but it seems to have become extinct (the program, I mean). I seem to recall that it was written in PDP-11 assembly; did it ever get rewritten in C? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer" "The complexity for minimum component costs has increased at a rate of roughly a factor of two per year." -- G.Moore, Electronics, Vol 38 No 8, 1965

10 years

Re: [TUHS] who is "Veigh S. Meer"?

by Doug McIlroy

> The punning pseudonym, the complaint at the end that Unix and C are dead > and nothing is even on the horizon to replace them, and the general snarky > tone suggest to me that it's Rob "Mark V. Shaney" Pike. In that case, > the affiliation with Bellcore is a blind ("not Goodyear, Goodrich"). VSM, MVS: what other mystery authors in Unix land identify thus with VMS? Doug

10 years, 1 month

Re: [TUHS] (no subject)

by Brian Walden

I authored those files so I could render the Seventh Edition manuals as PDF in 1998 (long after I had departed the Labs). As pic did not exist yet (Kernighan had not written it) there were never any original pic files for these documents. I do not know what 1127 was doing to publish diagrams at the time. The Bell logo I did directly in postscript so \(bs would render. The logo was originally it's own custom "character" just like an A, B or C, on the phototypesetter's optical font wheel. You can see what they look liked from the v7 PDF manuals -- In Volume 2A (http://plan9.bell-labs.com/7thEdMan/v7vol2a.pdf) bs.ps is on variety of pages such as 129, 130, 216 ms.pic is on page 127 make.ps is on page 282 In Volume 2B (http://plan9.bell-labs.com/7thEdMan/v7vol2b.pdf) implfig1.pic is on page 162 implfig2.pic is on page 168 these are the PDF page numbers (where the title is page 1) > From: Mark Longridge <cubexyz(a)gmail.com> > > I came across some Unix files in v7add such as bs.ps for the Bell logo > and ms.pic (described as Figure 1 for msmacros). > > http://www.maxhost.org/other/ms.pic > > I was wondering if there was some viewer or conversion program so we > could look at pic files from this era? > > Mark > >

10 years, 1 month

(no subject)

by Mark Longridge

I came across some Unix files in v7add such as bs.ps for the Bell logo and ms.pic (described as Figure 1 for msmacros). http://www.maxhost.org/other/ms.pic I was wondering if there was some viewer or conversion program so we could look at pic files from this era? Mark

10 years, 1 month

who is "Veigh S. Meer"?

by Deborah Scherrer

Peter Salus noted there was workshop in Newport, RI, in 1984 concerning "Distributed UNIX." The report on “Distributed UNIX” by Veigh S. Meer [a transparent pseudonym] appeared in /;login:/ 9.5 (November 1984), pp. 5-9. So who was "Veigh S. Meer"? The affiliation says "Bellcore," but who was there in 1984? Peter's first thought was Peter Langston. Any ideas? Debbie

10 years, 1 month

Re: [TUHS] who is "Veigh S. Meer"?

by Norman Wilson

Dave Horsfall: Call me slow, but can someone please explain the joke? If it's American humo[u]r, then remember that I'm British/Australian... There is no such thing as American humour, because Yanks don't know how to spell. They can't get the wood either. Norman Wilson (reformed Yank) Toronto ON

10 years, 1 month

We've lost Greg Chesson

by Dave Horsfall

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]

10 years, 1 month

Re: [TUHS] We've lost Greg Chesson

by norman＠oclsc.org

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

10 years, 1 month

Re: [TUHS] We've lost Greg Chesson

by Rudi Blom

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 >> >> >

10 years, 1 month

Anyone else here remember Portapunch?

by Dave Horsfall

---------- 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.

10 years, 2 months

Plan 9/Inferno Manuals?

by Ramakrishnan Muthukrishnan

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

10 years, 2 months

O'Reilly X11 books, take two

by Aharon Robbins

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

10 years, 2 months

BSD manual set experience

by Jeremy C. Reed

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 '#-~' '\-.-{'

10 years, 2 months

typesetting history

by Aharon Robbins

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

10 years, 2 months

Anyone have a pdf of the C/A/T manual

by Brantley Coile

I remember seeing a manual on the C/A/T typesetter at one point. I didn’t see it in bitsavers.org. Anyone have a pdf of it? bwc

10 years, 2 months

recreating bj.s for Unix v5

by Mark Longridge

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

10 years, 2 months

Re: [TUHS] success, bj assembled and linked in Unix v5

by norman＠oclsc.org

Mark Longridge: chmod 0744 bj Dave Horsfall: That has to be the world's oddest "chmod" command. ====== Not by a long shot. Recently, for reasons related both to NFS permissions and to hardware testing, I have occasionally been making directories with mode 753. At the place I worked 20 years ago, we wanted a directory into which anonymous ftp could write, so that people could send us files; but we didn't want it to become a place for creeps to stash their creepy files. I thought about the problem briefly, then made the directory with mode 0270, owned by the user used for anonymous ftp and by a group containing all the staff members allowed to receive files that way. That way creeps could deposit files but couldn't see what was there. I also told cron to run every ten minutes, changing the permissions of any file in that directory to 0060. Oh, and I had already maniacally (and paranoiacally) excised from ftpd the code allowing ftp to change permissions. I admit I can't think of a reason to use 744 offhand, since if you can read the file you can copy it and make the copy executable. But UNIX permissions can be used in so many interesting ways that I'm not willing to claim there is no such reason just because I can't see what it is. Norman Wilson Toronto ON

10 years, 2 months

success, bj assembled and linked in Unix v5

by Mark Longridge

OK, success... in Unix v5: as bj.s etc.s us.s ld a.out -lc mv a.out bj chmod 0744 bj It seems to work OK now. Probably should work on v6 and v7 as well. Mark

10 years, 2 months

Re: [TUHS] recreating bj.s for Unix v5

by jnc＠mercury.lcs.mit.edu

> From: Mark Longridge <cubexyz(a)gmail.com> > 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. My first question was going to be 'Maybe try an earlier version of the source?', but I see there is no earlier version online. Odd. ISTR that some of the fun things in V6 came without source, maybe blackjack was the same way? > Another idea would be generate the source code from the executable > itself, but there doesn't seem to be a disassembler for early Unix. Where's the binary? I'd like to take a look at it, and see if the source was assembler, or C (there's a C version in the source tree, too). Then I can look and see how close it is to that 2.11 source - that may be a re-implementation, and totally different. Noel

10 years, 2 months

Re: [TUHS] success, bj assembled and linked in Unix v5

by jnc＠mercury.lcs.mit.edu

> From: Mark Longridge <cubexyz(a)gmail.com> > OK, success... Yeah, I just got there too, but by a slightly longer route! (Google wasn't turning up the matches for the routines I needed, which you found in etc.s, etc - it seems the source archive on Minnie isn't being indexed by Google. So I wound up cobbling them together with a mix of stuff from other places, along with stuff I wrote/modified.) > Probably should work on v6 and v7 as well. Does on V6, dunno about V7. > It seems to work OK now. Yes, but this is _not_ the source for the V5/V6 'bj'. (I just checked, and the V5 and V6 binaries are identical.) Right at the moment, I've used enough time on this - I may get back to it later, and disassemble the V5/V6 binary and see what the original source looks like. Noel

10 years, 2 months

Re: [TUHS] recreating bj.s for Unix v5

by jnc＠mercury.lcs.mit.edu

> From: Noel Chiappa > another assembler source file, which contains the following routines > which are missing from bj.s: I missed some. It also wants quest1, quest2 and quest5 (and maybe more). This may present a bit of a problem, as I can't find any trace of them anywhere, and will have to work out from the source what their arguments, etc are, what they do, etc. I wonder how on earth the 2.11 people got this to assemble? (Or maybe they didn't?) Noel

10 years, 2 months

Re: [TUHS] recreating bj.s for Unix v5

by jnc＠mercury.lcs.mit.edu

> From: Mark Longridge <cubexyz(a)gmail.com> > 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. I saw that there's a SysIII bj.s, which is almost identical to the 2.11 one; so the latter is probably descended from the first, which I assume is Bell source. So I grabbed it and tried to assemble it. The errors are because bj.s is designed to be assembled along with another assembler source file, which contains the following routines which are missing from bj.s: mesg decml nline Dunno if you're aware of this, but, the line 'as a.s b.s' _doesn't_ separately assemble a.s and b.s, rather it's as if you'd typed 'cat a.s b.s > temp.s ; as temp.s'. (This is used in the demi-enigmatic "as data.s l.s" in the system generation procedure.) I looked around in the sources that come with V6, and I didn't see any obvious such file. I'm going to whip the required routines up really quickly, and see if the results assemble/run. I looked to see if I could steal them from the binary of 'bj' on V6, and... it looks like that binary is totally different from this source. Let me look into this... > Also other assembly source files don't seem to have .even in them. The V6 assembler groks '.even'. Noel

10 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

TUHS