Another question which crops up every now and again: "why is my kernel so

big?".  People must be using "config -g" without knowing it or something...

PR:		19997
Submitted by:	Eric Ogren <eogren@earthlink.net>
This commit is contained in:
Ben Smithurst 2000-07-19 19:20:26 +00:00
parent 7d410b6d55
commit 898ea1c8c3
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7681
2 changed files with 84 additions and 2 deletions

View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.74 2000/07/19 10:13:17 alex Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.75 2000/07/19 17:24:48 ben Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -4101,6 +4101,47 @@ device.</para>
</answer></qandaentry>
<qandaentry>
<question>
<para>Why is my kernel so big (over 10MB)?</para>
</question>
<answer>
<para>Chances are, you compiled your kernel in
<emphasis>debug mode</emphasis>. Kernels built in debug
mode contain many symbols that are used for debugging, thus
greatly increasing the size of the kernel. Note that if you
running a FreeBSD 3.0 or later system, there will be little
or no performance decrease from running a debug kernel,
and it is useful to keep one around in case of a system
panic.</para>
<para>However, if you are running low on disk space, or
you simply don't want to run a debug kernel, make sure
that both of the following are true:</para>
<itemizedlist>
<listitem>
<para>You do not have a line in your kernel
configuration file that reads:</para>
<programlisting>makeoptions DEBUG=-g</programlisting>
</listitem>
<listitem>
<para>You are not running <command>config</command> with
the <option>-g</option> option.</para>
</listitem>
</itemizedlist>
<para>Both of the above situations will cause your kernel to
be built in debug mode. As long as you make sure you follow
the steps above, you can build your kernel normally, and you
should notice a fairly large size decrease; most kernels
tend to be around 1.5MB to 2MB.</para>
</answer>
</qandaentry>
<qandaentry><question>
<para>Interrupt conflicts with multi-port serial code.</para></question><answer>

View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.74 2000/07/19 10:13:17 alex Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.75 2000/07/19 17:24:48 ben Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -4101,6 +4101,47 @@ device.</para>
</answer></qandaentry>
<qandaentry>
<question>
<para>Why is my kernel so big (over 10MB)?</para>
</question>
<answer>
<para>Chances are, you compiled your kernel in
<emphasis>debug mode</emphasis>. Kernels built in debug
mode contain many symbols that are used for debugging, thus
greatly increasing the size of the kernel. Note that if you
running a FreeBSD 3.0 or later system, there will be little
or no performance decrease from running a debug kernel,
and it is useful to keep one around in case of a system
panic.</para>
<para>However, if you are running low on disk space, or
you simply don't want to run a debug kernel, make sure
that both of the following are true:</para>
<itemizedlist>
<listitem>
<para>You do not have a line in your kernel
configuration file that reads:</para>
<programlisting>makeoptions DEBUG=-g</programlisting>
</listitem>
<listitem>
<para>You are not running <command>config</command> with
the <option>-g</option> option.</para>
</listitem>
</itemizedlist>
<para>Both of the above situations will cause your kernel to
be built in debug mode. As long as you make sure you follow
the steps above, you can build your kernel normally, and you
should notice a fairly large size decrease; most kernels
tend to be around 1.5MB to 2MB.</para>
</answer>
</qandaentry>
<qandaentry><question>
<para>Interrupt conflicts with multi-port serial code.</para></question><answer>