[Desire Android Development] Droidzone:
If I wanted to add ext4 support to my stock kernel, would it be enough to replace the boot.img-kernel file from the boot.img extracted via dsixda kitchen, with the same file of another rom (like Leedroid) which has this support. Do any other file need updation? Do I have to do anything in /boot.img-ramdisk

Just tried it out..

Boot loop with Leedroid..But that's probably b/c I used the a2sd version, though I did remove the a2sd script..

Here's my log..

After mounting everything, I did this..

C:\Software\htc\ROMs\DATA2SD\New Sibere>"C:\Software\htc\ROMs\DATA2SD\New Sibere\pusher.bat"
Preparing to push
Press any key to continue . . .
1377 KB/s (220384 bytes in 0.156s)
1301 KB/s (374860 bytes in 0.281s)
1218 KB/s (253468 bytes in 0.203s)
1086 KB/s (139012 bytes in 0.125s)
1098 KB/s (228540 bytes in 0.203s)
1377 KB/s (220384 bytes in 0.156s)
1530 KB/s (220384 bytes in 0.140s)
352 KB/s (28180 bytes in 0.078s)
591 KB/s (9460 bytes in 0.015s)
578 KB/s (18520 bytes in 0.031s)
856 KB/s (13708 bytes in 0.015s)
9 KB/s (9636 bytes in 1.000s)
972 KB/s (93396 bytes in 0.093s)

Pushing over!
Press any key to continue . . .

C:\Software\htc\ROMs\DATA2SD\New Sibere>adb shell
~ # cd /system/bin
cd /system/bin
/system/bin # chmod 755 tune2fs
chmod 755 tune2fs
/system/bin # chmod 755 debugfs
chmod 755 debugfs
/system/bin # chmod 755 e2fsck
chmod 755 e2fsck
/system/bin # chmod 755 mke2fs
chmod 755 mke2fs
/system/bin # chmod 755 resize2fs
chmod 755 resize2fs
/system/bin # chown 0.2000 tune2fs
chown 0.2000 tune2fs
/system/bin # chown 0.2000 debugfs
chown 0.2000 debugfs
/system/bin # chown 0.2000 e2fsck
chown 0.2000 e2fsck
/system/bin # chown 0.2000 mke2fs
chown 0.2000 mke2fs
/system/bin # chown 0.2000 resize2fs
chown 0.2000 resize2fs
/system/bin # cd /system/lib
cd /system/lib
/system/lib # chmod 644 libext2fs.so
chmod 644 libext2fs.so
/system/lib # chmod 644 libext2_blkid.so
chmod 644 libext2_blkid.so
/system/lib # chmod 644 libext2_com_err.so
chmod 644 libext2_com_err.so
/system/lib # chmod 644 libext2_e2p.so
chmod 644 libext2_e2p.so
/system/lib # chmod 644 libext2_profile.so
chmod 644 libext2_profile.so
/system/lib # chmod 644 libext2_uuid.so
chmod 644 libext2_uuid.so
/system/lib # chmod 755 /system/xbin/busybox
chmod 755 /system/xbin/busybox
/system/lib # chown 0.0 /system/xbin/busybox
chown 0.0 /system/xbin/busybox
/system/lib # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
/system/lib # chown 0.0 /system/etc/init.d/01data
chown 0.0 /system/etc/init.d/01data
/system/lib # :> /system/etc/mtab
:> /system/etc/mtab
/system/lib # cd /
cd /
~ # /system/bin/mke2fs -T ext4 -b 4096 -E stride=64,stripe-width=64 -O ^has_jour
nal,extents,^huge_file -m 0 -L userdata /dev/block/mmcblk0p2
/system/bin/mke2fs -T ext4 -b 4096 -E stride=64,stripe-width=64 -O ^has_jour
nal,extents,^huge_file -m 0 -L userdata /dev/block/mmcblk0p2
mke2fs 1.41.3 (12-Oct-2008)
Filesystem label=userdata
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
44544 inodes, 178176 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=184549376
6 block groups
32768 blocks per group, 32768 fragments per group
7424 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # mkdir /sd
mkdir /sd
~ # /system/xbin/busybox mount -t ext4 /dev/block/mmcblk0p2 /sd
/system/xbin/busybox mount -t ext4 /dev/block/mmcblk0p2 /sd
~ # cd /data
cd /data
/data # cp -a * /sd
cp -a * /sd
/data # cd /
cd /
~ # sync
sync
~ # ls -l /sd
ls -l /sd
lrwxrwxrwx 1 root root 14 Jan 11 18:13 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 11 18:13 app-private -> /system/
sd/app-private
drwx------ 4 system system 4096 Jan 11 17:12 backup
lrwxrwxrwx 1 root root 23 Jan 11 18:13 dalvik-cache -> /system
/sd/dalvik-cache
drwxr-xr-x 155 root root 12288 Aug 1 2008 data
drwxr-x--- 2 root log 4096 Jan 11 17:10 dontpanic
lrwxrwxrwx 1 root root 11 Jan 11 18:13 drm -> /data/local
drwxrwx--x 4 shell shell 4096 Jan 11 17:10 local
drwxrwx--- 2 root root 16384 Jan 11 17:10 lost+found
drwxrwx--t 10 system misc 4096 Jan 11 17:10 misc
drwx------ 2 root root 4096 Jan 11 17:10 property
drwxrwxr-x 8 system system 4096 Jan 11 17:13 system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 211420 0 211420 0% /dev
/dev/block/mtdblock4 40960 1224 39736 3% /cache
/dev/block/mtdblock3 256000 229588 26412 90% /system
/dev/block/mtdblock5 151168 8528 142640 6% /data
/dev/block/mmcblk0p1 14828520 1973712 12854808 13% /sdcard
/dev/block/mmcblk0p2 701488 8820 692668 1% /sd

~ # cd /system/etc/init.d
cd /system/etc/init.d
/system/etc/init.d # ls
ls
01data 40a2sd fixsuperm
02cachedalvikcache 99complete
/system/etc/init.d # rm 40a2sd
rm 40a2sd
/system/etc/init.d # /system/xbin/busybox umount /sd
/system/xbin/busybox umount /sd
/system/etc/init.d # exit
exit

C:\Software\htc\ROMs\DATA2SD\New Sibere>

I guess it's probably b/c of a2sd version..Going to try the other one