From: Antoine Martin <antoine@nagafix.co.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: TLS support - status - need for re-testing
Date: Thu, 23 Mar 2006 11:29:34 +0000 [thread overview]
Message-ID: <1143113374.17079.6.camel@localhost> (raw)
In-Reply-To: <200603230317.48384.blaisorblade@yahoo.it>
> Has anyone got success or failure with TLS code on 32-bit machines on 64-bit
> hosts?
I believe FC4 and FC5 x86 still fail with tls errors during fsck. Not
sure why. (images on my site)
All the other images were completely rebuilt in the last 2 months and
none of them have had their /lib/tls moved out of the way, so I assume
that glibc uses tls and all these images seem to work fine.
> More important: has anyone tested that?
I thought i had... but maybe not.
Antoine
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-23 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 2:17 [uml-devel] TLS support - status - need for re-testing Blaisorblade
2006-03-23 11:29 ` Antoine Martin [this message]
2006-03-23 21:14 ` [uml-devel] " Jeff Dike
2006-03-23 23:44 ` Blaisorblade
2006-03-24 1:51 ` Jeff Dike
2006-03-24 10:39 ` Antoine Martin
2006-03-24 11:44 ` Blaisorblade
2006-03-24 11:43 ` Blaisorblade
2006-03-24 4:17 ` Jeff Dike
2006-03-24 11:43 ` Blaisorblade
2006-03-24 17:32 ` Jeff Dike
2006-03-24 18:44 ` Blaisorblade
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=1143113374.17079.6.camel@localhost \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox