The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Angelo Papenhoff <aap@papnet.eu>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Reconstructed and newly set UNIX Manual
Date: Sat, 27 Oct 2018 00:29:09 +0200	[thread overview]
Message-ID: <20181026222909.GA24093@indra.papnet.eu> (raw)
In-Reply-To: <20181026221153.GA19920@indra.papnet.eu>

[this was meant to go over the list, Warren quoted it, but it
destroyed the formatting somewhat]

On 27/10/18, Warren Toomey wrote:
> On Fri, Oct 26, 2018 at 09:46:36PM +0200, Angelo Papenhoff wrote:
> > And most importantly: is the old troff really lost?
> 
> Angelo, I just trawled through the Unix Archive. Below is a list
> of tarballs with roff stuff in them. Hope this helps. Sorry that
> they are not in date order.
> Cheers, Warren

Unfortunately that does not include the old troff written in PDP-11
assembly.
The v6 tape and file system contain traces of it in the directory
/usr/source/s7, so we at least know (some of) the file names:

│002655f0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 |                |
│00265600 6d 01 72 6f 66 66 33 2e-73 00 00 00 00 00 00 00 |m?roff3.s       |
│00265610 6c 01 72 6f 66 66 34 2e-73 00 00 00 00 00 00 00 |l?roff4.s       |
│00265620 6b 01 72 6f 66 66 35 2e-73 00 00 00 00 00 00 00 |k?roff5.s       |
│00265630 6a 01 72 6f 66 66 37 2e-73 00 00 00 00 00 00 00 |j?roff7.s       |
│00265640 69 01 72 6f 66 66 38 2e-73 00 00 00 00 00 00 00 |i?roff8.s       |
│00265650 00 00 73 75 66 72 63 00-00 00 00 00 00 00 00 00 |  sufrc         |
│00265660 67 01 73 75 66 74 61 62-2e 73 00 00 00 00 00 00 |g?suftab.s      |
│00265670 00 00 74 63 61 74 73 69-6d 2e 73 00 00 00 00 00 |  tcatsim.s     |
│00265680 00 00 74 72 63 00 00 00-00 00 00 00 00 00 00 00 |  trc           |
│00265690 00 00 74 72 6f 66 66 31-2e 73 00 00 00 00 00 00 |  troff1.s      |
│002656a0 00 00 74 72 6f 66 66 32-2e 73 00 00 00 00 00 00 |  troff2.s      |
│002656b0 00 00 74 72 6f 66 66 33-2e 73 00 00 00 00 00 00 |  troff3.s      |
│002656c0 00 00 74 72 6f 66 66 34-2e 73 00 00 00 00 00 00 |  troff4.s      |
│002656d0 00 00 74 72 6f 66 66 35-2e 73 00 00 00 00 00 00 |  troff5.s      |
│002656e0 00 00 74 72 6f 66 66 36-2e 73 00 00 00 00 00 00 |  troff6.s      |
│002656f0 00 00 74 72 6f 66 66 36-61 00 00 00 00 00 00 00 |  troff6a       |
│00265700 00 00 74 72 6f 66 66 38-2e 73 00 00 00 00 00 00 |  troff8.s      |
│00265710 00 00 78 78 78 78 78 00-00 00 00 00 00 00 00 00 |  xxxxx         |
│00265720 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 |                |

Now it could be that v7 troff is perfectly capable of generating the
manual just like older troff would have, I just haven't dived more
deeply into it all yet. I was more concerned about reconstructing the
actual content rather than the exact looks for now, but it's still
something i want to get right eventually.


This didn't go through the list but I'll reply here:

On 26/10/18, Ken Thompson wrote:
> nice job.

Thanks, You've always been an inspiration to me!

aap

  parent reply	other threads:[~2018-10-26 22:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 19:46 Angelo Papenhoff
2018-10-26 19:57 ` Jim Capp
2018-10-26 20:41 ` Clem Cole
2018-10-26 21:05   ` Angelo Papenhoff
2018-10-26 21:58     ` Bakul Shah
2018-10-26 20:59 ` Warren Toomey
2018-10-27 17:15   ` Angelo Papenhoff
2018-10-27 17:41     ` Angelo Papenhoff
     [not found] ` <20181026214308.GA20796@minnie.tuhs.org>
     [not found]   ` <20181026221153.GA19920@indra.papnet.eu>
2018-10-26 22:29     ` Angelo Papenhoff [this message]
2018-10-26 23:06       ` Warner Losh
2018-10-26 23:46         ` Larry McVoy
2018-10-28 22:57 ` Angelo Papenhoff
2018-10-29  0:15   ` Clem cole
2018-11-01 17:21 ` Angelo Papenhoff
2018-10-27 11:59 Doug McIlroy
2018-10-27 12:28 ` Angelo Papenhoff
2018-10-27 13:07   ` Milo Velimirovic
2018-10-27 13:56     ` Toby Thain
2018-10-27 15:19     ` Ralph Corderoy
2018-10-27 15:53 ` Clem Cole
2018-10-27 16:25   ` Larry McVoy
2018-10-27 19:45   ` Lars Brinkhoff
2018-10-27 14:18 Nelson H. F. Beebe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181026222909.GA24093@indra.papnet.eu \
    --to=aap@papnet.eu \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).