For amd64 cdXX.iso and installXX.iso, create an EFI system partition image
containing the EFI boot loaders and install it as an El Torito boot image,
making the install CDs bootable in EFI mode.

"looks great" deraadt@
ok mlarkin@

Retire -E's "expert" mode. Introduced 23 years ago to avoid
confusing users with FFS attributes that only experts should
fiddle with. Actual use has withered away with functionality
rendered moot or moved elsewhere.

'-e' remains for the truly obscure corner cases.

Simply excise the code for now to see if hidden users/uses are
exposed. Further simplifications are possible if no such
users/uses surface.

ok with sthen@ millert@ kn@ otto@

Replace the only two uses of disklabel template files with 'echo "/ *"'.

No functional change.

ok kn@

Remove unused make variables FSTYPE (=install360) and FSDISKTYPE
(=mini34). Preparatory to removing some obsolete/unused disktab
entries.

grow diskspace

Use long filenames by default on FAT filesystems

These days, 8.3 filenames are often a problem, filesystems containing
firmware with long names must not truncate them -- it's also a sane default
as portable file system between OSes, anyway.

Altough undocumented in mount_msdos(8), the default for FAT32 already is to
use long filenames: ever since its import from NetBSD in 1998.

Previously, mount_msdos would ignore long filenames and default to short
filenames unless a flag was used or long ones were found on the filesystem
prior to mounting it.

Just always mount with support for long filenames (unless `-s' is used).


As various install media use FAT filesystems, adjust the remaining ones to
also pass explicit mount option reflecting the previous default.

OK deraadt

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Retire -E's "expert" mode. Introduced 23 years ago to avoid
confusing users with FFS attributes that only experts should
fiddle with. Actual use has withered away with functionality
rendered moot or moved elsewhere.

'-e' remains for the truly obscure corner cases.

Simply excise the code for now to see if hidden users/uses are
exposed. Further simplifications are possible if no such
users/uses surface.

ok with sthen@ millert@ kn@ otto@

Replace the only two uses of disklabel template files with 'echo "/ *"'.

No functional change.

ok kn@

Remove unused make variables FSTYPE (=install360) and FSDISKTYPE
(=mini34). Preparatory to removing some obsolete/unused disktab
entries.

grow diskspace

Use long filenames by default on FAT filesystems

These days, 8.3 filenames are often a problem, filesystems containing
firmware with long names must not truncate them -- it's also a sane default
as portable file system between OSes, anyway.

Altough undocumented in mount_msdos(8), the default for FAT32 already is to
use long filenames: ever since its import from NetBSD in 1998.

Previously, mount_msdos would ignore long filenames and default to short
filenames unless a flag was used or long ones were found on the filesystem
prior to mounting it.

Just always mount with support for long filenames (unless `-s' is used).


As various install media use FAT filesystems, adjust the remaining ones to
also pass explicit mount option reflecting the previous default.

OK deraadt

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Replace the only two uses of disklabel template files with 'echo "/ *"'.

No functional change.

ok kn@

Remove unused make variables FSTYPE (=install360) and FSDISKTYPE
(=mini34). Preparatory to removing some obsolete/unused disktab
entries.

grow diskspace

Use long filenames by default on FAT filesystems

These days, 8.3 filenames are often a problem, filesystems containing
firmware with long names must not truncate them -- it's also a sane default
as portable file system between OSes, anyway.

Altough undocumented in mount_msdos(8), the default for FAT32 already is to
use long filenames: ever since its import from NetBSD in 1998.

Previously, mount_msdos would ignore long filenames and default to short
filenames unless a flag was used or long ones were found on the filesystem
prior to mounting it.

Just always mount with support for long filenames (unless `-s' is used).


As various install media use FAT filesystems, adjust the remaining ones to
also pass explicit mount option reflecting the previous default.

OK deraadt

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Remove unused make variables FSTYPE (=install360) and FSDISKTYPE
(=mini34). Preparatory to removing some obsolete/unused disktab
entries.

grow diskspace

Use long filenames by default on FAT filesystems

These days, 8.3 filenames are often a problem, filesystems containing
firmware with long names must not truncate them -- it's also a sane default
as portable file system between OSes, anyway.

Altough undocumented in mount_msdos(8), the default for FAT32 already is to
use long filenames: ever since its import from NetBSD in 1998.

Previously, mount_msdos would ignore long filenames and default to short
filenames unless a flag was used or long ones were found on the filesystem
prior to mounting it.

Just always mount with support for long filenames (unless `-s' is used).


As various install media use FAT filesystems, adjust the remaining ones to
also pass explicit mount option reflecting the previous default.

OK deraadt

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

grow diskspace

Use long filenames by default on FAT filesystems

These days, 8.3 filenames are often a problem, filesystems containing
firmware with long names must not truncate them -- it's also a sane default
as portable file system between OSes, anyway.

Altough undocumented in mount_msdos(8), the default for FAT32 already is to
use long filenames: ever since its import from NetBSD in 1998.

Previously, mount_msdos would ignore long filenames and default to short
filenames unless a flag was used or long ones were found on the filesystem
prior to mounting it.

Just always mount with support for long filenames (unless `-s' is used).


As various install media use FAT filesystems, adjust the remaining ones to
also pass explicit mount option reflecting the previous default.

OK deraadt

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Use long filenames by default on FAT filesystems

These days, 8.3 filenames are often a problem, filesystems containing
firmware with long names must not truncate them -- it's also a sane default
as portable file system between OSes, anyway.

Altough undocumented in mount_msdos(8), the default for FAT32 already is to
use long filenames: ever since its import from NetBSD in 1998.

Previously, mount_msdos would ignore long filenames and default to short
filenames unless a flag was used or long ones were found on the filesystem
prior to mounting it.

Just always mount with support for long filenames (unless `-s' is used).


As various install media use FAT filesystems, adjust the remaining ones to
also pass explicit mount option reflecting the previous default.

OK deraadt

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Make "config -e" work with ramdisk kernels

amd64, alpha, i386 and macppc strip *all* symbols off the ramdisk bsd.rd
(before compressing it) and thus break config(8)'s modification feature:

$ gzcat bsd.rd > bsd.rd.raw
$ config -e bsd.rd.raw
...
config: failed to get first cfdata

This is different from "boot> boot /bsd.rd -c" which sucessfully drops into
UKC on all platforms regardless of stripping.

Having needed "config -e" this on arm64 made me look into this for all
platforms. Other platforms work because they don't strip these symbols.

Tweak objcopy(1)'s stripping on amd64 and macppc to unbreak permanent
modifications. I have no alpha or i386 to test, so these remain broken.

macppc works without cranking media size.
amd64 was cranked to the smallest possible size.

OK deraadt

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

increase ramdisk space for another driver

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Pass make flags to kernel and lib builds

Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.

Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.

Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'
does *not* pass `-C.' to change directories.
(can be easily tested with `make -p ... | grep MFLAGS'.)

This makes hacking on ramdisks/the installer much faster, espescially since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.

OK deraadt

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

distrib: restore rdsetroot -x usage (extract the disk.fs image) on stripped bsd.rd

It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.

ok danj@ deraadt@

distrib: use ${MACHINE} instead of hardcoded value

ok deraadt@

distrib: remove .comment section systematically

remove this section as part of crunchgen generated commands.
it avoids calling "strip -R .comment" for some but not all architectures.

ok deraadt@ danj@

distrib: remove .SUNW_ctf only on kernels

the .SUNW_ctf section is added by ctfstrip(1), which is only used for kernels.

ok deraadt@ danj@

distrib: merge "cp a b; strip b" to "objcopy -S a b"

ok deraadt@ danj@

distrib: remove duplicate strip(1) calls

"strip -R section" command run "strip" (without option) as well.
there is no need to call both.

(binaries checked with sha1)

original diff from danj@

ok deraadt@

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

distribute the gzip'd version of bsd.rd on platforms where we all boot
methods support it. if anyone finds a method which does not work, please
speak up.

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

grow amd64 ramdisk_cd.......

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@

Install cert.pem + ftp(1) binary that supports SSL, so the install script
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe

Inline IMAGE, CBIN, CRUNCHCONF and XNAME.
ok deraadt

Unshare Makefile.inc so we can determine how to squeeze makefs
into the picture.
ok natano

Use the new fdisk -b functionality to put an EFI system partition on the
minirootXX.fs image and put the new UEFI bootloader on there.

Stop relying on /etc/disktab for the partition layout. Instead use a suitable
template and let disklabel(8) allocate all remaining free space to the 'a'
partition.

ok deraadt@

zap trailing newlines; "go for it" deraadt

create small i386 and amd64 miniroots. These can be dd'd to a usb stick
or such, and easily booted.
Work by chris, integration mechanism by me

Place a smaller spwd.db onto the install media. Be consistant with the naming
of the "additional" list files (for architectures which split the list)
Then... cleanup some TZ which it is clear should not have been placed onto
certain media which don't have the space for them.

double size of amd64 boot media
tested by krw

do not install the cdromXX.fs file, it is useless

Make FLOPPYSIZE be in terms of 512 byte blocks like all the other ports.
This was something I missed in the initial "newfs -c" conversion.

first cut; most written by mickey, couple tunings by me

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

eliminate differences between all the list files as much as
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

verbose mkhybrid was never needed on these arch

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

pull cdfs into ramdisk_cd

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

Increase size to make slaacd fit.
Size problem noted by me, correct fix from deraadt@