From owner-freebsd-hackers Mon Dec 8 08:00:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA16916 for hackers-outgoing; Mon, 8 Dec 1997 08:00:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from beast.gu.net (beast.gu.net [194.93.190.196] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA16895; Mon, 8 Dec 1997 08:00:25 -0800 (PST) (envelope-from stesin@gu.net) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by beast.gu.net (8.8.7/8.7.3) with SMTP id RAA16868; Mon, 8 Dec 1997 17:59:33 +0200 (EET) Date: Mon, 8 Dec 1997 17:59:33 +0200 (EET) From: Andrew Stesin Reply-To: stesin@gu.net To: John Fieber cc: "Jordan K. Hubbard" , freebsd-hackers@freefall.FreeBSD.org Subject: Re: F00F patch problems for 2.2.5-RELEASE (incomplete patch.) In-Reply-To: Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, John Fieber wrote: > > > Fix: Update to the 2.2-stable version of the kernel or apply the > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Would you mind pointing out the breakpoint -STABLE snapshot date, > > please? > > I don't have an answer, but checking back in the file I was > rather stunned to notice that there is NO date information for > any of the updates. ?! > If you are applying the supplied patches, > that is probably okay, but a big problem for anyone being very > conservative and/or selective about tracking stable. That's exactly me myself :) > As has been > brought up recently, blindly tracking a "stable" kernel without > updating user-land utilities can bite you--I learned this from > personal experience. Same here. So I'm just grabbing the whole snapshot from time to time -- no time for extra experimentation. Best regards, Andrew Stesin nic-hdl: ST73-RIPE