HEADS UP: Status of FreeBSD 5.2 release

Freebird

FreeBSD's Scott Long has an update on the resolution of a serious show-stopper for FreeBSD 5.2 release.

[Read more]
-------------------------------------------------

Date: Tue, 16 Dec 2003 17:44:01 -0700 (MST)
From: Scott Long <scottl@freebsd.org>
To: Doug Barton <DougB@dougbarton.net>
cc: current@freebsd.org
Subject: Re: HEADS UP: Status of the 5.2 release

On Tue, 16 Dec 2003, Doug Barton wrote:
> Do we have an updated status on this? I just got my new laptop, so I was
> going to burn an ISO of the latest RC and give it a try, but if it's
> going to blow up on install I don't want to waste time...
>
> Doug
>

The root cause was found, fixed, testd, and committed to HEAD recently.
I expect it to be committed to RELENG_5_2 tomorrow. Until then, you can
either try a 5.2-CURRENT snapshot, or gamble with 5.2-RC1 by turning off
softupdates on the destination partitions. Once installed, you can
turn SU back on.

Scott

=======================
Date: Tue, 16 Dec 2003 13:23:40 -0800
From: Doug Barton <DougB@dougbarton.net>
To: Scott Long <scottl@freebsd.org>
cc: current@freebsd.org
Subject: Re: HEADS UP: Status of the 5.2 release

Do we have an updated status on this? I just got my new laptop, so I was
going to burn an ISO of the latest RC and give it a try, but if it's
going to blow up on install I don't want to waste time...

Doug


Scott Long wrote:
> All,
>
> As I mentioned yesterday, we have a serious show-stopper for the 5.2
> release. Jeff Roberson and Doug White did some good diagnosis work a
> few nights ago, but we are still without a fix. We cannot cut 5.2 until
> this gets resolved. I know that this is the end of the year and
> everyone has deadlines, family, travel, etc, but we really need some
> more eyes on this. To recap, a panic happens from sysinstall while
> unpacking the bin distribution. It is most readily created by enabling
> SoftUpdates on the root partition, but there are reports that SU is not
> a required factor. The panic originates in the fsync codepath and
> ends with a corrupt mutex. This is discussed on the freebsd-current@
> mailing under the subject of "HAVE TRACE & DDB Re: FreeBSD 5.2-RC1
> released". Any help is appreciated.
>
> Thanks,
>
> The Release Engineering Team
>


=================================
Date: Sat, 13 Dec 2003 20:34:08 -0700
From: Scott Long <scottl@freebsd.org>
To: current@freebsd.org
Subject: HEADS UP: Status of the 5.2 release

All,

As I mentioned yesterday, we have a serious show-stopper for the 5.2
release. Jeff Roberson and Doug White did some good diagnosis work a
few nights ago, but we are still without a fix. We cannot cut 5.2 until
this gets resolved. I know that this is the end of the year and
everyone has deadlines, family, travel, etc, but we really need some
more eyes on this. To recap, a panic happens from sysinstall while
unpacking the bin distribution. It is most readily created by enabling
SoftUpdates on the root partition, but there are reports that SU is not
a required factor. The panic originates in the fsync codepath and
ends with a corrupt mutex. This is discussed on the freebsd-current@
mailing under the subject of "HAVE TRACE & DDB Re: FreeBSD 5.2-RC1
released". Any help is appreciated.

Thanks,

The Release Engineering Team

l63

终于在vmware中安装上了，很喜欢现在gnome的启动画面；
呵呵//

struggle

这图不错，呵呵

zz1zz

5.2的gnome logo不错啊，我装的是5.1的。

l63

自己编译内核后；感觉启动速度超快；
今天在装下xfce试一下；

Gavin_tju

GNOME怎么编译也不会感觉比xfce4快的,嘿嘿,当然如果你的机器超级好,好到感觉不出差别也没法说:p
GNOME现在在ports中的2.4.1版本如果编译的话就有这个logo了,我现在用的就是:p