|
Lines 181-194
Link Here
|
| 181 |
send a <literal>HUP</literal> signal to inetd. To do this, get the |
181 |
send a <literal>HUP</literal> signal to inetd. To do this, get the |
| 182 |
process ID of inetd with <command>ps -ax | grep inetd | grep -v |
182 |
process ID of inetd with <command>ps -ax | grep inetd | grep -v |
| 183 |
grep</command>. Once you have it, send it a <literal>HUP</literal> signal. Do this by |
183 |
grep</command>. Once you have it, send it a <literal>HUP</literal> signal. Do this by |
| 184 |
<command>kill -HUP <pid></command>. This will force inetd to |
184 |
<command>kill -HUP <pid></command>. This will force <application>inetd</application> to |
| 185 |
re-read its config file.</para> |
185 |
re-read its config file.</para> |
| 186 |
|
186 |
|
| 187 |
<para>Did you remember to note the <literal>addr</literal> line from the |
187 |
<para>Did you remember to note the <literal>addr</literal> line from the |
| 188 |
output of the boot loader on the diskless system? Guess what, here is |
188 |
output of the boot loader on the diskless system? Guess what, here is |
| 189 |
where you need it.</para> |
189 |
where you need it.</para> |
| 190 |
|
190 |
|
| 191 |
<para>Add an entry to <literal>/etc/bootptab</literal> (maybe creating the |
191 |
<para>Add an entry to <filename>/etc/bootptab</filename> (maybe creating the |
| 192 |
file). It should be laid out identical to this:</para> |
192 |
file). It should be laid out identical to this:</para> |
| 193 |
|
193 |
|
| 194 |
<programlisting>altair:\ |
194 |
<programlisting>altair:\ |