[release-notes] 02/02: Add a bunch of info about installer changes
by git repository hosting
This is an automated email from the git hooks/post-receive script.
pbokoc pushed a commit to branch master
in repository release-notes.
commit e16a323049fc348cda0cd99764357e6df7743458
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Fri Oct 7 00:17:52 2016 +0200
Add a bunch of info about installer changes
---
en-US/Installation.xml | 191 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 191 insertions(+)
diff --git a/en-US/Installation.xml b/en-US/Installation.xml
index 1663e3e..5858874 100644
--- a/en-US/Installation.xml
+++ b/en-US/Installation.xml
@@ -32,4 +32,195 @@
</para>
</warning>
</section>
+
+ <section id="installation-anaconda-changes">
+ <title>Installer Changes</title>
+ <para>
+ This section lists important changes made in this release to the <application>Anaconda</application> installer and related components such as <package>pykickstart</package>, <package>blivet</package>, or <package>initial-setup</package>.
+ </para>
+
+ <section id="installation-anaconda-general">
+ <title>General Installer Changes</title>
+ <para />
+ <variablelist>
+ <varlistentry>
+ <term>Static routes configured during installation are now automatically configured on the installed system</term>
+ <listitem>
+ <para>
+ Previously, static route configuration files were not copied from the installation environment to the installed system. Consequently, static route configuration during installation was lost after the installation finished. These files are now copied, and static routes configured during installation are automatically configured on the installed system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Anaconda can't be installed with DNF2</term>
+ <listitem>
+ <para>
+ bla bla
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Screen Access Manager is now available in Anaconda</term>
+ <listitem>
+ <para>
+ A Screen Access Manager (SAM) has been added to Anaconda. The SAM controls which screens will be shown and records spokes visited into a configuration file. This enables tools running before <application>Anaconda</application> to hide specific screens if needed, and post-installation tools can in turn read the list of visited screens and avoid asking the user to configure the same settings twice.
+ </para>
+ <para>
+ The configuration file specification is available on GitHub: <ulink url=" https://github.com/rhinstaller/anaconda/blob/master/docs/user-interaction..." />.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>The Anaconda repository now has contribution guidelines</term>
+ <listitem>
+ <para>
+ The <application>Anaconda</application> repository on GitHub now contains a <filename>CONTRIBUTING</filename> file, which provides guidance for anyone wishing to contribute to the repository. Anyone thinking of making a contribution to the installer is strongly encouraged to familiarize themselves with the file at <ulink url="https://github.com/rhinstaller/anaconda/blob/master/CONTRIBUTING" /> before submitting a pull request.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="installation-anaconda-interface">
+ <title>Changes to Anaconda Interfaces (GUI and TUI)</title>
+ <para />
+ <variablelist>
+ <varlistentry>
+ <term>Host name is no longer being set automatically when not specified</term>
+ <listitem>
+ <para>
+ Previously, if you did not provide any host name in the <guilabel>Network & Hostname</guilabel> screen (or in Kickstart), <application>Anaconda</application> set the target system's host name to one that was obtained during installation. In Fedora 25, the <guilabel>Network & Hostname</guilabel> no longer automatically pre-fills the host name; instead it always defaults to <literal>localhost.localdomain</literal>, which effectively that the installed system will obta [...]
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>NTP configuration is now supported in the text-based interface</term>
+ <listitem>
+ <para>
+ The text-based interface now allows you to configure NTP servers similar to the <guilabel>Date & Time</guilabel> screen in the graphical interface.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="installation-anaconda-kickstart">
+ <title>Kickstart Changes</title>
+ <para />
+ <variablelist>
+ <varlistentry>
+ <term>The timezone command can now be used without specifying a time zone</term>
+ <listitem>
+ <para>
+ Starting with Fedora 25, you can use the <command>timezone</command> Kickstart command without actually specifying a time zone, which was mandatory in previous releases. Every possible option for this command is therefore optional; however, if the command is present in the Kickstart file, at least one of the options must be used.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>New option: network --no-activate</term>
+ <listitem>
+ <para>
+ The <command>network</command> command has a new option: <option>--no-activate</option>. Use this option to prevent the configured device from activating automatically.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Commands targeting disk devices can now specify targets in multiple variants</term>
+ <listitem>
+ <para>
+ Storage-related commands which target disk devices, such as <command>clearpart</command>, <command>part</command>, or <command>ignoredisk</command>, can now have their targets specified in multiple variants using the pipe ("<literal>|</literal>") delimiter. For example:
+ </para>
+ <screen>part / --device=<literal>sd*|hd*|vda,/dev/vdc</literal></screen>
+ <para>
+ The above example will match either of <literal>sd*</literal>, <literal>hd*</literal>, or <literal>vda</literal> <emphasis>and</emphasis> <literal>/dev/vdc</literal>. The specified variants are processed from left to right, and at least one of them must match an existing device in order for the command to succeed.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>The bootloader command now behaves differently when the --boot-drive option is not specified</term>
+ <listitem>
+ <para>
+ If you use the <command>bootloader</command> command without specifying a drive using the <option>--boot-drive=</option> option, the bootloader will now be installed on a drive determined by the following rules in this particular order:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ If the <option>--driveorder=</option> option was used, the boot loader will be installed on the first valid device specified
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The first present and valid disk containing a <filename>/boot</filename> partition will be used
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If none of the above apply, then the first valid disk from the list of all detected disks will be used
+ </para>
+ </listitem>
+ </orderedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="installation-anaconda-boot-options">
+ <title>Changes in Boot Options</title>
+ <para />
+ <variablelist>
+ <varlistentry>
+ <term>New option: inst.nosave=</term>
+ <listitem>
+ <para>
+ You can use the <option>inst.nosave=</option> option to control which installation results will be saved to the installed system. Installation results are files generated after the installation, such as the <filename>anaconda-ks.cfg</filename> autogenerated Kickstart file. This option is useful when using <application>Anaconda</application> to create a disk image, as it allows you to prevent potentially sensitive information such as installation logs and internal URLs from [...]
+ </para>
+ <para>
+ Valid values for this option are <literal>input_ks</literal> (do not save the original Kickstart file), <literal>output_ks</literal> (do not save <filename>anaconda-ks.cfg</filename>), <literal>all_ks</literal> (save neither Kickstart file), <literal>logs</literal> (do not save log files), and <literal>all</literal> (do not save any of the previous).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>New option: inst.singlelang</term>
+ <listitem>
+ <para>
+ This option allows you to run the installation in single language mode - in other words, it disables language selection for the installer as well as for the installed system. If a language is specified at the same time as this using the <option>inst.lang=</option>, the specified language will be used during installation and configured on the target system. If no language was specified, <application>Anaconda</application> and the installed system will default to <literal>en- [...]
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="installation-anaconda-misc">
+ <title>Miscellaneous Changes in the Installation Process</title>
+ <para />
+ <variablelist>
+ <varlistentry>
+ <term>Initial Setup now logs unhandled exceptions to journal</term>
+ <listitem>
+ <para>
+ The <application>Initial Setup</application> utility now logs unhandled exceptions to journal in order to simplify debugging in the event of a fatal crash.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Driver updates can now replace already loaded modules</term>
+ <listitem>
+ <para>
+ Drivers loaded from a Driver Update Disk (DUD) using the <option>inst.dd=</option> boot option can now replace already loaded drivers in addition to providing new ones, as long as the original driver/module is not in use.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Logs describing the system's original state are now saved before Anaconda starts</term>
+ <listitem>
+ <para>
+ In order to preserve logs describing the system's original state, Anaconda now saves several logs (outputs of the <command>lsblk</command>, <command>dmesg</command>, and <command>lvmdump</command> commands) immediately upon starting, before it makes any changes to the system. This can provide additional debugging information as these logs describe the initial state of the system.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ </section>
+
</section>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.