Skip to content
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

Open
pdsouza opened this issue May 20, 2017 · 7 comments
Open

Look into splitting up container mounts intelligently #1

pdsouza opened this issue May 20, 2017 · 7 comments

Comments

@pdsouza
Copy link
Member

pdsouza commented May 20, 2017

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

@utzcoz
Copy link
Member

utzcoz commented Oct 26, 2018

@pdsouza What about Overlay filesystem? Make root readonly, and add a directory in /data/media or /data/overlayfs to overlay the root directory of desktop. After that, all modification of desktop will saved in /data. With /data/media, all modification of user will stored in /data for a better experience to upgrade Maru. I have saw some system doing similar things.

@pdsouza
Copy link
Member Author

pdsouza commented Oct 27, 2018

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

@utzcoz
Copy link
Member

utzcoz commented Oct 29, 2018

@pdsouza I have search overlayfs in nexus 5x's kernel code, but there doesn't have some result about overlayfs. Sorry.

@meiser79
Copy link

meiser79 commented Jul 22, 2019

Removing the "nosuid" flag from /data causes a SafetyNet failure. Therefore, an overlay solution is much appreciated.

@utzcoz
Copy link
Member

utzcoz commented Sep 6, 2019

The Android 10 integrates Overlayfs to Android official.

  1. Android Overlayfs integration with adb remount
  2. Android 10 Release notes - Overlayfs

@pdsouza
Copy link
Member Author

pdsouza commented Sep 6, 2019

@utzcoz This is great news. We still have the kernel requirements for overlayfs so I guess we can only use this approach with modern kernels (3.18+). The legacy devices like N5 will have to continue to use nosuid unless overlayfs can be backported. But this is a great approach for all new devices.

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.

@utzcoz
Copy link
Member

utzcoz commented Sep 7, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants