minix/drivers/fbd/Makefile

# Makefile for the Faulty Block Device (FBD)

.include <bsd.own.mk>

PROG=	fbd
SRCS=	fbd.c rule.c action.c

DPADD+=	${LIBBLOCKDRIVER} ${LIBSYS}
LDADD+=	-lblockdriver -lsys
CPPFLAGS+=	-DDEBUG=0

# The FBD driver requires NetBSD libc.
MAN=

BINDIR?= /usr/sbin

.include <minix.service.mk>
Add fbd -- Faulty Block Device driver This driver can be loaded as an overlay on top of a real block device, and can then be used to generate block-level failures for certain transfer requests. Specifically, a rule-based system allows the user to introduce (overt and silent) data corruption and errors. It exposes itself through /dev/fbd, and a file system can be mounted on top of it. The new fbdctl(8) tool can be used to control the driver; see ``man fbdctl'' for details. It also comes with a test set, located in test/fbdtest. 2011-12-11 19:32:13 +01:00			`# Makefile for the Faulty Block Device (FBD)`

			`.include <bsd.own.mk>`

			`PROG= fbd`
			`SRCS= fbd.c rule.c action.c`

			`DPADD+= ${LIBBLOCKDRIVER} ${LIBSYS}`
libminc-related updates - add files needed for acpi, ahci, fbd, vfs to libminc - remove "-lc" from their respective makefiles - remove setenv from libminc (requires initialization) 2012-03-09 00:49:46 +01:00			`LDADD+= -lblockdriver -lsys`
Add fbd -- Faulty Block Device driver This driver can be loaded as an overlay on top of a real block device, and can then be used to generate block-level failures for certain transfer requests. Specifically, a rule-based system allows the user to introduce (overt and silent) data corruption and errors. It exposes itself through /dev/fbd, and a file system can be mounted on top of it. The new fbdctl(8) tool can be used to control the driver; see ``man fbdctl'' for details. It also comes with a test set, located in test/fbdtest. 2011-12-11 19:32:13 +01:00			`CPPFLAGS+= -DDEBUG=0`

			`# The FBD driver requires NetBSD libc.`
			`MAN=`

			`BINDIR?= /usr/sbin`

			`.include <minix.service.mk>`