Date: Mon, 17 Sep 2007 20:14:06 +0100 From: Daniel Bye <freebsd-questions@slightlystrange.org> To: freebsd-questions@freebsd.org Subject: Re: Clarification on updating FreeBSD through csup Message-ID: <20070917191406.GA30248@catflap.slightlystrange.org> In-Reply-To: <20070917205857.A56089@obelix.home.rakhesh.com> References: <20070917205857.A56089@obelix.home.rakhesh.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2007 at 09:24:26PM +0400, Rakhesh Sasidharan wrote: >=20 > Hi there! >=20 > Just seeking a clarification on keeping FreeBSD up-to-date through csup. = I=20 > am on FreeBSD 6.2 and want to keep up-to-date for security patches=20 > etc. >=20 > I understand I can use csup to follow the RELENG_62 branch. After the=20 > sources are downloaded, do I have to follow all the steps outlined in thi= s=20 > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html= )=20 > handbook document? I can understand building and installing world and=20 > kernel, but would I have to reboot to single user and do the mergemaster= =20 > stuff too? If you follow the complete rebuild instructions, yes. If you follow the instructions for *patching* the system as given in the relevant security notifications, then only if those instructions say so. You do subscribe to security-notifications@, don't you? ;-) > I *think* I might not have to do mergemaster coz security updates=20 > shouldn't have changes in the /etc files and so there'd be no need for=20 > merging files. Sometimes, the security fixes involve changes under /etc. The recent jails error comes to mind, as a case in point. > And I *think* I might have to reboot depending on whether I=20 > use the stuff being affected or not ... But I'd like a clarify=20 > from more knowledgeable folks nevertheless. :) If you follow the full procedure (buildworld, buildkernel, installkernel, installworld), then you absolutely must reboot after installing the new=20 kernel, and before installing the new world. Not doing so will soon lead=20 along the road to madness as your userland and kernel get out of step. As= =20 I said above, though, if you follow the shorter instructions given in the= =20 security notifications, then you may not need to - it depends very much on= =20 which bit of the system is affected by the changes.=20 > Also, would the "make buildworld installworld" part take a long time? Or= =20 > through the magic of "make" it just compiles the stuff that's getting=20 > updated (and stuff that requires on this)? The time taken depends very much on the specification of your system. My old Sun Ultra SPARC10, for example, takes up to 14 hours to do a full buildworld/buildkernel sequence, whereas the core duo boxes I look after for clients, zip through it in less then 1.5 hours. I'd suggest trying it out on a non-critical system, so as to familiarise yourself with the procedure. You'll be glad you did. Dan=20 --=20 Daniel Bye PGP Key: http://www.slightlystrange.org/pgpkey-dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG7tH9ixf5fBYiFmoRAtlpAJ4tK//qbpMxhKjBNNwcWiFBmIvXJgCgnE9c uagct5qVOXXawHGJod4grdg= =ho08 -----END PGP SIGNATURE----- --DocE+STaALJfprDB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070917191406.GA30248>