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 "echo 'w\ny\nq\n' | disklabel -E" with equivalent
'disklabel -dw'.

Tested & ok visa@

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

Build, boot and install tested by visa@

ok visa@

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

Arithmetic is hard! Since MBR partition 0 is the only partition in the boot
media MBR, just use '*' to take all the available space.

ok visa@ 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

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

Replace "echo 'w\ny\nq\n' | disklabel -E" with equivalent
'disklabel -dw'.

Tested & ok visa@

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

Build, boot and install tested by visa@

ok visa@

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

Arithmetic is hard! Since MBR partition 0 is the only partition in the boot
media MBR, just use '*' to take all the available space.

ok visa@ 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

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

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

Build, boot and install tested by visa@

ok visa@

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

Arithmetic is hard! Since MBR partition 0 is the only partition in the boot
media MBR, just use '*' to take all the available space.

ok visa@ 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

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

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

Arithmetic is hard! Since MBR partition 0 is the only partition in the boot
media MBR, just use '*' to take all the available space.

ok visa@ 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

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

Arithmetic is hard! Since MBR partition 0 is the only partition in the boot
media MBR, just use '*' to take all the available space.

ok visa@ 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

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

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

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

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

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

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)

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

Fix miniroot partition.

OK deraadt@

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

step by step, more removal of differences

repair more trivial differences

rm is in /bin, no need to specify

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

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

TOPDIR and TOP are not neccessary.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

CBIN variable is also pointless, it is always "instbin". Rather than
having two mysterious names, let's settle on one.

the BSD_RD variable is pointless

Use new rdsetroot.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.

Use makefs to build bsd.rd; tested by visa

Use new kernel compile method for ramdisks, de-escalating to $BUILDUSER
as required.
much help from natano and tb.

We do not produce "core" files, so they do not need to be deleted. they
have been *.core files for a very long time. That's a lot of unlink()
calls saved.

Turn on the distrib lib bits in crunchgen by setting SRCLIBDIR.
Add the new files to the clean target's rm list.

"why not get it tested?" deraadt@

add ramdisk installer for octeon, still has some rough edges and needs some
manual fiddling, but works good enough to perform an install on the CAM-0100.