[2025-jun-17] The SlackDocs mailing lists at https://lists.alienbase.nl/mailman/listinfo have been retired. No one has been using these lists for years and it's time to say goodbye. The list archives remain available at https://scalzi.slackware.nl/mailman/listinfo/slackdocs

[2025-jun-17] The SlackDocs Wiki has moved to a new server, in order to make it more performant.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
slackware:liveslak [2021/11/24 06:15 (UTC)] – Updated http download locations alienbobslackware:liveslak [2026/02/14 09:35 (UTC)] (current) – [Downloading ISO images] Removed no longer existing Indonesian mirror URL alienbob
Line 48: Line 48:
 Common download locations are: Common download locations are:
   * Primary site: https://download.liveslak.org/ (%%rsync://liveslak.org/liveslak/%%)   * Primary site: https://download.liveslak.org/ (%%rsync://liveslak.org/liveslak/%%)
-  * Darren's https://slackware.uk/liveslak/ (%%rsync://slackware.uk/liveslak%%) +  * Darren's UK mirror: https://slackware.uk/liveslak/ (%%rsync://slackware.uk/liveslak%%) 
-  * Willy's http://repo.ukdw.ac.id/slackware-live/+  * US mirror: https://us.liveslak.org/ (%%rsync://us.liveslak.org/liveslak/%%)
  
  
Line 132: Line 132:
  
  
-If you downloaded a liveslak ISO file and want to boot that ISO directly from its location on your computer's hard drive, you can use this Grub configuration block and add it to your ''/boot/grub/grub.cfg'':<code>+If you downloaded a liveslak ISO file and want to boot that ISO directly from its location on your computer's hard drive, you can use this Grub configuration block and add it to your ''/boot/grub/grub.cfg'' (the example code assumes you downloaded the XFCE ISO and stored it as "''/data/ISOS/slackware64-live-xfce-current.iso''"):<code>
 menuentry "LIVESLAK ISO" --class gnu-linux --class os --class icon-linux { menuentry "LIVESLAK ISO" --class gnu-linux --class os --class icon-linux {
   set iso='/data/ISOS/slackware64-live-xfce-current.iso'   set iso='/data/ISOS/slackware64-live-xfce-current.iso'
Line 143: Line 143:
 }</code> }</code>
  
-This example will add a 'LIVESLAK ISO' menu entry to your local computer's boot menu, through which you can start a downloaded XFCE Live ISO pre-configured for a US keyboard, Dutch language and Amsterdam timezone. +This example will add a 'LIVESLAK ISO' menu entry to your local computer's boot menu, through which you can start a downloaded XFCE Live ISO pre-configured for a US keyboard, Dutch language and Amsterdam timezone. You should of course change the "''bootparms''" string so that it matches your requirements.
  
 ==== Transfering ISO content to USB stick ==== ==== Transfering ISO content to USB stick ====
Line 464: Line 463:
   equivalent to parameter "toram".   equivalent to parameter "toram".
  
-toram=core => Load Console OS modules into RAM. Console-only Slackware +toram=core => 
-  loads fast, contains 'setup2hd' and frees up your USB drive so you can +  Load Console OS modules into RAM. 
-  overwrite it with a Persistent Live OS.+  Console-only Slackware loads fast, contains 'setup2hd' and frees up your USB drive 
 +  so you can overwrite it with a Persistent Live OS.
  
 toram=os => toram=os =>
Line 883: Line 883:
 #} #}
 </code> </code>
 +
 +=== Customizing the list of used packages ===
 +
 +Any liveslak ISO variant contains a specific set of Slackware packages, as defined in the various ''SEQ_*'' variables used in the ''make_slackware_live.sh'' script.  Your customized Live OS will be using variable "''SEQ_CUSTOM''".
 +
 +Let's breakdown the definition of such a variable to explain how to customize the package set for your own live ISO.
 +
 +The list of packages in the MATE ISO for instance, is defined by the ''SEQ_MSB'' variable (//MSB// stands for //Mate Slack Build//).  Its value is as follows: <code>
 +# grep ^SEQ_MSB make_slackware_live.sh
 +SEQ_MSB="tagfile:a,ap,d,e,f,k,l,n,t,tcl,x,xap,xfce,y pkglist:slackextra,mate local:slackpkg+"</code>
 +
 +Three keywords can be identified in the value of a ''SEQ_*'' variable, and these determine where the packages to be installed are going to be searched for:
 +  * tagfile - this is an Slackware tagfile for a complete package series.  For instance, using "tagfile:ap" means: install all packages in the **AP** series.
 +  * pkglist - this is a list of packages to be installed from the Slackware distro itself or from a Slackware-compatible 3rd-party repository.  The file containing that package list is searched in the ''./pkglists/'' subdirectory of the liveslak toplevel directory.  For instance, using "pkglist:mate" means: install all packages mentioned in the file ''./pkglists/mate.lst''.  If there is no matching ''./pkglists/mate.conf'' file then the packages are assumed to be present in the Slackware distro directory.  Else the ".conf" file is parsed and the variables that are defined in the ".conf" file will be used while generating the ISO.  Most importantly, "''SL_REPO_URL''" will contain the rsync URI pointing to the 3rd-party repository where the requested packages can be downloaded.
 +  * local - some packages can not be found in Slackware-compatible repositories.  The "local" keyword alows you to install packages from a subdirectory of the liveslak toplevel directory.  For instance, using "local:slackpkg+" means: install all packages found in subdirectory ''./local/slackpkg+/'' or if you are generating a 64bit live ISO, install all packages found in directory ''./local64/slackpkg+/''.
 +
 +For the value of a ''SEQ_*'' variable, any combination of these keywords can be used. Every keyword is followed by a colon, and that is followed by a comma-separated list of relevant package definitions. They are all separated by spaces.
  
 === Custom background images === === Custom background images ===
Line 970: Line 987:
   * The four digits of a modulename have a meaning.  Some ranges are claimed by the core OS, so please do not use them. Their prefixes are based on the package source: <code>   * The four digits of a modulename have a meaning.  Some ranges are claimed by the core OS, so please do not use them. Their prefixes are based on the package source: <code>
     0000 = contains the Slackware /boot directory     0000 = contains the Slackware /boot directory
 +    0005 = Console OS modules when explicitly enabled for a regular ISO installed otherwise from Slackware tagfiles
     0010-0019 = packages installed from a Slackware tagfile (a,ap,d, ... , y series)     0010-0019 = packages installed from a Slackware tagfile (a,ap,d, ... , y series)
     0020-0029 = packages installed from a package list as found in the ./pkglists subdirectory of the liveslak sources (min, noxbase, x_base, xapbase, xfcebase etc)     0020-0029 = packages installed from a package list as found in the ./pkglists subdirectory of the liveslak sources (min, noxbase, x_base, xapbase, xfcebase etc)

Trace:

QR Code
QR Code slackware:liveslak (generated for current page)