old-www/ldpwn/20040519.html

186 lines
12 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 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 }
div.c3 {margin-left: 2em}
pre.c2 {color: #000000}
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> 20<br>
<b>Publication Date :</b> 2004-05-19<br>
<hr></div>
<div class="TOC">
<dl>
<dt class="c1">Table of Contents</dt>
<dt>1. <a href="#new-review">Documents submitted for review</a></dt>
<dt>2. <a href="#new-proposed">New document proposals</a></dt>
<dt>3. <a href="#updated-docs">Updated HOWTOs, FAQs and Guides</a></dt>
<dt>4. <a href="#tldp-world-news">News in The LDP world</a></dt>
<dt>5. <a href="#tldp-discussions">Discussions on The LDP lists</a></dt>
<dt>6. <a href="#interview">Interview with Mark Komarinski</a></dt>
<dt>7. <a href="#tldp-contribute">HOWTO contribute to The LDP</a></dt>
</dl>
</div>
<div class="sect1">
<h1 class="sect1"><a name="new-review"></a>1. Documents submitted for review</h1>
<ul>
<li><span class="rss:item">Devin Watson <a href="http://lists.tldp.org/index.cgi?1:mss:7301:200405:hpddcdpgimaaaodmebkg" target="_top">sent in</a> a short but informative introduction into writing
daemons in Linux. The SGML (LinuxDoc) file can be found at <a href="http://www.linuxprofilm.com/articles/linux-daemon-howto.sgml" target=
"_top">http://www.linuxprofilm.com/articles/linux-daemon-howto.sgml</a>.</span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="new-proposed"></a>2. New document proposals</h1>
<ul>
<li><span class="rss:item">SPICE is a simulator for electronic circuits for use in the <a href="http://www.geda.seul.org/" target="_top">gEDA</a> (GPL'ed Electronic Design Automation tool suite)
environment. Stuart Brorson wrote a <a href="http://www.brorson.com/gEDA/SPICE/intro.html" target="_top">SPICE on gEDA HOWTO</a>, describing <a href="http://tclspice.sourceforge.net/" target=
"_top">TclSpice</a> and argues thus for including it into the TLDP collection: <span class="QUOTE">"The whole area of Linux as an engineering workstation is currently taking off, and I think it
valuable to have HOWTOs in place for the arriving hordes."</span></span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="updated-docs"></a>3. Updated HOWTOs, FAQs and Guides</h1>
<ul>
<li><span class="rss:item">The <a href="http://tldp.org/HOWTO/KickStart-HOWTO.html" target="_top">Kickstart HOWTO</a> will be moved to the <a href="http://tldp.org/authors/unmaint.html" target=
"_top">Unmaintained</a> directory upon request of the author, Martin Hamilton, who reasons that RedHat now provides enough documentation <a href=
"http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/part-install-info.html" target="_top">in their manual</a> and on this <a href=
"https://listman.redhat.com/mailman/listinfo/kickstart-list" target="_top">Kickstart mailinglist</a>.</span></li>
<li><span class="rss:item">Emma Jane Hogbin's <a href="http://tldp.org/HOWTO/ACPI-HOWTO/index.html" target="_top">ACPI HOWTO</a> v1.4 contains info about power management with the 2.6.5 kernel. The
update includes information on battery monitoring applications causing touchpad lockup problems.</span></li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="tldp-world-news"></a>4. News in The LDP world</h1>
<ul>
<li><span class="rss:item">Copyright of the Linux Dictionary<br></span>
<p><span class="rss:item">Binh Nguyen found a listening ear for linuxdig.com potentially violating the copyright on his work. After
contacting Scott Baust, the technical and administrative responsible for the linuxdig.com domain, he was
able to <a href="http://lists.tldp.org/index.cgi?1:msp:7273:200405:pdkghihaippeebaleahc" target="_top">resolve the issue</a>.</span></p>
</li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="tldp-discussions"></a>5. Discussions on The LDP lists</h1>
<ul>
<li><span class="rss:item">Beautifying XML<br></span>
<p><span class="rss:item">Gerardo Arnaez <a href="http://lists.tldp.org/index.cgi?1:msp:7283:200405:nmegdephfcmlokdpheja" target="_top">doesn't like</a> the standard <b class=
"command">xmlto</b>-generated HTML, but was at a loss as to how to make it more agreeable to the eye. Emma Jane suggested <a href=
"http://lists.tldp.org/index.cgi?1:msn:7282:200405:nmegdephfcmlokdpheja" target="_top">the use of style sheets</a>, and pointed to a couple of freely available ones. You might have problems reading
her explanations for including a stylesheet, because she mentions some HTML tags which are lost in the HTML conversion. So here is (once again) how you include a stylesheet:</span></p>
<p>Add a line like the following between the &lt;head&gt; and &lt;/head&gt; tags:</p>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="screen c2">
&#13;&lt;link rel="stylesheet" type="text/css" href="your_stylesheet.css" /&gt;
</pre></td>
</tr>
</table>
</li>
<li><span class="rss:item">LDAP related HOWTOs<br></span>
<p><span class="rss:item">In response to Machtelt Garrels mail about the maintenance of the LDAP HOWTOs hosted by TLDP, Glen Turner wanted to be a contributor <a href=
"http://lists.tldp.org/index.cgi?1:mss:7286:200405:kcjllafbebiblpmpfelc" target="_top">said that</a> the two LDAP HOWTOs did not illustrate current best practices. He gave pointers to <a href=
"http://www.duke.edu/~gettes/giia/ldap-recipe/" target="_top">A Recipe for Configuring and Operating LDAP Directories</a> by Michael R Gettes and a <a href="http://middleware.internet2.edu/" target=
"_top">general directory issues</a> resource.</span></p>
</li>
</ul>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="interview"></a>6. Interview with Mark Komarinski</h1>
<div class="c3">&gt;
<div class="figure"><span class="rss:item"><a name="AEN66"></a></span>
<p><span class="rss:item"><b>Figure 1. Mark Komarinski</b></span></p>
<div class="mediaobject">
<p><img src="mkomarinski.png" align="left"></p>
</div>
</div>
<p>Mark Komarinski, former event coordinator, is not as active any more as he used to be, at least not for the TLDP project, but certainly has some interesting things to say. <span class="QUOTE">"My
secret goal in life is to be one of those people who gets quoted all the time in articles"</span>, he laughingly admits.</p>
<div class="qandaset">
<div class="qandaentry">
<div class="question">
<p><a name="AEN79"></a><b>Q:</b> You've seen some people, docs and distros pass the review. What was the most remarkable moment for you (having to do with TLDP, of-course)?</p>
</div>
<div class="answer">
<p><b>A:</b> The response to the HOWTO-HOWTO (now the <a href="http://tldp.org/LDP/LDP-Author-Guide/html/index.html" target="_top">LDP Author Guide</a>) was really impressive. I get frequent emails
from people who say how much it's helped them.</p>
<p>The sad thing (but one I've come to accept) is that writing documentation isn't the most exciting thing in the world. Having worked previously as a technical support person, there are
similarities. It's one of those things that everyone needs, but is left to someone else to do.</p>
</div>
</div>
<div class="qandaentry">
<div class="question">
<p><a name="AEN86"></a><b>Q:</b> You've written for LinuxJournal, already in the very first issue, you've published quite some books about RedHat and other system administration, you just told me you
are working on a CUPS HOWTO, ... You're a very prolific author. Is there one subject that you haven't written about, but that you would like to cover one day or if you would only have the time?</p>
</div>
<div class="answer">
<p><b>A:</b> There are two reasons I write - either I know a bit about the subject and want to document it, or I know little about the subject and want to figure it out along the way. In order to
write about something you do need a good understanding of what you're writing about, which is the logic I used when writing the LDP Author Guide - I had a great reference guide in the ORA DocBook
book, but nothing that showed how to use the tools. So I started writing and learned the hard way.</p>
<p>In the case of the <a href="http://www.ibiblio.org/mdw/HOWTO/Remote-Serial-Console-HOWTO/index.html" target="_top">Remote Serial Console HOWTO</a> (note: not to be confused with David Lawyer's
<a href="http://www.ibiblio.org/mdw/HOWTO/Serial-HOWTO.html" target="_top">Serial HOWTO</a>), I had a bit of working knowledge of the subject already, so it was easier for me to write.</p>
<p>In terms of things I want to see, some of my started-but-stalled projects include a book covering the history of Linux, the CUPS HOWTO which I may just donate to another HOWTO depending on how far
I get, and a Linux Tuning Guide project I started on two years ago and is very much out of date.</p>
</div>
</div>
<div class="qandaentry">
<div class="question">
<p><a name="AEN95"></a><b>Q:</b> I bet a lot of authors and authors-to-be admire you. Do you have any good advice for them, apart from the <span class="QUOTE">"you'll need a lot of coffee"</span>
one?</p>
</div>
<div class="answer">
<p><b>A:</b> How do you get your start? Write and take chances. I got started writing for my college newspaper (a bi-weekly column where I was extolling the virtues of Linux in 1992!). When I heard
that a Linux magazine was going to start up (Linux Journal) I sent an email and asked if they were looking for authors. They said yes, and all I asked for was a free subscription. That publicity got
me noticed by my publisher and it went from there.</p>
<p>Coffee isn't that necessary, but it does help when you have 5 days left to submit your manuscript and you have 100 pages to go.</p>
</div>
</div>
<div class="qandaentry">
<div class="question">
<p><a name="AEN102"></a><b>Q:</b> We took a look at your web site, in the process of researching your background a bit. Why does it look like it has been made with a typewriter and then scanned
in?</p>
</div>
<div class="answer">
<p><b>A:</b> Well, strangely enough, while I do a lot of writing, some coding, and a lot of sysadmin-type work, I have no eye for web design. Hence the reason why all the pages look like they came
from gopher. If anyone reading this wants to help me out, I'd appreciate it :)</p>
<p><em>Later, Mark added this remark:</em></p>
<p>Ha. Your criticism of <a href="http://www.wayga.org/" target="_top">my web site</a> has prompted me to install bloxsom. Which doesn't look like the web circa 1993.</p>
<p><em>;-)</em></p>
</div>
</div>
</div>
</div>
</div>
<div class="sect1">
<hr>
<h1 class="sect1"><a name="tldp-contribute"></a>7. HOWTO contribute to The LDP</h1>
<p><a href="http://www.tldp.org/" target="_top">The Linux Documentation Project</a> (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>