From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Antoine Martin <antoine@nagafix.co.uk>,
Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [uml-devel] tls: set_thread_area failed
Date: Sun, 11 Dec 2005 00:34:43 -0600 [thread overview]
Message-ID: <200512110034.43397.rob@landley.net> (raw)
In-Reply-To: <1134153592.29209.2.camel@localhost.localdomain>
On Friday 09 December 2005 12:39, Antoine Martin wrote:
> > > Is this glibc? Any ideas?
> >
> > Yes, I see that on Debian Sarge too. Don't ask me why fsck uses thread,
> > but it seems to do that.
>
> I wasn't even thinking about that! So true, why on earth would fsck
> require threading!?
fsck -A does all filesystems in fstab in one run, and the single case
apparently defaults to one thread.
I didn't say it was a good design... :)
Rob
--
Steve Ballmer: Innovation! Inigo Montoya: You keep using that word.
I do not think it means what you think it means.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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-12-11 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 2:13 [uml-devel] tls: set_thread_area failed Antoine Martin
2005-12-09 17:52 ` Blaisorblade
2005-12-09 18:39 ` Antoine Martin
2005-12-10 14:26 ` Blaisorblade
2005-12-10 16:31 ` Antoine Martin
2005-12-11 6:34 ` Rob Landley [this message]
2005-12-11 16:01 ` Blaisorblade
2005-12-13 22:45 ` Nix
2005-12-14 3:05 ` [uml-devel] " Sven Köhler
2005-12-14 12:21 ` 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=200512110034.43397.rob@landley.net \
--to=rob@landley.net \
--cc=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--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.