Yes, the included make_slackware_live.conf file offers one things to edit and replace to make the iso their own. You can insert code into it at the bottom to have it execute upon creation.
Liveslak does have presets for a few different installs. An XFCE slimmed version, Cinnamon, KDE, and a stipped down base Slackware install, as well as a complete installed ISO.
I've personally done a fair bit of hacking away at the script myself to create my own
GNOME 42-based Slackware. The user account can be changed in the conf file,
is the item for that, you can change it to whatever you want (make sure to uncomment it as well). You can also change the
UID to another option and even change the
Code:
LIVEPW=yourp4s5w0rd
. You don't have to edit the conf file, you can just edit the script itself, but if you break it, it usually breaks
hard. So be careful, but don't be afraid. You can always start again!
If you want to leave the root/live accounts and add more, after line 108 in the make_slackware_live.sh has some items you can customize to add users/groups if you need advanced use of this feature.
As for packages, inside the pkglists/ folder you'll find sets of packages for specific installs, you can always hack away at them to tailor it to your needs. But the simplest method I've found for myself, is to edit the
within the Slackware package tree. If you're familiar with using them, the ADD/REQ are basically treated as auto-install but to not-include a package, you'll want to change it's entry to
and when creating the ISO, it will be omitted. Just like the installer would treat it. I keep local edited tagfiles and just copy them over a freshly copied -current tree myself and run with that. You can even replace specific packages with older/newer versions if you'd like, the script consults the tagfiles but doesn't seem to mind differing md5 data. If you want to omit entire package sets, edit the
line (if you're sticking to customizing that specific build, or choose the base your editing). It's really quite easy to play with once your familiar with the script.
My advice though, when re-building a pkgset you do have the option of just re-building the pkgset you've edited with the
line. It's just like the SEQ parameter, but you need to apply a
on the command. This can/will save a lot of time between edits and not re-building the entire ISO each time.
Most importantly, have fun! AlienBob has created a wonderful tool with liveslak!
EDIT: I forgot to mention persistence. I believe if you just write the ISO to a usb using other methods, no persistence folder is created, therefor, you will achieve what you're looking for. Not sure if one can turn it off from the iso2usb.sh script, but the ISO itself has no persistence.
Possible to create a Custom Slackware Live Edition ?
