Changes between Version 8 and Version 9 of Internal/ImageInstall

Timestamp:

Aug 29, 2006, 11:23:54 PM (18 years ago)

Author:

ssugrim

Comment:

Expanding the pxe and image sections.

Internal/ImageInstall

@@ -2 +2 @@
 My candidate is orbit-pc2, one of the user service machines. It's going to be migrated to a dell. 
 
-Step 1  -- Some kind of pxe thing happens. 
+Step 1 --
 
-step 2 -- Orbit-pc2 boots the image ...winlab.img
+PXE: This is a concerted effort between the dhcp server and the tftp server. In the dhcpd.conf file in the parameter "nextserver" is interpreted by the pxe booting clinet as "where to look" for the boot img (and associated directive files). The booting clinet then initiates a tftp session with the "next-server" and downloads an directive file that tells it what image to copy, uncompress, and boot. 
+
+
+step 2 --
+
+Getting the boot image: 
+
+On the tftp server a boot menu file (I'm going to call it that for lack of something better to call it) is stored in /tfptboot/pexlinux.cfg/ . It contains information on what image to download, and what boot flags to apply to the kernel.
+
+When the booting client wakes up, and establishes a tftp session with "next-server", it looks for a file in the /tftpboot/pxelinux.cfg directory that has it's '''IP ADDRESS''' as the name of the file ('''IN HEX, with no field delimiters'''). 
+
+{{{
+E.G. if your IP was 
+'''10.0.250.246'''
+the file would have to be named 
+'''0A00FAF6 '''
+
+NOTE: The link should point to the boot menu file '''NOT''' the image.
+}}}
+
+Assuming that the image file and boot menu file are valid, the booting client will boot and eventually put you at a console.
 
 once at the console, the resting place of the image was mounted.