The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Traditional method of dealing with embedded shar files
Date: Mon, 20 Jul 2020 13:52:57 -0400	[thread overview]
Message-ID: <CAC20D2OJsYwymjbg9xD+Lw_zeMx9QShSbw7bheK7cCwnsnYwUw@mail.gmail.com> (raw)
In-Reply-To: <78041442-c5e5-1b5c-8565-b6d31f23ec1b@gmail.com>

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

On Mon, Jul 20, 2020 at 1:25 PM Will Senn <will.senn@gmail.com> wrote:

> My questions for y'all are how would you go about doing this? Use vi to
> delete everything through the ==== cut here line?
>
Yep




> In my world, if I screw something up, it's 15 seconds to run a restore
> script in my simh directory and I can try again, so my level of concern for
> a mistake is pretty low. If I was doing this in 1980, on real hardware, I
> would have had many concerns, as I'm sure some of y'all can remember, how
> did you prepare and protect yourselves so a patch was successful.
>
Run an incremental backup and/or copy the files you new you we were messing
with.  The good news was that patch makes backups.

>
> BTW, I thought .shar was an archive format, so when I saw the patch was a
> shar file,
>
It was so of.  It was a way to send files around that people could easily
execute and you new would work through 7-bit based email which is all the
SMTP guaranteed in the early days.   Yeh but .. uucp was 8 yep.  But some
of the legs of the USENET were luck to be based on Arpanet site, which
might have had a mailer running BITNET.  When shar was created the 'least
needed' style assumptions were used.   As it was it was often that people
put tarballs, then compressed them and then uuencoded them inside.  Often a
space savings and made it easier -> compressed tar was pretty good, and
even with the 3 8-bit chars as 4 6-bit chars of uuencode it will worked out
well in practice.

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

  parent reply	other threads:[~2020-07-20 17:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 17:23 Will Senn
2020-07-20 17:44 ` Clem Cole
2020-07-20 17:52 ` Clem Cole [this message]
2020-07-20 17:56   ` Warner Losh
2020-07-20 18:08     ` Richard Salz
2020-07-20 18:07   ` Will Senn
2020-07-24 18:29     ` Random832
2020-07-24 18:46       ` Will Senn
2020-07-24 18:57         ` Clem Cole
2020-07-24 19:21           ` Will Senn
2020-07-25  2:00       ` Dave Horsfall
2020-07-20 17:55 ` Warner Losh
2020-07-20 18:11   ` Will Senn
2020-07-20 18:41     ` Clem Cole

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=CAC20D2OJsYwymjbg9xD+Lw_zeMx9QShSbw7bheK7cCwnsnYwUw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@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).