Date: Mon, 27 Dec 2010 00:29:47 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Rob <spamrefuse@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: kernel config file according to config(5): inconsistent ? Message-ID: <20101226235319.Y30408@sola.nimnet.asn.au> In-Reply-To: <20101226120033.CC15F1065773@hub.freebsd.org> References: <20101226120033.CC15F1065773@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In freebsd-questions Digest, Vol 342, Issue 9, Message: 1 On Sat, 25 Dec 2010 04:38:08 -0800 Rob <spamrefuse@yahoo.com> wrote: > I read the guidelines in the man pages of config(5) on how to make a customized > kernel config file: > > nooption name [, name [...]] > nooptions name [, name [...]] > Remove the specified kernel options from the list of previously > defined options. This directive can be used to cancel the > effects of option or options directives in files included using > include. > > So I put following in my MYKERNEL config file: > > include GENERIC > > nocpu I486_CPU > nocpu I586_CPU > ident MYKERNEL > > nomakeoptions DEBUG > > nooptions MD_ROOT > nooptions NFSCLIENT , NFSSERVER , NFSLOCKD , NFS_ROOT > nooptions MSDOSFS , CD9660 > nooptions PROCFS , PSEUDOFS > > The comma separated items seemed to cause an error when I do the buildkernel. > If I remove the commas and make a 'nooptions' per item, then it is OK. > > Something seems to be inconsistent here, right? > > Same inconsistency for "nodevices" with the syntax in the manpages and the real > config file.... Arguably unforgiving parsing and/or imprecise description. Try eg: nooptions NFSCLIENT, NFSSERVER, NFSLOCKD, NFS_ROOT with no space[s] before comma[s], as is generally conventional. cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101226235319.Y30408>