From owner-freebsd-current Tue May 1 16:58:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id CC2A537B423 for ; Tue, 1 May 2001 16:58:50 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 399E510F40F; Tue, 1 May 2001 18:58:55 -0500 (CDT) Message-ID: <021701c0d29a$a9dcf2c0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: , "Jordan Hubbard" Cc: References: <20010501191534.96E1A380C@overcee.netplex.com.au><20010501182359.A22707@over-yonder.net> <20010501165654K.jkh@osd.bsdi.com> Subject: Re: HEADS UP! bad bug in -current. Date: Tue, 1 May 2001 18:58:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It was almost like that dirpref problem I ran into a few weeks ago, I upgraded from -stable to -current and I had to reinstall because of it, but this usually doesn't happen. ----- Original Message ----- From: "Jordan Hubbard" To: Cc: Sent: Tuesday, May 01, 2001 6:56 PM Subject: Re: HEADS UP! bad bug in -current. > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > Has something near this magnitude of Really Bad Stuffage snuck into the > > codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message