Author: bdubbs
Date: 2011-03-04 20:28:36 -0700 (Fri, 04 Mar 2011)
New Revision: 9476
Added:
tags/6.8/
tags/6.8/BOOK/
tags/6.8/BOOK/chapter04/creatingtoolsdir.xml
tags/6.8/BOOK/chapter06/kernfs.xml
Removed:
tags/6.8/BOOK/chapter04/creatingtoolsdir.xml
tags/6.8/BOOK/chapter06/kernfs.xml
Modified:
tags/6.8/BOOK/chapter01/changelog.xml
tags/6.8/BOOK/general.ent
Log:
Set up for LFS-6.8
Modified: tags/6.8/BOOK/chapter01/changelog.xml
===================================================================
--- trunk/BOOK/chapter01/changelog.xml 2011-02-19 04:37:23 UTC (rev 9473)
+++ tags/6.8/BOOK/chapter01/changelog.xml 2011-03-05 03:28:36 UTC (rev
9476)
@@ -37,6 +37,15 @@
-->
<listitem>
+ <para>2011-03-04</para>
+ <itemizedlist>
+ <listitem>
+ <para>[bdubbs] Release LFS 6.8.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
<para>2011-02-18</para>
<itemizedlist>
<listitem>
Deleted: tags/6.8/BOOK/chapter04/creatingtoolsdir.xml
===================================================================
--- trunk/BOOK/chapter04/creatingtoolsdir.xml 2011-02-19 04:37:23 UTC (rev
9473)
+++ tags/6.8/BOOK/chapter04/creatingtoolsdir.xml 2011-03-05 03:28:36 UTC
(rev 9476)
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
- "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
- <!ENTITY % general-entities SYSTEM "../general.ent">
- %general-entities;
-]>
-
-<sect1 id="ch-tools-creatingtoolsdir">
- <?dbhtml filename="creatingtoolsdir.html"?>
-
- <title>Creating the $LFS/tools Directory</title>
-
- <para>All programs compiled in <xref linkend="chapter-temporary-tools"/>
- will be installed under <filename class="directory">$LFS/tools</filename>
- to keep them separate from the programs compiled in <xref
- linkend="chapter-building-system"/>. The programs compiled here are
- temporary tools and will not be a part of the final LFS system. By keeping
- these programs in a separate directory, they can easily be discarded later
- after their use. This also prevents these programs from ending up in the
- host production directories (easy to do by accident in <xref
- linkend="chapter-temporary-tools"/>).</para>
-
- <para>Create the required directory by running the following as
- <systemitem class="username">root</systemitem>:</para>
-
-<screen><userinput>mkdir -v $LFS/tools</userinput></screen>
-
- <para>The next step is to create a <filename
class="symlink">/tools</filename>
- symlink on the host system. This will point to the newly-created directory on
- the LFS partition. Run this command as <systemitem
- class="username">root</systemitem> as well:</para>
-
-<screen><userinput>ln -sv $LFS/tools /</userinput></screen>
-
- <note>
- <para>The above command is correct. The <command>ln</command> command
- has a few syntactic variations, so be sure to check
- <command>info coreutils ln</command> and <filename>ln(1)</filename>
- before reporting what you may think is an error.</para>
- </note>
-
- <para>The created symlink enables the toolchain to be compiled so that it
- always refers to <filename class="directory">/tools</filename>, meaning
- that the compiler, assembler, and linker will work both in this chapter
- (when we are still using some tools from the host) and in the next (when
- we are <quote>chrooted</quote> to the LFS partition).</para>
-
-</sect1>
Copied: tags/6.8/BOOK/chapter04/creatingtoolsdir.xml (from rev 9475,
trunk/BOOK/chapter04/creatingtoolsdir.xml)
===================================================================
--- tags/6.8/BOOK/chapter04/creatingtoolsdir.xml
(rev 0)
+++ tags/6.8/BOOK/chapter04/creatingtoolsdir.xml 2011-03-05 03:28:36 UTC
(rev 9476)
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
+ <!ENTITY % general-entities SYSTEM "../general.ent">
+ %general-entities;
+]>
+
+<sect1 id="ch-tools-creatingtoolsdir">
+ <?dbhtml filename="creatingtoolsdir.html"?>
+
+ <title>Creating the $LFS/tools Directory</title>
+
+ <para>All programs compiled in <xref linkend="chapter-temporary-tools"/>
+ will be installed under <filename class="directory">$LFS/tools</filename>
+ to keep them separate from the programs compiled in <xref
+ linkend="chapter-building-system"/>. The programs compiled here are
+ temporary tools and will not be a part of the final LFS system. By keeping
+ these programs in a separate directory, they can easily be discarded later
+ after their use. This also prevents these programs from ending up in the
+ host production directories (easy to do by accident in <xref
+ linkend="chapter-temporary-tools"/>).</para>
+
+ <para>Create the required directory by running the following as
+ <systemitem class="username">root</systemitem>:</para>
+
+<screen><userinput>mkdir -v $LFS/tools</userinput></screen>
+
+ <para>The next step is to create a <filename
class="symlink">/tools</filename>
+ symlink on the host system. This will point to the newly-created directory on
+ the LFS partition. Run this command as <systemitem
+ class="username">root</systemitem> as well:</para>
+
+<screen><userinput>ln -sv $LFS/tools /</userinput></screen>
+
+ <note>
+ <para>The above command is correct. The <command>ln</command> command
+ has a few syntactic variations, so be sure to check
+ <command>info coreutils ln</command> and <filename>ln(1)</filename>
+ before reporting what you may think is an error.</para>
+ </note>
+
+ <para>The created symlink enables the toolchain to be compiled so that it
+ always refers to <filename class="directory">/tools</filename>, meaning
+ that the compiler, assembler, and linker will work both in Chapter 5
+ (when we are still using some tools from the host) and in the next (when
+ we are <quote>chrooted</quote> to the LFS partition).</para>
+
+</sect1>
Deleted: tags/6.8/BOOK/chapter06/kernfs.xml
===================================================================
--- trunk/BOOK/chapter06/kernfs.xml 2011-02-19 04:37:23 UTC (rev 9473)
+++ tags/6.8/BOOK/chapter06/kernfs.xml 2011-03-05 03:28:36 UTC (rev 9476)
@@ -1,78 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
- "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
- <!ENTITY % general-entities SYSTEM "../general.ent">
- %general-entities;
-]>
-
-<sect1 id="ch-system-kernfs">
- <?dbhtml filename="kernfs.html"?>
-
- <title>Preparing Virtual Kernel File Systems</title>
-
- <indexterm zone="ch-system-kernfs">
- <primary sortas="e-/dev/">/dev/*</primary>
- </indexterm>
-
- <para>Various file systems exported by the kernel are used to communicate
to
- and from the kernel itself. These file systems are virtual in that no disk
- space is used for them. The content of the file systems resides in
- memory.</para>
-
- <para>Begin by creating directories onto which the file systems will be
- mounted:</para>
-
-<screen><userinput>mkdir -v $LFS/{dev,proc,sys}</userinput></screen>
-
- <sect2>
- <title>Creating Initial Device Nodes</title>
-
- <para>When the kernel boots the system, it requires the presence of a few
- device nodes, in particular the <filename
- class="devicefile">console</filename> and <filename
- class="devicefile">null</filename> devices. The device nodes will be
created
- on the hard disk so that they are available before <command>udevd</command>
- has been started, and additionally when Linux is started with
- <parameter>init=/bin/bash</parameter>. Create the devices by running the
- following commands:</para>
-
-<screen><userinput>mknod -m 600 $LFS/dev/console c 5 1
-mknod -m 666 $LFS/dev/null c 1 3</userinput></screen>
-
- </sect2>
-
- <sect2 id="ch-system-bindmount">
- <title>Mounting and Populating /dev</title>
-
- <para>The recommended method of populating the <filename
- class="directory">/dev</filename> directory with devices is to mount a
- virtual filesystem (such as <systemitem
- class="filesystem">tmpfs</systemitem>) on the <filename
- class="directory">/dev</filename> directory, and allow the devices to be
- created dynamically on that virtual filesystem as they are detected or
- accessed. Device creation is generally done during the boot process
- by Udev. Since this new system does not yet have Udev and has not yet
- been booted, it is necessary to mount and populate <filename
- class="directory">/dev</filename> manually. This is accomplished by bind
- mounting the host system's <filename class="directory">/dev</filename>
- directory. A bind mount is a special type of mount that allows you to
- create a mirror of a directory or mount point to some other location. Use
- the following command to achieve this:</para>
-
-<screen><userinput>mount -v --bind /dev $LFS/dev</userinput></screen>
-
- </sect2>
-
- <sect2 id="ch-system-kernfsmount">
- <title>Mounting Virtual Kernel File Systems</title>
-
- <para>Now mount the remaining virtual kernel filesystems:</para>
-
-<screen><userinput>mount -vt devpts devpts $LFS/dev/pts
-mount -vt tmpfs shm $LFS/dev/shm
-mount -vt proc proc $LFS/proc
-mount -vt sysfs sysfs $LFS/sys</userinput></screen>
-
- </sect2>
-
-</sect1>
Copied: tags/6.8/BOOK/chapter06/kernfs.xml (from rev 9474,
trunk/BOOK/chapter06/kernfs.xml)
===================================================================
--- tags/6.8/BOOK/chapter06/kernfs.xml (rev 0)
+++ tags/6.8/BOOK/chapter06/kernfs.xml 2011-03-05 03:28:36 UTC (rev 9476)
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
+ <!ENTITY % general-entities SYSTEM "../general.ent">
+ %general-entities;
+]>
+
+<sect1 id="ch-system-kernfs">
+ <?dbhtml filename="kernfs.html"?>
+
+ <title>Preparing Virtual Kernel File Systems</title>
+
+ <indexterm zone="ch-system-kernfs">
+ <primary sortas="e-/dev/">/dev/*</primary>
+ </indexterm>
+
+ <para>Various file systems exported by the kernel are used to communicate
to
+ and from the kernel itself. These file systems are virtual in that no disk
+ space is used for them. The content of the file systems resides in
+ memory.</para>
+
+ <para>Begin by creating directories onto which the file systems will be
+ mounted:</para>
+
+<screen><userinput>mkdir -v $LFS/{dev,proc,sys}</userinput></screen>
+
+ <sect2>
+ <title>Creating Initial Device Nodes</title>
+
+ <para>When the kernel boots the system, it requires the presence of a few
+ device nodes, in particular the <filename
+ class="devicefile">console</filename> and <filename
+ class="devicefile">null</filename> devices. The device nodes must be
created
+ on the hard disk so that they are available before <command>udevd</command>
+ has been started, and additionally when Linux is started with
+ <parameter>init=/bin/bash</parameter>. Create the devices by running the
+ following commands:</para>
+
+<screen><userinput>mknod -m 600 $LFS/dev/console c 5 1
+mknod -m 666 $LFS/dev/null c 1 3</userinput></screen>
+
+ </sect2>
+
+ <sect2 id="ch-system-bindmount">
+ <title>Mounting and Populating /dev</title>
+
+ <para>The recommended method of populating the <filename
+ class="directory">/dev</filename> directory with devices is to mount a
+ virtual filesystem (such as <systemitem
+ class="filesystem">tmpfs</systemitem>) on the <filename
+ class="directory">/dev</filename> directory, and allow the devices to be
+ created dynamically on that virtual filesystem as they are detected or
+ accessed. Device creation is generally done during the boot process
+ by Udev. Since this new system does not yet have Udev and has not yet
+ been booted, it is necessary to mount and populate <filename
+ class="directory">/dev</filename> manually. This is accomplished by bind
+ mounting the host system's <filename class="directory">/dev</filename>
+ directory. A bind mount is a special type of mount that allows you to
+ create a mirror of a directory or mount point to some other location. Use
+ the following command to achieve this:</para>
+
+<screen><userinput>mount -v --bind /dev $LFS/dev</userinput></screen>
+
+ </sect2>
+
+ <sect2 id="ch-system-kernfsmount">
+ <title>Mounting Virtual Kernel File Systems</title>
+
+ <para>Now mount the remaining virtual kernel filesystems:</para>
+
+<screen><userinput>mount -vt devpts devpts $LFS/dev/pts
+mount -vt tmpfs shm $LFS/dev/shm
+mount -vt proc proc $LFS/proc
+mount -vt sysfs sysfs $LFS/sys</userinput></screen>
+
+ </sect2>
+
+</sect1>
Modified: tags/6.8/BOOK/general.ent
===================================================================
--- trunk/BOOK/general.ent 2011-02-19 04:37:23 UTC (rev 9473)
+++ tags/6.8/BOOK/general.ent 2011-03-05 03:28:36 UTC (rev 9476)
@@ -1,5 +1,5 @@
-<!ENTITY version "SVN-20110218">
-<!ENTITY releasedate "February 18, 2011">
+<!ENTITY version "6.8">
+<!ENTITY releasedate "March 4, 2011">
<!ENTITY copyrightdate "1999-2011"><!-- jhalfs needs a literal dash, not
– -->
<!ENTITY milestone "6.8">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or
"x.y[-pre{x}]" -->
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
