We have moved to a new Sailfish OS Forum. Please start new discussions there.
9

[XA2 Plus] overlayFS support missing in the kernel [XA2] [SailfishX]

asked 2019-04-10 23:06:41 +0300

micuintus gravatar image

updated 2019-04-12 12:11:11 +0300

overlayFS support is not available in the Sailfish OS kernel.

Either compiling it into the kernel or allowing installing it as a kernel module via pkcon would be extremely helpful for making the use of the whole aliendalvik Android subsystem way more flexible.

See https://together.jolla.com/question/202862/provide-option-to-mount-the-system-partition-rootfs-for-aliendalvik-rewritable-xperia-xa2-xa2-plus-android-81/

edit retag flag offensive close delete

Comments

2

Note that, on the XA2, modules are not disabled. So until Jolla does this, it is possible to compile your own modules.

DrYak ( 2019-04-11 15:23:43 +0300 )edit
1

Also another added benefit :

  • XA2 has containers available in the kernel (well obvious as that's what the new LXC-based Alien Dalvik relies on)

  • if somebody adds OverlayFS, it becomes possible to run docker without needing to reformated BTRFS partitions.

DrYak ( 2019-04-11 16:16:28 +0300 )edit

Note that, on the XA2, modules are not disabled. So until Jolla does this, it is possible to compile your own modules.

Good point. TBH, I just shy away from the effort of finding the right kernel version, the right tool chain, etc. :) So if Jolla did it, it would be way more convenient. But yes, that's the coolness about FOSS: If the vendor doesn't help you, you can help yourself ;).

micuintus ( 2019-04-12 12:02:57 +0300 )edit

On the smartphone, uname -a telle me:

Linux Sailfish 4.4.172 #1 SMP PREEMPT Wed Feb 13 06:03:28 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

Which you can easily retrieve from the official kernel.org repository (it's not that much outdated, actually) (And I doube any extra patches from Qualcomm, Sony or Jolla would influence the drivers we're interested in).

The current configuration of the kernel can be found on the phone inside /proc/config.gz

For the tool chain we've got several alternatives :

Now what remains to be done:

  • find the correct list of arcane commands needed to get ONLY the desired module to compile and not the whole shebang... (My kernel-fu is a bit rusty, but there's a sequence of specific targets like make kerlenversion scripts prepare etc. that would only compile the desired parts instead of make all)
  • for the specific case of making RPMs (e.g. using the OBS service), wrap then the instructions into a SPEC file and build the RPM itself.

It this last part that is going to take an afternoon of hacking.

DrYak ( 2019-04-12 17:26:48 +0300 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2019-04-13 05:02:04 +0300

Thaodan gravatar image

You can fill a bug at mer.bugtracker/bugtracker.sailfishos.org and make a pr at github. Enabling that feature as a module by default would do no harm I think.

edit flag offensive delete publish link more

Comments

Do you mean https://git.merproject.org and https://bugs.merproject.org/ but where are is the kernel repo/project in this gitlab?

bomo ( 2019-04-13 10:53:48 +0300 )edit
1

I mean the bugtracker. Eg the first link and than submit a PR for the bug.

Thaodan ( 2019-04-14 03:05:06 +0300 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2019-04-10 23:06:41 +0300

Seen: 423 times

Last updated: Apr 13 '19