Re: [OFFTOPIC] 1149 (was: lonk (wss: Meta: behavior on list))
On Saturday 14 August 2021 08:44:44 to...@tuxteam.de wrote: > On Sat, Aug 14, 2021 at 07:37:00AM -0500, John Hasler wrote: > > tomas writes: > > > But... Usenet was /before/ 'phone, wasn't it? > > > > Yup. Back in the 1860s we did UUCP over manual telegraph. Earlier > > yet we used heliograph. Signal fires on hilltops were slow, but > > worked. And, of course, pigeons. > > Yes! Pigeons! UUCP over Avian Carrier. Later they shamelessly copied > that in rfc1149 [1]. > > (now seriously: my first Usenet feed actually was over UUCP over... > a 14.4k modem) > > Cheers > > [1] https://en.wikipedia.org/wiki/IP_over_Avian_Carrier > > - t Chuckle, you were a bit late to that party Tomas. When I first accessed Delphi, I used a 300 baud modem on a trs-80 color computer running os9. That was before Judge Green, and the 16 air miles to the access point was still long distance. So my coco ran my LD bill up over $100 some months. Nobody had 56k modems yet. I was in hog heaven when I got my first 1200 baud modem. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Still on stretch, getting ready for bullseye
Greetings all; I just installed another sata controller and 4 1 T-byte Samsung SSD's. The controller claims to be a 15 port port expander, but only 6 are bonded out, and collectively show up at ata7 in dmesg. They show up as /dev/sde/f/g/h but have not otherwise been touched. So I thought I'd make sure I was up to date, annd possibly install some raid-ish stuff to prepare this array for use as /home in the bullseye install, but something is ay least 5000% aglay. sudo apt update says it wants to gut much of the system and upgrade 2588 packages. Yet my repo list looks like its normal stretch. What is going on? Do I wind up on buster or should I kiss it all goodbye? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 08:05:27 Dan Ritter wrote: > Gene Heskett wrote: > > Greetings all; > > > > I just installed another sata controller and 4 1 T-byte Samsung > > SSD's. > > > > The controller claims to be a 15 port port expander, but only 6 are > > bonded out, and collectively show up at ata7 in dmesg. > > > > They show up as /dev/sde/f/g/h but have not otherwise been touched. > > > > So I thought I'd make sure I was up to date, annd possibly install > > some raid-ish stuff to prepare this array for use as /home in the > > bullseye install, but something is ay least 5000% aglay. > > > > sudo apt update says it wants to gut much of the system and upgrade > > 2588 packages. Yet my repo list looks like its normal stretch. > > > > What is going on? Do I wind up on buster or should I kiss it all > > goodbye? > > Tell us more about what you're doing, but also remember that you > can't skip stable versions in an upgrade - you need to upgrade > from stretch to buster, then to bullseye. > > -dsr- I am subbed Dan, don't need the Cc: Tell me where to read about an insitu upgrade from stretch to buster, its running very well on 5 other machines here. Or is that what apt wants to do this Monday morning by wanting to upgrade 2588 packages? This is an uptodate stretch, last checked day before yesterdaty, aka Saturday, but now it wants to do this: root@coyote:~$ apt update Hit:1 http://security.debian.org stretch/updates InRelease Hit:2 http://linuxcnc.org stretch InRelease Hit:3 https://deb.debian.org/debian oldstable InRelease Hit:4 http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/debian stretch InRelease Hit:5 http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian stretch InRelease Reading package lists... Done Building dependency tree Reading state information... Done 2588 packages can be upgraded. Run 'apt list --upgradable' to see them. 2 hours later it still wants to do that. That is enough to put me on buster. IF it works. That is the $64,000 question, will it work? Or has somebody misscopied the apt list from buster to stretch? Thanks Dan. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 09:01:32 Gene Heskett wrote: My mis-steak, its Tuesday not Monday. > On Tuesday 17 August 2021 08:05:27 Dan Ritter wrote: > > Gene Heskett wrote: > > > Greetings all; > > > > > > I just installed another sata controller and 4 1 T-byte Samsung > > > SSD's. > > > > > > The controller claims to be a 15 port port expander, but only 6 > > > are bonded out, and collectively show up at ata7 in dmesg. > > > > > > They show up as /dev/sde/f/g/h but have not otherwise been > > > touched. > > > > > > So I thought I'd make sure I was up to date, annd possibly install > > > some raid-ish stuff to prepare this array for use as /home in the > > > bullseye install, but something is ay least 5000% aglay. > > > > > > sudo apt update says it wants to gut much of the system and > > > upgrade 2588 packages. Yet my repo list looks like its normal > > > stretch. > > > > > > What is going on? Do I wind up on buster or should I kiss it all > > > goodbye? > > > > Tell us more about what you're doing, but also remember that you > > can't skip stable versions in an upgrade - you need to upgrade > > from stretch to buster, then to bullseye. > > > > -dsr- > > I am subbed Dan, don't need the Cc: > > Tell me where to read about an insitu upgrade from stretch to buster, > its running very well on 5 other machines here. > > Or is that what apt wants to do this Monday morning by wanting to > upgrade 2588 packages? This is an uptodate stretch, last checked day > before yesterdaty, aka Saturday, but now it wants to do this: > > root@coyote:~$ apt update > Hit:1 http://security.debian.org stretch/updates InRelease > Hit:2 http://linuxcnc.org stretch InRelease > Hit:3 https://deb.debian.org/debian oldstable InRelease > Hit:4 > http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0 >/debian stretch InRelease > Hit:5 > http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian > stretch InRelease > Reading package lists... Done > Building dependency tree > Reading state information... Done > 2588 packages can be upgraded. Run 'apt list --upgradable' to see > them. > > 2 hours later it still wants to do that. That is enough to put me on > buster. IF it works. That is the $64,000 question, will it work? Or > has somebody misscopied the apt list from buster to stretch? > > Thanks Dan. > > Cheers, Gene Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 09:08:43 Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:01:32AM -0400, Gene Heskett wrote: > > Tell me where to read about an insitu upgrade from stretch to > > buster, > > https://www.debian.org/releases/stable/amd64/release-notes/ > > > root@coyote:~$ apt update > > Hit:1 http://security.debian.org stretch/updates InRelease > > Hit:2 http://linuxcnc.org stretch InRelease > > Hit:3 https://deb.debian.org/debian oldstable InRelease > > Hit:4 > > http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0 > >.0/debian stretch InRelease > > Hit:5 > > http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian > > stretch InRelease > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > 2588 packages can be upgraded. Run 'apt list --upgradable' to see > > them. > > > > 2 hours later it still wants to do that. That is enough to put me on > > buster. IF it works. > > You literally have the word "oldstable" in your sources.list for your > main Debian repository? That's a really unsound practice. It will > lead to unexpected release upgrades (or worse, unexpected *failed* > release upgrades). > Now I am doubly confused, according to what I'm looking at in the synaptic repo list, I do have that in the first entry, disabled now. I sure don't recall adding that as it had to be added since Saturday. And now its only two to be updated, lightning and t-bird, not 2588 packages. > You also have multiple third-party repositories in your sources.list. > It's strongly recommended that you remove those during the release > upgrade. You may or may not also have to remove the *packages* that > came from them. It'll be on an "at your own risk" basis if you don't. Several folks on the TDE mailing list have already reported no problems doing the update. Ditto for linuxcnc, although they may have to build a realtime kernel before linuxcnc will run right again. But thats a special case for the other machines here, and not applicable to this one which isn't running machinery heavier than a tabloid sized brother printer. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 12:00:57 Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 07:24:45AM -0400, Gene Heskett wrote: > > Greetings all; > > > > I just installed another sata controller and 4 1 T-byte Samsung > > SSD's. > > > > The controller claims to be a 15 port port expander, but only 6 are > > bonded out, and collectively show up at ata7 in dmesg. > > > > They show up as /dev/sde/f/g/h but have not otherwise been touched. > > > > So I thought I'd make sure I was up to date, annd possibly install > > some raid-ish stuff to prepare this array for use as /home in the > > bullseye install, but something is ay least 5000% aglay. > > > > sudo apt update says it wants to gut much of the system and upgrade > > 2588 packages. Yet my repo list looks like its normal stretch. > > > > What is going on? Do I wind up on buster or should I kiss it all > > goodbye? > > > > Thanks. > > > > Cheers, Gene Heskett > > -- > > "There are four boxes to be used in defense of liberty: > > soap, ballot, jury, and ammo. Please use in that order." > > -Ed Howdershelt (Author) > > If we desire respect for the law, we must first make the law > > respectable. - Louis D. Brandeis > > Genes Web page <http://geneslinuxbox.net:6309/gene> > > I think the others have mostly covered this but: > > Do the update to Buster - take it as slow as you need to. Bring it > bang up to date. Where do I find the recipe to update stretch to buster? Thank you Andrew. > For the Buster to Bullseye - > > READ RELEASE NOTES :) > > Use apt. > > Change sources list. https://wiki.debian.org/SourcesList > > apt update > > apt upgrade > > [That will upgrade any services / packages that can be upgraded > in place without compromising anything else.] > > apt full-upgrade > > [Which will do the final upgrade and sort otu the warning messages > about distribution has changed etc.] > > Good luck, should be relatively straightforward. > > Andy Cater Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 16:57:44 Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: > > Where do I find the recipe to update stretch to buster? > > It's still at > <https://www.debian.org/releases/buster/amd64/release-notes/>. Thats fine but its html in little pieces, so if the update destroys my network. I'm DIW. so where is the complete .pdf so I can read hard copy without a network? Thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 17:45:49 piorunz wrote: > On 17/08/2021 21:57, Greg Wooledge wrote: > > On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: > >> Where do I find the recipe to update stretch to buster? > > > > It's still at > > <https://www.debian.org/releases/buster/amd64/release-notes/>. > > Or to by more precise, that's what most important to thread author: > > https://www.debian.org/releases/buster/amd64/release-notes/ch-upgradin >g.en.html > Lots closer to what I am looking for. Thank you. > -- > > With kindest regards, piorunz. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org > ⠈⠳⣄ Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: > > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > > > Where do I find the recipe to update stretch to buster? > > > > What, in this helpful thread, do you find difficult to understand? > > > > You have a collection of important machines in your charge. The > > complexity of managing them does not appear to be your forte. > > Eptness appears to have deserted you. > > > > Stick wuth what you have. It is less strain on you and on us. :) > > > > -- > > Brian. > > Brian - maybe a bit more consideration? Any of us can be exasperating > but it's worth spending some time with Gene to get it right. > > Gene, > > You have two upgrades to do. > > One from stretch -> buster. 9-10 That takes you from 2017 -> 2019. > > If you can reduce your /etc/apt/sources.list by commenting out third > party repositories like Trinity, that will help. > > [Taken from https://wiki.debian.org/LTS/Using] > > The Stretch /etc/apt/sources.list should look like this: > > deb http://deb.debian.org/debian/ stretch main contrib non-free > deb-src http://deb.debian.org/debian/ stretch main contrib non-free > > deb http://security.debian.org/ stretch/updates main contrib non-free > deb-src http://security.debian.org/ stretch/updates main contrib > non-free > > Bring Stretch up to date finally: apt update ; apt full-upgrade > > Go find the release notes for Buster: > > https://www.debian.org/releases/buster/amd64/release-notes/index.en.ht >ml - especially Section 4 and 5 > > Buster sources.list - Buster was the first list to use deb.debian.org > extensively > > deb http://deb.debian.org/debian/ buster main contrib non-free > deb-src http://deb.debian.org/debian/ buster main contrib non-free > > deb http://security.debian.org/debian-security buster/updates main > contrib non-free deb-src http://security.debian.org/debian-security > buster/updates main contrib non-free > > [Taken from https://wiki.debian.org/DebianUpgrade] > > Use apt update ; apt upgrade ; apt full-upgrade (optionally apt > autoremove) > > Buster to Bullseye - 10-11 - 2019-2021 > > Follow the same process again, essentially > > Bullseye sources.list > > deb http://deb.debian.org/debian bullseye main contrib non-free > deb-src http://deb.debian.org/debian bullseye main contrib non-free > > deb http://deb.debian.org/debian-security/ bullseye-security main > contrib non-free deb-src http://deb.debian.org/debian-security/ > bullseye-security main contrib non-free > > deb http://deb.debian.org/debian bullseye-updates main contrib > non-free deb-src http://deb.debian.org/debian bullseye-updates main > contrib non-free > > Uncomment third party repositories - change appropriately, then apt > update ; apt upgrade ; apt full-upgrade > > It's worth taking time to do this and writing down what step you've > taken (or just print off the appropriate pages and use them as a tick > list) There's a lot to do and it's _easy_ to mess up. > > Take care - all best, as always, > > Andy Cater Thank you Andy, thats more of the recipe I need to follow. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: > > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > > > Where do I find the recipe to update stretch to buster? > > > > What, in this helpful thread, do you find difficult to understand? > > > > You have a collection of important machines in your charge. The > > complexity of managing them does not appear to be your forte. > > Eptness appears to have deserted you. > > > > Stick wuth what you have. It is less strain on you and on us. :) > > > > -- > > Brian. > > Brian - maybe a bit more consideration? Any of us can be exasperating > but it's worth spending some time with Gene to get it right. > > Gene, > > You have two upgrades to do. > > One from stretch -> buster. 9-10 That takes you from 2017 -> 2019. > > If you can reduce your /etc/apt/sources.list by commenting out third > party repositories like Trinity, that will help. > > [Taken from https://wiki.debian.org/LTS/Using] > > The Stretch /etc/apt/sources.list should look like this: > > deb http://deb.debian.org/debian/ stretch main contrib non-free > deb-src http://deb.debian.org/debian/ stretch main contrib non-free > > deb http://security.debian.org/ stretch/updates main contrib non-free > deb-src http://security.debian.org/ stretch/updates main contrib > non-free > > Bring Stretch up to date finally: apt update ; apt full-upgrade I am here, and there was only a long lit of autoremoves, which I did. I was already uptodate. > Go find the release notes for Buster: > > https://www.debian.org/releases/buster/amd64/release-notes/index.en.ht >ml - especially Section 4 and 5 downoaded and printed setion 4 and section 5 but since I have 5 machines running buster from fresh installs from the linuxcnc site which is the same but with a realtime kernel, I don't expect any real showstoppers, but I've made dead tree out of both just in case. I'll let this simmer for 3 or 4 days, giving amanda a chance to catch up, then continue from here. Thank you Andrew. To Greg and Brian: I hope you both make it to my age, where poor short term memory will have become a daily fact, and that your experience by then is as wide as mine. I do have interests far wider than just debian. When I wrote my first program, it was for a tv station, ran on an rca 1802. That was 1979, and it was usefull enough they were still using it several times a day in 1995. Computers have gotten a few hunbred times faster and at least 100x more capable AND complex today. And I do have other interests. To many it seems. You've no doubt heard that water is not compressible, but in fact it is, it just takes another 7 miles of water on top of it to do it. I had fingerprints on the pcb's in the camera's that were on the Trieste when it went down into the mohole that took those pictures that proved it over 60 years ago. > Buster sources.list - Buster was the first list to use deb.debian.org > extensively > > deb http://deb.debian.org/debian/ buster main contrib non-free > deb-src http://deb.debian.org/debian/ buster main contrib non-free > > deb http://security.debian.org/debian-security buster/updates main > contrib non-free deb-src http://security.debian.org/debian-security > buster/updates main contrib non-free > > [Taken from https://wiki.debian.org/DebianUpgrade] > > Use apt update ; apt upgrade ; apt full-upgrade (optionally apt > autoremove) > > Buster to Bullseye - 10-11 - 2019-2021 > > Follow the same process again, essentially > > Bullseye sources.list > > deb http://deb.debian.org/debian bullseye main contrib non-free > deb-src http://deb.debian.org/debian bullseye main contrib non-free > > deb http://deb.debian.org/debian-security/ bullseye-security main > contrib non-free deb-src http://deb.debian.org/debian-security/ > bullseye-security main contrib non-free > > deb http://deb.debian.org/debian bullseye-updates main contrib > non-free deb-src http://deb.debian.org/debian bullseye-updates main > contrib non-free > > Uncomment third party repositories - change appropriately, then apt > update ; apt upgrade ; apt full-upgrade > > It's worth taking time to do this and writing down what step you've > taken (or just print off the appropriate pages and use them as a tick > list) There's a lot to do and it's _easy_ to mess up. > > Take care - all best, as always, > > Andy Cater Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Still on stretch, getting ready for bullseye
On Wednesday 18 August 2021 08:05:43 Andrew M.A. Cater wrote: > On Wed, Aug 18, 2021 at 09:12:24AM +0100, Tixy wrote: > > On Wed, 2021-08-18 at 09:03 +0200, to...@tuxteam.de wrote: > > > On Tue, Aug 17, 2021 at 10:01:32PM -0400, Greg Wooledge wrote: > > > > On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote: > > > > > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > > > > > > [an abridged version of the release notes] > > > > > > > > > > Thank you Andy, thats more of the recipe I need to follow. > > > > > > > > > > Cheers, Gene Heskett > > > > > > > > See, *this* is exactly what I tried to avoid -- giving someone > > > > an inferior version of the release notes, empowering their > > > > laziness, > > > > > > [...] > > > > Greg *was* trying to help Gene (and us) by getting him to read > > documentation from the Debian project, rather than picking one of > > several different 'easy' suggestions from this list. > > > > If you read the release notes you get a clue what to expect and what > > to do. Or you can not bother and just rely on the helpful people on > > this list. > > > > I know from my upgrade to Buster I had to take action due to > > AppArmor and nftables now being default and ending up migrating from > > legacy network names to new 'predictable' network names. Looking at > > the release notes again, there's also changes to increase security > > with sshd and OpenSSL, and with Systemd needing entropy at boot > > (Gene has some ARM boards the latter may hit). > > > > Want to take bets that Gene won't be back in a few days with > > problems caused by some of the above changes? He could save himself, > > and you, time and hassle if he read the release notes. > > Yes, yes, and yes. Agreed that you should read the release notes. > > I tried to put more of it into one email with pointers to where the > info was derived from so that it was in one place rather than five > emails. A convenience factor - not detracting from anybody else's > suggestions. > > Like all of us, Gene has his own ways of doing things, his own > habits and his own ability to do things. That's a necessarily > "different approach from the way I'd do it / different from my > experience / abd I'm sure I could do it better myself" situation. > > That's OK - his systems, his problems to sort if stuff goes > wrong - and yes, we could get into a to and fro of a longer thread - > but if any one of the emails above sorts out how to do this with good > will and good humour - it's a net win for all concerned. > And I should also point out that the 147 IQ I tested at in the 6th grade nominally 75 years ago, is at 86, no longer daily achieved, even with a daily B1 in the pilltainer. I guess he isn't ready for me, or I'd have missed roll call years ago, but most pulmonary embolisms, which I had at 79 yo courtesy of a "one a day" vitamin with way too much vitamin k in it, have a 2% survival rate, but the oxygen starvation did cost me some of those. And while doing this, I am also doing a pair of designs in openscad, one of a rotary drive for a cnc machine, Costing 1% of the commercial product, and ATM, measureing parts that have never been combined to make a mount for a sherpa direct drive 3d printers extruder driver, and a cheap haldis "volcano" hot end assembly with a side mounted BLTouch probe. All to fit on a CR10-S Pro V2 printer whose hot end was cooked out of service by the increase in temps that feeding it PETG filament needs. All that is way off-topic for this list, only related to show where I now am mentally/physically. How many 86 yo's do you know that can still claim doing that... But now it takes me a week to recover from what I once did all day. That tends to go with a rebuilt heart thats pumping 30% of what it did 70 year ago, now timed by a pacemaker. > The list archives are searchable: Google will find stuff on keywords > and the next person to look will find some element of step by step > instructions. And that has to be good for far more folks than this fading old fart represents. Thank you. And take care, ALL of you. > > -- > > Tixy > > All the best to all on the list, as ever, > > Andy Cater Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: smart fans
On Sunday 22 August 2021 12:46:14 Polyna-Maude Racicot-Summerside wrote: > On 2021-08-22 10:02 a.m., Emanuel Berg wrote: > > tomas wrote: > >> I disagree. The thing poses [1] as a DC motor (2 pins power, > >> one tacho). I don't think you get too much control over RPM > > > > That's what you get with the 4th wire/pin? A sensor to > > read RPM? > > Opposite > 3 wire = 2 wire to drive motor + 1 wire to get speed > 4 wire = 2 wire to drive, 1 to get speed, 1 to modify speed > I as a CET, am totally unimpressed with the miss-information being thrown about in this thread. A total lack of how its actually done in real hardware. 1. Any si diode, passing a few microamps of fwd current, is in fact an excellent, does not need to be calibrated, thermometer capable of 1 degree C accuracy. There are several million candidates buried in todays cpu's. 2, even a 2 wire fan can be controlled by using this voltage to determine the on time of a small transistor. Often down to 1% speed at room tmps, so other than the cost of the time at die bondout time, its free. The 1% minimum is actually used to help distribute the motors lubricant. 3, boiled down, the temp measured by this diode can be scaled to control the fan to maintain the device being monitored at a fixed maximum temp, and its done on 2 or 3 of the gates on the cpu die intended to be used to replace a bad gate in you cpu. Intelligently done at test and bondout time, it might add 10 seconds to the time needed to verify the rest of the chip. > > "What you can't measure, you can't control" Better, if you can measure it, you can control a 2 wite motor. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: smart fans
On Sunday 22 August 2021 17:04:06 Gene Heskett wrote: > On Sunday 22 August 2021 12:46:14 Polyna-Maude Racicot-Summerside wrote: > > On 2021-08-22 10:02 a.m., Emanuel Berg wrote: > > > tomas wrote: > > >> I disagree. The thing poses [1] as a DC motor (2 pins power, > > >> one tacho). I don't think you get too much control over RPM > > > > > > That's what you get with the 4th wire/pin? A sensor to > > > read RPM? > > > > Opposite > > 3 wire = 2 wire to drive motor + 1 wire to get speed > > 4 wire = 2 wire to drive, 1 to get speed, 1 to modify speed > > I as a CET, am totally unimpressed with the miss-information being > thrown about in this thread. A total lack of how its actually done in > real hardware. > > 1. Any si diode, passing a few microamps of fwd current, is in fact an > excellent, does not need to be calibrated, thermometer capable of 1 > degree C accuracy. There are several million candidates buried in > todays cpu's. > > 2, even a 2 wire fan can be controlled by using this voltage to > determine the on time of a small transistor. Often down to 1% speed at > room tmps, so other than the cost of the time at die bondout time, its > free. The 1% minimum is actually used to help distribute the motors > lubricant. > > 3, boiled down, the temp measured by this diode can be scaled to > control the fan to maintain the device being monitored at a fixed > maximum temp, and its done on 2 or 3 of the gates on the cpu die > intended to be used to replace a bad gate in you cpu. Intelligently > done at test and bondout time, it might add 10 seconds to the time > needed to verify the rest of the chip. > > > > "What you can't measure, you can't control" > > Better, if you can measure it, you can control a 2 wite motor. > And I knew I couldn't get by without a typu. s/b wire. In fact, if a motor has 3 wires, there is a good chance its a tacho wire, used ONLY to tell /you/ how fast its running. > Cheers, Gene Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: New SSD card for old dell 850
On Wednesday 25 August 2021 07:59:50 juh wrote: > Dear all, > > there is a LITEONIT LMT-32L3M (LWDA) in my dell xps 850 desktop > computer. I use it for the boot and system partitions, home is on a > hard disk. > > The SSD only has 32GB and I am pondering whether I can just attach a > bigger one and reinstall debian mounting / and /home to the ssd and > using the hard disk for archives. > > Here is picture of it: > https://www.ebay.com/p/668700327 Which is called an mSATA interface, and if you scroll down, there are links to mSATA LiteOn drives up to 128GB for under a $30 bill. Seems like a relatively low risk gamble to get one and try it. <https://www.ebay.com/p/1282481418?iid=234065274043> > But I fear that it requires a sort of miniPCI interface that modern > SSDs does not have. Can anyone confirm this or even better hint to a > compatible product? > > TIA > juh Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
old handicam movie camera and kino
Did work 15 years ago, but despite a new PCI-E firewire card, does not now work with kino, no remote controls. kino does recognize the device in it prefs and calls it by its name, a DCR-TRV460NTSC. What do I do to ident the error? It used to work with libraw1394, but that doesn't seem to be in the repo's now. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
old handicam movie camera and kino
Did work 15 years ago, but despite a new PCI-E firewire card, does not now work with kino, no remote controls. kino does recognize the device in it prefs and calls it by its name, a DCR-TRV460NTSC. What do I do to ident the error? It used to work with libraw1394, but that doesn't seem to be in the repo's now. I think I have everything else that kino uses, dvgrab, the rest of the 1394 stuff too, recognized in dmesg as /dev/fw0, but only at S100 speed. it S/B S400. Or was in 2004 when this camera was new. from dmesg: firewire_core :06:00.0: rediscovered device fw0 [21283.489871] firewire_core :06:00.0: phy config: new root=ffc1, gap_count=5 [21284.001594] firewire_core :06:00.0: rediscovered device fw0 [21284.094990] firewire_core :06:00.0: created device fw1: GUID 08004601044684e4, S100 [21286.593537] firewire_core :06:00.0: giving up on node ffc0: reading config rom failed: bus reset [22027.880117] firewire_core :06:00.0: rediscovered device fw0 [22027.880131] firewire_core :06:00.0: phy config: new root=ffc1, gap_count=5 [22028.391961] firewire_core :06:00.0: rediscovered device fw0 [22028.482526] firewire_core :06:00.0: created device fw1: GUID 08004601044684e4, S100 [22031.047900] firewire_core :06:00.0: giving up on node ffc0: reading config rom failed: bus reset Am I missing the cards driver or ?? greping lsmod for firewire gets: firewire_ohci 45056 0 firewire_core 81920 1 firewire_ohci crc_itu_t 16384 1 firewire_core Thanks for any advise dredged up from ancient memory. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: old handicam movie camera and kino
On Sunday 29 August 2021 03:33:22 to...@tuxteam.de wrote: > On Sat, Aug 28, 2021 at 09:25:40PM -0400, Gene Heskett wrote: > > Did work 15 years ago, but despite a new PCI-E firewire card, does > > not now work with kino, no remote controls. > > [...] > > > [21286.593537] firewire_core :06:00.0: giving up on node ffc0: > > reading config rom failed: bus reset > > No idea about firewire, but my brain extension [1] yields some > leads which sound half-promising. > > Cheers > [1] > https://html.duckduckgo.com/html/?q=firewire_core+%22giving+up+on+node >%22+%22reading+config+rom+failed%22+%22bus+reset%22 - t Chased down some likely suspects, and got the camera controls working so I can see the wedding on the tape in kino. But if I try to unmute the audio, I get a steady stream of can't open /dev/dsp so I'm still missing an audio codec I think. Usual suspects? Probably alsa-something?. Thanks Tomas. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: old handicam movie camera and kino
On Sunday 29 August 2021 06:18:46 to...@tuxteam.de wrote: > On Sun, Aug 29, 2021 at 04:55:46AM -0400, Gene Heskett wrote: > > On Sunday 29 August 2021 03:33:22 to...@tuxteam.de wrote: > > > On Sat, Aug 28, 2021 at 09:25:40PM -0400, Gene Heskett wrote: > > > > Did work 15 years ago, but despite a new PCI-E firewire card, > > > > does not now work with kino, no remote controls. > > > > > > [...] > > > > > > > [21286.593537] firewire_core :06:00.0: giving up on node > > > > ffc0: reading config rom failed: bus reset > > > > > > No idea about firewire, but my brain extension [1] yields some > > > leads which sound half-promising. > > > > > > Cheers > > > [1] > > > https://html.duckduckgo.com/html/?q=firewire_core+%22giving+up+on+ > > >node %22+%22reading+config+rom+failed%22+%22bus+reset%22 - t > > > > Chased down some likely suspects, and got the camera controls > > working so I can see the wedding on the tape in kino. > > > > But if I try to unmute the audio, I get a steady stream of can't > > open /dev/dsp so I'm still missing an audio codec I think. > > Can't-open-permission-denied or can't-open-no-such-file-or-directory? > no such file. Thanks Tomas > Cheers > - t Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: old handicam movie camera and kino
On Sunday 29 August 2021 08:21:11 Greg Wooledge wrote: > On Sun, Aug 29, 2021 at 12:18:46PM +0200, to...@tuxteam.de wrote: > > On Sun, Aug 29, 2021 at 04:55:46AM -0400, Gene Heskett wrote: > > > But if I try to unmute the audio, I get a steady stream of can't > > > open /dev/dsp so I'm still missing an audio codec I think. > > > > Can't-open-permission-denied or > > can't-open-no-such-file-or-directory? > > You're absolutely correct that Gene should try to get in the habit > of including *useful* information in his help requests. This includes > exact error messages. > > In this case, we can probably guess that he's missing the OSS > emulation layer. He's probably running something so incredibly old > that it *actually* still tries to use OSS -- thus the attempts to open > /dev/dsp. > > unicorn:~$ ls -l /dev/dsp > ls: cannot access '/dev/dsp': No such file or directory > > To solve that, he might try installing this guy: > > unicorn:~$ apt-cache search alsa dsp > alsa-oss - ALSA wrapper for OSS applications > [...] That wasn't the magic twanger Greg. from the terminal kino was launched in: ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp Could not open ALSA device "/dev/dsp": No such file or directory thousands of them. Camera speaker is alive though. Thanks Greg. > I can't claim any personal experience with it, though. I don't know > what steps are required beyond installing the package. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Solved! Re: old handicam movie camera and kino
On Sunday 29 August 2021 10:16:01 to...@tuxteam.de wrote: > On Sun, Aug 29, 2021 at 09:56:43AM -0400, Gene Heskett wrote: > > [...] > > > That wasn't the magic twanger Greg. > > but he was up the right path. /dev/dsp is part of the (by now > archaeological) OSS sound interface. > > To make /dev/dsp "appear", you need a kernel module faking it. > > For me, "sudo modprobe snd-pcm-oss" does that trick [1]. Catting > /etc/passwd to it actually produces some sound, albeit the accent > is a bit... slithery ;-) And was an endless machine gun until ctl+c'd here. cat should have ended at some point but I let it hammer for a good minute. Then sound in kino worked, quite well in fact. > Perhaps that'll do for you, perhaps you'll need additional modules. > > Proceed with fingers crossed. Works fine, thank you guys. > > Cheers > - t Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Solved! Re: old handicam movie camera and kino
On Sunday 29 August 2021 11:57:39 to...@tuxteam.de wrote: > On Sun, Aug 29, 2021 at 11:14:46AM -0400, Gene Heskett wrote: > > On Sunday 29 August 2021 10:16:01 to...@tuxteam.de wrote: > > [...] > > > > [...] Catting /etc/passwd to it actually produces some sound, > > > albeit the accent is a bit... slithery ;-) > > > > And was an endless machine gun until ctl+c'd here. cat should have > > ended at some point but I let it hammer for a good minute. > > You actually tried it :-o > I knew it was a test exersize that would produce gibberish at best from that file, and that it wuld prove the path worked. The surprising thing was that cat looped it endlessly. > I didn't expect anything meaningful out of it; just testing that > there's a path from /dev/dsp to the speakers. I was just too lazy to > find out which kind of sound format is digestible by /dev/dsp. > Funny, though, that it took so long for you. You must have a truly big > /etc/passwd... The usual stretch, I am the only user that bleeds if cut, living alone now, there are 3 or 4 others, "usefull idiots" playing in sandboxes they theroetically can't see out of. My web page is also this box, again playing in a sandbox so I have to jump thru hoops to update it. I set up iptables about 2 years back to stop the bots from mirroring it 2 or 3 times a day, burning up my upload bandwidth, and one of those bots now has a /8 on the end, and you just have to know who owns it. :) reads robots.txt, and then ignores it. > > Then sound in kino worked, quite well in fact. > > \o/ > > Glad it worked. > > Cheers > - t Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
html only email
Had better have a very interesting subjct line or it does not get read here. I have, for security reasons, told kmail to not show html, and to override that takes up to 5 mouse clicks. Plain text that gets past spamassassin and clamav, does get read 100%. So the choice as to whether or not your message is read, is up to you. If you choose to use a broken email agent, expect to be ignored. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: html only email
On Sunday 12 September 2021 07:59:49 to...@tuxteam.de wrote: > On Sun, Sep 12, 2021 at 06:59:35AM -0400, Gene Heskett wrote: > > Had better have a very interesting subjct line or it does not get > > read here. I have, for security reasons, told kmail to not show > > html, and to override that takes up to 5 mouse clicks. > > And... > > instant black background for free! Actually, Tomas, I think that is a configuration choice I made years ago and havn't touched since as these old eyes like black text on white. Plus my kmail is 1.9 since its tde's r14.0.10 version. 99.9% of kde 3.5's bugs fixed. Stable. :-) > > ;-) > > Cheers > - t Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: was: support for xfce in bullseye minimal netinst iso
On Tuesday 14 September 2021 10:08:34 Brian wrote: > On Tue 14 Sep 2021 at 09:27:25 +, Sriram wrote: > > [...] Can you suggest some links for downloading the bullseye along > > with xfce which comes to less than 1 GB or preferably somewhere > > around 500-800 MB, or suggest ways to install the xfce offline , > > there is no deb file for such GUI's. > > An xfce installation will pull in about 600 M of packages no matter > what you choose to do. Does this give some perspective? > > What I would consider is: > > 1. Skip installation of a desktop in d-i and finish the remainder of > the process. > > 2. Reboot, log in and create /etc/apt/apt.conf.d/01keep-debs. > > 3. Edit this file to have > > Binary::apt::APT::Keep-Downloaded-Packages "true"; > >Packages should remain in /var/cache/apt/archives/ for you to > reuse. No futher downloading of xfce packages is now needed. You have > your own personal "ISO" at no extra cost to disk space or bandwidth. > > 4. And finally do > > apt install task-xfce-desktop This is interesting and I will likely do it when I install the debian-11.1-net-install I just burnt. But, I have installed 4, 1 terabyte samsung SSD's on a separate non-raid controller card which I intend to use as a software raid-6 or 10 after moving the current boot disk with stretch on it to be /dev/sdd, or even leaving it disconnected until 11.1 is installed. It has precious data on its platters. Those samsungs have not been configured for anything yet. They are seen ok but individually in dmesg. Looked at by gparted, but nothing written. So, can the installer handle the configuration of those into a bootable format all by itself? If not, what do I install and do to ready them before moving /dea/sda out of harms way and booting the 11.1 net-install iso? I can if needed, install a 60 or bigger Gig SSD as the /boot partition on the motherboard controller as /dev/sda if the software raid can't be booted from. So how do I best proceed? Thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: mdadm RAID and the Bullseye installer
On Tuesday 14 September 2021 12:55:41 Dan Ritter wrote: > Gene Heskett wrote: > > This is interesting and I will likely do it when I install the > > debian-11.1-net-install I just burnt. > > > > But, I have installed 4, 1 terabyte samsung SSD's on a separate > > non-raid controller card which I intend to use as a software raid-6 > > or 10 after moving the current boot disk with stretch on it to be > > /dev/sdd, or even leaving it disconnected until 11.1 is installed. > > It has precious data on its platters. > > > > Those samsungs have not been configured for anything yet. They are > > seen ok but individually in dmesg. Looked at by gparted, but nothing > > written. > > > > So, can the installer handle the configuration of those into a > > bootable format all by itself? > > Yes. The installer can assemble them into an mdadm-style RAID 10 > and GRUB can boot from that. > > -dsr- Thank you Dan. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: was: support for xfce in bullseye minimal netinst iso
On Tuesday 14 September 2021 13:11:08 Andrew M.A. Cater wrote: > On Tue, Sep 14, 2021 at 11:49:02AM -0400, Gene Heskett wrote: > > On Tuesday 14 September 2021 10:08:34 Brian wrote: > > > On Tue 14 Sep 2021 at 09:27:25 +, Sriram wrote: > > > > [...] Can you suggest some links for downloading the bullseye > > > > along with xfce which comes to less than 1 GB or preferably > > > > somewhere around 500-800 MB, or suggest ways to install the xfce > > > > offline , there is no deb file for such GUI's. > > > > > > An xfce installation will pull in about 600 M of packages no > > > matter what you choose to do. Does this give some perspective? > > > > > > What I would consider is: > > > > > > 1. Skip installation of a desktop in d-i and finish the remainder > > > of the process. > > > > > > 2. Reboot, log in and create /etc/apt/apt.conf.d/01keep-debs. > > > > > > 3. Edit this file to have > > > > > > Binary::apt::APT::Keep-Downloaded-Packages "true"; > > > > > >Packages should remain in /var/cache/apt/archives/ for you to > > > reuse. No futher downloading of xfce packages is now needed. You > > > have your own personal "ISO" at no extra cost to disk space or > > > bandwidth. > > > > > > 4. And finally do > > > > > > apt install task-xfce-desktop > > > > This is interesting and I will likely do it when I install the > > debian-11.1-net-install I just burnt. > > > > But, I have installed 4, 1 terabyte samsung SSD's on a separate > > non-raid controller card which I intend to use as a software raid-6 > > or 10 after moving the current boot disk with stretch on it to be > > /dev/sdd, or even leaving it disconnected until 11.1 is installed. > > It has precious data on its platters. > > > > Those samsungs have not been configured for anything yet. They are > > seen ok but individually in dmesg. Looked at by gparted, but nothing > > written. > > > > So, can the installer handle the configuration of those into a > > bootable format all by itself? > > > > If not, what do I install and do to ready them before moving > > /dea/sda out of harms way and booting the 11.1 net-install iso? I > > can if needed, install a 60 or bigger Gig SSD as the /boot partition > > on the motherboard controller as /dev/sda if the software raid can't > > be booted from. > > As ever, it depends. Are you booting using UEFI? > > If so, then you'll need to allow the partitioner to configure an ESP > EFI system partition] which will allow the machine to store files for > booting. The rest can be set up using guided partitioning and mdadm. > If you're using Legacy/DOS booting - all bets are off. > > I'd be tempted to completely disconnect your stretch drive to do this > and then reconnect it just to copy dot files and ssh configs. > Essentially, stretch is gone and the likelihood of being able to use > configs directly is low - so keep it safe out of the way until you > want to copy precious data off it, at which point mount it under /mnt > or /media temporarily. > > If you have a spare 60G SSD, then you might want to use that as boot > and root filesystem anyway and let the partitioner create the RAID > system from four absolutely identically sized disks. > > One thing to watch out for in guided partitioning is that swap space > in a dedicated partition is now only 1GB by default. If you've got a > decent amount of memory, you may never hit swap anyway. I have 32G of dram, and 14G of swap now, but with a 17 day uptime, its under 2 megs in swap. I have huge buffers set in OpenSCAD. > I won't > trespass on your patience further but will be happy to help if needed. Good to know Andy IF I can get networking to survive the reboot. But my networking is host file based and usually goes away at reboot until properly configured again. So I kep a printed copy of all that stuff. There is not a functioning dhcp server here. Usually, proper routing is impossible until avahi and friends are lined up and have bloodied the wall behind them. Otherwise avahi insists on an non-functional 169.xx,xx,xx address for route and gateway. > All best, as ever, > > Andy Cater Thanks Andy. > > So how do I best proceed? > > > > Thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: (unable to start a new discussion) Re: Can surf the internet, but not my home network...
On Friday 17 September 2021 04:46:20 Brian wrote: > On Thu 16 Sep 2021 at 21:48:55 -0600, Charles Curley wrote: > > On Thu, 16 Sep 2021 19:46:43 -0300 > > > > Dedeco Balaco wrote: > > > Why am i unable to start a new discussion? I have sent 4 messages! > > > They have one attachment that is less than 150KiB - so, they are > > > not considered big, for the list, right? > > > > I consider 150 KiB to be monstrous. > > > > Have you tried sending a short message with no attachment? > > Dedeco Balaco already has two short messages showing in this thread. > That indicates he has the ability to start a new discussion. > > However, a new discussion should be started in a *new* thread, not > plonked willy-nilly into an existing thread. This is the second time > recently that someone has done that. The first time it involved an > experienced user! > > To take this thread further off-topic: there can be a good reason to > send an attachment; for example, a log. Compression would reduce its > size and is advised. Likewise, a screenshot of a problem should be loaded into gimp, re-exported as a .jpg, compressed until the colors are all screwed up. Leaving the compression at 12% quality will get a 250k screen shot, which will be blocked but jpeg throws away color before it throws away edges of text characters. So if showing a screen full of text to show the error, smunch the daylights out of it, it will still be readable. Even then its uo to the filters to say yay or nay. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: (unable to start a new discussion) Re: Can surf the internet, but not my home network...
On Friday 17 September 2021 09:10:01 Stefan Monnier wrote: > > edges of text characters. So if showing a screen full of text to > > show the error, smunch the daylights out of it, it will still be > > readable. > > Whatever happened to the idea of citing the actual text rather than > using an (unreadable) image? > > > Stefan Beats hell outta me Stefan, but a copy/paste from a terminal screen beats ALL the other methods for compression. But that involves launching whatever from a terminal screen, requiring the user to actaully type the command. Oh the horrors... Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Debian 11: Nvidia NVS 310 with nvidia driver freezes after two days
On Monday 20 September 2021 11:58:02 Charlie Gibbs wrote: > On Mon Sep 20 08:42:33 2021 "Alexander V. Makartsev" > > > wrote: > > On 19.09.2021 16:22, Roger Price wrote: > >> My Nvidia NVS 310 card with the nvidia 390.144 driver starts off > >> perfectly, but after two days freezes: no reaction to keyboard or > >> mouse action. > > > > Have you tried to run some benchmarks to force the issue? By doing > > that you could reveal some potential problem with inadequate > > cooling or problems of electrical nature. > > It is quite old hardware so it is hard to tell for sure. There > > could be myriad reasons why it freezes, ranging from faulty > > capacitors on motherboard and VGA to a faulty PSU. > > I was having similar problems with an old nVidia card (GeForce 630). > A friend gave me an ATI card to try. Although I never did get his > card to work, I did discover that my old card was in rough shape > physically. The fan had broken down, and the cooling fins on the > heat sink were full of dust bunnies. There wasn't much I could do > for the fan, but I gave the heat sink a thorough cleaning and put > the card back in. It's been running for over a week now with no > problems, where before it was locking up every day or two. > Fans can be replaced, there are vendors on ebay selling better quality replacements if you shop carefully. > >> I still have nouveau present. dpkg-query -l | grep nouveau > >> reports: ii libdrm-nouveau2:amd64 2.4.104-1 amd64 Userspace > >> interface to nouveau-specific kernel DRM services -- runtime > >> ii xserver-xorg-video-nouveau 1:1.0.17-1 amd64 X.Org X server -- > >> Nouveau display driver > > > > Doesn't matter if you have 'nouveau' installed, since proprietary > > nvidia driver blacklists it for you upon installation. > > On earlier versions of Debian (I'm currently running Buster), > I was having trouble with the nouveau driver locking up. > Replacing it with nVidia's proprietary driver corrected > that problem, so I've been wary of nouveau ever since. > But if your graphics card overheats, it doesn't matter > which driver you're running. :-) Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: The future of computing.
On Wednesday 22 September 2021 20:58:14 Nate Bargmann wrote: > * On 2021 22 Sep 16:14 -0500, harrywea...@tutanota.com wrote: > > For those with an interest: > > > > https://register.gotowebinar.com/register/5204765206263907088 > > Hmmm, as a radio amateur when I see QST, I immediately think of the > membership journal of the American Radio Relay League which has been > published since 1915 with a two year break for the Great War from 1917 > to 1919. > > Maybe IBM bought the rights to the name! > > - Nate Or the ARRL forgot to renew the copyright. Copyrights were originally issued for a period of 7 years, renewable once for an additional 7 years. Along comes Walt Disney and Mickey Mouse, and Walt had money enough to get the law changed so we have the current never expires situation by including corporations such as Disney in it definitions of authors. If its ever been renewed. But the law today gives me automatic copyright over what I write without additional public notice, I think for 90 years after I die. There is something wrong with this picture. 14 years was considered as the author having milked his writings for 99% of all they would ever generate in income. IMNSHO it (the original version) is still a good idea. Stealing an individuals creativity, and his rewards for being creative by awarding the copyright to a corporation, is theft pure and simple, and should become somebody lined up against the wall for 3rd offence grand larceny. But today, we'ed need Trumps incompleted wall to maybe have enough wall. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: The future of computing.
On Wednesday 22 September 2021 22:23:29 Nicholas Geovanis wrote: > On Wed, Sep 22, 2021, 9:13 PM Gene Heskett wrote: > > > > There is something wrong with this picture. 14 years was considered > > as the author having milked his writings for 99% of all they would > > ever generate in income. IMNSHO it (the original version) is still a > > good idea. Stealing an individuals creativity, and his rewards for > > being creative by awarding the copyright to a corporation, is theft > > pure and simple, > > Centuries ago a philosopher wrote: Behind every great fortune lies an > equally great crime. In America too I'm afraid. > We have no patent on it. > and should become somebody lined up against the wall for 3rd > > > offence grand larceny. But today, we'ed need Trumps incompleted wall > > to maybe have enough wall. > > No there aren't that many millionaires and billionaires and They > make sure of it. > This is true, but I'd also include the mba's who's major lesson to those billionaires is its ok to do it if you don't get caught. And buy them off or do away with the witnesses if you do get caught. Jeffery E. got caught but he was not the king pin, just the disposable front man. Same game continues, new address & phone number. > Cheers, Gene Heskett > > > -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: OT: Copyrights and patents (was: Re: The future of computing.)
On Thursday 23 September 2021 07:22:17 rhkra...@gmail.com wrote: > On Wednesday, September 22, 2021 10:12:49 PM Gene Heskett wrote: > > Or the ARRL forgot to renew the copyright. Copyrights were > > originally issued for a period of 7 years, renewable once for an > > additional 7 years. > > Hmm, without looking it up, I thought the 7/7 years was for patents, > and copyright was a little different (maybe like 13/13?)? (But Gene > probably remembers better than I do.) Debatable, mine will be 87 in a few days, but I didn't get political in my thinking until I could vote. But before I voted, I felt strong enough about the honest man that took my mother and her baby on with without ever having enough money to adopt me as Iowa made that a very expensive process, so on turning 21 I turned that respect into changing my last name to match his. That I could do for a $20 bill. He is now long gone, but has great, great, great grandkids wearing his name. > > Along comes Walt Disney and Mickey Mouse, and Walt had money > > enough to get the law changed so we have the current never expires > > situation by including corporations such as Disney in it definitions > > of authors. If its ever been renewed. But the law today gives me > > automatic copyright over what I write without additional public > > notice, I think for 90 years after I die. > > Something like that, but doesn't sound quite right (wish I had a > better memory). Previously copyrighted works are coming into the > "public domain" year by year, about 95 years after -- oh, maybe it is > after the author's death? Something like that. The point I was trying to make is that today, the law is for sale to the highest bidder. It is no longer "of the people, by the people, for the people". One of the reasons I like debian, they have set a set of principles and are sticking to them far better than today's version of the Republic the founders envisioned in the late 1700's. > Maybe there is an alternate path to > copyright expiring? Not sure how it works if a corporation owns a > copyright -- I don't think it is perpetual. > > And, at least some of the relevant laws differ by nation. > > > There is something wrong with this picture. 14 years was considered > > as the author having milked his writings for 99% of all they would > > ever generate in income. IMNSHO it (the original version) is still a > > good idea. Stealing an individuals creativity, and his rewards for > > being creative by awarding the copyright to a corporation, is theft > > pure and simple, > > Hmm, I don't think the copyright law nor the government award the > copyright to a corporation. If a corporation gets a copyright (or > patent) that is based on some explicit contractual or implicit (like > the "work for hire" doctrine) agreement > > > Cheers, Gene Heskett Anyway, this is off-topic for this list, and I should apologize for bringing up what has been for me, a very sore subject. So, last post. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Proprietary USB Drivers; Ya Gotta' Love'em.
On Saturday 25 September 2021 14:11:30 Martin McCormick wrote: > Charles Curley writes: > > Possibly a known kernel bug. > > > > https://forums.opensuse.org/showthread.php/538695-USB-driver-Zero-Le > >ngth-Descriptor > > > > https://lore.kernel.org/lkml/1507709452-31260-1-git-send-email-msala > >u...@iotecha.com/ > > > > -- > > Does anybody read signatures any more? > > > > https://charlescurley.com > > https://charlescurley.com/blog/ > > Thank you. That's got to be it. I've been doing debian Linux since > right around 2000 but I must admit that I don't know the easiest > way to include the patch referenced in the second link. > > I will need to do that on an i86 box plus the Raspberry Pi > I first discovered the issue on since I am apt to have the radio > connected to either system and, if this problem is fixable, this > solution is preferable because the radio defaults to using the > usbC port as the serial port so it should still work if a full > reset is ever needed and the mechanism for usb should naturally > accept as many different devices as practical because you never > know what you will need to connect until you try it and it fails. > > As an amusing aside, the radio has a usb mode, but > that's totally unrelated because in that case, USB stands for > upper side band and is a very energy-efficient method of radio > communication because it is only a spectrum of frequencies > consisting of the sidebands of an audio signal without the > carrier. It can be LSB or lower side band or USB for upper side > band. Nothing like a few new acronyms for your day. I guess that's > TMI. You forgot to mention it can get the message thru better because it has a 12 db advantage over competing noise compared to the original AM, sometimes called Ancient Mary in our circles. > Martin McCormick WB5AGZ Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
What do we have that will save a manpage as we see it on-screen
Greetings all; With the man markup subtracted, so what we save is exactly what we see. Thanks. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 12:34:16 Larry Martell wrote: man -t /path/to/man/file >file.txt groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with lots more markup. Not what I want obviously. Thanks Larry. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote: > On 10/1/21, Gene Heskett wrote: > > Greetings all; > > > > With the man markup subtracted, so what we save is exactly what we > > see. > > > > Thanks. > > > > Cheers, Gene Heskett. > > Hi, Gene. I'm not sure if I'm understanding correctly, but.. I do this > (am using the LILO package as an example): > > man lilo > manLILO > > I just tested it to make sure first. Mine here looks exactly like the > terminal version when that manLILO file is viewed in Mousepad (XFE4's > text editor). That still prints all the useful "SEE ALSO", last date > edited, and e.g. "LILO(8) leads that appear at the bottom, too. > > Others here sometimes do something a little fancier than only that ">" > (greater than sign), but I can't remember what it is nor if it applies > to something as straight forward as this one. > > Cindy :) did exactly what I wanted it to do. Thank you Cindy. ;o) Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 13:58:20 Lee wrote: > On 10/1/21, Gene Heskett wrote: > > Greetings all; > > > > With the man markup subtracted, so what we save is exactly what we > > see. > > Try the "--ascii" option - eg > man --ascii man > /tmp/man.txt > > Regards, > Lee Cindy's suggestion worked. Thanks Lee. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 15:47:18 Greg Wooledge wrote: > On Fri, Oct 01, 2021 at 12:24:50PM -0400, Gene Heskett wrote: > > With the man markup subtracted, so what we save is exactly what we > > see. > > If you want to reproduce what you see when you type "man bash" (just > as an example), you would need to *retain* the "man markup", not > subtract it. So, right off the bat, the question is confusing me. > > What is it you're actually trying to do here? Do you want to store > Debian's man pages in files, move them to another platform (say, > Microsoft Windows) and view them there? > > If you're not moving the files across systems, then I don't see the > point. If you want to see the same result again, just run "man bash" > again. Yes? The man page isn't going anywhere. > I'm tryting to configure the .hal file in linuxcnc, so loading the uncompressed file into geany and printing it, prints all the markup too, and any of that in a .hal file is a showstopper syntax error. I need to type it into the .hal file exactly as I see it onscreen. I thought I was doing that, Greg, when I said I wanted a file identical to what I see on screen when man has processed the manfile to show the onscrren text. Processing removes around 600 bytes. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 17:01:56 Greg Wooledge wrote: > On Fri, Oct 01, 2021 at 04:59:25PM -0400, Gene Heskett wrote: > > On Friday 01 October 2021 12:34:16 Larry Martell wrote: > > > > man -t /path/to/man/file >file.txt > > groff -mandoc /path/to/man/file > file.txt, both quadrupled the size > > with lots more markup. > > > > Not what I want obviously. > > There is nothing obvious here. What do you want? Why? What are you > going to do with the resulting file(s)? What I wanted on dead tree, was exactly what I see on screen. With the manpage markup gobbled up, leaving only the text I see on screen when I type man 9 filename. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 17:17:53 Greg Wooledge wrote: > On Fri, Oct 01, 2021 at 05:05:44PM -0400, Gene Heskett wrote: > > On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote: > > > man lilo > manLILO > > > > did exactly what I wanted it to do. Thank you Cindy. ;o) > > On Fri, Oct 01, 2021 at 05:07:37PM -0400, Gene Heskett wrote: > > On Friday 01 October 2021 13:58:20 Lee wrote: > > > man --ascii man > /tmp/man.txt > > > > Cindy's suggestion worked. Thanks Lee. > > *sigh* > > Do you know how frustrating this is? > > "Hey guys, I want a thing. I won't give any useful details, though. > Just make this thing for me. I want you all to guess what I want, and > I'll look through the answers, and pick the one I like the most. > You're all going to be my personal army of monkeys typing on the > keyboards. One of you will produce Shakespeare for me." > > > Even now, after you've declared a winner, we can still only *guess* > what the contest rules were. > > And the decision is nonsensical, because you've declared one winner > (Cindy) when the second-place runner up (Lee) gave a command that > gives *exactly* the same result as Cindy's command. > > unicorn:~$ man ls > manls > unicorn:~$ man --ascii ls > manls2 > unicorn:~$ ls -l manls manls2 > -rw-r--r-- 1 greg greg 8299 Oct 1 17:09 manls > -rw-r--r-- 1 greg greg 8299 Oct 1 17:10 manls2 > unicorn:~$ cmp manls manls2 > unicorn:~$ > > > We still don't know why you want this. I guess we'll never know. We apparently don't speak the same dialect of english Greg. I wanted a dead tree (aka paper) copy of a manpage, with ALL the markup totally stripped. As for Lee's suggestion, I didn't try it since Cindy's example worked perfectly and by the time I read Lee's msg, I had what I needed on the output tray of my huge printer. No reflection on Lee was intended. Still isn't. Thanks Greg. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 20:44:41 Fred wrote: > On 10/1/21 1:59 PM, Gene Heskett wrote: > > On Friday 01 October 2021 12:34:16 Larry Martell wrote: > > > > man -t /path/to/man/file >file.txt > > groff -mandoc /path/to/man/file > file.txt, both quadrupled the size > > with lots more markup. > > > > Not what I want obviously. > > > > Thanks Larry. > > > > Cheers, Gene Heskett. > > man command | col -b > command.txt > > Best regards, > Fred works fine, thanks. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 20:53:26 Greg Wooledge wrote: > On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote: > > man command | col -b > command.txt > > Curious. > > unicorn:~$ man ls > ls1 > unicorn:~$ man ls | col -b > ls2 > unicorn:~$ ls -l ls1 ls2 > -rw-r--r-- 1 greg greg 8299 Oct 1 20:49 ls1 > -rw-r--r-- 1 greg greg 7745 Oct 1 20:49 ls2 > > Glancing at the diff -u between the two files, most of the changes > appear to be whitespace related. > > Opening them both in vim, the second one has a bunch of literal tab > characters, whereas the first one has no tabs at all -- only spaces. > > So I guess most (or all?) of the size reduction is groups of spaces > being replaced by tabs. The manpage is jogaxisget.9. and they look very close to identical, but an ls -l shows: -rw-r--r-- 1 pi pi1321 Oct 2 05:38 jogaxisget.text -rw-r--r-- 1 pi pi1580 Oct 1 17:00 jogaxisget.txt either one will do. even for copy/paste as hal treats tabs the same as spaces and reads of past looking for the text. Thank you everybody, problem solved. Now to figure out what to hook it up to in a 700+ l.o.c. file containing at least 5000 signal names. TL;DR unless interested in cnc machinery The hookup syntax is : net netname output-1 [output-2] etc etc and there is not an example line to show how its hooked up to achieve the desired logic outputs in the manpage. Only the invocation lines are given. This is what I wanted: JOGAXISGET(9) HAL Component JOGAXISGET(9) NAME jogaxisget - determines which axis jogging SYNOPSIS loadrt jogaxisget [count=N|names=name1[,name2...]] FUNCTIONS jogaxisget.N (requires a floating-point thread) PINS jogaxisget.N.Xin0 bit in axis.x.kb-jog-active <-- (edited in) example signal name jogaxisget.N.Xin1 bit in jogaxisget.N.Yin0 bit in axis.y.kb-jog-active jogaxisget.N.Yin1 bit in jogaxisget.N.Zin0 bit in axis.z.kb-jog-active jogaxisget.N.Zin1 bit in jogaxisget.N.Ain0 bit in axis.a.kb-jog-active jogaxisget.N.Ain1 bit in jogaxisget.N.Xtrigger bit out jogaxisget.N.Ytrigger bit out jogaxisget.N.Ztrigger bit out jogaxisget.N.Atrigger bit out jogaxisget.N.activeX bit out jogaxisget.N.activeY bit out jogaxisget.N.activeZ bit out jogaxisget.N.activeA bit out jogaxisget.N.Xverify bit in (default: FALSE) axisui.Xisactive jogaxisget.N.Yverify bit in (default: FALSE) axisui.Yisactive jogaxisget.N.Zverify bit in (default: FALSE) axisui.Zisactive jogaxisget.N.Averify bit in (default: FALSE) axisui.Aisactive LICENSE GPL LinuxCNC Documentation 2021-09-30 JOGAXISGET(9) The idea is to keep a gui's radio buttons up to date with what the machine is doing, when signals external to the gui ae used to move the machine, in this case a pair of encoder dials that function like the hand cranks on a manual machine when it has been converted to cnc control. With a per click distance ranging from .0001 inches to 20 thousanths per click. All this extra is unique to my machine, I wrote it. The dials I have added are very handy when one is finding the positions to start a machining operation from, but at present, applying a touch-off to establish that point does not update the gui's radio buttons, so you find a point, and blindly apply the touch-off, only to discover the touch-off has been applied to the wrong axis because the radio buttons have not been updated by moving the machine with the dials. This logic module is designed to act the same as a keyboard jog, which does update the gui's radio buttons. But its up to me to find the right signals to tie together to adhieve that, as they are mutually exclusive, only one can be TRUE at a time, the most recent. For a lathe, which only has 2 axis's only X and Z pins will be used, but for a mill at least 3 need to be "hooked" up. But both of my mills have 4 asises, and could have as many as 9. And since this module was written the "axis" and "joints" have been divorced for increased versatility, so the the subnames on the 2nd line are now duff and the new names will have to be found by experimentation. And I'm the first to use this module, so I get to write the translation rules. Since N=69! is the largest that a ti calculator can handle, fun it won't be, cuz N is well north of 1000 in this case. Cheers, Gene Heskett. -- "There are four boxes to be used in defense
Re: What do we have that will save a manpage as we see it on-screen
On Friday 01 October 2021 22:52:59 David Wright wrote: > On Fri 01 Oct 2021 at 20:53:26 (-0400), Greg Wooledge wrote: > > On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote: > > > man command | col -b > command.txt > > > > Curious. > > > > unicorn:~$ man ls > ls1 > > unicorn:~$ man ls | col -b > ls2 > > unicorn:~$ ls -l ls1 ls2 > > -rw-r--r-- 1 greg greg 8299 Oct 1 20:49 ls1 > > -rw-r--r-- 1 greg greg 7745 Oct 1 20:49 ls2 > > > > Glancing at the diff -u between the two files, most of the changes > > appear to be whitespace related. > > > > Opening them both in vim, the second one has a bunch of literal tab > > characters, whereas the first one has no tabs at all -- only spaces. > > > > So I guess most (or all?) of the size reduction is groups of spaces > > being replaced by tabs. > > Yes, diff -ubw will confirm that whitespace is the only difference. > I'm too lazy to check that the /apparently/ significant differences > shown by diff and diff -u are merely caused by the left-margin offset, > which makes TABs skip to different columns from those intended. > > Like others, I tried to guess what Gene really wanted (I can barely > believe the answer) and to come up with a suitable method. I also > tried out others' suggestions. We don't know what the mysterious > man 9 actually is (unless there's a well-known command named "9"), > so I used man man and man bash¹. There is a well known man 9 command, it means to save man the trouble of searching the whole database, as there might be duplicate names to confuse the issue, but it this case look in man/man9 for the requested manpage. Sheesh, doesn't anyone read manpages anymore? :o) [...] Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Saturday 02 October 2021 07:45:07 Eric S Fraga wrote: > man pages are written in troff/nroff (which can be compiled using > groff) using the man style. You can do the following, for instance: > > gunzip -c /usr/share/man/man1/chmod.1.gz | groff -man | lp > > (or replace "lp" with "gv -" to see on screen). > > Replace chmod with specific command and note that there is a different > folder for each section of the Unix manual, man1 being for commands, > man2 for system libraries, ... > > troff is how us old-timers used to write before LaTeX took over. I > did my PhD in troff many moon ago on BSD Unix and then SunOS. > Testament to the quality of the software: I can still generate a PDF > of my thesis now after more than 30 years since I wrote it. Try that > in Word... ;-) And in 3 decades, word will have destroyed it 30 times (or more) :( Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Saturday 02 October 2021 11:13:09 Brian wrote: > On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote: > > On Friday 01 October 2021 17:17:53 Greg Wooledge wrote: > > [...] > > > > We still don't know why you want this. I guess we'll never know. > > > > We apparently don't speak the same dialect of english Greg. I wanted > > a dead tree (aka paper) copy of a manpage, with ALL the markup > > totally stripped. As for Lee's suggestion, I didn't try it since > > Cindy's example worked perfectly and by the time I read Lee's msg, I > > had what I needed on the output tray of my huge printer. No > > reflection on Lee was intended. Still isn't. > > Nitpicking time :). True. TBT, the use of bold was not something these old eyes considered. > You specified "...so what we save is exactly what > we see." Neither Cindy Sue Cause's mor Lee's give *exactly* what is > seen onscreen. If bolded headings are unwanted, either method gives a > nice text file to print. Yes, I should have more precisely stated "text". :( Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: What do we have that will save a manpage as we see it on-screen
On Saturday 02 October 2021 16:02:52 Brian wrote: > On Sat 02 Oct 2021 at 15:43:33 -0400, Gene Heskett wrote: > > On Saturday 02 October 2021 11:13:09 Brian wrote: > > > On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote: > > > > On Friday 01 October 2021 17:17:53 Greg Wooledge wrote: > > > > > > [...] > > > > > > > > We still don't know why you want this. I guess we'll never > > > > > know. > > > > > > > > We apparently don't speak the same dialect of english Greg. I > > > > wanted a dead tree (aka paper) copy of a manpage, with ALL the > > > > markup totally stripped. As for Lee's suggestion, I didn't try > > > > it since Cindy's example worked perfectly and by the time I read > > > > Lee's msg, I had what I needed on the output tray of my huge > > > > printer. No reflection on Lee was intended. Still isn't. > > > > > > Nitpicking time :). > > > > True. TBT, the use of bold was not something these old eyes > > considered. > > > > > You specified "...so what we save is exactly what > > > we see." Neither Cindy Sue Cause's mor Lee's give *exactly* what > > > is seen onscreen. If bolded headings are unwanted, either method > > > gives a nice text file to print. > > > > Yes, I should have more precisely stated "text". :( > > A very reasonable respose. Your eyes may be deteriorating but there is > nothing amaiss with your intellect. Thats holding up fairly well, tested at 147 in the 7nth grade, made my living in electroncs since I quit school in the 9th grade and went to work fixing what was then a new toy called a tv, and finished off my working years as the chief engineer and the often only tech at a local tv station for 18+ years. Been retired for 19 years with enough to support my hobbies. That pulmonary embolism did cost me a few points though. That eyesight loss unfortunately is slowly happening despite the daily intake of a 40 milligram dose of lutien daily for the last 35 or so years, trying to stave off going blind because I was declared diabetic type 2 about that many years ago. Macular degeneration, where I have dark spots dead center in the dark of the moon are beginning to be noticeable. OTOH, I'll be 87 Monday, so I don't imagine it would be good to complain too loudly. I guess I'm a survivor, or he isn't ready for me yet, I have surived a pulmonary embolism that kills >98% 8 years ago, my heart has had a couple attacks, a replacement valve, some stents and a pacemaker that keeps it running at about 30% effficiency, so I tire more easily than 40 years ago. But other than the aches & pains that seem to go with the years, I actually feel pretty good yet. Currently digging out a bush that found some growth hormones in the back yard, it was 20 feet across and nearly 20 feet high when I first decided it had to go as it was damaging the house, but I'll have to get a backhoe in to finish that, and replacing about 170 feet of split rail fencing around the lower third of my place with vinyl cuz I'm tired of replaceing the split rail every 10 years and its due again. Posts rotting off at ground level. Rails breaking of their own weight etc. The vinyl should outlast me. Got around 50 feet to go. Anybody wanna help? I pay well, in cash. Take care now Brian, and the rest of you who helped. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Then it happened to me...
On Sunday 10 October 2021 06:36:32 Reco wrote: > On Sun, Oct 10, 2021 at 08:33:03AM +0100, piorunz wrote: > > On 08/10/2021 18:10, Dan Ritter wrote: > > > I've just set postfix to drop anything from that host at SMTP > > > time, but I doubt it's going to work. I think they've found a > > > cannon to annoy debian-user subscribers with. > > > > Why we don't have this? > > https://forum.manjaro.org/ > > Maybe because there's [1]. There should be also IRC at libera.chat, > and that strange gizmo at [2]. > [1] is also superior to Discourse that Manjaro is using as [1] can be > viewed without enabled Javascript. > > You're free to convince list denizens to move elsewhere, there were > such efforts in the past. Where're still here btw. > > > We still use e-mail list, prone to spam, and abuse > > Once one uses own MTA, such issues are dealt quickly, simply, and most > importantly - permanently. > Consider it a hint. GMX is good, but not that good. > > > technology from 30 years ago? > > In other news, people are still using a wheel which was invented about > 6000 years ago (4500 BC if Wikipedia is to be believed). Some things > just get better with age. > And nothing beats federated communication system which works. There's > no reasonable alternative to SMTP yet. > > > Isn't it time to switch to online forums? > > Different way of communicating attracts different communities. I'm > sure there's lively one at [1]. > > > It's not that Debian haven't got the money, right? > > Where I'm living counting others' money is considered rude at best. > But I know a way - join Debian project, become Debian Developer, and > raise a General Resolution about Discourse. > > Reco > > [1] https://forums.debian.net/ I have to hit ctl+ quite a few times to get it readable. Then the python 3 questions were all too obvious. > [2] https://discourse.debian.org/ This does not resolve. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Mouse left button acts really strange
On Sunday 10 October 2021 09:52:40 Jeremy Nicoll wrote: > On Sat, 9 Oct 2021, at 19:52, sp...@caiway.net wrote: > > I really like Logitech mouses (fast scrolling!), but when used often > > they break each one/two year. > > I use my mice almost always in bed, with the mouse either on top > of the duvet or running around under it on the sheet. (The laptop > is on an overbed table.) > > What kills them most often is me forgetting where they are and > getting out of bed causing the mouse to fly off the bed where it > often collides with a bookcase (or worse) the metal frame of the > overbed table. > > The poor mice expire traumatically, not even managing to call for > help. No SQUEAK! Just a thud. The most common failure is the solder joints on the bottom of the boards under the swithes. That wave soldering process demands that the switches be held solidly to the board, not floating 1 to 10 thou up it the air. The solder is many times heavier than the switch so if not solidly held down while the solder wave goes by, they will float just a hair, leaving an air gap between the board and the bottom of the switch. This air gap is closed by the finger pressing the button, which gradually loosens the grip of the glue holding the copper to the bottom of the board and eventually cracking the solder joint, leading to a quick double click effect from the switch closing in response to the finger, then a break as the crack opens, followed by a second click as the finger lifts again and the crack closes, then the switch opens again, giving a double click where the finger made but one push. Those of us that have a hot soldering iron grafted to a hand can fix that, but we're often considered rare birds to be avoided by the girls lest the geekiness is catching. Some of us are even CET's, but that card, laid on the HR desk has gotten me every job I ever wanted, some quite lucrative. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
A .profile puzzle
Greetings all; The local electrical system, while better than Haiti's is getting to be a nuisance with 5 second power failures about weekly, or is that weakly? Most of my machines are running a 64 bit buster with a preempt-rt kernel. I made some mods to a 3d printer project in openscad last week, printed it, but forgot to save it. So I lost it when the latest failure rebooted that machine. A procedure I had long since committed to muscle memory now requires I be root to do what I've been doing as me for the last year, so I have now reprinted that after reinventing it, 4 times, w/o changing the printout, after the latest failure I have to be root to mount the card from the printer, I have to be root to overwrite the resliced file to the printers SD card, root to do it all. But mc now goes thru the motions as me, without telling me it doesn't have permission to overwrite that file. What the heck? 2 things really. 1. Before the latest failure I could do all this as me because the mount point for the card is in my home directory, I own it all. And didn't have to be root to do any of it. This was not fixed by a 2nd reboot. 2. and another pesky thing is starting a konsole to do work, needs a $PATH modification that we used to put in ~.profile. But opening a terminal hasn't called a ". .profile" since about jessie. So thats another PITA. So, what has replaced .profile as the function for such as that in recent releases? Thank you. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Sunday 17 October 2021 12:35:01 deloptes wrote: > Gene Heskett wrote: > > 1. Before the latest failure I could do all this as me because the > > mount point for the card is in my home directory, I own it all. And > > didn't have to be root to do any of it. This was not fixed by a 2nd > > reboot. > > I guess this problem is not related to the .profile issue you are > having below. Agreed. > Check the permissions on the mount point done, I still own it. > and the fstab its not in fstab, never was. I touched a file in home/gene/Downloads/3dp.stf named sdb1 to create a mount I didn't have to search thru /media to access. Up until this 5 second power failure, I could, as me, mount that SD card there, and use mc, as me, to overwrite a file on that card, then sync; eject sdb1. Led on card adapter goes out, pull the card, take it back to the printer and select and print the updated file. Now I have to be root to do any of it except the printer. The card is vfat, which has no concept of file ownership. > and also your > group membership. gene@dddprint:~/AppImages$ cat /etc/group|grep gene dialout:x:20:gene cdrom:x:24:gene sudo:x:27:gene audio:x:29:pulse,gene video:x:44:gene gene:x:1000: Nothing changed there in months. > The SD card might also need a fsck. by whose fsck? > > 2. and another pesky thing is starting a konsole to do work, needs a > > $PATH modification that we used to put in ~.profile. But opening a > > terminal hasn't called a ". .profile" since about jessie. So thats > > another PITA. > > > > So, what has replaced .profile as the function for such as that in > > recent releases? > > AFAIK bash is not reading profile when you login, but not sure - it > could be also that it is not a login shell. XFCe login, I think. I only see it once on that machine. logging in remotely with "ssh -Y machine-name" or 'user1000'@machine-name is how I generally run things from a comfy chair. > AFAIK you should open the terminal with "bash --login" to read the > profile. So try in the terminal "bash --login" Done, but no change in the $PATH. But it did take two ctl-d's to exit it. > I have put in my .profile > > alias bash='bash --login' > > long time ago Thank you deloptes. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Sunday 17 October 2021 12:39:50 Dan Ritter wrote: > Gene Heskett wrote: > > The local electrical system, while better than Haiti's is getting to > > be a nuisance with 5 second power failures about weekly, or is that > > weakly? > > That's a great case for a UPS... > Yup, but thats 4 more of them. Is anybody hving a real sale? > > 1. Before the latest failure I could do all this as me because the > > mount point for the card is in my home directory, I own it all. And > > didn't have to be root to do any of it. This was not fixed by a 2nd > > reboot. > > Are you mounting via /etc/fstab? If so, show us the line. nope, command line, as me, until this reboot. > > 2. and another pesky thing is starting a konsole to do work, needs a > > $PATH modification that we used to put in ~.profile. But opening a > > terminal hasn't called a ". .profile" since about jessie. So thats > > another PITA. > > > > So, what has replaced .profile as the function for such as that in > > recent releases? > > I'm guessing that your shell is /bin/sh. That used to be bash, > but now it's dash. I can't find an About for that one, its whatever xfce uses. > You could make your own shell bash -- just run chsh and log out, > then come back in again. > > Note that .profile is supposed to be read only by a login > shell, whereas .bashrc will be read by every interactive shell. > Here's the chunk of man bash: > >When bash is invoked as an interactive login shell, or as a > non-interactive shell with the --login option, it first reads and > executes commands from the file /etc/profile, if that file exists. > After reading that file, it looks for ~/.bash_profile, ~/.bash_login, > and ~/.profile, in that or der, and reads and executes commands from > the first one that exists and is readable. The --noprofile option may > be used when the shell is started to inhibit this behavior. I have tried putting that path stuff in .bashrc, but that fails too. > When an interactive login shell exits, or a non-interactive > login shell executes the exit builtin command, bash reads and > executes commands from the file ~/.bash_logout, if it exists. > > When an interactive shell that is not a login shell is > started, bash reads and executes commands from /etc/bash.bashrc and > ~/.bashrc, if these files exist. This may be inhibited by using the > --norc option. The --rcfile file option will force bash to read and > execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. > > When bash is started non-interactively, to run a shell script, > for example, it looks for the variable BASH_ENV in the environment, > expands its value if it appears there, and uses the expanded value > as the name of a file to read and execute. Bash behaves as if the > following command were executed: if [ -n "$BASH_ENV" ]; then . > "$BASH_ENV"; fi but the value of the PATH variable is not used to > search for the filename. > > > -dsr- Thanks Dan. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
your > environment in this file. > > .xsessionrc is unique to Debian. It's not found on other Linux > variants. Some other Linuxes introduce .xprofile or other > files. > >And then there's GNOME. Because obviously GNOME has to be unique > and have its own separate session type, and its own way of doing > everything, none of the answers above applies to GNOME. Except maybe > the .xsessionrc file. I think Debian still arranges for GNOME > sessions to dot that in. Maybe. Don't quote me on it. > >(But don't think that your job is done if you manage to export >environment variables from .xsessionrc. Oh no. GNOME is *so* much >worse than that. It's so bad that I won't even try to describe >it here. It needs a whole thread of its own. We've had several >over the years.) > > 4) And finally there's Wayland. I don't know what the hell Wayland > does. Nobody who uses it has ever told us how it works. You won't > find any useful information about it on the Debian wiki, etc. > > See also: > > https://wiki.debian.org/Xsession > https://wiki.debian.org/EnvironmentVariables Is it beer-thirty yet? Tis here. Except its a stretch to call the stuff this diabetic drinks beer. ;o) Some won't even call my coffee coffee. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Sunday 17 October 2021 15:45:36 songbird wrote: > Gene Heskett wrote: > > On Sunday 17 October 2021 12:39:50 Dan Ritter wrote: > >> Gene Heskett wrote: > >> > The local electrical system, while better than Haiti's is getting > >> > to be a nuisance with 5 second power failures about weekly, or is > >> > that weakly? > >> > >> That's a great case for a UPS... > > > > Yup, but thats 4 more of them. Is anybody hving a real sale? > > no, you buy one for the whole place and put it on tha main > panel. Thanks for the idea, but I have not seen one big enough to handle this place for the 6 or 7 seconds it takes for the 20kw generac to start. My now departed wife had COPD and needed non-stop oxygen toward the end, so I installed the generac about 8 or 9 years ago. It would take a 1500WA to handle the 2 machines in the garage plus a 1000WA in the shop building, and another 1000WA for the machine driving my 3d printers. They only make them whole house sized on bids, bring money in wheelborrows. I do reserve the right to bitch about the lack of timely maintenance as I will have to put up with this BS for a year before they'll replace the contacts in the substations voltage regulator. BTDT, several times in the 31+ years I've been here. So you could say I've been to this particular rodeo before. > i only have a small one here for my PC and a light, but it > has paid for itself many times over already in not having > random power outages take me down and mess things up. normally > when a storm comes through i turn off the PC anyways because > i really don't want to have things fried (even if i do have > the UPS and surge protection). i can do something else for > a while. > > if i were running large expensive equipment i'd surely have > some UPS and surge protection for those. if only just enough > to get them to shut down without destroying the work in > progress (or themselves). > > > songbird Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Sunday 17 October 2021 21:15:21 Douglas McGarrett wrote: > On 10/17/21 8:38 PM, David Christensen wrote: > > On 10/17/21 2:12 PM, Stefan Monnier wrote: > >>> normally when a storm comes through i turn off the PC anyways > >>> because I really don't want to have things fried (even if i do > >>> have the UPS and surge protection). > >> > >> Hmmm does turning them off make any difference w.r.t a surge large > >> enough to pass through the surge suppression? > >> > >> I thought the only effective way to make a difference is to > >> *unplug* them. > > > > +1 if you service is overhead and your concern is lightning strikes. > > > > > > David > > You should unplug the charger to the laptop from the AC line AND > from the laptop, and don't forget to disconnect the LAN if it is > wired. However, you can't disconnect everything in the computer area > or you'll go crazy! It would be a good idea to disconnect the router > from the modem and from power. I got a bad hit from lightning in July, > and it did take out the router and a desktop and a laptop, and damaged > a printer, not to mention other devices around the house--like the TV, > ferinstance! > --doug Your service is probably both old and not up to code, probably grandfathered in if it was built before the NEC became the law here in the states. I brought mine up to code in 2008, as I installed a 200 amp service myself and have not lost ANYTHING but a wired keyboard since. The strike caused me to get a shock spark similar to a door knob, jolted me and killed the keyboard. I now use wireless keyboards for the extra air gap, and its all powered up 24/7/365.25. 6 of them in various locations. The idea between the NEC and various other regulations is that if the line gets hit, it should all bounce in unison so the voltage on every connected wire goes up and down in unison, so the connected stuff still see's only the 5, 12, or 24 volts that runs it. It all may be 250k volts away from ground for a few microsecnds. A dirt ground, other than whats legally connected at the meterhead, is a ground loop that upsets this balanced condition and will eat your lunch. This includes the old time practice of grounding a clothes washer to the copper cold water pipe. That is the case in this house, but that copper never touches dirt, its plastic before it leaves the house. All the network is wired from a cable modem which has lightning arrestors before the cable gets into the house. So I'm a big target, I should lose stuff, but I haven't. Who am I? For starters, I am a Certified Electroncs Technician, registered in Nebraska as NB-118. One who spent the last 18 years of his working life as the Chief Operator of a middle market television station, much of the time by myself. Now I'm your classic old fart of 87, and getting slowly rusty but I still know a few things about electricity. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> * Gene Heskett [21-10/17=Su 12:18 -0400]:
> > [...] opening a terminal hasn't called
> > a ". .profile" since about jessie [...]
>
> Check whether you *also* have either .bash_profile or
> .bash_login, because either of those supersedes .profile:
>
> ls -lA ~/.bash_{profile,login}
Neither present, just .bashrc, and .bash_logout
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Monday 18 October 2021 07:17:05 Greg Wooledge wrote:
> On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> > On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> > > * Gene Heskett [21-10/17=Su 12:18 -0400]:
> > > > [...] opening a terminal hasn't called
> > > > a ". .profile" since about jessie [...]
> > >
> > > Check whether you *also* have either .bash_profile or
> > > .bash_login, because either of those supersedes .profile:
> > >
> > > ls -lA ~/.bash_{profile,login}
> >
> > Neither present, just .bashrc, and .bash_logout
>
> That's as expected, then. Your .profile is not being read *now*
> because it's not supposed to be, if you use a Display Manager to
> login.
>
> Your .profile *used* to be read by terminals, because previously, your
> terminals had been configured to run login shells. However, I'd bet
> it was *not* read by your session, meaning any changes to the
> environment would not be seen by graphical applications that you
> launched directly from your Desktop or your WM, without going through
> a terminal.
>
> Assuming you run a Debian X11 Session via a Display Manager, and also
> assuming you don't have a .xsession file, you probably want to
> configure your environment in ~/.xsessionrc (note the "rc" on the
> end).
That does not exist on that machine. I'll look into it a bit later,
thanks Greg.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Sata Hard drive testing
00 ff ff ff 0f Error: UNC at LBA = 0x0fff = 268435455 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- > 60 00 08 ff ff ff 4f 00 15d+00:06:45.692 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:45.683 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:45.656 READ NATIVE MAX ADDRESS > EXT [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:45.654 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:45.641 SET FEATURES [Set > transfer mode] > > Error 1330 occurred at disk power-on lifetime: 10525 hours (438 days + > 13 hours) > When the command that caused the error occurred, the device was > active or idle. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fff = 268435455 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- > 60 00 08 ff ff ff 4f 00 15d+00:06:45.526 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:45.517 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:45.491 READ NATIVE MAX ADDRESS > EXT [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:45.488 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:45.475 SET FEATURES [Set > transfer mode] > > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining > LifeTime(hours) LBA_of_first_error > # 1 Extended offline Completed without error 00% > 14551 - # 2 Extended offline Completed without error > 00% 14530 - # 3 Conveyance offline Completed without > error 00% 10165 - # 4 Conveyance offline Completed > without error 00% 10165 - # 5 Short offline > Completed without error 00% 10163 - # 6 Extended > offline Completed without error 00% 9997 - # 7 Short > offline Completed without error 00% 0 - > > SMART Selective self-test log data structure revision number 1 > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS > 1 0 0 Not_testing > 2 0 0 Not_testing > 3 0 0 Not_testing > 4 0 0 Not_testing > 5 0 0 Not_testing > Selective self-test flags (0x0): > After scanning selected spans, do NOT read-scan remainder of disk. > If Selective self-test is pending on power-up, resume after 0 minute > delay. What color is the sata data cable? if "hot red" aka magenta, bump it with a pencil and note if the syslog log blows up with reset errors. If it does, replace the data cable with any other color but that hot red. That particular plastic dye leads to cable failures and has been a known part of the electronics jungle since the 1970's. > > On 10/18/21 6:52 PM, Reco wrote: > > Hi. > > > > On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote: > >> I have been having problems with a drive (non-SSD) for a while now, > >> but I would like to "identify" the problem specifically, so that I > >> may perhaps be able to get the drive replaced. > > > > Assuming it's SATA/IDE drive, all you need to do is: > > > > apt install smartmontools > > smartctl -t long > > # wait for the test to finish > > smartctl -a > > > > Please post the output of the last command. > > > > Reco Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Sata Hard drive testing
On Thursday 21 October 2021 08:13:26 Dan Ritter wrote: > > === START OF INFORMATION SECTION === > > Device Model: ST8000DM004-2CX188 > > You should be able to return this drive without proving that it > is defective; this is one of Seagates' SMR drives that they did > not disclose were SMR. > > -dsr- And what does this SMR acronym mean, Dan? Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Sata Hard drive testing
On Thursday 21 October 2021 09:02:01 David wrote: > On Thu, 21 Oct 2021 at 23:53, Gene Heskett wrote: > > And what does this SMR acronym mean, Dan? > > Questions like this can be answered with an > internet search engine. Search for "Seagate SMR". > For fun you can add search terms like > "controversy guilty dreaded bad press" etc. Very Interesting and most informative Dan, and thank you. Carefully reading between the lines of several hits also explains why I stopped having major failures of amanda, the backup software, when I replaced a 1Tbyte seagate with a 240 gig series 860 samsung SSD, used as a holding disk while amanda is collecting its data to be written to tape w/o shoeshining the tape while at the same time cutting the time to do a 20 gig backup from 3 or 4 hours, to 20 minutes. This post is also being sent to the amanda-users list to alert the users who are currently being affected by this and not finding a definitive answer. Bottom line for amanda users is, do not use todays spinniing rust drives as holding disks. They are simply not trustworthy for short term buffer storage. Symptoms are reported to the user as crc errors in the holding disk. That particular DiskList Entry is then repeated until a good crc is obtained. But that also leaves the bad crc data left on the holding disk eventually using up its capacity without manual intervention to clean up the mess. A genuine PITA for us, and leaves the drive makers in an unfavorable, bad dog, no biscuit light. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
drawing smith charts
Greetings; One of the things I occasionally do is service my local AM radio station when its off the air. This includes trying to keep the VSWR under control. I have a redpitaya Vector Network Analyser that I use to tune the tower, and it gives me the tuning state in the form of a smith chart. But while it claims to run with a linux system as the display, it doesn't, so I had to buy a cheap all-in-one with win 10 home edition on it. Works great but is a pita to setup and get started. The windows driver is also about 50x the size of the linux driver that doesn't work. What can I install to a buster machine that might make this graphical display work? We had, a decade back, a something or other "plot" that might have been able to draw a smith chart but I haven't seen it in the repos recently. It also was a square plotter, whereas the smith chart is circular at its maximum error limits. Can anyone suggest a linux substitute? Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: drawing smith charts
On Saturday 23 October 2021 05:58:12 didier gaumet wrote: > Le samedi 23 octobre 2021 à 04:58 -0400, Gene Heskett a écrit : > > Greetings; > > > > One of the things I occasionally do is service my local AM radio > > station > > when its off the air. This includes trying to keep the VSWR under > > control. > > > > I have a redpitaya Vector Network Analyser that I use to tune the > > tower, > > and it gives me the tuning state in the form of a smith chart. But > > while > > it claims to run with a linux system as the display, it doesn't, so > > I had to buy a cheap all-in-one with win 10 home edition on it. > > Works great but is a pita to setup and get started. The windows > > driver is also > > about 50x the size of the linux driver that doesn't work. > > > > What can I install to a buster machine that might make this > > graphical display work? We had, a decade back, a something or other > > "plot" that > > might have been able to draw a smith chart but I haven't seen it in > > the > > repos recently. It also was a square plotter, whereas the smith > > chart is > > circular at its maximum error limits. > > > > Can anyone suggest a linux substitute? > > > > Cheers, Gene Heskett. > > Hello, > > I do not know nothing about radio setup, your hardware and this brand, > so I am afraid I can not help you much. > > But the manufacturer claims it works under Linux and provides > instructions to get it running: > https://redpitaya.readthedocs.io/en/latest/appsFeatures/applications/v >na/appVNA.html#linux-users-only Albeit there is an error in the link to > download the "control program" which points to the Windows client > instead of the Linux one. > The correct link > is:https://downloads.redpitaya.com/downloads/Clients/vna/vna-linux-too >l.zip Thank you very very much Didier. In my conversations with the maker in cz land I was never able to acquire that link from them. Every link they gave me pointed at the winblows version. Now to see if I can make it run on a pi4b. Or something similar that looks like a lappy but with a screen big enough to read. Attempting to run it on a pi4b running raspbian buster, which is normally running a cnc'd 11x54 lathe, with a preempt-rt kernel, it takes about 30 seconds to get to line 32 and a failure. line 32 tells it: from mpldatacursor import datacursor but it can't find mpldatacursor. found some mpl suspects, installing them on that pi now. Then runniing sudo updatedb, then try python3 ./vna.py again. And it still bails out, same error:(paste) pi@rpi4:/media/pi/workspace/vna-linux-tool $ python3 ./vna.py Traceback (most recent call last): File "./vna.py", line 32, in from mpldatacursor import datacursor ModuleNotFoundError: No module named 'mpldatacursor' And according to synaptic, there isn't such a critter. Any suggestions? I'll ask on the python list. Maybe someone there knows. Thank you Didier. that link is much appreciated. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: drawing smith charts
On Saturday 23 October 2021 06:06:12 Andrew M.A. Cater wrote: > On Sat, Oct 23, 2021 at 04:58:30AM -0400, Gene Heskett wrote: > > Greetings; > > > > One of the things I occasionally do is service my local AM radio > > station when its off the air. This includes trying to keep the VSWR > > under control. > > > > I have a redpitaya Vector Network Analyser that I use to tune the > > tower, and it gives me the tuning state in the form of a smith > > chart. But while it claims to run with a linux system as the > > display, it doesn't, so I had to buy a cheap all-in-one with win 10 > > home edition on it. Works great but is a pita to setup and get > > started. The windows driver is also about 50x the size of the linux > > driver that doesn't work. > > > > What can I install to a buster machine that might make this > > graphical display work? We had, a decade back, a something or other > > "plot" that might have been able to draw a smith chart but I haven't > > seen it in the repos recently. It also was a square plotter, whereas > > the smith chart is circular at its maximum error limits. > > Python3-scikit-rf looks promising to plot the data. > > Debian electronics / Debian ham teams might have some good ideas > > apt-cache search Smith threw this up > > There's also various gnuplot / octave plots that might work. > > Hope this helps > > All best, as ever, > > Andy Cater > Progress report Andy. The code kit I got from a link Didier posted failed to find a resource it needed, but I in my dotage finally remembered I had previously installed pip3 on that rpi4b, which found the missing code and installed it, and it now runs but without connecting to the VNA because its in a briefcase in the truck. Now I need to obtain another rpi4b and put raspbian buster on it, and a full cups install so I can print the smith charts right in the antenna shack that the FCC likes to see. So progress is being made. Gotta spend a few sheckles yet, but the first job will pay for that. Since the resources to do it with linux have now been rounded up, probably my best bet is to put a 60Gb kingston SSD that isn't doing anything else in the winblows all-in-one, in place of the winblows spinning rust install, and put buster on it. Progress, for some definition of the word. That guy Murphy, that wrote all those laws, is alive and plotting against me of course. Thats been an 87 year battle he has lost every time, but he's a stubborn SOB. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: A .profile puzzle
On Saturday 23 October 2021 22:00:42 piorunz wrote: > On 17/10/2021 17:18, Gene Heskett wrote: > > The local electrical system, while better than Haiti's is getting to > > be a nuisance with 5 second power failures about weekly, or is that > > weakly? (...) > > I made some mods to a 3d printer project in openscad last week, > > printed it, but forgot to save it. So I lost it when the latest > > failure rebooted that machine. > > With all due respect, you should know that UPS to power up one > computer for an hour cost £150 on eBay, or even £70 if you can buy > used and/or replace batteries yourself etc, as I did. Just buy that > and begone will be all reboots due to flaky electric, forever. > Not forever, only as long aa the batteries last. And 95% of the ups's seriously overcharge their batteries just to burn them up in 2 or 3 years. All to get an extra 10% runtime they can advertise. Ask ma bell how long those racks of big, glass tanked lead acid batteries in the back room that power your local phone company, last. Some of them are now more than 70 years old and still as good as new. The secret is the correct charge as measured by the SG of the acid in them. You cannot of course meaure a gell cell that way, the only thing you can do is quit charging them when you stop the charge and measure the tempurature sensitive volts, or in the case of a maintenance charger, reduce it over time until arriving at a voltage that results in a charge current below that which produces gas. An experiment I did back in the 70's at a tv station with a 335 commings engine spinning a 150 kw alternator, which could run the transmitter at about 40% power since it was a twin klystron transmitter needing nearly 300 kwh for full power. When I walked in the door in '69 the starter batteries were about 2 years old and about burned up since the maintenance charger was a 20 amp gas station type with a 50 ohm current limiter, no smarts at all. 3 months later they didn't have what it took when those 2 big 225 ah truck batteries were switched to 24 volts to start that cummings. So I cut a P.O. and went to Norfolk and bought two new batteries. And put a 2200 ohm current limiter in circuit to replace the 50 which was litterally boiling the batteries. 2 weeks later they were still warm and gassing so I changed the resistor to 4.7k ohms. Another week and I'd put a 10k in. SG 2 weeks later was nearly 1.28, still too high, 3 or 4 months later the resistor had been raised to 47k, the charging current was then less than 5 milliamps, the SG was still a bit high at 1.27, but the gassing was close to stopped. 8 years later, when I headed on down the road to an office door that said Chief Engineer with my name on it, those two 8 yo batteries were still turning that cum-along 335 everything but wrong side out starting it for its weekly exercise 15 minute run. The start relays closed, the bendix slammed into the flywheel, the first cylinder to hit tdc fired and about a second later the governor hit 1800 rpm and throttled it. All in about 1 short second, and the batteries were then 8 years old. That was in 1977, 45 years ago, maybe they are still there, I haven't checked. While I was there, the alternator on my wagon failed and I got a 120 amp version off a wrecked ambulance and built my own voltage regulator, putting in 4 or 5 times the tempcomp that factory regulators give. Kept a 600 cranking amp battery at around 1.265 SG. No gassing, no water loss, started a 348 pumpjack in -30F weather like it was summertime. The wild tempcomp put that alternator wide open for around a minute after starting but the headlights were a little bright. W/O adding any water, that alternator, regulator and battery were moved to the next 3 wagons I bought while living there. So I think I know a bit about Lead acid batteries. But the little cyberpower 650 I put on the rpi4 doesn't see a very much measurable load, so if the standby doesn't start, it dumps the power to the pi 2 minutes after I pull the plug, bummer & hard on the pi. Idiotic even. from upsc myups: ups.delay.shutdown: 120 ups.delay.start: 0 ups.load: 8 8 watts to run the pi and its interfacing, and the 120 seconds to shutdown is not adjustable. IMO I got took. OTOH it was only 40 bucks. shrug. The 20kw standby is up and running in about 4 seconds, so the 120 does cover it. --< there is no space here Piotr, so your sig gets copied in the quote, put a space after the -- and your sig will, or should, disappear in replies from others to your posts. > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org > ⠈⠳⣄ Thank you Piotr. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please u
problem with an HP AIO
Greetings all; This $350 thing in 2019, a model unk cuz its a tiny label in chinese, has W10HE on it and has decided it can't run the app I bought it for, a python app that I have already proved can run on linux with out needing a winderz magician to make it run. So I decided to remove the spinning rust wonderifitwillrunthistime drive, install a 6x faster kingston 60 GB SSD and put bullseye in it. Just one problem though. Its a work computer but this is only a 20k .py script in linux, where the winderz version is about 20 megs. This AIO has no visible screws anyplace that would let me into it to swap the drive. So, short of a fire axe, how does one get into a 2 yo HP AIO as sold by wally's? Many Thanks to anyone that knows the magic incantation that will open it! Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: problem with an HP AIO
On Monday 25 October 2021 21:37:24 piorunz wrote: > On 26/10/2021 02:29, Gene Heskett wrote: > > Greetings all; > > > > This $350 thing in 2019, a model unk cuz its a tiny label in > > chinese, has W10HE on it and has decided it can't run the app I > > bought it for, a python app that I have already proved can run on > > linux with out needing a winderz magician to make it run. > > > > So I decided to remove the spinning rust wonderifitwillrunthistime > > drive, install a 6x faster kingston 60 GB SSD and put bullseye in > > it. Just one problem though. Its a work computer but this is only a > > 20k .py script in linux, where the winderz version is about 20 megs. > > > > This AIO has no visible screws anyplace that would let me into it to > > swap the drive. > > > > So, short of a fire axe, how does one get into a 2 yo HP AIO as sold > > by wally's? > > > > Many Thanks to anyone that knows the magic incantation that will > > open it! > > > > Cheers, Gene Heskett. > > Hello Gene, > > Can you try again in English this time please, I can't understand what > is the problem you have described in full 5 paragraphs instead of 1. > No essays, just say what is the problem and how you want to fix it. > I need a way into this HP all in one, there are no visible screws anyplace. I want to open it and change the 1T HD out for a 60G kingston SSD. > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org > ⠈⠳⣄ Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: problem with an HP AIO
On Monday 25 October 2021 21:48:24 Greg Wooledge wrote: > how to open HP all-in-one Thank you very much, I think I found a video for the exact one I have from ddg. And have it bookmarked. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: problem with an HP AIO
On Monday 25 October 2021 22:06:09 Larry Martell wrote: > On Mon, Oct 25, 2021 at 9:57 PM Gene Heskett wrote: > > On Monday 25 October 2021 21:37:24 piorunz wrote: > > > On 26/10/2021 02:29, Gene Heskett wrote: > > > > Greetings all; > > > > > > > > This $350 thing in 2019, a model unk cuz its a tiny label in > > > > chinese, has W10HE on it and has decided it can't run the app I > > > > bought it for, a python app that I have already proved can run > > > > on linux with out needing a winderz magician to make it run. > > > > > > > > So I decided to remove the spinning rust > > > > wonderifitwillrunthistime drive, install a 6x faster kingston 60 > > > > GB SSD and put bullseye in it. Just one problem though. Its a > > > > work computer but this is only a 20k .py script in linux, where > > > > the winderz version is about 20 megs. > > > > > > > > This AIO has no visible screws anyplace that would let me into > > > > it to swap the drive. > > > > > > > > So, short of a fire axe, how does one get into a 2 yo HP AIO as > > > > sold by wally's? > > > > > > > > Many Thanks to anyone that knows the magic incantation that will > > > > open it! > > > > > > > > Cheers, Gene Heskett. > > > > > > Hello Gene, > > > > > > Can you try again in English this time please, I can't understand > > > what is the problem you have described in full 5 paragraphs > > > instead of 1. No essays, just say what is the problem and how you > > > want to fix it. > > > > I need a way into this HP all in one, there are no visible screws > > anyplace. I want to open it and change the 1T HD out for a 60G > > kingston SSD. > > Personally, I enjoyed Gene’s eloquent prose. Thanks Larry, but ou speak engish as a first language. Some here I suspect are still in the 80's where every byte costs money. Now its not so iron clad and I can vent my frustrations by inventing prose that is gibberish to those who never got phonics in school, and of coarse may not speak english as first language so they have a double hurdle to jump. Thats unfortunate when I do as it locks those who are translating on the fly, out of the conversation and some BWG's. My apologies as I am forever grateful to those that have learned english as a 2nd or 3rd, 4th etc language. I missed out on any other languages that may have been available when I was in school in the 1940's since I quit school shortly safter the 8th grade and went to work fixing what was then a brand new technology, tv's, and working as a broadcast engineer starting in the 1960's on till I hung that up just short of 20 years ago. In other words, I am now both a Certified Electronics Technician, but a certified old fart at 87 years. I'm growing old, but I refuse to grow up because acting my age is such a bore. :) Thank you all, I did get the help I needed. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Where do I find the definitive man page for mdadm?
Greetings raid experts; The man page we have goes on and on for megabytes without ever giving an example. I thought maybe it could scan for devices so that I could build an mdadm.conf but it wont do a --scan by itself. I have installed 4 1T samsung EVo 870's on their own non-raid sata controller, but with 11 days uptime and the logrotate manager having a 10k is too big attitude, all data from the last reboot has scrolled off the end of /var/log/syslog-7.gz. But I don't see an option (or recognize it if it is there) to give it a controller id and let it make a raid10 out of the 4 identical drives it could find there. If there is such a critter, point me at it please. What I'd like to do when I install bullseye, is use this raid10 for the /home partition in the bullseye install. Thanks. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Problem with Synaptic
On Friday 12 November 2021 07:30:36 Stephen P. Molnar wrote: > On 11/11/2021 03:11 PM, Brian wrote: > > On Thu 11 Nov 2021 at 14:34:20 -0500, Stephen P. Molnar wrote: > >> On 11/11/2021 02:06 PM, Brian wrote: > >>> On Thu 11 Nov 2021 at 12:38:33 -0500, Stephen P. Molnar wrote: > >>>> I am running buster on my Linux platform. > >>>> > >>>> I have installed a new Brother Laser print using the current > >>>> Brother Linux installer. > >>> > >>> The MFC-L2710DW is a modern device and is completely supported by > >>> packages shipped with Debian 11 (bullseye). It is also completely > >>> supported for printing via a wireless connection on buster. > >>> > >>> The packages needed for USB connections and scanning do not come > >>> with buster but can easily be obtained from > >>> > >>> https://github.com/alexpevzner/sane-airscan > >>> > >>> Do yourself a favour and read > >>> > >>> https://wiki.debian.org/CUPSQuickPrintQueues > >>> > >>> A user with a device such as yours does not need proprietary, > >>> non-free printing or scanning drivers in 2021. > >> > >> Very interesting. Thank you. > > > > Interesting indeed. Reaching for printing and scanning drivers, > > whether free or non-free, is still a user's first thought. I > > suppose one should work to tackle the issue you outline but > > switching to driverless printing and scanning is a lot easier > > and makes most problems involving drivers go away. Additionally, > > it future-proofs the printing and scanning systems. > > This is the immediate problem that I need to fix: > > comp@AbNormal:~$ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: The package brscan4 needs to be reinstalled, but I can't find an > archive for it. > > sudo apt update ran without any problems. Thats b'cuz the Brother installer puts all that stuff in /opt, and for the most part I havn't touched it in around 3 years. It has some tcp crc hiccups early on, but thats gone away a long time ago and for a cheap B&W brother lazer, and a huge MFC-J6920DW, it Just Works. And synaptic has not ever asked for my attention by fussing about it. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Problem with Synaptic
On Friday 12 November 2021 07:36:01 Eduardo M KALINOWSKI wrote: > On 12/11/2021 09:30, Stephen P. Molnar wrote: > > This is the immediate problem that I need to fix: > > > > comp@AbNormal:~$ sudo apt upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > E: The package brscan4 needs to be reinstalled, but I can't find an > > archive for it. > > > > sudo apt update ran without any problems. > > Try downloading it again (since it's not part of the archives, it must > be downloaded manually) and running 'apt install ./brscan4-..deb' > (substituting the actual file name, naturally). The './' is necessary > to tell apt it's a file name. No, to be precise, it tells the file system its a file in the currently cd'd to directory. Which may not be in the env's $PATH. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 08:39:31 Charles Curley wrote:
> On Fri, 12 Nov 2021 08:05:53 -0500
>
> Gene Heskett wrote:
> > The man page we have goes on and on for megabytes without ever
> > giving an example.
> >
> > I thought maybe it could scan for devices so that I could build an
> > mdadm.conf but it wont do a --scan by itself.
>
> Nope, near as I can figure --scan only works with an existing RAID
> setup. You have to create it first. And you have to create it
> manually. mdadm is not going to guess.
>
> Not that I am any kind or RAID expert, but I did create a RAID1
> installation about a year ago. I recently added a drive and moved from
> RAID1 to RAID5.
>
> In the interest of protecting my data should I ever have to install
> one of these drives somewhere else, I first created a partition on
> each of the two new drives. Then:
>
> mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sdc1
> /dev/sdd1
Thats what I've been looking for, a commandline example I can modify for
my use. Since posting, I have found that gparted spits out a list of
disks that have never been labeled, and those then are the disks I'll
want to use.
So
mdadm --create --verbose /dem/md0 --level=10 --raid-devices=4 /dev/sde /dev/sdf
/dev/sdg /dev/sdh
should work.
but once assembled, does it need formatted? I don't intend to encrypt.
> I then set up encryption in the RAID device:
>
> cryptsetup -y -v luksFormat /dev/md0
> cryptsetup luksOpen /dev/md0 encryptedRaid
> cryptsetup -v status encryptedRaid
> cryptsetup luksDump /dev/md0
>
> Preserve the header, just in case
> cryptsetup luksHeaderBackup /dev/md0 --header-backup-file
> ${HOSTNAME}.$(date +%Y.%m.%d).luks.raid.backup
>
> Then build the LVM on top of /dev/mapper/encryptedRaid:
>
> pvcreate /dev/mapper/encryptedRaid# create the physical volume.
> vgcreate hawk-vg-raid /dev/mapper/encryptedRaid # Create the volume
> group. lvcreate -n crc$( date +%Y ) -L 2862612M hawk-vg-raid # Create
> a logical volume
>
> etc. The RAID5 setup is working just fine.
>
> Note: The RAID volume is open for business as soon as you create it.
> But it will then take several hours to sync between the two drives.
> Same thing when I expanded from RAID1 to RAID5; it took more than a
> day of steady thrashing.
>
> Hope that helps.
A bunch, thanks.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 08:49:21 Dan Ritter wrote: > Gene Heskett wrote: > > The man page we have goes on and on for megabytes without ever > > giving an example. > > > > I thought maybe it could scan for devices so that I could build an > > mdadm.conf but it wont do a --scan by itself. > > You are looking for > > mdadm --detail --scan > > It is in that man page, as an example under --detail. > > > But I don't see an option (or recognize it if it is there) to give > > it a controller id and let it make a raid10 out of the 4 identical > > drives it could find there. > > > > If there is such a critter, point me at it please. > > You have to feed mdadm the drives you want specifically; there's > no scattershot approach. > > Let's say that the drives are /dev/sdf, /dev/sdg, /dev/sdh and > /dev/sdi. > > (You can re-confirm what drive is what via hdparm -i, or > smartctl.) > > If you have data on them, it will be wiped out. You should copy > off anything important, and then run wipefs on each of them. > > Then, creation is > > # mdadm -C /dev/md0 --level=10 --raid-devices=4 /dev/sdf /dev/sdg > /dev/sdh /dev/sdi > > (assuming you want it named /dev/md0 and there isn't one > already) > > Then you can make a filesystem on /dev/md0 and put it in your > fstab, mount it, and copy data over to it. > Thats was my next Q... > > What I'd like to do when I install bullseye, is use this raid10 for > > the /home partition in the bullseye install. > > The installer will recognize it as an md RAID and can be told that you > want to use it as-is, or you can destroy it and re-create it without > data. > > -dsr- Thanks Dan Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 08:49:21 Dan Ritter wrote: > Gene Heskett wrote: > > The man page we have goes on and on for megabytes without ever > > giving an example. > > > > I thought maybe it could scan for devices so that I could build an > > mdadm.conf but it wont do a --scan by itself. > > You are looking for > > mdadm --detail --scan > Null return on stretch version of mdadm. Supposedly up to date as of an hour ago. > It is in that man page, as an example under --detail. Not in the stretch man page. And its sounding as if I should do that during the bullseye install to get the more capable mdadm, but will the devices have the same names? With the reputation for volatility of device names a mistake there could destroy 23 years of data. > > But I don't see an option (or recognize it if it is there) to give > > it a controller id and let it make a raid10 out of the 4 identical > > drives it could find there. > > > > If there is such a critter, point me at it please. > > You have to feed mdadm the drives you want specifically; there's > no scattershot approach. > > Let's say that the drives are /dev/sdf, /dev/sdg, /dev/sdh and > /dev/sdi. > > (You can re-confirm what drive is what via hdparm -i, or > smartctl.) > > If you have data on them, it will be wiped out. You should copy > off anything important, and then run wipefs on each of them. > > Then, creation is > > # mdadm -C /dev/md0 --level=10 --raid-devices=4 /dev/sdf /dev/sdg > /dev/sdh /dev/sdi > > (assuming you want it named /dev/md0 and there isn't one > already) > > Then you can make a filesystem on /dev/md0 and put it in your > fstab, mount it, and copy data over to it. So mkfs.ext4 /md0 is required, ok > > What I'd like to do when I install bullseye, is use this raid10 for > > the /home partition in the bullseye install. > > The installer will recognize it as an md RAID and can be told that you > want to use it as-is, or you can destroy it and re-create it without > data. > > -dsr- Thanks Dan. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 09:29:06 David Wright wrote:
> On Fri 12 Nov 2021 at 08:05:53 (-0500), Gene Heskett wrote:
> > I have installed 4 1T samsung EVo 870's on their own non-raid sata
> > controller, but with 11 days uptime and the logrotate manager
> > having a 10k is too big attitude, all data from the last reboot has
> > scrolled off the end of /var/log/syslog-7.gz.
>
> Package rsyslog doesn't have attitude, it has:
>
> $ head -12 /etc/logrotate.d/rsyslog
> /var/log/syslog
> {
> rotate 7 ← increase to whatever you like
> daily
> missingok
> notifempty
> delaycompress
> compress
> postrotate
> /usr/lib/rsyslog/rsyslog-rotate
> endscript
> }
> $
And I just changed daily to weekly. Daily scrolls what I want to check on
out of reach way too soon.
> Cheers,
> David.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 10:18:07 Dan Ritter wrote: > Gene Heskett wrote: > > On Friday 12 November 2021 08:49:21 Dan Ritter wrote: > > > Gene Heskett wrote: > > > > The man page we have goes on and on for megabytes without ever > > > > giving an example. > > > > > > > > I thought maybe it could scan for devices so that I could build > > > > an mdadm.conf but it wont do a --scan by itself. > > > > > > You are looking for > > > > > > mdadm --detail --scan > > > > Null return on stretch version of mdadm. Supposedly up to date as of > > an hour ago. > > That would be expected if you don't have any current mdadm > devices. Explains that, thanks. > > Not in the stretch man page. And its sounding as if I should do > > that during the bullseye install to get the more capable mdadm, but > > will the devices have the same names? With the reputation for > > volatility of device names a mistake there could destroy 23 years of > > data. > > After you have set them up, mdadm.conf has things like this: > > ARRAY /dev/md/0 metadata=1.2 name=debian:0 > UUID=aeac6271:676b1852:04f077d6:fcd285d6 ARRAY /dev/md/1 metadata=1.2 > name=debian:1 UUID=d74ff881:2e966c37:ec6ef1ec:75b8cdce ARRAY /dev/md/2 > metadata=1.2 name=debian:2 UUID=7c56166b:0d5aed8b:a9d03c45:e9b8080c That doesn't appear to be true. I have run the create which seemed to be ok, then mkfs -text4 /dev/md0, then mounted it at /home2. But /etc/mdadm/mdadm.conf doesn't yet have any of that, only this: gene@coyote:~$ cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default (built-in), scan all partitions (/proc/partitions) and all # containers for MD superblocks. alternatively, specify devices to scan, using # wildcards if desired. #DEVICE partitions containers # automatically tag new arrays as belonging to the local system HOMEHOST # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays # This configuration was auto-generated on Sun, 08 Aug 2021 01:18:22 -0400 by mkconf Which from your descriptions is not complete. No ARRAY statements at all. What did I do wrong? And again, I don't trust UUID's as moving a drive cable to a different socket has invalidated the whole lot of them once before. I would much rather LABEL the array, and mount it in /etc/fstab by that label. At the instant its mounted as /dev/md0 to /home2 and looks like an empty nearly 2 T-byte drive to an ls -la: gene@coyote:~$ ls -la /home2 total 24 drwxr-xr-x 3 root root 4096 Nov 12 11:12 . drwxr-xr-x 29 root root 4096 Nov 12 11:16 .. drwx-- 2 root root 16384 Nov 12 11:12 lost+found LABEL as I recall is a journalctl function? Does it work on raid10's? Humm, now: gene@coyote:~/AppImages$ sudo mdadm --detail --scan [sudo] password for gene: ARRAY /dev/md0 metadata=1.2 name=coyote:0 UUID=8ad67ef1:a14d63ab:c684ec2b:42a0c011 So I should add that last line to which category in mdadm.conf? And for the time being use that UUID in /etc/fstab to mount it to /home2, right? > And during boot, the system will look for all drives/partitions that > fit that UUID for assembly, regardless of whether they are currently > named /dev/hdc3, /dev/sdq, or /dev/nvme0np1. > > -dsr- Thanks Dan Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 10:37:22 Andy Smith wrote: > Hello, > > On Fri, Nov 12, 2021 at 09:22:12AM -0500, Gene Heskett wrote: > > mdadm --create --verbose /dem/md0 --level=10 --raid-devices=4 > > /dev/sde /dev/sdf /dev/sdg /dev/sdh > > > > should work. > > You may want to create identical partitions on each of the devices > first, and use those instead of the raw unpartitioned devices. > > The reason is that there is hardware (primarily motherboards) out > there that get upset when they see a drive without a partition > table, and just blindly make one, which corrupts your RAID. There > are ASRock motherboards which are known to do this at every boot. > > Such things are broken of course and ideally would be avoided, but > having all your drives corrupted isn't a nice way to discover that > you own one. yes, makes you want to use the whole maryann for target practice, BTDT, something I am well equipt to do. All for just moving a drives sata cable to a different socket on the previous Asus motherboard, and so is this one, an Asus PRIME Z-370-A-II with a 6 core i5. > > but once assembled, does it need formatted? > > It will be an empty block device like any other. You get to choose > what filesystem to put on it, or use it however else you might use a > block device. Condensing this down bare bones it sounds like I should un-mount it, format each to ext4 and re-create it just in case. And should nuke mdadm.conf before re-creating it. Correct? Thanks Andy. > Cheers, > Andy Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 11:34:24 Charles Curley wrote: > On Fri, 12 Nov 2021 09:22:12 -0500 > > Gene Heskett wrote: > > So > > > > mdadm --create --verbose /dem/md0 --level=10 --raid-devices=4 > > /dev/sde /dev/sdf /dev/sdg /dev/sdh > > > > should work. > > It should. But there are good reasons to put partitions on the drives > first and use the partitions.. > > > but once assembled, does it need formatted? > > Yes. It's a raw block partition. > > I put LVM on, and made a logical volume which left some space so I > would have lots of flexibility in my array. > > There is a systemd service in Bullseye that creates a snapshot of LVM > logical volumes, fscks the snapshot, and reports the result if there > is an error. So I leave at least 20 GB available on my system disk for > that. Leaving a chunk available for that on your RAID array strikes me > as a good idea. Thanks Charles. Sounds like a good idea. I'll see if I can get gparted to see them now. It see's it, but its locked, in use by the system even if unmounted. Now what? Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 11:49:29 The Wanderer wrote: > On 2021-11-12 at 11:42, Gene Heskett wrote: > > On Friday 12 November 2021 10:18:07 Dan Ritter wrote: > >> Gene Heskett wrote: > >> > Not in the stretch man page. And its sounding as if I should do > >> > that during the bullseye install to get the more capable mdadm, > >> > but will the devices have the same names? With the reputation for > >> > volatility of device names a mistake there could destroy 23 years > >> > of data. > >> > >> After you have set them up, mdadm.conf has things like this: > >> > >> ARRAY /dev/md/0 metadata=1.2 name=debian:0 > >> UUID=aeac6271:676b1852:04f077d6:fcd285d6 ARRAY /dev/md/1 > >> metadata=1.2 name=debian:1 UUID=d74ff881:2e966c37:ec6ef1ec:75b8cdce > >> ARRAY /dev/md/2 metadata=1.2 name=debian:2 > >> UUID=7c56166b:0d5aed8b:a9d03c45:e9b8080c > > > > That doesn't appear to be true. I have run the create which seemed > > to be ok, then mkfs -text4 /dev/md0, then mounted it at /home2. > > > > But /etc/mdadm/mdadm.conf doesn't yet have any of that, only this: > > > > > Which from your descriptions is not complete. No ARRAY statements at > > all. What did I do wrong? > > Not sure if you did anything wrong, but now that you've done the > --create operation, you might try running > > # mdadm --detail --scan > > again. You might see that it now outputs definition lines like the > ones Dan presented as examples; if so, you can append those lines to > mdadm.conf, and if I'm not mistaken the result should (in theory) be > valid. > > > And again, I don't trust UUID's as moving a drive cable to a > > different socket has invalidated the whole lot of them once before. > > Eh? That doesn't make any sense at all. The UUID is supposed to be > stored *on* the drive, so that it is independent of connection. I can > testify that this has been the case in my experience with mdadm > RAID-array UUIDs. Does re-running blockid rewrite those? I recall I did that when the moved cable didn't mount on reboot. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 11:56:48 Dan Ritter wrote: > Andy Smith wrote: > > On Fri, Nov 12, 2021 at 09:22:12AM -0500, Gene Heskett wrote: > > > mdadm --create --verbose /dem/md0 --level=10 --raid-devices=4 > > > /dev/sde /dev/sdf /dev/sdg /dev/sdh > > > > > > should work. > > > > You may want to create identical partitions on each of the devices > > first, and use those instead of the raw unpartitioned devices. > > > > The reason is that there is hardware (primarily motherboards) out > > there that get upset when they see a drive without a partition > > table, and just blindly make one, which corrupts your RAID. There > > are ASRock motherboards which are known to do this at every boot. > > There's also the fact that disk manufacturers are notoriously > unable to commit to the same size disks across models. A RAID > expecting 4 identical 1,024,000,048,576 byte disks might be > unhappy when you have to substitute in a 1,016,000,000,384 byte > disk from the same manufacturer -- but if you created partitions > that were all 1,000,000,000,000 in size, everyone will get > along. > > -dsr- Dan: Forced to reboot to see if that would enable me to setup 2 partitions per disk that failed as the raid label overides any write perms, its locked for the other disk managers although fdisk was able to create and w rite an empty GPT table, which did not release the raid locks. So the ultimate hammer is now zeroing /dev/sde. At a rather glacial pace. Once that is done, I'll setup a 900g partition on each of /dev/sde|f|g| h1, and the remainder for the snapshots, called /dev/sde|f|g|h2. I was able to create an empty GPT table with fdisk and write it without being denied. I'll do the same with the other 3, and nuke /etc/mdadm/mdadm.conf, then do the /dev/md0 creation again with /dev/sde|f|g|h1 and md1 with the same list replacing the 1 with a 2. Then format md0 and md1. Will this satisfy everything? But now the real write speed is being tested, and it will take nearly 40 minutes to zero each drive, its used up the write buffer. Or /dev/zero is glacial. 1000204886016 bytes (1.0 TB, 932 GiB) copied, 2040.6 s, 490 MB/s =34 minutes And dd used to have a progress bar, but no mention in the man page, when did that go away? Its looking as if I'll have to reboot after zeroing all 4 of them, nuking mdadm.conf first. /dev/sde is still locked by the raid. Is there a quicker way to undo the creation and get my drives back to square zero so I can start all over? Thank you. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 11:57:28 Andrew M.A. Cater wrote: > On Fri, Nov 12, 2021 at 09:48:01AM -0500, Gene Heskett wrote: > > On Friday 12 November 2021 08:49:21 Dan Ritter wrote: > > > Gene Heskett wrote: > > > > The man page we have goes on and on for megabytes without ever > > > > giving an example. > > > > > > > > I thought maybe it could scan for devices so that I could build > > > > an mdadm.conf but it wont do a --scan by itself. > > > > > > You are looking for > > > > > > mdadm --detail --scan > > > > Null return on stretch version of mdadm. Supposedly up to date as of > > an hour ago. > > > > > It is in that man page, as an example under --detail. > > > > Not in the stretch man page. And its sounding as if I should do > > that during the bullseye install to get the more capable mdadm, but > > will the devices have the same names? With the reputation for > > volatility of device names a mistake there could destroy 23 years of > > data. > > > > > > But I don't see an option (or recognize it if it is there) to > > > > give it a controller id and let it make a raid10 out of the 4 > > > > identical drives it could find there. > > > > > > > > If there is such a critter, point me at it please. > > > > > > You have to feed mdadm the drives you want specifically; there's > > > no scattershot approach. > > > > > > Let's say that the drives are /dev/sdf, /dev/sdg, /dev/sdh and > > > /dev/sdi. > > > > > > (You can re-confirm what drive is what via hdparm -i, or > > > smartctl.) > > > > > > If you have data on them, it will be wiped out. You should copy > > > off anything important, and then run wipefs on each of them. > > > > > > Then, creation is > > > > > > # mdadm -C /dev/md0 --level=10 --raid-devices=4 /dev/sdf /dev/sdg > > > /dev/sdh /dev/sdi > > > > > > (assuming you want it named /dev/md0 and there isn't one > > > already) > > > > > > Then you can make a filesystem on /dev/md0 and put it in your > > > fstab, mount it, and copy data over to it. > > > > So mkfs.ext4 /md0 is required, ok > > > > > > What I'd like to do when I install bullseye, is use this raid10 > > > > for the /home partition in the bullseye install. > > > > > > The installer will recognize it as an md RAID and can be told that > > > you want to use it as-is, or you can destroy it and re-create it > > > without data. > > > > > > -dsr- > > > > Thanks Dan. > > > > Cheers, Gene Heskett. > > -- > > "There are four boxes to be used in defense of liberty: > > soap, ballot, jury, and ammo. Please use in that order." > > -Ed Howdershelt (Author, 1940) > > If we desire respect for the law, we must first make the law > > respectable. - Louis D. Brandeis > > Genes Web page <http://geneslinuxbox.net:6309/gene> > > Gene > > At the point when you want to install Bullseye: > > Use an expert install. > > set up the disks as RAID 10 first, then use the partition editor to > assign the RAID as /home > > At that point, you're done :) That will be good, but getting rid of the first raid10 I built is needing tactical nukes. Its taking almost 40 minutes a drive to zero them and start over. And this machine is acting like an 8086 machine doing it. very very slow. gkrellm is showing all 6 core in bright orange. Not any great temp rises though, staying below 35C for all 6 cores. The heat sink/radiator is huge, so huge I can't put the side panel back on the tower. 5" fan is turning silently at maybe 400 revs. I think I overbuilt it ;o) > All the very best, as ever, Of coarse, to you too Andy. Stay well. > Andy C. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 12:07:54 Charles Curley wrote: > On Fri, 12 Nov 2021 11:53:45 -0500 > > Gene Heskett wrote: > > Condensing this down bare bones it sounds like I should un-mount it, > > format each to ext4 and re-create it just in case. And should nuke > > mdadm.conf before re-creating it. Correct? > > Umount it, move mdadm.conf aside, create a new partition on each > drive. Don't bother to format any of them, mdadm will clobber that > formatting anyway. What do I use to create/write a new GPT partition table? Despite nuking mdadm.conf, and zeroing the drive with dd, its still locked and untouchable by gparted. And I cannot rmmod the raid stuff, its busy. Blanking the third one now with dd a 34 minute job. I'll reboot again when the 4th drive has been zeroed. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 12:26:02 Charles Curley wrote: > On Fri, 12 Nov 2021 12:03:25 -0500 > > Gene Heskett wrote: > > Thanks Charles. Sounds like a good idea. I'll see if I can get > > gparted to see them now. It see's it, but its locked, in use by the > > system even if unmounted. Now what? > > Well, if you are talking Any Smith's (and my) advice, I'd do the > following: > > * Umount the partition on the RAID array. > > * Move /etc/mdadm/mdadm.conf aside. > > * Put partitions on each of the four drives. Don't bother to put a > file system on any of them. > > * Use the same command line you did before, *except* use the > partitions you just created instead of the drives, to create the RAID > array. > > * Create the LVM stuff you need. I've only taken one pass at LVM, years ago in early fedora days before I got tired of running redhats lab-rat software, and it was the cause of three or so reinstalls and a total loss of all data each time. So I'm understandably spooky about it. Is it now dependable enough to use on a one box does it all machine? > * Lay down an ext4 file system on logical volumes as needed. > > * Add the LVs to /etc/fstab as needed. Thank you Charles. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Problem with Synaptic
On Friday 12 November 2021 13:38:48 Greg Wooledge wrote: > On Fri, Nov 12, 2021 at 08:19:15AM -0500, Gene Heskett wrote: > > On Friday 12 November 2021 07:36:01 Eduardo M KALINOWSKI wrote: > > > On 12/11/2021 09:30, Stephen P. Molnar wrote: > > > > This is the immediate problem that I need to fix: > > > > > > > > comp@AbNormal:~$ sudo apt upgrade > > > > Reading package lists... Done > > > > Building dependency tree > > > > Reading state information... Done > > > > E: The package brscan4 needs to be reinstalled, but I can't find > > > > an archive for it. > > > > > > > > sudo apt update ran without any problems. > > > > > > Try downloading it again (since it's not part of the archives, it > > > must be downloaded manually) and running 'apt install > > > ./brscan4-..deb' (substituting the actual file name, > > > naturally). The './' is necessary to tell apt it's a file name. > > > > No, to be precise, it tells the file system its a file in the > > currently cd'd to directory. Which may not be in the env's $PATH. > > It's both, Gene. > > To the file system (kernel), ./foo is a relative pathname that's 100% > equivalent to foo. There's no difference at all. > > However, to apt-get or apt, ./foo and foo are very different > arguments. The former is a relative path to a file, and the latter is > a package name. > > This has nothing to do with $PATH, because we're not talking about > running a program from the current directory. We're talking about > apt-get and apt specifically. > > You're thinking of the conventional use of "./configure" and so on to > run a program in the current directory. This is necessary because > PATH should never contain "." (or the empty string) as one of its > components. That would allow the execution of *anything* at all in > the current directory (the way MS-DOS works). This is a huge security > problem on a multi-user system, where someone could leave a script in > /tmp hoping for you to run it accidentally. > > It *works* because the shell bypasses the PATH search if the command > that you give it contains a slash character. ./configure means "run > the program named configure in the current directory, and don't search > anywhere else". Thanks Greg, a better view than mine. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 08:49:21 Dan Ritter wrote: Ok, zeroed them, nuked mdadm.conf & rebooted. gparted each one, setting 2 partitions in GPT format on each of 90 MIB (sde1) with label MDV1 and 5000 MIB (sde2) labeled MDV2 and applied that to each of the 4 drives. Double check as /dev/sdf somehow swapped positions on the drive, fixed that: Wash rinse and repeat for sdf, sdg, and sdh with labels of MDX1, MDX2, MDY1, MDY2 and MDZ1 and MDZ2. And of course gparted makes a file system when Apply is clicked. but: root@coyote:~$ mdadm -C /dev/md0 --level=10 --raid-devices=4 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 mdadm: /dev/sde1 appears to contain an ext2fs file system size=92160K mtime=Wed Dec 31 19:00:00 1969 mdadm: /dev/sdf1 appears to contain an ext2fs file system size=92160K mtime=Wed Dec 31 19:00:00 1969 mdadm: /dev/sdg1 appears to contain an ext2fs file system size=92160K mtime=Wed Dec 31 19:00:00 1969 mdadm: /dev/sdh1 appears to contain an ext2fs file system size=92160K mtime=Wed Dec 31 19:00:00 1969 Continue creating array? yes mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md0 started. root@coyote:~$ mdadm -C /dev/md1 --level=10 --raid-devices=4 /dev/sde2 /dev/sdf2 /dev/sdg2 /dev/sdh2 mdadm: /dev/sde2 appears to contain an ext2fs file system size=5120K mtime=Wed Dec 31 19:00:00 1969 mdadm: /dev/sdf2 appears to contain an ext2fs file system size=5120K mtime=Wed Dec 31 19:00:00 1969 mdadm: /dev/sdg2 appears to contain an ext2fs file system size=5120K mtime=Wed Dec 31 19:00:00 1969 mdadm: /dev/sdh2 appears to contain an ext2fs file system size=5120K mtime=Wed Dec 31 19:00:00 1969 Continue creating array? yes mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md1 started. root@coyote:~$ mkfs -Text4 /dev/md0 mke2fs 1.43.4 (31-Jan-2017) mkfs.ext2: invalid blocks '/dev/md0' on device 'mkfs' There are a few unallocated blocks at the ends of all drives. gparted chose alignment and prespace in MiB. Do I need to add a 3rd partition to use them up? All drives seem to be identical sizewise but the pages recommend identical partition sizes. Theoreticly I could expand the smaller partition to use it up. rerunning gparted, I find 4 870 GIB partitions labeled coyote:0 and 4 47 GiB paartitions all labeled coyote:1. Which isn't what I told gparted to label them as with about 3.5 GIB unallocated on each one. So I am lost as to Whats next? Or do I start doing it all over again using some other partitioning tool? Thanks all. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 15:12:15 Dan Ritter wrote: > Gene Heskett wrote: > > On Friday 12 November 2021 11:57:28 Andrew M.A. Cater wrote: > > > Use an expert install. > > > > > > set up the disks as RAID 10 first, then use the partition editor > > > to assign the RAID as /home > > > > > > At that point, you're done :) > > > > That will be good, but getting rid of the first raid10 I built is > > needing tactical nukes. Its taking almost 40 minutes a drive to > > zero them and start over. And this machine is acting like an 8086 > > machine doing it. very very slow. gkrellm is showing all 6 core in > > bright orange. Not any great temp rises though, staying below 35C > > for all 6 cores. The heat sink/radiator is huge, so huge I can't put > > the side panel back on the tower. 5" fan is turning silently at > > maybe 400 revs. I think I overbuilt it ;o) > > No need to do it the hard way: > > For each disk, run > > # wipefs /dev/sdX > > which will not destroy anything ; it will list the commands > needed to remove the existing filesystems. > > Then run that command, generally of the form wipdefs -o 0x1000 > or such, which will complete in seconds. > > Repeat for the next disk. > > -dsr- root@coyote:~$ wipefs /dev/sde -o 0x1000 wipefs: error: /dev/sde: probing initialization failed: Device or resource busy And I have to reboot as mdadm has no stop command. Thats BS. I did cobble up a wipefs with dd, wipefs cannot do it without yet another reboot. dd does not check, it just zeros the first 1000 hex blocks. Thanks Dan. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 17:01:01 The Wanderer wrote: > On 2021-11-12 at 16:52, Gene Heskett wrote: > > On Friday 12 November 2021 15:12:15 Dan Ritter wrote: > >> Gene Heskett wrote: > >>> That will be good, but getting rid of the first raid10 I built > >>> is needing tactical nukes. Its taking almost 40 minutes a drive > >>> to zero them and start over. And this machine is acting like an > >>> 8086 machine doing it. very very slow. gkrellm is showing all 6 > >>> core in bright orange. Not any great temp rises though, staying > >>> below 35C for all 6 cores. The heat sink/radiator is huge, so > >>> huge I can't put the side panel back on the tower. 5" fan is > >>> turning silently at maybe 400 revs. I think I overbuilt it ;o) > >> > >> No need to do it the hard way: > >> > >> For each disk, run > >> > >> # wipefs /dev/sdX > >> > >> which will not destroy anything ; it will list the commands needed > >> to remove the existing filesystems. > >> > >> Then run that command, generally of the form wipdefs -o 0x1000 or > >> such, which will complete in seconds. > >> > >> Repeat for the next disk. > >> > >> -dsr- > > > > root@coyote:~$ wipefs /dev/sde -o 0x1000 > > wipefs: error: /dev/sde: probing initialization failed: Device or > > resource busy > > And I have to reboot as mdadm has no stop command. Thats BS. > > Eh? > > From the mdadm man page (at least on my machine): But not on mine but I'll be switched, it worked and I was then able to format both and have the bigger one mounted, this time w/o any fussing after typeing yes, Like I've said 2 or 3 times, my man pages for a lot of this are NOT uptodate. Very frustrating. And thank you, a bunch! > >-S, --stop > deactivate array, releasing all resources. > > And from the EXAMPLES section: > > mdadm --stop --scan >This will shut down all arrays that can be shut down (i.e. are > not cur‐ >rently in use). This will typically go in a system shutdown > script. > > While it's probably not possible to stop the mdraid backend (since > IIRC it's part of the kernel?), it should certainly be possible to > tell it to let go of the devices it's managing. It sure did. Thank you again. Now I can proceed. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Friday 12 November 2021 17:43:34 Charles Curley wrote: > On Fri, 12 Nov 2021 13:41:22 -0500 > > Gene Heskett wrote: > > And dd used to have a progress bar, but no mention in the man page, > > when did that go away? > > From man dd: > >status=LEVEL > The LEVEL of information to print to stderr; 'none' >suppresses everything but error messages, 'noxfer' suppresses >the final transfer statistics, 'progress' shows periodic >transfer statistics Well, I sit corrected, it is there but gkrellm was sitting on top of progress. Thank you. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 06:02:35 Dan Ritter wrote: > Gene Heskett wrote: > > On Friday 12 November 2021 08:49:21 Dan Ritter wrote: > > > > Ok, zeroed them, nuked mdadm.conf & rebooted. > > gparted each one, setting 2 partitions in GPT format on each of > > 90 MIB (sde1) with label MDV1 and 5000 MIB (sde2) labeled MDV2 > > and applied that to each of the 4 drives. Double check as /dev/sdf > > somehow swapped positions on the drive, fixed that: Wash rinse and > > repeat for sdf, sdg, and sdh with labels of MDX1, MDX2, MDY1, MDY2 > > and MDZ1 and MDZ2. And of course gparted makes a file system when > > Apply is clicked. > > > > but: > > root@coyote:~$ > > mdadm -C /dev/md0 --level=10 --raid-devices=4 /dev/sde1 /dev/sdf1 > > /dev/sdg1 /dev/sdh1 mdadm: /dev/sde1 appears to contain an ext2fs > > file system > >size=92160K mtime=Wed Dec 31 19:00:00 1969 > > mdadm: /dev/sdf1 appears to contain an ext2fs file system > >size=92160K mtime=Wed Dec 31 19:00:00 1969 > > mdadm: /dev/sdg1 appears to contain an ext2fs file system > >size=92160K mtime=Wed Dec 31 19:00:00 1969 > > mdadm: /dev/sdh1 appears to contain an ext2fs file system > >size=92160K mtime=Wed Dec 31 19:00:00 1969 > > Continue creating array? yes > > You should stop there and run wipefs. I note from later mail in > this thread that you didn't; and then you had to reboot. > > With the array not started, or stopped, run wipefs on each of > the partitions. My mdadm manpage does not show the -S command. Scanniing it again to make sure, probably for about the 10th time and I finally found it but many megabytes of relatively unimportant drivel down from the top, IMO the manpage is missleading as such an important option ought to be shown on the first screenfull. So wipefs failed. dd doesn't care so zeroed the first 1000 blocks of each drive, nuke mdadm.conf then rebooted, gparted was then able to reconfigure the drives. But then mdadm wouldn't accept because gparted had formatted them, not to mention miss-labeled them, so yet another reboot, and keep rebooting unil somebody, Wanderer I believe, told me about "mdadm -S /dev/ice" command. Turns out I had to use fdisk to create a GPT partition table, one at +900G and one at +30G on each drive without formatting, then reboot again after nukeing mdadm.conf for the 9th or so time, at which point I was able to create a raid10 using sde1,sdf1,sfg1,and sdh1 as md0, and an md1 as sde2,sdf2,sdg2 and sdh2, and then format them both to ext4. > Then these -C commands should work well without warnings, and > creating a filesystem on the /dev/mdX devices will proceed > without warnings or errors. Yes, finally, but the mdadm man page and its poor formatting were far more hindrance than help. Experienced people here are to be thanked, and I do, but not that disastrous man page. > > There are a few unallocated blocks at the ends of all drives. > > gparted chose alignment and prespace in MiB. Do I need to add a 3rd > > partition to use them up? All drives seem to be identical sizewise > > but the pages recommend identical partition sizes. Theoreticly I > > could expand the smaller partition to use it up. > > I would not bother. > > -dsr- Thanks Dan. And everyone else who came to my rescue in this long thread. Nearly everyone was Cc: ing me, but I'm subscribed, close to a decade, maybe more. So I have duplicates to clean up. NBD. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 07:33:49 Andy Smith wrote: > Hello, > > On Fri, Nov 12, 2021 at 11:42:32AM -0500, Gene Heskett wrote: > > On Friday 12 November 2021 10:18:07 Dan Ritter wrote: > > > After you have set them up, mdadm.conf has things like this: > > > > > > ARRAY /dev/md/0 metadata=1.2 name=debian:0 > > > UUID=aeac6271:676b1852:04f077d6:fcd285d6 ARRAY /dev/md/1 > > > metadata=1.2 name=debian:1 > > > UUID=d74ff881:2e966c37:ec6ef1ec:75b8cdce ARRAY /dev/md/2 > > > metadata=1.2 name=debian:2 > > > UUID=7c56166b:0d5aed8b:a9d03c45:e9b8080c > > > > That doesn't appear to be true. I have run the create which seemed > > to be ok, then mkfs -text4 /dev/md0, then mounted it at /home2. > > > > But /etc/mdadm/mdadm.conf doesn't yet have any of that, only this: > > You don't need to list the arrays in /etc/mdadm/mdadm.conf since > udev assembles arrays based on the metadata that exists on each > device. It's fine for there to be no ARRAY lines in there. These > days it's only really useful in recovery situations or for setting > some special options per array. > > You can still do the > > # mdadm --detail --scan > > to find the lines to put in the mdadm.conf yourself. > > > And again, I don't trust UUID's as moving a drive cable to a > > different socket has invalidated the whole lot of them once before. > > I would much rather LABEL the array, and mount it in /etc/fstab by > > that label. > > There may be some conceptual error here. The UUIDs you would put in > /etc/fstab are FILESYSTEM UUIDs, not array UUIDs. Lots of things in > computing have UUIDs. > > After you put a filesystem on each array you can refer to the > FILESYSTEM label in /etc/fstab. These labels are internal to each > filesystem and nothing to do with any layer below, such as md. > > > LABEL as I recall is a journalctl function? Does it work on > > raid10's? Its been quite a while but fdisk didn't do labels, but I see it grew that along with GPT tables. But back in the day, ISTR adding a label to a drive was done by journalctl and I'd call adding a label to a drive a function. > Filesystem labels have nothing to do with journalctl. And I don't > know what you mean by them being "a function". > > Again, filesystems (can) have labels, these are a filesystem detail, > RAID doesn't know nor care. So I see, but the names for md0 and md1 are shown as hostname:0 and hostname:1 > > Humm, now: > > gene@coyote:~/AppImages$ sudo mdadm --detail --scan > > [sudo] password for gene: > > ARRAY /dev/md0 metadata=1.2 name=coyote:0 > > UUID=8ad67ef1:a14d63ab:c684ec2b:42a0c011 > > > > So I should add that last line to which category in mdadm.conf? > > mdamd.conf doesn't have categories. You would just append that line > at the end, ensuring it is all on one line. Yup, that was kmails word wrap. I forgot to turn it off when I pasted that. > > > And for the time being use that UUID in /etc/fstab to mount it to > > /home2, right? > > No, because that is not a filesystem UUID. And you said you wanted > to mount the filesystem by label anyway. So put whatever label you > chose when you did mkfs (or when you did it form the installer). > > In a later email you did this: > > # mkfs -Text4 … > > and got an obscure error. > > That's because you did "-T" instead of "-t", which means something > completely different. You may want to get into the habit of doing: > > # mkfs.ext4 … > > instead as it's clearer and easier to remember. > > Cheers, > Andy Thanks Andy. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 07:33:49 Andy Smith wrote: > Hello, > > On Fri, Nov 12, 2021 at 11:42:32AM -0500, Gene Heskett wrote: > > On Friday 12 November 2021 10:18:07 Dan Ritter wrote: > > > After you have set them up, mdadm.conf has things like this: > > > > > > ARRAY /dev/md/0 metadata=1.2 name=debian:0 > > > UUID=aeac6271:676b1852:04f077d6:fcd285d6 ARRAY /dev/md/1 > > > metadata=1.2 name=debian:1 > > > UUID=d74ff881:2e966c37:ec6ef1ec:75b8cdce ARRAY /dev/md/2 > > > metadata=1.2 name=debian:2 > > > UUID=7c56166b:0d5aed8b:a9d03c45:e9b8080c > > > > That doesn't appear to be true. I have run the create which seemed > > to be ok, then mkfs -text4 /dev/md0, then mounted it at /home2. > > > > But /etc/mdadm/mdadm.conf doesn't yet have any of that, only this: > > You don't need to list the arrays in /etc/mdadm/mdadm.conf since > udev assembles arrays based on the metadata that exists on each > device. It's fine for there to be no ARRAY lines in there. These > days it's only really useful in recovery situations or for setting > some special options per array. > > You can still do the > > # mdadm --detail --scan > > to find the lines to put in the mdadm.conf yourself. > > > And again, I don't trust UUID's as moving a drive cable to a > > different socket has invalidated the whole lot of them once before. > > I would much rather LABEL the array, and mount it in /etc/fstab by > > that label. > > There may be some conceptual error here. The UUIDs you would put in > /etc/fstab are FILESYSTEM UUIDs, not array UUIDs. Lots of things in > computing have UUIDs. > > After you put a filesystem on each array you can refer to the > FILESYSTEM label in /etc/fstab. These labels are internal to each > filesystem and nothing to do with any layer below, such as md. > > > LABEL as I recall is a journalctl function? Does it work on > > raid10's? > > Filesystem labels have nothing to do with journalctl. And I don't > know what you mean by them being "a function". > > Again, filesystems (can) have labels, these are a filesystem detail, > RAID doesn't know nor care. > > > Humm, now: > > gene@coyote:~/AppImages$ sudo mdadm --detail --scan > > [sudo] password for gene: > > ARRAY /dev/md0 metadata=1.2 name=coyote:0 > > UUID=8ad67ef1:a14d63ab:c684ec2b:42a0c011 > > > > So I should add that last line to which category in mdadm.conf? > > mdamd.conf doesn't have categories. You would just append that line > at the end, ensuring it is all on one line. And I just found I didn't have an mdadm.conf, and I had figure a new -C would have created it. But the last time I ran it, no mdadm.conf was created. So I made a 2 liner from the --scan output. What else should it have? ARRAY /dev/md0 metadata=1.2 name=coyote:0 UUID=3d5a3621:c0e32c8a:e3f7ebb3:318edbfb ARRAY /dev/md1 metadata=1.2 name=coyote:1 UUID=ddb6ffa2:e068b701:f316cc5f:83938a13 You indicate that these are not the UUID's to put in fstab, or do I miss-understand? Experiment after putting those UUID's into fstab @coyote:etc$ mount /home2 mount: can't find UUID=3d5a3621:c0e32c8a:e3f7ebb3:318edbfb root@coyote:etc$ mount /snapshot mount: can't find UUID=ddb6ffa2:e068b701:f316cc5f:83938a13 root@coyote:etc$ mount /dev/md0 -text4 /home2 root@coyote:etc$ mount /dev/md1 -text4 /snapshot @coyote:etc$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 16380992 0 16380992 0% /dev tmpfs 3280240 95163270724 1% /run /dev/sda5 1857400436 317616932 1445362976 19% / tmpfs16401180 0 16401180 0% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs16401180 0 16401180 0% /sys/fs/cgroup /dev/sdb1 229699916 61472 217900640 1% /sdb /dev/sdc1 1921802432 879249728 944860648 49% /amandatapes /dev/sda347799020 6444388 38896828 15% /var /dev/sda1 944120188864 690080 22% /boot tmpfs 3280236 43280232 1% /run/user/1000 /dev/md0 1812963068 77852 1720721940 1% /home2 /dev/md1100203600 61464 95009032 1% /snapshot Which nicely demos why I don't trust UUID's. But, why didn't it work? Why did I have to revert to md0/md1 names to remount them? > > And for the time being use that UUID in /etc/fstab to mount it to > > /home2, right? > > No, because that is not a filesystem UUID. And you said you wanted > to mount the filesystem by label anyway. So put whatever label you > chose when you did mkfs (or when you did it from the installer). I didn't know mkfs
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 07:42:40 The Wanderer wrote: > apt-cache policy mdadm mdadm: Installed: 3.4-4+b1 Candidate: 3.4-4+b1 Version table: *** 3.4-4+b1 500 500 http://deb.debian.org/debian stretch/main amd64 Packages 100 /var/lib/dpkg/status I have another 1T SSD coming, and will remove sda and replace it as sda for a new debian 11.1 install, then put it back on an sdd cable to get my data back, so now I'm waiting for that drive to arrive. I'm tired of the new spinning rust and their volatile errors that go with SMR drives. They'd make good target practice for my new 6.5 creedmoor barrel. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 08:58:15 Andy Smith wrote: > On Sat, Nov 13, 2021 at 08:39:15AM -0500, Gene Heskett wrote: > > And I just found I didn't have an mdadm.conf, and I had figure a > > new -C would have created it. But the last time I ran it, no > > mdadm.conf was created. > > > > So I made a 2 liner from the --scan output. What else should it > > have? > > It can be empty or missing. So the answer to your question is, > "nothing". Mine have this: > > CREATE owner=root group=disk mode=0660 auto=yes > HOMEHOST > MAILADDR root > > "man mdadm.conf" should tell you what each of those things does. > > > ARRAY /dev/md0 metadata=1.2 name=coyote:0 > > UUID=3d5a3621:c0e32c8a:e3f7ebb3:318edbfb ARRAY /dev/md1 metadata=1.2 > > name=coyote:1 UUID=ddb6ffa2:e068b701:f316cc5f:83938a13 You indicate > > that these are not the UUID's to put in fstab, or do I > > miss-understand? > > You've clearly read the email you are replying to which said "array > UUIDs are not filesystem UUIDs and do not go in fstab", so I don't > know why you are asking the same thing again. > > Array UUIDs are not filesystem UUIDs and do not go in fstab. What is > unclear about this statement that you felt the need to do it anyway? > > > Experiment after putting those UUID's into fstab > > I still don't understand why, after reading me tell you that they > don't go in fstab, you then put them in fstab. > > > @coyote:etc$ mount /home2 > > mount: can't find UUID=3d5a3621:c0e32c8a:e3f7ebb3:318edbfb > > Guess what - if you put arbitrary nonsense in /etc/fstab, it won't > work. > > > root@coyote:etc$ mount /snapshot > > > > Which nicely demos why I don't trust UUID's. > > All you've demonstrated is that if you put garbage in your fstab > then it won't work. > > But no one cares whether you "trust UUIDs" or not. You already said > that you wanted to use fs labels, not UUIDs. Great. Do that then. I just did. Works. > > But, why didn't it work? > > I'm at a loss as to why you have to ask. You are replying to an > email that tells you not to put nonsense in your fstab, you then > show a transcript of you putting nonsense in your fstab, and then > ask why it didn't work. You even, further down, quote me telling you > not to put array UUIDs in your fstab. Is this performance art? > > > Why did I have to revert to md0/md1 names to remount them? > > 'cos given a choice between nonsense and a device node, mounting a > device node is more likely to work. So I've changed it. I guess the next question is why does --scan even report it if its no good? blkid returns different UUID's. Would those work? Generally moot now, I just umounted them, LABEL'd them with mkfs.ext4 -L and can mount by labels now. > > > > And for the time being use that UUID in /etc/fstab to mount it > > > > to /home2, right? > > > > > > No, because that is not a filesystem UUID. And you said you wanted > > > to mount the filesystem by label anyway. So put whatever label you > > > chose when you did mkfs (or when you did it from the installer). > > > > I didn't know mkfs can do labels. > > If only any of these tools had a man page. > > $ man mkfs.ext4 That is an alias to mkfs which covers all. > […] > >-L new-volume-label > Set the volume label for the filesystem to > new-volume-label. The maximum length of the volume label > is 16 bytes. > > Andy Thanks Andy. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 09:51:05 Andy Smith wrote: > On Sat, Nov 13, 2021 at 09:28:46AM -0500, Gene Heskett wrote: > > the next question is why does > > --scan even report it if its no good? blkid returns different > > UUID's. Would those work? > > Why are you under the impression that every single thing called a > UUID must work as a *filesystem* UUID? > > Lots of things have a UUID. Universally Unique IDentifiers are > useful things. But not every UUID is a filesystem UUID. This is like > taking the VIN from your car and putting it in fstab then asking why > it didn't mount your car as a filesystem. > > MD arrays aren't filesystems, they are block devices. > > "blkid" does report filesystem UUIDs, according to its manpage, so > the answer to that one is is yes. > > Andy I wouldn't argue near as loud if it hadn't already been proven to me that what you call filesystem UUID's are volatile. It happened when I moved a drive from sda to sdd several years ago. Getting ready to switch to the next version of debian because I always install to a new drive, which I installed wheezy on, then put the old drive back in on a different sata port to get my data copied to the new drive. No boot but single. It took me 3 days to build an fstab that mounted everything by Labels. When I finally had a working system again, I ran blkid again, and with the same drives except the boot drive re-arranged, every UUID blkid reported was different from what it was in the now commented out lines in fstab. The downside of now using mkfs to install a label, I didn't use it then but something else, but mkfs also wipes the drive, so in this case I hadn't moved anything to it, so I lost nothing reformating to install the label. The utility, if it wasn't journal-something or other I don't recall, but it could label a partition that already had content, without losing that data. rant on: That isn't moving forward in any field including computers. This stretch install uses UUID's to mount the system, and bullseye might also be left that way, but you can take it to the bank that anything associated with amanda is mounted by labels. Its simply too big a risk to do UUID mounts with something that important. I wrote a wrapper for amanda, and its data is several gigs that are also backed up after amanda is done. I can lose the boot drive, get in the pickup and go get a fresh one, put it in and re-install to bare metal, using a net-install dvd, get the amanda from the repo's and with amanda's backups, have this system restored to about 2:20 this morning in time to cook dinner. Computers were designed to work for you, not against you. This email, minus the typing I'm doing, will be sent with one click, and one more takes me to the next unread message. If I can answer, one more click selects a pm or list reply. Everything else is being done by scripts I wrote, because computers are supposed to work "for you", not "make work" for you. /rant off: Thanks Andy. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 11:41:00 David Wright wrote: > On Sat 13 Nov 2021 at 07:26:04 (-0500), Gene Heskett wrote: > > My mdadm manpage does not show the -S command. Scanniing it again to > > make sure, probably for about the 10th time and I finally found it > > but many megabytes of relatively unimportant drivel down from the > > top, IMO the manpage is missleading as such an important option > > ought to be shown on the first screenfull. > > You could sponsor it—just reply to one of those junk emails, > "Get top page ranking!" Sure, and its a good thing these jerks can't be located, as I know where an old mine cache is, with several 1 cup containers of 75 yo nitro that ought to be really unstable by now in it. Probably someones sick idea for darwin award bait. I would have spoiled their fun by backing off a couple hundred meters and seeing what effect an Ackley-06 rattling around inside it had, but it looked like I might be ducking a 200lb steel door if I did. So I walked off and went back to deer hunting. Safer. > Serously, you need only type /\-S into less, if you set it as > your manpage viewer, export MANOPT="-P less" > > I would make one small criticism of some manpages; for example: > chmod has its arguments documented in running text, whereas a > table would be much easier to scan: > > A combination of the letters ugoa controls which users' access > to the file will be changed: > u the user who owns it, > g other users in the file's group, > o other users not in the file's group, > a all users. > none the effect is as if (a) were given, but bits > that are set in the umask are not affected. > > compared with: > > A combination of the letters ugoa controls which users' > access to the file will be changed: the user who owns > it (u), other users in the file's group (g), other > users not in the file's group (o), or all users (a). > If none of these are given, the effect is as if (a) > were given, but bits that are set in the umask are not > affected. > > Cheers, > David. Plus 100 or more, David. That wall of text has confused me since red hat 5.0 in 1998. Soon to be 25 years. This has been a linux only house for that long. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 15:44:35 Andy Smith wrote: > On Sat, Nov 13, 2021 at 01:14:56PM -0500, Gene Heskett wrote: > > I wouldn't argue near as loud if it hadn't already been proven to me > > that what you call filesystem UUID's are volatile. > > What I and everyone else call filesystem UUIDs do not change unless > you force them to change, because they only exist inside the > filesystem. It seems far more likely that you are confused, in the > same way you have been confused throughout this whole thread. If > you've got something outside of your control scribbling in your > filesystems then that is a very serious bug. > > I think you are and have been confused between different things that > have UUIDs. Filesystems, MD arrays, GPT partitions and lots of other > things all can have UUIDs. > > In this thread you have repeatedly shown that you don't understand > the difference between those UUIDs and have tried to use them in > your fstab, so it seems far more likely that any prior issue you > have had with filesystem UUIDs is going to be down to similar > confusions and not some serious bug. > > > It happened when I moved a drive from sda to sdd several years > > ago. > > Barring some strange bug that only you have ever seen, it is not > possible, so I believe you are mistaken. This is going to be > another one of those things where you swear software behaved in > incredibly improbable ways, you are asked to reproduce it and can't. > I will gladly eat humble pie if you can reproduce this one and show > us. I will be excited for the bug report we can make together, > because that would be a real doozy. > > Like that time you said that having an IPv6 address configured > prevented you from compiling some software, a claim you kept > repeating in multiple unrelated threads any time IPv6 was mentioned, > until you were asked to reproduce the issue and couldn't. > > We all make mistakes from time to time but filling the archives with > bold assertions like "filesystem UUIDs are volatile" I think would > come under the category of an extraordinary claim that would require > extraordinary proof. > > > Getting ready to switch to the next version of debian because I > > always install to a new drive, which I installed wheezy on, then > > put the old drive back in on a different sata port to get my data > > copied to the new drive. No boot but single. It took me 3 days to > > build an fstab that mounted everything by Labels. When I finally > > had a working system again, I ran blkid again, and with the same > > drives except the boot drive re-arranged, every UUID blkid > > reported was different from what it was in the now commented out > > lines in fstab. > > "blkid" also reports things called PARTUUIDs, so I think this is > explained by it doing that, and you being confused. Nothing you have > described could cause a filesystem UUID to change. > > > The downside of now using mkfs to install a label, I didn't use it > > then but something else, but mkfs also wipes the drive, so in this > > case I hadn't moved anything to it, so I lost nothing reformating to > > install the label. The utility, if it wasn't journal-something or > > other I don't recall, but it could label a partition that already > > had content, without losing that data. > > You have not once in this thread asked how to label an existing > filesystem without re-creating it. Although you don't even need to > ask us, because: > > https://lmgtfy.app/?q=how+do+I+label+an+ext4+filesystem > > So instead of doing a trivial search, or even asking, you just > assume that it can't be done and have a nice old rant. Weird flex, > but OK. > > The above is for ext* filesystems; other filesystems have their own > tools for changing the label. A similar search will find them, too. > > People have been putting and changing labels on filesystem in Linux > for decades. It's well understood and well documented. If you look. > First you complain that fs UUIDs are volatile, now you complain that > fs labelling is hard without even doing the most basic research. At > least these topics have been adequately covered, so unwary searchers > are unlikely to stumble upon this thread in future and be led down a > very long garden path by the bizarre claims within. > > > Its simply too big a risk to do UUID mounts with something that > > important. > > For you, maybe, but I guarantee this is down to some confusion on > your part. Confusion is still a valid reason to shy away from > something, especially when there is an alternate approach (mount b
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 18:37:34 Greg Wooledge wrote: > On Sat, Nov 13, 2021 at 04:06:43PM -0700, Charles Curley wrote: > > On Sat, 13 Nov 2021 16:57:01 -0500 > > > > Gene Heskett wrote: > > > So which of these various UUID's is actually valid in an fstab > > > > Thanks, Andy. This is nice to know about. > > > > Gene, the answer is, anythng the TYPE of which is a valid file > > system. Try, e.g.: > > > > blkid | grep -E -i \(ext\|ntfs\|fat\) > > lsblk is a lot easier and prettier for this purpose. > > unicorn:~$ sudo lsblk -o +UUID > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID > sda 8:00 931.5G 0 disk > ├─sda1 8:10 260M 0 part /boot/efi 4C30-7972 > ├─sda2 8:2016M 0 part > ├─sda3 8:30 92.2G 0 part7294B93794B8FEA3 > ├─sda4 8:40 980M 0 part609E71C79E71966E > ├─sda5 8:50 11.5G 0 part6858F6A458F66FE4 > ├─sda6 8:60 11.2G 0 part [SWAP] > 08c87bdb-17f4-40ab-9b2f-5cb2f29149fb ├─sda7 8:70 23.3G 0 part > / c4691ccb-2090-491e-8e82-d7cc822db04a ├─sda8 8:80 > 23.3G 0 part /home 19fb397b-a113-4536-a03d-d60e176cbfdf └─sda9 > 8:90 651.9G 0 part /stuff > 95058c4a-44e2-4a90-87b5-2a5fe40d3cdb sr0 11:01 418.7M 0 rom Is not me thats confused but both lsblk and blkid spitting out 4 sets of identical UUID's as all drives are identical. Example: root@coyote:etc$ lsblk -o +UUID NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID sda 8:00 1.8T 0 disk ├─sda18:10 953M 0 part /boot 06aa3215-a6a6-4fbb-86ca-186c47e1334c ├─sda28:20 14.9G 0 part [SWAP] 8b675a91-5aa5-401b-bf50-d8afc3e8115a ├─sda38:30 46.6G 0 part /var ee491e5c-7394-434f-b50a-f4354f6c9869 ├─sda48:40 1K 0 part └─sda58:50 1.8T 0 part / 0e698024-1cf3-4dbc-812d-10552c01caab sdb 8:16 0 223.6G 0 disk └─sdb18:17 0 223.6G 0 part /sdb 4982ee4c-58c4-4d2b-b9d5-69344c3cb090 sdc 8:32 0 1.8T 0 disk └─sdc18:33 0 1.8T 0 part /amandatapes 3b6848c1-7b09-43be-a7aa-ae63d82f5f26 sde 8:64 0 931.5G 0 disk ├─sde18:65 0 878.9G 0 part 3d5a3621-c0e3-2c8a-e3f7-ebb3318edbfb │ └─md0 9:00 1.7T 0 raid10 /home2 708320b3-10af-4c15-b5b1-a9ff7be06d99 └─sde28:66 0 48.8G 0 part ddb6ffa2-e068-b701-f316-cc5f83938a13 └─md1 9:10 97.6G 0 raid10 /snapshot 733718b2-e7f8-4b00-a390-264e5c73c453 sdf 8:80 0 931.5G 0 disk ├─sdf18:81 0 878.9G 0 part 3d5a3621-c0e3-2c8a-e3f7-ebb3318edbfb │ └─md0 9:00 1.7T 0 raid10 /home2 708320b3-10af-4c15-b5b1-a9ff7be06d99 └─sdf28:82 0 48.8G 0 part ddb6ffa2-e068-b701-f316-cc5f83938a13 └─md1 9:10 97.6G 0 raid10 /snapshot 733718b2-e7f8-4b00-a390-264e5c73c453 sdg 8:96 0 931.5G 0 disk ├─sdg18:97 0 878.9G 0 part 3d5a3621-c0e3-2c8a-e3f7-ebb3318edbfb │ └─md0 9:00 1.7T 0 raid10 /home2 708320b3-10af-4c15-b5b1-a9ff7be06d99 └─sdg28:98 0 48.8G 0 part ddb6ffa2-e068-b701-f316-cc5f83938a13 └─md1 9:10 97.6G 0 raid10 /snapshot 733718b2-e7f8-4b00-a390-264e5c73c453 sdh 8:112 0 931.5G 0 disk ├─sdh18:113 0 878.9G 0 part 3d5a3621-c0e3-2c8a-e3f7-ebb3318edbfb │ └─md0 9:00 1.7T 0 raid10 /home2 708320b3-10af-4c15-b5b1-a9ff7be06d99 └─sdh28:114 0 48.8G 0 part ddb6ffa2-e068-b701-f316-cc5f83938a13 └─md1 9:10 97.6G 0 raid10 /snapshot 733718b2-e7f8-4b00-a390-264e5c73c453 sr0 11:01 1024M 0 rom So we are talking at cross purposes here as this did not answer my question well enough to make it work on the first try. I'll use labels, /home2 and /snapshot, thank you. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Where do I find the definitive man page for mdadm?
On Saturday 13 November 2021 22:37:19 Tom Dial wrote: > On 11/13/21 14:57, Gene Heskett wrote: [...] > >>> It happened when I moved a drive from sda to sdd several years > >>> ago. > >> > >> Barring some strange bug that only you have ever seen, it is not > >> possible, so I believe you are mistaken. This is going to be > >> another one of those things where you swear software behaved in > >> incredibly improbable ways, you are asked to reproduce it and > >> can't. I will gladly eat humble pie if you can reproduce this one > >> and show us. I will be excited for the bug report we can make > >> together, because that would be a real doozy. > >> > >> Like that time you said that having an IPv6 address configured > >> prevented you from compiling some software, a claim you kept > >> repeating in multiple unrelated threads any time IPv6 was > >> mentioned, until you were asked to reproduce the issue and > >> couldn't. That I found. Getting rid of avahi and its git fixed that right up. I think in the intervening years, its gotten some TLC because its not been a problem since wheezy. The problem was that it was assigning an ipv6 route to a system 200 miles from the nearest ipv6 socket. > >> We all make mistakes from time to time but filling the archives > >> with bold assertions like "filesystem UUIDs are volatile" I think > >> would come under the category of an extraordinary claim that would > >> require extraordinary proof. > >> > >>> Getting ready to switch to the next version of debian because I > >>> always install to a new drive, which I installed wheezy on, then > >>> put the old drive back in on a different sata port to get my > >>> data copied to the new drive. No boot but single. It took me 3 > >>> days to build an fstab that mounted everything by Labels. When I > >>> finally had a working system again, I ran blkid again, and with > >>> the same drives except the boot drive re-arranged, every UUID > >>> blkid reported was different from what it was in the now > >>> commented out lines in fstab. > >> > >> "blkid" also reports things called PARTUUIDs, so I think this is > >> explained by it doing that, and you being confused. Nothing you > >> have described could cause a filesystem UUID to change. > >> > >>> The downside of now using mkfs to install a label, I didn't use > >>> it then but something else, but mkfs also wipes the drive, so in > >>> this case I hadn't moved anything to it, so I lost nothing > >>> reformating to install the label. The utility, if it wasn't > >>> journal-something or other I don't recall, but it could label a > >>> partition that already had content, without losing that data. > >> > >> You have not once in this thread asked how to label an existing > >> filesystem without re-creating it. Although you don't even need to > >> ask us, because: > >> > >> https://lmgtfy.app/?q=how+do+I+label+an+ext4+filesystem > >> > >> So instead of doing a trivial search, or even asking, you just > >> assume that it can't be done and have a nice old rant. Weird flex, > >> but OK. > >> > >> The above is for ext* filesystems; other filesystems have their > >> own tools for changing the label. A similar search will find them, > >> too. > >> > >> People have been putting and changing labels on filesystem in > >> Linux for decades. It's well understood and well documented. If you > >> look. First you complain that fs UUIDs are volatile, now you > >> complain that fs labelling is hard without even doing the most > >> basic research. At least these topics have been adequately covered, > >> so unwary searchers are unlikely to stumble upon this thread in > >> future and be led down a very long garden path by the bizarre > >> claims within. > >> > >>> Its simply too big a risk to do UUID mounts with something that > >>> important. > >> > >> For you, maybe, but I guarantee this is down to some confusion on > >> your part. Confusion is still a valid reason to shy away from > >> something, especially when there is an alternate approach (mount > >> by label) that works much better for you, but blaming it on > >> mysteriously changing UUIDs and/or the mdadm man pages is not > >> helping. > >> > >> Andy > &
Re: Fwd: lists.debian.org has received bounces from you
On Wednesday 24 November 2021 13:08:19 Nicholas Geovanis wrote: > Top posting necessarily. > Folks have discussed list bounces like this one in this forum already. > I would like to draw the administrators' attention to > bendel.debian.org, as shown here. I can't see enough to diagnose it as > false positive or problem. Thanks The mail server at your ISP is bouncing it, call tech and have them whitelist bendel.debian.org. That doesn't mean they don't send spam, cuz they do occasionally, but at least it won't send you threatening msgs to ignore. You'll then get the spam but spamassassin can handle that. > -- Forwarded message - > From: Debian Listmaster Team > Date: Wed, Nov 24, 2021, 10:45 AM > Subject: lists.debian.org has received bounces from you > To: > > > Dear subscriber, > > We've encountered some problems while sending listmail to your > emailaddress nickgeova...@gmail.com. > > In the last seven days we've seen bounces for the following list: > * debian-user > 1 bounce out of 149 mails in 7 days (0%, kick-score is 80%) > (https://lists.debian.org/bounces/u9lHbXYWgI1VcxqPZbbglg) > > (The link above points to a copy of the latest bounce > and will be valid for seven days.) > > If the bounce-rate passes the kick-score, our bounce-detection will > forcibly remove your subscription. > > Bounces happen from time to time when spam slips through our filters > but are rejected by your mail provider. If you are your own mail > provider and use 'Before-Queue Content filtering', you should > whitelist bendel.debian.org from > Content filtering. > > However: You can safely ignore this message (and you will not be > unsubscribed > > :-) ) if your bounce rate remains low. > > For more information see https://wiki.debian.org/Teams/ListMaster/FAQ > > You are welcome to contact listmas...@lists.debian.org if you think > this message was sent in error. > > Sincerely, > The Listmaster Team Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
new buster install, dvd said 11.,1 but installed 10.1
Plz excuse the foul attitude, one of seagates finest 2T drives ate its own lunch friday and I'm on web mail. Lost everything but I have backups I cannot access. apt/synaptic will not let me install any of Trinity, claims I have held broken packages it refuses to name. and synaptics fix-broken does nothing. so I'm locked out of my normal email, and the repo version of amanda keeps telling me I can't recover a perfectly good backup because /bin/tar is not secure. WTH? Where do I start on a new buster net install? The backups are all from stretch. All I want is the data. So how do make /bin/tar usable/secure? Thanks all. Cheers, Gene Heskett
filesystem I'd?
Whats the name of the filesystem used on 64G micro-sd's labeled SDXC ? Thanks all.
