(old)Puppy Linux Discussion Forum

radky wrote:
Hi 666philb,

Is the following format OK?

OpenSSL: 1.0.1f 6 Jan 2014, built on: Fri Jan 9 17:52:35 UTC 2015

yes that's perfect

The developer of tahrpup (666philb) has requested a feature update for Pup-SysInfo-2.6.

Consequently, an updated Pup-SysInfo-2.6.pet is currently available at the download link in the first post.

Specifically, the OpenSSL report now displays the build date, and the Bash report is adjusted for non-English locales.

Since the initial upload was only hours ago, the version number of Pup-SysInfo-2.6 has not changed.

Thank you for quick responses and fixes, radky.
These tools are great indeed.

Godspeed!

radky,

Just to let you know your improvements have been noticed.
Your programs, that are in Tahrpup, have been updated using Tahrpup updates.

Thanks for the bug fixes and improvements!!

Griot, bigpup and 666philb,

Thanks for your kind comments!

Pup-SysInfo-2.6.1. See first post.
- Updated network report to accurately detect the status of firewall_ng (Puppy's new firewall).
- Bugfix: display of log reports failed if special control-code characters present.

Hi radky, in

/usr/local/Pup-SysInfo/Pup-SysInfo
line 324
You pass -q to report-video... is there any reason for that?, as far as I know, this script does not require any parameters.

The woofce's report-video is about to be sensitive to parameters, see:

https://github.com/puppylinux-woof-CE/w ... /675/files

jlst wrote:You pass -q to report-video... is there any reason for that?, as far as I know, this script does not require any parameters.

Hi jlst,

If I recall correctly, forum member TaZoC created the original report-video utility and he included the -q parameter which provided an optional (quiet) report without calling the GUI.

TaZoc changed the name of his utility to video-info on 21-Jan-2013, so the -q switch is no longer valid in the current Puppy report-video.

I'll prepare an update for PupSysInfo.

Thanks for the report!

Pup-SysInfo-2.6.2. See first post.
- Bugfix: The original -q (quiet) parameter of report-video is no longer valid in Woof-CE and is now removed from PupSysInfo's video report.

PupSysInfo-2.6.3. See first post.
- Add 'Actual Free RAM' and 'Actual Used RAM' to Memory report
- Bugfix: understatement of total size of savefile (Personal Storage Report)
- Bugfix: failed detection of available space in savefolder (Personal Storage Report)
- Bugfix: failed 'grep' when generating lspci reports with special characters

Many thanks, radky.

PupSys-Info-2.6.5
- Adjust the memory (personal storage) report to correctly parse the single-tmpfs architecture of the new Woof-CE init (gyro 2016)
- Continue support for the multiple-tmpfs architecture of legacy Pups

PupSys-Info-2.6.6
- Bugfix: failed modprobe for Cpu temperature detection in some legacy AMD and Intel Pentium processors
- Bugfix: inaccurate display of WiFi signal strength at 100%

I have just discovered Pup-Sysinfo System Information on TahrPup 6.0.5 after using Linux Puppies for several years. It appears very useful to me, but I have a few concerns.

The version of PSI which I had was 2.6, but I saw that the latest seems to be 2.6.6. I down loaded the pet of 2.6.6 and installed it. It seems to have replaced the older version I had. Is this a good way to update this (or other) Puppy applications?

I was very pleased to see that the Mainboard > CPU > shows a Bit Capable number. I need a good easy way to determine the bit capable of the specific computer which I am using. I am responsible for several barebones computers without hard drives running Puppy Linux from a USB memory stick. I have been trying to use the command line to get this information. This seems to differ from the value I get from PSI. This is troubling. I am not good on the terminal, but I can usually, but not always, get a reply from a command for that information. Sorry, I do not have that command which I found on the internet. Actually SSI gives a 64 bit capable report on every machine I have looked it up on. I was sure that some of these were 32 bit machines, and that the command line said so.

Please, someone, enlighten me. There seems to be a wealth of information easily available using SSI. I am very glad i found it. I regret not having seen it before. I bet I am missing a lot of other valuable tools.

Thanks!

Peter

Hi Peter,

As true for most Puppy utilities, each release of PupSysInfo installs to the same directory.

This assures a consistent path in the file system for all versions.

---

PupSysInfo uses the Puppy-standard dmidecode utility to define CPU architecture.

For 64-bit processors, 'dmidecode -t 4 | grep capable' returns '64-bit capable' and this is what you see in the PSI report.

The dmidecode utility reports information about the system's hardware as defined in the system BIOS. Consequently, the accuracy of the dmidecode report is only as accurate as the information encoded in the BIOS by manufacturers, and this may vary depending on the manufacturer or BIOS version.

Alternatively, you can grep for the 'lm' flag in /proc/cpuinfo.

grep -o -w 'lm' /proc/cpuinfo | sort -u

The lm flag (if present) indicates 'Long mode' or 64-bit CPU

Thanks for your comments!

Edit: Maybe you could PM moderator Flash and request removal of your duplicate post in the Utilities forum. (thanks)

Thanks very much for the information you provided. It has taught me a lot. I am not sure I know how to use it, but I will try.

Some of my computers which indicate 64 bit compatable on PSI will not boot 64 bit versions of Puppy.. Partly for this reason, I am working to standardize all my computers as 32 bit Tahr 6.05. Unfortunately I have not been able to get some of the older computers to boot even the 32 bit Tahr.

I will try to have the duplicate of my post deleted.

thanks again for your help.

Peter

PupSys-Info-2.7
- Add 'Video RAM' report (thanks 01micko)
- Add kernel command line to hardware and system reports
- Add support for the concise sysinfo report of inxi, if installed (PSI menu -> Sys-Apps -> Inxi)
- Adjust output of the Uptime report, and add Processes (total and running)
- Replace xmessage with gtkdialog-splash as the primary notification dialog
- Bugfix: In some scenarios, system reports with non-ASCII characters did not display

radky wrote:- Replace xmessage with gtkdialog-splash as the primary notification dialog

Why?

MochiMoppel wrote:

radky wrote:- Replace xmessage with gtkdialog-splash as the primary notification dialog

Why?

Hi MochiMoppel,

Replacing xmessage with gtkdialog-splash is primarily a consideration of aesthetics.

In my opinion, the default appearance of the xmessage dialog is acceptable in recent Pups but the appearance in older Pups is much less appealing.

On the other hand, the gtkdialog-splash dialog is relatively consistent in legacy and modern Pups.

If gtkdialog-splash is not available (renamed, deleted or not installed), PupSysInfo-2.7 will default to xmessage as the notification dialog, in which case the behavior is identical to prior versions of this application.

Thanks

Hi radky, thanks for your answer and thanks for your wonderful application. The new version works fine for me.

radky wrote:In my opinion, the default appearance of the xmessage dialog is acceptable in recent Pups but the appearance in older Pups is much less appealing.

I suspected a compatibility issue, but aesthetics?

I compared gxmessage versions of an old Puppy 4.2 and of the newest Tahrpup. Both versions rendered exactly the same in my Slacko5.6 (second dialog in screenshot). So if it's not gxmessage itself, it must be the parameters. Different Puppies may default to different fonts, leading to a more or less pleasant look. Dialog-splash is hard-coded for DejaVu bold. If you specify this font for gxmessage you can achieve the same consistent look in all Puppies (see 3rd dialog in the screenhot, produced with Puppy 4.2 version). Not that bad, better than the second one and much,much faster than gtkdialog-splash. Even if speed may not matter for a dialog that says "Please wait..." I guess that the time it takes until gtkdialog-splash makes its appearance on screen can sometimes be longer than the wait it announces.