Looks like you got this working just fine
. Likely, you'd blocked the terminal emulator in superuser, and didn't notice. That can happen. If not, maybe it just got screwed up. Either way, as you guys were discussing, a2sd check will tell you your current set up. If you want to verify manually, run these commands from the terminal:
ls -l -d /data/app
ls -l -d /data/app-private
ls -l -d /data/dalvik-cache
If you see the name of the dir with a "->" after it, and another directory named either /system/sd or /sd-ext, with app, app-private, or dalvik-cache (depending on which one you ran the command for), then it worked. A2sd basically just copies your apps to the sdcard, then creates a symlink (shortcut) from where the system thinks apps should be to where you actually moved the apps. You're basically fooling the phone into thinking apps are on internal storage when they really aren't. This is completely different from builtin apps2sd, which moves only portions of apps to /sdcard/.anrdoid_secure. Yes, you can use them both at the same time, but it's pointless, and a waste of space. I do usually keep an apps2sd app around, though, just to make sure apps *don't* get moved via that method. Beyond that, since you moved the actual directory where apps are installed, all apps will reside and be installed on the sdcard, now. Just one more quick note - technically speaking, depending on the speed of your sdcard, the purpose of moving dalvik to /cache rather than the sdcard is that it might be a little faster. Since /cache is *basically* unusable space (sorta) you can use it with no impact on your usable space (/data). If you have a fast sdcard, it's a moot point.
