Update location of "less" source directory to the build of various
install medias.

Remove unnecessary gnu/usr.bin path from SRCDIRS.

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

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

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...

Nothing needs disktab anymore, so we'd rather have an inode and
slightly over 1K of space on install media...

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

Alas poor dot.hdprofile. I knew him... not at all Horatio. (Remove)

Of the arious list files 28 said
PROG usr/bin/gzip usr/bin/gzcat usr/bin/gunzip
while 14 picked
PROG usr/bin/gzip usr/bin/gunzip usr/bin/gzcat

Make them all choose the former. No functional change.

Fix indent on common/protocols changes.

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.11.2;
Use the cutdown distrib/common/services and distrib/common/protocols
rather than the full fat etc versions

Pare down the size of the INSTALL kernel images. This was done by:

1) Removing chio, rcmd, restore, scsictl, shutdown and slattach
from the ramdisk images
2) Removing the isp* driver from the INSTALL kernel configs
3) Reducing the memory disk and ramdisk size back from 4400 to 4200 blocks

As a result, also remove mention as QLogic ISP controllers as being
supported by the installation.

With this, the INSTALL kernel images should once again be usable;
the firmware apparently imposes a size limit around 5MB on the files
it will load.

Longer-term, this port probably ought to get it's own stand-alone boot
loader, so that it might use e.g. loadable modules.

branches: 1.9.4;
Add -lprop to the LIBS line so that ifconfig will link.

branches: 1.8.2; 1.8.6; 1.8.8;
- use common/termcap.mini
- set TERM=wsvt25

branches: 1.7.4;
Since /etc/services has gotten rather large, use a minimal one for install
kernels. (mount_nfs is notably the only binary that doesn't gracefully deal
with the lack of an /etc/services file, it appears.)

Only use ping6 and rtsol if ${USE_INET6} != "no".
Part of PR 28994.

Add -lz, now needed by gzip.

Add more bits the cats install disk.
Most noticeable change is the addition of dhclient, we now prompt if the
user wants DHCP autoconfiguration.
Also added chio, rcmd, ping6, rtsol, scsictl

We now use the cut down versions of:
dhclient, ifconfig, ping, ping6 and route

The ramdisk has grown by about 200k, however the kernel can take that, we're
still a few 100k from the current 5MB limit for cats kernels.

replace _SRC_TOP_ with NETBSDSRCDIR, since the latter is the "public" version

consistency cleanup

The results of my cats NWDO hacking.

This was tested using a custom INSTALL kernel. The current one is >4Mb
which the cats firmware can't currently boot. We need to decide what
needs to be removed from INSTALL.