Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jun 2004 01:45:36 +0300
From:      Giorgos Keramidas <keramida@ceid.upatras.gr>
To:        Chris <bsdnewbie@coolarrow.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Bug report 64462
Message-ID:  <20040610224536.GA4406@gothmog.gr>
In-Reply-To: <20040610134134.1899e793.wmoran@potentialtech.com>
References:  <200406101233230373.24F9167F@coolarrow.com> <20040610134134.1899e793.wmoran@potentialtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2004-06-10 13:41, Bill Moran <wmoran@potentialtech.com> wrote:
>"Chris" <bsdnewbie@coolarrow.com> wrote:
>> I submitted a bug report:
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=64462
>>
>> back in March,and didn't notice any followup on it yet. Is there any way to
>> know if/when the bug will be addressed, or if someone found a fix for it?
>
> Considering that it's for 5.X, you might want to subsribe to FreeBSD-current@
> and ask there.

If possible, you should also try a newer version of 5.X.  If, for any
reason, you cannot install -CURRENT just give me a couple of days.  It's
been a while since I burned my last CD-ROM image, but I can give it a
try this weekend on my 5.2-CURRENT workstation at home (I'm running a
fairly recent 5.2-CURRENT build earlier this morning) and see if I can
reproduce the problem you reported.

- Giorgos



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040610224536.GA4406>