While moving from ED-on-SD to swap-on-sd:ED-on-EMMC, as a rule of thumb, I would not expect *as much* improvement in performance, as with moving from image file to dedicated partition. Yet, if You're still using swap on eMMC, by moving it to microSD You're going to feel overall increase in performance for *whole* device, so it's definitely worth the effort. Especially, if You'll also add to this customization of few swap related settings.

In Your situation, as a quick&dirty improvement, I would just "cut" 768 MB from microSd fat32, and create swap there (so, use both Ed and swap on microSD). When time permits, and You'll be able to "clean" some thing on eMMC, You can always "kick" Your dedicated partition into eMMC.

Thanks, but it wouldn't be possible without sulu messing with dist-upgrade and it complications (I could not fix pulseaudio etc issues in thousand of years...) and of course, qole bringing us ED and easy chroot as whole, on first place.

Anyway, no worries. Image that I've uploaded is (well, at least *should*) be independent of any "personal" tweaks in .chroot and .xbindkeysrc. Also, image was mkfs'ed as ext3, so it can be used by people without kernel-power as well, while still regaining possibility to mount is as ext4 - yet, keep in mind, that some 'special' ext4 benefits aren't available when doing so, see wikipedia article about ext filesystem. I concluded, that people using ext4 will be (most likely) sitting on dedicated partition anyway, so they can copy content of image file to any filesystem they feel fancy.

Nice catch. Well, I'm pretty sure that it wont work if You want to repartition Ed partition from it but I'm sure You know it already. I would also not risk repartitioning that include /home + opt (/dev/mmcblk0p2) - remember, we're still in chroot, so AIUI, it would be almost like repartitioning ED from within ED.

On the other hand, I don't see much reason, why we shouldn't be able to cut&slize /dev/mmcblk0p1 (MyDocs), or MicroSD as a whole. Just be sure, that it doesn't involve moving/resizing mentioned /home/ + opt. Also, be sure to disable swap on microSD, before messing with SD.

Repartitioning with GUI independant from other device would be great, but for full solution, we would need some thing like u-boot loading kernel from microSD + ArchLinux from microSD. Doable, yet I think no one tried this up to date.

/Estel

// Edit

As You all have probably noticed, the file I uploaded is image packed as .lzma - just like any other ED image files. You need to unpack it first (can be done via tar -xf --lzma <file>) - warning, on device, it's prone to same things, that haunted images provided by qole, i.e. device can get unresponsive during unpacking. In my case - using swap on microSD and tweaked settings, there is no such problem - it unpacks gracefully, and device is 100% responsive during unpacking (yet, unpacking takes 100% of CPU, so other programs aren't blazing fast), but in other setup's it may be better to first unpack it on other machine. AFAIK, it's safe to do so under any OS - may be even windoze + 7zip (unpacked image file won't suffer due to windows filesystems not handling permissions - for the same reasons, image file can be held on MyDocs).

While unpacking on device - no matter of setup - it may be good to do it with nice command, so (for example) 'nice 19 tar -xf --lzma ed-squeeze-final.ext3.lzma' - of course, if You already cd'ed to directory, where You want to see unpacked image.
---

After un-lzma'ing, image can be used directly with ED (just remember, to change 'ext2' to 'ext3' in /home/user/.chroot). It's content can be also moved to dedicated partition - to do so, just trivially mount image somewhere ('mount -o loop <imagefile> <mounpoint>), and 'cp -a' it's content to desired place (dedicated partition). Then, modify /home/user/.chroot, to make it point to Your dedicated partition, instead of image file.
---

When qole will review my questions about files from /home/user/, and image will be confirmed to working fine for few brave folks testing it, I'll land on ED installation, as "first" choice. I've also prepared .desktop files for Maemo (to easy launch LibreOffice or Chromium), so maybe I'll be also time for small update of package - if not, .desktop files can be also downloaded separately.