From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Brian Hays" Subject: 3.0.2 kernels Date: Fri, 7 Apr 2006 20:21:47 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1842564257==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1842564257== Content-Type: multipart/alternative; boundary="----=_Part_8960_632427.1144455707827" ------=_Part_8960_632427.1144455707827 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I've noticed that when executing "make kernels" in the 3.0.2 tree separate "xen0" and "xenU" are no longer created. Is this by design? Is there a way to have both kernels built when executing make dist? Thank you, Brian ------=_Part_8960_632427.1144455707827 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I've noticed that when executing "make kernels" in the 3.0.2 tree= separate "xen0" and "xenU" are no longer created. Is t= his by design? Is there a way to have both kernels built when executing mak= e dist?

Thank you,
Brian
------=_Part_8960_632427.1144455707827-- --===============1842564257== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1842564257==--