summaryrefslogtreecommitdiff
path: root/distrib
AgeCommit message (Collapse)Author
2019-04-30fix disktype related typoTheo de Raadt
2019-04-30Every Makefile on every architecture had deviated in unique ways.Theo de Raadt
Eliminate many more differences. When it makes sense, build bsd.rd and miniroot/ramdisk.fs and cd.iso in the same directory. More steps coming after this..
2019-04-29Make v[46]_info() return all the interface flags instead of justKenneth R Westerback
deducing that the interface is up or down. Check for "UP," in the returned flags where a return value of UP was used previously. ok kn@ with feedback/optimizations to be pondered further.
2019-04-29$() is expanded by make itself, so consistently use `cat vnd`; ok deraadt@Christian Weisgerber
2019-04-29These Makefile.inc are now empty and unused.Theo de Raadt
2019-04-29TOPDIR and TOP are not neccessary.Theo de Raadt
2019-04-29remove the abstraction REV on top of abstraction OSrev which is alwaysTheo de Raadt
the sme.
2019-04-28reduce delta with ../ramdisk/listTheo de Raadt
2019-04-28oops, repair some BSDRD confusionTheo de Raadt
2019-04-28cleanup the situation around "df -i"Theo de Raadt
2019-04-28incorporate GZIPFLAGS into place everywhereTheo de Raadt
2019-04-28Oops; hardcode instbin directlyTheo de Raadt
2019-04-28Cull BSDRD variables which are always bsd.rdTheo de Raadt
2019-04-28NEWFS_WILL_FAIL is a ridiculous unused artifact.Theo de Raadt
2019-04-28CBIN variable is also pointless, it is always "instbin". Rather thanTheo de Raadt
having two mysterious names, let's settle on one.
2019-04-28the BSD_RD variable is pointlessTheo de Raadt
2019-04-28Use new vnconfig vnd-auto-allocate mode. Resolve some variation betweenTheo de Raadt
architectures, and start removing some crazy junk that has collected over the years. Being tested on all architectures... ok various people.
2019-04-27It's timer_pid not timeout_pidkn
There since introduction in 1.18 (2013). OK halex
2019-04-26syncTheo de Raadt
2019-04-25syncTheo de Raadt
2019-04-25Move the expected set location to /home/_sysupgrade.Florian Obser
We found that /home/upgrade is a too common name and this will be in line with the upcomming sysupgrade(8) utility. discussed with deraadt@
2019-04-25syncVisa Hankala
2019-04-25syncTheo de Raadt
2019-04-24In unattended mode do a reboot even if things go wrong andFlorian Obser
additionally install a watchdog to do a reboot after 30 minutes if the script gets completely stuck. A half upgraded system that reboots at least gives us a chance that it will come back and we can fix it. Just having it sit there isn't helping anyone. It would be nicer if the watchdog were kernel based... OK deraadt
2019-04-24Perform unattended upgrade if /bsd.upgrade is present.Florian Obser
Sets are expected to be in /home/upgrade. Original idea, input & OK deraadt
2019-04-24Tweak the initial sentence to mention OCTEON II and OCTEON III.Visa Hankala
2019-04-23syncTheo de Raadt
2019-04-23syncTheo de Raadt
2019-04-23syncVisa Hankala
2019-04-22When upgrading only prompt for disks that contain a root partition.Florian Obser
With this the question "Which disk is the root disk" has the correct default in case of full disk encryption. Before it would list sd0 sd1 with sd0 being the backing store and sd1 the unlocked disk. This is a step towards fully unattended upgrades running completely on defaults (i.e. no need for an autoinstall(8) answer file). In the past there have been concernes that we should not touch any odd disk without the operator telling us as there might be bugs lurking. It is early enough in the cycle to find out for sure. input halex, kn "just commit it" deraadt
2019-04-21syncTheo de Raadt
2019-04-15syncTheo de Raadt
2019-04-14Instead of using COPTS=-Oz (and similar) in make environment to forceTheo de Raadt
tightly-built ramdisk kernels, set the option in per-arch Makefile.inc based upon SMALL_KERNEL
2019-04-06syncTheo de Raadt
2019-04-05syncTheo de Raadt
2019-04-05Use new rdsetroot.Theo de Raadt
2019-04-05syncTheo Buehler
2019-04-04Sync.Joel Sing
2019-04-04syncTheo de Raadt
2019-04-03syncTheo de Raadt
2019-04-02syncTheo de Raadt
2019-04-02After upgrade time, delete contents of /var/syspatch. EitherTheo de Raadt
we are on a release (and the rollbacks are meaningless) or it's a snapshot (and they are even more meaningless) It appears the first syspatch of a release does that cleaning, but why not get ahead.. ok phessler
2019-04-02syncTheo de Raadt
2019-04-02After upgrade, cleanup old clang and gcc compoents.Theo de Raadt
Test by phessler
2019-04-01syncTheo de Raadt
2019-03-29syncStuart Henderson
2019-03-25syncTheo de Raadt
2019-03-21syncTheo de Raadt
2019-03-19syncTheo de Raadt
2019-03-18syncanton