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_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30906 invoked from network); 20 Jul 2020 18:09:12 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 20 Jul 2020 18:09:12 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id D6C409BA58; Tue, 21 Jul 2020 04:09:11 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5C1289BA4B; Tue, 21 Jul 2020 04:08:40 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="mvqz/fgJ"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 9F8999BA4C; Tue, 21 Jul 2020 04:08:38 +1000 (AEST) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) by minnie.tuhs.org (Postfix) with ESMTPS id 3161F9BA32 for ; Tue, 21 Jul 2020 04:08:37 +1000 (AEST) Received: by mail-lf1-f49.google.com with SMTP id i80so10213769lfi.13 for ; Mon, 20 Jul 2020 11:08:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3yN0pHoPijxzWsQv8a98xTAOKYt4RHux9CuvII0C9/0=; b=mvqz/fgJV8LHowzeGp9IMsBdmnHS1rzVrln0UzIGRNaqU1JnRBfeomePxIRZ0bR78M BkvGVt7Vh60o+d7wIfI/O98xD3FE8X/9fkPQlesv1NBwAs+kZ1fGRbmbktKJIC6VO61t jTpEQZZV9DfWhuuEpxeYeWDKa7A5ydKgAWk9so4+ynoEmLLxxHwUJTunQptySwm67Ijj W63yoNNNtjBDhPwRqTVlEOnUxvKT7PbMo6Ww6X9wRKcDJ+XAkTT4Y7DX5MUTAZXDEX8F x6Cy3vvBKDp1Nph0V/BRLbaNOxHa+MB/hOrvjWMZH1SaCzh9sgUq36rQLnPK8viW5cZC 1mIg== 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=3yN0pHoPijxzWsQv8a98xTAOKYt4RHux9CuvII0C9/0=; b=Ec5KnLGgd9u9CRXj7TyRXkA+XkId4rbRDMq0ZzsgxKLZGYYd4zZ+SwBGTxFgXsfSzc DQkmLCZ2xcUKTreoDynQVbVwlWun3UweiLwz2iVfn/Kh2jfNIjuhfh3IENkLNmO6Vyy+ iuYigWcnHvyE3X9XV0wY7V9SVxh0ROj7qXiJwexU9D3oza6KfFaDlk+yRkZcO0WsiR9X xlOb5Hy81/uP7gxz83xGabjAP2U4MJ4gV0O1XTpbRj0vln/HK5U4/cpORxZZWTXZnOtd PMSSlrFSjm8at3nYlOFVdiJbCjTp3pe2h5qglT2HWCsQa5tyKadRIaNZAK2ABeMHV6kN d0yA== X-Gm-Message-State: AOAM532Q1w4anNhMxPSF7Gms8nZStuoPO76tlQJ3b/O1tAGe5kh7rjNW Q+tgPoIvT7wESxPt1JV46Uo1as03YbA8siU5zw5FBhrl X-Google-Smtp-Source: ABdhPJxKPpa2X0rwJ4mjqLY62EtzlzCBv9cFL2HgtiM1CxREgLejynfOh+EpWBzTorN8A+joO8UteFKKqEtyT8ThHiA= X-Received: by 2002:a05:6512:31d5:: with SMTP id j21mr11417992lfe.83.1595268515410; Mon, 20 Jul 2020 11:08:35 -0700 (PDT) MIME-Version: 1.0 References: <78041442-c5e5-1b5c-8565-b6d31f23ec1b@gmail.com> In-Reply-To: From: Richard Salz Date: Mon, 20 Jul 2020 14:08:23 -0400 Message-ID: To: Warner Losh Content-Type: multipart/alternative; boundary="0000000000002eb71a05aae365b2" 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" --0000000000002eb71a05aae365b2 Content-Type: text/plain; charset="UTF-8" shar, by the way, stands for "shell archive." That is, it's an archive that could be unpacked by feeding the file into sh. The most complete unshar is probably at http://sources.vsta.org/comp.sources.unix/volume15/cshar/ It's portable C (for its time, 20 years ago). Safety, in terms of not trashing an existing file, was a goal. On Mon, Jul 20, 2020 at 1:59 PM Warner Losh wrote: > > > 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 > --0000000000002eb71a05aae365b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
shar, by the way, stands for "shell archive.&quo= t;=C2=A0 That is, it's an archive that could be unpacked by feeding the= file into sh.
The most complete unshar is probably at http://sources.= vsta.org/comp.sources.unix/volume15/cshar/=C2=A0 It's portable C (f= or its time, 20 years ago). Safety, in terms of not trashing an existing fi= le, was a goal.


On Mon, Jul 20, 2020 at 1:59 PM Warner = Losh <imp@bsdimp.com> wrote:
<= div dir=3D"ltr">

On Mon, Jul 20, 2020 at 11:54 AM Clem Cole <clemc@ccc.com> wrote:
<= div dir=3D"ltr">

<= /div>

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
--0000000000002eb71a05aae365b2--