Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
slackware:pxe [2006/09/27 21:18] – Updated documentation about creating the initrd.img alien | slackware:pxe [2006/10/01 20:41] – Another typo fixed (tnaks volkerdi!). alien | ||
---|---|---|---|
Line 2: | Line 2: | ||
- | When the time comes to install Slackware on your computer, you have a limited number of options regarding the location of your Slackware packages. Either | + | When the time comes to install Slackware on your computer, you have a limited number of options regarding the location of your Slackware packages. Either |
The number of possible options for booting your Slackware installer is similarly limited: either you boot your computer from the bootable first CDROM of the Slackware CD set, or from the DVD, or (in those cases where the computer BIOS refuses to recognize the CD as bootable) create boot/root floppies and boot from those. There is even loadlin, the DOS based Linux starter, but let's not concern ourselves with the past today. | The number of possible options for booting your Slackware installer is similarly limited: either you boot your computer from the bootable first CDROM of the Slackware CD set, or from the DVD, or (in those cases where the computer BIOS refuses to recognize the CD as bootable) create boot/root floppies and boot from those. There is even loadlin, the DOS based Linux starter, but let's not concern ourselves with the past today. | ||
Line 52: | Line 52: | ||
For ease of instruction, | For ease of instruction, | ||
- | * Our example network uses IP addresses in the range of '' | + | * Our example network uses IP addresses in the range of **'' |
- | * Our network server will have the IP address of **192.168.0.1** and the default gateway is **192.168.0.10**. Server and gateway do not need to be the same physical machine. | + | * Our network server will have the IP address of **192.168.0.1** and the default gateway is **192.168.0.10**. Server and gateway |
- | * The IP address range that the DHCP server will use to lease to DHCP/BOOTP enabled computers is '' | + | * The IP address range that the DHCP server will use to lease to DHCP/BOOTP enabled computers is **'' |
- | * The DNS domain will be "'' | + | * The DNS domain will be "**'' |
- | * The server will run all required services, i.e. acts as the LAN's DNS,DHCP, TFTP and NFS server. If you decide to separate DHCP and TFTP services onto two different servers (it does not matter where the NFS server runs), I will add a comment on what you should take care of in the [[# | + | * The server will run all required services, i.e. acts as the LAN' |
* Directories are used as follows: | * Directories are used as follows: | ||
- | * Toplevel of the complete Slackware 11.0 directory tree (excluding the source code if you're short on disk space) is ''/ | + | * Toplevel of the complete Slackware 11.0 directory tree (excluding the source code if you're short on disk space) is **''/ |
- | * The directory where we store the boot files for the TFTP server is ''/ | + | * The directory where we store the boot files for the TFTP server is **''/ |
==== DHCP ==== | ==== DHCP ==== | ||
Line 85: | Line 85: | ||
group { | group { | ||
allow bootp; | allow bootp; | ||
+ | next-server 192.168.0.1; | ||
use-host-decl-names on; | use-host-decl-names on; | ||
if substring (option vendor-class-identifier, | if substring (option vendor-class-identifier, | ||
Line 98: | Line 99: | ||
} | } | ||
} | } | ||
- | </ | + | </ |
- | + | ||
- | <note tip> | + | |
next-server 192.168.0.254;</ | next-server 192.168.0.254;</ | ||
+ | |||
+ | <note tip>If you are running a version of ISC dhcpd that is >= 3.0.3 , then the addition of a '' | ||
</ | </ | ||
<note tip> | <note tip> | ||
- | If you are already using dnsmasq as your DNS/DHCP server, then the above instructions for the ISC DHCP server are not applicable to your setup. In that case, I have another [[: | + | If you are already using **dnsmasq** as your DNS/DHCP server, then the above instructions for the ISC DHCP server are not applicable to your setup. In that case, I have another [[: |
</ | </ | ||
Line 116: | Line 117: | ||
</ | </ | ||
We need to create the directory ''/ | We need to create the directory ''/ | ||
- | mkdir / | + | mkdir / |
The tftpd service is now configured and running. We just need to populate it's root directory, but I'll keep that for another paragraph. | The tftpd service is now configured and running. We just need to populate it's root directory, but I'll keep that for another paragraph. | ||
Line 233: | Line 234: | ||
Save the isolinux.cfg file from the Slackware CDROM to the tftp directory: < | Save the isolinux.cfg file from the Slackware CDROM to the tftp directory: < | ||
- | cp ~ftp/pub/ | + | mkdir -p / |
- | </ | + | cp /mirror/ |
+ | </ | ||
sed -i -e " | sed -i -e " | ||
-e " | -e " | ||
- | / | + | / |
</ | </ | ||
- | Note: The //create_pxe_initrd.sh// script mentioned in the [[# | + | Note: The [[http://www.slackware.com/~alien/tools/ |
===== Trying it out ===== | ===== Trying it out ===== | ||
Line 262: | Line 264: | ||
Good luck! | Good luck! | ||
- | |||
====== Example configuration scripts ====== | ====== Example configuration scripts ====== | ||
Line 283: | Line 284: | ||
# Allow bootp requests | # Allow bootp requests | ||
allow bootp; | allow bootp; | ||
+ | |||
+ | # Point to the TFTP server: | ||
+ | next-server 192.168.0.1; | ||
# Default lease is 1 week (604800 sec.) | # Default lease is 1 week (604800 sec.) | ||
Line 392: | Line 396: | ||
allow bootp; | allow bootp; | ||
- | # Only use next-server if the TFTP service runs on another | + | # Point to the TFTP server |
- | # You'd fill in the IP address of that TFTP server here: | + | next-server 192.168.0.1; |
- | | + | |
# If you want to log the boot process, you will need to configure | # If you want to log the boot process, you will need to configure | ||
# your logserver to allow logging from remote hosts. | # your logserver to allow logging from remote hosts. | ||
#option log-servers 192.168.0.1; | #option log-servers 192.168.0.1; | ||
+ | |||
use-host-decl-names on; | use-host-decl-names on; | ||