does not install the un-patched ramdisk kernels. The snap_md_post
target builds the installation ramdisk image, patches that into the
ramdisk kernels, and installs them. Also the miniroot.
Automated snapshot build works now.
ld.so.conf. (Frankly, new systems shouldn't ship with a ld.so.conf.) We
use rpath for that purpose now. Unfortunately, 1.4 won't have this
change, so it will be in 1.4.1.
rc.subr to the default rc.conf.
While this is no longer necessary to supress noise,
it increases the clarity of the situation and removes
one more bit of what should be adjustable configuration
from scripts that site admins shouldn't have to edit.
Addresses PRs misc/7406 and (partially) bin/7491.
+ Make installation/diskimage installation/netboot in ${RELEASEDIR}
+ snap_md_post depends on the diskimage, the diskimage tar file and
the install kernel, and installs these into the right places in
${RELEASEDIR}.
port-specific Makefiles can add to.
+ Separate snap_md into snap_md_pre and snap_md_post that are depended
on before and after snap_kern.
+ Build all kernels listing in ${BUILD_KERNELS}, but don't put them in
${RELEASEDIR}.
file that just does "include" GENERIC, and therefore has no "config" line.
It's simplest to assume that "netbsd" will be the result in that case.
Rather than duplicate config(8)'s parser in awk (or something), we should
adjust config to parse the config file and spit out the kernel names, and
then use that to replace this awk script thing.
kernel per config file and the resulting kernel need not be named
"netbsd"; therefore paw through the config file after the kernel
builds are done, find them all, and put them where they belong per
release(7). This all done with some clever awk/sh scripting, from
PR 7180 by David Forbes.
of "local" it will not mount filesystem types it identifies as
network file systems (currently just nfs). Call the function twice,
before networking starts with arg "local", after networking starts
with arg "network". Remove critfs_require_network as is now redundant.
christos