NameDateSize

..Today4 KiB

bin/H10-Nov-2025153

compat/H10-Nov-202546

crypto/H10-Nov-202588

dev/HToday182

fs/HToday4 KiB

games/H10-Nov-202570

h_macros.hH A D20-Aug-20162.7 KiB

include/H10-Nov-20254 KiB

ipf/H10-Nov-20254 KiB

kernel/HToday4 KiB

lib/HToday4 KiB

libexec/H10-Nov-202570

MakefileH A D19-Aug-2023746

Makefile.incH A D24-Apr-2023480

modules/H10-Nov-20254 KiB

net/HToday4 KiB

READMEH A D18-May-2012941

rump/H10-Nov-2025135

sbin/H10-Nov-20254 KiB

share/H10-Nov-202559

sys/HToday137

usr.bin/HToday4 KiB

usr.sbin/H10-Nov-20254 KiB

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