{usr.,}{s,}bin: replace LINT_SUPPORTED with the standard NOLINT

While here, re-enable lint in those cases where lint was skipped due to
a bug in interpreting abstract types, which was fixed in cgram.y 1.469
from 2023-08-02.

Force at most partial RELRO for rump_server and related libraries

rump_server with -l uses lazy resolution by default and thus cannot be
used with full RELRO/BIND_NOW.

usr.bin: enable lint checks for most programs in /usr/bin

Previously, lint was only activated for the libraries, but not for the
kernel or userland programs. Activate lint for the programs in /usr/bin
for now, more will follow later.

This only affects builds that set MKLINT=yes.

Allow to set sanitizer flags for the rump build from the
build.sh command line, like: -V RUMP_SANITIZE=address

More nofifo

Deal with fallout from the addition of
KERN_PROC_CWD in sysctl(3)
That is kern.proc.$$.KERN_PROC_CWD (I think - not that it matters here)

The effect is that -lrump now requires -lrumpvfs

This set of changes fixes (I believe) regular dynamic builds,
more might be required for static builds (will be verified soon).

branches: 1.12.10;
With the removal of HAVE_REGISTER_T from rumpuser_port.h, _KERNTYPES does not
need to be defined. This allows register_t to be typedef'd to RUMP_REGISTER_T
without conflict, as highlighted in PR kern/52206.

Revert previous change so builds can resume.
_KERNTYPES needs to be defined for NetBSD builds to succeed.
_KERNTYPES must not be defined for buildrum.sh builds to succeed.

Do not define _KERNTYPES as this breaks build with buildrump.sh due to
conflicting types for register_t.
Closes PR kern/52206
Steered in the right direction by christos.

branches: 1.9.6;
Define _KERNTYPES for things that need it.

Move sysproxy support into a separate component, rumpkern_sysproxy,
instead of it being always provided by the rump kernel base. This
move accomplishes two things:

1) it is no longer necessary to provide sysproxy hypercall stubs for
platforms which do not want to use sysproxy
2) it is easier to reason about the security aspects, since configurations
not linking the sysproxy component simply do not support remote
system calls

discussed on rumpkernel-users

Support disklabel partitions on all platforms.

also addresses buildrump.sh issue #41 (github)

Handle static rump kernel base correctly.

Need bsd.own.mk for mk.conf, include it at an opportune place.

Make it possible to omit libutil from the link. It's used only for
disklabel stuff, and is only harmful on platforms that don't currently
provide user namespace disklabel interfaces.

branches: 1.3.4; 1.3.10;
Allow to specify -d hostpath offset,size with disklabel.

branches: 1.2.2;
there's a manpage now ... just not here

Add rump_server which is just like rump_allserver with the exception
that it links in only -lrump instead of everything. The startup
time difference (especially when attaching a debugger) is noticeable.