Date: Mon, 07 Dec 2009 11:23:56 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Alex Huth <a.huth@tmr.net> Cc: freebsd-questions@freebsd.org Subject: Re: update/upgrade question Message-ID: <4B1CE5CC.409@infracaninophile.co.uk> In-Reply-To: <20091207105332.GC3765@borusse.borussiapark> References: <20091207095416.GA3765@borusse.borussiapark> <4B1CD725.8030607@infracaninophile.co.uk> <20091207105332.GC3765@borusse.borussiapark>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9956F4AB72994C6B141FF53E Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Alex Huth wrote: > * Matthew Seaman schrieb: >>> Next question is if i don't get updates with freebsd-update when i ha= ve >>> a stable version? I have the problem with two machines (6.3 and 6.4).= On both >>> i do not get the public key because it is not available on the remote= server. >>> I have test it with debug. >> freebsd-update only covers the RELEASE branches. That is equivalent t= o >> RELENG_6_3 or RELENG_6_4 in your cases. However 6.3-RELEASE is due to= go out >> of support on the 31st January (http://www.freebsd.org/security/securi= ty.html) >> so now would be a good time to think about upgrading. > So if i understand that right, it is not possible to follow the engenee= ring in > stable and having all patches without using the way over "make buildwor= ld > ..."? Yes. If you want to track one of the development branches (HEAD, RELENG_= N) then you have to update sources by csup(1) or various other mechanisms an= d then compile your kernel+world yourself. Alternatively you can track release branches (RELENG_N_M) in the same way= , or so long as the release branch is still in support, you can use freebsd-update(8) to pull down pre-built binary updates.=20 Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK --------------enig9956F4AB72994C6B141FF53E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksc5dIACgkQ3jDkPpsZ+VZCcQCgtq2lfQpUSIreVzTnhtYO9ATa oisAnRL09DKTA5BVlLZbEM8CjsVy4Ldz =LjaF -----END PGP SIGNATURE----- --------------enig9956F4AB72994C6B141FF53E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B1CE5CC.409>