Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.uzoreto.com!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!69.80.99.11.MISMATCH!border-1.nntp.ord.giganews.com!nntp.giganews.com!Xl.tags.giganews.com!local-2.nntp.ord.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail NNTP-Posting-Date: Mon, 27 Mar 2023 03:12:05 +0000 Subject: Re: uefi malware--threat to all? Newsgroups: comp.os.linux.misc References: <20230321020154@news.eternal-september.org> <7CGdnQege7aJoIT5nZ2dnZfqn_udnZ2d@earthlink.com> <8203f13e6918891b2622edd3a1663283@msgid.frell.theremailer.net> <87ttyag8m7.fsf@gmail.com> <191638ac475fb3327cbd4c3743205b13@msgid.frell.theremailer.net> <-6mdnQ6m2uggf735nZ2dnZfqnPudnZ2d@earthlink.com> <6357fjxeds.ln2@Telcontar.valinor> From: "27E.G756" <27E.G756@noq24u.net> Organization: anode intersection Date: Sun, 26 Mar 2023 23:11:50 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <6357fjxeds.ln2@Telcontar.valinor> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Message-ID: Lines: 33 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 68.222.41.46 X-Trace: sv3-MvJ8vSqY8eE/6aIEhwlDB9keTk+vlLQOyVAmuIl5Mdv6mOv9m6GcDtlHzfakGrVvikk0cdbMkjDKtYL!SRD7T8gYhRkv31kSLh63dOlWZn79OD8vMciD6TUGATbBUT7oDaKzLFEtIIGmCHZ4Mek+lrJgAUmb!ODLj5lByjPwMqvav2Kw= X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Xref: csiph.com comp.os.linux.misc:37660 On 3/26/23 8:37 PM, Carlos E.R. wrote: > On 2023-03-27 02:26, 27E.G756 wrote: >> On 3/24/23 8:58 PM, Fritz Wuehler wrote: >>> jeshgrca [j]: >>> j> "A programmer has a problem and thinks "I know! I'll use sed(1)!" Now >>> j> the programmer has two problems." >>> >>> If 'sed' isn't one's cup of tea, there are other similar tools out there >>> such as 'msrp', 'binmay', or in a pinch 'm4' to choose from. >>> >>> Replacing a bunch of fixed strings and numbers in a pre-recorded macro >>> script file isn't exactly rocket science. >> >>    Careful ... I did that to a long script and ONE entry >>    was "different" - and it erased the box  :-) >> >>    Yes, that CAN happen ... it was a 'reverse' of "rsync --delete" >>    and finding blank 'source' files due to the error it proceeded >>    to erase all the "obsolete" files it could get to ... > > Whoa! that happened to me. Run rsync --delete on the wrong backup set. > And deleted the original instead. In this case there were many live links open - including to an NAS. So guess ... GOOD reason to keep LOTS of backups here there and everywhere ! Storage is cheap these days. These days I open source NAS/cifs mounts READ-ONLY for backups, just in case, and only one at a time.