Solved Pkg-base multiple kernels

I am new to building my own kernels so i might have some mistakes in my kernel configuration files.

I have built 3 kernels and packaged them with pkgbase, I build generic and 2 more kernels one for a firewall and one for a FreeBSD SAN machine.

My GENERIC is stock Head src and my other kernel configurations is as following.

Code:
root@aasennas:~ # cat /usr/src-head/sys/amd64/conf/FCGENERIC
include GENERIC
ident FCGENERIC

device isp
device ispfw
options         ISP_TARGET_MODE
options         ISP_DEFAULT_ROLES=1

root@aasennas:~ # cat /usr/src-head/sys/amd64/conf/ALTQGENERIC
include GENERIC
ident ALTQGENERIC

options         ALTQ
options         ALTQ_CBQ                # Class Based Queuing (CBQ)
options         ALTQ_RED                # Random Early Detection (RED)
options         ALTQ_RIO                # RED In/Out
options         ALTQ_HFSC               # Hierarchical Packet Scheduler (HFSC)
options         ALTQ_PRIQ               # Priority Queuing (PRIQ)

The question is as following why is generic producing more files then FCGENERIC and ALTQGENERIC?
 
running
kldxref /boot/kernel*


fixes the problem, but linker.hints was missing from the custom kernel, is there a way to build it by build kernel?
 
linker.hints was missing from the custom kernel, is there a way to build it by build kernel?
Easiest way is to use kldxref_enable in /etc/rc.conf, see also /etc/defaults/rc.conf:

Code:
#kld_list=""            # Kernel modules to load after local disks are mounted
kldxref_enable="NO"     # Build linker.hints files with kldxref(8).
kldxref_clobber="NO"    # Overwrite old linker.hints at boot.
kldxref_module_path=""  # Override kern.module_path. A ';'-delimited list.
I usually use both kldxref _enable and _clobber together.
 
So the kldxref_enable="YES" is to run kldxref when building the kernel and kldxref_clobber="YES" is running it at boot?

So if i use the clobber i don`t need the enable when i use the kernel on another machine then the build machine?
 
So the kldxref_enable="YES" is to run kldxref when building the kernel
No, it will run kldxref during the boot phase. After all, that's what /etc/rc.conf is primarily used for in the first place.

The clobber option simply ensures that it will always replace an existing file.
 
Back
Top