From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Christopher Faylor <me@cgf.cx>
Subject: Re: [uml-devel] NPTL status?
Date: Sat, 10 Sep 2005 16:19:38 +0200 [thread overview]
Message-ID: <200509101619.38922.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050909162442.GA11934@trixie.casa.cgf.cx>
On Friday 09 September 2005 18:24, Christopher Faylor wrote:
> As I understand it NPTL support in UML is still a work in progress. Is
> this correct? If so, is there an experimental patch set which works
> better with NPTL
Yes, but I'd really underline _experimental_.
> and might allow things like RHEL4 to boot
> out-of-the-box?
Basically, no. At least nothing you'd rely onto.
There is something like that, but it doesn't work very well yet.
If you browse my website, in the patches directory:
http://www.user-mode-linux.org/~blaisorblade/patches/devel-guest/
there are some test trees which include TLS support code.
It depends - at this stage, because of the difference between distros (glibc
version mainly), with the same code I can see one behaviour (say "nothing
works") and somebody else have no problem.
My Debian Sarge appears to be very picky, while Jeff, with more or less the
same patches, has FC4 working "well enough" (there are still some spurious
segfaults, however).
And Sébastien Dugué tried LinuxFromScratch 6.1 with glibc 2.3.5 and it worked
well - but I think LFS is not a heavy stress tool for NPTL.
> I am currently using a 2.6.12 guest kernel with RH9 rootfs and have
> moved things around in /lib so as to avoid problems with NPTL but
> I was hoping that there might be some improvements which would allow
> me to use later versions of glibc without modification.
RH9 is entirely different - that wouldn't even work with a plain 2.6 kernel on
i386, I think.
In fact, I've seen some early NPTL code on Ingo Molnar's site and it isn't at
all compatible with current API. So RH9's NPTL will never be supported.
> Is this possible?
> cgf
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-09-10 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 16:24 [uml-devel] NPTL status? Christopher Faylor
2005-09-10 14:19 ` Blaisorblade [this message]
2005-09-10 18:18 ` Christopher Faylor
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=200509101619.38922.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=me@cgf.cx \
--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