PupSysInfo-3.6

[radky]

Old Forum
https://oldforum.puppylinux.com/viewtop ... 11#p579411

Download PupSysInfo-3.6
https://www.smokey01.com/radky/Pup-SysInfo-3.6.pet

See changelog in second post below.

PupMates
https://www.smokey01.com/radky/PupMates.html

[radky]

Pup-SysInfo-3.6
• Adjust initial size of the PupSysInfo GUI based on screen dimensions.
• Adjust system information reports for compatibility with recent wayland and compositor updates in Woof-CE.
• Adjust format and content of the Quickview report. Go to PSI menu -> Sys-Specs -> Profiles -> Quickview,
• Adjust format and content of the PCI summary report. Go to PSI menu -> Devices -> PCI Devices -> Summary.
• Adjust format and content of the USB summary report. Go to PSI menu -> Devices -> USB Devices -> Summary.
• Adjust access to online PCI and USB device identification repositories. Specifically, add one-click access to the online HTML document corresponding to the selected PCI or USB device. Go to PSI menu -> Devices -> PCI or USB Devices -> Vendor ID and/or Device ID.
• Adjust Audio, Display and Network reports to prevent duplicate items in some scenarios.
• Adjust all System Profile reports (Quickview, Summary, Complete) to include the current percent usage of CPU, Memory and Swap resources. Go to PSI menu -> Sys-Specs -> Profiles. The CPU monitor is optional (enable/disable in Preferences).

Note: The Linux kernel manages the allocation of system memory and records the corresponding realtime memory statistics in /proc/meminfo. Although used memory is often defined as: MemUsed = MemTotal - MemFree, with the introduction of the MemAvailable parameter in kernel 3.14 the calculation of used memory is more accurately defined as: MemUsed = MemTotal - MemAvailable.

Importantly, these simple memory calculations are further enhanced by system information monitors that acknowledge the capacity of the Linux kernel to dynamically reallocate unused resources such as buffers, cached and reclaimable memory. Consequently, to more accurately define used memory, modern monitors deduct recoverable resources when reporting actual used memory though the methodology and calculations may vary with the monitor selected. For example, the popular Top utility and recent iterations of LxTask and PupSysInfo calculate used memory as follows:

MemUsed (actual) = MemTotal - MemFree - (Buffers + Cached + Reclaimable)

Other monitors common to Puppy Linux (such as older versions of Conky, LxTask and Htop) may use different calculations for used memory. For example, LxTask has an option to include buffers and cached resources in the calculation of used memory but older releases may exclude kernel-designated sReclaimable memory. Also, for many years Htop included shared resources (Shmem) in the used memory calculation but in 2021 (v3.1.0+) the Htop developers changed the MemUsed calculation and the report of used memory now correlates with Top and recent releases of LxTask and PupSysInfo.

For an interesting discourse on the variance in memory values reported by common Linux memory monitors (top, htop, conky, inxi, neofetch, screenfetch), please consider the following blog by Mboaba (translate button available at top right):

https://byteria.blogspot.com/2020/10/co ... usage.html

Pup-SysInfo-3.5
• Major update in content, format and organization of system information reports. Compatible with Legacy and Modern Woof-CE Pups, including Xwayland and Wayland variants. Also, fully compatible with Fatdog64.
• Add new 'Quick Profile' report for a concise snapshot of current system information. This new report provides a quick review of computer hardware and current system status. Go to PSI -> System-Specs -> Quick Profile.
• Add complete multi-format Partitions report. Go to PSI -> Sys-Specs -> Partitions.
• Add reports of Users and Groups. Go to PSI -> Sys-Files -> Users.
• Adjust format and content of system information reports for improved data retrieval and review. Convert multiple reports to a simple columnar format and adjust categories of information for improved accessibility to data.
• Adjust CPU report to include additional information about the central processor configuration, speed and onboard capabilities. Go to PSI -> Mainboard -> CPU.
• Adjust Sensor report (CPU temperature) for compatibility with recent linux kernels and multi-sensor motherboards. Go to PSI -> Devices -> Sensors.
• Adjust Memory report for concordance with standard linux memory monitors such as LxTask. Specifically, actual cached memory = cached memory + reclaimable memory as defined in /proc/meminfo.
• Adjust report of files that auto-launch at system startup. Go to PSI -> Sys-Files -> Startup.
• Remove long-standing dependence on perl to filter (remove) non-ascii characters from system information reports. However, if perl is installed (such as the default tiny-perl package of Puppy Linux) PupSysInfo will use this facility (in addition to baseline tr and sed filters) to remove non-ascii characters that may interfere with the display of system information reports.

Note: The new information reports require a monospace font for proper display of formatted text. This is the default display in PupSysInfo and standard text editors such as Geany. If you include a short sysinfo report in a post to the Puppy forum, simply apply the 'code' filter to maintain proper formatting of text.

Pup-SysInfo-3.2.1
• Adjust Kernel report for compatibility with recent kernels >= 5.18 (thanks peebee).

Pup-SysInfo-3.2
• Adjust code to run successfully as non-root (thanks jamesbond). Note: In Fatdog Linux, Pup-SysInfo generates useful sysinfo reports but complete data retrieval requires a basic perl installation such as the default 'tiny perl' package of Puppy Linux. Users of Fatdog Linux can use the GSlapt package manager to install the necessary perl files (for example, perl 5.26.1-x86_64-1 in Fatdog64-812).
• Adjust video report for Wayland-based Pups.
• Disable default probe of drives by the parted utility. In some scenarios, desktop drive icons overlap after the parted utility is called for the sysinfo report. If this is not an issue for your Pup, the parted probe may be enabled in Preferences.

PupSysInfo-3.1
• Adjust Kernel report to show the incremental minor version (recent Woof-CE kernels only)
• Bugfix: Prior versions of PupSysInfo call the ddcprobe utility to provide minor video information such as the monitor serial number. However, there are several reports that ddcprobe may fail in some scenarios or may 'freeze' the system with 100% CPU usage. Consequently, the call to ddcprobe is now removed. (thanks foxpup)

PupSysInfo-3.0:
• Add option to disable probing by the parted utility when generating drive storage reports (USB, SCSI and PartScan ). This may be helpful in Pups that assign the same x-position to drive icons (overlapping icons) after the parted utility probes the corresponding drives. Go to Menu -> File -> Preferences.
• Adjust ascii filter for sysinfo reports
• Adjust audio, video and cpu-vulnerability reports
• Adjust GTK3 and Xwayland compatibility
• Adjust Gtk stock icon viewer
• Adjust Help dialog
• Remove Font size option

PupMates
https://www.smokey01.com/radky/PupMates.html

[bigpup]

Thanks for this newer version.
PupSysinfo is in about all Puppy versions and is good to see you made a newer version, with improvements.
Hope you have done, whatever it takes, for Woof-CE build system, to use this newer version.

I just used this to update PupSysinfo in Raspup 8.2.1.
It had version 2.8.6

Being on a Raspberry Pi 400 computer.
It is amazing, how much information this program does provide, about the computer.

[peebee]

I've uploaded all of @radky updates to Woof‐ce-noarch?...

https://github.com/puppylinux-woof-CE/w ... ges-noarch

[radky]

PupSysInfo-3.1

See first and second posts.

PupMates
https://www.smokey01.com/radky/PupMates.html

[jamesbond]

@radky, please see the issue here: viewtopic.php?p=49249#p49249

Pup-SysInfo runs well under Fatdog as root. (The PET is converted to TXZ package, and the TXZ package is installed just like any other Fatdog package).

But when run as non-root, it's stuck, that's because pupsysinfo tries to re-launch itself as root using "sudo", and Fatdog's "sudo" actually asks for a password in the terminal. If we launch it from menu item (from the desktop) as non-root, this password-prompt will never be seen, and the app is stuck forever. The end-user thinks the app is not working.

Here's my suggestion to fix it. Replace line 6 with the following:

Code: Select all

if [ "`whoami`" != "root" ]; then
	if type gtksu 2> /dev/null; then   # Fatdog
		exec gtksu "Launching Pup-Sys-Info" ${0} ${@}
	elif type sudo 2> /dev/null; then # Other puppies with support for sudo
		exec sudo -A ${0} ${@}
	else
		Xdialog --msgbox "Running Pup-SysInfo as non-root. Some information might be missing." 0 0
	fi
fi

If there is neither gtksu nor sudo, the program will continue to run as "non-root", and probably fails to gather some statistics, but at least it won't be stuck (or you can choose to completely bail out of the privilege escalation fails).

PS: we have to test for gtksu first, not because I'm a megalomaniac but because the test for "sudo" will be successful even in Fatdog - just that Fatdog's sudo isn't everyone else's sudo and behaves differently.

[radky]

@jamesbond,

Thanks for the code to run PupSysInfo under Fatdog as root. I tested in Fatdog64-812 and most system information reports were successful. A couple of incomplete reports require a basic perl installation such as the 'tiny perl' package of Puppy, but overall PupSysInfo seems compatible with Fatdog (which by the way is a very nice distro with a refined desktop and a great selection of integrated applications).

I'll include your code in the next update which should be available soon.

Thanks again

[radky]

PupSysInfo-3.2

See first and second posts.

PupMates
https://www.smokey01.com/radky/PupMates.html

[radky]

PupSysInfo-3.2.1

See first and second posts.

PupMates
https://www.smokey01.com/radky/PupMates.html

[bigpup]

PupSysInfo-3.2.1 installed in Raspup 8.2.1 running a Raspberry Pi 400
It works OK!

About 95% of the info is provided.
That is normal for PupSysinfo on a PI computer.
These are ARM CPU and very specific motherboard computers.
I am happy with the large amount of useful info it does provide!

[radky]

PupSysInfo-3.5

See first and second posts.

PupMates
https://www.smokey01.com/radky/PupMates.html

[radky]

PupSysInfo-3.6

See first and second posts.

PupMates
https://www.smokey01.com/radky/PupMates.html