Slacko 5.7.2CE was published in 2019. Most of the posts to its thread can be found by plugging "Slacko 5.7.2 CE" in https://rockedge.org/psearch/. But the OP didn't make it thru the transition of http://www.murga-linux.com/ to https://oldforum.puppylinux.com/. Below the heading "Supplemental" is some information not provided by that OP which you may want to read first before considering making use of this Puppy. I have, however, highlighted the reason it was built and published. So, without further ado, here's what I wrote in that OP [and at that time kept a copy of for no good reason 
]
It’s identified as CE (community edition) Slacko as its contents are the efforts of many of Puppy’s Community. My part has primarily been that of packager. As I worked on it the refrain from Louis Armstrong’s rendition of the “Dummy Song”, https://www.youtube.com/watch?v=g2KgeBkFUcw often rattled around in my brain. Worth listening to before you consider my boring tale.
You’ll find it here: https://www.mediafire.com/folder/qs5aaidclm5im/. See this post, https://www.forum.puppylinux.com/viewto ... 076#p86076
What you get is a Slacko 5.7 (Slackware 14.0 compatible) which on a Quad-Core booted to desktop and opened PupSysInfo to reveal that only 68 Mbs of RAM had actually been used, although the entire 7,860 Mbs of RAM present were available for use. A Pentium-M Thinkpad T42 needed only 91 Mbs. [More about RAM, later].
I took Sailor Enceladus’ Slacko 5.7.1_r6231.iso, https://www.mediafire.com/folder/kwhxks ... .0#myfiles but substituted rockedge’s 4.14.63_full_rt (Real-time) kernel. http://rockedge.org/kernels/. The efficiency of a Real-Time kernel surprised me. Before testing, I had assumed it would require more, not less, RAM to perform a given task. I attribute most of the lowering of RAM needed to just to operate, mentioned above, to rockedge’s Real-Time kernel.
My goal was to construct a Puppy for older computers owned by recent Windows emigres. The target box is one with 512 Mbs of RAM, or less, perhaps unable to handle sse2 encryption, but, if capable could run firefox quantum OOTB. Inspired by jemimah’s Salukis, and the Carolinas which followed it, I originally intended a Puppy with a minimum of “builtin” user-applications, but easily expandable if the user chose to have the adrv.sfs load on bootup. [I’ll explain later why this last goal was largely abandoned]. However, two other aspects of Saluki also played a role in its design.
Saluki and the Carolina used a Control Panel to provide an easier-for-newbies-to-navigate method of customizing the Desktop and configuring settings than a ‘Stock’ Puppy’s maze of a menu system. And it’s Thunar Filemanager presented newbies less of a learning curve that rox. Desiring, however, to remain with the low-resource demands of JWM & rox, radky’s JWMDesk and PupControl were used, updated to their most recent versions, along with other enhancements by radky. While rox remains the default file-manager, the dual-pane xfe was installed to supplement it. Further newbie support was provided by AppFinder configured to use Puppy’s Categories definitions. One advantage of AppFinder is that when a Category is selected in its Left-Panel, not only are what may be to a newbie the strange names of applications displayed in the Right-Panel, but also a description of their use [read from the Comments argument of their respective desktop files].
“Utility” is just a noun for something which is useful. If it isn’t useful, why should it be present at all? Too many apps end up in such a ubiquitous category. And there’s a great deal of overlap between applications which show up under “Settings” and those which show up under “Setup”. I chose the following ‘dividing line’: if an application was entirely or primarily one which only provided INFORMATION, I assigned it to Settings. If it was primarily for changing settings it was assigned to Setup.
Unfortunately, under the current Categories recognized by Puppies, no distinction is made between setting up the operating system you’ve booted into, and the operating system you want either by way of remastering or creating a vehicle for installing to another medium. I’ve tried to alleviate that condition somewhat by modifying the Category arguments of some application’s desktop files in order that they appear on the Menu adjacent to similar applications, or those which are often used in combination (e.g. grub4dos after gparted). Some of those changes may be considered ‘unorthodox’. So, if an application isn’t where you’re used to finding it, continue looking. And before you panic, open Menu>Setup>Menu Manager – Edit the Menu.
If configuration of an application might not be needed except as part of one’s initial setup and not often thereafter, AND radky’s JWMDesk or PupControl provided a relatively easy way to find the configuration application, I used Menu>Setup>Menu Manager -- Edit the Menu to turn its display off. If you really want it on your Menu, reverse the process. Before doing so, consider the following: (1) Its /usr/share/applications/...desktop, used by JWM to generate Menu listings remains and can be clicked to start the application. And (2) ApplicationFinder --there’s a launcher next to the Start-Menu-- employs a different technique to generate its Menu listings. So the application will still appear on it.
Very few Applications were actually removed. Those which were, obviously, can be reinstalled via Puppy Package Manager. The most obvious applications you won’t find are:
Abiword -- replaced by focuswriter. See this thread for advice about it: http://murga-linux.com/puppy/viewtopic.php?t=99763
gmeasures -- replaced by don570’s Puppy Units
geany -- by oscartalks’ version
galculator by rufwoof’s version
All remaining Applications, such as those by zigbert, shinobar and rcrsn51 have been updated to their latest version as of the end of January 2019.
Seamonkey 2.35 was chosen for inclusion. I’ll discuss this along with alternatives later in this thread.
Supplemental. As noted above, the build included libraries necessary to run the then-current firefox-quantum. It should still be able to run any current mozilla-or-clone web-browser. But it won't run any Chromium-or-clones. The included web-browser is Seamonky 2.35, which at the time was serviceable while requiring the least amount of RAM. IIRC, however, if a computer lacked the SSE2 or greater instruction set a web-browser such as the SSE palemoon from here, https://www.forum.puppylinux.com/viewto ... p=170#p170 would be needed.
It would boot from almost all 'non-pae' computers if 'force-pae' was added to the kernel/linux line of its stanza in menu.lst or grub.cfg
To reduce its size and resource demands, additional applications were packaged in two 'alphabet' SFSes: an adrv.sfs and a ydrv.sfs. They are available for separate downloads from the same repo as Slacko 5.7.2CE, itself: https://www.mediafire.com/folder/qs5aaidclm5im/. The below screenshots show their contents. To have those applications as part of your operating system immediately upon boot-up, just place either or both of those 'alphabet' SFSes next to the puppy_ceslacko_5.7.2.sfs.
- SlackoCE's adrv.sfs.png (84.28 KiB) Viewed 1963 times
- SlackoCE's ydrv.sfs.png (67.04 KiB) Viewed 1963 times
