Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Feb 2011 12:47:42 -0800
From:      Rem P Roberti <remegius@comcast.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Stuck
Message-ID:  <4D5AE66E.1070603@comcast.net>
In-Reply-To: <C66259A3-EC5C-44BA-9921-6B02C8E7632E@vicor.com>
References:  <201102151225.p1FCPQoW094547@fire.js.berklix.net> <C66259A3-EC5C-44BA-9921-6B02C8E7632E@vicor.com>

next in thread | previous in thread | raw e-mail | index | archive | help

> NOTE: Slightly OT, but figured it was worth the post.
>
> As a side-note, the config-file will be "cleaned up" before being embedded into the kernel. Meaning "config -x `sysctl -n kern.bootfile`" will rarely ever match the config that was used to generate the kernel in the first place.
>
> Specifically, comments are removed, and if you've nested configs using the "include" statement, redundant and/or conflicting directives will be consolidated.
>
> If you instead wish to embed the kernel config AS-IS, comments and structure remaining in-tact, you should instead:
>
> 	cd /sys/ARCH/conf
> 	config -C -g CONFIG
>
> NOTE: `/sys' ought to be a symbolic link to `/usr/src/sys'
> NOTE: ARCH is to be replaced with something like "i386", "amd64", etc.
> NOTE: CONFIG is to be replaced with something like "GENERIC", "PAE", "MYCUSTOMKERNELCONFIG", etc.
>
> Then one simply does the following to compile the kernel:
>
> 	cd ../../compile/CONFIG
> 	make depend
> 	make
>
> BUT... then again not everybody:
> a. compiles their own custom kernels
> b. uses a custom config
> c. needs to be able to extract the config verbatim from the compiled kernel
>
> YNMV (Your Needs May Vary).
> --
> Devin
>
>

Not off topic at all, and much appreciated.  A lot of what has been 
offered as a result of my OP is a bit over my head at this stage of the 
game, but much isn't.  I'm gaining on it!

Cheers...

Rem




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D5AE66E.1070603>