[release-notes] Direct kernel boot
John J. McDonough
jjmcd at fedoraproject.org
Mon May 7 12:30:57 UTC 2012
commit d95a188182a085ade0a431c58dabc013d2dd9c93
Author: John J. McDonough <jjmcd at fedoraproject.org>
Date: Mon May 7 08:28:47 2012 -0400
Direct kernel boot
- Split out into separate section Installation.xml
- Added admonition
- Further refined prose
- Bump kernel version
en-US/Installation.xml | 101 ++++++++++++++++++++++++++++++++++++++++++++
en-US/Kernel.xml | 78 +---------------------------------
en-US/Release_Notes.ent | 2 +-
en-US/Release_Notes.xml | 3 +
en-US/Revision_History.xml | 1 +
5 files changed, 108 insertions(+), 77 deletions(-)
---
diff --git a/en-US/Installation.xml b/en-US/Installation.xml
new file mode 100644
index 0000000..f7f80f8
--- /dev/null
+++ b/en-US/Installation.xml
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook EBNF Module V1.1CR1//EN"
+"http://www.oasis-open.org/docbook/xml/mathml/1.1CR1/dbmathml.dtd">
+<?xml-stylesheet href="http://www.informatik.fh-wiesbaden.de/~werntges/home_t/proj/dbkcss102/wysiwygdocbook1.02/driver.css" type="text/css"?>
+
+
+
+
+
+<section>
+ <title>Installation</title>
+ <indexterm>
+ <primary>Boot</primary>
+ <secondary>PXE</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>Boot</primary>
+ <secondary>Direct kernel</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>Direct kernel boot</primary>
+ </indexterm>
+ <indexterm>
+ <primary>PXE</primary>
+ <secondary>Boot</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>repo</primary>
+ </indexterm>
+ <indexterm>
+ <primary>stage2</primary>
+ </indexterm>
+ <indexterm>
+ <primary>vmlinuz</primary>
+ </indexterm>
+ <indexterm>
+ <primary>initrd</primary>
+ </indexterm>
+ <para>
+ <warning>
+ <title>Changes to Direct Kernel Boot</title>
+ <para>
+ There are significant changes when installing via a direct
+ kernel boot such as PXE. Normal installation from
+ installation media is unaffected.
+ </para>
+ </warning>
+ </para>
+ <para>
+ Advanced users may do any of a number of styles of network
+ installation, generally involving setting up some minimal kernel
+ environment to perform the installation. This operation has
+ undergone significant changes in Fedora 17.
+ </para>
+ <para>
+ In F16, it is generally <emphasis>only</emphasis> necessary to
+ specify the kernel and initrd location, and the install would work
+ - <code>kernel/initrd</code> gets <code>stage1</code>, and
+ <code>stage1</code> gets <code>stage2</code>.
+ </para>
+ <para>
+ With noloader, this is no longer the case: when doing a direct
+ kernel boot, the location for <code>stage2</code> must be
+ specified. In other words: pass <code>repo=</code> or
+ <code>stage2=</code> (or <code>inst.repo=</code> or
+ <code>inst.stage2=</code>, as is now preferred), pointing to a
+ repository. If the <code>stage2</code> image is on one server
+ but then the installation packages are on some other server,
+ <code>stage2=</code> must be used: <code>repo=</code> should
+ only be used if the single server contains everything needed
+ for the install (both the <code>stage2</code> image
+ <emphasis>and</emphasis> all the packages to install). Note that
+ <code>stage2=</code> still expects to see a 'repository' tree,
+ you cannot just pass the path direct to a
+ <filename>squashfs.img</filename> file (which is how
+ <code>stage2=</code> worked when it previously existed in F15
+ and earlier).
+ </para>
+ <para>
+ For example:
+<screen>
+label linux
+kernel vmlinuz
+append initrd=initrd.img
+</screen>
+ is no longer valid. It is necessary to specify <code>repo</code>:
+<screen>
+label linux
+kernel vmlinuz
+append initrd=initrd.img repo=http://dl.fedoraproject.org/pub/fedora/linux/development/17/x86_64/os/
+</screen>
+ or <code>stage2</code>:
+<screen>
+label linux
+kernel vmlinuz
+append initrd=initrd.img stage2=http://my.internal.server/17/x86_64/os/
+</screen>
+ (or any other valid mirror).
+ </para>
+</section>
+
diff --git a/en-US/Kernel.xml b/en-US/Kernel.xml
index a5f7080..f1890dd 100644
--- a/en-US/Kernel.xml
+++ b/en-US/Kernel.xml
@@ -8,8 +8,7 @@
<section>
-
- <title>Kernel</title>
+ <title>Kernel</title>
<indexterm>
<primary>kernel</primary>
</indexterm>
@@ -20,79 +19,6 @@
<para>
Fedora &PRODVER; features the &KERNEL; kernel.
</para>
- <section>
- <title>Changes to direct kernel boot</title>
- <indexterm>
- <primary>Boot</primary>
- <secondary>PXE</secondary>
- </indexterm>
- <indexterm>
- <primary>Boot</primary>
- <secondary>Direct kernel</secondary>
- </indexterm>
- <indexterm>
- <primary>Direct kernel boot</primary>
- </indexterm>
- <indexterm>
- <primary>PXE</primary>
- <secondary>Boot</secondary>
- </indexterm>
- <indexterm>
- <primary>repo</primary>
- </indexterm>
- <indexterm>
- <primary>stage2</primary>
- </indexterm>
- <indexterm>
- <primary>vmlinuz</primary>
- </indexterm>
- <indexterm>
- <primary>initrd</primary>
- </indexterm>
- <para>
- In F16, you really <emphasis>only</emphasis> needed to specify
- the kernel and initrd location, and the install would work -
- <code>kernel/initrd</code> gets <code>stage1</code>, and <code>stage1</code> gets <code>stage2</code>.
- </para>
- <para>
- With noloader, this is no longer the case: when doing a direct
- kernel boot, the location for <code>stage2</code> must be
- specified. In other words: pass <code>repo=</code> or
- <code>stage2=</code> (or <code>inst.repo=</code> or
- <code>inst.stage2=</code>, as is now preferred), pointing to a
- repository. If the <code>stage2</code> image is on one server
- but then the installation packages are on some other server,
- <code>stage2=</code> must be used: <code>repo=</code> should
- only be used if the single server contains everything needed
- for the install (both the <code>stage2</code> image
- <emphasis>and</emphasis> all the packages to install). Note that
- <code>stage2=</code> still expects to see a 'repository' tree,
- you cannot just pass the path direct to a
- <filename>squashfs.img</filename> file (which is how
- <code>stage2=</code> worked when it previously existed in F15
- and earlier).
- </para>
- <para>
- For example:
-<screen>
-label linux
-kernel vmlinuz
-append initrd=initrd.img
-</screen>
- is no longer valid. It is necessary to specify <code>repo</code>:
-<screen>
-label linux
-kernel vmlinuz
-append initrd=initrd.img repo=http://dl.fedoraproject.org/pub/fedora/linux/development/17/x86_64/os/
-</screen>
- or <code>stage2</code>:
-<screen>
-label linux
-kernel vmlinuz
-append initrd=initrd.img stage2=http://my.internal.server/17/x86_64/os/
-</screen>
- (or any other valid mirror).
- </para>
- </section>
</section>
+
diff --git a/en-US/Release_Notes.ent b/en-US/Release_Notes.ent
index 37af9bd..d828cba 100644
--- a/en-US/Release_Notes.ent
+++ b/en-US/Release_Notes.ent
@@ -4,5 +4,5 @@
<!ENTITY HOLDER "Fedora Project Contributors">
<!ENTITY PRODVER "17">
<!ENTITY PREVVER "16">
-<!ENTITY KERNEL "3.3.0">
+<!ENTITY KERNEL "3.3.4">
diff --git a/en-US/Release_Notes.xml b/en-US/Release_Notes.xml
index 5f9df06..f93d0dc 100644
--- a/en-US/Release_Notes.xml
+++ b/en-US/Release_Notes.xml
@@ -30,6 +30,9 @@
<xi:include href="Kernel.xml"
xmlns:xi="http://www.w3.org/2001/XInclude">
</xi:include>
+ <xi:include href="Installation.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude">
+ </xi:include>
<!--
<xi:include href="Boot.xml"
xmlns:xi="http://www.w3.org/2001/XInclude">
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 03f4ee3..9c7c1d3 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -24,6 +24,7 @@
<member>BZ#819160 - Typo in Circuit Design</member>
<member>BZ#819161 - Correct URL in Circuit Design</member>
<member>BZ#819164 - typo in Embedded Development section</member>
+ <member>Bump kernel version to 3.3.4</member>
</simplelist>
</revdescription>
</revision>
More information about the docs-commits
mailing list