All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mikhail V.Paremski" <mparem@cisco.com>
To: xen-devel@lists.sourceforge.net
Cc: Kip Macy <kmacy@fsmware.com>
Subject: Re: Re: Where to get FreeBSD port for Xen
Date: Thu, 20 Jan 2005 09:00:55 -0800	[thread overview]
Message-ID: <200501200900.56564.mparem@cisco.com> (raw)
In-Reply-To: <20050119151721.Q35260@demos.bsdclusters.com>

Thanks Kip,

I'll wait.
BTW. Do Ypu hane any plans to run FreeBAD on dom0?

Cheers,
Mikhail.

On Wednesday 19 January 2005 03:18 pm, Kip Macy wrote:
> It looks like apache had gone out to lunch. I just restarted it and it
> is accessible again. If you wait a day I'll have 5.3 up. 5.2.1 is what
> is there right now.
>
>
> 			-Kip
>
> On Wed, 19 Jan 2005, Mikhail V.Paremski wrote:
> > Dear Kip,
> >
> > Recently I've tried to access to www.fsmware.com/xenofreebsd and
> > www.bsdclusters.com/xenofreebsd pages. Noone is responding. Is there any
> > way to get FreeBSD for Xen?
> >
> > Best regards,
> > Mikahil.
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  reply	other threads:[~2005-01-20 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200501191606.22899.mparem@cisco.com>
2005-01-19 23:18 ` Where to get FreeBSD port for Xen Kip Macy
2005-01-20 17:00   ` Mikhail V.Paremski [this message]
2005-01-20 21:52     ` Kip Macy
2005-01-21  0:18       ` David Rhodus
2005-01-21 22:23         ` Kip Macy
2005-01-24  0:39   ` Derrik Pates
2005-01-24  0:44     ` Kip Macy
2005-01-24  1:31     ` Kip Macy
2005-01-24  5:04       ` Derrik Pates
2005-01-24  6:15         ` Kip Macy
2005-01-24  6:18           ` Derrik Pates
2005-01-24  6:47             ` Kip Macy
2005-01-24 22:57               ` Derrik Pates
2005-01-24 23:03                 ` Kip Macy
2005-01-24 23:50                 ` Kip Macy
2005-01-25  0:27                   ` OpenBSD " Dave Feustel
2005-01-25  0:38                     ` Kip Macy
2005-01-25  1:02                       ` Dave Feustel
2005-01-25  1:05                         ` Kip Macy
2005-01-25 22:04                       ` Scott Parish
2005-01-25  0:53                   ` Re: Where to get FreeBSD " Derrik Pates
2005-01-24  2:25     ` Kip Macy
2005-01-24  9:01       ` Hidetoshi Shimokawa
2005-01-24 21:29         ` Kip Macy
2005-01-25  3:05           ` Hidetoshi Shimokawa
2005-01-25  4:09             ` Kip Macy
2005-01-25  4:40             ` 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=200501200900.56564.mparem@cisco.com \
    --to=mparem@cisco.com \
    --cc=kmacy@fsmware.com \
    --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.