From: Tupshin Harper <tupshin@tupshin.com>
To: Adam Heath <doogie@brainfood.com>
Cc: "xen-devel@lists.sourceforge.net" <xen-devel@lists.sourceforge.net>
Subject: Re: Re: xen 2.0.x and debian
Date: Sun, 06 Feb 2005 00:09:36 -0800 [thread overview]
Message-ID: <4205D0C0.7050000@tupshin.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0502060107530.5424@gradall.private.brainfood.com>
Adam Heath wrote:
>>Or if there are any specific Debian instructions for compiling the xen0
>>kernel that you could provide, that might help a lot!
>>
>>
>
>Apply the patch, either by hand, or by using make-kpkg to automatically apply
>it.
>
>
>
I agree that the burden of pre-compiled xen kernels isn't necessary.
What would be nice would be if make-kpkg worked with the --initrd
option, so that you could use it to create xen kernels and initrds that
would be as close as possible to standard prepackaged debian kernels.
When I tried make-kpkg --initrd, it didn't fail, but the resulting .deb
didn't install an initrd for the kernel either.
-Tupshin
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-02-06 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 3:16 xen 2.0.x and debian Tom Hibbert
2005-02-02 14:47 ` Nuutti Kotivuori
2005-02-05 7:57 ` Adam Heath
2005-02-05 20:01 ` Adam Heath
2005-02-05 22:24 ` Mark Williamson
2005-02-06 0:31 ` Adam Heath
2005-02-06 6:34 ` Travis Newman
2005-02-06 7:11 ` Adam Heath
2005-02-06 8:09 ` Tupshin Harper [this message]
2005-02-06 8:11 ` Adam Heath
2005-02-06 10:31 ` Mark Williamson
2005-02-06 6:54 ` Tupshin Harper
2005-02-06 7:07 ` Adam Heath
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=4205D0C0.7050000@tupshin.com \
--to=tupshin@tupshin.com \
--cc=doogie@brainfood.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.