[Samsung Galaxy Mini] stepph:
Let' make a plan:

ASSUMPTION:

What i know of link2sd on my GT-S5570 (mini/next/pop) is valid for other devices/roms

REQUIREMENTS :

1) we have a stock rom

2) we use LINK2SD with an EXT4 partition on external SDCARD

3) we wanto to start using DOC's mod

4) we cannot loose apps and their data, and don't want to use backup tools

PLAN:

1) uninstall Link2sd apps

2) remove link2sd startup-file, move the files as required.

options are:

2.a) adb shell commands - only ROOT

2.b) push script, execute it, remove it - only ROOT

2.c) update.zip - only for CWM, no ROOT

2.d) insert in DOC's init.data.sh - for all

3) Reboot and flash DOC's mod for your kernel.

4) Reboot and ... Enjoy !!!

Let's go first with OPTION A - an adb shell as root.

DEVELOPMENT of step 2 (Phase1 - Remove Link2sd traces)

Link2SD mount its partition using the file: /system/etc/install-recovery.sh

# cat /system/etc/install-recovery.sh
#!/system/bin/sh
[COLOR=red]#added by link2sd[/COLOR]
[COLOR=red]LOG=/data/link2sd-install-recovery.log[/COLOR]
[COLOR=red]echo "$(date) mounting..." > $LOG[/COLOR]
[COLOR=red]mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2 1>>$LOG 2>>$LOG[/COLOR]
[COLOR=red]mount -t ext4 -o rw /dev/block/mmcblk0p2 /data/sdext2 1>>$LOG 2>>$LOG[/COLOR]
[COLOR=red]mount >> $LOG[/COLOR]
[COLOR=red]echo "$(date) mount finished" >> $LOG[/COLOR]

if this is the file, we can delete it.

# rm /system/etc/install-recovery.sh

NOTE: in case the file is different - other tools may use this file - we should only remove the red lines.

In systems with kernel enabling init.d support may also exist the file: /system/etc/init.d/11link2sd,

similar to that above (different LOG filename). If it exist, this file has to be deleted.

# rm /system/etc/init.d/11link2sd

Also this LOG files has to be removed:

/data/link2sd-install-recovery.log

/data/link2sd-11link2sd.log

and I found the following ones too :

/data/link2sd-boot-receiver.log (from BootReceiverService.smali inside Link2SD)

/data/link2sd-debuggerd.log (where do those files come from ?)

# rm /data/link2sd-install-recovery.log
# rm /data/link2sd-11link2sd.log
# rm /data/link2sd-boot-receiver.log
# rm /data/link2sd-debuggerd.log

(note for future versions of the script: instead of deleting fixed files, deleted files pointed by LOG variable in scripts ?)

DEVELOPMENT of step 2 (Phase2 - remount /data/sd-ext2)

before going on, we should umount /data/sdext2

# fuser -k /data/sdext2
# umount /data/sdext2

...but it cannot work, so it is better if we reboot our device, then

open a new adb shell....

NOTE : here you cannot use linked apps !!!!

if some app is VERY important, please move it in internal memory.

!! if you test this 'alpha' PLEASE DO a backup !!

We should mount the ext4 partition somewhere :

# mkdir /sd-ext
# chmod 777 /sd-ext/
# chown root.root /sd-ext
# mount -t ext4 -o rw /dev/block/vold/179:2 /sd-ext

NOTE: the above may be not necessary in some custom rom...

DEVELOPMENT of step 2 (Phase3 - backup linked apks)

# mkdir /sd-ext/app.bak
# mv /sd-ext/*.apk /sd-ext/app.bak/
# mv /sd-ext/data /sd-ext/data.bak
# mv /sd-ext/dalvik-cache /sd-ext/dalvik-cache.bak

DEVELOPMENT of step 2 (Phase4 - copy original /data)

With a COPY instead of a MOVE, you could preserve apps on phone interal memory,

in case you have to boot the device without sdcard.

NOTE: this is also a 'safety gear' for some important apps - before testing !!!

# cp /data /sd-ext/

DEVELOPMENT of step 2 (Phase5 - replace linked apps with backupped ones )

so we should overwrite links with real files.

# mv /sd-ext/app.bak/* /sd-ext/app/
# mv /sd-ext/data.bak/* /sd-ext/data/
# mv /sd-ext/dalvik-cache.bak/* /sd-ext/dalvik-cache/

---------------------------------------------

Here it is !! or at least it should be....

Now we should be ready go on with point 3 and 4...

...And have Link2SD moved to new big 'internal' memory !

(I get no time to test it now, maybe next week....)