Name
Date
Size
#Lines
LOC

..--

bin/H--5,0103,573

crypto/H--3,0141,931

dev/H--2,6021,729

fs/H--23,92416,776

games/H--6932

include/H--5,8884,644

ipf/H--18,12416,289

kernel/H--5,6693,687

lib/H--88,49059,718

libexec/H--1,568801

modules/H--1,5901,012

net/H--17,80212,624

rump/H--3,4622,120

sbin/H--1,9051,212

share/H--575340

sys/H--1,047668

usr.bin/H--17,72615,143

usr.sbin/H--1,002699

MakefileH A D31-Dec-2015799 4830

Makefile.incH A D06-Dec-2013207 107

READMEH A D26-Feb-2013941 2115

h_macros.hH A D15-Oct-20152.6 KiB8645

README

1$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $
2
3When adding new tests, please try to follow the following conventions.
4
51. For library routines, including system calls, the directory structure of
6   the tests should follow the directory structure of the real source tree.
7   For instance, interfaces available via the C library should follow:
8
9	src/lib/libc/gen -> src/tests/lib/libc/gen
10	src/lib/libc/sys -> src/tests/lib/libc/sys
11	...
12
132. Equivalently, all tests for userland utilities should try to follow their
14   location in the source tree. If this can not be satisfied, the tests for
15   a utility should be located under the directory to which the utility is
16   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
17   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
18   even though the source code for the program is located under src/external.
19
203. Otherwise use your own discretion.
21