From: "Steven smith" <sos22@cam.ac.uk>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: kaz <shigekazun@yahoo.co.jp>,
brianw@terrabox.com, Alvin Starr <alvin@iplink.net>,
Xen Devel Mailing List <xen-devel@lists.sourceforge.net>,
sos22@srcf.ucam.org
Subject: Re: Is it possible to Xenify a stock Redhat/Fedora kernel.
Date: Tue, 23 Nov 2004 16:55:42 +0000 [thread overview]
Message-ID: <20041123165542.GA1114@archibold> (raw)
In-Reply-To: <E1CWP40-00009a-00@mta1.cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
> > > I presume we'd need a Debian box to actually build the .deb's, or
> > > are there some simple tools we can just add to our FC2 box that
> > > does the nightly build?
> > I believe we need a debian box to generate debiaized packages nightly.
> It would certainly be easier if the tools could be made to run
> standalone, but I guess we could setup a Debian box if need be --
> it'll just be harder to integrate into the nightly build.
We don't actually need a Debian box for this. You see, there's
this really cool virtualisation software called Xen, and we might
be able to get away with doing it in a domain on top of that.
:)
Steven.
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2004-11-23 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 17:03 Is it possible to Xenify a stock Redhat/Fedora kernel Alvin Starr
2004-11-22 17:16 ` kaz
2004-11-22 19:10 ` Brian Wolfe
2004-11-23 0:10 ` kaz
2004-11-23 0:13 ` Brian Wolfe
2004-11-23 0:21 ` kaz
2004-11-23 0:20 ` Ian Pratt
2004-11-23 0:43 ` kaz
2004-11-23 1:01 ` Ian Pratt
2004-11-23 2:09 ` kaz
2004-11-23 16:46 ` Brian Wolfe
2004-11-23 18:11 ` kaz
2004-11-23 18:17 ` Brian Wolfe
2004-11-23 16:55 ` Steven smith [this message]
2004-11-23 7:46 ` Dariusz Pietrzak
2004-11-23 8:09 ` kaz
2004-11-23 16:43 ` Brian Wolfe
2004-11-27 1:46 ` Fran
2004-11-23 17:46 ` Rik van Riel
2004-11-23 18:05 ` JAmes Atwill
2004-11-25 21:43 ` Rik van Riel
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=20041123165542.GA1114@archibold \
--to=sos22@cam.ac.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=alvin@iplink.net \
--cc=brianw@terrabox.com \
--cc=shigekazun@yahoo.co.jp \
--cc=sos22@srcf.ucam.org \
--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.