The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Leah Neukirchen <leah@vuxu.org>
Subject: Re: [TUHS] Diff and Patch on v7
Date: Sat, 25 Jul 2020 09:19:31 -0600	[thread overview]
Message-ID: <CANCZdfrqe=jk06wmZpG+OXeZo7JyKSDHpyZfcMZBLjWuZR0b8Q@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PDV-uJ8EdbmPr+GCaWsKeG-5=op47gnBGQy4ScjQrpgQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3464 bytes --]

On Sat, Jul 25, 2020 at 8:41 AM Clem Cole <clemc@ccc.com> wrote:

> Will that is the output that would have go into patch(1).  As Leah says,
> the old days we used diff -e to create the patch and then ed file
> <diff_output
> That said, when Larry wrote patch, V7 was still very much alive and
> kicking and Larry had come from that world/his code would be likely to be
> fairly clean of vax-isms.  I bet if you can find a version that will
> compile and run on V7.   V6 is likely to be more difficult since the
> language changes for stdio.  But patch(1) is small and simple so I bet even
> that would be pretty straight forward.
>

I'd start with the last larry wall version of patch, before gnu took it up.
It likely will compile there out of the box. There's a copy in 2.11BSD
that's version 2 that at least fits into a PDP-11 with separate I&D space.
It's also on the 2.10.1BSD tape as well. configure will almost certainly
work on the V7 shell. Not sure about v6, unlikely. It will compile under
V7's c compiler as well, since it's pure K&R. It also runs well enough to
apply all the diffs 2.11BSD has produced over the years. It looks like it
doesn't require separate I&D space to load, but it's big enough that it
helps a lot. V7 had separate i&D space, so you're good there.

However, it will only accept context diffs, not unified diffs. You may have
to convert newer unified diffs to context diffs. Well, it also accepts
normal diffs and ed scripts too :)

Looking at the size of FreeBSD's patch, it's only 53kB text and 8kB data on
amd64, so there's a chance newer versions will fit (this is the last
BSD-licensed version, with bug fixes). It groks everything that gnu patch
groks. gnu patch is 175k of text and 8k of data and is quite likely a lost
cause on the pdp-11 (with overlays, 176k is the absolute max, but 150k is
where it gets hard... but V7 didn't have an overlay linker).

Warner

>
> On Sat, Jul 25, 2020 at 10:29 AM Will Senn <will.senn@gmail.com> wrote:
>
>> On 7/25/20 9:03 AM, Leah Neukirchen wrote:
>> > Will Senn <will.senn@gmail.com> writes:
>> >
>> >> I got a diff for adding actual backspace and delete to v7, linked off
>> >> of gunkies... Anyhow, I can manually edit the referenced files and
>> >> rebuild, but I would rather do it canonically. I don't see patch
>> >> anywhere, so did v7 users use diffs to patch source and if so what's
>> >> the magic?
>> > patch(1) was written by Larry Wall in 1985, and released over Usenet.
>> >
>> > v7 users likely used diff -e, and piped to ed to apply it.
>> >
>> That makes sense. So, if that's how it went then I'm wondering if my
>> diff is meant to run against source on the host and the results placed
>> into v7, rather than run in v7. Does this look like a modern diff vs the
>> old stuff?:
>>
>> --- usr/src/cmd/getty.c    1979-05-05 08:19:21.000000000 +0100
>> +++ usr.fix/src/cmd/getty.c    2018-01-09 11:07:37.157953044 +0100
>> @@ -5,11 +5,11 @@
>>
>>   #include <sgtty.h>
>>   #include <signal.h>
>> -#define ERASE    '#'
>> -#define KILL    '@'
>> +#define ERASE    '\177'
>> +#define KILL    '\025'
>>
>>   struct sgttyb tmode;
>> -struct tchars tchars = { '\177', '\034', '\021', '\023', '\004', '\377'
>> };
>> +struct tchars tchars = { '\003', '\034', '\021', '\023', '\004', '\377'
>> };
>>
>>   struct    tab {
>>       char    tname;        /* this table name */
>>
>>
>> Will
>>
>> --
>> GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF
>>
>>

[-- Attachment #2: Type: text/html, Size: 5097 bytes --]

  reply	other threads:[~2020-07-25 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-25 13:52 Will Senn
2020-07-25 14:03 ` Leah Neukirchen
2020-07-25 14:28   ` Will Senn
2020-07-25 14:39     ` Clem Cole
2020-07-25 15:19       ` Warner Losh [this message]
2020-07-25 15:45     ` Richard Salz

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='CANCZdfrqe=jk06wmZpG+OXeZo7JyKSDHpyZfcMZBLjWuZR0b8Q@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=clemc@ccc.com \
    --cc=leah@vuxu.org \
    --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).