How to clean up /

[Kevin Oberman]

On Mon, Dec 3, 2012 at 1:51 PM, Johannes Totz <johannes at jo-t.de> wrote:
> On 30/11/2012 10:25, Fleuriot Damien wrote:
>>
>>
>> On Nov 30, 2012, at 9:59 AM, Alfred Bartsch <bartsch at dssgmbh.de> wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Am 30.11.2012 08:16, schrieb Kevin Oberman:
>>>>
>>>> On Thu, Nov 29, 2012 at 8:46 PM, Daniel O'Connor
>>>> <doconnor at gsoft.com.au> wrote:
>>>>>
>>>>>
>>>>> On 30/11/2012, at 12:14, mbsd <mbsd at isgroup.com.ua> wrote:
>>>>>>
>>>>>> Ξ ~ → du -sh /boot/kernel 59M   kernel
>>>>>>
>>>>>> Try to recompile your kernel without debug.
>>>>>
>>>>>
>>>>> Or delete /boot/kernel/*.symbols.
>>>
>>>
>>> You may suppress the installation of the *.symbols files by inserting
>>> the following statement into /etc/make.conf:
>>>
>>> # prevent installation of "*.symbols" in /boot/kernel
>>> INSTALL_NODEBUG=        yes
>>
>>
>>
>> In addition to the previous advice you've received regarding symbol files,
>> you may also want to only compile and install the kernel modules you
>> actually use.
>> There's also the side benefit of the kernel being that much faster to
>> rebuild.
>>
>> Get the list with "kldstat".
>>
>> Here for example, we only build a very few of them:
>> $ kldstat
>> Id Refs Address            Size     Name
>>   1   19 0xffffffff80100000 b0eec0   kernel
>>   2    1 0xffffffff80c0f000 bca8     geom_label.ko
>>   3    1 0xffffffff80c1b000 1350     mfi_linux.ko
>>   4    4 0xffffffff80c1d000 47958    linux.ko
>>   5    1 0xffffffff80e12000 40c3     linprocfs.ko
>>   6    1 0xffffffff80e17000 a14      linsysfs.ko
>>
>>
>> This yields a very lightweight kernel folder, even when retaining the
>> debug symbols:
>> $ du -hs
>>   46M   .
>>
>> This is what you want in /etc/rc.conf :
>> MODULES_OVERRIDE=geom/geom_label if_lagg if_vlan linprocfs linsysfs linux
>> mfi/mfi_linux
>
>
> This should be in /etc/make.conf?

thiat woruld work, but it would be better to put it into
/etc/src.conf. make.conf will define the variable for any make(1)
operation while src.conf is only used for building/installing the
world and kernel. (I'll admit that a namespace collision is very
unlikely here, but I think it is just good practice to use src.conf
for defining things only relevant to the OS.)
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6558 at gmail.com