From 7037f0609e5350ac2c785fedd2c94c29a6b73bfd Mon Sep 17 00:00:00 2001
From: Eric Andersen
Date: Thu, 11 Dec 2003 07:16:11 +0000
Subject: Rework the website
---
docs/uclibc.org/FAQ.html | 332 +++++---------
docs/uclibc.org/cvs_anon.html | 185 +-------
docs/uclibc.org/cvs_howto.html | 44 ++
docs/uclibc.org/cvs_write.html | 91 +---
docs/uclibc.org/download.html | 32 ++
docs/uclibc.org/footer.html | 18 +
docs/uclibc.org/header.html | 80 ++++
docs/uclibc.org/index.html | 508 +++------------------
docs/uclibc.org/lists.html | 45 ++
docs/uclibc.org/news.html | 124 +++++
docs/uclibc.org/old-news.html | 988 ----------------------------------------
docs/uclibc.org/oldnews.html | 887 ++++++++++++++++++++++++++++++++++++
docs/uclibc.org/other_libs.html | 24 +
docs/uclibc.org/products.html | 27 ++
docs/uclibc.org/robots.txt | 2 -
docs/uclibc.org/toolchains.html | 52 +++
16 files changed, 1529 insertions(+), 1910 deletions(-)
create mode 100644 docs/uclibc.org/cvs_howto.html
create mode 100644 docs/uclibc.org/download.html
create mode 100644 docs/uclibc.org/footer.html
create mode 100644 docs/uclibc.org/header.html
create mode 100644 docs/uclibc.org/lists.html
create mode 100644 docs/uclibc.org/news.html
delete mode 100644 docs/uclibc.org/old-news.html
create mode 100644 docs/uclibc.org/oldnews.html
create mode 100644 docs/uclibc.org/other_libs.html
create mode 100644 docs/uclibc.org/products.html
delete mode 100644 docs/uclibc.org/robots.txt
create mode 100644 docs/uclibc.org/toolchains.html
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html
index 98f1b94aa..70dd14366 100644
--- a/docs/uclibc.org/FAQ.html
+++ b/docs/uclibc.org/FAQ.html
@@ -1,69 +1,49 @@
-
+
-
-
- uClibc FAQ-- a C library for embedded systems
-
-
+Frequently Asked Questions
-
-
-
-
-
-
-
-
-
-
- µ C l i b c
-
- |
-
-
-
-
-
-
-
-
-
-
-
- uClibc Frequently Asked Questions (FAQ)
-
-
- |
-
-
-
-This is a collection of some of the frequently asked questions
+This is a collection of some of the most frequently asked questions
about uClibc. Some of the questions even have answers. If you
have additions to this FAQ document, we would love to add them,
-
-When you are done, you can click here to return
-to the uClibc home page.
+
+ - Why is it called uClibc?
+
- What platforms does uClibc run on?
+
- Why are you doing this? What's wrong with glibc?
+
- So uClibc is smaller then glibc? Doesn't that mean it
+ completely sucks? How could it be smaller and not suck?
+
- Why should I use uClibc?
+
- If I use uClibc, do I have to release all my source code to the world for
+ free? I want to create a closed source commercial application and I want
+ to protect my intellectual property.
+
- Can I use it on my x86 development system?
+
- Does uClibc support shared libraries?
+
+
- How do I compile programs with uClibc?
+
- Why do I keep getting "sh: can't access tty; job control
+ turned off" errors? Why doesn't Control-C work within my shell?
+
- How do I make autoconf and automake behave?
+
- When I run 'ldd' to get a list of the library dependencies
+ for a uClibc binary, ldd segfaults! What should I do?
+
- Why does localtime() return times in UTC even when I have my timezone set?
+
- What is the history of uClibc? Where did it come from?
+
- I demand that you to add <favorite feature> right now! How come
+ you don't answer all my questions on the mailing list instantly? I demand
+ that you help me with all of my problems Right Now!
+
- I need you to add <favorite feature>! Are the uClibc developers willing to
+ be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide
+ support contracts?
+
- I think you guys are great and I want to help support your work!
+
+
+
+
+
+
- |
-
- What platforms does uClibc run on?
-
- |
-
-
- Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300,
- m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors.
-
-
+
- |
-
- Why is it called uClibc?
-
- |
-
The letter 'u' is short for µ (the greek letter "mu"). µ is commonly used
as the abbreviation for the word "micro". The capital "C" is short for
@@ -77,13 +57,20 @@ to the uClibc home page.
ARM7TDMI. These days, uClibc also works just fine on normal Linux systems
(such as i386, ARM, and PowerPC), but we couldn't think of a better name.
+
+
+
+
+
+
+ Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300,
+ m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors.
+
+
+
+
+
- |
-
- Why are you doing this? What's wrong with glibc?
-
- |
-
Initially, the project began since the GNU C library lacked support for
MMU-less systems, and because glibc is very large. The GNU C library is
@@ -100,14 +87,12 @@ to the uClibc home page.
+
+
+
+
- |
-
- So uClibc is smaller then glibc? Doesn't that mean it completely sucks?
- How could it be smaller and not suck?
-
- |
-
uClibc and glibc have different goals. glibc strives for features
and performance, and is targeted for desktops and servers with
@@ -152,13 +137,10 @@ to the uClibc home page.
+
+
+
- |
-
- Why should I use uClibc?
-
- |
-
I don't know if you should use uClibc or not. It depends on your needs.
If you are building an embedded Linux system and you are tight on space, then
@@ -175,15 +157,12 @@ to the uClibc home page.
+
+
+
- |
-
- If I use uClibc, do I have to release all my source code to the world for
- free? I want to create a closed source commercial application and I want
- to protect my intellectual property.
-
- |
-
No, you do not need to give away your application source code just because
you use uClibc and/or run on Linux. uClibc is licensed under the
those you gave the fully linked application.
+
+
+
-
-
- Can I use it on my x86 development system?
-
- |
-
Sure! In fact, this can be very nice during development. By
installing uClibc on your development system, you can be sure that
@@ -225,13 +201,10 @@ to the uClibc home page.
+
+
+
- |
-
- Does uClibc support shared libraries?
-
- |
-
Yes. uClibc has native shared library support on i386, ARM, mips,
SH, CRIS, and PowerPC processors. Other architectures can use shared
@@ -243,13 +216,10 @@ to the uClibc home page.
shared library support they may be able to help.
+
+
+
- |
-
- How do I compile programs with uClibc?
-
- |
-
You will need to have your own uClibc toolchain (i.e. GNU binutils and
gcc configured to produce binaries linked with uClibc).
@@ -281,14 +251,12 @@ to the uClibc home page.
and use resize2fs to make them fill a partition... Whatever works best for
you.
+
+
+
+
- |
-
- Why do I keep getting "sh: can't access tty; job control turned off" errors?
- Why doesn't Control-C work within my shell?
-
- |
-
This isn't really a uClibc question, but I'll answer it here anyways. Job
control will be turned off since your shell can not obtain a controlling
@@ -302,13 +270,10 @@ to the uClibc home page.
run your shell on a real console...
+
+
+
- |
-
- How do I make autoconf and automake behave?
-
- |
-
When you are cross-compiling, autoconf and automake are known to behave
badly. This is because a large number of configure scripts (such as the
@@ -319,14 +284,11 @@ to the uClibc home page.
configure scripts.
+
+
+
- |
-
- When I run 'ldd' to get a list of the library dependencies for a uClibc
- binary, ldd segfaults! What should I do?
-
- |
-
Use the ldd that is built by uClibc, not your system's one. When your
system's ldd looks for library dependencies, it actually _runs_ that
@@ -338,13 +300,10 @@ to the uClibc home page.
cross compiling.
+
+
+
- |
-
- Why does localtime() return times in UTC even when I have my timezone set?
-
- |
-
The uClibc time functions get timezone information from the TZ environment
@@ -359,13 +318,11 @@ to the uClibc home page.
automagically use the specified setting.
+
- |
-
- What is the history of uClibc? Where did it come from?
-
- |
-
+
+
+
The history and origin of uClibc is long and twisty.
In the beginning, there was GNU libc. Then, libc4
@@ -421,15 +378,12 @@ to the uClibc home page.
+
+
+
- |
-
- I demand that you to add <favorite feature> right now! How come
- you don't answer all my questions on the mailing list instantly? I demand
- that you help me with all of my problems Right Now!
-
- |
-
You have not paid us a single cent and yet you still have the
product of several years of work from Erik and Manuel and
@@ -438,15 +392,14 @@ to the uClibc home page.
ignore you.
+
+
+
+
+
- |
-
- I need you to add <favorite feature>! Are the uClibc developers willing to
- be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide
- support contracts?
-
- |
-
Sure! Now you have our attention! What you should do is contact Erik Andersen of
are several other active uClibc contributors who will almost certainly be able
to help you out. Erik can contact them and ask them about their availability.
-
+
+
+
+
-
-
- I think you guys are great and I want to help support your work!
-
- |
-
Wow, that would be great! You can click here to help support uClibc and/or request features.
@@ -483,70 +433,8 @@ to the uClibc home page.
support requests, etc., you can contact
CodePoet Consulting here.
-
- |
-
- Ok, I'm done reading all this stuff.
-
- |
-
-
-Well then, click here to return to the uClibc home page.
-
-
-
-
-
- |
- | |
-
-
-
-
-
-
-
+
-
-
-
+
-
-
diff --git a/docs/uclibc.org/cvs_anon.html b/docs/uclibc.org/cvs_anon.html
index 388626f39..e5ed5b80a 100644
--- a/docs/uclibc.org/cvs_anon.html
+++ b/docs/uclibc.org/cvs_anon.html
@@ -1,46 +1,16 @@
-
+
-
-
-uClibc Anonymous CVS Instructions
-
-
-
-
-
-
-Accessing the uClibc CVS Repository
-
-
-
-
-
-
- u C l i b c
-
- |
-
-
-
-
-
-
-
-
-
- Anonymous CVS
-
- |
-
+Anonymous CVS
We allow anonymous (read-only) CVS access to everyone. The first command you
need to run for anonymous CVS access is:
cvs -d:pserver:anonymous@uclibc.org:/var/cvs login
-CVS will prompt you for a password. Just press Enter. This step only
-needs to be done once, the first time you attempt to access CVS.
+CVS will prompt you for a password. Just press the Enter key (there is no
+password for anonymous access). This step only needs to be done once, the first
+time you attempt to access CVS.
Once the login is complete, you can then check the list of available
CVS modules by running the following command (all on one line):
@@ -50,12 +20,16 @@ cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -c
If you wish, you can then check out a local copy of any of the
available modules. The following is an example of how to grab
-a copy of the uClibc source code:
+a copy of uClibc:
cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc
This will create a directory called uClibc in the current
-directory which contains the latest and greatest source code for
-uClibc.
+directory. This directory will contain the latest and greatest source
+code for uClibc.
+
+
+If you are not already familiar with using CVS, I recommend you visit
+this quick Introduction to CVS.
I usually create a ~/.cvsrc file with the following things in it, and I
@@ -76,137 +50,8 @@ cvs update
Because you've only been granted anonymous access to the tree, you won't be
able to commit any changes. Changes can be submitted for inclusion by posting
-them to the appropriate mailing list.
-
-
-
- |
-
-
-
-
-
-
-
- How to use CVS
-
- |
-
-
-
-If you want to know all the gory details, you will want to visit
-the CVS main web page.
-For the impatient, the following is probably about all you need to know:
-
-
-
- cvs checkout -c
- - Will list the modules available for checkout
-
cvs checkout < module name >
- - Will checkout the named module
-
cvs co < module name >
- - Same thing
-
cvs update
-
- - Updates your local archive so it is in sync with the repository
- -- your local updates are left intact. Tries to merge upstream updates
- into your local updates. You will see the following tags when it is
- updating your local repository: C means conflict, U means update,
- P means patched, and M means modified.
-
cvs up
- - Same thing
-
cvs update < file name >
- - Same thing but for just the named file(s)/directory(s).
-
cvs commit
- - Will check in all your work.
-
cvs add < file name >
-
- - Adds the named file/directory into CVS
-
cvs remove < file name >
- - Removes the named file/directory from the upstream repository.
-
cvs rm < file name >
- - Same thing
-
cvs log < file name >
-
- - Gives you the complete version history of what has happened to the named file(s).
- Along with all tags, all commit messages, etc...
-
cvs status < file name >
- - Gives you the current version number of the file(s) in question.
-
cvs tag TAGNAME
- - Tags the versions of everything in the repository with the TAGNAME label.
-
cvs tag TAGNAME < file name >
- - Tags the named file(s) in the repository with the TAGNAME label.
-
cvs diff
-
- - Gives you the difference between the local repository and the upstream repository.
-
cvs diff < file name >
- - Same but for the named file(s).
-
cvs diff -r 1.5 < file name >
- - Same but gives you the difference between the named file(s) and
- version 1.5 of the named file(s).
-
cvs diff -r TAGNAME < file name >
-
- - Same but gives you the difference between the named file(s) and the
- of the file tagged TAGNAME in the upstream repository.
-
cvs rdiff -r TAGNAME module
- - Gives you a diff (that you can actually use with patch) between the current
- version of module and the specified tagged version.
-
cvs import < directory to import > < name for new module > start
- - Add a new module into the CVS archive.
-
-
-
-
-
-
- |
-
-
-
-
-
-
-
-
-
-
-
+them to the appropriate mailing list. For those that are actively contributing
+CVS write access can be made available.
+
diff --git a/docs/uclibc.org/cvs_howto.html b/docs/uclibc.org/cvs_howto.html
new file mode 100644
index 000000000..cff3a353c
--- /dev/null
+++ b/docs/uclibc.org/cvs_howto.html
@@ -0,0 +1,44 @@
+
+
+
+How to use CVS
+
+
+If you want to know all the gory details, you will want to visit
+the CVS main web page.
+For the impatient, the following is probably about all you need to know:
+
+
+
+ cvs checkout -c
+ - Will list the modules available for checkout
+
cvs checkout < module name >
+ - Will checkout the named module
+
cvs co < module name >
+ - Same thing
+
cvs update
+
+ - Updates your local archive so it is in sync with the repository
+ -- your local updates are left intact. Tries to merge upstream updates
+ into your local updates. You will see the following tags when it is
+ updating your local repository: C means conflict, U means update,
+ P means patched, and M means modified.
+
cvs up
+ - Same thing
+
cvs update < file name >
+ - Same thing but for just the named file(s)/directory(s).
+
cvs commit
+ - Will check in all your work.
+
cvs add < file name >
+
+ - Adds the named file/directory into CVS
+
cvs remove < file name >
+ - Removes the named file/directory from the upstream repository.
+
cvs rm < file name >
+ - Same thing
+
cvs log < file name >
+
+
+
+
+
diff --git a/docs/uclibc.org/cvs_write.html b/docs/uclibc.org/cvs_write.html
index 6a75138c1..f7c642f7d 100644
--- a/docs/uclibc.org/cvs_write.html
+++ b/docs/uclibc.org/cvs_write.html
@@ -1,39 +1,7 @@
-
+
-
-
-uClibc CVS Read/Write Instructions
-
-
-
-
-
-
-
-Accessing the uClibc CVS Repository
-
-
-
-
-
-
- u C l i b c
-
- |
-
-
-
-
-
-
-
-
-
- CVS Read/Write Access
-
- |
-
+CVS Read/Write Access
If you want to be able to commit things to CVS, first contribute some
stuff to show you are serious. Then, very nicely ask
@@ -41,7 +9,7 @@ stuff to show you are serious. Then, very nicely ask
an account. To access CVS, you will want to add the following to set up your environment:
$ export CVS_RSH=/usr/bin/ssh
-$ export CVSROOT='username@cvs.uclibc.org:/var/cvs'
+$ export CVSROOT='username@cvs.busybox.net:/var/cvs'
It goes without saying you must change username to your own
username...
@@ -59,57 +27,6 @@ Note that if you would prefer to keep your communications with me
private, you can encrypt your email using my
public key.
-
-
-
- |
-
-
-
-
-
-
-
-
-
-
-
-
+
diff --git a/docs/uclibc.org/download.html b/docs/uclibc.org/download.html
new file mode 100644
index 000000000..cf888fc2f
--- /dev/null
+++ b/docs/uclibc.org/download.html
@@ -0,0 +1,32 @@
+
+
+
+
+Download
+
+Source for the latest release can always be
+downloaded from http://www.uclibc.org/downloads
+
+
+You can also obtain Daily Snapshots of
+the latest CVS source tree for those wishing to follow uClibc development,
+but cannot or do not wish to use CVS.
+
+
+
+
+
+
+
diff --git a/docs/uclibc.org/footer.html b/docs/uclibc.org/footer.html
new file mode 100644
index 000000000..0c7adb18a
--- /dev/null
+++ b/docs/uclibc.org/footer.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+
+
+
+
+ Copyright © 1999-2003 Erik Andersen
+
+ Mail all comments, insults, suggestions and bribes to
+
+ Erik Andersen andersen@codepoet.org
+
+
+