From: David Rhodus <sdrhodus@gmail.com>
To: Kip Macy <kmacy@fsmware.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
dfeustel@mindspring.com, xen-devel@lists.sourceforge.net
Subject: Re: Porting Xen
Date: Wed, 22 Dec 2004 23:31:56 +0000 [thread overview]
Message-ID: <fe77c96b0412221531c0e2671@mail.gmail.com> (raw)
In-Reply-To: <20041221194859.C10500@demos.bsdclusters.com>
On Tue, 21 Dec 2004 19:50:08 -0800 (PST), Kip Macy <kmacy@fsmware.com> wrote:
> >
> > Is OpenBSD closer to FreeBSD than NetBSD?
>
> It is a fork of NetBSD, but the FreeBSD port was completed more
> recently.
>
Is the code from the port going to be made public available ?
--
-David
Steven David Rhodus
<drhodus@machdep.com>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-22 23:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 2:38 Porting Xen Ian Pratt
2004-12-22 3:50 ` Kip Macy
2004-12-22 23:31 ` David Rhodus [this message]
2004-12-22 23:55 ` Kip Macy
2004-12-22 4:36 ` David Hopwood
2004-12-22 5:10 ` Adam Sulmicki
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 17:35 Carl Holtje ;021;vcsg6;
2005-01-05 14:18 ` aq
2005-01-05 14:25 ` Mark Williamson
2005-01-05 16:25 ` Dan Magenheimer
2004-12-22 5:01 Ian Pratt
2004-12-22 11:39 ` Dave Feustel
2004-12-22 11:43 ` Keir Fraser
2004-12-22 21:49 ` David Hopwood
2004-12-22 11:45 ` Dave Feustel
2004-12-22 13:13 ` Keir Fraser
2004-12-21 16:03 Dave Feustel
2004-12-21 19:19 ` Kip Macy
2004-12-21 19:32 ` Luciano Miguel Ferreira Rocha
2004-12-21 19:59 ` Dave Feustel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe77c96b0412221531c0e2671@mail.gmail.com \
--to=sdrhodus@gmail.com \
--cc=dfeustel@mindspring.com \
--cc=drhodus@machdep.com \
--cc=kmacy@fsmware.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.