From slitt at troubleshooters.com Tue Aug 2 09:52:28 2022 From: slitt at troubleshooters.com (Steve Litt) Date: Tue, 02 Aug 2022 02:52:28 -0400 Subject: GoLUG online presentation: General FOSS presentation Message-ID: <347f9448bb7b5edc4f84878a0be4bf6255d2a75f.camel@troubleshooters.com> Hi all, Wednesday Evening, August 3, 2022, at 7pm Eastern Daylight time, the monthly GoLUG online meeting will be a discussion about all things FOSS: The Linux kernel, the GNU utils, periperals, drivers, application software, programming techniques and anything else FOSS. Anyone and everyone can speak and participate. When: 7pm Eastern Daylight time on Wednesday, August 3, 2022. Where: https://meet.jit.si/golug Thanks, SteveT Steve Litt GoLUG Publicity Coordinator Greater Orlando Linux User Group From efraim at flashner.co.il Wed Aug 3 23:06:38 2022 From: efraim at flashner.co.il (Efraim Flashner) Date: Wed, 3 Aug 2022 23:06:38 +0300 Subject: slightly OT - backup strategy In-Reply-To: <20220717164946.725c4714@shlomo1.solomon> References: <20220717164946.725c4714@shlomo1.solomon> Message-ID: Coming in late: I keep a bunch of that stuff in git-annex. I can then use git-annex to sync the data around to my different machines, and I use a couple of S3 compatible places online to keep an offsite location for the files synced with git-annex. One collection for my Music files, one for family photos. Documents and Download folders are synced using syncthing. -- Efraim Flashner ????? ????? GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From shlomo.solomon at gmail.com Fri Aug 5 09:25:59 2022 From: shlomo.solomon at gmail.com (Shlomo Solomon) Date: Fri, 5 Aug 2022 09:25:59 +0300 Subject: Kubuntu kernel version Message-ID: <20220805092559.2dd119fa@shlomo1.solomon> I recently read that Ubuntu 20.04 has upgraded from kernel 5.13 to 5.15 Although I regularly run: sudo apt update;sudo apt upgrade;sudo apt autoremove;sudo apt clean to keep my system up to date, I was still on 5.4 uname -r 5.4.0-122-generic I downloaded and ran ubuntu-mainline-kernel.sh and was asked if I wanted the latest kernel. After rebooting, I got: uname -r 5.19.0-051900-generic Since that seemed strange (5.19 and not 5.15), I found and ran the following: sudo apt-get install --install-recommends linux-generic-hwe-20.04 This installed the expected 5.15. Part of the output was: Setting up linux-generic-hwe-20.04 (5.15.0.43.46~20.04.14) But after rebooting, I'm still on 5.19 - I assume because this is a higher version and the GRUB entry was not removed. 2 questions: 1 - Is it normal that sudo apt update; sudo apt upgrade left me with a 5.4 kernel? It has been upgraded over time, but not to 5.13 and 5.15. 2 - Is there a problem having 5.19 instead of the recommended 5.15 and should I uninstall it? -- Shlomo Solomon http://the-solomons.net Claws Mail 3.17.5 - KDE Plasma 5.18.5 - Kubuntu 20.04 From d.s at daniel.shahaf.name Sat Aug 27 21:19:10 2022 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Sat, 27 Aug 2022 18:19:10 +0000 Subject: dd(8)-written disk has ~800MB of NULs Message-ID: <13643951-16cd-4dad-988d-910d281de523@www.fastmail.com> Subject: dd(8)-written disk has ~800MB of NULs tl;dr: I dd(8)'d a partition to a HD in an external enclosure, then cmp(1)'d to verify the copy, and found 800MB of NULs in the target of the copy; I'm trying to figure out what went wrong and whether I can trust the enclosure and HD the data was written to. --- What happened: I booted a host from a live USB [debian buster, kernel 4.19.67-2+deb10u1] and used dd(8) to copy one of the host's partitions to a 3.5" SATA disk in an external USB3.0 enclosure [vid 2109 pid 0711, quirks US_FL_NO_ATA_1X]. The enclosure is connected via two USB cables (the manufacturer's USB?3 B?A?cable and a 3m USB?A extension cable) and has its own 220V power supply. The partition in question is ~700GB. It wasn't mounted at the time. The argument to dd(8)'s of= option was a partition on the target disk, not a regular file. dd(8) processed data at 26MB/s. (IIRC, I didn't specify any bs= argument.) dd(8)'s exit code was zero. I turned off the host and the next day, in the same live environment, cmp(1)ed the source and target partitions. cmp(1) found a difference about 20% of the way in. A closer look revealed that 192774 4096-byte blocks (about 770MB) in the middle of the target partition contained only NULs. Other than those NULs, the target partition was identical to the source partition. I have now re-written those 800MB, which succeeded. Reading them back succeeded too and they compare equal to the source partition. SMART status of the source disk is clean. I can't get SMART status of the target disk easily (that's unsupported by the enclosure). --- I'm not sure what to make of that. It seems like dd(8) silently failed to write 800MB of data. The target partition is in an area of the target drive that was likely never used before. It's possible all-NULs is what those 771MB contained before the dd(8) run. Thus, two possibilities: either the sectors weren't written to at all, or they were written to with NULs rather than with the correct data. --- I'd like to understand what caused the silent write failure so I can ensure it won't happen again, and more importantly, so I can ensure disks I write will be readable when I need them. What should be my first suspect here? A hardware issue? What part of the setup should I look at first? What should I do to make sure the data will be readable? If I verify the data after writing it [e.g., by cmp(1) to a known-good copy, or by verifying PGP signatures], does that ascertain that the data will be readable /in the future/ assuming the drive is kept in storage in the meantime? Cheers, Daniel P.S. I have another, verified backup of that partition, as well as a non-block-level backup of it, so no need to worry about that partition. From shlomif at gmail.com Sun Aug 28 04:45:21 2022 From: shlomif at gmail.com (Shlomi Fish) Date: Sun, 28 Aug 2022 04:45:21 +0300 Subject: [RFC] FOSS Licences Wars (revision 2) Message-ID: hi all! i've written a 2nd version of "FOSS Licences Wars": https://www.shlomifish.org/philosophy/computers/open-source/foss-licences-wars/rev2/ it has corrections and some new text. -- Shlomi Fish https://www.shlomifish.org/ Chuck Norris was challenged to fight the world, and accepted. He bet on himself, won, and collected the bet money. Please reply to list if it's a mailing list post - http://shlom.in/reply . From vordoo at yahoo.com Sun Aug 28 17:48:55 2022 From: vordoo at yahoo.com (Vordoo) Date: Sun, 28 Aug 2022 17:48:55 +0300 Subject: Fwd: dd(8)-written disk has ~800MB of NULs In-Reply-To: <8880e0ee-acd6-fcf0-08fa-18ea8727ef7f@yahoo.com> References: <8880e0ee-acd6-fcf0-08fa-18ea8727ef7f@yahoo.com> Message-ID: <8d83ce68-ab4e-179a-188f-38e735a31eb8@yahoo.com> An HTML attachment was scrubbed... URL: