The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] rebuilding the unix v5 man pages
Date: Sun, 10 Aug 2014 12:36:03 -0400	[thread overview]
Message-ID: <CADxT5N6mgMTjtHWfiyT9Nhh9TPe+x7ZsQRk9SUeD3cYzShbR4A@mail.gmail.com> (raw)

Since there's a pdf of the unix v5 man pages I figured I might as well
recreate all the necessary files to have man pages in v5.

There's a very simple thompson shell script that I used from v6 to create man:

if X$2 != X"" nroff man0/naa man$1/$2.$1
if X$2 = X"" nroff man0/naa man1/$1.1

I borrowed the assembly language source from v6 to recreate nroff for
v5. After that it was just a matter of matching the date from various
files in v4 and v6. If the date was exactly the same for a given man
page file I just copied it straight into v5. If the date was different
then I used the version in v6 and just edited it until it matched what
was shown in the v5 manual pdf.

It should also help me figure out a lot of the differences between v5
and v6. When it's all done I'll put the disk images and configuration
files on archive.org and post the URL here.

I developed a sort of philosophy for adding stuff to unix v5 which
goes beyond the  v5root.tar.gz files donated by Dennis Ritchie:

No changing of cc or as.
No changing of the kernel code beyond recompiling the existing v5 code.
No changing of the existing device drivers (adding new ones is OK).
No backporting of iolib or stdio into v5.
No changing libc.
Adding userland programs is OK as long as the above rules are followed.

Mark



                 reply	other threads:[~2014-08-10 16:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CADxT5N6mgMTjtHWfiyT9Nhh9TPe+x7ZsQRk9SUeD3cYzShbR4A@mail.gmail.com \
    --to=cubexyz@gmail.com \
    /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).