| 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>. An easy way to determine |
would be <filename>C0A80103.SUN4C</filename>. An easy way to determine |
| 275 |
this is to pull up a shell on another Unix machine and: |
this is to enter the following command in a shell (assuming the |
| 276 |
|
machine's intended IP is 10.0.0.4). |
| 277 |
|
|
| 278 |
</para><para> |
</para> |
| 279 |
<userinput>printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4</userinput> |
|
| 280 |
</para><para> |
<informalexample><screen> |
| 281 |
|
printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 |
| 282 |
|
</screen></informalexample> |
| 283 |
|
|
| 284 |
|
<para> |
| 285 |
|
|
| 286 |
if the machine's intended IP is 10.0.0.4. This will spit out the IP in |
This will spit out the IP in hexadecimal; to get to the correct |
| 287 |
hexadecimal; you will need to change all letters to uppercase and append |
filename, you will need to change all letters to uppercase and |
| 288 |
the subarchitecture name if necessary, to get to the correct filename. |
if necessary append the subarchitecture name. |
| 289 |
|
|
| 290 |
</para><para> |
</para><para> |
| 291 |
|
|