From: Pavel Machek <pavel@ucw.cz>
To: Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>
Cc: Josh Triplett <josh@joshtriplett.org>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Jon Bernard <jbernard@debian.org>, Jan Blunck <jblunck@suse.de>,
Pierre Habouzit <madcoder@debian.org>,
Steven Munroe <munroesj@linux.vnet.ibm.com>,
Bert Wesarg <bert.wesarg@googlemail.com>,
ltt-dev@lists.casi.polymtl.ca, rp@svcs.cs.pdx.edu,
linux-kernel@vger.kernel.org
Subject: Re: Userspace RCU 0.2.3
Date: Sat, 17 Oct 2009 19:16:15 +0200 [thread overview]
Message-ID: <20091017171615.GD1526@ucw.cz> (raw)
In-Reply-To: <4AD75EA6.8080809@polymtl.ca>
On Thu 2009-10-15 13:40:54, Pierre-Marc Fournier wrote:
> Josh Triplett wrote:
> >
> > Even Debian has given up on real 386 systems at this point, primarily
> > because system libraries like glibc have; 486 and better represents the
> > bare minimum required at this point. I don't know of any distributions
> > supporting real 386 systems at this point, and doing so would represent
> > a major undertaking.
> >
>
> What about embedded systems? Anyone know if some 386 chips, perhaps even
> in smp configurations, are still in use in those?
smp 386: definitely not.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-18 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 22:36 Userspace RCU 0.2.3 Mathieu Desnoyers
2009-10-15 0:02 ` Paul E. McKenney
2009-10-15 2:39 ` Mathieu Desnoyers
2009-10-15 4:34 ` Paul E. McKenney
2009-10-15 9:00 ` Josh Triplett
2009-10-15 17:40 ` Pierre-Marc Fournier
2009-10-17 17:16 ` Pavel Machek [this message]
2009-10-18 22:02 ` [rp] " Mathieu Desnoyers
2009-10-18 22:52 ` Pavel Machek
2009-10-18 23:16 ` [ltt-dev] " Mathieu Desnoyers
2009-10-19 23:59 ` Userspace RCU 0.2.4 Mathieu Desnoyers
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=20091017171615.GD1526@ucw.cz \
--to=pavel@ucw.cz \
--cc=bert.wesarg@googlemail.com \
--cc=compudj@krystal.dyndns.org \
--cc=jbernard@debian.org \
--cc=jblunck@suse.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=madcoder@debian.org \
--cc=munroesj@linux.vnet.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pierre-marc.fournier@polymtl.ca \
--cc=rp@svcs.cs.pdx.edu \
/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