path: root/README.txt
diff options
author Eric Hameleers <>2016-04-13 21:58:16 +0200
committer Eric Hameleers <>2016-04-13 21:58:16 +0200
commit24aa0e77fab13ad6186e86c7d7d83891dae30d89 (patch)
tree71f8318d26d2d9c31b62e1b6400215169e6e7d97 /README.txt
parent6dfb4058af8a59c17aeeb80b567ce521f6ace59b (diff)
README.txt updated for the network boot (NFS root) functionality.
Diffstat (limited to 'README.txt')
1 files changed, 41 insertions, 0 deletions
diff --git a/README.txt b/README.txt
index 6d25257..cae5109 100644
--- a/README.txt
+++ b/README.txt
@@ -103,6 +103,33 @@ Examples:
You might have noticed that the "-P" parameter does not accept a size parameter. This is because the unencrypted container file is created as a 'sparse' file that starts at zero size and is allowed to grow dynmically to a maximum of 90% of the initial free space on the Linux partition of the USB stick.
+==== PXE booting the Live OS ====
+Slackware Live Edition can do a network boot boot using PXE protocol off a NFS export. Extract the content of the ISO to (for instance) a new directory called ''slackware-live'' below your TFTP server's ''/tftproot'' directory and export that directory via NFS. Then add lines like this to your ''pxelinux.cfg/default'' file (assuming your NFS server has IP address ''''): <code>
+label liveslak
+kernel slackware-live/boot/generic
+append initrd=slackware-live/boot/initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 kbd=us tz=Europe/Amsterdam locale=us_EN.utf8 nfsroot= hostname=pxelive
+As shown in the example above, a boot parameter ''nfsroot'' is used for network boot. The parameter value defines the IP address of your NFS server and the path of the NFS export where you extracted the Slackware Live ISO. Hint: to get a listing of the exported shares of your NFS server, run ''showmount -e localhost'' on the NFS server.
+Actually, two boot parameters are available to properly support network boot. A second boot parameter ''nic'' can be used to define the characteristics of your Live environment's network configuration, like the name of the network interface, static IP adress and such. If you are on a network where a DHCP server configures your clients, then the ''nic'' parameter will not be needed as Slackware Live Edition will figure out all the details by itself.
+Syntax of these two parameters:
+ nic=<driver>:<interface>:<dhcp|static>[:ipaddr:netmask[:gateway]]
+Example uses of the two network boot parameters:
+ nfsroot=
+ nic=auto:eth0:dhcp
+ nic=auto:eth0:static:
+ nic=:eth1:static:
+After you have setup your PXE environment (DHCP, TFTP and NFS servers) properly using the above information, boot one of your PXE-capable computers, interrupt the boot and select "network boot" and type or select the appropriate label (in the above example, that would be ''liveslak''). You will see the kernel and initrd being downloaded and booted, and then the Live OS will start just as if it was running from a local medium.
+Persistence is not supported in this configuration; currently the overlayfs does not support NFS as a writable layer in the live filesystem.
==== Boot parameters explained ====
@@ -141,6 +168,20 @@ noload=mod1[,mod2[...]] => Prevent loading of one or more
squashfs modules from the directory "/liveslak/addons".
By default all these "addon" modules are loaded on boot.
+=== Network boot ===
+ =>defines the IP address
+ of the NFS server, and the path to the extracted content
+ of Slackware Live Edition.
+ => network device customization, usually this parameter is
+ not needed when your network runs a DHCP server.
+ Specify a driver if UDEV does not detect the device. Specify the
+ interface if Slackware Live can not figure it out. If you specify
+ 'static' you need to also specify ipaddr and netmask. The gateway
+ is optional but needed to access the internet for instance.
=== Hardware related ===
localhd => initialize RAID/LVM on local hard drives.