| 271 |
blank, so the file the client looks for is just |
blank, so the file the client looks for is just |
| 272 |
<filename>client-ip-in-hex</filename>. Thus, if your system |
<filename>client-ip-in-hex</filename>. Thus, if your system |
| 273 |
subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename |
subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename |
| 274 |
would be <filename>C0A80103.SUN4C</filename>. |
would be <filename>C0A80103.SUN4C</filename>. An easy way to determine |
| 275 |
|
this is to pull up a shell on another Unix machine and: |
| 276 |
|
|
| 277 |
|
</para><para> |
| 278 |
|
<userinput>printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4</userinput> |
| 279 |
|
</para><para> |
| 280 |
|
|
| 281 |
|
if the machine's intended IP is 10.0.0.4. This will spit out the IP in |
| 282 |
|
hexadecimal; you will need to change all letters to uppercase and append |
| 283 |
|
the subarchitecture name if necessary, to get to the correct filename. |
| 284 |
|
|
| 285 |
</para><para> |
</para><para> |
| 286 |
|
|