From owner-freebsd-questions@FreeBSD.ORG Thu Dec 23 10:05:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4E6E16A4CE for ; Thu, 23 Dec 2004 10:05:19 +0000 (GMT) Received: from male.aldigital.co.uk (male.thebunker.net [213.129.64.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D979343D45 for ; Thu, 23 Dec 2004 10:05:17 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from gravitas.thebunker.net (gateway.ash.thebunker.net [213.129.64.4]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by male.aldigital.co.uk (Postfix) with ESMTP id 41B5797741; Thu, 23 Dec 2004 10:05:16 +0000 (GMT) Received: from [127.0.0.1] (localhost [127.0.0.1])iBNA5ElA088010; Thu, 23 Dec 2004 10:05:14 GMT (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <41CA9853.6030405@infracaninophile.co.uk> Date: Thu, 23 Dec 2004 10:05:07 +0000 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Marella References: <3B5700417F70BA4CA7D2EA98375EF64003157033@CAUUNI2K000MSG.unibanco> <41C7F33B.7000509@infracaninophile.co.uk> <20041222141819.2fc5e93e@localhost> In-Reply-To: <20041222141819.2fc5e93e@localhost> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3DDCA17CDE186DF098BA8231" cc: Marcio Cardenuto Mallavazzi cc: freebsd-questions@freebsd.org Subject: Re: Question about FreeBSD 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 10:05:20 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3DDCA17CDE186DF098BA8231 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Robert Marella wrote: > On Tue, 21 Dec 2004 09:56:11 +0000 > Matthew Seaman wrote: > > >> 5.3-STABLE is a moving target from the RELENG_4 development branch. >> It should run stably and it can be used usefully as a desktop system >>or whatever, but tracking -STABLE is not recommended for *absolutely has >>to be up 24x7* type applications, because new functionality and support >>for new hardware will be introduced, which can result in problems >>occasionally. (In practice this very rarely happens: which is a great >>tribute to the degree of care taken by FreeBSD developers). Err... Um... I hope you all noticed the deliberate misteak. Of course it's the RELENG_5 branch for 5.3-STABLE. > If one is *tracking* 5.3-STABLE on a non-critical system and is subscribed > to the stable mailing list, how does one know when to cvsup and build world? > I have not seen anything on the list to indicate I should update my source. > > I have seen that 5.3-RELEASE is now P2 but nothing about STABLE. Should I > be doing it regularly (weekly, daily)? Or did I just miss something? > > Thank you for this and all of your previous posts. I look forward to > seeing your name as a poster for I know it will be another learning > experience. You should certainly be subscribed to freebsd-security@... or freebsd-announce@... so you get notification of any new security alerts. Any security fixes that go into one of the -RELEASE branches will also go into -STABLE, so doing a cvsup+buildworld cycle will get you the fixes. Otherwise, if you're particularly interested, you can subscribe to one of the cvs-foo@... mailing lists and see all of the commits going into the tree, or you can just cvsup(1) regularly (but not necessarily buildworld at the same time) and watch the cvsup output to see if there have been commits to part of the system that particularly interest you. Or you can just decide to update daily or monthly or at whatever frequency suits you best, as well as updating when ever a security alert appears that affects you. Unless there's a particular bug that's been affecting you, there really isn't any /necessity/ to update. However, it can be a useful exercise to help you keep in touch with current areas of work, and it helps the developers if you can report any problems with an up-to-date system. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor School Rd PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone Tel: +44 1304 617253 Kent, CT14 0JL UK --------------enig3DDCA17CDE186DF098BA8231 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQCVAwUBQcqYWpr7OpndfbmCAQIQywP+KML8IvYtEgQ7HTqB16Mv1lCxasSCgpFZ VcDOSEGRFCyexkkbj+tKTwKOCMDYEpsCh1i6pcIC0PlY/ifxKOk+uDf8P6jUMMpR LL7A6/yOQ67H5/0qOibku6UFsiv04GM46PDYsaKlRhtnm8ZNq35LLeSmevsRBnOP zPWh+rR258g= =Ec8o -----END PGP SIGNATURE----- --------------enig3DDCA17CDE186DF098BA8231--