On Tue, Dec 30, 2014 at 12:22 PM, Antti Kantee <[email protected]> wrote: >> The mem/ directory has an example - add an image.tar file and it will >> make a standalone executable that when run will untar the tarfile that >> is linked into its binary. This runs on linux/netbsd7/rumprun-posix >> fine and will populate the root fs, and should be trivial to add into >> a Xen/baremetal image, just remove main() and call extract() after >> rump_init(). > > What's the envisioned end-user usage? Ideally I guess you'd specify > something like TARBALL=tarball.tgz when you build your rumprun image, > and that would take care of everything. But it's not obvious to me > where the TARBALL=foo info should be specified. Related: we still > didn't figure out what to do with crunchgen.
I just tidied it up a little, but annoyingly you cant specify the name of the objects for ld --format-binary, so currently it expects the tarfile to be called image.tar. Then link image.tar.obj and untar.o into your application and call the entrypoint (as main.c does). Easiest way to test it out is use rumprun-posix - you can just set CC=rump-cc and run make and untar.c will untar what you put in image.tar into your rump kernel. Patches welcome. Justin ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
