-
Notifications
You must be signed in to change notification settings - Fork 15
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
Look into splitting up container mounts intelligently #1
Comments
@pdsouza What about Overlay filesystem? Make root readonly, and add a directory in |
@utzcoz Oh wow, overlayfs looks very cool. This could solve our problem. Do you know if this is available on Android kernels? Do we need a minimum kernel version to support overlayfs? |
@pdsouza I have search |
Removing the "nosuid" flag from /data causes a SafetyNet failure. Therefore, an overlay solution is much appreciated. |
The Android 10 integrates |
@utzcoz This is great news. We still have the kernel requirements for I wonder if we can experiment with this in Android 9 too? I will be porting Maru up to Android 9 / LineageOS 16 soon. I think it will be sometime before Android 10 / LineageOS 17 is out and stable. But maybe we can experiment with Android 10 on pure AOSP with Pixel devices to prototype this. |
@pdsouza Okay, I can help test it with Android 10 on pure AOSP with Pixel(Sailfish). If I have some updates, I will post them to this issue to discuss. |
/ should be mounted on /system but we would need a way to get around the fact that it is "ro". This would be good since we wouldn't need to remove the "nosuid" flag from /data.
/home should be mounted on /data/media. This would make it easier for users to upgrade Maru without having to back up their desktop data. They could use TWRP factory reset and still preserve their desktop /home directory.
The text was updated successfully, but these errors were encountered: