From owner-freebsd-current Sat May 5 7: 0: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from chunky.cacheboy.net (chunky.cacheboy.net [203.56.168.70]) by hub.freebsd.org (Postfix) with ESMTP id 8762D37B423; Sat, 5 May 2001 07:00:00 -0700 (PDT) (envelope-from adrian@chunky.cacheboy.net) Received: (from adrian@localhost) by chunky.cacheboy.net (8.11.3/8.11.3) id f45Dxjl13292; Sat, 5 May 2001 15:59:45 +0200 (CEST) (envelope-from adrian) Date: Sat, 5 May 2001 15:59:45 +0200 From: Adrian Chadd To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP! bad bug in -current. Message-ID: <20010505155945.A8812@chunky.cacheboy.net> References: <20010501165654K.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Wed, May 02, 2001 at 11:22:23PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001, Robert Watson wrote: > On Tue, 1 May 2001, Jordan Hubbard wrote: > > > > 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. ;-) > > Obviously I haven't been playing in the right bits of the system, I'll > have to start hacking the low-level stuff in FFS some more... I tend not > to cause permanent damage to file systems, sadly. > > I think we can all take lessons from phk here -- he achieves a level of > destructiveness that makes even the pro's marvel in wonder. *grin* Its ok. phk has just reminded us of what -current really is .. :-) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message