From: Will Senn <will.senn@gmail.com>
To: Leah Neukirchen <leah@vuxu.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Diff and Patch on v7
Date: Sat, 25 Jul 2020 09:28:19 -0500 [thread overview]
Message-ID: <d0a17193-bd6d-89c3-efec-79209fd6841d@gmail.com> (raw)
In-Reply-To: <878sf7adz3.fsf@vuxu.org>
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
next prev parent reply other threads:[~2020-07-25 14:28 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 [this message]
2020-07-25 14:39 ` Clem Cole
2020-07-25 15:19 ` Warner Losh
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=d0a17193-bd6d-89c3-efec-79209fd6841d@gmail.com \
--to=will.senn@gmail.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).