xen-devel

[Top] [All Lists]

[Xen-devel] ARCH=xen

from [James Harper]

[Permanent Link][Original]

To:	"Xen Devel Mailing List" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] ARCH=xen
From:	"James Harper" <JamesH@xxxxxxxxxxxxxxxx>
Date:	Sun, 12 Dec 2004 16:45:20 +1100
Delivery-date:	Sun, 12 Dec 2004 05:40:16 +0000
Envelope-to:	xen+James.Bulpin@xxxxxxxxxxxx
List-archive:	<http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help:	<mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id:	List for Xen developers <xen-devel.lists.sourceforge.net>
List-post:	<mailto:xen-devel@lists.sourceforge.net>
List-subscribe:	<https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe:	<https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender:	xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index:	AcTgDcRg04Yr1pn8TtOQimruS/H5Dw==
Thread-topic:	ARCH=xen

Is there a way to get the system to know it’s architecture is xen (so that compiles etc “just work”), even though it is sort of really i386 (so that userland config just “just works”)? I guess this really isn’t possible or it would have been done, but it would nice if, eg once official debian packages are produced, the system would be ARCH=xen so that the right kernel gets installed, but that it knows that i386 binary’s are compatible so there doesn’t have to exist a whole new architecture for userland.

James

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] ARCH=xen, James Harper <=

Previous by Date:	[Xen-devel] debian, James Harper
Next by Date:	[Xen-devel] Problem when making a domain, aq
Previous by Thread:	[Xen-devel] debian, James Harper
Next by Thread:	[Xen-devel] Problem when making a domain, aq
Indexes:	[Date] [Thread] [Top] [All Lists]