[Galaxy S I9000 Android Development] z4ziggy:
WARNING:

Use this on your own risk! I will not be held responsible for any failure that might be caused by using this.

"How should I know if it works? That's what beta testers are for. I only coded it."

- Linus Torvalds

What:

Yet another attempt at breaking free from RFS on the SGS phone (ie, lagfix), for Eclair, Froyo, and hopefully Gingerbread...

Which:

Supported devices are I9000 ATM. Theoretically it should work on all SGS variants, but since I only have I9000 to test on, I can't confirm this. I'd appreciate if other model owners will give it a try and report back.

Why:

KISS. I don't want to compile my own kernel or use a specific kernel (see voodoo) for my lagfix. I'd like to have a lagfix for ANY kernel out there.

z4mod is the 1st attempt in achieving that.

Another issue is standards. We don't need multiple lagfixes, all doing the same thing. One method, easy to customize and implement - thats the way to go.

How:

1. Use the online z4mod patcher to patch your kernel.

2. Download and apply one of the following update.zip files to convert your /data partition to the filesystem of your choice.

z4mod update.zip variants:

z4mod.ext2.update.zip - convert to ext2 - works on ALL kernels.

z4mod.ext3.update.zip - convert to ext3 - works only on modified kernel which supports ext3.

z4mod.ext4.update.zip - convert to ext4 - works only on modified kernel which supports ext4.

z4mod.auto.update.zip - automatically find which fs are supported by the kernel and convert to best suited - works on ALL kernels.

z4mod.rfs.update.zip - convert back to RFS - works on ALL kernels..

These update.zip files can be applied only to kernels which has been patched with z4build - a shell script which patches zImage to allow the init scripts additional non-RFS mount to each RFS partition, or with our online z4mod patcher. If the ROM you wish to install wasn't originally patched with z4build already, you can run z4build yourself on the zImage from the ROM package and put the patched zImage back to the ROM package for flashing, or use the online z4mod patcher to do it for you. It is that easy.

[NOTE:] Kernels (zImage) patched by z4build supports both mounts - RFS and non-RFS. So it doesn't change anything for users who doesn't apply z4mod.

You can also patch your z4mod scripts to enhance it's functionality, add more filesystems support, etc.

Although z4mod allows converting all the partitions from RFS to ext2/3/4, our update.zip files only convert /data - since this is ment for the 'masses'. If you feel brave enough, feel free to experiment with converting more partitions. All the sources are well documented.

Who:

z4ziggy, aka Elia Yehuda.

___

Original post [for reference]:

Although this is a half-baked project and far from complete, im introducing it to the xda community so i might get more ideas, and fix/implement more functionality, as the project advances.

z4mod is the 1st step in breaking free from RFS death grip - or at least tries to achieve this. The project adds ext3 support to a given zImage's init scripts, and creates update.zip for converting all RFS partitions and flash the patched zImage.

...thats the idea anyway.

ext4 support is planned for future official release. for testings purposes ext3 is sufficient.

sources and information can be found on my blog here: http://z4ziggy.wordpress.com