From: quanstro@quanstro.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [Fwd: [olpc-software] Multi-protection VMAs and memory
Date: Fri, 12 May 2006 10:58:35 -0500 [thread overview]
Message-ID: <a0d2227bf72fca605cd4d30273443fb0@quanstro.net> (raw)
In-Reply-To: <4464ADB8.9080901@lanl.gov>
isn't wrong to blame shared libraries for this? don't misunderstand --- shared
libraries have plenty of drawbacks --- but this seems at first glance to be a problem with
the crossproduct of bloated applications and glibc badness?
and yes, things are getting kludgy.
- erik
> Just got this from the OLPC list. Another reason to love shared
> libaries. Are things getting kludgy here or what ...
>
>
next prev parent reply other threads:[~2006-05-12 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 15:46 [9fans] [Fwd: [olpc-software] Multi-protection VMAs and memory usage] Ronald G Minnich
2006-05-12 15:58 ` quanstro [this message]
2006-05-16 10:47 ` [9fans] [Fwd: [olpc-software] Multi-protection VMAs and memory Paweł Lasek
2006-05-16 16:59 ` LiteStar numnums
2006-05-12 16:23 ` [9fans] [Fwd: [olpc-software] Multi-protection VMAs and memory usage] David Leimbach
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=a0d2227bf72fca605cd4d30273443fb0@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).