[release-notes: 4/4] updated fedUP section, some other minor edits
Pete Travis
immanetize at fedoraproject.org
Tue Jan 8 07:44:41 UTC 2013
commit 32c882c912373e9fadb6b9f27314c54c6a75630a
Author: Pete Travis <immanetize at fedoraproject.org>
Date: Tue Jan 8 00:44:07 2013 -0700
updated fedUP section, some other minor edits
en-US/Desktop.xml | 14 +++++++++++---
en-US/File_Systems.xml | 2 +-
en-US/Installation.xml | 39 ++++++++++++++++++++++++---------------
3 files changed, 36 insertions(+), 19 deletions(-)
---
diff --git a/en-US/Desktop.xml b/en-US/Desktop.xml
index f660591..b261f0e 100644
--- a/en-US/Desktop.xml
+++ b/en-US/Desktop.xml
@@ -21,11 +21,15 @@
<section>
<title>Cinnamon</title>
- <para> Fedora users now have the option of using <application>Cinnamon</application>, an advanced desktop environment based on <application>GNOME3</application>. <application>Cinnamon</application> takes advantage of advanced features provided by the <application>GNOME</application> backend while providing users with a more traditional, accessible desktop experience. </para>
+ <para> Fedora users now have the option of using <application>Cinnamon</application>, an advanced desktop environment based on <application>GNOME3</application>. <application>Cinnamon</application> takes advantage of advanced features provided by the <application>GNOME</application> backend while providing users with a more traditional, accessible desktop experience. Install Cinnamon with the command:
+ <screen>
+ <command>yum groupinstall "Cinnamon Desktop"</command>
+ </screen>
+ </para>
</section>
<section>
<title><application>GNOME</application> </title>
- <para> Fedora 18 includes the newest <application>GNOME</application> release, version 3.6. You will notice these changes: </para>
+ <para>Fedora 18 includes the newest <application>GNOME</application> release, version 3.6. You will notice these changes: </para>
<itemizedlist>
<listitem>
<para>
@@ -155,7 +159,11 @@
</section>
<section>
<title><productname>MATE</productname></title>
- <para> This is the initial release of <productname>MATE Desktop</productname> for Fedora 18. It brings back a classic, intuitive, and easy to use desktop that users have been long requesting. Support for <application>MATE></application> in Fedora is provided in <varname>#fedora-mate</varname> or <varname>#mate</varname> on <orgname>irc.freenode.net</orgname> or through the Fedora bugzilla. </para>
+ <para> This is the initial release of <productname>MATE Desktop</productname> for Fedora 18. It brings back a classic, intuitive, and easy to use desktop that users have been long requesting. Install MATE by issuing the command:
+ <screen>
+ <command>yum groupinstall "MATE Desktop"</command>
+ </screen>
+ Support for <application>MATE</application> in Fedora is provided in <varname>#fedora-mate</varname> or <varname>#mate</varname> on <orgname>irc.freenode.net</orgname> or through the Fedora bugzilla. </para>
</section>
<section>
<title><productname>Xfce</productname></title>
diff --git a/en-US/File_Systems.xml b/en-US/File_Systems.xml
index 9a6a838..b2921a8 100644
--- a/en-US/File_Systems.xml
+++ b/en-US/File_Systems.xml
@@ -53,7 +53,7 @@
<section>
<title>/tmp on tmpfs </title>
<para>
- By default, <filename>/tmp</filename> on Fedora 18 will be on a tempfs. Storage of large temporary files should be done in <filename>/var/tmp</filename>. This will reduce the I/O generated on disks, increase SSD lifetime, save power, and improve performance of the <filename>/tmp</filename> filesystem.
+ By default, <filename>/tmp</filename> on Fedora 18 will be on a tmpfs. Storage of large temporary files should be done in <filename>/var/tmp</filename>. This will reduce the I/O generated on disks, increase SSD lifetime, save power, and improve performance of the <filename>/tmp</filename> filesystem.
</para>
</section>
</section>
diff --git a/en-US/Installation.xml b/en-US/Installation.xml
index 4c28c4b..9ec495f 100644
--- a/en-US/Installation.xml
+++ b/en-US/Installation.xml
@@ -34,13 +34,13 @@
<section>
<title>Installing grub</title>
<para>
- Fedora has used <application>GRUB2</application> for several releases. A great improvement over legacy <application>GRUB</application>, <application>GRUB2</application> supports more filesystems, virtual block devices such as <application>mdadm</application> and <application>LVM</application>, automatically scans for and configures available operating systems, and presents visual improvements. This added functionality makes the lives of Fedora users much easier, but comes at the cost of size. <application>GRUB2</application> fits in the <function>Master Boot Record</function> of a drive, but many filesystems do not leave room for <application>GRUB2</application> without special configuration.
+ Fedora has used <application>GRUB2</application> for several releases. A great improvement over legacy <application>GRUB</application>, <application>GRUB2</application> supports more filesystems, virtual block devices such as <application>mdadm</application> and <application>LVM</application>, automatically scans for and configures available operating systems, and presents visual improvements. This added functionality makes the lives of Fedora users much easier, but comes at the cost of size. <application>GRUB2</application> fits in the <function>Master Boot Record</function> of a drive, but many filesystems do not leave room on a partition for <application>GRUB2</application> without special configuration.
</para>
<para>
<application>Anaconda</application> now follows the recommendation of upstream <application>GRUB</application> developers and does not install <application>GRUB2</application> to partitions. Users with multiboot systems are encouraged to make use of GRUB's OS detection:
<screen>
<command>
- grub2-mkconfig -o /boot/grub2/grub.cfg
+ # grub2-mkconfig -o /boot/grub2/grub.cfg
</command>
</screen>
Users can also choose to skip bootloader installation with anaconda. GRUB can be manually installed to a partition with the <function>force</function> option, at the risk of filesystem damage, or another bootloader can be used.
@@ -64,7 +64,15 @@
<section>
<title>What is <application>fedUP</application> ?</title>
<para>
- <application>Fedup</application> is a new tool for upgrading Fedora installations that is replacing preupgrade and the DVD methods of upgrading that have been used in previous Fedora releases. It utilizes <application>systemd</application> for much of the upgrade functionality and will eventually be able to source packages from a DVD and use the regular install repos instead of needing a specially created side repo.
+ <application>Fedup</application> is a new tool for upgrading Fedora installations that is replacing preupgrade and the DVD methods of upgrading that have been used in previous Fedora releases. It utilizes <application>systemd</application> for much of the upgrade functionality and will eventually be able to source packages from a DVD and use the standard repository instead of an upgrade specific side repo.
+ </para>
+ </section>
+ <section>
+ <title>
+ Upgrade Sources
+ </title>
+ <para>
+ <application>FedUP</application> can use several sources to perform an upgrade. The Fedora mirrors are used by default. It can also use an installation image with the <function>--iso</function> argument, or use the <function>--device</function> to use a device or mountpoint as a source. Options are also available to enable or disable network repositories.
</para>
</section>
<section>
@@ -81,19 +89,12 @@
</para>
</section>
<section>
- <title>Using fedUP</title>
+ <title>Using FedUP</title>
<para>
Using the <application>fedup-cli</application> command, prepare the upgrade using the following command:
</para>
- <warning>
- <title>Using the correct URL</title>
- <para>
- To use the public Fedora resources to upgrade to Fedora 18 Beta, replace [insert-arch-here] below with the arch that you're upgrading - either x86_64 or i386. The final release should not require <function>--instrepo</function> to be explicitly declared.
- </para>
- </warning>
- <para>
- <screen><command>sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo=http://dl.fedoraproject.org/pub/fedora/linux/releases/test/18-Beta/Fedora/[insert-arch-here]/os/</command></screen>
- <!-- Fix and verify above URL for GA !! -->
+ <para>
+ <screen><command>sudo fedup-cli --network 18 --debuglog fedupdebug.log </command></screen>
</para>
<para>
At this point, the Fedora 17 system is ready for upgrade.
@@ -103,7 +104,7 @@
<section>
<title>Running the Upgrade</title>
<para>
- Once you reboot, there will be a 'System Upgrade' boot option at the grub prompt. Note that it is not the default and will need to be selected manually in order for the upgrade process to continue. Adding <command>plymouth.splash=fedup</command> to boot arguments for the Beta will show a graphical progress screen during upgrade. This will be the default for the final release. If all goes as it should, you might see a few boot messages but will eventually see the fedup plymouth theme.
+ Once you reboot, there will be a 'System Upgrade' boot option at the grub prompt. The system will boot into a special environment to perform the upgrade.The screen will show a graphical progress screen during upgrade.
</para>
<note>
<title>Go get some coffee</title>
@@ -144,5 +145,13 @@
<screen><command>journalctl -a -o cat</command></screen>
</para>
</section>
- </section>
+ <section>
+ <title>Third party modules</title>
+ <para>The <filename>initramfs</filename> created by FedUP may need to be rebuild in some cases where drivers are provided by a third party repository. If you experience issues with thrid party drivers after the upgrade, boot into a single or multi-user target and issue the following command:
+ <screen>
+ <command># dracut /boot/initramfs-$(uname -r).img $(uname -r)</command>
+ </screen>
+ </para>
+ </section>
+</section>
</section>
More information about the docs-commits
mailing list