Reducing the need to compile a custom kernel

Alexander Leidinger Alexander at
Tue Feb 14 08:10:59 UTC 2012

Quoting Volodymyr Kostyrko <c.kworr at> (from Mon, 13 Feb 2012  
17:44:33 +0200):

> Alexander Leidinger wrote:
>> Feasible: depend upon your definition of "feasible". You would have to
>> add all keymaps statically into the kernel. No idea which parts exactly
>> we talk about, but:
>> ---snip---
>> % du -h /usr/share/syscons/
>> 40k /usr/share/syscons/scrnmaps
>> 570k /usr/share/syscons/fonts
>> 1.1M /usr/share/syscons/keymaps
>> 1.8M /usr/share/syscons/
>> ---snip---
>> I wouldn't mind for 40k, but 1.8M looks more like the value to calculate
>> with. Anyway, this is out of the scope of the original question.
> Correct me if I'm wrong but zfs already fetches plain file  
> /boot/zfs/zpool.cache on load. Can't this be:
>  1. Postponed to later processing.
>  2. After filesystems are mounted the keymap is loaded.

This is already the case. you can set the keymap in rc.conf.

> Or even:
>  1. Put all viable files on the / partition.
>  2. Select and load correct one before kernel is fired.

This is not the same as compiling it in the kernel. Think about a  
problem where parts of your FS are corrupt / damaged / overwritten  
with nonsense. Yes you can minimize the problem by loading it more  
early, but having it in the kernel removes the keyboard problem  


A lost ounce of gold may be found, a lost moment of time never.    Alexander @ PGP ID = B0063FE7       netchild @  : PGP ID = 72077137

More information about the freebsd-stable mailing list