Kuliax Log

We have some news to tell you, most of them are from our development line. We listed them below for easy reading.

• Our RAM 256 MB was back to our development machine, this is great! Thank you Visipro for fixing our RAM, we’ve tested it and it run well. No more error messages, no md5sum checksum errors, no error reports by memtest86+. If you want to know the story behind it, read RAM Problem and fsck.ext3, badblocks, memtest86+.
• We’ve created some additional mailing lists in googlegroups: kuliax-devel dedicated for Kuliax development, kuliax-commits for Kuliax SVN commits, and kuliax-bugs for reports from our Bugtracker. The last one are being reconstructed and built, just wait a day or two.
• Live chat and support via IRC as a communication channel will be our first place, beside mailing lists, to discuss everything inside Kuliax. Wanna talk and discuss with us? just join #kuliax at irc.freenode.net. If you use Gaim/Pidgin and don’t know how to connect to our IRC channel, read this page.

For all member of development team, please help me to setup, fix, and update our software infrastructures.

Have you seen Kuliax stickers yet? You can see them here or here (faster if you come from Indonesia).

Which stickers do you like most??

Choose them in http://jzxt.pollhost.com/

We had a notification from DokuWiki when we logged in to wiki in kuliax.org on July 19, 2007. It told us that there was a XSS vulnerability discovered in DokuWiki and we should read the bug report for manual fix or upgrading the current version.

Actually the vulnerability is discovered in spellchecker backend and affected all version to 2007-06-26, even when spellchecker is disabled. But we’ve just known from the bug report that the vulnerability only exploitable with IE browser because of its broken MIME handling.

Continue Reading »

Frappr.com is one of map services on the Internet targeted for mapping communities. We just think that what if we can mapped people around Kuliax: developers, contributors, users, and supporters in one map. So we’ve created a map in frappr.com: www.frappr.com/kuliax.

So add yourself to the map and show your support to Kuliax Project

Kernel patch developed by Con Kolivas (CK) for 2.6.22 has been released. This is the last -ck patch ever. We planned to use this patchset in Kuliax 7.0 to improve the responsiveness and interactivity, like we did in our first 6.0 release. Why CK discontinued this project? quoted from ck.wikia.com, CK stated the following reasons:

• If whatever performance advantage it has is all but abolished compared to mainline then there is no point maintaining alternate patches to achieve the same endpoint.
• All interest I have in kernel development, even out of the mainline spotlight, has been… abolished (I had nastier words but decided not to use them.) It is clear that I cannot develop code for the linux kernel intended only to be used out of mainline and not have mainline get involved somewhere along the line. Whether it be the users or even other developers repeatedly asking “when will this be merged”. This forever gets me into a cycle of actually trying to merge the stuff and … well you all know what happens at that point (again I had nastier words but decided not to use them.) So, I’ve had enough. I’m out of here forever. I want to leave before I get so disgruntled that I end up using windows.”

Continue Reading »

Linux Kernel 2.6.22 has been released on July 8, 2007. Torvalds said in the git web interface:

Linux 2.6.22. Woo-hoo. I’m sure somebody will report a “this doesn’t compile, and I have a new root exploit” five minutes after release, but it still feels good ;)’.

And that sounds good for us too, because we can use this kernel version in Kuliax 7.0 and start building it with our planned patches, configuration, and optimization.

Continue Reading »

Maybe you want to know how we examined RAM problem in the previous post. We have tried several ways to do it:

• fsck.ext3 -c, ex: as root run fsck.ext3 -c /dev/hda6, it will check ext3 filesystem in the logical partition number 6 with badblocks checking.
• badblocks, this is separated program used for searching badblocks in a storage device. The recomended way to run this app is by using option -c via fsck.ext3. But if you want to run it directly never mind, it’s your choice, I’ve told you. Just run: badblocks -n /dev/hdaX for non-destructive mode instead of running it with option -w. You can’t combined the options in a single command. Continue Reading »