Slackware malignant fibrous histiocytoma treatment liveslak – slackdocs

Slackware Live Edition can do a network boot boot using malignant fibrous histiocytoma treatment 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 192.168.0.1):

Actually, two boot parameters are available to properly support network boot. A second boot parameter nic can be used to define malignant fibrous histiocytoma treatment 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 malignant fibrous histiocytoma treatment configures your clients, then the nic parameter will not be needed as Slackware malignant fibrous histiocytoma treatment Live Edition will figure out all the details by itself.

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 malignant fibrous histiocytoma treatment booted, and then the Live OS will start just as if malignant fibrous histiocytoma treatment it was running from a local medium.

If your DHCP server takes too long in acknowledging the malignant fibrous histiocytoma treatment client’s request, the DHCP client times out and the boot of your malignant fibrous histiocytoma treatment Live OS will fail because the NFS-mounted Live filesystem will not become available. In that case you can try increasing the wait time malignant fibrous histiocytoma treatment before the DHCP client decides that it is not going malignant fibrous histiocytoma treatment to get an IP address from the server. Add the boot parameter dhcpwait=30 (example value) where the number 30 is the number of seconds the malignant fibrous histiocytoma treatment DHCP client should wait for a server response. You should of course pick a value that is sufficiently malignant fibrous histiocytoma treatment large for your network setup.

A practical example would be that your bring a USB malignant fibrous histiocytoma treatment stick with Slackware Live Edition to a LAN party, use it to boot one of the computers and then malignant fibrous histiocytoma treatment all the other computers in the (wired) LAN will be able to do a network boot and malignant fibrous histiocytoma treatment run the same Slackware Live Edition a couple of minutes malignant fibrous histiocytoma treatment later. The computer with the USB stick will act as the malignant fibrous histiocytoma treatment PXE server and all the other computers will be its malignant fibrous histiocytoma treatment PXE clients, reading the Slackware data off that USB stick. The clients will inherit the server’s timezone,language and keyboard settings by default but those can be malignant fibrous histiocytoma treatment overridden. The PXE clients will not have ‘persistence’. If the server has access to the Internet, the clients will have access as well.

When you boot the Live OS you can then start malignant fibrous histiocytoma treatment a script “pxeserver” from the console in runlevel 3 or from an X malignant fibrous histiocytoma treatment terminal in runlevel 4. The script will gather all required information and if it malignant fibrous histiocytoma treatment is unable to figure something out by itself it will malignant fibrous histiocytoma treatment ask you. If it is unable to figure out the wired network malignant fibrous histiocytoma treatment interface that it should use, you can add the name of your interface (for instance, eth1) as a single parameter to the script when you start malignant fibrous histiocytoma treatment it.

The PXE server uses dnsmasq to offer DNS to the malignant fibrous histiocytoma treatment PXE clients. The dnsmasq program will enable its internal DHCP server capabilities malignant fibrous histiocytoma treatment if your LAN does not have its own DHCP server. Dnsmasq will also start a TFTP server which the PXE malignant fibrous histiocytoma treatment clients will connect to in order to retrieve the boot malignant fibrous histiocytoma treatment files (kernel and initrd). The pxeserver script also starts a NFS server which will malignant fibrous histiocytoma treatment be used by the Live initrd to obtain the squashfs malignant fibrous histiocytoma treatment modules and boot the Live OS. If your PXE server has multiple network interfaces, for instance a wireless interface which is connected to the malignant fibrous histiocytoma treatment outside world and a wired interface connected to another computer malignant fibrous histiocytoma treatment which will become a PXE client (or indeed connected to a switch with a whole bunch malignant fibrous histiocytoma treatment of prospective PXE clients behind that) then the PXE server will setup packet forwarding so that malignant fibrous histiocytoma treatment the PXE clients will be able to access the outside malignant fibrous histiocytoma treatment world through the wired interface and out to that other malignant fibrous histiocytoma treatment interface.

If you have multiple network interfaces, it is important to know that dnsmasq will only bind malignant fibrous histiocytoma treatment to the interface where you want PXE clients to connect malignant fibrous histiocytoma treatment to. In a multi-NIC situation where a second NIC is connected to the malignant fibrous histiocytoma treatment outside world (your local network), this means that the DHCP/ DNS server started by dnsmasq will not interfere with an malignant fibrous histiocytoma treatment existing DHCP server in your local network.

RELATED POSTS