From owner-freebsd-current Tue May 4 0:23:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2C2F814F9A for ; Tue, 4 May 1999 00:23:13 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08671; Tue, 4 May 1999 01:22:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55644; Tue, 4 May 1999 01:23:50 -0600 (MDT) Message-Id: <199905040723.BAA55644@harmony.village.org> To: Dispatcher Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 May 1999 15:41:51 EDT." <199905021941.PAA22423@blackhelicopters.org> References: <199905021941.PAA22423@blackhelicopters.org> Date: Tue, 04 May 1999 01:23:50 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905021941.PAA22423@blackhelicopters.org> Dispatcher writes: : For mission-critical systems, I'm still installing 2.2.8-stable. And the security officer still back ports relevant patches to 2.2.8-stale. The 2.2.8 -> 3.x transition lost support for several devices (aic being the mostly loudly complained about). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message