summaryrefslogtreecommitdiffstats
path: root/usr.sbin/syspatch/syspatch.8 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* When asking to install patches and none are available, return 2.ajacoutot2020-12-071-2/+4
| | | | | man page and inputs from schwarze@ ok sthen@
* Add a EXIT STATUS sectionsolene2020-07-251-2/+4
| | | | "no objection" ajacoutot@
* "If any sets are missing, patches are skipped accordingly."ajacoutot2019-06-151-2/+3
| | | | wording help and ok jmc@
* Add support for KARL:ajacoutot2017-08-221-10/+6
| | | | | | | | | | | - only extract the according /usr/share/compile/GENERIC{,.MP} - if a "kernel" patch was properly installed (or rolled back), run /usr/libexec/reorder_kernel _once_ just before exiting - don't backup /bsd anymore, reorder_kernel already does it for us - drop 2 now unused functions: install_kernel() and sp_cleanup() While it appears to work fine after some quick testing, it should still be considered WIP.
* Document that patches are cumulative and as such it is not possible to installajacoutot2017-05-091-2/+4
| | | | | | only a subset of them. with input from jmc@
* Add a `-R' switch that reverts all patches.ajacoutot2017-05-051-3/+5
| | | | | | prodded by deraadt@ knobs sorting input jmc@ ok sthen@
* use .Em for emphasis, not .Paschwarze2017-04-081-3/+3
|
* Ox on its own line;jmc2017-02-071-2/+3
|
* Add installurl to FILES and SEE ALSO.ajacoutot2017-02-071-2/+5
|
* Make it possible to install patches even if we don't have all sets installedajacoutot2016-12-081-7/+10
| | | | | | (e.g. no x sets); in this case, syspatch will skip the patch *but* it will still be listed as available. This will allow applying the patch in case sets are installed later on.
* Change the hierarchy under /var/syspatch/ so that the output of installed orajacoutot2016-11-301-7/+7
| | | | | | | | | | | | | missing patches matches the official names. e.g. $ doas syspatch -c 015_libssl Add a bit more output on what we are doing. Tighten a few checks and rename some vars. People playing with syspatch on 6.0 should update syspatch.sh asap from current as I will soon remove the temporary quirks glue.
* Document the fact that *for now* syspatch only works on official releases andajacoutot2016-11-291-2/+6
| | | | will always sync and apply all patches regardless of the installed sets.
* /bsd.rollbackXX -> bsd.syspatchXX to make it more obvious where it comes fromajacoutot2016-11-161-3/+3
| | | | | and less prone to conflict. Simplify ls_installed while here.
* Small wording tweak and a couple of fixes from jmc@ajacoutot2016-11-151-5/+5
|
* Extend documentation a bit. It'll probably need some adjustments soon.ajacoutot2016-11-101-3/+21
|
* Simplify.ajacoutot2016-11-081-3/+3
|
* rollback -> revert where it makes sense.ajacoutot2016-11-031-4/+4
|
* apply_patches should not take any arguments.ajacoutot2016-09-101-3/+3
| | | | Few tweaks while here.
* Minimal man page.ajacoutot2016-09-071-3/+16
|
* syspatch goal is not to act as a package manager but to sync the system to theajacoutot2016-09-071-3/+3
| | | | | | | | corresponding stable. So prevent rollbacking a specific binpatch but instead always rollback the latest one. It's the only way we can know the system is consistent. discussed with halex@ jasper@ robert@
* No need to install the /var/syspatch/$REL directory, the binpatch does it for us.ajacoutot2016-09-051-1/+2
| | | | | | Put /var/syspatch into a variable, it's used more than 10 times. prodded by robert@
* Welcome syspatch(8), a binary patch management utility for the base system.ajacoutot2016-09-051-0/+37
This is currently a POC, maybe it will become something, maybe not. Therefore it will not be hooked to the build before we are happy with it. Workflow would be something like: - fetch and verify signed tarballs containing the patched binaries from a mirror - create a rollback tarball of the files we are about to replace - extract and install the patched files *** BIG FAT RED DISCLAIMER *** This is very much WIP, it does *NOT* work, don't bikeshed, don't use it! "get it in" deraadt@