all: fix "Invalid internal option" warning from make

branches: 1.3.2; 1.3.6;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

branches: 1.2.4;
Add an iso_image target (iso-image as a target name doesn't play well with
bsd.subdirs.mk) in distrib/makefile, which builds an iso image for $MACHINE
with binary sets, stored in ${RELEASEDIR}/iso. The image is bootable for:
alpha, amd64, cats, i386, pmax, sgimips, sparc, sparc64, sun3, vax.
mac68k/macppc no there yet because of missing feature in makefs.

call iso_image in distrib/ for iso-image in the top Makefile.

branches: 1.1.16;
allow "make release" to work. no install stuff yet though.

branches: 1.1.2; 1.1.14;
Add an iso_image target (iso-image as a target name doesn't play well with
bsd.subdirs.mk) in distrib/makefile, which builds an iso image for $MACHINE
with binary sets, stored in ${RELEASEDIR}/iso. The image is bootable for:
alpha, amd64, cats, i386, pmax, sgimips, sparc, sparc64, sun3, vax.
mac68k/macppc no there yet because of missing feature in makefs.

call iso_image in distrib/ for iso-image in the top Makefile.

Consistently use ${RELEASEDIR}/${RELEASEMACHINE} instead of
${RELEASEDIR}/${MACHINE} (Paul Ripke)

Now that we do not force debug sets off install CDs any more, explicitly
set CDRELEASE_NODEBUG everywhere.

branches: 1.5.10; 1.5.12;
Initial pass to be unaffected by build umask on build artifacts
1. ${MKDIR} -> ${MKDIR} ${MKDIRPERM}
2. ${CP} -> ${INSTALL} ${COPY} -m <perm>

branches: 1.4.2; 1.4.6; 1.4.54; 1.4.58;
Yank the bridge kernels from here too.

Now that we have support in ofwboot to correctly guess the right kernel,
produce a CD that works on both the 7044 and the pegasos.

- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

branches: 1.1.2; 1.1.6;
Add an iso_image target (iso-image as a target name doesn't play well with
bsd.subdirs.mk) in distrib/makefile, which builds an iso image for $MACHINE
with binary sets, stored in ${RELEASEDIR}/iso. The image is bootable for:
alpha, amd64, cats, i386, pmax, sgimips, sparc, sparc64, sun3, vax.
mac68k/macppc no there yet because of missing feature in makefs.

call iso_image in distrib/ for iso-image in the top Makefile.

branches: 1.3.2; 1.3.6;
Yank the bridge kernels from here too.

Change bsddisklabel.c to export it's functions rather than declaring them
all static. This makes it possible to write a md_make_bsd_partitions()
function without having to copy all of bsddisklabel.c into md.c.

Make ofppc sysinst install sanely and in a bootable manner on both my
7044, and my pegasos. The only thing the user needs to do is pick the
right kernel set.

branches: 1.1.2;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

branches: 1.1.2; 1.1.4; 1.1.8;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

1. Remove all the special handling of variables (-d -p -P -s -S) that
were dealing with DBG (-d) LDSTATIC/NOPIE (-p), and the rest with
disabling/enabling sanitizers.
2. Use emalloc/estrdup for all the allocators instead of only some cases.
3. Add -V varspec which passes variables on the command line (as DBG
and LDSTATIC used to be passed before) instead of appending them
to the on-the-fly Makefile using -v varspec.
4. Change the distrib and rescue Makefiles to use -V instead of the removed
flags.

The motivation of this is to make variable handling consistent, less magical,
and remove the need for changing crunchgen each time we want to add disabling
an option by default.

(as proposed in tech-toolchain)

set MAKEDEVTARGETS=ramdisk so that the ramdisk /dev/ is populated.
from PR#51659.

branches: 1.8.30; 1.8.32;
In distrib/*/ramdisks/common/Makefile.ramdisk, allow the caller to
pre-define the LISTS variable if they do not want it to include
${.CURDIR}/lists. This opens the possibility of making some of the
many distrib/*/ramdisks/*/lists files shared in the future.

XXX: Some of the differences between these files seem to be unnecessary.

branches: 1.7.6; 1.7.12;
Remove terminfo.db as it's now embedded in libterminfo.

Use the rescue terminfo.db in our images instead of termcap.

Replace references to local and now no-longer-existing termcap files
with references to ${DISTRIBB}/common/termcap. Hi, abs@!

${NETBSDSRCDIR}/distrib/common/protocols => ${DISTRIBDIR}/common/protocols
${NETBSDSRCDIR}/distrib/common/services => ${DISTRIBDIR}/common/services

Change ramdisks from dhclient to dhcpcd and add corresponding glue to
sysinst. For amd64, the crunchgen binary shrinks by 150KB uncompresssed,
60KB compressed.

branches: 1.2.2;
Use the cutdown distrib/common/services and distrib/common/protocols
rather than the full fat etc versions

branches: 1.1.2; 1.1.4; 1.1.8;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

PR install/54780: in the (of course totally unlikely) case that sysinst
should crash, run "stty sane".

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.74; 1.1.76;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

Fix indent.

Remove unnecessary gnu/usr.bin path from SRCDIRS.

branches: 1.8.4;
Remove terminfo.db as it's now embedded in libterminfo.

Use the rescue terminfo.db in our images instead of termcap.

34 different termcap subsets, plus a couple of ports still using
the full termcap distfile. In an attempt to reduce the madness
switch everyone (except the i386 cd install which does its own
thing) to the same (under 8K) termcap subset:

ansi ansi/pc-term compatible with color
dumb|unknown 80-column dumb tty
hp300h HP Catseye console
iris-ansi-ap IRIS ANSI in application-keypad mode
iris-ansi|iris-ansi-net IRIS emulating 40 line ANSI terminal (almost VT100)
sun|sun1|sun2|sun-il Sun Microsystems Inc. console with working insert-line
vt100|vt100-am DEC VT100 (w/advanced video)
vt220-8 DEC VT220 8 bit terminal
vt220|vt200|vt300 DEC VT220 in vt100 emulation mode
wsvt25 NetBSD wscons in 25 line DEC VT220 mode
wsvt25m NetBSD wscons in 25 line DEC VT220 mode with Meta
x68k|x68k-ite NetBSD/x68k ITE
xterm|vs100 xterm terminal emulator (X Window System)

Trying to provide similar functionality across all ports? It'll never
catch on...

${NETBSDSRCDIR}/distrib/common/protocols => ${DISTRIBDIR}/common/protocols
${NETBSDSRCDIR}/distrib/common/services => ${DISTRIBDIR}/common/services

Fix indent on common/protocols changes.

branches: 1.3.2;
Use the cutdown distrib/common/services and distrib/common/protocols
rather than the full fat etc versions

branches: 1.2.2; 1.2.6;
Change bsddisklabel.c to export it's functions rather than declaring them
all static. This makes it possible to write a md_make_bsd_partitions()
function without having to copy all of bsddisklabel.c into md.c.

Make ofppc sysinst install sanely and in a bootable manner on both my
7044, and my pegasos. The only thing the user needs to do is pick the
right kernel set.

branches: 1.1.2;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

Adjust for sysinst move.

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.36; 1.1.50;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

branches: 1.1.2; 1.1.4; 1.1.8;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

34 different termcap subsets, plus a couple of ports still using
the full termcap distfile. In an attempt to reduce the madness
switch everyone (except the i386 cd install which does its own
thing) to the same (under 8K) termcap subset:

ansi ansi/pc-term compatible with color
dumb|unknown 80-column dumb tty
hp300h HP Catseye console
iris-ansi-ap IRIS ANSI in application-keypad mode
iris-ansi|iris-ansi-net IRIS emulating 40 line ANSI terminal (almost VT100)
sun|sun1|sun2|sun-il Sun Microsystems Inc. console with working insert-line
vt100|vt100-am DEC VT100 (w/advanced video)
vt220-8 DEC VT220 8 bit terminal
vt220|vt200|vt300 DEC VT220 in vt100 emulation mode
wsvt25 NetBSD wscons in 25 line DEC VT220 mode
wsvt25m NetBSD wscons in 25 line DEC VT220 mode with Meta
x68k|x68k-ite NetBSD/x68k ITE
xterm|vs100 xterm terminal emulator (X Window System)

Trying to provide similar functionality across all ports? It'll never
catch on...

branches: 1.1.2; 1.1.4; 1.1.8;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

Ten identical list.inet6 files, or one common/list.inet6?
Not a difficult choice.

Change ramdisks from dhclient to dhcpcd and add corresponding glue to
sysinst. For amd64, the crunchgen binary shrinks by 150KB uncompresssed,
60KB compressed.

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.16;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

nvi has moved.

branches: 1.8.2; 1.8.8;
Update location of "less" source directory to the build of various
install medias.

Use src/distrib/utils/x_gzip in all install ramdisks/miniroots for now
since installation file systems might be flooded by -llzma.

branches: 1.6.4;
Adjust file lists for recent move:
usr/sbin/chown -> sbin/chown
usr/bin/chgrp -> bin/chgrp

Use the rescue terminfo.db in our images instead of termcap.

Change ramdisks from dhclient to dhcpcd and add corresponding glue to
sysinst. For amd64, the crunchgen binary shrinks by 150KB uncompresssed,
60KB compressed.

branches: 1.3.4;
usr.bin/vi/build -> usr.bin/nvi/build

Add -lprop to the LIBS line so that ifconfig will link.

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.10;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.

Ten identical list.inet6 files, or one common/list.inet6?
Not a difficult choice.

branches: 1.1.2; 1.1.4; 1.1.8;
- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.

- create a mostly working sysinst/ramdisk environment. i was
able to successfully run sysinst, but the screen displays many
"bad format `p'" errors i am yet to track down entirely that
make it somewhat difficult to see.