Subj : Re: Miss.RvrDamBreach-Davenpt To : Barry Martin From : Nancy Backus Date : Tue Sep 03 2019 17:17:42 -=> Quoting Barry Martin to Nancy Backus on 29-Aug-2019 19:32 <=- NB>>> And now soon to return, to find your deluge to answer.... ;) BM>> The good news is I did break up the replies into smaller BM>> chunks, mainly to not potentially overload my side, but also good BM>> stopping points. NB>> When I got back, I did tailor my packets a little... I was able to NB>> put the echoes from Tiny's that I would have messages in to reply to NB>> into one packet, and all the rest into another one... made the one NB>> to answer a little more wieldy than it would have been otherwise... NB>> Of course, I wasn't gone for a month.... :) BM> No, just a fraction of a month. :) Make that fractionS of a month... BM> It was easier for me to download all and work on it a little at a BM> time. Pretty sure I have a maximum packet size set somewhere -- has BM> been a while since fiddled with those settings. I'm sure I have maximum packet size set on each of the bbses, but generally what would work best for actually reading/answering them is much smaller than that default... It's way too easy to overwhelm this computer with a huge packet... It needs more than double (maybe triple?) the space to open it, and more headspace to close it again... And I tend to not really have a lot of room available at a time... NB>>> It's been bad enough for me that I was away for about 3 weeks out NB>>> of 5 (from June 14 to July 20)... close to being caught up now, NB>>> admittedly I've not rushed on these replies to you... but pretty NB>>> current otherwise at the moment... and then a couple weeks still NB>>> before I'm off again... BM>> As I said sometime before, the REPs should be a pleasurable option, BM>> not a dutiful requirement. NB>> Oh, they are... and that's also why I don't get myself stressed out NB>> when it takes a while to plod thru them all... ;) If I get the last NB>> 6 to you from this packet answered tonight, I'll be able to tuck this NB>> packet away... and continue on to the ones that are more recent... :) BM> Yup: seemed a little funny to read of 4th of July in the earlier BM> message with Labor Day coming up in a few days. Really stretched out threads.... NB>>>> Works out as a good thing for both of you.... :) BM>>> Yes, that's what I figure. In one way I get the better of the deal BM>>> because he's customizing the instructions for what I have here. And BM>>> he gets to test his utility on a live and 'raw' system and make BM>>> corrections/comments. LIS, I've needed to install a few utility BM>>> files. he's needed to make permissions/file ownership alterations. NB>>> He'll have a more robust piece of software, you'll have a nice NB>>> working utility.... :) BM>> True, though on my end the utility is a one-function one: the source BM>> and destination, file locations, etc., are hard-coded into the BM>> software, though I think written in Python so would just need to use a BM>> text editor to update. I only vaguely understand so at this point BM>> easier to leave all corrections up to him -- plus if I make a change BM>> isn't in the 'master' for eventual distribution. NB>> One-function utilities aren't all that bad a thing... as long as NB>> they perform a function that you need to have done.... :) BM> Yes, though for this utility it would seem to make more sense to have BM> a configuration while the user would edit instead of editing the actual BM> programme file. Essentially the same as the configuration file BM> modifies the programme file, just I prefer not fiddling with the BM> master. Maybe you should suggest that to him.... or do the actual work with an iteration of the program, not the original one...? BM>>> The good news is I think we're about ready to do the full transfer of BM>>> TV show files from the old system to the new. (Yea!!) Waiting for BM>>> the system to be available currently (the export/import process will BM>>> pause itself when a show is being recorded so as to not 'overflow' the BM>>> read/write channels and cause corruption). NB>>> Sounds promising... :) BM>> I'll admit to being amazed at the details, forethought, etc. Possibly BM>> due to 'oh poop!' events that happened years ago when he first started BM>> creating this set of utilities , but still. NB>> Good that he is able to figure it all out... :) BM> LIS I think he's one of the developers though never stated anywhere BM> and didn't make any difference - he knew the stuff was what mattered. Yup, either way, he's developing it now, too... and knows what's going on with it... ;) BM> BTW, the transferred files (from old system to new) work fine. The BM> old Backend has been powered off for some time -- maybe only a week but BM> seems longer! Still have to move the hardware around -- the new BM> Backend is still on the floor and needs to be moved to the cabinet, but BM> first need to make room on/in the cabinet.... Eventually... ;) BM>> And it does work: just before I left I done some testing with larger BM>> chunks: move over all shows from Channel 8_3, for instance. (The file BM>> names have the channel included.) Couple of 'specific channel' tests, BM>> passed. Got 'brave' and tried copying over the remainder: only real BM>> difference was instead of a batch of maybe twenty or thirty files was BM>> over a hundred files. Passed. :) NB>> Hurrah for that! And no doubt a major relief when it did pass... ;) BM> Yes. There's always the "it works on x-system but will it work on BM> y-system?". He has (IIRC) 12 TB of storage, I 'only' 4 TB. And both BM> of those numbers are 'wrong' as we really need to be looking at free BM> space. For a short while I was using about half, so 2 TB. And the way BM> the transfer utility worked is it only bit off small chunks: a single BM> TV programme at a time, so usually no more than 2 GB; select, process, BM> move over; select, process, move over.... You have WAY more capacity than I have... ;) But the important thing is that you do have what you need to do the job at hand.... :) BM>> I didn't have time to update the hardware: update the Frontends BM>> (viewing computers) to the current Ubuntu (18.04.3) and the MythTV BM>> utility so left alone. Good news for our testing is Backend 2 (the BM>> old/original computer doing the recording and storage) is still BM>> recording shows and so can be used for our final testing. NB>> Very useful... :) So, have you done that final testing yet, and NB>> updated the hardware...? BM> Yup! :) One had to have semi-major surgery: knew the power supply BM> needed replacing as the fan froze some time back -- held off replacing BM> as 'inconvenient' plus the major system change. Did put in the new BM> PSU, checked, swapped the HDD for SSD (hard drive for a solid state BM> one) -- now boots in around thirty seconds. That one is in the Ironing BM> Room in the basement. All right... :) NIce when things work properly... :) BM> Will see about replacing the fan in the old PSU instead of buying a BM> whole new PSU. Makes sense... and with it out of the computer, twill be easier to work with... ;) BM>> And I was surprised when the car started right up after my appointment. BM>> Was either still raining or had just stopped, forgot. Probably the BM>> heat of the engine and gravity pulling the splashed water down cleaned BM>> the wires and removed the short. And did have the car checked and the BM>> spark plug harness needed replacing: cracked insulation. NB>> Which probably had been there before your forced puddle-drive... NB>> ;) Just as well to find it sooner than later, when it might have NB>> given you more grief... :) BM> Right. I recall I left things for a while. Had a foggy period and BM> the car didn't like that because of the moisture getting in to the BM> cracks so that's when had the wiring harness replaced. So you probably would have found it sooner or later... this way at least you were warned to watch out for it... ;) ttyl neb .... I have seen the evidence. I want DIFFERENT evidence... --- EzyBlueWave V3.00 01FB001F * Origin: Tiny's BBS - http://www.tinysbbs.com (454:1/452) .