From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Another amusing glibc day ...
Date: Fri, 4 Jan 2008 20:28:51 -0500 [thread overview]
Message-ID: <646ff839a4d2833721b02a7428038704@coraid.com> (raw)
In-Reply-To: <283f5df10801041707vcfd2d22x882f77ecb6992d1c@mail.gmail.com>
> well, uClibc & dietlibc are rather limited. *BSD libc is a viable option, as
> is Sun's.
> Honestly though, if we're going to do something as radical as get rid of
> glibc, can we please do a little better? Might as well fix everything else
> wrong, like, oh, say BSD SOCKETS!
> =)
sockets are not an invention of the c library, regardless of what drepper thinks.
you'll have to swap out the operating system to do that.
... wait a second.
- erik
next prev parent reply other threads:[~2008-01-05 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 1:42 ron minnich
2008-01-03 4:12 ` LiteStar numnums
2008-01-03 19:46 ` Roman Shaposhnik
2008-01-05 1:07 ` LiteStar numnums
2008-01-05 1:28 ` erik quanstrom [this message]
2008-01-05 1:33 ` LiteStar numnums
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=646ff839a4d2833721b02a7428038704@coraid.com \
--to=quanstro@coraid.com \
--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).