On Sun, Apr 23, 2017 at 4:23 PM, Rick Payne (Offshore) <ri...@rossfell.co.uk > wrote:
> > > On 23 Apr 2017, at 05:14, Nadav Har'El <n...@scylladb.com> wrote: > > > > Pekka, another question we should ask ourselves is what is the plan with > Capstan, and more importantly, the binary OSv releases. The OSv v0.24 > version he used is two years old (!). If we're not going to produce any > more pre-compiled releases (are we?) should we at least remove the antique > ones and force people to compile OSv on their own before using Capstan? Or > should we make another release? Or what? > > On this front, I have a rebar_osv plugin for the erlang ‘rebar’ build tool > that will take an erlang release and build an OSv image. Its simpler to > port an erlang OTP application to OSv that way than using the apps/erlang > setup. It will also include a recent OSv base image (as I use the same > method of CPIO-ing in the files). Hope to release that soon - are you ok > with me including an OSv base image? > Yes. However note that I think that Capstan's notion of "base image" is misdirected. The Capstan "base image" is an image with a particular size (e.g., 10 GB) plus the OSv kernel and some collection of "default" files. If you want a 100 MB or 100 GB image instead, you're out of luck. What I think is a better approach is to take separatey the OSv kernel with just cpiod.so and mkfs.so (i.e., take build/release/loader.img) and the files, and compose the image with the size you want and uploading the files you want to it. This is more-or-less what the Mikelangelo project's fork of Capstan is doing. Maybe that's what you are also planning to do? Nadav. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
