FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006]

[Bob Johnson]

Kai <kai at xs4all.net> wrote
> Hello,
>
> Another ™.02,
>
> Today I'm installing Freebsd 6 from a CD, and I'm having to jump through
> loops to get it up-to-date. Take for example FreeBSD-SA-06:03.cpio.
>
> First I need to install the sources for the complete OS, then run a patch on
> it, and all that for the installation of 1 measily binary, and then keep
> track of the fact that I did this.

And all I had to do was
# freebsd-update fetch
# freebsd-update install

Although that was a 5.4 system, not 6.0.

>
> Supplying kernel-source patches is fine, but IMHO there is something really
> wrong with this. I don't want to be bothered by the hassle of keeping track
> of which security update I patched in my sourcetree and which not.
>
> So, please pretty please make something that lets us admins just download a
> binary package for an updated cpio, and let something whine if its installed
> already on a system.
>
> Shouldn't be too big a problem to get this done in 2006, rpm could do the
> job, apt-get would suffice too?

Have you looked at ports/security/freebsd-update? It handles this if
you are using a GENERIC kernel (and it works fine for non-generic
kernels if what needs updating is not part of the kernel).

As near as I can tell, the discussion here is (a) why not make
freebsd-update part of the base distribution instead of a port, and
(b) we need a tool that can do the same job on non-generic kernels
(which leads to a discussion of the best way to accomplish that).  But
I'm not trying real hard to follow it closely, although I agree that
moving freebsd-update into the base system would be a good idea.

- Bob