FreeBSD 5-CURRENT bug?
Several servers I manage running FreeBSD 5-CURRENT as of 20040228 appears to bearing wierd deadlocks, which could be triggered by ps(1), top(1) and w(1).
共691篇文章。
Several servers I manage running FreeBSD 5-CURRENT as of 20040228 appears to bearing wierd deadlocks, which could be triggered by ps(1), top(1) and w(1).
junsu and I have discussed about some big hacks to FreeBSD kernel, and the implementation of a minidump is a good idea, I think.
On Windows there’s a minidump mechanism. The minidump will save ‘crashing’ pages only, while full dump will save the whole core memory when the system going to crash.
It’s the latest NetBSD stable RELEASE. This version is dedicated to Erik Reid, a NetBSD developer who contributed many MIPS related port efforts, as well as the XFree86 DRI interface, and were dead in an sailing accident in February 18, 2004.
Under a more restrictive licence, the XFree86 project has finally released the long-awaited XFree86 4.4.0-RELEASE. Well, this is really a big news, however, the licence (Yes you guys may say that it is very similiar to the BSD Licence with four clause, however it is not, and more importantly, this is more like the ancient four clause one, which was replaced by a new three-caluse one, and most BSDers will prefer a two clause one like the following:
据说骑车的时候把锁骨摔断了(极度怀疑这篇报道的真实性!)……
Wish him to be recovered soon…
This will catch up with FreeBSD-CURRENT’s latest kern_fork.c change (rev. 1.215):
https://research.delphij.net/freebsd/pid.diff
The patch is based on junsu’s port of NetBSD PID Allocator. Use this on your own risk :-)
Scott Long today announced the release. This is a point release over 5.2-RELEASE which addresses many critical bugs.
The -CURRENT have already differentiated from the RELENG_5_2 branch, say, 5.2.1-RELEASE by this time. The most significant differences are:
It can be obtained here:
http://www.arbornet.org/~junsu/gcov.diff
I have noticed that the FreeBSD mailing list stops to send me mail from circa 19:05 CST here yesterday. What happend?!
Profiling based optimization means better performance.
Here’s phk’s suggestion:
We can compile our kernel with "--test-coverage --profile-arcs" to
do basic-block profiling (see kernbb(8) and gcov(1)/gcc(1) docs.)