are development snapshots (although not as "bleeding edge" as current).
Per tron@'s suggestion.
This way we get consistent messages along the development process. Otherwise,
STABLE could carry no message while a RC could, disappearing again after the
real formal release. With this change only formal releases do not carry any
special message in motd.
a release candidate), tell the user that he might expect problems and how
to effectively report them to the developers.
No objections in tech-userlevel@; only positive responses.
NetBSD Foundation Membership still pending.) This stack was written by
Iain under sponsorship from Itronix Inc.
The stack includes support for rfcomm networking (networking via your
bluetooth enabled cell phone), hid devices (keyboards/mice), and headsets.
Drivers for both PCMCIA and USB bluetooth controllers are included.
Only slightly dissimilar to the one Chuck Silvers posted to tech-toolchain.
Builds are now likely to proceed as far as running out of space in the
install media.
snap_pre so that make will execute it before building the kernels.
This is all because .WAIT doesn't recursively apply to dependencies.
Add some .PHONY and .MAKE so that child makes use the same job pipe.
specification in .../mtree/NetBSD.dist, run ${TOOL_MTREE} again with
different args to register the new directories in the metalog.
Previously, these directories were not mentioned at all
in the metalog.
Reviewed by agc
named(8) looks for it. You can now really get a caching name server
by simply setting "named=yes" in "/etc/rc.conf" as documented in
The NetBSD Guide. This fixes PR bin/30662 by Christian Hattemer.
makes the field overflow even on archs where ${MACHINE} is pretty short.
Also rearange MKISOFS_FLAGS so that they default to -quiet unless the
user explicitly asks for -v. Add -hide-joliet-trans-tbl to get rid of
the TRANS.TBL files on modern OSs.
headers and LKM.
Add MKPF; if set to no, don't build and install the pf(4) programs,
headers, LKM and spamd.
Both options default to yes, so nothing changed in the default build.
Reviewed by lukem.
added to the CD-ROM (only if they exist), as proposed on tech-install
and tech-toolchain without objections. Note, this will "bloat" the CD-ROM
image if you have done a "./build.sh sourcesets". If you don't want that,
just move "source" out of ${RELEASEDIR} for the "make iso-image".
some files were imported to the different places from the previous version.
v3_5:
etc/pf.conf
etc/pf.os
etc/spamd.conf
share/man/man4/pf.4
share/man/man4/pflog.4
share/man/man5/pf.conf.5
share/man/man5/pf.os.5
share/man/man5/spamd.conf.5
v3_6:
dist/pf/etc/pf.conf
dist/pf/etc/pf.os
dist/pf/etc/spamd.conf
dist/pf/share/man/man4/pf.4
dist/pf/share/man/man4/pflog.4
dist/pf/share/man/man5/pf.conf.5
dist/pf/share/man/man5/pf.os.5
dist/pf/share/man/man5/spamd.conf.5
different cd-rom image (e.g. using the INSTALL_LAPTOP-derived boot
image), make it possible to add a string to the cd-rom image name
by setting the optional environment variable CDROM_NAME_ADD.
* most files are installed with CONFIGFILES (from bsd.files.mk)
* empty files are created in a cleaner fashion
* MAKEVERBOSE is supported for the remaining custom items
target) instead of using home-grown 'distribution' targets or using
FILES with the 'install' target.
Add some etc/ subdir Makefiles where appropriate.
XXX: some of etc/Makefile install-etc-files could be converted to CONFIGFILES.
