At 05:43 PM 2/1/2009, Dan Nelson wrote:
Do you have options LIBALIAS in your kernel config?
Nope. There was nothing that said that such an option was needed
(or even that it existed). I did find it, via a recursive grep, in
a file labeled NOTES a couple of levels up in the directory
All:
I'm building a machine using FreeBSD 7.1-RELEASE, and noticed that
there was now a kernel configuration option to enable in-kernel NAT
in IPFW. So, starting with a pristine system, I tried to rebuild
the kernel with this feature as I trimmed out the unneeded device
drivers. But the
In the last episode (Feb 01), Brett Glass said:
I'm building a machine using FreeBSD 7.1-RELEASE, and noticed that there
was now a kernel configuration option to enable in-kernel NAT in IPFW.
So, starting with a pristine system, I tried to rebuild the kernel with
this feature as I trimmed out
At 05:43 PM 2/1/2009, Dan Nelson wrote:
Do you have options LIBALIAS in your kernel config?
Nope. There was nothing that said that such an option was needed
(or even that it existed). I did find it, via a recursive grep, in
a file labeled NOTES a couple of levels up in the directory
In the last episode (Feb 01), Brett Glass said:
At 05:43 PM 2/1/2009, Dan Nelson wrote:
Do you have options LIBALIAS in your kernel config?
Nope. There was nothing that said that such an option was needed
(or even that it existed). I did find it, via a recursive grep, in
a file labeled
At 08:41 PM 2/1/2009, Dan Nelson wrote:
LINT was removed back in 2000 and replaced with NOTES, since that better
describes what it's really used for. IPFIREWALL_NAT and LIBALIAS should
additionally be documented in ipfw(4) imho.
Indeed they should. I'm not a committer, or I'd add the
