View Single Post
Posts: 2,292 | Thanked: 4,135 times | Joined on Apr 2010 @ UK
#130
Originally Posted by mr_pingu View Post
Said short: Set it up once, never bother anymore, it just works. That's why I prefer ereswap over FlopSwap.. Besides I dont have 3 swap partitions. However the way FlopSwap goes, is cleaner than Ereswap's way...
FlopSwap can be intrgated into cron/alarmd to run on a schedule if required. It's covered in the wiki.
I prefer to run everything on the card to reduce flash wear as I have said before.
While I agree FlopSwap is more restrictive in some ways (swap locations), it is designed to install and remove cleanly with no residue like applications IMO should.

This also makes it more user friendly hence the GUI, not a command tool like ereswap. Many beginners can utilise swap on SD with minimal knowledge using FlopSwap.

This is why I made FlopSwap instead of a GUI for ereswap.

Originally Posted by Estel View Post
It's true, that adding separate script on /etc/event.d/ is "cleaner", in a way that it have less chances or messing something up
Agreed hence my design.

Originally Posted by Estel View Post
Hoever, without modifying rcS_late, we have situation, where one script enables regular swap on eMMC, and another one disables it, just a moment later. It makes booting a little longer due to unnecessary operation being performed (although, in practice, it's hardly-to-non noticeable), but most importantly, just don't match my aesthetic, and can create problems, if one decide to go without any eMMC swap, at all.
Change in boottime is milliseconds.
FlopSwap is not designed to work with no device SD.
The device SD can be swapped to, so the back cover can be removed. Not everyone has modifed the magnet on the back cover.

Originally Posted by Estel View Post
That's why I've decided to go with the way of sed-modifying rcS-late, which was paincfully more hard to write, than just adding another script to /etc/event.d/, especially, that they way sed command was written, tries to be compatible with modified rcS-late's, too (unless the very swap lines vere touched, but in that case, one wouldn't need ereswap, probably).
This is were modifing rcs-late can cause problems, and would cause a boot loop if rcs-late fails.
If the extra event.d file fails it would be ignored and booting should continue on device swap.

Originally Posted by Estel View Post
After all, we have major respected packages touching boot-critical script - including things from CSSU - so why should we restrain ourselves
CSSU fair enough, these are"system" updates, but IMO applications shouldn't just start modifing root and adding files everywhere. This is how root starts to get full of unremovable rubbish, for people that have NFC.

At the end of the day it's nice to have options.
Both do the same thing and both have there place.
__________________

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -


Before posting or starting a thread please try this.
 

The Following 2 Users Say Thank You to sixwheeledbeast For This Useful Post: