> :NFS append race @0:19
[snip]
> There were a bunch of situations that could cause this, including an
> append race for which the debug message was named after. The append
> race is now fixed but there are still a few situations that can cause
> this to occur.
Just anothe
> http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html
>
> Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8)
Significantly less than what its doing now.
What the article fails to mention, is that (last I heard) CA*Net3 is *not*
connected to the Intern
In attempting to test out Cameron's emu10k1 support, one quickly notices that
the build dies in $SUBJECT due to unresolved constants.
The attached patch fixes the problem. I'm happy to report that mpg123 is
playing mp3's quite fine. There's a little burst of static when it first
starts up, but ot
On Sun, Apr 16, 2000 at 09:30:17PM -0400, Donn Miller wrote:
> With a fresh cvsup as of 1/2 hour ago, I get the following link errors
> during the link stage of the kernel build. (Please see attached
> file.)
Try re-config/re-compiling your kernel after adding the following line to
/sys/conf/fil
On Sat, Oct 21, 2000 at 11:08:28PM +1000, Idea Receiver wrote:
>
> I just upgrade one of my server to -current. that server connect to ADSL
> and act as a gateway.
>
> however, after I upgrade that server to -current, all other clients
> (all windows 98) start acting really strange. clients was
> the other problem i had after switch that system to -current
> is that after a random time, the connection will frzzed.
> the routing table still exist, connection is still up.
> just cant connect to anywhere outside the network. no error
> or anything been loged in ppp.log.
Interestingly enoug
> > When it happens, killing ppp and restarting it is usually enough.
> >
> > I have no idea what causes it.
> >
>
> kill ppp and restart it doesnt help at all.
> will it make any different if i change a network card?
I dont think so. There are times when I cant do a simple kill/restart, and
> BTW: I believe PPPoE in both Julian and Archie's cases specifically
> uses the netgraph PPP implementation, so it's an "all in the
> kernel" approach; the problem may be your use of user space code
> (i.e. killable code, since you can't kill it in the kernel, only
> unlink or unload it).
Actual
