Tests for the compat_linux inotify framework from GSoC 2023 (Theodore Preduta)

Remove MKCRYPTO option.

Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed

Remove MKCRYPTO option.

Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed fifteen years ago, and are
essentially irrelevant for software with published source code.

In the intervening time, nobody bothered to remove the option after
its motivation -- the US export restriction -- was eliminated. I'm
not aware of any other operating system that has a similar option; I
expect it is mainly out of apathy for churn that we still have it.
Today, cryptography is an essential part of modern computing -- you
can't use the internet responsibly without cryptography.

The position of the TNF board of directors is that TNF makes no
representation that MKCRYPTO=no satisfies any country's cryptography
regulations.

My personal position is that the availability of cryptography is a
basic human right; that any local laws restricting it to a privileged
few are fundamentally immoral; and that it is wrong for developers to
spend effort crippling cryptography to work around such laws.

As proposed on tech-crypto, tech-security, and tech-userlevel to no
objections:

https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html
https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html
https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html

P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of
*bad* crypto that was conditional on it, e.g. DES in telnet... That
should probably be removed too, but on the grounds that it is bad,
not on the grounds that it is (nominally) crypto.

show more ...

Don't build tests that depend on RUMP if BSD_MK_COMPAT_FILE is defined.

Run tests in kyua-atf-compat if MKKYUA!=no.

Stop assuming that test programs and directories are the same thing during
Atffile generation.

This is needed to be able to generate Kyuafiles (coming later), as these
clearly differentiate between

Stop assuming that test programs and directories are the same thing during
Atffile generation.

This is needed to be able to generate Kyuafiles (coming later), as these
clearly differentiate between the definition of test programs and the
recursion into other subdirectories (or files).

In particular: rename ATFFILE_EXTRA_TPS to ATFFILE_EXTRA_SUBDIRS and
change the logic in bsd.test.mk to keep track of subdirectories aside from
_TESTS when creating the Atffile.

show more ...

Register kyua-cli into the Atffile when MKKYUA!=no.

Auto-generate the top-level Atffile.

This fixes a problem in MKKYUA=no builds in which the kyua-testers
subdirectory in /usr/tests was created unconditionally and atf-run was
confused because such s

Auto-generate the top-level Atffile.

This fixes a problem in MKKYUA=no builds in which the kyua-testers
subdirectory in /usr/tests was created unconditionally and atf-run was
confused because such subdirectory didn't have an Atffile of its own.
(Due to the way our directory creation and file lists work, I'm not
sure it's possible to just not "install" the empty directory. But
that'd be an alternative to this.)

Auto-generating the Atffile causes it to only list the subdirectories
listed by the Makefile, which can vary depending on various MK* options.

Problem found by martin@.

show more ...

Move tests for examples from tests/examples to tests/share/examples.

This is to match the layout of the installed and source files more closely.
While doing this, honor the MKSHARE variable, as the

Move tests for examples from tests/examples to tests/share/examples.

This is to match the layout of the installed and source files more closely.
While doing this, honor the MKSHARE variable, as the files these tests
validate are only installed when MKSHARE=yes.

show more ...

Add placeholder test programs for share/mk files.

The main goal of this change is to simplify the further addition of test
cases for the share/mk infrastructure by adding a few placeholder test
prog

Add placeholder test programs for share/mk files.

The main goal of this change is to simplify the further addition of test
cases for the share/mk infrastructure by adding a few placeholder test
programs to the tests tree.

To not leave these test programs empty, I have added a bunch of extremely
simple test cases to them.

show more ...

Exclude tests that use rump

Only descend into ipf if MKIPFILTER != "no"

Deprecate tests/toolchain.

Deprecate tests/util.

Add tests to ensure that the new asm examples build and run, just as the
end-user is supposed to work with them.

only decent into crypto/tests if ${MKCRYPTO} != "no". (sets are probably
also broken, but i didn't get that far yet.)

Remove syscall SUBDIR.

evbppc can do modules now.

Add tests to check "cc" can compile a working hello world.
(this test fails at least on riz's macppc)

add tests for the -d functionality of rump_server(1)

Avoid double-inclusion of bsd.subdir.mk file. This eliminates some harmlessnbut annoying warning messages.

do the alphabet

Hook traceroute test case to build. it was added to lists so unbreak build now.

Make tests set generation optional, skipped for MKATF=no build.

Add some basic tests of resize_ffs(8). The 'grow' test does nothing
more than create an empty file system, grow it, and makes sure fsck
finds the result clean. The 'shrink' test does likewise for s

Add some basic tests of resize_ffs(8). The 'grow' test does nothing
more than create an empty file system, grow it, and makes sure fsck
finds the result clean. The 'shrink' test does likewise for shrinking,
but is an expected failure at the moment due to PR bin/44177.

show more ...

Add test of pad(4): stuff some audio into /dev/audio, read it from
/dev/pad. Test that we got sensible output by comparing against
a previous audibly good result.

This exercises auconv, audio and p

Add test of pad(4): stuff some audio into /dev/audio, read it from
/dev/pad. Test that we got sensible output by comparing against
a previous audibly good result.

This exercises auconv, audio and pad.

show more ...