[Pkg-xen-changes] r202 - trunk/xen-3.0/debian

[Guido Trotter]

Author: ultrotter
Date: Sat Jun 10 08:44:17 2006
New Revision: 202

Modified:
   trunk/xen-3.0/debian/xen-utils-3.0.README.Debian

Log:
Update xen-utils-3.0.README.Debian on /lib/tls. Keeping anyway a reference to
the "old way" for sarge systems, at least until etch is released. This goes
towards fixing #372524, for which an update about kernels is needed (I'm going
to write it later today)


Modified: trunk/xen-3.0/debian/xen-utils-3.0.README.Debian
==============================================================================
--- trunk/xen-3.0/debian/xen-utils-3.0.README.Debian	(original)
+++ trunk/xen-3.0/debian/xen-utils-3.0.README.Debian	Sat Jun 10 08:44:17 2006
@@ -6,7 +6,11 @@
    Since Xen guest machines have to work in non-contiguous areas of memory,
    they cannot support a segmented glibc efficiently.  If your glibc is
    segmented Xen will have to emulate the support, with a high performance
-   penalty. To solve this problem you just have to execute this command:
+   penalty. Luckily the Debian GLibc Team has agreed to provide a non-segmented
+   version to be used with xen, which is available in the libc6-xen package,
+   recommended by this one. Should this package be not available for you (eg.
+   because you are using xen on Debian 3.1 - sarge) you can work around the
+   segmentation issue by just executing this command:
 
    mv /lib/tls /lib/tls.disabled
 
@@ -19,9 +23,9 @@
    rm -rf /lib/tls.disabled
    mv /lib/tls /lib/tls.disabled
 
-   again. We'll be working towards a better solution, but for now this is it.
-   Please remember to always keep your system tls disabled.
-
+   again. This of course is not necessary if you use the provided libc6-xen
+   package, which of course is the recommended course of action whenever
+   possible.  Anyway please remember to always keep your system tls disabled.
 
 * About the kernel: