From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29060 invoked from network); 20 Jul 2020 17:53:42 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 20 Jul 2020 17:53:42 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 26D3B9BA61; Tue, 21 Jul 2020 03:53:42 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5C6229BA30; Tue, 21 Jul 2020 03:53:26 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="NIgGSH9z"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 1D3EB9BA32; Tue, 21 Jul 2020 03:53:25 +1000 (AEST) Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) by minnie.tuhs.org (Postfix) with ESMTPS id 8E0549BA2A for ; Tue, 21 Jul 2020 03:53:24 +1000 (AEST) Received: by mail-qt1-f177.google.com with SMTP id j10so13812029qtq.11 for ; Mon, 20 Jul 2020 10:53:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bZrj2wGznctde6/31Ezf0c9lsY/4NcghC2I7C3tIBmM=; b=NIgGSH9zY1Voy05/uByM7I0fTSYu0zSaDjDxl/NBptgFqBHcouMij2W6Wxtqoenm9S MWFJRZ7gXXxOxTNq0ugqjz6VR1z4lRJa+GLJBLpOrv6vrv6lvfDQ02z2J+ot2dYbBTwk aFaMdQO2NkQOjvzlQcF7uavB/f1f6tCUMxQ7k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bZrj2wGznctde6/31Ezf0c9lsY/4NcghC2I7C3tIBmM=; b=OvCDBXcsXIEDyrhYY+2FwSSGA5InVdX6z1LEZQ1VLtzJ1Vb77fcAtzXW3YNx5kEXfd Bkk0INmnyj2hsT8bj6NpWQxDGOiIc0RgiKmsQlXsngzt13DJXaiJqdPM3JcOnogAP98A QoJMbYeHcyyVSfulYLDNEPwtHoJqaW+zCplVglu4kKjoGtjzSHNlzqMg6r4cK4vntK8Q pd7Dqp3XYB6Ru04+iaF6tT6H2EMqQJAADxPydVim1y7p0DzO705xqAa+fZh15IG3GEss Pu5yaap2VX+F4sObtTzg3h0gtPMgzwA/K0Crqo+HRIeV7ndUhPhNKbUR7ub8WFQiKQuX K/xQ== X-Gm-Message-State: AOAM5334Zo+OOYerjXh/f3r349+b7G9hgfZIgyCTL61jvSUHaOjWyLpq UZJNUFAn1LLM3+Uoe0IRSbZUS5INKeLeyxMtRChh0Q== X-Google-Smtp-Source: ABdhPJyoArzE0cMQQGlIINA42kUp/Fgm6hg4QgQ5B0bq79ZCeonl1Wt9OobR/Zs96pjQxW1yy1cXadGPCf/fduns0HY= X-Received: by 2002:ac8:130d:: with SMTP id e13mr25268586qtj.253.1595267603589; Mon, 20 Jul 2020 10:53:23 -0700 (PDT) MIME-Version: 1.0 References: <78041442-c5e5-1b5c-8565-b6d31f23ec1b@gmail.com> In-Reply-To: <78041442-c5e5-1b5c-8565-b6d31f23ec1b@gmail.com> From: Clem Cole Date: Mon, 20 Jul 2020 13:52:57 -0400 Message-ID: To: Will Senn Content-Type: multipart/alternative; boundary="000000000000d578cd05aae32e91" Subject: Re: [TUHS] Traditional method of dealing with embedded shar files X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000d578cd05aae32e91 Content-Type: text/plain; charset="UTF-8" On Mon, Jul 20, 2020 at 1:25 PM Will Senn 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. --000000000000d578cd05aae32e91 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Jul 20, 2020 at 1:25= PM Will Senn <will.senn@gmail.co= m> wrote:
=20 =20 =20
My questions for y'a= ll are how would you go about doing this? Use vi to delete everything through the =3D=3D=3D=3D cut here line?
Yep


=C2=A0<= /div>
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 messin= g with.=C2=A0 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.=C2=A0 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 a= ll the SMTP guaranteed=C2=A0in the=C2=A0early days.=C2=A0=C2=A0 = Yeh but .. uucp was 8 yep.=C2=A0 But some of the legs of the USENET were lu= ck to be based on Arpanet site, which might have had a mailer running BITNE= T.=C2=A0 When shar was created the 'least needed' style assumptions= were used.=C2=A0 =C2=A0As it was it was often that people put tarballs, th= en compressed them and then uuencoded them inside.=C2=A0 Often a space savi= ngs 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=C2=A0out well= in practice.
--000000000000d578cd05aae32e91--