NOTICE: This package has been removed from pkgsrc

./net/netbsd-tap, NetBSD kernel module for virtual Ethernet devices

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]


Branch: CURRENT, Version: 20050610, Package name: netbsd-tap-20050610, Maintainer: cube

tap(4) is a virtual Ethernet device driver. Each tap(4) device appears as a
regular Ethernet NIC to the kernel, with a MAC address and a set of media
interfaces. It is a clonable network interface, which means any number of
such devices can be created by the administrator.

Just like tun(4), tap(4) offers a TTY interface to each of its devices which
allows an application to read and inject Ethernet frames into the network
stack. tap(4) devices can be created and used individually for system-wide
configurations, but an application can also use a special clonable device
node to create interfaces on demand.

As a LKM must be compiled with the same environment as the kernel with respect
to a handful of definition (DEBUG, DIAGNOSTIC, MULTIPROCESSOR, LOCKDEBUG and
MALLOCLOG), the package provides a variable, TAP_KERNEL_ENV, to hold the
correct addition to the compilation command line. For example, you might want
to define it the following way in mk.conf:

TAP_KERNEL_ENV= -DDIAGNOSTIC -DMULTIPROCESSOR



Package options: bpf

Version history: (Expand)


CVS history: (Expand)


   2009-02-24 00:19:23 by Quentin Garnier | Files touched by this commit (15) | Package removed
Log message:
Remove net/netbsd-tap.  NetBSD 2.0 is just too old;  later versions of
NetBSD have tap(4) in the kernel.
   2008-04-29 07:46:09 by Martin Husemann | Files touched by this commit (87)
Log message:
Drop clauses 3 and 4 from TNF licenses
   2006-07-21 16:27:56 by Johnny C. Lam | Files touched by this commit (13)
Log message:
"BUILD_ENV" was misnamed.  It's actually the environment that is passed
to all internal recursive make processes.  As such, rename it to
"PKGSRC_MAKE_ENV".

XXX Note, some of the usage of this variable in package Makefiles seems
XXX incorrect.  They probably want "MAKE_ENV", which is the environment
XXX passed to the make process when running "make" within ${WRKSRC}.
   2006-07-09 01:11:17 by Johnny C. Lam | Files touched by this commit (877)
Log message:
Change the format of BUILDLINK_ORDER to contain depth information as well,
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.

For example, "make show-buildlink3" in fonts/Xft2 displays:

	zlib
	fontconfig
	    iconv
	    zlib
	    freetype2
	    expat
	freetype2
	Xrender
	    renderproto
   2006-07-09 00:39:49 by Johnny C. Lam | Files touched by this commit (877)
Log message:
Track information in a new variable BUILDLINK_ORDER that informs us
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
   2006-04-12 12:27:47 by Roland Illig | Files touched by this commit (749)
Log message:
Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
   2006-04-06 08:23:06 by Jeremy C. Reed | Files touched by this commit (1147)
Log message:
Over 1200 files touched but no revisions bumped :)

RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).
   2006-03-30 20:06:19 by Johnny C. Lam | Files touched by this commit (38)
Log message:
Avoid extra stat() calls by not repeatedly checking whether a file
exists on the disk -- we can just check whether a variable defined by
find-files.mk is "__nonexistent__" or not.