|
Lines 272-283
Link Here
|
| 272 |
name you want to give your kernel. For example:</para> |
272 |
name you want to give your kernel. For example:</para> |
| 273 |
|
273 |
|
| 274 |
<screen>&prompt.root; <userinput>cd /usr/src/sys/<replaceable>i386</replaceable>/conf</userinput> |
274 |
<screen>&prompt.root; <userinput>cd /usr/src/sys/<replaceable>i386</replaceable>/conf</userinput> |
| 275 |
&prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen> |
275 |
&prompt.root; <userinput>cp GENERIC <replaceable>MYKERNEL</replaceable></userinput></screen> |
| 276 |
|
276 |
|
| 277 |
<para>Traditionally, this name is in all capital letters and, if you |
277 |
<para>Traditionally, this name is in all capital letters and, if you |
| 278 |
are maintaining multiple &os; machines with different hardware, |
278 |
are maintaining multiple &os; machines with different hardware, |
| 279 |
it is a good idea to name it after your machine's hostname. We will |
279 |
it is a good idea to name it after your machine's hostname. We will |
| 280 |
call it <filename>MYKERNEL</filename> for the purpose of this |
280 |
call it <filename><replaceable>MYKERNEL</replaceable></filename> for the purpose of this |
| 281 |
example.</para> |
281 |
example.</para> |
| 282 |
|
282 |
|
| 283 |
<tip> |
283 |
<tip> |
|
Lines 305-311
Link Here
|
| 305 |
&prompt.root; <userinput>ln -s /root/kernels/<replaceable>MYKERNEL</replaceable></userinput></screen> |
305 |
&prompt.root; <userinput>ln -s /root/kernels/<replaceable>MYKERNEL</replaceable></userinput></screen> |
| 306 |
</tip> |
306 |
</tip> |
| 307 |
|
307 |
|
| 308 |
<para>Now, edit <filename>MYKERNEL</filename> with your favorite text |
308 |
<para>Now, edit <filename><replaceable>MYKERNEL</replaceable></filename> with your favorite text |
| 309 |
editor. If you are just starting out, the only editor available |
309 |
editor. If you are just starting out, the only editor available |
| 310 |
will probably be <application>vi</application>, which is too complex to |
310 |
will probably be <application>vi</application>, which is too complex to |
| 311 |
explain here, but is covered well in many books in the <link |
311 |
explain here, but is covered well in many books in the <link |
|
Lines 506-512
Link Here
|
| 506 |
|
506 |
|
| 507 |
<para>This is the identification of the kernel. You should change |
507 |
<para>This is the identification of the kernel. You should change |
| 508 |
this to whatever you named your kernel, |
508 |
this to whatever you named your kernel, |
| 509 |
i.e. <literal>MYKERNEL</literal> if you have followed the |
509 |
i.e. <literal><replaceable>MYKERNEL</replaceable></literal> if you have followed the |
| 510 |
instructions of the previous examples. The value you put in the |
510 |
instructions of the previous examples. The value you put in the |
| 511 |
<literal>ident</literal> string will print when you boot up the |
511 |
<literal>ident</literal> string will print when you boot up the |
| 512 |
kernel, so it is useful to give the new kernel a different name if you |
512 |
kernel, so it is useful to give the new kernel a different name if you |
|
Lines 1445-1451
Link Here
|
| 1445 |
as &man.ps.1; may not work properly. To do this, simply |
1445 |
as &man.ps.1; may not work properly. To do this, simply |
| 1446 |
rename the directory containing the good kernel:</para> |
1446 |
rename the directory containing the good kernel:</para> |
| 1447 |
|
1447 |
|
| 1448 |
<screen>&prompt.root; <userinput>mv /boot/kernel /boot/kernel.bad</userinput> |
1448 |
<screen>&prompt.root; <userinput>mv /boot/kernel <replaceable>/boot/kernel.bad</replaceable></userinput> |
| 1449 |
&prompt.root; <userinput>mv /boot/<replaceable>kernel.good</replaceable> /boot/kernel</userinput></screen> |
1449 |
&prompt.root; <userinput>mv /boot/<replaceable>kernel.good</replaceable> /boot/kernel</userinput></screen> |
| 1450 |
|
1450 |
|
| 1451 |
</note> |
1451 |
</note> |