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@

Change variables 'MRFSDISKTYPE' to 'MRDISKTYPE' like every other arch.

No functional change.

Noticed by & ok kn@

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use the '-b' to create boot partitions instead of '-e' scripts.

Media creation & subsequent installation tests by visa@

ok visa@

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

Correct the library path for native build of ramdisks.

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@

Change variables 'MRFSDISKTYPE' to 'MRDISKTYPE' like every other arch.

No functional change.

Noticed by & ok kn@

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use the '-b' to create boot partitions instead of '-e' scripts.

Media creation & subsequent installation tests by visa@

ok visa@

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

Correct the library path for native build of ramdisks.

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use the '-b' to create boot partitions instead of '-e' scripts.

Media creation & subsequent installation tests by visa@

ok visa@

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

Correct the library path for native build of ramdisks.

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@

Use the '-b' to create boot partitions instead of '-e' scripts.

Media creation & subsequent installation tests by visa@

ok visa@

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

Correct the library path for native build of ramdisks.

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@

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

Correct the library path for native build of ramdisks.

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@

Correct the library path for native build of ramdisks.

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@

Adjust ramdisk generation for self hosting, remove cross bits.

Riscv64 distrib pieces to buld ramdisk
Copied from arm64 with minimal changes.
ok deraadt@