-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preparing as secondary #1
base: master
Are you sure you want to change the base?
Conversation
The main reason sailfish doesn't boot as a secondary is the lack of finding it's original /system of cm12.1. Sailfish wasn't meant for a secondary ROM. So what it does on boot is always mounting mmcblk0p23 via system.mount. That block however, always contains /system of the primary ROM. For the mismatch of expected and found /system, HAL doesn't get initialized in the way it should, and that's why we got no change from the splash screen when we boot exactly the same sailfish as secondary. That's why we're tweaking the way Sailfish mounts /system here. MultiROM also, is made for an universal /system configuration. Not the chroot type config Sailfish uses. So it always mounts the secondary ROMs /system to the root /system. We're binding those two and deleting */system.mount's for the sake of booting as a secondary ROM.
I don't think these files belong here. It could be either directly written to /boot. |
It's required for MultiROM at boot up. Everything happens after, happens after this script has run. And i just edited the script and added the fstab. You can't do anything before MR finds fstab and run main_init. So technically, these files are needed at /boot. |
That's correct but what I meantsay to was that these files do not belong here. They belong in my droid-config-wt88047 repository. The sparse folder there represents the root folder of sailfish. |
Telling you after a boot to it. |
/dev/mmcblk0p30 on / type ext4 (rw,noatime,data=ordered) |
No description provided.