<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="./howto.xsl"?>
<howto
  xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="http://starling.ws/XML/howto.xsd">    
  <head>
	  <navigation ToC="yes" section="yes" topic="yes" subtopic="yes" subsubtopic="yes" links="yes"/>
	  <pdfmarks body="no" section="no" topic="no" subtopic="no" subsubtopic="no"/>
    <title></title>
		<description></description>
		<keywords>NetBSD, Starling</keywords>
		<author>Gan Uesli Starling</author>
		<copyright>2003, Gan Uesli Starling</copyright>
  </head>
  <body>
    <title></title>
		<p class="center"><b></b>
		  <br/>
			<br/><a class="button" href="http://starling.us/gus_netbsd/">&#160;home: http://starling.us/gus_netbsd&#160;</a>
		  <br/>
			<br/>by &#284;an &#364;esli Starling
			<br/>copyright 2003
		</p>
    <section>
      <title>Introduction</title>
      <p><warn>Newbie? Good... Don&#8217;t panic!</warn> This is a fairly simple how-to. It only runs long because of exhaustive notes, unexpurgated example files and cli sessions in fullest detail.</p>
      <ul>
        <li>Regular black body-text conveys the more important instructions and comments.</li>
        <li><note>This color text denotes excessive, almost-trivial commentary (BSD-land common knowledge). 
          <br />Those already in the know may just ignore this light-color text.</note>
        </li>
        <li><code>Monospace in this color denotes cli arguments, file names and/or short excerpts from either.</code></li>
        <li><cli>Monospace on this background denotes entire files, whole lines from files and/or complete cli sessions with&#160;<cmd>commands you enter</cmd>&#160;darker than OS output such as the prompt.</cli></li>   
        <li><code>baal: {666}</code> simbolizes a randomly numbered starting prompt in <code>csh</code> (the C-shell).</li>
        <li><i>Italics anywhere denote a side comment only.</i></li>   
      </ul>
    </section>

    <section>
      <title>Objective</title>
			<p><b>Desired outcomes are:</b></p>
			<ul>
  			<li></li>
  			<li></li>
  			<li></li>
			</ul>
    </section>

    <section>
      <title>Start Of Instructions</title>
			<p><b>Note: </b><note>Nothing herein is simulated. What follows describes real configurations. Passwords, secrets, network names and IP numbers have been changed to obfuscate my network from hackers.</note>
			</p>
      <topic>
        <title>Starting conditions</title>
			</topic>	
    </section>

<!--

    <section>
      <title></title>
    </section>
      <topic>
        <title></title>
      </topic>
      	<subtopic>
        	<title></title>
      	</subtopic>
      		<subsubtopic>
        		<title></title>
      		</subsubtopic>
-->  		
		
    <section>
      <title>Final Comments</title>
			<p>Have my efforts aided you? I hope so. If this be the case, please consider making a similar effort yourself, even if only one single time. When next you surmount a confusing task in Unix-land, post a how-to of your own up on the Web. Then send me the link for inclusion on my how-to index page <i>(with full credit to you, of course)</i>.</p>
			<p>Alternately, should you wish to contribute perhaps a little something, but lack the time to write a how-to, consider making a token donation <i>(five bucks?)</i> to my favorite cause: the Jamseng medical hospice <a href="http://vajra.us/Zadoh_1/S_jamseng.JPG" target="_blank">(see photo)</a> in a remote <i>(even by Tibetan standards!)</i> valley outside the town of Zadoh in the province of Kham in Tibet. Please know that with this fund, administrative costs are zero; one hundred percent goes straight to Tibet. Here is the address:</p>
			<p class="left" style="color: maroon">Jamseng Clinic Fund
			<br />P. O. Box 4
			<br />Nelson B.C. V1L 5P7
			<br />CANADA</p>
			<p>Respectfully,</p>
			<p>&#284;an &#364;esli Starling<br />Kalamazoo, MI, USA</p>
    </section>
    <section>
      <title>How To Report An Error.</title>
			<p><span style="color: orange;">ERROR REPORTING:</span> Below is my email. But please only use it to report a real and genuine error somewhere within the above instructions. I have invested time I don&#8217;t have just to compose this little bit of illumination. Thus I shall only respond to corrections from definite sources who write presenting  complete correction details. Still, I hope I have been of assistance to someone. Thank you.</p>
			<p><a href="mailto:gan@starling.us">gan@starling.us</a></p>
    </section>
  </body>
</howto>

