Anonymous
noClue, (not that you would advocate using it but) you know the commandline “locate” command, right?
When I booted slackware-derived Porteus Linux and discovered absence of that command, I was stymied.
I had believed its inclusion was a “universal standard” among linux distros.
Whelp, I learned it is not universally exposed as (or aliased as) “locate”.
On some systems it (or its packagename) is “slocate”, instead. On other systems, it is “mlocate”.
In any event, I never considered going to the Porteus forum and playing provocateur, ala
“Reeeeee! Y’all are insaaaaane! So stooooopid! Caught in the past…”
interspersed, bipolar-like, with “lookit. It’s so easy. I gonna teach you…” tutorials.
Yep, I too am attentive toward achieving ‘sane more ideal’ defaults. Over in the antiX19 alpha topic, I groused about a couple details. However, I realized it would be counterproductive, if not outright disruptive, to repeatedly harp about those same details even though they are important to me. Hopefully you can see the mirror, and aren’t still unsure whether you’re in the country.
ps: I now further realize “there’s a GNU findutils-packaged locate command” and a separate,
same-named “we don’t need no stinkin’ GNU” locate command from nognu.org, and…
pps (or call it a FYI):
For many of the PuppyLinux variants, the locate command is absent, period. Full stop.
After quite some searching (web-wide, b/c “locate” has seldom been mentioned in pupplinux forum ~~ few
people seem to even notice its absence) you can discover a “slocate” pkg is available for Slacko
and someone has packaged “mlocate” for use on bizzybox-only puppy systems.