Avoid forcible mounting a dirty filessystem. Mount such filesystems
read-only instead. This means that writing to the filesystem will fail.
As a consequence chmod'ing of files in the bootloader wil

Avoid forcible mounting a dirty filessystem. Mount such filesystems
read-only instead. This means that writing to the filesystem will fail.
As a consequence chmod'ing of files in the bootloader will fail, but that
will fix itself on the next clean boot.

Same change as I committed to powerpc64 a few days ago.

ok kn@, deraadt@

show more ...

Check outcome of loadrandom() on octeon

If loadrandom() succeeds, set RB_GOODRANDOM in boothowto.

To enable fchmod(), disk_open() has to mount the filesystem in writable
mode. This is tricky becaus

Check outcome of loadrandom() on octeon

If loadrandom() succeeds, set RB_GOODRANDOM in boothowto.

To enable fchmod(), disk_open() has to mount the filesystem in writable
mode. This is tricky because the filesystem might be unclean. Hence the
code has to use MNT_FORCE.

Input and OK deraadt@

show more ...

Add a bootloader for octeon.

The firmware on OCTEON machines usually does not provide an interface
for accessing devices, which has made it tricky to implement an OpenBSD
bootloader. To solve this d

Add a bootloader for octeon.

The firmware on OCTEON machines usually does not provide an interface
for accessing devices, which has made it tricky to implement an OpenBSD
bootloader. To solve this device access problem, this new loader has
been built on top of a small kernel. The kernel provides all the
necessary devices drivers, while most of the usual bootloader logic
is in a userspace program in a ramdisk.

The loader program is accompanied by a special device, octboot(4).
The main purpose of this device is to implement a mechanism for
loading and launching kernels. The mechanism has been inspired by Linux'
kexec(2) system call.

The bootloader will be enabled later when it is ready for general use.

Discussed with deraadt@

show more ...