Recompiling a kernel is no longer a rite of passed for nearly all BSD
users; only advanced users now compile kernels. Expand rationale for building a custom kernel: unused features still take up memory that could be used by applications.
This commit is contained in:
parent
dfe5a50083
commit
cf1dd0e5d7
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=34272
1 changed files with 6 additions and 4 deletions
|
@ -96,7 +96,7 @@
|
|||
dynamic loadable kernel module for that functionality.</para>
|
||||
|
||||
<para>Building a custom kernel is one of the most important rites of
|
||||
passage nearly every BSD user must endure. This process, while
|
||||
passage for advanced BSD users. This process, while
|
||||
time consuming, will provide many benefits to your &os; system.
|
||||
Unlike the <filename>GENERIC</filename> kernel, which must support a
|
||||
wide range of hardware, a custom kernel only contains support for
|
||||
|
@ -112,9 +112,11 @@
|
|||
|
||||
<listitem>
|
||||
<para>Lower memory usage. A custom kernel often uses less memory
|
||||
than the <filename>GENERIC</filename> kernel, which is important
|
||||
because the kernel must always be present in real
|
||||
memory. For this reason, a custom kernel is especially useful
|
||||
than the <filename>GENERIC</filename> kernel by omitting unused
|
||||
features and device drivers. This is important because the kernel
|
||||
code remains resident in physical memory at all times, preventing
|
||||
that memory from being used by applications.
|
||||
For this reason, a custom kernel is especially useful
|
||||
on a system with a small amount of RAM.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
Loading…
Reference in a new issue