XRP Ninja

But being a subsystem maintainer requires that you trust contributors to some degree, and you just can't trust contributors when you're a perfectionist. This means that the maintainer should be less of a perfectionist than the contributors, otherwise he/she ends up doing everything by him/herself. -- Jean Delvare "Ends up doing everything by him/herself"!

继续进行…… 下面是其他架构文档的翻译 http://gentoo.linuxsir.org/doc/progress.xml 任务认领中 我知道现在各个语言的文档都在翻译2007.0对应的文档 不过毕竟我们已经开始了2006.1的，现在还没完，理应先完成它 握有po这个武器，不用担心努力白费

要说两句，不说会憋出问题的。 首先，和Gentoo Weekly Newsletter翻译一样，Gentoo文档的翻译也还在继续。不过我最近捣鼓龙芯比较多，GWN和文档上花的时间不是很多。 目前文档翻译的过程是这样，我分配，然后翻译团队成员翻译，完了交给我，再交给审校人员审校。最后发表前，我还会再看一遍。每一篇文档，我都会做最后的把关，清除所有可能残留的错误。 有些错误甚至是语义上的错误。这是确实存在的，是令我比较郁闷的地方。所以每篇文章在我没看过一遍之前，我不敢就这么直接放到网上。而这会花很多时间。所以事实上有一些已经完成审校的文档积压在我这里，还没有发布。我的错，之后我会给文档更多一点时间。 之前的翻译模式有一个问题是不够透明，最好都发到gentoo-china邮件列表里。 就事论事，举个例子： The <c>video</c> statement controls framebuffer display options. It needs to be given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for 2.4 kernels) followed by the control statements you wish to enable. 审校后的文章里这句话译为： <c>video</c>声明用来控制framebuffer的显示参数。在你想启用的控制声明后必须给予framebuffer驱动（2.6内核使用<c>vesafa</c>，2.4使用<c>vesa</c>）。 这第二句完全没有表达出原文的意思，而且vesafb误写为了vesafa。当然人非圣贤，马有失蹄，但是遇到后面这种比较低级的失误，还是令人比较郁闷。我改动后，如下： <c>video</c>参数用来控制framebuffer的显示参数。此参数的内容形式是首先给出framebuffer驱动的名称（2.6内核使用<c>vesafb</c>，2.4使用<c>vesa</c>），后面跟着的

Foxsen(Zhang Fuxin, 张福新) has released a patch against linux 2.6.21-rc5. I have tried it today. It works well so far. My gentoo on loongson still have two minor problems, related to audio and video playback respectively. First of all, please be aware that none of these programs I used to play audio and video has any loongson specific patch. loongson has implemented its own multimedia instructions. So theoretically if properly patched, the performance will be better. On the audio side, audacious doesn't perform well when the frequency is low, while mplayer works fine. Maybe it's because they use difference libraries. On the video side, when mplayer plays some mpeg2 or divx video, video will fall behind audio, especially when the video's resolution is high. Last but not least, I heard some devs talked about loongson's profile on #gentoo-mips. It is widely accepted that it is not necessary to have a specific profile for loongson. Well, I am not insisting that we should have

If loongson finally were officially supported by gentoo, it must have its own profile. Currently, it uses cobalt's profile. Of course, one has to do some dirty hacks to make it usable with loongson. For example, cheat portage to make it think colo is already installed. Loongson box uses pmon as bios and bootloader, doesn't use colo which is cobalt's bootloader. Recently, I have read PMS draft. For me, it is quite informative. I've learned some internals about our package manager, specifically I've learned something about profile which i don't know before. Then I applied those knowledge into reality. I created a loongson specific profile in loongson overlay and used it. The main trick here is to write absolute path of parent directory into PARENT file, instead of "..". And it turned out to work well.

http://www.mips.com/PressRoom/PressReleases/2007-03-28 http://www.st.com/stonline/stappl/press/news/year2007/t2154.htm How exciting!!!

I have uploaded a stage4 to ftp://godson2e:lemote@www.easy2fly.org/, under the directory of Gentoo. FEATURES include but not limited to: 1. nptl pthread library, the debian shipped with box uses Linuxthreads pthread library. 2. complete KDE 3.5.5 3. 4 kernels, 32bit/64bit, with/without kgdb 4. partial mirror of gentoo.org, include half-translated Simplifid Chinese handbook 5. firefox, mplayer, audacious... I used binutils-2.17 when compiling firefox, USE flag of binutils is "multislot -multitarget nls -test -vanilla" This mplayer doesn't contain any loongson specific patch, but it works.