From: Kip Macy <kip.macy@gmail.com>
To: Nils Toedtmann <xen-devel@nils.toedtmann.net>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: freebsd kernel
Date: Fri, 15 Apr 2005 09:36:11 -0700 [thread overview]
Message-ID: <b1fa29170504150936303f1527@mail.gmail.com> (raw)
In-Reply-To: <1113557309.5467.21.camel@crusher.takatukaland.de>
I do.
http://www.fsmware.com/xenofreebsd/5.3/xen-2.0-testing/050415/kernel
This isn't from the mainline tree (it has some local modifications).
Nonetheless, it should work just fine. I ran it last night against
yesterday's -testing. I've done kernel builds and basic tasks on it.
Get in touch with me directly if there are further issues.
-Kip
On 4/15/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote:
> Am Donnerstag, den 14.04.2005, 21:49 -0700 schrieb Kip Macy:
> > You probably don't have the mental bandwidth to run it right now, but
> > just in case I've put it at:
> > http://www.fsmware.com/xenofreebsd/5.3/050414/kernel
> >
> > I've just pulled a fresh tree and am doing a make world just in case
> > there is something wrong with my tree from March 22nd.
>
> I run the freebsd kernel from the 2.0.5 demo iso. It boots but trying to
> "make" anything results in segfaults or amoking kernel (so i cannot
> build a new kernel - it's a chicken-egg problem). As some of my domUs
> are productive i run 2.0-testing, so i cannot use your -unstable
> kernels. A friend of mine (freebsd-addicted) will build me a recent
> xen-2.0 kernel when he has time.
>
> Or do you accidentaly have a recent kernel for xen-2 hanging around ...?
>
> /nils.
>
>
next prev parent reply other threads:[~2005-04-15 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 4:49 freebsd kernel Kip Macy
2005-04-15 9:28 ` Nils Toedtmann
2005-04-15 16:36 ` Kip Macy [this message]
2005-04-16 9:04 ` Nils Toedtmann
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=b1fa29170504150936303f1527@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-devel@nils.toedtmann.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.