make installkernel/make installworld steps on the consuming systems. (edit: you have to distribute your /etc/src.conf, and possibly /etc/make.conf, to all the systems for that to work, build options must be the same for the build and install steps)
Is that related to 'update-packages' in src?
I didn't have a look into pkgbase myself yet (not that I don't like experiments, but there are others more important to me
), but as it is already "implemented" in the build system of 
src, I'd say that's very likely!
Still works. Saves a lot of time. And best off all, you don't have to allow every server access to the internet for updates.
server {
listen 192.168.X.X:80;
server_name fbsd-update.example.com;
root /var/cache/fbsd-update;
access_log /var/log/nginx/proxy-access.log;
location / {
proxy_cache fbsdupdate_cache;
proxy_cache_lock on;
proxy_buffering on;
proxy_http_version 1.1;
proxy_cache_revalidate on;
proxy_cache_valid 200 7d;
expires max;
add_header X-Proxy-Cache $upstream_cache_status;
proxy_pass http://update.freebsd.org;
}
}| The sha256(1) hash key for the desired release, is published within the respective release announcement. | |
| To generate the "End of Life" number for build.conf, refer to the "Estimated EOL" posted on the FreeBSD Security Website. The value of EOL can be derived from the date listed on the web site, using the date(1) utility, for example: |
