dig/host/whatever assumes that it is using BIND8 code. mixing BIND4 in
libc with BIND8 code will result in very strange behavior, or program panics.
it is not necessary for dig/host/whatever to obey /etc/nsswitch.conf, actually
dig(1) is explicit about it.
now dist/bind is almost clean BIND822p5, with the following exception:
- /etc/irs.conf will never be visited when running BIND8 toolchain,
to make it less complex. the search order for BIND8 toolchain is
defined in dist/bind/lib/irs/gen.c:default_map_rules().
and usr.sbin/bind compiles them in BSD make framework, with no tricks at all.
- Move SEE ALSO section before the HISTORY section as described in
mdoc(7) with:
+ removing traing dot.
+ spliting files into FILES section.
- Refer pathnames using .Pa (rather .Ar or .Xr).
this changes function prototype for __ivalid*.
This commit breaks binary compatibility for __ivalid*. I believe this can be
forgiven due to the following:
- this is not really exported function. no function prototype is in headers.
function name starts with underbars. No third-party applications are
expected to use it.
- the function was introduced very recently, when rcmd.c was made IPv6-ready.
- the only customer in NetBSD tree is lpd.
(lpd.c) sync with rcmd.c change.
on each of them, and don't bother listening on them. this allows messages
to be forwarded even with -s enabled.
XXX: not 100% sure if this is susceptable to a DoS, e.g someone filling
up kernel buffers with a backlog of packets not being read, but shutdown(2)
should prevent that even if it possibly doesn't at this time.
* minor KNF
dev/vndvar.h or dev/ccdvar.h so that struct pool is always available
regardless of multiple inclusion. Actually, ccdconfig.c compiles without
this change but ...
per mount point, the way ``try to export and unexport an unnecessary
mount point later'' may leave unwanted information in the kernel, and
doesn't work if a mount point is default exported or publically exported.
To fix the race condtion, we need another way.
version 0 RMT protocol, the query of status makes no sense (send back, in
binary, the mtget structure), but systems sometimes use it anyway. And when
they use it, they get upset if they get back something that is a different
size from what they expect. The original mtget structure in BSD 4.3 is
24 bytes in size, and that seems to be what they can cope with.
The correct fix would be to go to Version 1 RMT, but that's a horse of
another color...
tsubai