The best thing is to disable eMMC swap completely via /sbin/swapoff <location of emmc swap>, but anyway, good find. If it's done on point, when no data is written to swpa at all, it shouldn't make any difference in booting time. Still, do we gain anything by it? If our script is screwed, we will end without swap = system still won't boot, like with screwed settings in rcS-late. Either way, recovery console (in any flavor, be it backupmenu's one or any other) is needed to fix that by hand (or via backup). I think it's similar effort to (via recovery console) "rm /etc/event.d/custom-screwed-script", and "cp /pah/to/rcS-late.backup /etc/event.d/rcS-late". In fact, when talking about practical side (bootable/unbootable), any script dealing with swap in such way is "critical" to the system. /Estel
The point was to speed up boot by streamlining the swap selection process (and avoid activating eMMC swap then swapping-off a few seconds later). It should be safe to throw in "if /lib/modules/current/ramzswap.ko insmod /lib/modules/current/ramzswap.ko disksize_kb=65536 swapon -p 5 /dev/ramzswap0" before MMC-device swap detection happens. However, I would strongly suggest testing out ramzswap options before putting it in. The results people are getting are wildly variable. If the pre-Fremantle guys say it's good, we need to get our kernel tunables just right (avoid everything getting put into ramzswap, and hitting swap+cpu hell, etc)