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 revision Previous revision
Next revision
Previous revision
slackware:liveslak [2017/09/23 17:40 (UTC)]
alienbob [ISO variants] updated with studioware and dlackware.
slackware:liveslak [2019/11/13 21:55 (UTC)] (current)
alienbob [Sources] URL fixes
Line 10: Line 10:
 Slackware Live Edition does not have to be installed to a computer hard drive (//however you do have that choice if you want to: using the ''​setup2hd''​ script//​). ​ You can carry the USB stick version with you in your pocket. ​ You'll have a pre-configured Slackware OS up & running in a minute wherever you can get your hands on a computer with a USB port. Slackware Live Edition does not have to be installed to a computer hard drive (//however you do have that choice if you want to: using the ''​setup2hd''​ script//​). ​ You can carry the USB stick version with you in your pocket. ​ You'll have a pre-configured Slackware OS up & running in a minute wherever you can get your hands on a computer with a USB port.
  
-The USB version is "​persistent"​ - meaning that the OS stores your updates on the+Liveslak is a directory tree containing scripts, bitmaps and configuration files. ​ Only 6 scripts are meant to be run by you, the user.  These scripts ("​make_slackware_live.sh",​ "​iso2usb.sh",​ "​makemod",​ "​setup2hd",​ "​pxeserver"​ and "​upslak.sh) are explained in more detail in the section "​Scripts and tools" higher up.  When creating a Live ISO from scratch, you only need to run the "​make_slackware_live.sh"​ script. +The USB version is "​persistent"​ - meaning that the OS stores your updates on the USB stick. ​ The CD/DVD versions (and the USB stick if you configure it accordingly) operate without persistence,​ which means that all the changes you make to the OS are lost when you reboot.
- USB stick. ​ The CD/DVD versions (and the USB stick if you configure it accordingly) operate without persistence,​ which means that all the changes you make to the OS are lost when you reboot.+
  
 In order to protect your sensitive private data in case you lose your USB stick (or in case it gets stolen) you can enhance your persistent USB Live OS with an encrypted homedirectory and/or an encrypted persistence file, to be unlocked on boot with a passphrase that only you know. In order to protect your sensitive private data in case you lose your USB stick (or in case it gets stolen) you can enhance your persistent USB Live OS with an encrypted homedirectory and/or an encrypted persistence file, to be unlocked on boot with a passphrase that only you know.
Line 47: Line 46:
  
 Common download locations are: Common download locations are:
-  * Primary site: http://bear.alienbase.nl/mirrors/​slackware-live/​ (%%rsync://bear.alienbase.nl/​mirrors/​slackware-live/​%%)+  * Primary site: http://slackware.nl/​slackware-live/​ (%%rsync://slackware.nl/​mirrors/​slackware-live/​%%)
   * Darren'​s http://​slackware.uk/​people/​alien-slacklive/​ (%%rsync://​slackware.uk/​people/​alien-slacklive/​%%)   * Darren'​s http://​slackware.uk/​people/​alien-slacklive/​ (%%rsync://​slackware.uk/​people/​alien-slacklive/​%%)
   * Willy'​s http://​repo.ukdw.ac.id/​slackware-live/​   * Willy'​s http://​repo.ukdw.ac.id/​slackware-live/​
Line 99: Line 98:
 Editing a Grub menu before booting it is possible by pressing the "​e"​ key.  After making your changes to the boot commandline,​ press <F10> to boot.  To discard your changes, press <​ESC>​. Editing a Grub menu before booting it is possible by pressing the "​e"​ key.  After making your changes to the boot commandline,​ press <F10> to boot.  To discard your changes, press <​ESC>​.
  
-Another difference between Syslinux and Grub2 menus: in Grub2 you can select a non-US keyboard, language and/or timezone and you will return to the main menu every time.  You still have to select "Start SLACKWARE Live" to boot the computer. ​ In the Syslinux menu, only the keyboard selection menu will return you to the main menu.  Any non-US *language* selection on the other hand will boot you into Slackware Live immediately;​ without returning to the main menu.  This is a limitation of syslinux which would require exponentially more menu files to construct ​ a menu with more choices. ​ Grub2 supports variables which make it easy to modify a menu entry'​s characteristics.+Another difference between Syslinux and Grub2 menus: in Grub2 you can select a non-US keyboard, language and/or timezone and you will return to the main menu every time.  You still have to select "Start SLACKWARE Live" to boot the computer. ​ In the Syslinux menu, only the keyboard selection menu will return you to the main menu.  Any non-US *language* selection on the other hand will boot you into Slackware Live immediately;​ without returning to the main menu.  This is a limitation of syslinux which would require exponentially more menu files to construct a menu with more choices. ​ Grub2 supports variables which make it easy to modify a menu entry'​s characteristics.
  
  
Line 107: Line 106:
 A script is available which allows you to transfer the ISO image content to a USB stick, making some modifications depending on the script'​s parameters. A script is available which allows you to transfer the ISO image content to a USB stick, making some modifications depending on the script'​s parameters.
  
-The USB stick will be erased and re-formatted when running this script (except when using the '​-r'​ refresh ​optoin)!  Before inflicting any irreversible damage, the script will show you a prompt at which point you can evaluate whether it is safe to continue.+The USB stick will be erased and re-formatted when running this script (except when using the '​-r'​ refresh ​option)!  Before inflicting any irreversible damage, the script will show you a prompt at which point you can evaluate whether it is safe to continue.
  
 This script, called '​iso2usb.sh',​ accepts the following parameters: <​code>​ This script, called '​iso2usb.sh',​ accepts the following parameters: <​code>​
Line 186: Line 185:
     # ./upslak.sh -d     # ./upslak.sh -d
   * Updating kernel and modules, providing two packages as input and assuming the USB stick is known as /dev/sdX:   * Updating kernel and modules, providing two packages as input and assuming the USB stick is known as /dev/sdX:
-    # ./upslak.sh -o /dev/sdX -m kernel-modules-4.9.50-x86_64-1.txz -k kernel-generic-4.9.50-x86_64-1.txz+    # ./upslak.sh -o /dev/sdX -m kernel-modules-4.19.0-x86_64-1.txz -k kernel-generic-4.19.0-x86_64-1.txz
   * Restore the previous kernel and modules after a failed update, and let the script scan your computer for the insertion of your USB stick:   * Restore the previous kernel and modules after a failed update, and let the script scan your computer for the insertion of your USB stick:
     # ./upslak.sh -s -r     # ./upslak.sh -s -r
Line 339: Line 338:
  
 === Media tweaks === === Media tweaks ===
 +
 +cfg=[skip|write] =>
 +  Specify '​skip'​ to skip disk-based configuration file containing
 +  OS parameters; or specify '​write'​ to write current OS parameters
 +  to disk.
  
 hostname=your_custom_hostname[,​qualifier] => hostname=your_custom_hostname[,​qualifier] =>
Line 420: Line 424:
   * The boot/ directory contains the syslinux configuration used when the Live OS boots on a computer with a BIOS.  This directory also contains the kernel and initrd files which are used to actually boot the OS.   * The boot/ directory contains the syslinux configuration used when the Live OS boots on a computer with a BIOS.  This directory also contains the kernel and initrd files which are used to actually boot the OS.
   * The liveslak/ directory contains all the squashfs modules which are used to assemble the filesystem of the Live OS, as well as files that are copied directly into the root of the Live filesystem. ​ It contains four subdirectories:​   * The liveslak/ directory contains all the squashfs modules which are used to assemble the filesystem of the Live OS, as well as files that are copied directly into the root of the Live filesystem. ​ It contains four subdirectories:​
-    * addons/ - modules which are stored in this directory will always be added the Live filesystem unless you prevent that with a "​noload="​ boot parameter;+    * addons/ - modules which are stored in this directory will always be added to the Live filesystem unless you prevent that with a "​noload="​ boot parameter;
     * optional/ - modules in this directory will not be added to the filesystem of the Live OS unless you force this with a "​load="​ boot parameter;     * optional/ - modules in this directory will not be added to the filesystem of the Live OS unless you force this with a "​load="​ boot parameter;
     * system/ - this directory contains all the modules which were created by the "​make_slackware_live.sh"​ script. ​ All these modules are numbered and the Live init script will use that to re-assemble the Live filesystem in the exact same order as they were created initially.     * system/ - this directory contains all the modules which were created by the "​make_slackware_live.sh"​ script. ​ All these modules are numbered and the Live init script will use that to re-assemble the Live filesystem in the exact same order as they were created initially.
Line 449: Line 453:
  
   * The script reads a package sequence for the Live variant and installs all packages in this sequence to subdirectories of a temporary directory tree.   * The script reads a package sequence for the Live variant and installs all packages in this sequence to subdirectories of a temporary directory tree.
-  * Every Slackware package set (a, ap, d, ... , y) or package list (min, xbase, xapbase, ...) is installed into a separate '​root'​ directory.+  * Every Slackware package set (a, ap, d, ... , y) or package list (min, noxbase, x_base, xapbase, ...) is installed into a separate '​root'​ directory.
   * Each of those root directories is "​squashed"​ (using squashfs) into a separate squashfs module. ​ Such a module is a single archive file containing the compressed directory structure of the installed packages.   * Each of those root directories is "​squashed"​ (using squashfs) into a separate squashfs module. ​ Such a module is a single archive file containing the compressed directory structure of the installed packages.
   * These module files are subsequently loop-mounted and then combined together into a single read-only directory structure using an "​overlay mount"​. ​ The overlayfs is relatively new; earlier Live distros have been using aufs and unionfs to achieve similar functionality,​ but those were not part of any stock kernel source and therefore custom kernels had to be compiled for such a Live distro.   * These module files are subsequently loop-mounted and then combined together into a single read-only directory structure using an "​overlay mount"​. ​ The overlayfs is relatively new; earlier Live distros have been using aufs and unionfs to achieve similar functionality,​ but those were not part of any stock kernel source and therefore custom kernels had to be compiled for such a Live distro.
Line 473: Line 477:
     * a locate database is created,     * a locate database is created,
     * etc...     * etc...
-  * All these modifications are written to the writable filesystem that was created in the previous section. This filesystem will also be stored on the ISO as a squashfs module and when the Live OS boots, it will be mounted read-only just like all the other modules. Its name will be "​0099-slackware_zzzconf-current-x86_64.sxz"​ or more generically "​0099-slackware_zzzconf-$SLACKVERSION}-${ARCH}.sxz"​+  * All these modifications are written to the writable filesystem that was created in the previous section. This filesystem will also be stored on the ISO as a squashfs module and when the Live OS boots, it will be mounted read-only just like all the other modules. Its name will be "​0099-slackware_zzzconf-current-x86_64.sxz"​ or more generically "​0099-slackware_zzzconf-${SLACKVERSION}-${ARCH}.sxz"​
  
  
Line 504: Line 508:
  
 This section explains how the script modifies the ISO for the enhanced USB functionality. This section explains how the script modifies the ISO for the enhanced USB functionality.
 +
 +== Layout of the USB stick ==
 +
 +The "​iso2usb.sh"​ script wipes and re-partitions the USB stick unless the "​-r"​ or //refresh// parameter is used.  See section "​[[#​transfering_iso_content_to_usb_stick|Transfering ISO content to USB stick]]"​ for an explanation of all commandline switches. \\ The script will create 3 partitions:
 +
 +  * First partition: a small (1 MB in size) FAT partition which  is not used for Slackware Live Edition. ​ It can be used by an alternative bootloader if needed. ​ You can also store your LUKS keyfile on it to unlock a LUKS-encrypted Slackware Linux computer (see the [[http://​ftp.osuosl.org/​pub/​slackware/​slackware64-current/​README_CRYPT.TXT|README_CRYPT.TXT]] file on your Slackware DVD for more information on LUKS keyfiles).
 +  * Second partition: a 100 MB VFAT partition containing the kernel, initrd and all the other stuff required by syslinux and grub2 to boot Slackware Live Edition.
 +  * Third partition: a Linux partition taking up all of the remaining space. It contains the actual liveslak modules, the persistent live storage and optionally your encrypted homedirectory. You can use the remainder of this Linux //ext4// filesystem'​s free space to store anything you like.
 +
 +Note that this script is the only supported method of transfering the liveslak ISO content to a USB stick and make that USB stick into a persistent live OS.  Several 3rd party tools (like multibootusb,​ rufus, unetbootin) that claim to be able to mix several Live OS'es on a single USB stick and make them all work in a multi-boot setup, are not currently supporting liveslak.
  
 == Mounting a filesystem in an encrypted container == == Mounting a filesystem in an encrypted container ==
Line 587: Line 601:
 This section explains how the script modifies the content of the Live USB stick. This section explains how the script modifies the content of the Live USB stick.
  
-When the script is started, it will do some sanity checks and then extracts the comtent ​of the initrd image. Some characteristics of the initrd will be recorded:+When the script is started, it will do some sanity checks and then extracts the content ​of the initrd image. Some characteristics of the initrd will be recorded:
   * existence of previously backed-up kernel modules is checked,   * existence of previously backed-up kernel modules is checked,
   * template variables and their values are obtained from the init sctript,   * template variables and their values are obtained from the init sctript,
Line 612: Line 626:
 == Replace the liveslak init script == == Replace the liveslak init script ==
  
-The init script inside the initrd image is the core of liveslak. ​ The init script prepares the Live filesystem and configures several run-time OS parameters. ​ If you have made modifications to this init script you can easily replace the default init script with yourw own script using the '​-i'​ option. ​ The "​upslak.sh"​ script is smart enough to recognize a iveslak template as input. ​ The "​.tpl"​ extension of some liveslak files means that these are templates. ​ They are not usable as-is, because they contain placeholder strings like "​@VERSION@ or "​@DISTRO@"​ that first need to be replaced with real values. ​ The "​upslak.sh"​ script will take care of these substitutions.+The init script inside the initrd image is the core of liveslak. ​ The init script prepares the Live filesystem and configures several run-time OS parameters. ​ If you have made modifications to this init script you can easily replace the default init script with your own script using the '​-i'​ option. ​ The "​upslak.sh"​ script is smart enough to recognize a iveslak template as input. ​ The "​.tpl"​ extension of some liveslak files means that these are templates. ​ They are not usable as-is, because they contain placeholder strings like "​@VERSION@" ​or "​@DISTRO@"​ that first need to be replaced with real values. ​ The "​upslak.sh"​ script will take care of these substitutions.
  
 == Wrap persistence data into a new squashfs module == == Wrap persistence data into a new squashfs module ==
Line 626: Line 640:
 You also need the "​liveslak"​ script collection which can be downloaded from any of the [[#​liveslak_sources|links at the bottom of this page]]. You also need the "​liveslak"​ script collection which can be downloaded from any of the [[#​liveslak_sources|links at the bottom of this page]].
  
-Liveslak is a directory tree containing scripts, bitmaps and configuration files. ​ Only scripts are meant to be run by you, the user.  These scripts ("​make_slackware_live.sh",​ "​iso2usb.sh",​ "​makemod",​ "​setup2hd",​ "​pxeserver"​ and "​upslak.sh"​) are explained in more detail in the section "​[[#​scripts_and_tools|Scripts and tools]]"​ higher up.  When creating a Live ISO from scratch, you only need to run the "​make_slackware_live.sh"​ script.+Liveslak is a directory tree containing scripts, bitmaps and configuration files. ​ Only scripts are meant to be run by you, the user.  These scripts ("​make_slackware_live.sh",​ "​iso2usb.sh",​ "​makemod",​ "​setup2hd",​ "​pxeserver"​ and "​upslak.sh"​) are explained in more detail in the section "​[[#​scripts_and_tools|Scripts and tools]]"​ higher up.  When creating a Live ISO from scratch, you only need to run the "​make_slackware_live.sh"​ script.
  
  
Line 655: Line 669:
     * locale = the locale used in the country     * locale = the locale used in the country
     * xkb = optional custom X keyboard variant for the language     * xkb = optional custom X keyboard variant for the language
-  * liveinit - this is the "​init"​ script which is copied into the initrd image for the Live OS.  Together with the Slackware generic kernel, the initrd is what boots the computer. The "​init"​ script assembles the Live filesystem from its squashfs modules.+  * liveinit.tpl - this is the template for the "​init"​ script which is copied into the initrd image for the Live OS.  Together with the Slackware generic kernel, the initrd is what boots the computer. The "​init"​ script assembles the Live filesystem from its squashfs modules.
   * make_slackware_live.conf - the configuration file for the "​make_slackware_live.sh"​ script. ​ You can define defaults for many script parameters here so that you do not have to edit the script itself.   * make_slackware_live.conf - the configuration file for the "​make_slackware_live.sh"​ script. ​ You can define defaults for many script parameters here so that you do not have to edit the script itself.
   * make_slackware_live.sh - the script that generates the Live ISO.   * make_slackware_live.sh - the script that generates the Live ISO.
   * makemod - this script creates a squashfs module out of a Slackware package (or out of a directory tree).   * makemod - this script creates a squashfs module out of a Slackware package (or out of a directory tree).
   * menu.tpl - template which is used to generate the syslinux boot menu for BIOS computers.   * menu.tpl - template which is used to generate the syslinux boot menu for BIOS computers.
-  * pxeserver - the script that starts a PXE server allowing other computers to boot Slackware Live over the network. +  * pxeserver.tpl template to generate ​the script that starts a PXE server allowing other computers to boot Slackware Live over the network. 
-  * setup2hd - the script you use to install your Slackware Live to a harddisk.+  * setup2hd.tpl  ​template to generate ​the script you use to install your Slackware Live to a harddisk.
   * setup2hd.local - here a developer of a custom Live OS can override the default post-installation routine by (re-)defining the function "​live_post_install()"​ in the ''​setup2hd''​ script.   * setup2hd.local - here a developer of a custom Live OS can override the default post-installation routine by (re-)defining the function "​live_post_install()"​ in the ''​setup2hd''​ script.
  
Line 673: Line 687:
  -a arch            Machine architecture (default: x86_64).  -a arch            Machine architecture (default: x86_64).
                     Use i586 for a 32bit ISO, x86_64 for 64bit.                     Use i586 for a 32bit ISO, x86_64 for 64bit.
 + -c comp            Squashfs compression (default: xz).
 +                    Can be any of 'gzip lzma lzo xz zstd'.
  -d desktoptype ​    ​SLACKWARE (full Slack), KDE4 (basic KDE4),  -d desktoptype ​    ​SLACKWARE (full Slack), KDE4 (basic KDE4),
-                    XFCE (basic XFCE), PLASMA5 (full Plasma5 replaces KDE4),+                    XFCE (basic XFCE), PLASMA5 (KDE Plasma5 replaces KDE4),
                     MATE (Gnome2 fork replaces KDE4), CINNAMON (fork of Gnome3                     MATE (Gnome2 fork replaces KDE4), CINNAMON (fork of Gnome3
-                    Shell replaces KDE4).+                    Shell replaces KDE4), DLACK (adds Gnome3, PAM and systemd).
  ​-e ​                Use ISO boot-load-size of 32 for computers  ​-e ​                Use ISO boot-load-size of 32 for computers
                     where the ISO won't boot otherwise (default: 4).                     where the ISO won't boot otherwise (default: 4).
  ​-f ​                ​Forced re-generation of all squashfs modules,  ​-f ​                ​Forced re-generation of all squashfs modules,
                     custom configurations and new initrd.img.                     custom configurations and new initrd.img.
 + -l <​localization> ​ Enable a different default localization
 +                    (script-default is '​us'​).
  -m pkglst[,​pkglst] Add modules defined by pkglists/<​pkglst>,​...  -m pkglst[,​pkglst] Add modules defined by pkglists/<​pkglst>,​...
  -r series[,​series] Refresh only one or a few package series.  -r series[,​series] Refresh only one or a few package series.
Line 696: Line 714:
 The script uses package repositories to create a Live ISO.  The packages will be installed into a temporary directory. The script uses package repositories to create a Live ISO.  The packages will be installed into a temporary directory.
  
-In order to create a Live ISO for any of these variants, the package repositories that are required must be available as a local directory (this can be a network-mounted directory).  ​//A local mirror ​of the Slackware repository ​is mandatory - you have to download these yourself//​. ​ Any other packages, i.e. those that are used from a 3rd party repository will be downloaded from a remote server as long as a rsync URL for the repository is configured in ./​pkglists/​*.conf.+In order to create a Live ISO for any of these variants, the package repositories that are required must be available as a local directory (this can be a network-mounted directory).  ​If you have not mirrored them locally, then all packages ​of the Slackware repository ​as well as those you require ​from  a 3rd party repository will be downloaded from a remote server as long as a rsync URL for the repository is configured in ./​pkglists/​*.conf.
  
 When all pre-reqs are met, you issue a single command to generate the ISO.  The following example will create a pure Slackware Live Edition: When all pre-reqs are met, you issue a single command to generate the ISO.  The following example will create a pure Slackware Live Edition:
Line 716: Line 734:
 You can create your own custom Live OS by changing its characteristics in the configuration file "''​make_slackware_live.conf''"​. You can create your own custom Live OS by changing its characteristics in the configuration file "''​make_slackware_live.conf''"​.
 Among the things you can change are: Among the things you can change are:
-  * The name of the Desktop variant (the script itself knows "//​SLACKWARE//",​ "//​PLASMA5//",​ "//​XFCE//",​ "//​MATE//" ​and "//​CINNAMON//"​),​+  * The name of the Desktop variant (the script itself knows "//​SLACKWARE//",​ "//​PLASMA5//",​ "//​XFCE//",​ "//​MATE//"​"//​CINNAMON//", "//​STUDIOWARE//"​ and  "//​DLACK//"),
   * The list(s) of packages used for your custom distribution,​   * The list(s) of packages used for your custom distribution,​
   * The name of the useraccount (by default that is "//​live//"​),​   * The name of the useraccount (by default that is "//​live//"​),​
Line 732: Line 750:
 # and "​pkglists/​cinelerra.lst"​ defining the package location and package list # and "​pkglists/​cinelerra.lst"​ defining the package location and package list
 # respectively):​ # respectively):​
-#​SEQ_CUSTOM="​min,​xbase,​xapbase,​xfcebase,​cinelerra"​+#​SEQ_CUSTOM="​min,​noxbase,​x_base,​xapbase,​xfcebase,​cinelerra"​
  
 # OPTIONAL: # OPTIONAL:
Line 826: Line 844:
     0000 = contains the Slackware /boot directory     0000 = contains the Slackware /boot directory
     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, xbase, 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)
     0030-0039 = a '​local'​ package, i.e. a package found in subdirectory ./local or ./local64 (depending on architecture)     0030-0039 = a '​local'​ package, i.e. a package found in subdirectory ./local or ./local64 (depending on architecture)
     0099 = liveslak configuration module (contaning all the customizations that change the installed packages into a usable Live OS) </​code>​     0099 = liveslak configuration module (contaning all the customizations that change the installed packages into a usable Live OS) </​code>​
Line 846: Line 864:
 Website: https://​www.slax.org/​ Website: https://​www.slax.org/​
  
-SLAX was the original Live variant of Slackware. ​ The linux-live scripts which are used to create a SLAX ISO were generalized so that they can create a Live version of any OS that is already installed to a harddrive. ​ SLAX development stalled a couple of years ago but its creator seems to have warmed up recently.+SLAX was the original Live variant of Slackware. ​ The linux-live scripts which are used to create a SLAX ISO were generalized so that they can create a Live version of any OS that is already installed to a harddrive. ​ SLAX development stalled a couple of years ago. \\ In 2017 a new release of SLAX became available, however Slackware is no longer ​its parent OS. New SLAX releases are based on Debian.
  
 The Live functionality of SLAX is based on aufs and unionfs which requires a custom-built kernel with aufs support compiled-in. ​ It is small and has its boot scripts tweaked for startup speed. The Live functionality of SLAX is based on aufs and unionfs which requires a custom-built kernel with aufs support compiled-in. ​ It is small and has its boot scripts tweaked for startup speed.
Line 880: Line 898:
 Website: http://​slackex.exton.net/​ Website: http://​slackex.exton.net/​
  
-A website offering Live versions based on many regular Linux distributions. ​ The SlackEX version is loosely based on Slackware with a custom kernel and some tools that are not part of Slackware itself. ​ I was unable to find the sources for this live distro.+A website offering Live versions based on many regular Linux distributions. ​ The SlackEX version is loosely based on Slackware with a custom kernel and some tools that are not part of Slackware itself. ​ I was unable to find the sources for this live distro. Its creator stopped SlackEX development in December 2017.
  
  
Line 888: Line 906:
 Slackware Live Edition is created by the '​liveslak'​ scripts developed and maintained by Eric Hameleers aka Alien BOB [[alien@slackware.com]]. Slackware Live Edition is created by the '​liveslak'​ scripts developed and maintained by Eric Hameleers aka Alien BOB [[alien@slackware.com]].
  
-  * Git repository: %%git://bear.alienbase.nl/​liveslak.git%% +  * Git repository: %%git://slackware.nl/​liveslak.git%% 
-  * Git repository (browsable):​ http://bear.alienbase.nl/cgit/liveslak/+  * Git repository (browsable):​ http://git.slackware.nl/​liveslak/​
   * Download mirror: http://​www.slackware.com/​~alien/​liveslak/​   * Download mirror: http://​www.slackware.com/​~alien/​liveslak/​
  
Line 895: Line 913:
 ====== Sources ====== ====== Sources ======
 <!-- If you copy information from another source, then specify that source --> <!-- If you copy information from another source, then specify that source -->
-  * Original source: [[http://bear.alienbase.nl/cgit/​liveslak/​tree/​README.txt]]+  * Original source: [[https://git.slackware.nl/​liveslak/​tree/​README.txt]] 
 +  * Project landing page: [[https://​alien.slackbook.org/​blog/​slackware-live-edition/​]]
 <!-- Authors are allowed to give credit to themselves! --> <!-- Authors are allowed to give credit to themselves! -->
   * Originally written by [[wiki:​user:​alienbob | Eric Hameleers]]   * Originally written by [[wiki:​user:​alienbob | Eric Hameleers]]
-<!-- * Contrbutions ​by [[wiki:​user:​yyy | User Y]] -->+<!-- * Contributions ​by [[wiki:​user:​yyy | User Y]] -->
  
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must also remove the tag-word "​template"​ below. Otherwise your page will not show up in the Table of Contents --> <!-- You must also remove the tag-word "​template"​ below. Otherwise your page will not show up in the Table of Contents -->
 {{tag>​slackware live author_alienbob}} {{tag>​slackware live author_alienbob}}

In Other Languages
QR Code
QR Code slackware:liveslak (generated for current page)