Subj : Re: Too many? :) To : Barry Martin From : Ky Moffet Date : Tue Sep 29 2020 21:57:00 BARRY MARTIN wrote: > Hi Ky! > > > Yes, didn't know there were so many variations out there! > KM> Since I've been paying attention it's mushroomed, tho most fade > KM> away unremarked and unlamented. > > Yes, I suppose rather easy as modify to my preferences, I think it's the > latest and greatest so publish. A few people, mostly relatives and > friends trying to be supportive try it but otherwise doesn't take off, Or the maintainer and his immediate cronies. I'd feel more secure if my preferred distro was more than a one-man-band, because that's a single point of potential disaster; OTOH everything is very stable because Tex doesn't change things up much. No sudden corporate 180s. > KM> There used to be a catalog of all the Puppy variants... over > KM> 2000!! > > That number seems like more than the number of actual dog breeds! Which would be about 300, depending how you count 'em. My fave is MintPup, tho technically it's a DebianDog spin; unfortunately not maintained. I sometimes use Wary as an old-hardware boot disk. > > As for the listing, I was thinking a separate file, not a tree output. > KM> Oh, but the Tree output tells me where it is on disk... occurs to > KM> me, tho (this is your fault) that I could print out the Big > KM> Family Tree (how much paper, again?) and mark the branches I've > KM> tried... nah, sounds like work. > > If you use a teen-tiny you should get it to fit on a single sheet! If I used little teeny print I'd need little teeny eyes to read it... https://people.well.com/user/bubbles/LilTEyes.txt > As for marking, maybe could still do it on computer: create a file with > a name forcing it to the top/beginning of the tree branch list. I've > used "aa_" if I want a force a file's location. Thinking of the > Recipes subdir I have (and honestly intended to use!): At least on Windows you can use ! or !! or !!! to force a front sort. This does not work on linux, which ignores the leading ! mark. > /home/barry/File Cabinet/Recipes/ > |-- aa_Cooking Tips > |-- aa_Food Timeline > | |-- Food Timeline: food history research service_files Food timeline, fish: Fresh, Stale, and Stinking in 3 days. > Prefacing the 'aa_' forces the Cooking Tips subdir towards the top. > You'll have to test how it works with numbers, if any listing has > numbers, or even non alphanumeric characters I've done the opposite -- prefix with zzz_ to force it to the end. > KM> Or in this case, vanished from the various FTPs, probably cuz Tex > KM> (or whoever does this for him) did one of his periodic trawls to > KM> get rid of outdated editions. Which I disagree with, see above. > > In the old days storage space was at a premium so the culling sort of > made sense. Now, not so much, so just move to that Old Stuff directory. Yeah... that's why it irks me so much that Microsoft nuked all the old support files. They've done this twice now, apparently under the theory that this would force people to upgrade. No, it just annoys us... when they announced that they were killing the pre-XP files, I pulled all of 'em, and it was only 8GB. They didn't announce it when they killed most of the XP support files. :/ > > KM> In this case ... someone had done a nice implementation of > KM> Cinnamon on PCLOS, and seemed like it would make a good regular > KM> spin... recommended it to our Spin Doctor for updating, but then > KM> no one could find a copy online. > > Darn misspellings! (Y'mean it's not 'Sinahmum'?) Haha... I found it somewhere weird but the archive later disappeared. > > KM> I have dozens, perhaps hundreds of directories named Stuff... or > > KM> sometimes !Stuff... sometimes both.... > > I try to be a little more descriptive but doesn't always work. I do > > have a few variations on 'temporary'! > KM> That too!! > > Let's see: > > Temporary > |-- A lot of Stuff > |-- More stuff > |-- Other stuff That! > > Oo! Linux is case-sensitive!! > > Temporary > |-- a lot of stuff > |-- a lot of Stuff > |-- more stuff > |-- More stuff > |-- More Stuff OMFG... yeah, that!! Tho I try to avoid the case-sensitive thing because do not wish to make a mess when interacting with Windows. (Win10 is also case-sensitive.) > > The backs of which can be used for scratch paper! > KM> Too late, I printed it on scratch paper (Wound up wishing I > KM> had more scribble space!) > > Scotch tape pieces of smaller scratch paper to the original large sheet > of scratch paper! (Back in my college days, way before home computers > were common, I did a term paper, editing with the literal cut and paste: > the draft was very lumpy.) Oh yeah, been there, done that... whilst constructing first novel from 56 originally-unrelated scenes in the era of typewriter. > > KM> Yes! this is where I rebooted my brain!! > > Things really got equalized! > KM> BEEP BEEP > > You're either backing up or if you're AMI havign a memory parity check > error! That would explain much. > Back a couple years ago I noticed it seemed when LibreOffice and Mozilla > stuff was being updated they actually downloaded the entire version > rathet than just the new files. Possibly everything as changed, though > more likely to ensure no old files to screw up the works. Partly because integrity checks get upset when body parts don't match. > KM> Nothing wrong with this hardware; it runs a dozen other OSs just > KM> fine. Windows is a pretty good canary in the coal mine for bad > KM> hardware, and it loves that PC. Also moved the install to an > KM> older and more generic PC... no change. > > Some sort of sneaky incompatibility. ...You got "ARM" instead of "AMD". > It's 64-bit instead of 32-bit (should have a warning message). LOL, yes, I've suddenly downgraded to ARM > nomodeset came to mind because when I was having troubles with the > installation due to the faulty RAM it came up numerous times as a > potential work-around; a few days ago in the MythTV Forum with nVidia > drivers. Oh. Fortunately not my problem. > KM> Only thing I can think might be similar -- having trouble with > KM> 64GB RAM. However... the Red Hat family (broadly including the > KM> Mandrake cousins) has no problem with it, and that should be a > KM> kernel function anyway, and it's not like the kernel is that > KM> different from one version to the next ... and a given kernel is > KM> the same across distros. And if Debian with its 3 year old kernel > KM> has no trouble with 64GB, then no distro using a newer kernel > KM> (everyone else) should either. > > Vague stuff coming up. With MotionEye there are two main versions: > MotionEyeOS and MotionEye -- the first is more or less a self-entity and > what I'm using here. The second is a utility, added on to an OS like > Raspbian. I tried the utility a year or two back and didn't have any Raspbian is still 32bit, IIRC. > luck so went back to the OS version. So by using the MotionEyeOS > version there could be some old code not working properly past 32GB. Which might be explained by the above. > OTOH it seems to work fine for some people - maybe I'm missing a command > switch? Wait for next generation hardware. > FWIW Ubuntu has a bare-bones option. I think the ISO is the same, just > select a 'minimal' option instead of 'full'. I've not tried it even > though on some computers which are essentially dedicated Frontends (to > MythTV) it could make sense. Invariably I'd eventually need whatever > was missing. Yeah, most of 'em do. In my experience they're not just barebones, but also lots of everyday stuff doesn't quite work. Inability to configure the desktop is no worry for a server, but annoying for a workstation. Another reason I don't bother looking at barebones distros, unless that's all there is. > KM> Yeah, to deal with all that you need a stable of programmers... > KM> at the distro level, tho, it's really just putting it all > KM> together with a script; all the real programming has already been > KM> done, especially at the hardware level (drivers etc.) > KM> In fact OpenSuSE used to have an automated online "factory" where > KM> you could specify whatever you wanted (built on OpenSuSE, but > KM> with a wide choice of desktops and features) and it would spit > KM> out a custom distro ISO for your personal entertainment. I had it > KM> build a version with Trinity desktop, tho it didn't turn out as > KM> well as Trinity on PCLOS. But still, shows at that level it's > KM> just scripts. > > My guess is it's similar to a OEM installation: created specifically for > (say) HP and they only use certain AMD or Intel CPUs, so don't have to > include (nor test for) all the others. Same for the video card and > probably a bunch of other motherboard variables. (Remember my level of > understanding isn't nearly as in-depth as yours on this stuff! My > 'Black Boxes' are giant!) Occurred to me that why Debian's installer is so freakin' slow might be because it's still doing a lot of building from source AS it installs (I gather Slackware and Gentoo still do this for the whole install). Just guessing but can't think of anything else that would take so durn long. Which in this day and age is just insane. Yeah, you get an end result precisely tailored, but at the cost of a lot more time and bother, especially when 99% of installs want to wind up with the ordinary generic one-size-fits-all binary, so why individually build it? > > .. Picked up book called "Glue in Many Lands"; can't put it down. > KM> Sticky situation! > > I am rather attached! To what?? > .. Famous Last Words: Everything seems to be working fine now. Barry's USB. þ RNET 2.10U: ILink: Techware BBS þ Hollywood, Ca þ www.techware2k.com --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .