Well I do believe we have been over this but I will refresh some memory. The link for the cache is in the data partition and not the cache partition.
I know about that symlink, and that doesn't matter here. See below.
Hence if one loads up with enough apps that will shrink the amount of space for the cache to perform.
Not really, and certainly not in
this case. The user's problem seems to have been caused by him skipping the repartition (or a wipe data/factory reset) step between different ROM installs; and not by the ROM not "enjoying sitting" on a 2048/0 partition setup (whatever that means). Even on a 2048 MB
/data partition, his ROM install would've succeeded for these reasons:
1. A repartition operation will clear
/data, so there will be plenty of space when the ROM is installed.
2.
/cache/dalvik-cache is used, as far I know, only by the apps or jar files installed in
/system. Every other installed app will put its dalvik cache files in
/data/dalvik-cache. And, system apps will populate
/cache/dalvik-cache (or whereever that points to) only in two instances: when the ROM is freshly installed, or after the
/cache has been wiped. This means that once the .dex files are in place, no more writing is done to
/cache/dalvik-cache.
3. The amount of space used by all the dalvik files is small since only files in
/system/app,
/system/framework, ... are cached there. I would be surprised if
/cache/dalvik-cache exceeded 50-70 MB on
any ROM. This means that even on a 2048 MB
/data partiition, you would have to
massively fill the disk for the effects like you imagine to even be seen. In actuality, (see point #2 above), you'll almost never see a full
/data partition causing problems with creating files in
/cache/dalvik-cache even if that was just a symlink into some directory inside
/data.
4. If
/data were indeed full, then you would start seeing other problems (like a failure to install apps outright) far before any problems writing into
/cache/dalvik-cache.
Since 4096 is the highest we can currently go, unless jumping to the new DRH setup, ...
A max of 4GB for
/data is only a CWM limitation. And you can
very easily enlarge it further while keeping all your existing data intact.
...we will always see this issue.
See point #3. This is
almost never going to cause problems.
I know one can link the cache back just by changing a couple of lines in the ramdisk, but I am working on a different method and just hoping that it will work the way it is setup in my head.
The symlink method is only
one way to use a non-standard directory for the system dalvik-cache. I know of 2 more techniques to do the same thing; and if you'd sent me the config files like I'd you to, I could've told you which method was being used and how to change it. You have to actively add stuff to change the default location for the system dalvik-cache location; if you remove those additions, the standard location will be used. Ie. there's no need to complicate this any more using more non-standard changes.