From 83d06c569c280324874460374f5b2ca3ebe63263 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Tue, 9 Sep 2003 10:02:31 +0000 Subject: Yet more trivial doc updates --- docs/uclibc.org/index.html | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'docs/uclibc.org/index.html') diff --git a/docs/uclibc.org/index.html b/docs/uclibc.org/index.html index 6d83c33a6..30b8703bc 100644 --- a/docs/uclibc.org/index.html +++ b/docs/uclibc.org/index.html @@ -47,14 +47,17 @@ uClibc. Porting applications from glibc to uClibc typically involves just recompiling the source code. uClibc even supports shared libraries and threading. It currently runs on standard Linux and MMU-less (also known as µClinux) -systems with support for alpha, ARM, i386, i960, h8300, m68k, mips/mipsel, +systems with support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors.

-If you are building an embedded Linux system and you find that glibc is -eating up too much space, you should consider using uClibc. If you are -building a huge fileserver with 12 Terabytes of storage, than using -glibc may be a better choice... +If you are building an embedded Linux system and you find that +glibc is eating up too much space, you should consider using +uClibc. If you are building a huge fileserver with 12 Terabytes +of storage, then using glibc may make more sense. Unless, for +example, that 12 Terabytes will be Network Attached Storage and +you plan to burn Linux into the system's firmware... +

uClibc is maintained by -- cgit v1.2.3