All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: "La Monte H.P. Yarroll" <piggy@timesys.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML running on host-kernel 2.6.0 with NPTL-enabled glibc problem
Date: Fri, 09 Jan 2004 13:39:52 +0000	[thread overview]
Message-ID: <3FFEAF28.8000707@vgertech.com> (raw)
In-Reply-To: <3FFEACBC.7060704@timesys.com>



La Monte H.P. Yarroll wrote:
> 
> Going back through your posting it looks like it probably does not 
> matter if the host kernel
> implements TLS as long as libc does not use NTPL.  Is this a correct 
> interpretation?
> 

The host kernel runs UML fine... UML doesn't run only when system's 
glibc has nptl+tls support.

This same kernel runs UML with the same glibc, compiled without nptl+tls 
support.

So, I can only assume that's nptl :)

Regards,
Nuno Silva



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-01-09 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09  9:09 [uml-devel] UML running on host-kernel 2.6.0 with NPTL-enabled glibc problem Nuno Silva
2004-01-09 13:19 ` La Monte H.P. Yarroll
2004-01-09 13:29   ` La Monte H.P. Yarroll
2004-01-09 13:39     ` Nuno Silva [this message]
2004-01-09 13:35   ` Nuno Silva
2004-01-10 20:25 ` Oleg Drokin
2004-01-11 10:49   ` BlaisorBlade
2004-01-11 18:28     ` Oleg Drokin
2004-01-12  3:49   ` Nuno Silva

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=3FFEAF28.8000707@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --cc=piggy@timesys.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 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.