ftp://ftp.NetBSD.org/pub/NetBSD/packages/{VERSION}/{MACHINE}/All
to newer one:
ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/{MACHINE}/{VERSION}/All
which is documented in the pkgsrc guide, and also note the alternative path:
/pub/NetBSD/packages/current-packages/NetBSD/{MACHINE}/{VERSION}/All
for mirrors which don't mirror /pub/pkgsrc but have only /pub/NetBSD.
- basic resolvconf like functionality to combine the resolv.conf entries
from running instances
- improve timer handling to not break with early wake ups and other edge
cases related to the kernel time granularity
- improve handling of dhcpcd -n and rebinding after carrier loss to
better deal with changing networks
- add option to black list servers based on server id
- don't check for ARP conflict if the interface already has the address
- improve signal handling during vfork/exec
Major changes are:
- better detection of double applied patches
- rejects remain unified diffs for unified patches
- far less limitations, e.g. patch lines may be arbitrary long
This addresses PR standards/11220 by changing patch -b behavior to be
POSIX compliant. Old behavior can be obtained using --suffix, which
works since NetBSD 1.4. pkgsrc has been adjusted accordingly.
as snap_md_post target in etc/etc.${MACHINE}/Makefile.inc rather than
as release target in distrib/${MACHINE}/Makefile so that builds for
release in distrib/${MACHINE}/Makefile don't have to be serialized.
XXX: maybe ramdisk kernels should be installed into binary/kernel dir
XXX: as other ports rather than installation dir, and
XXX: kernel config names should be preserved in their filenames.
in src/distrib/common/Makefile.image so that ${MAKESUMS} will be invoked
after the target image is installed into the releasedir, not before,
even if make -jN is specified.
XXX some ports do ${MAKESUMS} for installation/miniroot files
XXX in etc/etc.${MACHINE}/Makefile.inc later again.
image is installed properly
- INSTALL_IPAQ should be in BUILD_KERNELS rather than KERNEL_SETS
since it requires ramdisk image by mdsetimage(8) in src/distrib
bits that the 'user' can change.
Who knows what the effect of a user signal handler (which I think might have
access to the bits) changing these bits might be!
