| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
At a minimum, amd64/i386 should now boot from 4TB GPT formatted disks.
More daddr32_t terminations with extreme prejudice to follow.
Tested by various, in snaps for a few days.
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The kernel text will grow larger when retguard adds code to many
functions to check their return addresses. The entire kernel
(including text, data, bss, symbol table, and ramdisk) must fit under
the CLAIM_LIMIT. A kernel that overflows this limit may fail very
quickly, by causing a "DEFAULT CATCH!" error in Open Firmware.
Crank version to "1.10", so I can see whether the running ofwboot uses
the higher CLAIM_LIMIT.
ok deraadt@
|
| |
|
| |
|
| |
|
|
|
|
| |
ok deraadt@
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Document the new feature in boot(8) man page.
OK jmc@ deraadt@
|
|
|
|
|
|
| |
inspect the memory layout that the firmware has created. It is
especially useful for UEFI debugging.
OK deraadt@ kettenis@
|
|
|
|
|
|
|
|
|
| |
section, which has grown a fair bit with the introduction of retguard.
Mortimer discovered the repeated 512-byte sequence as retguard keys, and
this resolves the issue. (Chacha does not fit on the media, so 1.5K early
drop RC4 is hopefully sufficient in our KARL link universe)
Version crank the bootblocks. sysupgrade -s will install new bootblocks.
ok djm mortimer
|
|
|
|
| |
ok deraadt@
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so the file cannot be re-executed upon the next boot. This provides a
stronger one-shot-upgrade model than the upgrade script's rm /bsd.upgrade.
Now various forms of upgrade failure will reboot into /bsd, which is probably
more recoverable. Performing fchmod -x depends on (1) use of MI boot.c
(not alpha/macppc/sparc64/sgi/octeon) and (2) "can write blocks" functionality
in the IO layer. Most architectures have this support now.
Two diagnostics "fchmod a-x %s: failed" and "/bsd.upgrade is not u+x" will
remain in the tree while refinements happen for some of the laggard
architectures.
based upon a discussion florian
tested in snapshots for more than a week without any complaints
|
|
|
|
| |
memcpy() correct behaviour. This also brings the bcopy() macro into line.
|
|
|
|
|
| |
details from the ELF header instead of faking it.
Proposal from mlarkin, tested on most architectures already
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
defer their creation to later, so that they are owned by BUILDUSER.
This eliminates the last root-owned files in obj/ from 'make build'.
In addition, place a MACHINE == hppa test in hppa/stand/Makefile.inc
to avoid creating bogus symlinks on all other archs.
joint work with & ok natano, "let's try it" deraadt
|
|
|
|
|
| |
as discussed with jsing@ it's easier this way to ensure people have
bootblocks capable of loading the section
|
|
|
|
| |
ok millert@ kettenis@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
correctly - logically complete that now by removing MLINKS from base;
authors need only to ensure there is an entry in NAME for any function/
util being added. MLINKS will still work, and remain for perl to ease
upgrades;
ok nicm (curses) bcook (ssl)
ok schwarze, who provided a lot of feedback and assistance
ok tb natano jung
|
|
|
|
| |
ok beck@ deraadt@
|
| |
|
|
|
|
| |
ok millert@ jasper@
|
|
|
|
| |
headers by mistake.
|
|
|
|
|
|
|
| |
from tilo stritzky
thanks miod for help with the diff, and who also noted that
leading whitespace gets stripped too;
|
| |
|
|
|
|
|
| |
way by mpi@. Bump version.
ok mpi@
|
|
|
|
| |
of fs_ops; makes the `ls' command finally work in the boot loader.
|
| |
|
|
|
|
| |
referenced by the bootblocks.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
"sure" miod@
|
|
|
|
| |
ok miod@
|