From owner-freebsd-stable Wed May 26 10: 7:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id CD99014D61 for ; Wed, 26 May 1999 10:07:34 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id KAA17994; Wed, 26 May 1999 10:07:33 -0700 (PDT) (envelope-from obrien) Message-ID: <19990526100733.B7630@nuxi.com> Date: Wed, 26 May 1999 10:07:33 -0700 From: "David O'Brien" To: Mike Meyer , freebsd-stable@FreeBSD.ORG Subject: Re: [Q] How stable is FreeBSD 3.X ? Reply-To: deobrien@ucdavis.edu References: <374C0839.AD2EE3FC@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Mike Meyer on Wed, May 26, 1999 at 08:48:55AM -0700 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not familiar with service packs. However, I can certainly tell the > difference between doing a "make world" and installing a patch from > Sun. The patch doesn't change every system binary. However, with FreeBSD, a future patch will not undo the patch I just installed. Sun has a history of "dueling" patches when a system binary has two unrelated problems with it. Patch 1 will fix problem 1, and when you install patch 2 to fix problem 2 -- guess what! Patch 2 doesn't include the fix for problem 1. > and you don't necessarily have to reboot the system as part of the > process. But since you don't know if what was patched was something only read at startup, you always need to reboot a Sun after patching. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message