[Solved] pciutils.tcz vs pci-utils and usbutils vs usb-utils and x86 vs x86_64

[Leee]

Over the years, I've installed Tiny Core (or, really, just Core) on a bunch of computers and have configured a bunch of bootable USB sticks with Core as well.  I often find myself, sans GUI, using tce-load to pull down those first few extensions or creating onboot.lst by hand and it has vexed me, for over a decade, that I can never seem to remember, "Is it pci-utils.tcz or pciutils.tcz" and "Is it usb-utils.tcz or usbutils.tcz?"

Lately, I've been putting together a script to partially automate the process of updating from 13.1/x86_64 to 14.0/(both x86_64 and x86).  Understand that, for me, "updating" really means a fresh install along side the original, leaving the original completely intact.  In this case, two fresh installs - one 32 bit and one 64 bit.  Adding two new entries in grub.cfg is the biggest manual step.

Since each of the new 14.0 installations will be essentially a clone of the 13.1 install, I just copied onboot.lst from core13.1/tce64 to each of core14.0/tce64 and core14.0/tce and told my tce-lode script to go get the extensions listed in onboot.lst for each of the 14.0 installations.  What could go wrong?


Well, what indeed?  It turns out that
14.x/x86_64 has pciutils.tcz  while 14.x/x86 has pci-utils.tcz    and
14.x/x86_64 has usb-utils.tcz while 14.x/x86 has usbutils.tcz

Two one-character tweaks to onboot.lst and everybody's happy, of course, but it got me thinking - which is always dangerous.

So I snooped the info.list files back as far as 4.x and found that for x86, it has always been pci-utils.tcz but for x86_64, it changed from pci-utils.tcz to pciutils.tcz between 4.x and 5.x.


Similarly, it has always been usb-utils.tcz for x86_64 but for x86, it changed from usb-utils.tcz to usbutils.tcz between 5.x and 6.x.


I just wasted -way- too many brain cells on that, but those few that are left feel vindicated about the "can't remember which is which" thing.     

[HotNoob]

2025, ran into this.

http://tinycorelinux.net/16.x/x86_64/tcz/pciutils.tcz
http://tinycorelinux.net/16.x/x86/tcz/pci-utils.tcz

[Leee]

Dang it!  I saw this thread come alive and thought, "Oooh, somebody's fixed it"....

Lacking any reason to have them different, I feel like the naming should be standardized to either "include" or "not include" the hyphen and do it the same for both architectures.

I suppose there's something to be said, as well, for the "That's how we've always done it" line of thought, though I've been told that's not usually best.  I'm toying with the idea of coding an "exceptional processing" section for this into my updater script.  (Actually, I was thinking I had done that a year ago, but apparently not.)

[Rich]

Hi Leee
The extensions were created by different people for different architectures:
x86:

Code: [Select]

Title:          pci-utils.tcz
Extension_by:   juanito
Title:          usbutils.tcz
Extension_by:   bmarkus
x86_64:

Code: [Select]

Title:          pciutils.tcz
Extension-by:   dentonlt
Title:          usb-utils.tcz
Extension_by:   juanito
juanito used the dash naming convention, bmarkus and dentonlt did not.

In addition, the naming conventions are opposite between the 2 architectures:

Code: [Select]

x86       pci-utils.tcz    usbutils.tcz
x86_64    pciutils.tcz     usb-utils.tcz

[Juanito]

I guess that, all things being equal, the extensions should be named after their source tarballs, which are currently pciutils and usbutils.

[Juanito]

pci-utils updated and name changed to pciutils; alsa-config, inxi and udev-extras dep files adjusted in x86 repo

[Leee]

Thank Juanito.

[Juanito]

usb-utils renamed to usbutils in x86_64 repo and libosinfo, udev-extra and usbip dep files adjusted.

[gadget42]

instead of "solved" could there be "adjustments made" or something in the title to give future searchers/visitors/etc a hint

although i suppose most people will be searching for the word "solved" so maybe just stick with that...sigh..

[Rich]

Hi gadget42
This topic has been marked as solved. With an 80 character limit on subject
length (and about 70 chars used), space is at a premium.

Besides, when a thread is marked as solved, it means it either has been fixed
or an explanation has been given as to why it's not an issue. The posts in the
thread contain the information as to how it was solved. If the user wishes to
know the solution, they need to go through the thread. That's what it's there
for. The subject should be a very brief description of the issue. That's what it's
there for.