From: Christian Laursen <xi@borderworlds.dk>
To: mark.williamson@cl.cam.ac.uk
Cc: xen-devel@lists.sourceforge.net, Keichii Moto <keichiitoyota@yahoo.com>
Subject: Re: Xen FreeBSD port is available?
Date: 13 Oct 2004 16:00:32 +0200 [thread overview]
Message-ID: <86655esoov.fsf@borg.borderworlds.dk> (raw)
In-Reply-To: <200410131303.47792.mark.williamson@cl.cam.ac.uk>
"Mark A. Williamson" <mark.williamson@cl.cam.ac.uk> writes:
> > > NetBSD and FreeBSD as well. I can't find FreeBSD/xen
> > > source, where I can fetch it?
>
> I don't think the FreeBSD source is publically available, since the full port
> is still being finished off. Others on this list might know more details
> about this...
Okay.
It would be somewhat nice with a minimal status page somewhere so that people
can get an idea about it without having to ask here.
Just a suggestion of course.
I would very much like to help out with testing even before the port is
completely finished.
--
Christian Laursen
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-13 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 5:01 Xen FreeBSD port is available? Keichii Moto
2004-10-13 9:49 ` Christian Laursen
2004-10-13 12:03 ` Mark A. Williamson
2004-10-13 14:00 ` Christian Laursen [this message]
2004-10-14 9:52 ` Kip Macy
2004-10-14 14:25 ` Fred Clift
2004-10-14 20:37 ` Kip Macy
2004-10-14 15:05 ` Christian Laursen
2004-10-25 3:33 ` FreeBSD stable? was " Kip Macy
2004-10-26 7:50 ` Christian Laursen
2004-10-26 21:39 ` Kip Macy
2004-10-28 6:52 ` Keichii Moto
2004-10-14 15:23 ` Brian Wolfe
2004-10-14 20:35 ` Kip Macy
2004-10-13 23:38 ` Kip Macy
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=86655esoov.fsf@borg.borderworlds.dk \
--to=xi@borderworlds.dk \
--cc=keichiitoyota@yahoo.com \
--cc=mark.williamson@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.