Age | Commit message (Collapse) | Author |
|
ok ajacoutot robert
|
|
* Remove syspatch files from the installed system and not the ramdisk.
* Directly try to remove the old files without superfluous check.
* Use an extended glob to match /usr/lib/gcc-lib contents that don't
belong to this OS version.
* For /usr/lib/clang, set an array to the expansion of the glob, which is
an alphabetically sorted list, drop the last element, and rm the rest.
ok tb@
|
|
Instead of having a single timeout for the entire upgrade, start anew right
before extracting each set's tarball.
Do so by replacing the background job with a proper co-process that gets
killed and restarted (reset), analogue to the dmesg listener in interactive
mode.
Prompted by and OK sthen
OK deraadt
|
|
|
|
|
|
OK sthen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on my anoncvs server it takes about 20m already to untar sets, which is
a bit close to the limit for my liking (we only want to trigger the
watchdog if things are *really* stuck; if it's still proceeding then
rebooting mid-upgrade can leave things in a worse state).
we can probably do something smarter (e.g. reset the watchdog after
untarring each set) but this is an easier-to-test initial improvement.
ok florian deraadt kn
|
|
|
|
|
|
|
|
approach was not right, and there is still room for improvement.
OK deraadt@
|
|
tweaked along the way by at least myself and tj;
ok tj deraadt
|
|
|
|
|
|
caused by recent Makefile changes.
Confirmed by me, "sure" deraadt@
|
|
|
|
|
|
to the boot partition.
To use the bootloader, the firmware has to be configured to load
file "boot" instead of "bsd".
OK deraadt@
|
|
OK deraadt@
|
|
the size of the "boot" file.
OK deraadt@
|
|
|
|
|
|
|
|
|
|
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@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
|
|
"can't hurt" deraadt@
|
|
|
|
more empty space before the MS-DOS and OpenBSD partitions.
Also make sure we don't overwrite the firmware with the Pine64 on anything
but the Pine64 and Pine64+.
With help from jsg@
ok deraadt@, jsg@, patrick@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..
|