lspci-3.4.0 for Puppies

[musher0]

Hello all.

Please find at the URL below a *.pet archive of the latest pciutils, pciutils-3.4.0.
~~~~~~~~~~~
-- https://www.adrive.com/public/75eUQm/pciutils-3.4.0.pet --
~~~~~~~~~~~

Why this pet? I realized Puppies might not have as many tools as other
distros to probe the ids of your computer's PCI's. < lscpi > is mentioned
in a lot of places on the web as a tool to inspect your computer's PCI's,
but it's not in Puppies by default. So here you go.

"If there is a genuine need, it will be met." (American author Henry
Miller, somewhere in "Big Sur and the Oranges of Hieronymus Bosch")

Another tool you might consider for this is inxi,
-- https://github.com/smxi/inxi --,
which is more complete since it can also probe the CPU, the kernel and
a couple of other things.

I compiled these "pciutils" to go in /usr instead of /usr/local. Aside from
that, a very "default" compilation. Compiled in upupRaring-3.9.9.2 from the source obtained at the URL indicated above, which is the developer's
site.

In the hope that this may be useful to some.

Have a great week-end!

musher0

[B.K. Johnson]

@musher0
The following phrase from your post caught my eye.

I compiled these "pciutils" to go in /usr instead of /usr/local.

The tone makes it seems the placement is arbitrary and non-standard, but you offer no explanation for the location you select. If /usr/local is the "correct" or standard place, then I daresay an explanation is necessary if placed elsewhere.

If there is one thing I hate about Linux it is the unpredictability of where developers place programs and the inevitable rats nest of symlinks?

[musher0]

Oh.

Sorry if I caused any anxiety or anger.

Well, in Puppy Linux, as I understand it, /usr/local/bin is reserved for "local" apps
and utilities, meaning: they are specific to Puppy, such as the series of default*
launchers you find there, or apps and utilities chosen by the user.

Again, -- as I understand it and my understaning of it could be wrong --, really core
utilities such as busybox and awk go in /bin. The utilities that are not core and not
Puppy- or user-pecific go in /usr/bin.

Other distros give a different meaning to "local", as in "if it didn't come with the
distro iso, it goes in /usr/local/bin".

To be frank, I hesitated between putting lscpi & Co. in /bin and /usr/bin because I
feel that these cpi utilities are core utilities similar in importance to the GNU coreutils.

I hope this is helpful. BFN.

musher0

[B.K. Johnson]

musher0 wrote:

Sorry if I caused any anxiety or anger.

You neither caused anxiety nor anger; my post was not intended to convey either.

Other distros give a different meaning to "local", as in "if it didn't come with the distro iso, it goes in /usr/local/bin".

Puppy Linux, as I understand it, /usr/local/bin is reserved for "local" apps
and utilities, meaning: they are specific to Puppy

I don't see any essential difference between these.

I feel that these cpi utilities are core utilities [unstated but inferred and therefore, should be put in /usr/bin or /bin]

Well, here we differ. IMHO, it is the puppy developer who determines the core utils, not the user. Therefore, in view of my take on core utils and finding no meaningful difference between the particular puppyism and what other distros do, I would have placed it in /usr/local/bin.

But worry not my Canadian friend from the lovely Gatineas of Quebec, it's just my opinion.

[musher0]

Hello, B. K. Johnson.

Live and learn, eh? Thanks for contributing to my Linux education. However,
being a practical man more than a Linux theoretician or purist, I'm happy
that any executable works from any "/bin" directory in the $PATH.

Anyway, here is a screen cap of what lscpi does and the URL of its man page.

I hope that will help our Puppyists discover more easily some of the
hardware supporting their Puppy.

BFN.

musher0