Originally, I just stated that opium needs a couple of simple changes to make all the Unix stuff optional (none of it is essential). But it looks like I was misinformed about the status of core_kernel.
On February 13, 2016 at 9:16:53 AM, Ashish Agarwal ([email protected]) wrote: Rudi, can you explain further. Do you mean that core_kernel currently doesn't support mirage but that some minor fixes will make it mirage compatible? On Fri, Feb 12, 2016 at 6:15 PM, <[email protected]> wrote: The last real obstacle was core_kernel. At this point there’s some minor obstacles remaining to make sure some Unix specific bits are factored well enough (e.g. Cmdliner/file serving). Cheers, Rudi. On February 12, 2016 at 6:13:43 PM, Sean Grove ([email protected]) wrote: When you say that Opium isn't ready for Mirage, is there an issue tracking what's outstanding? I was hoping to use it in a Mirage starter-project for a workshop next month. On Fri, Feb 12, 2016 at 2:05 PM, Sven Anderson <[email protected]> wrote: Hi, I’d like to write a simple REST-API (the typical HTTP/json stuff). Opium is not yet ready for mirage, and I’m not sure about webmachine, neither if it’s ready for mirage, nor if it is maybe overkill for a small API with 5 to 10 nodes. So I want to ask in this list, what is the recommendation for implementing a REST API on mirage today? Thanks in advance and best regards, Sven _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
