In freebsd-questions Digest, Vol 342, Issue 9, Message: 1
On Sat, 25 Dec 2010 04:38:08 -0800 Rob spamref...@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 [,
On Mon, 27 Dec 2010 00:29:47 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
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.
That doesn't work either.
On Sun, 26 Dec 2010, Bruce Cran wrote:
On Mon, 27 Dec 2010 00:29:47 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Arguably unforgiving parsing and/or imprecise description. Try eg:
nooptions NFSCLIENT, NFSSERVER, NFSLOCKD, NFS_ROOT
with no space[s] before comma[s], as
On Mon, 27 Dec 2010 01:50:45 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Probably should be easy, but from trying to parse that and lang.l I
get the vague impression (at best) that Rob's original should have
worked?
Too much partying probably .. care to enlighten us?
The NOOPTION
On Sun, 26 Dec 2010, Bruce Cran wrote:
On Mon, 27 Dec 2010 01:50:45 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Probably should be easy, but from trying to parse that and lang.l I
get the vague impression (at best) that Rob's original should have
worked?
Too much
Hi,
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
