Subject: Re: Nightmare File Corruptions with 1.6Q - FFS?
To: Sean Davis <firstname.lastname@example.org>
From: Kevin Lahey <email@example.com>
Date: 04/11/2003 18:36:05
On Fri, 11 Apr 2003 19:44:47 -0400
Sean Davis <firstname.lastname@example.org> wrote:
> FFS2 should *NOT* have been put in current until it was made stable, IMHO.
> 1.6Q right after the FFS2 code went in corrupts files with much enthusiasm,
> late 1.6Q and 1.6R can't even find init on this machine (i386). What ever
> happened to developing things on branches and fixing at least most of the
> bugs before merging? I've been using -current since 1.4ZC, and this is the
> worst bug I've seen yet.
Speaking as somebody who just lost 10 days worth of e-mail (nope, not
backed up), I have to agree that this is the worst I've ever been thwacked
for running -current. OTOH, I'm glad that it went in. It seems like
whenever something goes into a branch it languishes forever. It is far
better to get it up into -current and start banging on it.
After all, I saw the warning that it was going in, and I decided to
upgrade anyway. It *is* -current. Now, if the bugs don't get fixed,
I'll agree with you, but I see a stream of bugfixes going in.