Re: [PATCH RFC 0/5] Split off mini-os to a separate tree

From: Martin Lucina <martin@lucina.net>
To: Thomas Leonard <talex5@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Anil Madhavapeddy <anil@recoil.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, pooka@iki.fi, quan.xu@intel.com,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	dgdegra@tycho.nsa.gov
Subject: Re: [PATCH RFC 0/5] Split off mini-os to a separate tree
Date: Mon, 26 Jan 2015 18:42:11 +0100	[thread overview]
Message-ID: <20150126174211.GB5686@nodbug.moloch.sk> (raw)
In-Reply-To: <CAG4opy-FXEx2envK3ELswJrj+i_JCbMrXS50krZKGY5i8qiFNw@mail.gmail.com>

talex5@gmail.com said:
> In case it's useful: for the standalone version of Mini-OS used by
> Mirage, I had to include these directories too:
> 
> 1. xen/include/public
> 2. xen/common/libfdt
> 3. xen/include/xen/libfdt
> 4. config
> 
> ( https://github.com/talex5/xen/tree/minios-releases )

Ah, so that's where the Mirage fork of Mini-OS lives. I knew there was one,
but not where. Any other forks please speak up :-)

Which parts of Mini-OS does Mirage actually use? I know you have an OCaml
implementation of netfront, for instance.

> Will there be a separate mailing list for Mini-OS? That would be very
> useful for people who don't want to keep up with xen-devel.

+1

It would be useful to coordinate work. We (Rump Kernels) have also done a
bunch of changes to our fork [1], including ongoing work on namespacing
Mini-OS APIs (see [2] in case you missed it).

Martin

[1] https://github.com/rumpkernel/rumprun-xen/tree/master/xen
[2] http://thread.gmane.org/gmane.comp.rumpkernel.user/581