Puppy Linux Discussion Forum

Please, when giving information on what Puppy version is being used.

Example that is no help:

F96CE
Is this F96-CE_4 or F96CE_XFCE_FUSILLI

Bionic
Is this Bionicpup32 8.0 or Bionicpup64 8.0 or Bionicpup64-23 v2, etc......

Give us the complete full name of the Puppy version ISO.

This will provide the full name of the Puppy version, including the exact version number of it.

Yes, this exact version number is important. You could be using an older version, that has been fixed with a newer version.

Example of what is needed:
Fossapup64 9.5
BookwormPup64 10.0.3
BookwormPup64 10.0.4
BookwormPup64 10.0.6

This Puppy Linux even uses a date to indicate different versions.
BookwormPup32-23.12-240323
BookwormPup32-23.12-240223
BookwormPup32-23.12-240309

Example install of F96-CE:
You give the info from Pup-sysinfo as fossapup64 9.6

But that does not provide what release it was.
It could be the first one or the 4th one.

They all would show as fossapup64 9.6 in Pup-Sysinfo

But the specific ISO could be:
F96-CE.iso
F96-CE_2.iso
F96-CE_3.iso
F96-CE_4.iso
Each one is a different release with much different stuff in it.
F96-CE_4 is the last release and most bug free and error fixed of all of them.

So the version being used could be any of them.

If you give F96-CE_4 as the version you are using.

We all then know you are using the latest release and stuff in it should work this way.

A quick shortcut way to copy to clipboard exact version of complicated filenames that I often use is:

Right click on the file, and select Rename. The filename will be highlighted in the renaming window.
Right click again on the hilighted portion and select Copy. That copies the name (without the extension) into the clipboard.
Close the rename window (you aren't really renaming anything)
Paste the filename from the clipboard wherever you need it.

(This can also work to copy a full path, or a partial one, if you select more of what's in the rename window manually.)

vtpup wrote: ↑Sat Mar 30, 2024 4:25 pm

A quick shortcut way to copy to clipboard exact version of complicated filenames that I often use is:

Right click on the file, and select Rename. The filename will be highlighted in the renaming window.
Right click again on the hilighted portion and select Copy. That copies the name (without the extension) into the clipboard.
Close the rename window (you aren't really renaming anything)
Paste the filename from the clipboard wherever you need it.

(This can also work to copy a full path, or a partial one, if you select more of what's in the rename window manually.)

I use the same technique very often.

@bigpup

Is this what you want:

Operating System:
Distro Name fossapup64 9.6 (x86_64)
Woof-CE Build testing;cd5dcd04f;2023-01-21 15:35:41

I got this using:: menu -> system -> PupSysInfo -> File -> System Reports -> Summary <click>

Then copy & paste.

Cobaka

The complete full name of the Puppy version ISO is really the best information on what exact Puppy version it is.

You give the info from Pup-sysinfo as fossapup64 9.6

But that does not provide what release it was.
It could be the first one or the 4th one.

They all would show as fossapup64 9.6 in Pup-Sysinfo

But the specific ISO could be:
F96-CE.iso
F96-CE_2.iso
F96-CE_3.iso
F96-CE_4.iso
Each one is a different release with much different stuff in it.
F96-CE_4 is the last release and most bug free and error fixed of all of them.

So the version being used could be any of them.

If you give F96-CE_4 as the version you are using.

We all then know you are using the latest release and stuff in it should work this way.

Well, it depends on the specific scenario. If I make an application for Fossa96-CE, it would be confusing to specify the name of the distribution in the post as Fossa96-CE_4 for example as that may indicate that it will only work with version 4 but in terms of an enquiry about a specific version you are correct. How would you know however which release number you are using if you don't have the original iso anymore (System Info and DISTRO_SPECS give the date of release but not the specific release name)? I suggest that the specific name of release is specified correctly in DISTRO_SPECS and that the Puppy file names are amended accordingly for easy reference.

Yes, it would be nice if all the people that release a Puppy version, would follow some kind of naming standard.

It is never going to happen!

But the exact name of the Puppy version ISO, does seem to follow some kind of specific version release identification.

If you post some software you found or produced.

It always helps to also provide what Puppy versions you think it will work in.

Yes, I have seen the Puppy version release version, have an affect on software working or not working.
the newer release version, now has newer updated needed dependency stuff to run the program, that the older release version did not have.
Also it will usually have fixed bugs that are in the earlier release.

BookwormPup64 is a good example of this.
See the changes made to each new release version:
viewtopic.php?p=89021#p89021

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Getting DISTRO_SPECS correct, each time anything changes, does seem to be easily overlooked by Puppy version developers.

BUT WE NEED US TO GIVE THEM SOME UNDERSTANDING!

They are trying to do a lot of stuff usually all by themselves!!

At very minimum, we should help test, help them find errors like this, and tell them about them.
.
.
.
.

They are trying to do a lot of stuff usually all by themselves!!

them find errors like this

Oh well, that is what it is. If the kitchen gets too hot leave it. Puppy is not the end of it all, so MANY other distributions available that just waiting to be explored. I'm getting tired of this "only a few developers maintaining and working on Puppy and other users should do more blah, blah, blah". Forgetting to change the version name of a distribution is not an error it's an oversight.

I wonder if it would be possible to write a bash script that collected a bunch of info (including distro_specs) and other stuff that would remove doubt about the puppy under test.

Maybe including info such as creation date/time and size of main puppy sfs?

Would be handy to ask newbies to click on the script (or cli one liner) and provide the output...

greengeek wrote: ↑Wed Apr 10, 2024 8:22 am

I wonder if it would be possible to write a bash script that collected a bunch of info (including distro_specs) and other stuff that would remove doubt about the puppy under test.

Maybe including info such as creation date/time and size of main puppy sfs?

Would be handy to ask newbies to click on the script (or cli one liner) and provide the output...

So.......sorta like a 'Puppy' version of Inxi, or Neofetch, except concentrating specifically on the "Puppy specs" rather than the hardware.......yes?

Doesn't radky's PupSysInfo already provide this? (Yep; tab -> "Sys-specs", where as part of the report it'll give the readout from /etc/DISTRO_SPECS. Can't get much more Puppy-specific than this...)

Mike.

Pup-Sysinfo ->Sys-Specs ->Distro Specs

Good info if the developer of the Puppy version is providing the correct info in the Distro Specs.

There have been reports, that this did not get updated with new info, several times in different Puppy releases.

But this will always be correct for the needed info.

Or just provide the exact name of the Puppy version ISO.

But what if the person does not know exactly which iso was used to create their installation?

Then an extra bit of detective work may be necessary.

I just tried this one liner:

ls -lt /initrd/mnt/tmpfs > /root/pupfiles.txt

It lists details of my puppy files - including modification date - to a text file "/root/pupfiles.txt" .
Don't know if this would work on other pups but I think knowing the mod date for the base puppy.sfs would be critical in confirming which version of any given pup is in use.

EDIT : Actually, the following syntax is a bit more useful as it clearly lists the modification year:

ls -l --time-style=long-iso /initrd/mnt/tmpfs

So if I want to create a txt file listing my current puppy sfs and *drvs I can do this:

ls -lt --time-style=long-iso /initrd/mnt/tmpfs > /root/pupfiles_with_dates.txt

**Tested as working with both Dpup Stretch 7.5 (32bit) and Fossapup64 9.5 (64bit) so far.
Typical output:

total 330212
drwxrwxrwt 13 root root      1020 2024-04-12 22:14 tmp
drwxr-xr-x 14 root root       320 2024-04-12 21:58 pup_rw
-rw-r--r--  1 root root 135553024 2024-04-09 20:31 puppy_fossapup64_9.5.sfs
-rw-r--r--  1 root root 107257856 2023-08-19 06:18 adrv_fossapup64_9.5.sfs
-rw-r--r--  1 root root  39276544 2023-08-16 12:56 ydrv_fossapup64_9.5.sfs
-rw-r--r--  1 root root  31535104 2023-07-28 18:37 zdrv_fossapup64_9.5.sfs
-rw-r--r--  1 root root  24514560 2023-07-28 18:37 fdrv_fossapup64_9.5.sfs