* Kir Kolyshkin <k...@openvz.org> wrote: > It's pretty simple. What OpenVZ kernel does it creates a container and > runs /sbin/init inside it. What goes next is up to that particular > /sbin/init. If you need to run an app let /sbin/init run just it, or let > this app be /sbin/init (but bear in mind there will be no child reaper > as in usual linux system so you might need to take some extra care about > zombie processes).
ACK. The probably easiest way is to take some minimal OS image, so you also get a shell, libc, and essential setups (mounting /proc and /sys), etc. You'll most likely also need some little setup stuff to let your app communicate with the outside world (eg. routing, filesystem access, etc). Doing this all completely on your own takes a lot of more efforts, but makes a good learning project :) Some time ago (left it aside due lack of time), I've been working on an kind of nano-distro for such use-cases, built with my Briegel buildsystem (it crosscompiles tiny images which only include the really essential stuff) . If you're really interested, I'd dig it out again. cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- _______________________________________________ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users