Moderators: 666philb, Forum moderators
@radky Ran through different file types and the right click options are perfect. Ready to go I say.
Did find that the icon switch.png for conky_toggle_switch.sh in the tray is missing in the adrv SFS /usr/share/pixmaps. Check also that conky_toggle_switch.sh is in the correct position in the adrv SFS. I noticed when I went to shut off conky that the icon button was missing in the tray but was in the tray configuration.
I would like to adopt similar right click options in KLV.
The conky_toggle_switch (conky_toggle_switch.sh and switch.png) of the main tray have been removed and replaced by two separate items (conky restart and conky stop) in the utilities menu (right side of tray). This was done so a single click of 'conky restart' will turn off the current conky monitor followed automatically by a fresh conky start. A quick restart of conky is useful at times to synchronize the conky background with the underlying ROX desktop background. If you prefer a simple on/off toggle, then ETP's original conky_toggle_switch.sh would be a great addition to KLV.
I'll check the upcoming radky5 when it's available. But from radky4 and wizard's post it appears that radky has included all (and done a much better job than me) with these exceptions: as mentioned by rockedge 'run-in-terminal' and (far less important) dir2iso. F96-radky-R4 has ISOMaster on the menu so I guessed that dir2iso would be present. pfind locates it in /usr/sbin. I don't know if it will function via Right-Click, or even if it does it would be better to add ISOMaster, or nothing.
About Run in Terminal, the problem I had including it for AppImages in my pet was the 'suffix' of an AppImage could be anything or nothing: e.g. Application.Appimage, Application.appimage, or just Application. [Several of MikeWalsh's portables are essentially AppImages --without a suffix-- started by a wrapper which makes some modifications of how the application functions].
I think I captured the most frequent by Right-Clicking any variation I had among my accumulation of AppImages, selection "Customize Menu", dropping Run-in-Terminal into the GUI which opened, then copying the new file which appeared in /OpenWith into my 'Build-Directory' 's corresponding folder.
I've attached my pet's /root/.config/rox.sourceforge.net/OpenWith in the hope it may save you some time and effort. But check the contents of the included folders for unwanted or conflicting content.
@ Rockedge, I started a Right-Click thread here, https://www.forum.puppylinux.com/viewtopic.php?t=7077. Not only do I have no objection to radky or anyone else who actually knows what (s)he's doing take over the responsibility of that thread, I would welcome it. My efforts were out of desperation: no one else was providing the tools I needed to explore the new breed of Puppys.
I would recommend that a Right-Click pet be maintained, perhaps @ https://distro.ibiblio.org/puppylinux/p ... es-common/ and/or wherever someone woofing a Puppy can obtain it. We now know that currently a woofed Puppy will not include Right-Clicks. [There was a suggestion that DistroWatch's criteria would preclude post woof modified Puppys from being 'official': 'though I have doubts about that suggestion]. Certainly, being able to include Right-Clicks while woofing a Puppy would make life easier.
The combination of files needed to provide Right-Clicks is the same without regard for what Puppy is in use. AFAICT, currently their only dependency is that Rox is file-manager (untested, rox being present if another file-manager is the default). Originally constructed for VanillaDpup, I have since employed it with various F-96s, S15Pup64 and IIRC VoidPup. No binaries are involved; only relationships to whatever version of /usr/local/Apps/Run-in-terminal is already present. So they should also work under 32-bit Puppys.
Except for some fundamental change in Rox, I can think of only one other which might require revision.There was a Right-Click pet created by don570 which worked great in the Puppy it was created for and several older Puppys. But I think a change in 'bash-dialog' employed by newer Puppys derailed it under those.
dir2iso would be present. pfind locates it in /usr/sbin. I don't know if it will function via Right-Click, or even if it does it would be better to add ISOMaster, or nothing.
I use dir2iso quite often.
mikeslr wrote: ↑Tue Dec 13, 2022 10:36 pmI would recommend that a Right-Click pet be maintained, perhaps @ https://distro.ibiblio.org/puppylinux/p ... es-common/ and/or wherever someone woofing a Puppy can obtain it. We now know that currently a woofed Puppy will not include Right-Clicks.
I think it would be great to "merge" that .pet into https://github.com/puppylinux-woof-CE/w ... /rox-filer, so we have one ROX-Filer package that carries all fixes and additions.
Sofiya wrote:
Touchpad won't start
@Sofiya
Could you provide information about your touchpad ?
1 - Input devices: cat /proc/bus/input/devices
2 - Kernel log: dmesg
3 - xerrs.log
With additional information, I'm sure rockedge and other knowledgeable forum members will be happy to respond.
Thanks
mm .... right now I'm loading, checking everything started). these were magnetic storms 
KL
PUPPY LINUX Simple fast free
New F96_4-radky5 iso
Outdated iso removed
MD5:3eb346b137726b39e538493b4ce9c7bc
SHA1:31dbb9ff2ba01bb6a14a3c9cd28fcde5551e9290
Changelog:
• Update 6.0.12 kernel (devx and kernel sources are available in Menu -> Setup -> quickpet fossa -> Useful tab). Please see Note below.
• Update available options of 'quickpet fossa' for installation of popular applications (Menu -> Setup -> quickpet fossa)
• Update Puppy help resources in /usr/share/doc
• Adjust configuration options of the Gatotray and Lockstate menu items
• Adjust function of network shares for compatibility with ConnMan and Connect Wizard tools (thanks wizard)
• Adjust ROX right-click options (thanks mikeslr)
• Adjust and simplify nomenclature of items in the main menu
• And many more adjustments to hopefully improve the desktop experience
Note: The 6.0.10-FP kernel of FP96 is configured for relatively recent hardware but also supports many older hardware types. Please be aware, recent kernels may add warning messages to the kernel log, indicating older hardware may not fully comply with modern specifications. For example, on 24 Feb 2022, the kernel devs added a new warning about out-of-date legacy BIOS firmware. The 6.0.10-FP kernel works great in my old 2008 Toshiba laptop but the kernel log repeatedly informs me the old BIOS firmware does not comply with current ACPI specifications. In such cases, one can simply ignore the warnings -- or switch to an older kernel.
Hi @radky,
I tried numerous times to download your previous releases - but every time chromium spit out a network error (after downloading a good peace of the iso, ~ 170 MB or so).
I did not resume - since there was no checksum provided.
Today I used a pristine firefox and all went well - and you finally provided checksums to verify, good!
Thank you ...
peace
@radky I've really been putting F96_4-radky5 through some paces and can report excellent results throughout.
Well done! 
I have some X10 switches that I control from a desktop using a USB CM19a transceiver that I can communicate with remote wireless receivers and motion sensors. The driver for the cm19a is written for python2.7 and I have several small programs for switch toggle controls and to poll the motion sensors queue.
I loaded the devx and installed python2 alongside the python3 components already present and everything is running perfectly. Python components installed relatively easily, which is always a plus.
I am seeing smooth kernel performance and a great idle. The attention to details is paying off and this has become a really useful, polished distro.
At some point I am going to compile and attempt to install Zoneminder which will test the OS in all kinds of directions. Looking forward to it!
Am going to hook up a HP F4500 printer and go with @rcrsn51 's HP kit and round off testing with some print jobs and attempt remote scanning with F96_4-radky5
From earier
it would be better to add ISOMaster,
+1
@Clarity
In the last four developmental releases of FP96, isomaster is included as one of the ROX right-click options for ISO images.
Super elegant, super smooth. Thank you very much.
I can report that remotescan works fine with a Brother MFC-L2700DW.
Entering the necessary extra rules in Firewall Setup 0.8 also worked.
Completed preliminary ISO file booting via QEMU running in Deb-DOG as well as booting bare-metal via SG2D. Tested both pristine as well as allowing this Radky5 version to find and use its SAVEs as well as offering upgrades to prior session-saves.
Operationally perfect! No use issues to report. PM works, PET installation of some of @ETP's and @Jasper's PETs are working without issues.
Thanks to all in this continued progression!
Request: TLDR
Could a future version contain the TLDR package. Its ability to suggest Linux command examples on the terminal/console has reduced any need to swing to the internet for examples. OR could it be packaged in the REPO as a PET (although its tiny size suggest it be included within the system for the similar benefits to MAN command it brings).
Using Package Manager NG, tldr seems to install, but, when attempting to execute via Terminal, 'command not found'
Using the traditional PPM, tldr does install with dependencies. On F96-CE terminal on the desktop, the tldr command does work.
Code: Select all
# tldr-hs -v
0.4.0.1
# tldr-hs --update
# tldr-hs tldr
tldr
Display simple help pages for command-line tools from the tldr-pages project.More information: https://tldr.sh.
...Other command searches using tldr yiields great suggestions for Linux command uses.
Non-impact, non-priority finding when using Package Manager NG Repo updater?
Message: Checking pkgs
/usr/local/petget/0setup: line 337: support/findpkgs: No such file or directory
Finished.
I am also seeing problems since original F96 build from woof-CE. I use a script I made to install Zoneminder and web server in Fossapup64-9.5 that relies heavily on Pkg-cli to do the installation work. Pkg has not worked correctly yet but I am just starting to really examine what it will take to fix it.
Might be just a simple adjustment. @dimkr might know more about it and have some ideas as to where we start to address a fix.
Is @sc0ttman around as of late?
Remove builtin packages does not work as expected!
From what I've tried, packages are affected with empty files in /root/packages/builtin_files
E.g. removing bluez results in a set of .wh. Entries in /initrd/pup_rw
When removing e.g. Palemoon, /usr/sbin/remove_builtin ends without error, but it has no effect on the corresponding directories in /initrd/pup_rw.
I have tried:
abiword, Palemon, gPlanatary - not working
Bluez, connnman - works
@fr-ke I think those applications are all included in the adrv SFS. To remove them from the system completely rename the adrv and disable it from loading. Or edit the SFS yourself and unsquash the adrv edit and delete the programs you desire, then squash it again. Edit-SFS is a program that can be helpful in this job. I just open the SFS to view it, then copy the contents to a new directory. From which I edit it, then squash the new directory into an adrv SFS.
PackIt makes a good SFS adrv out of the work directory.
F96-CE is modular in design and the quick removal of applications is easy as renaming the SFS files. Removal of the Built in packages will work with the tools included as expected.
You would have to probably delete /root/.moonchild productions
@rockedge
I know how to do this and I use these tools all the time.
I just wanted to help and point out that puppy's features of removing packages and installing packages and then remastering them can produce unexpected results.
It was unexpected for me, which is why I started looking for the cause.
@fr-ke That's true that SFS editing and remastering at any level does at times bring unexpected results.
Some mechanism with a GUI that can package manage the adrv and bdrv "on the fly" will be optimal.
I would like to "second" the request for TLDR to be included in a future build. It is helpful and can be used offline too.
Or an alternative if someone could make a suggestion?
Hello @radky
I've already reported on the booting of this distro via its ISO file. So far, I have booted this via every ISO file booter I have without issue; namely Ventoy, SG2D, QEMU, and ISObooter. Every one of this also is capable of pristine operations, creation of their save-session, and finding the saves upon reboot with NO interruption or change in any boot stanzas at boot time. EXCELLENT Builds allow this kind of Frugal operation with no need to move ISO contents for any reason for a complete and thorough PUP operation.
This POST is to share something extraordinary in past PUP use on the LAN. As most members do, I use SAMBA to share specific PC folders from the local PC to others on the LAN (TV, etc.). On this PC that I have exchanged and written files to/from it for years, running Slacko v8 bare-metal.
I dont know what you may have done, but for some unknown (at this time) F96 is exchanging files to and from it at a speed unseen on this PC before. Your implementation of SAMBA does not show anything different, but, something has affected performance exceptionally for writing files to it over the LAN from others as well as the behavior of the SAMBA utilities baked into this distro. File transfers have ALWAYS been faster than writing files to most all of my USB sticks (they are slow by any metric). But, this F96 best the prior distro(s) used on this old PC.
If you know, pat yourself on the back, if not, then just smile...I am.
Hats off to both you and @rockedge for this thread and the work effort you present us, here, on the forum. THANKS!!!
P.S. 15% faster using F96 for 2GB file transfer tests.
So I finally booted the iso I had downloaded. Really nice! I'm just checking to see if I've got the latest and greatest. My iso is: F96_4-CE_radky4. Is that the latest release?
Fossapup has always had a nice toolset, and this is new one is even better.
geo_c
Old School Hipster, and Such
Due to most likely a technician flipping the wrong switch while servicing a neighbor I have lost Internet service until the provider sends another tech to turn the switch back on. Which may take up to four days and is no fault of my own or my equipment's.
This has given me the opportunity to try out the USB tethering to a mobile phone with cellular data. Conman does identify the usb tether device but I have not been able to switch over to use it, I used the Network manager switcher to select the Network Wizard to make the connection which worked as expected. Network Wizard "saw" the usb network device and allowed it's selection. Using the wizards steps the connection to Internet was made.
In summary: F96_4-radky5-CE works well with a tethered Internet connection via an inexpensive mobile phone.
So I can type this and work on some things but will need to wait to upload anything significant (i.e. ISO files)
The fortunes of tech, I lost mine last week for a couple of days when someone chopped a fiber cable up. Have dumb phone, so had to wait for them to fix.
Luckily, I have movies on my file server, so still had plenty of entertainment.
wizard
Big pile of OLD computers
Well I thought I would try this as it seems to be an example of the way in which puppy linux is moving. There are now three posts on this which I found a little confusing. I made the mistake of downloading the version on the first post of this thread before reading all the posts in the thread. I have also now had an attempt to download the latest version F96_4-CE_radky6.iso. This took well over an hour then "failed" at 482MB. I have tried again and had problems with the download each time. Has anybody else had this problem? I am trying yet again to download it as I type this. It's currently sitting at 7m to go. Sorry just gone back up again. I am not confident this download will work either. However, I have installed F96_4-CE 4th Gen. I have a manual frugal install on an hdd formatted as ext3. I'm booting from grub4dos. I largely copied what I used to boot FossaPup64 95. i.e.
Code: Select all
title F96-4-CE (64bit) (sda2/F96-4-CE)
find --set-root uuid () 60e6917a-e1db-44f9-8d58-6f0df737eeb5
kernel /F96-4-CE/vmlinuz psubdir=/F96-4-CE pmedia=atahd pfix=fsck
initrd /F96-4-CE/initrd.gzThis worked but gave a number of errors which flew by at a rate which made them impossible to read. It did boot to a desktop. I did some setting up all of which worked. I then shutdown and chose to make a save file (I like them). I had a look at the "boot" folder in the iso and looked at the examples in grub>menu.lst and found this
Code: Select all
title fossapup64 9.6
kernel /vmlinuz pmedia=cd pfix=fsck
errorcheck off
initrd /initrd.gz
initrd /ucode.cpio /initrd.gzI included errorcheck off in my code below the kernel line hoping it would suppress the errors I see at boot up but it doesn't. So I have a number of questions.
1. What's causing the error codes?
2. Should including errorcheck off stop them and is it in the correct place?
3. Have these errors been noticed by others
4. Have any been addressed in the updates?
5. What does ucode.cpio do?
I now appear to have a copy of F96_4-CE_radky6.iso, downloaded while I was typing, at 483 MB. Is there an md5 checksum for this.
I'd appreciate any help with the above. I'll now have a go at installing the F96_4-CE_radky6.iso.
Regards,
Ken.
Edit: Now have a manual frugal install of F96_4-CE_radky6.iso. using a similar boot stanza to that for F96-4-CE including errorcheck off. Do not see errors at bootup anymore. Did a basic setup and made a save file. Have both rebooted and shutdown and rebooted and all seems fine. I'm posting from it now. My initial impression is that it looks much more polished than F96_4-CE 4th Gen. Will spend some more time on it latter.
@keniv Yes all of the boot errors in the F96 versions have been fixed in all of radky versions and can be ignored in the F96 version prior to the radky versions.
Many many improvements and fixes have occurred between this earlier version and the current version. The kernels have been changed several times to find the right fit.
Please transition to F96_4-radky6-CE for a real look at this new Fossapup, early versions before the radkyXX versions are depreciated.
Install it just like any Fossapup64.
The file ucode.cpio is micro code for the kernel to add enhanced kernel hardening.
If you have continued problems downloading the ISO, I can make another download location available.
Is radky6 available on the same link you provided me above for radky5? Or should I just wait for the upcoming official release? I'm in no hurry.
geo_c
Old School Hipster, and Such
@geo_c Here is the link for the ISO :
F96_4-radky6-CE
If there are any problems downloading it I can make another download location available!