PXE安装Solaris 10 1/06 + 系统

Boot Solaris OS on x86 platform from a network

Well, if you just need to boot or manually install x86 machine from network, and you find Network-Based Installations book not really covering a network boot process, and utilities like setup_install_server and add_install_client looks messy, doing too much and scary to you, then you can check the following info out.
Notes explains x86 machine boot process, how to configure TFTP and DHCP servers on Solaris OS for PXE use, how to work in GRUB.

1. x86 machine boot process

First of all, x86 machine's BIOS must support Preboot eXecution Environment (PXE) -- that's a facility for doing network init basically before the actual boot occurs. How it works? Let's go through the boot process.

1. After power on a machine, BIOS initializes processor, tests memory and initializes other I/O devices:

   Phoenix ServerBIOS 3 Release 6.0
   Copyright 1985-2002 Phoenix Technologies Ltd.
   All Rights Reserved
   Production RELEASE: System BIOS Revision = V1.34.4.2
   SP Interface (PRS) Revision = 97
   SP - BIOS Interface Active
               +==============================+                         
               |       Sun Microsystems       |                         
               |        Sun Fire V20z         |                         
               +==============================+                         
   CPU 0 = AMD Opteron(tm) Processor 244
   1 CPU Detected, E4
   PCIX - Slot1: PCIX-66     Slot2: PCIX-133
   672M System RAM Passed
   Press <F2> to enter SETUP  Press <F12> to Network Boot
       

   On some machines it is possible to enable/disable PXE in BIOS, some machines display a boot menu or allow to modify a boot sequence, on some machines F12 key enters PXE (i. e. Network Boot).
   If you work through some management interface which cann't send directly F12 key to a console, then you can use Esc-Shift-2 (i. e. Esc-@) instead.
   Whatever the key is, somehow we do enter PXE ...
2. 
   
3. PXE in turn uses Dynamic Host Configuration Protocol (DHCP) [2] to discover network configuration and find out where the bootable image is:

   Broadcom NetXtreme Ethernet Boot Agent v7.6.6
   Copyright (C) 2000-2004 Broadcom Corporation
   All rights reserved.
   
   Broadcom UNDI PXE-2.1 v7.6.6
   CLIENT MAC ADDR: 00 C0 9F 9E 40 09 GUID: F40A0DA0 197C 11DA 9FDF 0060B0B39DD0  
   DHCP /
       

   In particular, PXE broadcasts DHCPDISCOVER message

   IP:   ----- IP Header -----
   IP:
   IP:   Protocol = 17 (UDP)
   IP:   Destination address = 255.255.255.255, BROADCAST
   IP:
   UDP:  ----- UDP Header -----
   UDP:
   UDP:  Source port = 68
   UDP:  Destination port = 67 (BOOTPS)
   UDP:
   DHCP: ----- Dynamic Host Configuration Protocol -----
   DHCP:
   DHCP: Message type = DHCPDISCOVER
   DHCP: Requested Options:
   DHCP:    1 (Subnet Mask)
   DHCP:    2 (UTC Time Offset)
   DHCP:    3 (Router)
   DHCP:    5 (IEN 116 Name Servers)
   DHCP:    6 (DNS Servers)
   DHCP:   11 (RFC 887 Resource Location Servers)
   DHCP:   12 (Client Hostname)
   DHCP:   13 (Boot File size in 512 byte Blocks)
   DHCP:   15 (DNS Domain Name)
   DHCP:   16 (SWAP Server)
   DHCP:   17 (Client Root Path)
   DHCP:   18 (BOOTP options extensions path)
   DHCP:   43 (Vendor Specific Options)
   DHCP:   54 (DHCP Server Identifier)
   DHCP:   60 (Client Class Identifier =)
   DHCP:   67 (Option BootFile Name)
   DHCP:   128 (Site Option)
   DHCP:   129 (Site Option)
   DHCP:   130 (Site Option)
   DHCP:   131 (Site Option)
   DHCP:   132 (Site Option)
   DHCP:   133 (Site Option)
   DHCP:   134 (Site Option)
   DHCP:   135 (Site Option)
   DHCP: Maximum DHCP Message Size = 1260 bytes
   DHCP: Unrecognized Option = 97, length = 17 octets
   DHCP: Unrecognized Option = 93, length = 2 octets
   DHCP:   Value = 0x00 0x00 (unprintable)
   DHCP: Unrecognized Option = 94, length = 3 octets
   DHCP:   Value = 0x01 0x02 0x01 (unprintable)
   DHCP: Client Class Identifier = "PXEClient:Arch:00000:UNDI:002001"
       

   Such DHCP trace can be obtained by the snoop -v dhcp command on DHCP server machine, if it runs Solaris OS.
   Obviously DHCP server must be running in the same network segment as the PXE client machine.
   See "Configuring DHCP server on Solaris OS for PXE use" section for how to get DHCP worked.
4. 
   
5. After receiving discove