If a custom release is built using the native
make release
procedure,
freebsd-update-server code will work
from your release. As an example, a release without ports or
documentation can be built by clearing functionality pertaining
to documentation subroutines findextradocs ()
,
addextradocs ()
and altering the download
location in fetchiso ()
, respectively, in
scripts/build.subr
. As a last step, change
the sha256(1) hash in build.conf
under
your respective release and architecture and you are ready to build
off your custom release.
Adding -j
flags to NUMBER
buildworld
and
obj
targets in the
scripts/build.subr
script may speed up
processing depending on the hardware used, however it is not
necessary. Using these flags in other targets is not
recommended, as it may cause the build to become unreliable.
Create an appropriate DNS SRV record for the update server, and put others behind it with variable weights. Using this facility will provide update mirrors, however this tip is not necessary unless you wish to provide a redundant service.
This, and other documents, can be downloaded from http://ftp.FreeBSD.org/pub/FreeBSD/doc/
For questions about FreeBSD, read the
documentation before
contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.