summaryrefslogtreecommitdiff
path: root/docs/uclibc.org
diff options
context:
space:
mode:
Diffstat (limited to 'docs/uclibc.org')
-rw-r--r--docs/uclibc.org/index.html31
1 files changed, 13 insertions, 18 deletions
diff --git a/docs/uclibc.org/index.html b/docs/uclibc.org/index.html
index fe7ae6a7c..20cc125fc 100644
--- a/docs/uclibc.org/index.html
+++ b/docs/uclibc.org/index.html
@@ -37,24 +37,19 @@
</TD></TR>
<TR><TD BGCOLOR="#eeeee0">
-
-<a href="http://uclibc.org">uClibc</a> (aka µClibc but pronounced
-yew-see-lib-see) is a C library for embedded Linux systems. It is much smaller
-then GNU libc, but nearly all applications supported by the
-<a href="http://www.gnu.org/software/libc/libc.html">GNU C Library (aka glibc)</a>
-also work perfectly with uClibc. Porting applications from
-glibc to uClibc typically involves just recompiling the source code. uClibc
-supports standard Linux systems (such as x86, strongArm, and powerpc), and also
-supports <a href="http://www.uclinux.org">MMU-less (also known as µClinux)</a>
-systems, such as those based on the Coldfire, dragonball, or arm7tdmi
-micro-controllers. If you are building an embedded Linux system, and you fine
-the GNU libc is eating up too much space, you should consider using uClibc
-instead. If you are working on an older system with limited memory (such as an
-oldworld Mac), uClibc may also be useful for you. If you are using a standard
-desktop Linux workstation to develop applications for an embedded Linux system,
-you can use run uClibc on your workstation while doing development. If you are
-trying to build a ultra fast fileserver for your company that has 12 Terabytes
-of storage, then you probably want to use glibc...
+<a href="http://uclibc.org">uClibc</a> (aka µClibc/pronounced yew-see-lib-see)
+is a C library for embedded Linux systems. It is much smaller then the
+<a href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>, but
+nearly all applications supported by the glibc also work perfectly with uClibc.
+Porting applications from glibc to uClibc typically involves just recompiling
+the source code. uClibc supports standard Linux systems (such as x86,
+strongArm, and powerpc), and also supports
+<a href="http://www.uclinux.org">MMU-less (also known as µClinux)</a> systems,
+such as those based on the Coldfire, dragonball, or arm7tdmi micro-controllers.
+If you are building an embedded Linux system and you find that glibc is
+eating up too much space, you should consider using uClibc instead. If you are
+building an ultra fast fileserver for your company with 12 Terabytes of
+storage, then you probably want to use glibc...
<p>