FAQ.html: dead links, wrong content-type

[Denis Vlasenko]

Hi,

I noticed by accident, that at http://www.uclibc.org/FAQ.html,
in this section:

====================================
Is a pre-compiled uClibc development system available?

If you want to be really lazy and start using uClibc right away
without needing to compile your own toolchain or anything, you
can grab a pre-compiled uClibc development system. These are
currently available for [arm], [armeb], [i386], [mips], [mipsel],
[powerpc], and [sh4].

These are bzip2 compressed ext2 filesystems containing all
the development software you need to build your own uClibc
applications, including: bash, awk, make, gcc, g++, autoconf,
automake, ncurses, zlib, openssl, openssh, gdb, strace, busybox,
GNU coreutils, GNU tar, GNU grep, etc.

Each of these uClibc development systems was created using
[buildroot], specifically, [buildroot.tar.bz2] along with
[these sources]. 
=====================================

First group of links, which point to root_fs_<arch>.ext2.bz2 files,
makes Firefox try to _display_ the files, not download them, because
content type implies "text":

HTTP/1.1 200 OK
Date: Fri, 16 Mar 2007 23:15:26 GMT
Server: Apache/2.2.3 (Debian) DAV/2 PHP/4.4.4-8 mod_ssl/2.2.3 OpenSSL/0.9.8c
Last-Modified: Wed, 12 Jan 2005 08:09:23 GMT
ETag: "1a1ea-1a36788-51b6f2c0"
Accept-Ranges: bytes
Content-Length: 27486088
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/plain; charset=UTF-8

In the last paragraph, [buildroot.tar.bz2] and [these sources] links are dead.
--
vda