Date: Thu, 25 Oct 2012 14:51:38 +0700 From: Erich Dollansky <erichfreebsdlist@ovitrap.com> To: jb <jb.1234abcd@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: kernel config Message-ID: <20121025145138.10c1f745@X220.ovitrap.com> In-Reply-To: <loom.20121025T091143-809@post.gmane.org> References: <loom.20121025T083330-938@post.gmane.org> <20121025140453.06fbf81e@X220.ovitrap.com> <loom.20121025T091143-809@post.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Thu, 25 Oct 2012 07:26:27 +0000 (UTC) jb <jb.1234abcd@gmail.com> wrote: > Erich Dollansky <erichfreebsdlist <at> ovitrap.com> writes: > > > ... > > Just check how a custom kernel is build. You can then build three > > versions of it. One with nothing, one with the modules you want and > > one with the non-conflicting modules build-in. > > > > Just read the handbook regarding custom kernels. > > ... > > I have already read all docs :-) > The problem is I still do not get it ... > ok, the I hope that I will get what you want. > I understand that files sys/conf/NOTES and sys/<arch>/conf/NOTES > contain directive lines like 'device', 'options', 'machine', 'ident', > 'maxusers', 'makeoptions' etc that the user may place in the kernel > configuration that she will run config(8) with. > Yes, taken them as examples. > What is the specific mechanism (directive in GENERIC file, or You copy GENERIC into a new file i.e. ALLOPTIONS and set then is this file the options you want. You would need three files like this. ALLOPTIONS, NOOPTIONS and MYOPTIONS as an example. NOOPTIONS would then contain all options removed which you do not want. Be careful here as you might get a kernel which will not boot anymore. MYOPTIONS will contain then the options you would like to have in your kernel. Of course, you can use any other names you want to use. > something else in GENERIC file or elsewhere) that says build support > for cd9660 fs as built-in and ext2fs as module, or entire kernel as The modules are always build, at least to my knowledge. So, you do not need any options for this. You just need to load them later. > built-in, or entire kernel as modular (except things that must be > built-in, but then what things and where is this specified) ? Did you get what I wrote up there or was this not what you want to do? Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121025145138.10c1f745>