cvs commit: www/lfs faq.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Fri Oct 17 06:07:53 PDT 2003


jeroen      03/10/17 07:07:53

  Modified:    hints    submit.html
               lfs      faq.html
  Log:
  Fix a spelling error. Applied Tushars patch to hints/submit.html
  
  Revision  Changes    Path
  1.43      +2 -1      www/hints/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/submit.html,v
  retrieving revision 1.42
  retrieving revision 1.43
  diff -u -r1.42 -r1.43
  --- submit.html	17 Sep 2003 16:52:13 -0000	1.42
  +++ submit.html	17 Oct 2003 13:07:53 -0000	1.43
  @@ -57,6 +57,7 @@
   	<li>The hint document is text based. The format for the hints is as explained at the end of this document.</li>
   	<li>Avoid including scripts and patches in the hints. Keep these as separate files to avoid spoiling the beauty of the hint:) Patches should follow the <a href="http://patches.linuxfromscratch.org">patches format</a>. For all attachments for the hint, created a tarball with the same name as your hint and that will untar into a directory that has the same name as the name of your hint (without the .txt extension). For example, if your hint is foo.txt, then the tarball would be named foo.tar.bz2 (replace compression extension by the one that you use) and it would untar into foo directory. This tarball will be hosted in the download section for users to download. Patches for packages will also be hosted on Patches project website. For example, if your hint has a patch for gcc, that patch will be hosted under gcc directory. So be sure to mention the name of your hint in the patch description.</li>
   	<li>To submit or update a hint, send an e-mail to the <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">hint mailing list</a>. From there it will be picked up by the hint maintainer, who will update the hint index and the tarball. To check if your hint has already been included, you can <a href="http://linuxfromscratch.org/mailman/listinfo/hints">subscribe</a> to the hints mailinglist and check for the CVS commit message. Keep the hints list solely for <strong>submitting hints and updates to hints</strong>.</li>
  +	<li><strong>Note that by submitting a hint, you agree to the conditions mentioned on this page with respect to the hint. In particular, you allow other users to take over the maintainership of the hint if another user contacts you with a request (for taking over the maintainership or integrating his/her work in your hint) and you fail to respond to the request for a month. If you would not like someone to take over the maintainership of the hint, please state so clearly in the hint. Authors should also keep the contact information updated.</strong></li>
   </ul>
   
   <h3 id="hintformat">Hint Format</h3>
  @@ -66,7 +67,7 @@
   	<p>Hint authors may be interested in <a href="downloads/files/MAINTAINER/checkHint">a rudimentary script</a> that checks the format of the hint. If the script reports an error, there is a huge possibility that the hint will be returned to you for reformatting. Suggestions to make the script more feature rich are always welcome. </p>
   	<dl>
   		<dt>AUTHOR:</dt>
  -			<dd>This field can be repeated if there are multiple authors. Each author line should have name and contact details of the hint author.</dd>
  +			<dd>This field can be repeated if there are multiple authors. Each author line should have name and contact details of the hint author. Restrict this field for the current authors of the hint. Previous authors should be acknowledged in the ACKNOWLEDGEMENTS section.</dd>
   		<dt>DATE:</dt>
   			<dd>The date the hint was last updated in international format (YYYY-MM-DD).</dd>
   		<dt>LICENSE:</dt>
  
  
  
  1.23      +1 -1      www/lfs/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvsroot/www/lfs/faq.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- faq.html	30 Sep 2003 14:43:10 -0000	1.22
  +++ faq.html	17 Oct 2003 13:07:53 -0000	1.23
  @@ -554,7 +554,7 @@
   				<li>Setting up default gateway...</li>
   				<li>SIOCADDRT:No such device [failed]</li>
   			</ul>
  -			<p>eth0 is a virtual device with no /dev entry. It refers to the first detected network card in your system. The reason the kernel can't route find this device is because you forgot to add support for your network card in the kernel. The kernel detected the card but doesn't have a driver for it. The LFS boot script tries to bring up the network but fails because of this.</p>
  +			<p>eth0 is a virtual device with no /dev entry. It refers to the first detected network card in your system. The reason the kernel can't find this device is because you forgot to add support for your network card in the kernel. The kernel detected the card but doesn't have a driver for it. The LFS boot script tries to bring up the network but fails because of this.</p>
   			<p>Recompile your kernel with the proper driver, either built in or as a module. If you compiled the network driver as a module, then also adjust /etc/modules.conf to alias the network card module as eth0; for example: <code>alias eth0 8139too</code>. If you don't know which network card you have, you can use <code>dmesg</code>, /proc/pci or <code>lspci</code> to find out.</p>
   		</dd>
   	<dt id="spurious-8259A-interrupt">spurious 8259A interrupt: IRQ14 </dt>
  
  
  



More information about the website mailing list