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

Add "DVD" ISOs for x86 that don't have to follow CD size limitations.

These include all available sets.

branches: 1.3.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.2.2;
Add example on how to make an install CD - it's the same
as the bootcd* CDs just with the install sets added to
the CD as well.

XXX 1) The implementation of this is rather cludgy (copying sets around),
as our makefs(8) can't put files from multiple directories into
one image -- something that mkisofs can do with 'graft' points
XXX 2) This should be run after 'build.sh release' - It would be nice
if we had a seperate stage to add such hooks in our build framework

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@

Add a __cdromclean target so we can add arch-specific rules to it and use
it to clean efiboot

Actually include a bootable kernel in the KERNEL_DIR boot images.

This enables us to actually boot the image into qemu from /netbsd/kernel
and load modules from /netbsd/modules/... , keeping the modules and
kernel together, and removing kernel version numbers from the modules'
path.

From christos@

LGTM, commit it...

Add new file-system spec.in for KERNEL_DIR=yes

branches: 1.29.2;
Add the extra spec for the amd64 cdroms

Remove modules set from the i386 install cd

It is not particularly useful to be able to load modules while
installing on i386, probably the most useful one is dtrace,
and this takes up about 20mb on a port that is already exceeding
CD limits. Most stuff you'd want to use while installing is already
in GENERIC.

The modules set is still available compressed for installing into
a target system, meaning modules are available after installation.

While here, add man set to the installation DVD, it's helpful to be able
to read e.g. the man page for fdisk when rescuing a system.

Move DRM-driver firmware from base to its own set, gpufw

This set is only installed on amd64,i386,evbarm.
This set is installed on minimal installs and on install media, in
case someone needs it for basic driver functionality.

Comments:
Switched to a single MK tunable for it - that is probably unneeded.

An upcoming DRM update will include even fatter firmware, and we'd
like to minimize the impact of it.

distrib/amd64/cdroms: honor CDBOOTOPTIONS when installing EFI bootloader

Revert "distrib/amd64/cdroms: honor CDBOOTOPTIONS when installing EFI bootloader"

https://mail-index.netbsd.org/current-users/2021/02/17/msg040358.html
I think this change had unexpected side effects and needs further review

distrib/amd64/cdroms: honor CDBOOTOPTIONS when installing EFI bootloader

MKREPRO_TIMESTAMP fixes for efiboot

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

amd64: make BIOS and UEFI dual bootable iso image.

branches: 1.20.2; 1.20.4;
Obey MKKMOD=no.
From Rin Okuyama in PR install/50061.

Make sure to copy the language catalog files for sysinst, but do not
copy sysinst itself to / on the CD, and instead use the base version
for installation.

Do not default any CD_SETS - let the MD makefiles request them specifically.

2nd try: make amd64, i386, sparc64 and vax iso images use full sets.
While there fix an old bug that makefs used the build hosts /etc/group
and passwd information when creating the image.
Thanks to Andreas Gustafsson for extensive testing.

Add full libexec contents to the CD image - this makes dhcpcd happy.

Revert previous untill fallout has been fixed.

Add a new simple method to put whole sets on CD images (instead of
listing single binaries or patterns) and use those for the existing
ISO images.

Add libpthread.so* - new lzma needs it.

Punt custom dhcpcd hooks in favour up upstream hooks

CD images need libarchive if MKBSDTAR is yes.

branches: 1.10.2;
Adjust for sysinst move.

PR install/48818: put vi on install CDs

branches: 1.8.8;
PR/47276: ftp has https support now

branches: 1.7.2;
Switch terminfo(3) to cdb(5).

branches: 1.6.2; 1.6.4;
Include liblzma to unbreak gzip on the install CD.

Include libgcc_s.so symlinks in /usr/lib, so that binaries in /usr
linked against it actually work.

branches: 1.4.2;
On install CDs: make ^C and ^Z work (mostly) as they used to do on
crunched/ramdisk install media again.
Fixes the remaining parts of PR 44738.

Mirror a change that was made on i386 by gdt@.

XXX i386 and amd64 distrib have lots in common, maybe more files/logic
could/should be shared.

Message log reads:

Use ${INSTALL} ${COPY} instead of ${CP}.

This avoids a problem where files with mode 0400 (CVSREAD=t) are
copied to OBJDIR and then can't be re-copied on a subsequent build.
ok joerg@

branches: 1.2.2;
Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

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

kernfs no longer needs a hacky workaround to make rootdev appear.

branches: 1.2.24;
Create /var/tmp for vi. Pointed out by Izumi Tsutsui.

branches: 1.1.12; 1.1.24;
Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

Enable basic command line editing in amd64 installer shells

When a user selects "exist installer" or hits ^Z in sysinst, the
calling install.sh runs a shell, plus shows a message indicating
they can type "exit" to return to the installer.

Add -E to the arguments to this shell, to enable command line editing,
(primarily for arrow keys, but basic emacs sequences will also work)

At this point this is only on amd64, as this is the port which is
least likely to be installing on particularly esoteric terminal
hardware, and is also likely to have the highest proportion of less
experienced users

branches: 1.4.26;
Make sure to copy the language catalog files for sysinst, but do not
copy sysinst itself to / on the CD, and instead use the base version
for installation.

Switch device database to cdb(5). Rework ttyname(3) and ttyname_r(3) to
depend on new devname_r(3) as heart. Add /dev/pts magic directly to
devname(3). While it can lead to returning non-existing paths, the
behavior is more consistent that way. Drop caching layer in devname(3),
it doesn't buy anything for the common case of having access to the
database. Teach devname(3) proper fallback behavior of scanning /dev.
Create both old-style and new-style database for now in /etc/rc.d/sysdb.

branches: 1.2.4; 1.2.6;
On install CDs: make ^C and ^Z work (mostly) as they used to do on
crunched/ramdisk install media again.
Fixes the remaining parts of PR 44738.

Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

branches: 1.1.4;
Add new file-system spec.in for KERNEL_DIR=yes

distrib/amd64/cdroms/spec.in: Add buffer line after $NetBSD$.

Reduces chance of merge conflicts when changing content we might
plausibly edit. No functional change intended.

Add $NetBSD$ keyword

branches: 1.1.2;
Add the extra spec for the amd64 cdroms

Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

Add a boot.cfg file to bootcds as well as i386.

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

Express more confidence in our ability to boot on hardware with ACPI
enabled and don't warn our users that it might not and already suggest
workarounds.

The ability to disable ACPI and SMP is still there, by dropping to
the boot prompt.

branches: 1.3.48;
Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

Remove trailing whitespace.

Add a boot.cfg file to bootcds as well as i386.

distrib/amd64/cdroms: honor CDBOOTOPTIONS when installing EFI bootloader

Revert "distrib/amd64/cdroms: honor CDBOOTOPTIONS when installing EFI bootloader"

https://mail-index.netbsd.org/current-users/2021/02/17/msg040358.html
I think this change had unexpected side effects and needs further review

distrib/amd64/cdroms: honor CDBOOTOPTIONS when installing EFI bootloader

Add a comment about iLO

branches: 1.5.48;
Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

fix a typo in a comment

Add a boot.cfg file to bootcds as well as i386.

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

Exclude compat sets from ISO images that struggle to fit on a CD-ROM

When debug is excluded, also exclude the compat debug sets.

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.4.46; 1.4.48;
Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

Also add boot.cfg into the installation CD, as was intended by ad@.

branches: 1.2.12; 1.2.14;
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.1.2;
Add example on how to make an install CD - it's the same
as the bootcd* CDs just with the install sets added to
the CD as well.

XXX 1) The implementation of this is rather cludgy (copying sets around),
as our makefs(8) can't put files from multiple directories into
one image -- something that mkisofs can do with 'graft' points
XXX 2) This should be run after 'build.sh release' - It would be nice
if we had a seperate stage to add such hooks in our build framework

Express more confidence in our ability to boot on hardware with ACPI
enabled and don't warn our users that it might not and already suggest
workarounds.

The ability to disable ACPI and SMP is still there, by dropping to
the boot prompt.

branches: 1.3.48;
Bring amd64 installation ISO to same state as the i386 one:
- GENERIC kernel for booting
- root is now cd0a
- use the same scripts and conf files as the i386 install ISO.

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

Sync with src/distrib/i386/cdroms/installcd/boot.cfg.in reg 1.4:
> Bump the timeout to 30s, it takes longer to read and digest the information
> esp. if you have not seen it before.

branches: 1.1.4; 1.1.6;
Also add boot.cfg into the installation CD, as was intended by ad@.

Remove modules set from the i386 install cd

It is not particularly useful to be able to load modules while
installing on i386, probably the most useful one is dtrace,
and this takes up about 20mb on a port that is already exceeding
CD limits. Most stuff you'd want to use while installing is already
in GENERIC.

The modules set is still available compressed for installing into
a target system, meaning modules are available after installation.

While here, add man set to the installation DVD, it's helpful to be able
to read e.g. the man page for fdisk when rescuing a system.

Add "DVD" ISOs for x86 that don't have to follow CD size limitations.

These include all available sets.

Add "DVD" ISOs for x86 that don't have to follow CD size limitations.

These include all available sets.

Restore Makefile.installimage include after variables are set. Makes amd64
USB install images bootable again.

fix building amd64 with USE_XZ_SETS=no.

bump the size of images if USE_XZ_SETS != no. consolidate a lot of
the code between installimage/Makefile and installimage-bios/Makefile
into installimage/installimage.mk.

There is no point in putting a second sysinst binary into the install
image's root filesystem.

Still not big enough - bump some more.

With recent changees to debug kernel stuff from Christos we are
once again pushing the size limit. Bump it again.

Once again things have grown, so the install image allocation size
needs to be bumped.

XXX There's gotta be a better way to maintain this! :-)

The install image grew again - update size

branches: 1.16.4;
The image, with all sorts of MK*DEBUG* turned on, has once again grown.
This time probably as a result of the move to gcc-10.

Bump size to accomodate.

The install-image has grown a bit recently, and at least amd64 has
outgrown the previous size specification when the system was built
with all of MKDEBUG, MKKDEBUG, and MKDEBUGLIB set to "yes" (and
also when in-tree X11 is included).

So, bump the size a bit.

Oooppss we need another size bump

Install image built with all of MKDEBUG, MKKDEBUG, and MKDEBUGLIB all
set to "yes" is a bit larger, so bump the image size accordingly.

Only install gptmbr.bin if USE_GPTMBR=yes

rename amd64 uefi-installimage to be just installimage.

Works for both purposes, no confusing name.

branches: 1.10.2;
Use the special device name "ROOT." in /etc/fstab not just on the arm
images, but also on the bootable disk images of other ports, so that
they can be booted from differently named devices. Merge the i386 and
amd64 -live-sd0root and -live-wd0root images into a single live image
per port, bootable both from usb media and in qemu. Drop the -xx0root
suffixes from image names as they are no longer meaningful.

branches: 1.9.2; 1.9.4;
Bump install image sizes. Clang alone adds 100MB+ for a full debug build
and that pushes the full MKDEBUG build over the constraints.

Bump a little to handle clang images.

Try to make images big enough for debug sets

branches: 1.6.6;
Grow!

Punt custom dhcpcd hooks in favour up upstream hooks

branches: 1.4.2;
Adjust for sysinst move.

branches: 1.3.8;
Allow overriding live-image and install-image sizes by
INSTIMAGEMB (for install-images), USBIMAGEMB (for x86 sd0root liveimages),
and EMUIMAGEMB (for other liveimages) variables.
Per discussion on current-users@:
http://mail-index.NetBSD.org/current-users/2012/10/29/msg021368.html

branches: 1.2.2;
Change the naming scheme of "live" images and usb install images
to incorporate the OS name and version.

XXX should also not hardcode ${BOOTDISK} in the name, but that would
require reordering stuff and more testing than I have time for right now.
Another day.

As discussed on current-users@ back in March, with some adjustments.

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

Express more confidence in our ability to boot on hardware with ACPI
enabled and don't warn our users that it might not and already suggest
workarounds.

The ability to disable ACPI and SMP is still there, by dropping to
the boot prompt.

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

kernfs no longer needs a hacky workaround to make rootdev appear.

branches: 1.1.4; 1.1.44;
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.1.4;
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.

Enable basic command line editing in amd64 installer shells

When a user selects "exist installer" or hits ^Z in sysinst, the
calling install.sh runs a shell, plus shows a message indicating
they can type "exit" to return to the installer.

Add -E to the arguments to this shell, to enable command line editing,
(primarily for arrow keys, but basic emacs sequences will also work)

At this point this is only on amd64, as this is the port which is
least likely to be installing on particularly esoteric terminal
hardware, and is also likely to have the highest proportion of less
experienced users

branches: 1.3.2;
There is no point in putting a second sysinst binary into the install
image's root filesystem.

Switch device database to cdb(5). Rework ttyname(3) and ttyname_r(3) to
depend on new devname_r(3) as heart. Add /dev/pts magic directly to
devname(3). While it can lead to returning non-existing paths, the
behavior is more consistent that way. Drop caching layer in devname(3),
it doesn't buy anything for the common case of having access to the
database. Teach devname(3) proper fallback behavior of scanning /dev.
Create both old-style and new-style database for now in /etc/rc.d/sysdb.

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

Use FFSv2 for amd64 live-image and install-image via new $IMGFFSVERSION.

Fixes PR/59007.

branches: 1.4.2;
amd64 installimage: Reduce non-xz size slightly to fit 4GB flash drives

The installimage sizes were bumped in 2022 because of some growth, and
the case for not-xz sets went to 4000 (MiB). That's just over what a
lot of "4 GB" flash drives are, but seems obviously intended to fit.
The actual usage of the filesystem, from a current build from earlier
this year (with non-xz sets) is:

/dev/dk1 3.7G 833M 2.7G 23% /mnt

and similar for netbsd-10 built yesterday, so we can afford to shrink
slightly. Drop to 3800, which is still huge, but will make 4 GB flash
drives work.

The new drm modules made the image file grow again! Bump the size
limit a bit.

XXX Other $ARCH might also need this.

Restore Makefile.installimage include after variables are set. Makes amd64
USB install images bootable again.

fix building amd64 with USE_XZ_SETS=no.

bump the size of images if USE_XZ_SETS != no. consolidate a lot of
the code between installimage/Makefile and installimage-bios/Makefile
into installimage/installimage.mk.

There is no point in putting a second sysinst binary into the install
image's root filesystem.

Punt custom dhcpcd hooks in favour up upstream hooks

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

Restore Makefile.installimage include after variables are set. Makes amd64
USB install images bootable again.

fix building amd64 with USE_XZ_SETS=no.

bump the size of images if USE_XZ_SETS != no. consolidate a lot of
the code between installimage/Makefile and installimage-bios/Makefile
into installimage/installimage.mk.

There is no point in putting a second sysinst binary into the install
image's root filesystem.

Still not big enough - bump some more.

With recent changees to debug kernel stuff from Christos we are
once again pushing the size limit. Bump it again.

Once again things have grown, so the install image allocation size
needs to be bumped.

XXX There's gotta be a better way to maintain this! :-)

branches: 1.1.2;
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)

branches: 1.1.2;
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)

branches: 1.1.2;
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)

branches: 1.1.2;
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)

Enable basic command line editing in amd64 installer shells

When a user selects "exist installer" or hits ^Z in sysinst, the
calling install.sh runs a shell, plus shows a message indicating
they can type "exit" to return to the installer.

Add -E to the arguments to this shell, to enable command line editing,
(primarily for arrow keys, but basic emacs sequences will also work)

At this point this is only on amd64, as this is the port which is
least likely to be installing on particularly esoteric terminal
hardware, and is also likely to have the highest proportion of less
experienced users

branches: 1.2.2;
There is no point in putting a second sysinst binary into the install
image's root filesystem.

branches: 1.1.2;
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)

There is no point in putting a second sysinst binary into the install
image's root filesystem.

branches: 1.1.2;
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)

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.3.4; 1.3.8;
Build amd64 xen kernels, and include them in the distrib.

branches: 1.2.4;
For the benefit of modern hardware, enable ACPI by default in INSTALL and
GENERIC kernels. If ACPI is an issue on your hardware, 'boot -c' and
'disable acpi' should be a workaround. ACPI-enabled kernels works fine
on pre-acpi hardware.
for amd64:
- add ACPI to INSTALL and GENERIC, remove the *_ACPI config files.
- get rid of the bootfloppy-big.fs boot image, and got to a 3-floppy boot
image
for i386:
- introduce INSTALL_LARGE which has ACPI and some devices with big firmware
- move some devices from INSTALL to INSTALL_LARGE
- Boot floppies still use INSTALL, and bootfloppy-big.fs is still there
(for thoses who want to build el-torito floppy emulation boot CD) and use
INSTALL.
For both, drop the 'iso-image' code in etc/ to make the iso bootable, we'll
use something else to build bootable CDs.

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

Add distrib/common/Makefile.minirootkmod. Apart from comments and the
conversion of some constants to variables, this is identical to the code
that was previously present in both distrib/amd64/kmod/Makefile and
distrib/i386/kmod/Makefile.

Change distrib/amd64/kmod/Makefile and distrib/i386/kmod/Makefile to just
set some variables and .include "../../common/Makefile.minirootkmod".

branches: 1.2.2;
Use a new variable, MODULEVER, for kernel modules, tracking what's been
done elsewhere.

branches: 1.1.6; 1.1.8;
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.1.6; 1.1.10;
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

Use the special device name "ROOT." in /etc/fstab not just on the arm
images, but also on the bootable disk images of other ports, so that
they can be booted from differently named devices. Merge the i386 and
amd64 -live-sd0root and -live-wd0root images into a single live image
per port, bootable both from usb media and in qemu. Drop the -xx0root
suffixes from image names as they are no longer meaningful.

branches: 1.1.4; 1.1.42; 1.1.44;
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.

Use FFSv2 for amd64 live-image and install-image via new $IMGFFSVERSION.

Fixes PR/59007.

branches: 1.3.2;
amd64 live image: support EFI as well as BIOS boot

The biggest caveat is that there's a small number of machines that try to
EFI boot but fail, so would prefer a BIOS only image. I'm not adding a
separate BIOS only image because the live image is pretty niche.
(For regular installation images, we do create a separate BIOS-only version)

Use the special device name "ROOT." in /etc/fstab not just on the arm
images, but also on the bootable disk images of other ports, so that
they can be booted from differently named devices. Merge the i386 and
amd64 -live-sd0root and -live-wd0root images into a single live image
per port, bootable both from usb media and in qemu. Drop the -xx0root
suffixes from image names as they are no longer meaningful.

branches: 1.1.4; 1.1.42; 1.1.44;
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.

restore amd64 live image support for resize root after combined mbr/gpt commit

we need to resize_gpt now, as it takes precedence over mbr/disklabel
this change brings us to behave like the evbarm images.

XXX: we don't seem to touch disklabel and MBR, but they exist. Not sure whether
that has any negative repercussions, maybe another system might regard MBR as the
sole source of truth when GPT also exists.

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Add support for EC2 and resize root to AMD64 live images.

Live images built with MKDEBUG=yes fit in 2 GB since installing _pic.a
libraries was disabled in src/share/mk/bsd.own.mk 1.1150.

The amd64 live image no longer fits in 2 GB when built with with
MKDEBUG, as releases are. Bump the size to just under 4 GB (as in
4*10^9, not 4*2^30), the next larger common USB thumb drive size.

Fix previous: set EMUIMAGEMB, not USBIMAGEMB.

Use the special device name "ROOT." in /etc/fstab not just on the arm
images, but also on the bootable disk images of other ports, so that
they can be booted from differently named devices. Merge the i386 and
amd64 -live-sd0root and -live-wd0root images into a single live image
per port, bootable both from usb media and in qemu. Drop the -xx0root
suffixes from image names as they are no longer meaningful.

branches: 1.3.30; 1.3.32;
Allow overriding live-image and install-image sizes by
INSTIMAGEMB (for install-images), USBIMAGEMB (for x86 sd0root liveimages),
and EMUIMAGEMB (for other liveimages) variables.
Per discussion on current-users@:
http://mail-index.NetBSD.org/current-users/2012/10/29/msg021368.html

branches: 1.2.2;
Change the naming scheme of "live" images and usb install images
to incorporate the OS name and version.

XXX should also not hardcode ${BOOTDISK} in the name, but that would
require reordering stuff and more testing than I have time for right now.
Another day.

As discussed on current-users@ back in March, with some adjustments.

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

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Add support for EC2 and resize root to AMD64 live images.

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Don't override /etc/rc.conf if it sets ec2_init.

Recognize OpenStack too (it also has a metadata service).

Typical values for machdep.dmi are:

machdep.dmi.system-vendor = OpenStack Foundation
machdep.dmi.system-product = OpenStack Nova
machdep.dmi.system-version = 17.0.12
machdep.dmi.system-serial = c46130fb-a56e-43f2-9d98-492d24656b9c
machdep.dmi.system-uuid = 680b8119-0d74-4f78-a6fd-e79dfede905c
machdep.dmi.bios-vendor = SeaBIOS
machdep.dmi.bios-version = 1.10.2-1ubuntu1
machdep.dmi.bios-date = 20140401
machdep.dmi.chassis-vendor = QEMU
machdep.dmi.chassis-type = QEMU
machdep.dmi.chassis-version = pc-i440fx-2.8
machdep.dmi.processor-vendor = QEMU
machdep.dmi.processor-version = pc-i440fx-2.8
machdep.dmi.processor-frequency = 2000 MHz

Look for the string "amazon" in a few different sysctl nodes. There doesn't
seem to be a single spot to check that works with both XenPVHVM and KVM
instances.

Add support for EC2 and resize root to AMD64 live images.

restore amd64 live image support for resize root after combined mbr/gpt commit

we need to resize_gpt now, as it takes precedence over mbr/disklabel
this change brings us to behave like the evbarm images.

XXX: we don't seem to touch disklabel and MBR, but they exist. Not sure whether
that has any negative repercussions, maybe another system might regard MBR as the
sole source of truth when GPT also exists.

/etc/rc.d/cerctl_init: New script for certctl rehash in live images.

This is very limited -- it does not supplant postinstall to rehash
certificates on upgrade; it only runs certctl rehash if
/etc/openssl/certs is an empty directory, as you get in live images
not created with sysinst.

We could also have a more general-purpose way to run postinstall(8)
on first boot of an image, but that has a lot more moving parts to
think about, so let's start with this limited-scope low-risk
approach.

PR install/57629

XXX pullup-10

branches: 1.2.2;
Check for right sysctl node to make live image work OOTB on OpenStack:

machdep.dmi.system-product = OpenStack Compute

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Add support for EC2 and resize root to AMD64 live images.

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Add support for EC2 and resize root to AMD64 live images.

restore amd64 live image support for resize root after combined mbr/gpt commit

we need to resize_gpt now, as it takes precedence over mbr/disklabel
this change brings us to behave like the evbarm images.

XXX: we don't seem to touch disklabel and MBR, but they exist. Not sure whether
that has any negative repercussions, maybe another system might regard MBR as the
sole source of truth when GPT also exists.

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Add support for EC2 and resize root to AMD64 live images.

amd64: liveimage: use RC_CONF_EXTRA instead of rc.conf.d

Add support for EC2 and resize root to AMD64 live images.

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