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
---

I've found something that worry me - sudden of nothing, my device refuse to boot past 5 dots (no reboot loop, just stay with black screen and backlight on forever), unless I remove line:
...from rcS-late.

It's part of script, that check for existence of swaptype partition in place provided via config... I've idea how to make it more reliable, so i'll release fix in few days (I hope).

What is most strange, though, is that I could swear it worked for me yesterday, and it seems to work for all of You. Still, keep that in mind - if, by any chance, someone got hit by similar problem during boot, just open recovery console (via backupmenu, or any other flavor), mount rootfs, and comment out mentioned line in rcS-late. Unfortunately for me, I had to restore rootfs, until I repeated all steps and got hit by same thing again - only then I realized what is causing problems.

Well, it's -devel after all, and sometimes, packages turn on their creators, eh?

// Edit 2

BTW, out of complete curiosity, if someone got an idea why blkid -g executed from rcS-late makes whole booting process go limbo state, I would appreciate info.

/Estel