ramdisk-zfsroot: Only enable if zfs is enabled.

PR port-amd64/58316
PR port-amd64/57948 (followup pullup)

ramdisk-zfsroot: Enable build by default on amd64.

XXX Should maybe copy this to other ports like evbarm64 too.

PR port-amd64/57948

branches: 1.4.20;
Remove MKCRYPTO option.

Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed fifteen years ago, and are
essentially irrelevant for software with published source code.

In the intervening time, nobody bothered to remove the option after
its motivation -- the US export restriction -- was eliminated. I'm
not aware of any other operating system that has a similar option; I
expect it is mainly out of apathy for churn that we still have it.
Today, cryptography is an essential part of modern computing -- you
can't use the internet responsibly without cryptography.

The position of the TNF board of directors is that TNF makes no
representation that MKCRYPTO=no satisfies any country's cryptography
regulations.

My personal position is that the availability of cryptography is a
basic human right; that any local laws restricting it to a privileged
few are fundamentally immoral; and that it is wrong for developers to
spend effort crippling cryptography to work around such laws.

As proposed on tech-crypto, tech-security, and tech-userlevel to no
objections:

https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html
https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html
https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html

P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of
*bad* crypto that was conditional on it, e.g. DES in telnet... That
should probably be removed too, but on the grounds that it is bad,
not on the grounds that it is (nominally) crypto.

Omit cgd based ramdisks and miniroot modules if MKCRYPTO=no

Final part of PR kern/51282

Build the cgdroot ramdisk by default (for full-disk encryption support). It currently contains the same utilities found in an amd64 sysinst ramdisk, which should be useful in case of emergency.

branches: 1.1.20; 1.1.44; 1.1.50;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

x86: Release the ramdisks too.

This way we will get cgdroot.fs (and zfsroot.fs too) in the release.

PR misc/57534

branches: 1.16.2;
Add missing EFI bootloaders to the install kernel ramdisk,
noticed by Lloyd Parkes.

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)

branches: 1.14.2;
fix duplicated chunk from merge

Merge the [pgoyette-compat] branch

branches: 1.12.2;
Specify NOSANITIZER in distrib/amd64/ramdisks/common

This option cannot be set in distrib/common/Makefile.distrib as it's too
late, after including <bsd.own.mk> that will set MKSANITIZER.

This makes generation of ramdisk for amd64 with MKSANITIZER=yes successful.

branches: 1.11.8; 1.11.14;
PR install/50311: missing gptmbr.bin on ramdisk based installs.

branches: 1.10.10; 1.10.12;
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.9.6; 1.9.12;
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

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

branches: 1.3.2; 1.3.6;
Move and share a common termcap.mini file.

branches: 1.2.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.)

Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

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

branches: 1.3.46; 1.3.48;
Sync the ramdisks dot.profile file between amd64 and i386.

branches: 1.2.14;
Add /sbin/dmesg to ramdisk since /kern/msgbuf is a bit annoying.
mount_kernfs is still there because there is no size restriction.

branches: 1.1.20;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

Add missing EFI bootloaders to the install kernel ramdisk,
noticed by Lloyd Parkes.

branches: 1.21.2;
Make gzip on some crunched install media support xz decompression
(just like our base version does).

branches: 1.20.14; 1.20.16;
PR install/50311: missing gptmbr.bin on ramdisk based installs.

branches: 1.19.2; 1.19.4;
Include installboot on amd64/i386 install ramdisks in prep for a change
to sysinst which will use it instead of a handrolled replacement.

branches: 1.18.2;
Add sbin/gpt to amd64 install ramdisk.

Add support for ext2fs to i386/amd64 ramdisks.
This is usefull for setup with various xen hosting providers.
Prompted by Blair Sadewitz.

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

Fix indent.

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

branches: 1.13.2;
Sync ramdisks content across i386 and amd64. Biggest change is for amd64,
where configuration for crunchgen(1) is moved from ramdisk/ to common/.

For i386, only mbrlabel(8) and various LFS related binaries are added. Yes,
LFS. It was added to amd64 ramdisk 3 years ago, I believe it's for a good
reason... ?

branches: 1.12.2;
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.

Remove unnecessary gnu/usr.bin from SRCDIRS.

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

branches: 1.5.2; 1.5.6;
Move and share a common termcap.mini file.

branches: 1.4.2;
Add libexec to SRCDIRS so that the source of the newly added
lfs_cleanerd can be found.

Enable LFS from sysinstall.

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

Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

branches: 1.2.2;
Move and share a common termcap.mini file.

branches: 1.1.10;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

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

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

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.20; 1.1.30;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

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

branches: 1.1.20;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

Add newfs_msdos to amd64 install media, proposed on port-amd64@ back in
december.
newfs_msdos is needed to make a UEFI bootable disk.

branches: 1.14.42;
Add dkctl to install ramdisk so that you can enable disk writecaches before
install, if necessary.

branches: 1.13.4;
Sync ramdisks content across i386 and amd64. Biggest change is for amd64,
where configuration for crunchgen(1) is moved from ramdisk/ to common/.

For i386, only mbrlabel(8) and various LFS related binaries are added. Yes,
LFS. It was added to amd64 ramdisk 3 years ago, I believe it's for a good
reason... ?

branches: 1.12.2;
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.

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

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.8.2;
Make x86 installation use tmpfs.

branches: 1.7.2;
Add /sbin/dmesg to ramdisk since /kern/msgbuf is a bit annoying.
mount_kernfs is still there because there is no size restriction.

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

branches: 1.5.8; 1.5.10;
Include sysctl on the amd64 boot floppy. This is useful for allowing
people to test suspend/resume and can be used to find other values as
well.

branches: 1.4.2;
/libexec, not /usr/libexec.

Enable LFS from sysinstall.

Sync with i386: add sbin/raidctl to amd64's install ramdisk.

branches: 1.1.4;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

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

branches: 1.1.20;
Prepare creation of boot CDs:

* Move files in distrib/amd64:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

branches: 1.1.6; 1.1.10;
Build the cgdroot ramdisk by default (for full-disk encryption support). It currently contains the same utilities found in an amd64 sysinst ramdisk, which should be useful in case of emergency.

Add a symlink to /altroot/stand to help the kernel find modules.

branches: 1.1.6; 1.1.10; 1.1.24; 1.1.32;
Build the cgdroot ramdisk by default (for full-disk encryption support). It currently contains the same utilities found in an amd64 sysinst ramdisk, which should be useful in case of emergency.

branches: 1.2.2;
ramdisk-zfsroot: Build with -D_REENTRANT

zpool(8) requires libhack built with it.

zfs: build a ramdisk on amd64 with enough to mount rpool/ROOT on /

Until we get ZFS integrated into our boot loader, this is the next best
thing. The idea is simple - have a small FFS partition with a kernel,
modules and this ramdisk. Once the ramdisk boots it will mount the FFS
partition read only, copy the needed ZFS modules to the ramdisk and then
unmount the partition. Then we import the ZFS root pool, mount the
ZFS root filesystem and then pivot to it.

Because the initial FFS partition is not mounted at this point, we
can mount it in /altroot so we can replace the kernel and modules with
newer ones so it's easily maintainable.

This ZFS boot strapper currently makes the following assumptions:
* The device NAME=boot is the FFS with kernel, modules and this ramdisk.
* The ZFS root pool and root filesystem are called rpool/ROOT.

A boot.cfg menu entry can then be added like so:
menu=Boot ZFS root:fs /ramdisk-zfsroot.fs;boot

branches: 1.1.4;
zfs: build a ramdisk on amd64 with enough to mount rpool/ROOT on /

Until we get ZFS integrated into our boot loader, this is the next best
thing. The idea is simple - have a small FFS partition with a kernel,
modules and this ramdisk. Once the ramdisk boots it will mount the FFS
partition read only, copy the needed ZFS modules to the ramdisk and then
unmount the partition. Then we import the ZFS root pool, mount the
ZFS root filesystem and then pivot to it.

Because the initial FFS partition is not mounted at this point, we
can mount it in /altroot so we can replace the kernel and modules with
newer ones so it's easily maintainable.

This ZFS boot strapper currently makes the following assumptions:
* The device NAME=boot is the FFS with kernel, modules and this ramdisk.
* The ZFS root pool and root filesystem are called rpool/ROOT.

A boot.cfg menu entry can then be added like so:
menu=Boot ZFS root:fs /ramdisk-zfsroot.fs;boot