IMHO, it's foolish to try to use a new release in a production 
environment until it has been out about three months.  Even then, it 
might not be ready.

This is in no way meant as a criticism; the folks working on the sparc64 
port have put in many hours of work, to put it mildly.  It is just a 
fact of life; some things won't be discovered before release.

Probably in this case it won't really take three months, but it's 
unreasonable to expect production quality on all hardware at the time of 
release.  I share your desire for a stable sparc system, but I consider 
the current state normal and expected and I'm impressed by how quickly 
each substantial problem is being fixed.

So, the best advise, for any o/s release, is, watch the list and wait, 
or put it on a non-production machine and be one of the testers.  Don't 
put it on a production machine yet.

As I said, that's just my opinion and others might have a completely 
different idea.

Gert Doering wrote:

>In muc.lists.netbsd.port.sparc Valeriy E. Ushakov wrote:
>
>  
>
>>On Thu, Feb 03, 2005 at 11:21:14 -0800, glen mccready wrote:
>>    
>>
>
>  
>
>>>>charles posted a work-around a while back that should help:
>>>>
>>>>http://mail-index.netbsd.org/tech-kern/2005/01/06/0006.html
>>>>        
>>>>
>>>any idea when these workarounds will hit -current? :-)
>>>      
>>>
>
>  
>
>>http://mail-index.netbsd.org/source-changes/2005/02/03/0015.html
>>    
>>
>
>Cool :-)
>
>Now - can one of you tell me whether it's a good or bad idea to apply
>those to 2.0.1 on sparc64?
>
>I *am* having crashes that might be attributeable to "threads+swapping",
>but I'm not using -current (but 2.0.1).  The suspect application is 
>"clamav-milter", built vs. system libpthread.
>
>gert
>  
>