From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/articles: linux-kernel-compiling.xml
Date: Fri, 10 Dec 2010 09:00:54 +0000 (UTC) [thread overview]
Message-ID: <20101210090054.2E66420054@flycatcher.gentoo.org> (raw)
nightmorph 10/12/10 09:00:54
Modified: linux-kernel-compiling.xml
Log:
remove dead TLDP link, add kernelnewbies.org links. bug 348329
Revision Changes Path
1.4 xml/htdocs/doc/en/articles/linux-kernel-compiling.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/articles/linux-kernel-compiling.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/articles/linux-kernel-compiling.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/articles/linux-kernel-compiling.xml?r1=1.3&r2=1.4
Index: linux-kernel-compiling.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/linux-kernel-compiling.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- linux-kernel-compiling.xml 4 Mar 2010 09:12:18 -0000 1.3
+++ linux-kernel-compiling.xml 10 Dec 2010 09:00:54 -0000 1.4
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/linux-kernel-compiling.xml,v 1.3 2010/03/04 09:12:18 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/linux-kernel-compiling.xml,v 1.4 2010/12/10 09:00:54 nightmorph Exp $ -->
-<guide link="/doc/en/articles/linux-kernel-compiling.xml" disclaimer="articles">
+<guide disclaimer="articles">
<title>Compiling the Linux kernel</title>
<author title="Author">
@@ -21,8 +21,8 @@
document is an updated version of the original article, and contains
various improvements made by the Gentoo Linux Documentation team -->
-<version>1.1</version>
-<date>2005-10-09</date>
+<version>2</version>
+<date>2010-12-10</date>
<chapter>
<title>Introducing the kernel</title>
@@ -640,10 +640,11 @@
</p>
<ul>
+<!-- not accessible as of 2010; bug 348329
<li>
<uri link="http://www.tldp.org/HOWTO/Kernel-HOWTO/">The Linux Kernel
HOWTO</uri>, another good resource for kernel compilation instructions.
- </li>
+ </li> -->
<!-- not accessible <li>
<uri link="http://www.tldp.org/HOWTO/LILO-crash-rescue-HOWTO/">The LILO,
Linux Crash Rescue HOW-TO</uri>, which shows you how to create an emergency
@@ -653,10 +654,18 @@
<uri link="http://www.kernel.org">www.kernel.org</uri>, the site that hosts
the Linux Kernel archives.
</li>
+ <li>
+ <uri link="http://kernelnewbies.org/FAQ">The Kernel Newbies</uri> FAQs.
+ Kernel Newbies is an excellent resource for learning how to <uri
+ link="http://kernelnewbies.org/FAQ/KernelCompilation">compile the
+ kernel</uri>, as well as learning how the different pieces work. The site
+ also provides a detailed yet easy-to-read overview of the <uri
+ link="http://kernelnewbies.org/LinuxChanges">changes</uri> between each new
+ kernel release.
+ </li>
</ul>
</body>
</section>
</chapter>
-
</guide>
reply other threads:[~2010-12-10 9:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101210090054.2E66420054@flycatcher.gentoo.org \
--to=nightmorph@gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox