Date: Tue, 1 May 2001 18:23:59 -0500 From: GH <grasshacker@over-yonder.net> To: current@freebsd.org Subject: Re: HEADS UP! bad bug in -current. Message-ID: <20010501182359.A22707@over-yonder.net> In-Reply-To: <20010501191534.96E1A380C@overcee.netplex.com.au>; from peter@wemm.org on Tue, May 01, 2001 at 12:15:34PM -0700 References: <20010501191534.96E1A380C@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 01, 2001 at 12:15:34PM -0700, some SMTP stream spewed forth: > Any -current kernel built over the weekend is a likely victim of this bug. > In a nutshell, it will eat your root filesystem at the very least, leaving > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > is should be avoided at all costs. > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > will self destruct after install. > > ------- Forwarded Messages *snip* Say, FreeBSD is usually pretty safe, even in CURRENT. Has something near this magnitude of Really Bad Stuffage snuck into the codebase before? (This is just for my personal knowledge. I don't remeber anything this bad in recent times.) gh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010501182359.A22707>