old-www/ldpwn/20040121.html

180 lines
14 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy for Linux/x86 (vers 1st June 2003), see www.w3.org">
<title>The Linux Documentation Project Weekly News</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7">
<style type="text/css">
body {
background-color: #FFFFFF;
color: #000000;
}
:link { color: #0000FF }
:visited { color: #840084 }
:active { color: #0000FF }
p.c2 {font-weight: bold}
dt.c1 {font-weight: bold}
</style>
</head>
<body class="article">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="title"><a name="AEN2"></a>The Linux Documentation Project Weekly News</h1>
<b>Issue Number :</b> 3<br>
<b>Publication Date :</b> 2004-01-21<br>
<hr></div>
<div class="TOC">
<dl>
<dt class="c1">Table of Contents</dt>
<dt>1. <a href="#new-released">New documents @ TLDP</a></dt>
<dt>2. <a href="#new-for-review">Documents submitted for review</a></dt>
<dt>3. <a href="#new-proposed">New document proposals</a></dt>
<dt>4. <a href="#updated-docs">Updated HOWTOs, FAQs and Guides</a></dt>
<dt>5. <a href="#tldp-world">News in The LDP world</a></dt>
<dd>
<dl>
<dt>5.1. <a href="#news-item1">Linux+XFS HOWTO to Unmaintained</a></dt>
</dl>
</dd>
<dt>6. <a href="#discussions">Discussions on TLDP lists</a></dt>
<dd>
<dl>
<dt>6.1. <a href="#discussion1">ISBN for TLDP documents</a></dt>
</dl>
</dd>
<dt>7. <a href="#interview">Interview with Guylhem Aznar</a></dt>
<dt>8. <a href="#feedback">HOWTO contribute to TLDP</a></dt>
</dl>
</div>
<div class="sect1">
<h1 class="sect1"><a name="new-released"></a>1. New documents @ TLDP</h1>
<p>This week we have for you:</p>
<ul>
<li><span class="rss:item">The <a href="http://tldp.org/HOWTO/Webcam-HOWTO/" target="_top">Webcam HOWTO</a>, a long-needed addition to our collection. Howard Shane documents the use of USB, FireWire
and parallel port webcams, explains about video devices and has detailed info for a number of webcam brands. He also discusses applications like <span class="application">Xawtv</span>, <span class=
"application">Gqcam</span> and <span class="application">SANE</span>, and what to do when things don't work out as planned. The HOWTO already contains info for the new 2.6 kernels.</span></li>
<li><span class="rss:item">The <a href="http://tldp.org/HOWTO/Cryptoloop-HOWTO/" target="_top">Cryptoloop HOWTO</a>, by Ralf Holtzer. With the Cryptoloop functionality, which is part of the CryptoAPI
in the 2.6 kernels, you can encrypt disk partitions without the need to install kernel patches. Ralf explains how to configure the kernel, where to get adapted <b class="command">losetup</b> and
<b class="command">mount</b> programs and how to use these commands.</span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="new-for-review"></a>2. Documents submitted for review</h1>
<ul>
<li><span class="rss:item">Artemio completed his <a href="http://lists.tldp.org/index.cgi?5:mss:7200:200401:nnghnjankckgmeplmgkk" target="_top">SquashFS HOWTO</a>; Tabatha is doing a last
checkup.</span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="new-proposed"></a>3. New document proposals</h1>
<ul>
<li><span class="rss:item">Daniel Burr wrote this <a href="http://lists.tldp.org/index.cgi?5:mss:7198:200401:degpojhlceedpfcncgab" target="_top">VCD conversion HOWTO</a>, explaining how to convert
your video tapes to a format suitable for Video CDs. He awaits your input.</span></li>
<li><span class="rss:item">Daniel Sumers Myers <a href="http://lists.tldp.org/index.cgi?1:mss:6451:200401:addnmndhfbflgdbiaohg" target="_top">proposed</a> to write a HOWTO on installing the Berkeley
Open Infrastructure for Network Computing (BOINC; <a href="http://boinc.berkeley.edu" target="_top">http://boinc.berkeley.edu)</a> and creating a simple test project.</span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="updated-docs"></a>4. Updated HOWTOs, FAQs and Guides</h1>
<ul>
<li><span class="rss:item">Howard Shane published v1.05 of the <a href="http://tldp.org/HOWTO/Scanner-HOWTO/" target="_top">Scanner HOWTO</a>, which contains various corrections and
updates.</span></li>
<li><span class="rss:item">Rick Moen did some corrections of addresses in v1.7.6 of the <a href="http://tldp.org/HOWTO/User-Group-HOWTO.html" target="_top">LUG HOWTO</a>. Don't forget to let him know
if your LUG's address or contact info change!</span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="tldp-world"></a>5. News in The LDP world</h1>
<div class="sect2">
<h2 class="sect2"><a name="news-item1"></a>5.1. Linux+XFS HOWTO to Unmaintained</h2>
<p>Russel Ingram let us know that his Linux+XFS HOWTO can be moved to the unmaintained collection. While SGI's journaling filesystem is of course supported in the 2.6 kernels, Russel hasn't had the
opportunity to keep the document nor his own skills up to date. He welcomes anyone who wishes to take over this document but also argues that you now have XFS support by default.</p>
<p>Note that you may also use the ext3 or Reiser journaling filesystems, but tests have pointed out that XFS has better performance for really large files (in the Gigabytes range).</p>
</div>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="discussions"></a>6. Discussions on TLDP lists</h1>
<div class="sect2">
<h2 class="sect2"><a name="discussion1"></a>6.1. ISBN for TLDP documents</h2>
<p>Machtelt Garrels was toying with the idea of ISBN numbers for The LDP documents. People had various opinions about that and Martin WHEELER in a related context said that The LDP should not not be
attempting to do what it is. Emma Jane Hogbin <a href="http://lists.tldp.org/index.cgi?1:mss:6475:200401:jcgoangfebccbgnflhnf" target="_top">contradicted</a> him and listed the incremental progress
of The LDP and the work that she had been doing recently.</p>
</div>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="interview"></a>7. Interview with Guylhem Aznar</h1>
<p>After a period of silence, we finally have another interview ready for you. We had the opportunity of asking TLDP's <span class="QUOTE">"bad guy"</span>, Guylhem Aznar, a couple of questions.
Guylhem cuts the knots in troublesome issues; that is why people feel very strongly - and sometimes also very differently - about him.</p>
<p>Guylhem is a native French speaker, and the fun thing about such people is that they tell you much more than you want to know. We were flooded with answers to our questions, and although we had to
cut here and there, we don't want to keep Guylhem's interesting remarks from you. So this interview is a little bit longer than usual.</p>
<div class="figure"><a name="AEN66"></a>
<p class="c2">Figure 1. Guylhem Aznar, taker of decisions</p>
<div class="mediaobject">
<p><img src="guylhem.png" align="left"></p>
</div>
</div>
<p><em>Q: What are you doing in the TLDP organization?</em></p>
<p>A: Apart from taking responsibilities in solving troublesome issues, I'm not really doing very much at the moment.</p>
<p>There was a time when my role was much more active. On the one hand I'm happy: the fact that I don't need to interfere that often anymore is a sure sign that TLDP is running smoothly now.
Decisions are taken, applied and respected in an atmosphere of mutual trust. TLDP has matured, the team works. Moreover, being a medical resident, a PhD student, running my own consultancy business
and contributing to various free software projects, all simultaneously, I don't have a lot of free time.</p>
<p>But on the other hand there are still problems, such as the license issues we discussed recently, or the co-operation with non-English efforts. There are also problems with old and outdated
documents, and I am concerned about the lack of new authors. However few hours I have to myself, I'd like to invest those in order to keep TLDP from coming to harm.</p>
<p><em>Q: So how did you get involved?</em></p>
<p>A: It was round about 1997, because of the lack of responsiveness from the French group which I submitted my documents to.</p>
<p>I decided to start writing in English, and submitted my documents to TLDP. There was an excellent ambiance and the project was very interesting. All went well for some time, but just before the
turn of the century, a severe problem arose: the LDP leader of those days had to resign, for many reasons, and I did not trust the only candidate for the succession. I feared there were going to be
conflicts of interest, so I started a campaign and got <span class="QUOTE">"elected"</span>.</p>
<p><em>Q: Can you tell us about your presidency?</em></p>
<p>A: My first job was to unify the LDP again: we had mailing lists and servers all over the world, and nobody knew who was responsible for what. So I started by putting together a <span class=
"QUOTE">"staff"</span>, a team of volunteers that could get TLDP structured. I learned the hard way that it was a good thing to have procedures and to discuss steps with my team before actually
taking action.</p>
<p>After a short romance with SGI, we got the relationship with ibiblio going again. They were very understanding and provided a lot of support, which enabled us to centralize resources in North
Carolina.</p>
<p><em>Q: Under your chairmanship, the LDP changed its name to TLDP. Can you explain, for the readers who joined us more recently, why this happened?</em></p>
<p>A: Well, after I was elected, I didn't want the other candidate to feel left out. So I trusted him to be our webmaster. However, we <span class="QUOTE">"lost"</span> linuxdoc.org because this
person first purchased the .com and ran a commercial website on it on the back of TLDP, then claimed ownership on the .org because he had paid for the domain renewal. We offered to refund him for any
expenses but he refused any agreement which would have transferred back the domain to us. So history proved I was right about not trusting him in the first place. As I said, I learned the hard way.
This time I learned that many people are interested in TLDP, but not always for the good of the project.</p>
<p>Anyway, we had to find a new domain name, and TLDP.org was short and free, so I took my responsibilities and moved the project to the domain we are currently using. TLDP is now much more than the
former English-only project, and much more efficient, so it was for the best, if you ask me. I'd like to take this opportunity to ask other non-English projects to join us, rather than duplicating
efforts. I'm confident that our new evolutions - such as sorted documentation, more automatisation and the <span class="QUOTE">"seal of quality"</span> on the documents we put forward will make them
want to work altogether.</p>
<p><em>Q: I read somewhere that you have a cure for ignorance. We're very curious as to what this is?</em></p>
<p>A: Education, education and education. With a little support to help getting started.</p>
<p>I call it a <span class="QUOTE">"cure"</span> because I think ignorance is a disease (I'm into medicine, don't blame me!). It can cause lot of symptoms, such as stupid questions, lack of
understanding on how to fix basic problems, bad behavior, and lack of respect for this enormous effort.</p>
<p>I'm quite concerned by the current flow of GNU/Linux users who do not take time to learn the system: the basics such as the shell, the multi-user aspect, and above all, free software ethics. If I
had a wish, I'd like a desktop icon on every distribution linking to basic documents, to give new users a clue. You can't blame them now - TLDP is not very visible, and free documentation is not
always put forward.</p>
<p>Moreover, some people take free software for granted. They think it's normal and ask authors for all kind of features or support as if it was compulsory for the authors, who are in most cases not
even payed. They do code for their personal satisfaction, not to indulge their every wish!</p>
<p><em>(Note from the reaction: these are the same people who think it is a perfectly normal thing not to pay for commercial software as well and just make illegal copies...)</em></p>
<p>This ignorance fuels Open Source movements, which only take free software basic principles but forget ethics and the true projects behind free software - society and politics. These words
shouldn't be taboos: political and social movements should be mentioned along free software for all sorts of reasons.</p>
<p>I'd like new GNU/Linux users to be aware of the global project behind free software. Free software is about coming back to true capitalism - a real competition, with real business opportunities.
The current situation with <span class="QUOTE">"intellectual property"</span> and non-free software is an artificial scarcity created to try to sell what can't be sold. Illegal copy is just a symptom
of the lack of adaptation between the market and the people. Free software offers an excellent way to solve that problem. DRM, DMCA, Palladium etcetera are all designed to try to make a broken model
work. You can see that I can get quite excited about this, but let's face it: we live in the digital age. Live with it or die like the dinosaurs did.</p>
<p><em>Thank you, Guylhem, for this abundance of ideas!</em></p>
<p>Find out more about Guylhem at <a href="http://externe.net/" target="_top">http://externe.net/</a>.</p>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="feedback"></a>8. HOWTO contribute to TLDP</h1>
<p>The Linux Documentation Project (TLDP) is working on developing free, high quality documentation for the GNU/Linux operating system. If you want to help TLDP, consider joining <tt class=
"email">&lt;<a href="mailto:discuss-subscribe@en.tldp.org">discuss-subscribe@en.tldp.org</a>&gt;</tt>.</p>
<p>Help us create this newsletter. We need volunteers who follow the community (mailing lists, newsgroups, web channels) and report events related to free software documentation. Write to us at
<tt class="email">&lt;<a href="mailto:feedback@en.tldp.org">feedback@en.tldp.org</a>&gt;</tt>.</p>
<p>The LDP Weekly News is compiled and edited by Machtelt Garrels and Y Giridhar Appaji Nag with help from several other people.</p>
</div>
</div>
</body>
</html>