Oke,

>
>
> heh, sounds like an intel ethernet interface. they were doing stupid
> stuff to me too, and i threw them out and replaced them with tulip cards
> i found in the supply cabinet.. :)
>

So I have a "stupid NIC", but can somebody then explain to me why
the Kernel build running from the same nfs mount has no problems ?

But on the other hand it looks like it is in that direction !, when
I ftp the files from ftp.netbsd.org/pub/NetBSD-current/src/<dir>/ the build
goes on, until it finds an other directory with similar problems. And again
I ftp the files. I have done this for I think 4 directories and it looks
like
/usr/src/lib is building now !

Is there maybe a problem with sup and nfs ?, that screws-up some files


>
> On Tue, 4 Jun 2002, Michael Kukat wrote:
>
> > Hi !
> >
> > On Tue, 4 Jun 2002, Lord Isildur wrote:
> > > > Yes, most likely you have stored these files on a machine which have
> > > > a bit-error in bit 1 somewhere in its memory, therefore causing s to
> > > > become q. This is most likely a PC because they normally don't have
> > > > parity memory and this won't be detected. The VAXen all have parity
> > > > memories so it's not likely it is caused there.
> >
> > Using cheap PC-crap, it could even be the NIC. A friend of mine
> had trouble
> > with a Novell network a while ago, and intensive hunting for
> this revealed the
> > network adapter flipping bits from time to time. Resulted in
> destroyed files
> > occasionally.
> >
> > ...Michael

Greets, Jan

----
With regards Jan H. van Gils
Internet web-page http://www.Knoware.NL/users/janvg/
Internet e-mail address JanVG@Knoware.NL
RIPE Whois JHG5-RIPE, 6BONE Whois JHG1-6BONE