| #
3e58d19e |
| 09-Dec-2020 |
krw <krw@openbsd.org> |
Use daddr_t and not daddr32_t in boot media.
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,
Use daddr_t and not daddr32_t in boot media.
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@
show more ...
|
| #
6a5f8025 |
| 24-Mar-2013 |
deraadt <deraadt@openbsd.org> |
Use sys/param.h to be able to get at DEV_BSIZE
|
| #
214337f8 |
| 13-Mar-2011 |
deraadt <deraadt@openbsd.org> |
Change daddr_t to daddr32_t. The bootblocks on our architectures only
do 32-bit block spanning. If later on we get some that can/should do
64-bit, that can be done now using daddr64_t (but of cours
Change daddr_t to daddr32_t. The bootblocks on our architectures only
do 32-bit block spanning. If later on we get some that can/should do
64-bit, that can be done now using daddr64_t (but of course, we are taking
this step to finalize the daddr_t 64-bit conversion).
ok miod krw
show more ...
|
| #
3c1af18d |
| 03-Apr-2010 |
miod <miod@openbsd.org> |
Minor reliability fixes:
- clear initrd signature before returning to PMON or to the loaded kernel
- fail /etc/boot.conf access when loading from an initrd image, instead of
letting it point to the
Minor reliability fixes:
- clear initrd signature before returning to PMON or to the loaded kernel
- fail /etc/boot.conf access when loading from an initrd image, instead of
letting it point to the beginning of the kernel image and have the code
complain of lines being too long.
Bump minor version.
show more ...
|
| #
ea5da297 |
| 17-Feb-2010 |
miod <miod@openbsd.org> |
If PMON has loaded an initrd binary, and this binary looks like a valid
ELF image, assume it's the kernel and try to boot it immediately.
This allows a Gdium system with both the bootloader and the
If PMON has loaded an initrd binary, and this binary looks like a valid
ELF image, assume it's the kernel and try to boot it immediately.
This allows a Gdium system with both the bootloader and the kernel image on
an ext2fs partition, with `al' pointing to the bootblocks and `rd' pointing
to the kernel in PMON environment, to boot a kernel with proper kernel
symbols, for the first time.
(please don't get me started on how reliable `load -k' is on the Gdium)
Bump bootblocks version to 0.2.
show more ...
|