- Add some replaceable elements to granularize the markup
PR: docs/123143 Submitted by: pgj
This commit is contained in:
parent
545f3afe56
commit
6b6ea32dbb
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=31951
1 changed files with 5 additions and 5 deletions
|
@ -272,12 +272,12 @@ ath_hal(4) - Atheros Hardware Access Layer (HAL)</programlisting>
|
|||
name you want to give your kernel. For example:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/src/sys/<replaceable>i386</replaceable>/conf</userinput>
|
||||
&prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen>
|
||||
&prompt.root; <userinput>cp GENERIC <replaceable>MYKERNEL</replaceable></userinput></screen>
|
||||
|
||||
<para>Traditionally, this name is in all capital letters and, if you
|
||||
are maintaining multiple &os; machines with different hardware,
|
||||
it is a good idea to name it after your machine's hostname. We will
|
||||
call it <filename>MYKERNEL</filename> for the purpose of this
|
||||
call it <filename><replaceable>MYKERNEL</replaceable></filename> for the purpose of this
|
||||
example.</para>
|
||||
|
||||
<tip>
|
||||
|
@ -305,7 +305,7 @@ ath_hal(4) - Atheros Hardware Access Layer (HAL)</programlisting>
|
|||
&prompt.root; <userinput>ln -s /root/kernels/<replaceable>MYKERNEL</replaceable></userinput></screen>
|
||||
</tip>
|
||||
|
||||
<para>Now, edit <filename>MYKERNEL</filename> with your favorite text
|
||||
<para>Now, edit <filename><replaceable>MYKERNEL</replaceable></filename> with your favorite text
|
||||
editor. If you are just starting out, the only editor available
|
||||
will probably be <application>vi</application>, which is too complex to
|
||||
explain here, but is covered well in many books in the <link
|
||||
|
@ -506,7 +506,7 @@ cpu I686_CPU</programlisting>
|
|||
|
||||
<para>This is the identification of the kernel. You should change
|
||||
this to whatever you named your kernel,
|
||||
i.e. <literal>MYKERNEL</literal> if you have followed the
|
||||
i.e. <literal><replaceable>MYKERNEL</replaceable></literal> if you have followed the
|
||||
instructions of the previous examples. The value you put in the
|
||||
<literal>ident</literal> string will print when you boot up the
|
||||
kernel, so it is useful to give the new kernel a different name if you
|
||||
|
@ -1445,7 +1445,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
|
|||
as &man.ps.1; may not work properly. To do this, simply
|
||||
rename the directory containing the good kernel:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mv /boot/kernel /boot/kernel.bad</userinput>
|
||||
<screen>&prompt.root; <userinput>mv /boot/kernel <replaceable>/boot/kernel.bad</replaceable></userinput>
|
||||
&prompt.root; <userinput>mv /boot/<replaceable>kernel.good</replaceable> /boot/kernel</userinput></screen>
|
||||
|
||||
</note>
|
||||
|
|
Loading…
Reference in a new issue