Age | Commit message (Collapse) | Author |
|
|
|
The list of not yet tested archs is smaller, so follow bsd.regress.mk(5)
advise and just print SKIPPED on those.
|
|
|
|
|
|
|
|
Testing with three softraid chunks now means NDISKS=3 as one would expect
and not NDISKS='1 2 3'.
This uses the powerful jot(1) -w and rs(1) -T commands and allows for more
simplifications in the Makefile.
|
|
Treat keydisks like real chunks until installboot properly skips it and
does not touch/install to them anymore.
|
|
From Joshua Sing
|
|
Those that still fail (softraid+keydisk or explicit-stage-files) have fixes on tech@.
|
|
|
|
|
|
CID 356777
|
|
CID 356778
|
|
|
|
|
|
Still fails due to the disklabel/vnd kernel race but running into failing
'installboot -p' helps exercising the fsck/newfs exit code fix.
REGRESS_EXIT_EARLY=1 runs past the prepare target without the diff but
properly stops with it as installboot now exits 1 if system(3) fails.
|
|
From Joshua Sing
|
|
From Joshua Sing
|
|
|
|
|
|
Tiny bit less noise. The many REGRESS_SETUP_ONCE targets could be merged
into a single one and then be added to .SILENT unless VERBOSE=yes to focus
on actual installboot output and ditch the dd/fdisk/disklabel noise by default.
|
|
|
|
Keydisks requires special treatment and should not be touched by installboot.
In real setups they are probably offline (temporary USB stick, only present
during boot to unlock), but when they are around (keydisk chunk on same disk
as crypto volume)...
installboot currently installs treats keydisk like any other chunk, which
must be fixed.
Thus change the tests into a should-work-but-currently-broken setup so an
installboot fix can be immediately tested against it.
|
|
From Joshua Sing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Not all architectures did what the installer does with empty disks.
|
|
Running installboot(8) on softraid(4) volumes means installing stages on
every softraid chunk.
The overall idea is the same, but MD implementations differ.
sparc64_softraid.c's sr_install_bootblk() reuses sparc64_installboot.c's
md_installboot() for this.
For sparc64, md_installboot() does the copy of stage 2, usually
/usr/mdec/ofwboot to /ofwboot, so when `-r root' is passed, it prefixes the
file path with "root".
For single-disk installations (plain-disk and single-chunk softraid) this is
fine, but as soon as multiple chunks are used, md_installboot() currently
prefixes the path each time, obviously resulting in invalid paths starting
with the second run.
Other architectures do reuse md_installboot() as well but either don't do
such a copy or implement the prefixing differently -- plus they must support
softraid in the firt place to be able to hit this type of bug.
With this fixed, regress/usr.sbin/installboot finally passes on sparc64 and
installboot no longer fails at the end of a fresh installation onto softraid
with multiple chunks.
"looks correct" miod
|
|
Used to flag the newly added test_bind_unix_socket() as expected to
fail.
|
|
|
|
|
|
from mlarkin
|
|
|
|
From Joshua Sing
|
|
From Joshua Sing
|
|
|
|
|
|
|
|
These exercise MD4 and MD5 with the test vectors from RFCs 1320 and 1321.
From Joshua Sing <joshua () hypera ! dev>
|
|
|
|
|
|
for output, use 'err' as a label and avoid some silly repetitions.
|
|
The old tests were incomplete, some of them had no license and the code
quality was questionable. The new tests by Joshua Sing cover what they
did (and additionally SHA-224 and SHA-384). Many thanks!
|
|
|
|
From Joshua Sing
|
|
Adjust the test for now to -Cr4, which isn't exactly in the spirit of the
test but fixes things for now.
Now that we have agentx I should write a backend with more predictable
output to make regress more stable.
pointed out by anton@
|