From: kaz <shigekazun@yahoo.co.jp>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: brianw@terrabox.com, Alvin Starr <alvin@iplink.net>,
Xen Devel Mailing List <xen-devel@lists.sourceforge.net>
Subject: Re: Is it possible to Xenify a stock Redhat/Fedora kernel.
Date: Tue, 23 Nov 2004 09:43:52 +0900 [thread overview]
Message-ID: <41A287C8.5010409@yahoo.co.jp> (raw)
In-Reply-To: <E1CWOPc-00080l-00@mta1.cl.cam.ac.uk>
Ian Pratt wrote:
>
> Should we be adding a bunch of .deb targets to our top-level
> Makefiles, or is it more gory than that? Can the existing
> buildconfigs stuff be adapted for building custom debian kernels?
Currently there are a lot modification between genuine Xen-2.0.1's
Makefile and debiaized version of Makefile.
But I believe we can modify it for both .deb and .rpm nightly build.
> 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.
> I'd like to see us building .deb's and .rpm's nightly -- the
> current install.sh stuff is far from ideal (though actually seems
> to work remarkably well on all modern distros).
Yes, agreed definitely.
If official Xen project to offer deb's repo, I am very happy to upload
Xen 2.0.1 debianized packages to the repo and maintain them til Xen-2.0
official debian packages to be released.
thanks & regards,
--
kaz
-------------------------------------------------------
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-11-23 0:43 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 [this message]
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
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=41A287C8.5010409@yahoo.co.jp \
--to=shigekazun@yahoo.co.jp \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=alvin@iplink.net \
--cc=brianw@terrabox.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.