Bug report 64462
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? Thanks, Chris _ Email harvesters eat this: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bug report 64462
Chris [EMAIL PROTECTED] 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. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bug report 64462
On 2004-06-10 13:41, Bill Moran [EMAIL PROTECTED] wrote: Chris [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
