Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| blog:netboot_solaris [2019/02/17 16:42] – john | blog:netboot_solaris [2019/02/17 16:45] (current) – john | ||
|---|---|---|---|
| Line 54: | Line 54: | ||
| </ | </ | ||
| - | The next step is supplying a kernel image to the booting Sparc machine. | + | The next step is supplying a kernel image to the booting Sparc machine. Note that modern versions of rarpd on Linux will also try to find a Sun kernel image, if you already have a working tftp server elsewhere ignore that feature of rarpd by running it with the //-e// flag: rarpd -d -v -e. |
| === tftp === | === tftp === | ||
| As the machine starts to boot it will make a request via TFTP, to the same server that it received a rarp request from, for a kernel image. | As the machine starts to boot it will make a request via TFTP, to the same server that it received a rarp request from, for a kernel image. | ||
| + | |||
| + | In my case: | ||
| + | |||
| + | < | ||
| + | Feb 17 16:43:56 curse tftpd[4446]: | ||
| + | Feb 17 16:44:05 curse tftpd[4478]: | ||
| + | </ | ||
| The name of the kernel image will depend on the IP address that you have assigned to the Sparc machine. Unfortunately it's in hexadecimal format. In the case of assigning 192.168.1.15, | The name of the kernel image will depend on the IP address that you have assigned to the Sparc machine. Unfortunately it's in hexadecimal format. In the case of assigning 192.168.1.15, | ||