all: fix "Invalid internal option" warning from make

Restore having a BIOS-only amd64 USB image.

Several people reported having hardware that struggles booting the mix
EFI+BIOS image, and it's better to offer them a working image.

Keeping the EFI image as having the obvious name, this is going to become
more likely to work by default as newer hardware may not support BIOS boot.

(XXX pullup-9)

rename amd64 uefi-installimage to be just installimage.

Works for both purposes, no confusing name.

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

make amd64 EFI install image

XXX merge to installimage?

branches: 1.11.2; 1.11.4;
Omit cgd based ramdisks and miniroot modules if MKCRYPTO=no

Final part of PR kern/51282

Obey MKKMOD=no.
From Rin Okuyama in PR install/50061.

Restore unintentionally deleted file, which prevented building of any
install media. PR port-amd64/49558.

Nuke the five(!) install floppies. Welcome to 2015. Approved by
dsl@, Master of Port.

branches: 1.7.6;
Enabled building the kernel module containing the ramdisk required for full-disk encryption support by default. This should be the last part necessary on the amd64 port.

XXX reproduce and test on the i386 port
XXX implement support for full-disk encryption installs in sysinst

branches: 1.6.6;
Add "live-image" and "install-image" target support to build.sh.

"live-image" target builds pre-installed disk images that can be used on
emulators or boot from USB memory sticks to try NetBSD without installation.
Currently amd64, i386, pmax, sparc, sparc64, sun2, sun3, and vax
(which have working emulators and don't require extra tools like preparing
msdosfs or partitioning MD label structures) support this target.

"install-image" target builds an bootable installation disk image that can
be used as an install CD but burned into USB memory sticks etc.
Current only amd64 and i386 (which would support USB boot) have this target.

For more details (and known issue) see following posts on netbsd-bugs@:
http://mail-index.NetBSD.org/netbsd-bugs/2011/08/06/msg023639.html
http://mail-index.NetBSD.org/netbsd-bugs/2011/09/23/msg024207.html
http://mail-index.NetBSD.org/netbsd-bugs/2011/12/07/msg025166.html
http://mail-index.NetBSD.org/netbsd-bugs/2011/12/08/msg025178.html

No particular comments about implementation, and
"go ahead" comments from mrg@, riz@ and christos@.

Closes PR toolchain/45153 and PR misc/45155.

branches: 1.5.6;
Build miniroot.kmod installation module for amd64. Hook GENERIC
with it.

See http://mail-index.netbsd.org/port-i386/2011/01/14/msg002247.html

branches: 1.4.12;
Use the new common/Makefile.bootcd to make i386 and amd64 bootable ISO
images. amd64 gets a single kernel; i386 images gets 3 kernels:
- netbsd, copy from netbsd-INSTALL_LARGE.gz, loaded by default
- nbsd-l, copy from netbsd-INSTALL_LAPTOP.gz
- nbsd-i, copy from netbsd-INSTALL.gz for those who want the traditionnal
non-ACPI kernel
- drop the bootcd-laptop image
both gets an installcd image, which is the same as bootcd but with the
binary sets in addition to kernels.

branches: 1.3.4;
Add & enable boot-CDs (with ramdisk kernels only, no install sets),
built as part of a regular release. For more information, see
http://mail-index.netbsd.org/tech-install/2006/05/11/0001.html

OK: core@

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_64 -> amd64