From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Brian Kernighan and very early *roff history
Date: Fri, 14 Jan 2022 13:35:45 +0000 [thread overview]
Message-ID: <20220114133545.C83CA219E2@orac.inputplus.co.uk> (raw)
In-Reply-To: <YeF6XymuCj2KgHAa@indra.papnet.eu>
Hi aap,
> v6 has assembler sources for nroff and deleted directory entries of
> troff (and others):
>
> 00064e00: 6d01 726f 6666 332e 7300 0000 0000 0000 m.roff3.s.......
> 00064e10: 6c01 726f 6666 342e 7300 0000 0000 0000 l.roff4.s.......
> 00064e20: 6b01 726f 6666 352e 7300 0000 0000 0000 k.roff5.s.......
> 00064e30: 6a01 726f 6666 372e 7300 0000 0000 0000 j.roff7.s.......
> 00064e40: 6901 726f 6666 382e 7300 0000 0000 0000 i.roff8.s.......
> 00064e50: 0000 7375 6672 6300 0000 0000 0000 0000 ..sufrc.........
> 00064e60: 6701 7375 6674 6162 2e73 0000 0000 0000 g.suftab.s......
> 00064e70: 0000 7463 6174 7369 6d2e 7300 0000 0000 ..tcatsim.s.....
> 00064e80: 0000 7472 6300 0000 0000 0000 0000 0000 ..trc...........
> 00064e90: 0000 7472 6f66 6631 2e73 0000 0000 0000 ..troff1.s......
Are inodes 0x0168, etc., re-used elsewhere? If so, it would be
interesting to where.
Or is there a chance they still hold useful information about blocks
which may contain troff content?
--
Cheers, Ralph.
next prev parent reply other threads:[~2022-01-14 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 13:07 Noel Chiappa
2022-01-14 13:27 ` Angelo Papenhoff
2022-01-14 13:35 ` Ralph Corderoy [this message]
2022-01-14 13:55 ` Will Senn
2022-01-14 13:58 ` Will Senn
2022-01-14 14:25 ` Will Senn
-- strict thread matches above, loose matches on Subject: below --
2022-01-14 0:04 Tom Lyon via TUHS
2022-01-14 0:10 ` Rob Pike
2022-01-14 7:38 ` arnold
2022-01-14 10:13 ` Jaap Akkerhuis
2022-01-14 11:48 ` Rob Pike
2022-01-14 14:08 ` Larry McVoy
2022-01-14 11:59 ` Angelo Papenhoff
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=20220114133545.C83CA219E2@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=tuhs@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).