maxnet / berryboot

Berryboot -- Boot menu / OS installer
http://www.berryboot.com/
Other
806 stars 133 forks source link

OverlayFS #440

Open kivutar opened 6 years ago

kivutar commented 6 years ago

Hello, I'm maintaining https://github.com/lakkatv/Lakka-LibreELEC and some of my users would like to use berryboot with my distro.

I think it boots properly, but uses its own kernel that lacks OverlayFS, which is a requirement for Lakka.

If it's the case, I have a collection of OverlayFS patches that you may want to include.

macmpi commented 6 years ago

@Kivutar berryboot does support overlay through aufs kernel extension. It's fairly similar to recent kernels' overlayfs, and it should work fine with Lakka, as it is with other similar distributions (LibreELEC, OpenELEC, Volumio2, etc...). I'll let @maxnet eventually comment on this.

I recently made few integration scripts to support some distributions' native functions such as updates/reset & al that are part of distributions init, and that berryboot can not support by default. My scripts bridge that. I have currently supported Volumio2 and LibreELEC (Kodi); you may have a look there. After a quick look at Lakka which leverages core LibreELEC system, I think I can very easily make scripts for Lakka.

macmpi commented 6 years ago

@Kivutar I indeed noticed few tmp-XXX-mount systemd mounts are choking at startup under berryboot.

We could probably fix that in my integration script that runs before berryboot composes it's own overlay. Are there other parts of the code dynamically tweaking overlays, or are those 5 systemd services the only ones?

kivutar commented 6 years ago

They are the only mount services using overlays. So it should be OK to tweak them. But they are contained in a squashfs.

macmpi commented 6 years ago

By default berryboot makes a rw overlay on top of /: so all squash hierarchy is visible and "modifiable".

I'm not sure about what those additional mounts achieve and how they are used at runtime. For instance, I could symlink each of these into their /usr/share/xxx counterparts, but I'm not sure that's really what you need.

I looked at / at runtime under ssh on a native image, and it did not seem those folders "contain" related /usr/share/xxx contents... They all seemed empty. Any guidance on what you need and how those are used is appreciated, so that I can construct proper folders or links within berryboot overlay context.

macmpi commented 6 years ago

@Kivutar I have added Lakka support in my berryboot-scripts. Feel free to test and point your users there.