Before you reply about derivatives, I am already well aware of their existence, but you may want to take a look at this first: https://www.reddit.com/r/slackware/c...ware_141_i486/.

Anyway...

I created/manage a GNU/Linux distribution called PsychOS (https://psychoslinux.gitlab.io). The current version is i686 and uses Devuan ASCII as its base. However, as I intend to move backwards instead of forwards for creating different versions of PsychOS, such as now moving on to PsychOS486, I have had one heck of a time trying to figure out the best way to get the latest software, or as late as one can get, for i486 and then respin/remaster that distro.

I want to use Slackware 14.1 if I can but perhaps because it is install only, that may be why it hasn't seemed like a possible option. I have tried everything I can think of to get it to create a bootable ISO. Please see this for an idea of what I have tried so far: https://psychoslinux.gitlab.io/docum...dingIndex.html.

I have no idea how other people have managed to create live versions of Slackware.

So far, it seems like Slacko Pup may be my only option, or at least it has gotten to the closest to what I am looking for besides actual Slackware, but I would like to know what other people here think before I start to fully commit to the idea.

I know next to nothing about this subject, but I think the big thing needed with liveslak was the overlayfs support provided in newer kernels and the squashfs tools since he has everything created as squashfs modules that are overlay mounted over each other until you get to a usable system.

Have you tried looking into the liveslak scripts to just get rid of the overlay and squashfs module support and create everything directly on the drive? It might make you lose some of the benefits provided by the liveslak scripts (like being able to update the base OS from new packages without affecting the persistent areas and might require tweaking of the setup2hd script if you're looking for the ability to install.

Liveslak does indeed only support Slackware 14.2 and newer.
Creating a bootable installer ISO (like the official ISO images you can download for Slackware) is not hard when you want to add your own customizations, just read isolinux/README.TXT
Adapting the installer script with your customizations will be the harder part, look at the scripts inside the installer to get a grasp of what it they do: https://git.slackware.nl/current/tre...sources/initrd

You can also check the work from Dimitris Tzemos aka djemos basically live ISOs and live installers for Slackware and distributions based on Slackware in his GitHub repositories. He was also kind enough to provide a variant for Slint, that I feel ashamed not to have used yet. I was and still am wondering whether to either use it or liveslak, but I still have items with a higher priority in my TODO list.

Maybe I can help you getting Slint a supported variant of Slackware Live, if it does not deviate too much from a regular Slackware.
Do you have a Slackware-compatible repository?

1 members found this post helpful.

Thanks Eric for offering to help, as if you weren't yet busy enough! Much appreciated.
It does differ significantly. I attach a list of packages in Slint that differ from the version shipped in Slackware.

And we ship many additional packages that make a Slint ISO and an installed system rather big. I just rebuilt an ISO with the packages currently shipped, its size is 4.5 G

As Slint should stay accessible to blind users with both speech and Braille so should be a live version.

Additionally the greeting screen of both isolinux and grub is not at all accessible, which prevents the user to tweak the command line, including to set the keyboard layout and the locale.

As an aside, some distributions allow to customize the installation reading a configuration file when running the installer. This is an option for Debian, also Clear Linux, cf. https://docs.01.org/clearlinux/lates...onfigfile.html and the config file can be fetched from a server or written on an USB thumb drive. Providing such a feature would need work, even more if a web form is provided to help the end user write a custom config file just filling fields. I vaguely remember having seen something like that on the web, can't remember where.
Yes: http://slackware.uk/slint/x86_64/slint-14.2.1/

But I'm afraid that make a Slint live be not straightforward for the reasons stated above, so it's maybe not worth your time and mine, at least as Slint is now. Maybe this could be considered for Slint 15?

Attached Files

pkg_slint_vs_slack.txt (1.3 KB, 13 views)

I am not concerned about package lists, as long as you have one, and a repository.
Things to take care of are a non-standard initrd to be used with a kernel. The liveslak run the installed mkinitrd command in a chroot so that should work even if you modified that, but the init script for liveslak is incomparable to that of Slackware.
And liveslak installs the distro kernel, but I think that can be worked around.
And there's a bit of post-processing for each variant so that the Live OS does what the user expects, out of the box.\For instance here is what happens if the DLACKWARE variant is being built: https://git.slackware.nl/liveslak/tr...=1.3.5.2#n2042

I.e. it should be possible but will require your input about how Slint initialization and initial configuration differs from Slackware.

1 members found this post helpful.