On Sat, Jan 01, 2005 at 08:15:39PM +0100, Timo Schoeler wrote:
> >>but after all, why isn't a  bug-fixed 1.6.2 iso supplied?
> >
> 
> Harvard Eidnes wrote:
> 
> >Well, most probably because there are other severe problems with
> >sparc64 on 1.6.2; I beleive the compiler being one of them, and that
> >it's not the only largish problem with that combination.
> >
> >I think your best bet is to use 2.0 on sparc64, or... 2.0.1 when that
> >comes out -- a couple of important fixes for fatal problems in the
> >sparc64 port didn't make the cut for 2.0.  We hope to push out 2.0.1
> >for sparc64 relatively quickly.
> 
> Matthias Scheler wrote:
> 
> >But after NetBSD 2.0 has been released, why do you insist on using 
> >1.6.2?
> >NetBSD-sparc64 has been significantly been improved after in that 
> >release.
> 
> hi,
> 
> of course i am aware of the differences between 1.6.2 and 2.0 -- and i 
> can confirm that using 2.0 on sparc64 is less pain than using 1.6.2.
> 
> nevertheless, i see no reason to distribute a *buggy* 1.6.2 iso for 
> while the bug is i) known and ii) fixed...

Yes, and if those changes have been pulled up to the 1.6 branch the 1.6.3
release would incorporate them.

The fact is, the "1.6.2" release didn't have them. Just like the 2.0 
release doesn't have features/fixes from -current today. We won't be going
back and "correcting" the 2.0 images out there...We'll release 2.1, 2.2, etc
to pull up fixes.

James