HardenedBSD/lkm/ipfw/Makefile

#	$Id: Makefile,v 1.2 1995/01/12 13:57:51 ugen Exp $

.PATH:	${.CURDIR}/../../sys/netinet
KMOD=	ipfw_mod
SRCS=	ipfw_lkm.c ip_fw.c
NOMAN=
CFLAGS+= -DIPFIREWALL  -DIPACCT
#
#If you want it verbose
#CFLAGS+= -DIPFIREWALL_VERBOSE
#

.include <bsd.kmod.mk>
Remove trailing whitespace. 1995-05-30 08:12:45 +02:00			`# $Id: Makefile,v 1.2 1995/01/12 13:57:51 ugen Exp $`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 14:03:02 +01:00
			`.PATH: ${.CURDIR}/../../sys/netinet`
			`KMOD= ipfw_mod`
Remove trailing whitespace. 1995-05-30 08:12:45 +02:00			`SRCS= ipfw_lkm.c ip_fw.c`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 14:03:02 +01:00			`NOMAN=`
			`CFLAGS+= -DIPFIREWALL -DIPACCT`
			`#`
Checking new lkm structure.. 1995-01-12 14:57:51 +01:00			`#If you want it verbose`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 14:03:02 +01:00			`#CFLAGS+= -DIPFIREWALL_VERBOSE`
			`#`

			`.include <bsd.kmod.mk>`