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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29725 invoked from network); 20 Jul 2020 17:59:27 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 20 Jul 2020 17:59:27 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 8409C9BA75; Tue, 21 Jul 2020 03:59:25 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 04D349BA30; Tue, 21 Jul 2020 03:58:58 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=bsdimp-com.20150623.gappssmtp.com header.i=@bsdimp-com.20150623.gappssmtp.com header.b="PfvWLwju"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 7A3959BA30; Tue, 21 Jul 2020 03:57:12 +1000 (AEST) Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) by minnie.tuhs.org (Postfix) with ESMTPS id A62B19BA2A for ; Tue, 21 Jul 2020 03:57:11 +1000 (AEST) Received: by mail-qk1-f174.google.com with SMTP id l6so16276728qkc.6 for ; Mon, 20 Jul 2020 10:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XX/Kv7jsD9GQa0V32KOl3ZvVlPIF4x/oNMAlwxhmOQg=; b=PfvWLwjuAQruJtbWqdeRMMXTr/U3E8XwIh/qyBKqTIVXAzyYNRiYI8ORICPZ0eegtL rvVZN9zxPDqIfsjQZnZU8Pv1aRrhLZn1dqEwr7IvVnO8pGpNEw5jvuLNSkv1hOscwjyu jPgyW6pGLqG3s96GorFO1M3ti4UzJbwMei8l6mGnM/vRNDsedzFSD83s8hhVGWUJadl8 zTJmLWUH+5XJqYncwMb1gvs7a3uJ0rY4Pw6RKyWCniwYK3oAgGNnEfpinO5z11Ay0NsR Hp7vlueFHa0cYRxma7WYvEkssghOqQixOPSgq+OlL9uQ1hHreyoOTfg4mGiYw5sUIBQx WXbw== 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=XX/Kv7jsD9GQa0V32KOl3ZvVlPIF4x/oNMAlwxhmOQg=; b=JhM2Xo2379mHIs7rhB/jOOKlzfhnR8FM3krxmgPBXwfOTw/pOBTwZa/8xbNgs84c6Q GTbpOtXBRayjsDEYKVIIhUZHSnJ8aJE1IbZFTiemTleXOfHs3mXOQqQkS7iP5cnLd97c QGs2bdCAKkZDe4mRy14u/j/9jXHF5aLhyeS3/cqNO74+M8/EKMP+0mXzhKo31Qv/vJ/H EkZD5mtkUK7MIfMFhs2zQOk2uRyVL551LaZgAlwVPMbvMsxKHIJYhmpAZMP2Ka1o1zh8 f7P8KF6ELR1olgYNa5ILwDiyeG+7/Gtqht62IkksJdrnFEV80qPPnY2S1O6jPt+m8WXA QwOA== X-Gm-Message-State: AOAM531XqOXSW1pq8mmgeYlADGQWY2Zk3QBp7NtAX3Mae/8sWatI45kW HCoNNH8JeVhO2JzcrAAUbNIKBWF3VSp/tG/Z7dTuFOu4 X-Google-Smtp-Source: ABdhPJznZ8qpFWI3RIr+3GJXEHbRB80jskNQW6iv79oWhFkGbRgI+oJLEsNU59C/ypEgVND7xI0k6pDLa36shH2/q0U= X-Received: by 2002:a05:620a:148d:: with SMTP id w13mr24041849qkj.215.1595267830739; Mon, 20 Jul 2020 10:57:10 -0700 (PDT) MIME-Version: 1.0 References: <78041442-c5e5-1b5c-8565-b6d31f23ec1b@gmail.com> In-Reply-To: From: Warner Losh Date: Mon, 20 Jul 2020 11:56:59 -0600 Message-ID: To: Clem Cole Content-Type: multipart/alternative; boundary="0000000000005fc9d405aae33ced" 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" --0000000000005fc9d405aae33ced Content-Type: text/plain; charset="UTF-8" On Mon, Jul 20, 2020 at 11:54 AM Clem Cole wrote: > > > 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. > There's various 'unshar' programs, but they are all just restricted versions of the shell because of the wide diversity of 'shar' implementation... uuencoded compressed tar balls added another layer to this mess as well :) Warner --0000000000005fc9d405aae33ced Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jul 20, 2020 at 11:54 AM Clem= Cole <clemc@ccc.com> wrote:
=


On Mon, Jul 20, 2020 at 1:25 PM Will Senn <will.senn@gmail.com> 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
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 back= up and/or copy the files you new you we were messing with.=C2=A0 The good n= ews 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.

Ther= e's various 'unshar' programs, but they are all just restricted= versions of the shell because of the wide diversity of 'shar' impl= ementation...=C2=A0 uuencoded compressed tar balls added another layer to t= his mess as well :)

Warner
--0000000000005fc9d405aae33ced--