From: Matthias Bethke <Matthias.Bethke@gmx.net>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] other *libc
Date: Fri, 14 Oct 2005 14:32:35 +0200 [thread overview]
Message-ID: <20051014123235.GA8961@huxley.linguistik.uni-erlangen.de> (raw)
In-Reply-To: <b18fbe3c050928080336fa91ed@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Hi Eduardo,
on Wednesday, 2005-09-28 at 15:03:13, you wrote:
> > How using other *libc will affect server performance (this is most important
> > question here)?
>
> YMMV, using dietlibc and uClibc only makes sense with embedded setups
Everybody I've talked to who has seen Fefe's Linux boxes (I haven't) was
very impressed by their speed, especially when booting. AFAIK he has
most of his software compiled with dietlibc, so it seems to make sense
even for servers.
regards
Matthias
--
I prefer encrypted and signed messages. KeyID: 90CF8389
Fingerprint: 8E1F 1081 A466 2946 B98A B9E2 099F 3B91
[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]
prev parent reply other threads:[~2005-10-14 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 14:20 [gentoo-server] other *libc Alex Efros
2005-09-28 15:03 ` Eduardo Tongson
2005-10-14 12:32 ` Matthias Bethke [this message]
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=20051014123235.GA8961@huxley.linguistik.uni-erlangen.de \
--to=matthias.bethke@gmx.net \
--cc=gentoo-server@lists.gentoo.org \
/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