From Newsgroup: alt.os.linux.slackware

Sorry for re-posting this, but I was worried that the fire of interest
might sputter and die.

On Thu, 26 Feb 2026 20:03:40 -0500, MummyChunk wrote:

Thanks for the update. Grok's warning makes sense: having "Slackware" in
the project name can look like endorsement, even if that isn't your
intent. Renaming the toolkit to something like SAM.Zombie and describing
it as "for Slackware 15.0" or "works with Slackware" feels safer.

The idea itself is interesting, especially the part about converting a running LiveSlak into a persistent setup without a full reinstall.
What's your persistence approach under the hood, and how easy is it to
roll back if someone changes their mind?

Thanks for the interest, and sorry for the delay in answering!

I'm working on a release of "Zombie Silas" as part of the SAM.Zombie
library. Perhaps even I will produce actual, bootable Zombie Silas
flashdrives for distribution as well.

Under the hood, the tweaks to a running LiveSlak are very much like the
tweaks to an rsynced copy of a Slackware reference installation (a
"Basis"). Both are performed by the same script, aptly called "bite". The
two processes are a little different, yet very much the same. This
similarity is accomplished by using chroot for the Slackware tweaks and
root to perform the LiveSlak tweaks.

The LiveSlak tweaks are temporary and must be performed as root at each
boot of LiveSlak. This is a serious nuisance, but a great benefit at the
same time. After all, it provides real persistence and custom
modifications to the environment and system, including KDE.

This is a response to the post seen at: http://www.jlaforums.com/viewtopic.php?p=701801931#701801931

--- Synchronet 3.21f-Linux NewsLink 1.2