Where to find Individual Puppy Linux Packages for Installation in FatDog?

[Neo_78]

Puppy Linux has a tool called "PupSysInfo" to monitor system logs, which I would like to test in FatDog.

Where I can I find official packages from Puppy Linux for download and installation in FatDog64?

The Puppy Linux repository does not seem to host individual software packages like the FatDog source repository.

According to the documentation a PET package conversion might be possible:

"You can try converting a pet package. This is Puppy's native format. Fatdog's own package format is called txz. To convert a pet package to txz format right-click the pet package icon in ROX-Filer and select “Convert to New Package Format”. This will create a txz package alongside the pet package. Give the conversion process enough time to finish then install the package with right-menu click “Install Package”. There is no guarantee that the converted package will run on Fatdog. Some dependencies could be missing, etc."

Also, what would be the correct process to request software or cli tools (for instance from Debian) to be added to the official FatDog gslapt repository?

[Feek]

Puppy Linux has a tool called "PupSysInfo" to monitor system logs, which I would like to test in FatDog.

The latest version of PupSysInfo should be here:
viewtopic.php?t=3557&i=1
I did not try to convert it for use in Fatdog.

[jamesbond]

Thank you @Feek.

@Neo_78, go to the link that @Feek pointed, download the Pup-SysInfo-3.1.pet, after downloading it, right-click and choose "Convert to New Package Format", and it will create "Pup-SysInfo-3.1-x86_64-PET.txz". Right-click on this TXZ file, and then choose "Install Package". Pup-SysInfo will show up under "System" menu. I did a brief tests, it seems to work okay for the most parts (but of course don't expect it work 100%).

Also, what would be the correct process to request software or cli tools (for instance from Debian) to be added to the official FatDog gslapt repository?

Just ask here, in this forum, like what you just did for Pup-SysInfo.
It may happen. Or It may not happen. Or it may happen after a very long time, after you're bored yourself and moved on to other distro. We are slow and lazy

[m1k3]

We are slow and lazy

You may be slow and lazy but you guys make one heck of an OS which is the most important thing. Every time I play around with another distro I'm dismayed by the trend to make everything flat and low contrast. I miss the GTK+ 2 days. Plus, it's hard to beat FatDog's streamlined layering functionality and useful set of tools. This OS truly is a hidden gem. I only wish the Internet wasn't so hostile to Seamonkey.

[Neo_78]

Thanks @Feek and @jamesbond. Will try that and report back if anything should be broken. Not sure if there are any alternative GUI-based system log managers for FatDog64 ?!?

I actually really like FatDog. Having tested quiet a number of other Linux distributions, it's the first time that I feel that an OS is not standing in my way, is not full of bloat and can be customized to my liking. Excellent job of the development team !!!

Update:

I have been able to install PupSysInfo and have not encountered any errors so far. All tabs seem to produce valid reports.

[Neo_78]

It looks like PET files that have been installed in this way under the root account cannot be executed under a non-root user account. The respective menu links do not work.

Is there a way around this?

[jamesbond]

It looks like PET files that have been installed in this way under the root account cannot be executed under a non-root user account.

No, it's not the method of installation/conversion. The installation works correctly, and so is the conversion. But the conversion only changes the package format, it doesn't modify the programs inside the package. If the program decides to do some acrobatics when it's not run by root, there is nothing that the package-converter can do.

The respective menu links do not work.

If you run this from the terminal (the command to launch Pup-SysInfo from CLI is "pupsysinfo"), you will see why.

Code: Select all

sandbox# run-as-spot
sandbox# id
uid=502(spot) gid=502(spot) groups=502(spot),3(tty),17(audio),18(video),111(lp),112(lpadmin),1001(vboxusers)
sandbox# pupsysinfo
Password: 

It's stuck there waiting for a password.

Is there a way around this?

Yes, of course. But the "workaround" is application specific.
Firstly, we need to know why does it ask for password when it's being as non-root?
If you open the file /usr/local/Pup-SysInfo/Pup-SysInfo (the actual Pup-Sysinfo program), you will see why.
On line 6, it says this:

Code: Select all

[ "`whoami`" != "root" ] && exec sudo -A ${0} ${@}

It basically means that if you're not root, then try to re-run the program under "sudo".
The entire idea of "sudo" is to enable non-root users to run program as root, without any authentication (if you think that's not very secure, then you're right!). But our "sudo" isn't the real one, it actually calls "su" behind the scene, and "su" always asks for password (at least the one we use, not su-FULL). That's why you see the password prompt when you launched it in terminal. If you launched it from the menu, you don't see the password prompt - but the program is still stuck there, waiting for the password that never comes ...

So how to fix it?

1. You can just comment out the entire line 6 (add a # in the beginning of the line). But this may or may not work. There is a reason why radky wants to escalate to root; I think it's because some parts of the system info can only be obtained when you're running as root.

2. Instead of using "sudo", why not use Fatdog's privilege escalation program, which is "gtksu".
Delete line 6, and in its place put this:

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

But from your other threads, you don't like gtksu, so this is probably not something you want as well ...

[jamesbond]

You may be slow and lazy but you guys make one heck of an OS which is the most important thing. Every time I play around with another distro I'm dismayed by the trend to make everything flat and low contrast. I miss the GTK+ 2 days. Plus, it's hard to beat FatDog's streamlined layering functionality and useful set of tools. This OS truly is a hidden gem. I only wish the Internet wasn't so hostile to Seamonkey.

Thank you for the kind words.

If you like seamonkey, we can't build it from source nowadays yet (because it requires Rust compiler), but you can always update the seamonkey to the latest official version using the Control Panel. I'm not sure if it will helps the Internet, though. I know our SM includes user agent switcher exactly for this purpose - but the new SM has a completely different "extensions" infrastructure, so that the old one may not work and you may need to install a new one from somewhere.

[Neo_78]

I appreciate your detailed explanation @jamesbond

But from your other threads, you don't like gtksu, so this is probably not something you want as well...

I see how gtksu has its value and place in the system. To understand this better, it executes only this specific program with root privileges and does not leave the user permanently with escalated privileges, correct?

Wouldn't it be possible to enable / disable gtksu on a per user basis in the configuration? So some non-root users can call it while others do not have that capability.

[jamesbond]

Wouldn't it be possible to enable / disable gtksu on a per user basis in the configuration? So some non-root users can call it while others do not have that capability.

1. Rename gtksu to gtksu-bin.
2. Write a replacement shell-script (make sure it's only editable by root) which checks for who are allowed to launch gtksu.

(Untested) Example:

Code: Select all

#!/bin/sh
case $(whoami) in
    ben|john|jack) gtksu-bin "$@" ;;
    *) Xdialog --msgbox "Naughty boy!" 0 0 ;;
esac

You're welcome to write a more elaborate script that loads config files, checks for more conditions, etc. The possibilities are limitless.

[Neo_78]

Will try that @jamesbond Can you recommend a good source / book on shell scripting?

[dr__Dan]

Hi Neo_78. Here are two sources he recommended to me.
https://www.man7.org/linux/man-pages/man1/dash.1.html
https://grymoire.com/Unix/Sh.html
I found the second more useful, They are both specifically posix-compliant, as is the default shell in Fatdog64. Also available (and more popular) is bash, with some additional features and some different behaviour.
Dan

[don570]

I learned bash scripting with Advanced Bash scripting guide

https://oldforum.puppylinux.com/viewtopic.php?t=80501

___________________________________________

Newest version...

https://tldp.org/LDP/abs/abs-guide.pdf
___________________________________

[Neo_78]

Thanks @dr__Dan and @don570 Will check out those sources.