[Galaxy Ace S5830 Android Development] mdfzhi:
ketut.kumajaya, thanks for that great tutorial of rom cooking :D

i've tried it, and i think theres something need to be note of

losetup /dev/loop0 system.rfs
mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=4 -O ^resize_inode,^ext_attr,^huge_file,^has_journal /dev/loop0
tune2fs -c 100 -i 100d -m 0 /dev/loop0

losetup /dev/loop0 data.rfs
mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=16 -O ^resize_inode,^ext_attr,^huge_file /dev/loop0
tune2fs -c 100 -i 100d -m 0 /dev/loop0
mount /dev/loop0 /tmp/ext4

losetup /dev/loop0 csc.rfs
mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=4 -O ^resize_inode,^ext_attr,^huge_file /dev/loop0
tune2fs -c 100 -i 100d -m 0 /dev/loop0
mount /dev/loop0 /tmp/ext4

wont works, those command(losetup, mkfs.ext4, tune2fs and mount) need root access, so it should be

sudo losetup /dev/loop0 system.rfs
sudo mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=4 -O ^resize_inode,^ext_attr,^huge_file,^has_journal /dev/loop0
sudo tune2fs -c 100 -i 100d -m 0 /dev/loop0

sudo losetup /dev/loop0 data.rfs
sudo mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=16 -O ^resize_inode,^ext_attr,^huge_file /dev/loop0
sudo tune2fs -c 100 -i 100d -m 0 /dev/loop0
sudo mount /dev/loop0 /tmp/ext4

sudo losetup /dev/loop0 csc.rfs
sudo mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=4 -O ^resize_inode,^ext_attr,^huge_file /dev/loop0
sudo tune2fs -c 100 -i 100d -m 0 /dev/loop0
sudo mount /dev/loop0 /tmp/ext4

or the user itself should manually make him/her in those groups (but i think theres only mount group, no group for losetup, mkfs.ext4 and tune2fs. atleast in my machine).

ok then, enough of that, i've also got a few question.

1. in fix-system.sh script, these line:

rm -f bin/cat
rm -f bin/chmod
rm -f bin/chown
rm -f bin/cmp
rm -f bin/date
rm -f bin/dd
rm -f bin/df
rm -f bin/dmesg
rm -f bin/getevent
rm -f bin/getprop
rm -f bin/hd
rm -f bin/id
rm -f bin/ifconfig
rm -f bin/iftop
rm -f bin/insmod
rm -f bin/ioctl
rm -f bin/ionice
rm -f bin/kill
rm -f bin/ln
rm -f bin/log
rm -f bin/ls
rm -f bin/lsmod
rm -f bin/lsof
rm -f bin/mkdir
rm -f bin/mount
rm -f bin/mv
rm -f bin/nandread
rm -f bin/netstat
rm -f bin/newfs_msdos
rm -f bin/notify
rm -f bin/printenv
rm -f bin/ps
rm -f bin/reboot
rm -f bin/renice
rm -f bin/rm
rm -f bin/rmdir
rm -f bin/rmmod
rm -f bin/route
rm -f bin/schedtop
rm -f bin/sendevent
rm -f bin/setconsole
rm -f bin/setprop
rm -f bin/sleep
rm -f bin/smd
rm -f bin/start
rm -f bin/stop
rm -f bin/sync
rm -f bin/top
rm -f bin/umount
rm -f bin/uptime
rm -f bin/vmstat
rm -f bin/watchprops
rm -f bin/wipe
rm -f bin/dumpmesg

should delete all those file stated in the command. can i know why we should remove those file? just curious :D

2. in fix-data.sh script

if [ -d data_test ]; then
rm -rf data_test
fi

if [ -d kernel-tests ]; then
rm -rf kernel-tests
fi

if [ -d local ]; then
rm -rf local
fi

if [ -d qmi_test ]; then
rm -rf qmi_test
fi

will delete data_test, kernel-tests, local and qmi_test folder. may i know why?

3. on command to create blank ext4 image for data.rfs

count=46400

will make the size whooping 185mb. may i know why its so big? because i saw default data.rfs from default rom is just around 5mb. would'nt there be problem when flashing data.rfs file as big as 185mb?

thanks :D:D:D