To view parent comment, click here.
To read all comments associated with this story, please click here.
What some people don't realize, is that while freebsd-update performs an immediate binary upgrade of the base system, it also updates the relevant sources. This is evident from the following line in /etc/freebsd-update.conf:
# Components of the base system which should be kept updated.
Components src world kernel
The immediate impact of this: If you have compiled a custom kernel prior to the update, you only need to recompile / reinstall it (using the same configuration file). This is usually a 10-20 minute process on any recent machine and only requires two commands.
If your plan is to stay to -RELEASE + security patches, you only need freebsd-update and the occasional kernel recompilation. No need whatsoever to make buildworld.
As for ports, once again you don't really need to upgrade if you don't have any functionality problem (and the port does not exhibit security problems) you are in no way forced to upgrade. The portaudit program can be used to email you daily on the security status of installed ports.
"What some people don't realize, is that while freebsd-update performs an immediate binary upgrade of the base system, it also updates the relevant sources. [...] The immediate impact of this: If you have compiled a custom kernel prior to the update, you only need to recompile / reinstall it (using the same configuration file). This is usually a 10-20 minute process on any recent machine and only requires two commands."
I think it's possible to do it with one command:
# make buildkernel installkernel KERNCONF=MYKERNEL
This is one command. :-)
"If your plan is to stay to -RELEASE + security patches, you only need freebsd-update and the occasional kernel recompilation. No need whatsoever to make buildworld."
I didn't explain it in such a clear way, so thank you, you're correct of course: Using freebsd-update obsoletes compiling processes except for the kernel, if you want to use a custom kernel.
"As for ports, once again you don't really need to upgrade if you don't have any functionality problem (and the port does not exhibit security problems) you are in no way forced to upgrade."
As I mentioned before, using daily updated ports is interesting only if you're intendedly planning to use "bleeding edge software". In most other cases, using the precompiled packages via pkg_add command is the usual way to install software, or, for upgrading, preceded by deletion of the package (not fully elegant, but working; pay attention to dependencies).






Member since:
2006-10-08
"No need to rebuild world unless you want to move to another point version or another branch. Even for that, it's my understanding that freebsd-update will now upgrade you from one point releae to the next as well."
The freebsd-update provides a means to update the base system on a binary basis, so it exists to help you avoiding "make buildworld buildkernel" etc. as long as you would tend to use the GENERIC kernel configuration file. For updating the world, there is nothing that the system maintainer changes (e. g. /etc/make.conf), but regarding the kernel, there are users (I may include myself here) who intendedly compile a custom kernel, for example, to have just the hardware drivers in the kernel that exist physically inside the worksation, or to have some kernel parameters tweaked that cannot be set at "runtime level", for example firewall behaviour, bktr (Brooktree TV capturer) configuration or language settings, such as
options SC_DFLT_FONT
makeoptions SC_DFLT_FONT=iso
options ATKBD_DFLT_KEYMAP
makeoptions ATKBD_DFLT_KEYMAP="german.iso"
options UKBD_DFLT_KEYMAP
makeoptions UKBD_DFLT_KEYMAP="german.iso"
Such "strange" things cannot be handled by freebsd-update, as far as I know.