FreeBSD

Finally I caught the kernel panic caused by some strange bugs found in thread scheduling. Investigating the crashdump.

The following change is considered as a new errata candadite from my view:

peter 2005-04-18 21:36:17 UTC FreeBSD src repository

Modified files: (Branch: RELENG_5_4)
sys/i386/i386 genassym.c vm86bios.s
sys/i386/include pcb.h
Log:
MFC: stop i386_vm86() from either panicing or trashing random pages.

This can improve stability, however we can not easily prove that it is producable :-) So I have turned that to re@.

To quote him:

So I finally tried DragonFly on one of our test servers (not my desktop :-). It seems that DragonFly still have some issues with the SATA devices. I am trying to fix it, maybe by porting some good FreeBSD ATAng code.

DragonFly has gave us some good examples that how a user-friendly operating system should, and some different way on designing a MP-capable architecture. Thanks, Matt!

Sometimes you may need to build some packages for older/newer versions of FreeBSD. That is simple if you use jail and other mechanisms.

In order to be successful, you need a “Full jail” say ordinary jail, installed with binary that is built from the target version of FreeBSD. For instance, build a 6.0 userland by sync’ing code to -HEAD.

Secondly, you need to replace two files in the jail: uname(1) and sysctl(1). What you have to do is to use sed to replace both FreeBSD version and __FreeBSDVersion (say, kern.osreldate), according to porters’ handbook.

Cameron Grant, the developer of FreeBSD newpcm driver, has untimely died on 20th March, 2005. May him rest in peace.

方法A: 使用代理。

在/etc/make.conf中设置：
FETCH_ENV= “HTTP_PROXY=IP[:端口]”
如果需要，在FETCH_ENV值后面加入空格，
HTTP_PROXY_AUTH=basic:*:user:password

After several months’ work, we have finally get the Handbook into shape, and currently only the MAC and NETWORK-SERVER chapters are partially translated. All chapters are now in sync with English revision.

Review comments are highly appreciated.

Cameron Grant, author of the newpcm driver, died this morning. May he rest in peace.

As title. We *need* to struggle to make the upcoming 6.0-RELEASE a good release . I hope we can show the great improvements taken place in 6-CURRENT and hopefully we can cut 6-STABLE this June.

Highlights on recent 6-CURRENT that was not merged (and may never be merged):

• MPSAFE VFS
• Integrated VFS hashing (generallized, traditionally it’s different on ufs, msdosfs, etc)
• 64bit-ize of several utilities, to ensure better usage of large storage.