Expand description of USES=kmod explaining why KMODDIR=/boot/kernel is
a bad idea and therefore rewritten. Approved by: gjb (mentor)
This commit is contained in:
parent
9cd0a36f09
commit
3eda0879ac
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43213
1 changed files with 7 additions and 1 deletions
|
|
@ -144,7 +144,13 @@
|
||||||
<listitem><para>Define <varname>KMODDIR</varname> to <filename
|
<listitem><para>Define <varname>KMODDIR</varname> to <filename
|
||||||
class="directory">/boot/modules</filename> by default, add it
|
class="directory">/boot/modules</filename> by default, add it
|
||||||
to <varname>PLIST_SUB</varname> and <varname>MAKE_ENV</varname>,
|
to <varname>PLIST_SUB</varname> and <varname>MAKE_ENV</varname>,
|
||||||
and create it upon installation.</para></listitem>
|
and create it upon installation. If KMODDIR is set to
|
||||||
|
<filename class="directory">/boot/kernel</filename>, it will be
|
||||||
|
rewritten to <filename class="directory">/boot/modules</filename>.
|
||||||
|
This prevents breaking packages when upgrading the kernel due to
|
||||||
|
<filename class="directory">/boot/kernel</filename> being renamed
|
||||||
|
to <filename class="directory">/boot/kernel.old</filename> in the
|
||||||
|
process.</para></listitem>
|
||||||
<listitem><para>Handle cross-referencing kernel modules upon installation
|
<listitem><para>Handle cross-referencing kernel modules upon installation
|
||||||
and deinstallation.</para></listitem>
|
and deinstallation.</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue