LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

add a discussion item, ispell, render on sid, ready to publish

This commit is contained in:
appaji 2004-03-23 14:55:18 +00:00
parent 1a4bd4dd62
commit 32b2a8633c
1 changed files with 24 additions and 58 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

82
LDP/ldpwn/20040324.xml
View File

@ -15,14 +15,12 @@
<title>New documents @ TLDP</title> <title>New documents @ TLDP</title>
<para>Tabatha completed the review of Kai Schlachter's <ulink url="http://tldp.org/HOWTO/Glibc-Install-HOWTO/">Glibc Installation HOWTO</ulink>, which details the installation of a new glibc version on a Linux system. Kai decided to write this documentation after having struggled with the subject without finding a decent overview of tasks to perform.</para> <para>Tabatha completed the review of Kai Schlachter's <ulink
</sect1> url="http://tldp.org/HOWTO/Glibc-Install-HOWTO/">Glibc Installation
HOWTO</ulink>, which details the installation of a new glibc version on
<sect1 id="new-for-review"> a Linux system. Kai decided to write this documentation after having
struggled with the subject and finding no good documentation with an
<title>Documents submitted for review</title> overview of the tasks to perform.</para>
<para>All submissions have been processed.</para>
</sect1> </sect1>
<sect1 id="updated-docs"> <sect1 id="updated-docs">
@ -30,63 +28,30 @@
<itemizedlist> <itemizedlist>
<listitem><para>The <ulink url="http://tldp.org/HOWTO/Linux+IPv6-HOWTO/">Linux IPv6 HOWTO</ulink> v0.46 by Peter Bieringer features minor updates and corrections and more links to external resources.</para></listitem> <listitem><para>The <ulink
url="http://tldp.org/HOWTO/Linux+IPv6-HOWTO/">Linux IPv6 HOWTO</ulink>
<listitem><para>.</para></listitem> v0.46 by Peter Bieringer features minor updates and corrections and more
links to external resources.</para></listitem>
<listitem><para>.</para></listitem>
</itemizedlist> </itemizedlist>
</sect1> </sect1>
<sect1 id="tldp-world">
<title>News in The LDP world</title>
<sect2 id="news-item1">
<title>News item 1</title>
<para>.</para>
</sect2>
<sect2 id="news-item2">
<title>News item 2</title>
<para>.</para>
</sect2>
<sect2 id="news-item3">
<title>News item 3</title>
<para>.</para>
</sect2>
</sect1>
<sect1 id="discussions"> <sect1 id="discussions">
<title>Discussions on TLDP lists</title> <title>Discussions on TLDP lists</title>
<sect2 id="discussion1"> <sect2 id="discussion1">
<title>Discussion topic 1</title> <title>TLDP Mirrors</title>
<para>.</para> <para>In <ulink
url="http://lists.tldp.org/index.cgi?1:mss:6821:200403:icjmgahabpdlipbhobhb">response</ulink>
</sect2> to Tille's post indicating a map of The LDP mirrors, Saqib Ali suggested
that we have an automatic redirector based on the IP address of the
<sect2 id="discussion2"> client machine. Various people <ulink
<title>Discussion topic 2</title> url="http://lists.tldp.org/index.cgi?1:mss:6826:200403:ehngfbpnepphojhokgdn">disagreed</ulink>
with reasons and suggested <ulink
<para>.</para> url="http://lists.tldp.org/index.cgi?1:mss:6835:200403:ifhbolfhjihbhnkaanhb">alternative
methods</ulink> of handling traffic. </para>
</sect2>
<sect2 id="discussion3">
<title>Discussion topic 3</title>
<para>.</para>
</sect2> </sect2>
@ -95,7 +60,7 @@
<sect1 id="interview"> <sect1 id="interview">
<title>Interview with Fred Stutzman</title> <title>Interview with Fred Stutzman</title>
<figure> <figure>
<title>Fred Stutzman, leader of our iBiblio support team.</title> <title>Fred Stutzman, leader of iBiblio/TLDP support team.</title>
<mediaobject> <mediaobject>
<imageobject> <imageobject>
<imagedata fileref="fred.eps" format="EPS" /> <imagedata fileref="fred.eps" format="EPS" />
@ -117,7 +82,8 @@ Nevertheless, Fred is very important to us: he manages, with his colleagues, the
TLDP servers at iBiblio. He is going to tell us about the hardware and network TLDP servers at iBiblio. He is going to tell us about the hardware and network
resources you need if you want to start a TLDP-like project.</para> resources you need if you want to start a TLDP-like project.</para>
<para><emphasis>Q: Do we eat a lot of bandwidth? And the mirrors? What connection (uplink) do you have for all this? <para><emphasis>Q: Do we eat a lot of bandwidth? And the mirrors? What
connection (uplink) do you have for all this?</emphasis></para>
<para>A: Does TLDP use a lot of bandwidth? I wouldn't say TLDP is <para>A: Does TLDP use a lot of bandwidth? I wouldn't say TLDP is
necessarily a bandwidth-heavy site. That is to say, most of the necessarily a bandwidth-heavy site. That is to say, most of the
transactions from TLDP sites involve highly efficient, basic HTML documents. A rather unscientific interrogation of server logs shows that transactions from TLDP sites involve highly efficient, basic HTML documents. A rather unscientific interrogation of server logs shows that
@ -129,7 +95,7 @@ pages are just a few kilobytes, the images a few more. All in all, this adds
up - but with our uplink (which I'll get to) and the global system of up - but with our uplink (which I'll get to) and the global system of
mirrors, we're able to sustain the traffic load.</para> mirrors, we're able to sustain the traffic load.</para>
<para>iBiblio's network connectivity is provided by a 1 gygabit direct uplink to the <para>iBiblio's network connectivity is provided by a 1 gigabit direct uplink to the
campus' border router. Connectivity to commodity networks and I2/Abilene campus' border router. Connectivity to commodity networks and I2/Abilene
is provided by an OC-48 uplink. iBiblio's traffic load averages about is provided by an OC-48 uplink. iBiblio's traffic load averages about
260Mbits/Sec, with web traffic a substantial part of that load.</para> 260Mbits/Sec, with web traffic a substantial part of that load.</para>