Changes between Version 13 and Version 14 of Internal/ImageInstall
- Timestamp:
- Aug 31, 2006, 11:14:56 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/ImageInstall
v13 v14 4 4 Step 1 -- 5 5 6 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. 6 PXE net-work booting (on the source machine): -- [[BR]] 7 8 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. 7 9 8 10 {{{ 9 11 Our current setup: 10 DHCPD runs on dhcp1.orbit-lab.org 12 DHCPD runs on dhcp1.orbit-lab.org (10.0.0.1) 11 13 AFTPD runs on repository2.orbit-lab.org (10.0.50.40, this is "next-server") 12 14 }}} … … 32 34 33 35 {{{ 34 TIP:35 36 Some snags I've run into: 36 37 … … 43 44 S: Restart TFTPD on the next-server. In our current setup this is repository2 and the server name is AFTPD. 44 45 45 P: No BIF get loaded by the client, and the machine move to other boot media46 P: No BIF get loaded by the client, and the machine moves to other boot media 46 47 S: Make sure the file is named appropriately. When the pxe clinet searches for the BIF, it list (and displays on screen) 47 the names it tires. A clever use of the Pause/Break key will help you find what its looking for. 48 the names it tires. If you don't see this list of attempts, the client hasn't found / communicated with the tftp server. 49 If you see the list, a clever use of the Pause/Break key will help you find what its looking for. 48 50 49 51 }}} 50 51 52 52 53 53 once at the console, the resting place of the image was mounted. 54 54 55 55 step 3 -- 56 57 Finding a place to put your image: 58 56 59 {{{ 57 60 mount -o nolock repository2:/export/orbit/image/tmp /mnt … … 64 67 So now that I have some place to put the image file, I can create it with the imagezip utility (should live in /bin on the image). 65 68 69 {{{ 70 Note: NFS is not particularly fourth coming with information. For instance if you type the name of the share point incorrectly, 71 you get a permission denied error. Some what misleading 72 }}} 73 74 66 75 step 4 -- 76 Getting the image: 77 67 78 {{{ 68 79 imagezip /dev/hda - > /mnt/orbit-pc1... … … 81 92 Since frisbee is a client / server type service, I'll need a place for the server to run. This place should have access to my freshly generated image. Mogwai (?!$#@) is our candidate. Once ssh'd to mogwai, I'll scp my file from repository2, and place it in /tmp. (an exercise left to the reader) 82 93 83 step 5 94 step 5 -- 95 Starting up a frisbee server/daemon (frisbeed): 96 84 97 {{{ 85 98 frisbeed -p 5050 -m 10.0.250.221 /tmp/orbit-pc2... … … 90 103 '' /tmp/orbit-pc2 is my image file, freshly copied.''[[BR]] 91 104 92 step 6 105 step 6 -- 106 Pulling down the image to the "client" 107 108 '''Note: This setup requires that you preform steps 1 and 2 on the target machine. From here you should be at the similar console to the one you had when using the imagezip utility. Since all I'm doing is using the frisbee client to get the image from the frisbee server I made in step 5, I don't need step 3.''' 109 93 110 {{{ 94 111 frisbee -p 5050 -m 10.0.101.10 -i 10.0.250.221 /dev/hda
