FreeBSD

Sigh, I got this:

This doesn’t seem to be possible to my best of knowledge. What happend?

It’s 5.3-RELEASE-p2, and the panic string was: panic: pmap_enter: invalid page directory pdir=0xc1e063, va=0xffc00000

Traditionally, FreeBSD has many NO_FOO knobs while it also has NOFOO knobs that is quite confusing. Today, Ruslan Ermilov (The Makefile guru at FreeBSD campaus) has started his NOFOO -> NO_FOO conversion, this will make everything consist.

It’s now consered as a legacy branch like RELENG_2_2 and RELENG_3. Future commits to RELENG_4 no longer needs re@’s approval, but only those committed to RELENG_4_11 (with re@’s approval, of course) will go to 4.11-RELEASE. 4.11-RELEASE will be the final 4-STABLE release and it will be a errata release.

Today I have bought a BenQ FP756-12ms LCD monitor and now I can use it at home for my developments and my *BSD involements can be better continued.

It seems that the official FreeBSD qmail port’s disable-qmail (as well as the Live with Qmail documentation) will need write access to /usr/bin and /usr/libexec, and hence the “fast jail” script I have written has been rendered useless :-(

I will investigate the issue this weekend and hopefully I will be able to work around the issue.

Today liukang has suggested some software that will fight against blog spamming. They are:

http://www.jayallen.org/projects/mt-blacklist/

and

http://www.neuro-tech.net/archives/000315.html

The first is MT plugin and the second is its data automatic updater.

I’ve no time to turn them into ports at this time. Will try them on my box and if I have time I will port them.

Someone has started a vote on developers@. Will we keep the moscot?

最近几天和FreeBSD有关的活动将不得不减少。

Today I start to build a package set for corporation’s production servers. However, perl 5.8 build was stopped with a strange error.

I went into investigating what is happening. Finally I found that I should have mount_devfs’ed before jailing the builder :-( What a shame…

When I have loaded drm/radeon, my laptop will reboot right after X11 is going to start. Not known why this time… :-(