Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Oct 2003 20:49:51 +0100
From:      Miguel Mendez <flynn@energyhq.es.eu.org>
To:        Leo Bicknell <bicknell@ufp.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: 5.x kernel config changes?
Message-ID:  <20031030204951.088887e6.flynn@energyhq.es.eu.org>
In-Reply-To: <20031030194053.GA862@ussenterprise.ufp.org>
References:  <20031030194053.GA862@ussenterprise.ufp.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Dixitur illum Leo Bicknell <bicknell@ufp.org> scribere...

[Moving to questions, since all of these are FAQs]

Hi, here we go...
 
> 1) It appears IPFW just works (eg, configure it in /etc/rc.conf).  It
>    used to be you had to compile it in.  What's interesting to me is
>    that IPFW options are not in generic, and I didn't think "options"
>    could be done in LKM's.  What am I missing?

You aren't missing anything, the module is loaded if needed.

> 2) IPDIVERT is missing / doesn't work, so while my IPFW config seemed 
>    to take/work natd did not work.  If IPFW is just going to work
>    having IPDIVERT just work seems like a good idea as well.

As per 1), if ipfw is loaded as module no ipdivert functionality will be
present, you need to add both in your kernel config.

> 3) There seems to be no more LINT or other listing of all the options.
>    Why?  In particular I needed "options NETATALK" but couldn't
>    remember the name and there was no file to quickly grep.  Has the
>    list of options been moved somewhere else?

The config file is now called NOTES, and was splitted in two parts,
machine dependent and machine independent. You can generate the LINT file
with: make LINT in that same directory where NOTES is.

> 4) Due to the way the makefiles now work it seems impossible to build
> a
>    new kernel after changing just "options" statements and install it
>    without also rebuilding all the modules...which takes quite some
>    time.  This seems to be because it moves the whole directory out of
>    the way in /boot.  This seems a little suboptimal to me.

You can choose not to build modules by setting it in make.conf.

Cheers,
-- 
	Miguel Mendez <flynn@energyhq.es.eu.org>
	http://www.energyhq.es.eu.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031030204951.088887e6.flynn>