| Age | Commit message (Collapse) | Author |
|---|
|
pointed out by kn, tested in snaps for a week
|
|
more distributed way of doing something smart and failovery, but this
annotation in the script isn't helping.
|
|
groups, and then kill the process group instead of the ksh pid. Some
of these processes contain sleep, which kept running, and in some
cases retained stderr (or other fd) and confused parent processes.
In some cases, add manual wait. Finally, store the pid (nee pgrp)
in /tmp/xxpid files rather than variables, since there is a bit
of recursion and sub-shell confusion happening, and we have confused
ourselves at least twice with these pid variables not being in scope.
ok beck, with florian, ok kn
In snaps for almost a week. A few more tweaks may come in a while.
|
|
write ourselves. This is a sad fact. libz just did this to us, again.
I don't care to hunt for reasons or justifications because it is an
endless battle.
Therefore this tiny (floppy) media can no longer include the TZ files.
Because some other architectures also have tight media, we have an
install script mechanism to cope with this -- when they are missing, it
asks the timezone question later, after the base set is installed with
the files)
|
|
|
|
|
|
|
|
|
|
We only had one watchdog running that triggered after 30 minutes. If
an unattended upgrade (e.g. started by sysupgrade(8)) took longer than
this in total, the machine would reboot half way through an upgrade.
The intention was that the watchdog would be reset after each set
download and after each set installation. But this never worked
correctly because the actual upgrade ran in a sub-shell and WDPID was
not visible.
To fix this we first need to export WDPID to make it visible in the
sub-shell. Then reset_watchdog was guarded by $UU && reset_watchdog,
but UU wasn't visible either. But we can't export it because we would
enter a loop. We can just use the fact that WDPID is not empty to
restart the watchdog.
Lastly the watchdog process would keep stderr and stdout open. This
made the tee(1) hang that is collecting the autoupgrade log that is
mailed to root.
As a simplification, we don't need to run the watchdog as a
co-process, we don't want to communicate with it, we can just run it
in the background.
Problem reported by stsp
With & OK deraadt
OK millert
|
|
blanks in the arrays of type names, simplifying the code and
making better use of printf().
Along the way discover that "APFS Recovery" fits, so nuke the
annoying "AFPS Recovry" contraction.
No intentional functional change.
Some "APFS Recovery" nits pointed out by jsg@
|
|
|
|
|
|
the remaining directory list is good enough
ok sthen
|
|
|
|
|
|
ok jsg@
|
|
OpenBSD.
|
|
|
|
because of the the tar+mv combination. Purge both path variations
better, so that an interrupted install can be restarted.
ok miod abieber kettenis
|
|
running Xorg in a way that isn't fully understood. So change the arm64
install.md to munge /etc/ttys to enable the ttyC0 entry if we detect that
wsdisplay0 is the console and make sure the code in install.sub that
does the actual munging disables the console entry before enabling another
entry to prevent running two getty(8) processes on (effectively) the same
device.
ok deraadt@
|
|
|
|
New verbiage suggested by deraadt@.
|
|
|
|
This mostly adds some checks to make sure that if for some reason the firmware
files aren't present on the EFI System Partition the users doesn't see
several error messages.
ok deraadt@
|
|
|
|
|
|
apple specific install instructions still needed
|
|
|
|
|
|
formatting the partition such that its contents actually survive.
ok krw@
|
|
also uses these names. This implements a complete interface for
atomic operations, such functions can be used for every access.
They provide compiler barriers, but no CPU memory barriers. This
is consistent with our other atomic operations.
OK mvs@ visa@
|
|
|
|
|
|
Improved chicken scratches from tb@
|
|
devices and copy it into the right directory on the ramdisk such that it
can be used in the installer. And copy it in place at the end of the
install procedure such that it is available for use in the newly installed
system.
ok deraadt@
|
|
ok afresh1@ kevlo@, who both ran into the same issue
|
|
|
|
|
|
|
|
|
|
|
|
OK kettenis@ deraadt@
|
|
|
|
|
|
ok jca@
|
|
rather than relying on /usr/mdec/mbr.
Tested by tobhe@
|
|
|
|
Build, boot and install tested by bluhm@
ok bluhm@
|
|
|
|
Build, boot and install tested by bluhm@
ok bluhm@
|
