R-Pi PXE Server - Revision history

Bredman: Added text describing skill level

2012-02-11T09:42:28Z

Added text describing skill level

2012-02-08T17:59:47Z

Removed text about RPi as DHCP proxy. A DHCP proxy needs 2 network interfaces, RPi only has one interface.

2012-02-08T17:38:25Z

‎What does it do?

2012-02-08T12:47:53Z

2012-02-08T12:47:21Z

2012-02-08T10:15:15Z

2012-02-07T18:54:54Z

‎Extra useful text

2012-02-07T18:53:07Z

‎Extra useful text

2012-02-07T18:32:22Z

‎Test with a single PC

2012-02-07T18:30:48Z

‎Configuring the tftp server on the RPi

@@ Line 21: / Line 21: @@
 *A boot SD card for the Raspberry Pi. [What size? Needs to hold ISO image]
 *An Ethernet cable to connect to the local network.
 =How does it work?=

← Older revision		Revision as of 17:59, 8 February 2012
Line 10:		Line 10:
	As yet, I have not decided on Fedora or Debian, so the instructions are a bit of a mix at the moment.		As yet, I have not decided on Fedora or Debian, so the instructions are a bit of a mix at the moment.

−	~~Thinking about using dnsmasq instead of dhcpd, dnsmasq can act as a dhcp proxy, which would avoid interference with any dhcp server already in the network.~~

@@ Line 15: / Line 15: @@
 =What does it do?=
-This server allows your to use cheap PCs in a classroom/library/café which do not have their own hard disks. When the PCs are turned on, they will fetch the boot information from a PXE/netboot server. The major advantage is that the cost of each PC is reduced because individual hard disks are not needed. Also, there is no information stored locally on each PC for the user to tamper with. If the user messes up a PC, just reboot the PC to return to normal.
+This server allows you to run a number of networked PCs, each without its own hard disk, in a classroom/library/café. When the PCs are turned on, they will fetch the boot information from a PXE/netboot server. The cost of each PC is reduced because individual hard disks are not needed. Also, there is no information stored locally on each PC for the user to tamper with - if the user messes up a PC, just reboot the PC to return to normal.
 =What do you need?=

← Older revision		Revision as of 12:47, 8 February 2012
Line 400:		Line 400:

	From here on the system will boot into whichever kernel you specify. (We could configure the system to timeout here and just boot into a default option, but we didn't.)		From here on the system will boot into whichever kernel you specify. (We could configure the system to timeout here and just boot into a default option, but we didn't.)
		+
		+
		+
		+	{{Template:Raspberry Pi}}

← Older revision		Revision as of 10:15, 8 February 2012
Line 7:		Line 7:
	As yet, I have not decided on Fedora or Debian, so the instructions are a bit of a mix at the moment.		As yet, I have not decided on Fedora or Debian, so the instructions are a bit of a mix at the moment.

−		+	Thinking about using dnsmasq instead of dhcpd, dnsmasq can act as a dhcp proxy, which would avoid interference with any dhcp server already in the network.

@@ Line 203: / Line 203: @@
 =Extra useful text=
 From http://www.debian-administration.org/articles/478
 If you're looking to perform a lot of system recovery, or system installation, then network booting with PXE is ideal. PXE allows you to boot up a system and have it automatically get an IP address via DHCP and start booting a kernel over the network.

@@ Line 188: / Line 188: @@
 ==Test with a single PC==
 A) At this stage, you're ready to hook up the switch. You should have CAT5 running between the switch & the PXE boot server, and the client box.
@@ Line 199: / Line 201: @@
 E) If you run into any problems, check /var/log/messages for errors (that's where all dhcp & tftp stuff will get logged). /var/log/httpd is where apache logs, but if you get that far, your problem is an apache configuration/setup issue, and not a PXE boot issue.
 =Extra useful text=
 From http://www.debian-administration.org/articles/478

@@ Line 167: / Line 167: @@
   default linux
   timeout 100
-−
   label linux
   kernel vmlinuz