docs-commits September 2014

docs-commits@lists.fedoraproject.org

5 participants
89 discussions

[install-guide/F21-rewrite] Small fix in Boot Options
by pbokoc 03 Sep '14

03 Sep '14

commit bb83868e89dcc2facfdf10a9c2513c2a54fd38bc Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Wed Sep 3 19:20:46 2014 +0200 Small fix in Boot Options en-US/Boot_Options.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml index d8ececf..35287bd 100644 --- a/en-US/Boot_Options.xml +++ b/en-US/Boot_Options.xml @@ -977,7 +977,7 @@ Password: </tbody> </tgroup> </table> - <important>  + <important>  <para> When performing a Kickstart installation, booting from local media and having the Kickstart file on local media as well, the network will not be initialized. This means that any other Kickstart options requiring network access, such as pre-installation or post-installation scripts accessing a network location, will cause the installation to fail. This is a known issue; see BZ#<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=1085310">1085310</ulink> for details. </para>

1 0

[install-guide/F21-rewrite] Adding a screenshot for memtest
by pbokoc 03 Sep '14

03 Sep '14

commit bf396d239386cd40f909e20a502fb4f1c6b18caf Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Wed Sep 3 19:20:33 2014 +0200 Adding a screenshot for memtest en-US/images/boot/memtest86.png | Bin 0 -> 48880 bytes 1 files changed, 0 insertions(+), 0 deletions(-) --- diff --git a/en-US/images/boot/memtest86.png b/en-US/images/boot/memtest86.png new file mode 100644 index 0000000..782c962 Binary files /dev/null and b/en-US/images/boot/memtest86.png differ

1 0

[install-guide/F21-rewrite] Moving back the Boot Options chapter
by pbokoc 03 Sep '14

03 Sep '14

commit 2d4e93e3ae0763e625f27b3368d401fba3383b31 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Wed Sep 3 19:17:47 2014 +0200 Moving back the Boot Options chapter en-US/Boot_Options.xml | 1260 ++++++++++++++++++++++++++++++++++++++++++++++-- 1 files changed, 1216 insertions(+), 44 deletions(-) --- diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml index c6af906..d8ececf 100644 --- a/en-US/Boot_Options.xml +++ b/en-US/Boot_Options.xml @@ -4,49 +4,1221 @@ %BOOK_ENTITIES; ]> <chapter id="chap-anaconda-boot-options"> - <title>Boot Options</title> - <para> - intro text - </para> - - <section id="sect-boot-options-installer"> - <title>Configuring the Installation System at the Boot Menu</title> - <para> - text - </para> - </section> - - <section id="sect-boot-options-deprecated-removed"> - <title>Deprecated and Removed Boot Options</title> - <para> - text - </para> - </section> - - <section id="sect-boot-options-maintenance"> - <title>Using the Maintenance Boot Modes</title> - - <section id="sect-boot-options-memtest"> - <title>Loading the Memory (RAM) Testing Mode</title> - <para> - text - </para> - </section> - - <section id="sect-boot-options-mediacheck"> - <title>Verifying Boot Media</title> - <para> - text - </para> - </section> - - <section id="sect-boot-options-rescue"> - <title>Booting Your Computer in Rescue Mode</title> - <para> - text - </para> - </section> - - </section> + <title>Boot Options</title> + <para> + The <application>Anaconda</application> installer includes a range of boot options for administrators, which modify the default behavior of the installation program by enabling or disabling certain functions. To use one or more boot options, you either have to boot from installation media and append these options at the boot menu (see <xref linkend="sect-boot-menu" />), or you must add them into your PXE server configuration file if you are booting from a network (see <xref linkend="chap-pxe-server-setup" />). + </para> + <para> + You can use multiple options at the same time; in that case, separate them by a single space. + </para> + <para> + There are two basic types of options described in this chapter: + </para> + <itemizedlist> + <listitem> + <para> + Options presented as ending with an "equals" sign (<literal>=</literal>) require a value to be specified - they cannot be used on their own. For example, the <option>inst.vncpassword=</option> option must also contain a value (in this case, a password). The correct form is therefore <option>inst.vncpassword=<replaceable>password</replaceable></option>. On its own, without a password specified, the option is invalid. + </para> + </listitem> + <listitem> + <para> + Options presented without the "<literal>=</literal>" sign do not accept any values or parameters. For example, the <option>rd.live.check</option> option forces <application>Anaconda</application> to verify the installation media before starting the installation; if this option is present, the check will be performed, and if it is not present, the check will be skipped. + </para> + </listitem> + </itemizedlist> + <para> + In addition to the options described in this chapter, the boot prompt also accepts <application>dracut</application> kernel options. A list of these options is available as the <systemitem>dracut.cmdline(7)</systemitem> man page. + </para> + <note> + <para> + Boot options specific to the installation program always start with <literal>inst.</literal> in this guide. Currently, this prefix is optional - for example, <option>resolution=1024x768</option> will work exactly the same as <option>inst.resolution=1024x768</option>. However, it is expected that the <literal>inst.</literal> prefix will be mandatory in future releases. + </para> + </note> + + <section id="sect-boot-options-installer"> + <title>Configuring the Installation System at the Boot Menu</title> + <para> + The exact way to specify custom boot options is differs based on your system's architecture, firmware and the method you use to boot the installation. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; if you are booting from a network using a PXE server, you must add boot options into the boot loader configuration file before you boot the installation system. For specific instructions, see <xref linkend="sect-boot-menu" /> if you are booting from local media, and <xref linkend="chap-pxe-server-setup" /> if you are booting from a server. + </para> + </section> + + <section id="sect-boot-options-available"> + <title>Available Boot Options</title> + <para> + The following options are available in &PRODUCT;: + </para> + + <section id="sect-boot-options-sources"> + <title>Specifying the Installation Source</title> + <variablelist> + <varlistentry> + <term><option>inst.repo=</option></term> + <listitem> + <para> + Specifies the installation source - that is, a location where the installation program can find the images and packages it requires. For example: + </para> + <screen><option>inst.repo=cdrom</option></screen> + <para> + The source must be either: + </para> + <itemizedlist> + <listitem> + <para> + an installable tree, which is a directory structure containing the installation program's images, packages and repodata as well as a valid <filename>.treeinfo</filename> file + </para> + </listitem> + <listitem> + <para> + a DVD (a physical disk present in the system's DVD drive) + </para> + </listitem> + <listitem> + <para> + an ISO image of the full &PRODUCT; installation DVD, placed on a hard drive or a network location accessible from the installation system + </para> + </listitem> + </itemizedlist> + <para> + This option allows for the configuration of different installation methods using different formats. The syntax is described in the table below. + </para> + <table id="tabl-boot-options-sources"> + <title>Installation Sources</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="3*" /> + <thead> + <row> + <entry> + Installation source + </entry> + <entry> + Option format + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Any CD/DVD drive + </entry> + <entry> + <option>inst.repo=cdrom</option> + </entry> + </row> + <row> + <entry> + Specific CD/DVD drive + </entry> + <entry> + <option>inst.repo=cdrom:<replaceable>device</replaceable></option> + </entry> + </row> + <row> + <entry> + Hard Drive + </entry> + <entry> + <option>inst.repo=hd:<replaceable>device</replaceable>:/<replaceable>path</replaceable></option> + </entry> + </row> + <row> + <entry> + HTTP Server + </entry> + <entry> + <option>inst.repo=http://<replaceable>host</replaceable>/<replaceable>path</replaceable></option> + </entry> + </row> + <row> + <entry> + HTTPS Server + </entry> + <entry> + <option>inst.repo=https://<replaceable>host</replaceable>/<replaceable>path</replaceable></option> + </entry> + </row> + <row> + <entry> + FTP Server + </entry> + <entry> + <option>inst.repo=ftp://<replaceable>username</replaceable>:<replaceable>password</replaceable>@<replaceable>host</replaceable>/<replaceable>path</replaceable></option> + </entry> + </row> + <row> + <entry> + NFS Server + </entry> + <entry> + <option>inst.repo=nfs:[<replaceable>options</replaceable>:]<replaceable>server</replaceable>:/<replaceable>path</replaceable></option> + <footnote> + <para> + This option uses NFS protocol version 3 by default. To use a different version, add <option>+nfsvers=<replaceable>X</replaceable></option> to <replaceable>options</replaceable>. + </para> + </footnote> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + Disk device names may be specified using the following formats: + </para> + <itemizedlist> + <listitem> + <para> + Kernel device name, for example <systemitem>/dev/sda1</systemitem> or <systemitem>sdb2</systemitem> + </para> + </listitem> + <listitem> + <para> + File system label, for example <systemitem>LABEL=Flash</systemitem> or <systemitem>LABEL=RHEL7</systemitem> + </para> + </listitem> + <listitem> + <para> + File system UUID, for example <systemitem>UUID=8176c7bf-04ff-403a-a832-9557f94e61db</systemitem> + </para> + </listitem> + </itemizedlist> + <para> + Non-alphanumeric characters must be represented as <literal>\x<replaceable>NN</replaceable></literal>, where <replaceable>NN</replaceable> is the hexadecimal representation of the character. For example, <literal>\x20</literal> is a white space ("<literal> </literal>"). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.stage2=</option></term> + <listitem> + <para> + Specifies the location of the installation program runtime image to be loaded. The syntax is the same as in <xref linkend="tabl-boot-options-sources" />. This option will ignore everything except for the image itself, it is not possible to use it to specify the location of packages. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.dd=</option></term> + <listitem> + <para> + If you need to perform a driver update during the installation, use the <option>inst.dd=</option> option. It can be used multiple times. The location of a driver RPM package can be specified using any of the formats described in <xref linkend="tabl-boot-options-sources" />. With the exception of the <option>inst.dd=cdrom</option> option, the device name must always be specified. For example: + </para> + <screen><option>inst.dd=/dev/sdb1</option></screen> + <para> + Using this option without any parameters (only as <option>inst.dd</option>) will prompt the installation program to ask you for a driver update disk with an interactive menu. + </para> + <para> + Note that you should never attempt to perform a driver update during the installation unless a missing our faulty driver is preventing you from completing the installation. Updating drivers which are not essential during the installation should always be performed after the system is installed. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-kickstart"> + <title>Kickstart Boot Options</title> + <variablelist> + <varlistentry> + <term><option>inst.ks=</option></term> + <listitem> + <para> + Gives the location of a Kickstart file to be used to automate the installation. Locations can be specified using any of the formats valid for <option>inst.repo=</option>. See <xref linkend="tabl-boot-options-sources" /> for valid formats. + </para> + <para> + If you only specify a device and not a path, the installation program will look for the Kickstart file in <filename>/ks.cfg</filename> on the specified device. If you use this option without specifying a device, the installation program will use the following: + </para> + <screen><option>inst.ks=nfs:<replaceable>next-server</replaceable>:/<replaceable>filename</replaceable></option></screen> + <para> + In the above example, <replaceable>next-server</replaceable> is the DHCP <literal>next-server</literal> option or the IP address of the DHCP server itself, and <replaceable>filename</replaceable> is the DHCP <literal>filename</literal> option, or <filename>/kickstart/</filename>. If the given file name ends with the <literal>/</literal> character, <literal><replaceable>ip</replaceable>-kickstart</literal> is appended. For example: + </para> + <table id="tabl-default-kickstart-location"> + <title>Default Kickstart File Location</title> + <tgroup cols="3"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="1*" /> + <colspec colnum="3" colwidth="3*" /> + <thead> + <row> + <entry> + DHCP server address + </entry> + <entry> + Client address + </entry> + <entry> + Kickstart file location + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <systemitem class="ipaddress">192.168.122.1</systemitem> + </entry> + <entry> + <systemitem class="ipaddress">192.168.122.100</systemitem> + </entry> + <entry> + <systemitem class="ipaddress">192.168.122.1</systemitem>:<filename>/kickstart/192.168.122.100-kickstart</filename> + </entry> + </row> + </tbody> + </tgroup> + </table> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.ks.sendmac</option></term> + <listitem> + <para> + Adds headers to outgoing <systemitem class="protocol">HTTP</systemitem> requests with the MAC addresses of all network interfaces. For example: + </para> + <screen><literal>X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab</literal></screen> + <para> + This can be useful when using <option>inst.ks=http</option> to provision systems. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.ks.sendsn</option></term> + <listitem> + <para> + Adds a header to outgoing <systemitem class="protocol">HTTP</systemitem> requests. This header will contain the system's serial number, read from <filename>/sys/class/dmi/id/product_serial</filename>. The header has the following syntax: + </para> + <screen><literal>X-System-Serial-Number: <replaceable>R8VA23D</replaceable></literal></screen> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-display"> + <title>Console, Environment and Display Options</title> + <variablelist> + <varlistentry> + <term><option>console=</option></term> + <listitem> + <para> + This kernel option specifies a device to be used as the primary console. For example, to use a console on the first serial port, use <option>console=ttyS0</option>. This option should be used along with the <option>inst.text</option> option. + </para> + <para> + You can use this option multiple times. In that case, the boot message will be displayed on all specified consoles, but only the last one will be used by the installation program afterwards. For example, if you specify <option>console=ttyS0 console=ttyS1</option>, the installation program will only use <literal>ttyS1</literal>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>noshell</option></term> + <listitem> + <para> + Disables access to the root shell during the installation. This is useful with automated (Kickstart) installations - if you use this option, a user can watch the installation progress, but they cannot interfere with it by accessing the root shell by pressing <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.lang=</option></term> + <listitem> + <para> + Sets the language to be used during the installation. Language codes are the same as the ones used in the <command>lang</command> Kickstart command as described in <xref linkend="sect-kickstart-commands" />. On systems where the <package>system-config-language</package> package is installed, a list of valid values can also be find in <filename>/usr/share/system-config-language/locale-list</filename>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.geoloc=</option></term> + <listitem> + <para> + Configures geolocation usage in the installation program. Geolocation is used to pre-set the language and time zone, and uses the following syntax: <option>inst.geoloc=<replaceable>value</replaceable></option> + </para> + <para> + The <replaceable>value</replaceable> parameter can be any of the following: + </para> + <table id="tabl-boot-options-geoloc"> + <title>Valid Values for the inst.geoloc Option</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="2*" /> + <tbody> + <row> + <entry> + Disable geolocation + </entry> + <entry> + <option>inst.geoloc=0</option> + </entry> + </row> + <row> + <entry> + Use the Fedora GeoIP API + </entry> + <entry> + <option>inst.geoloc=provider_fedora_geoip</option> + </entry> + </row> + <row> + <entry> + Use the Hostip.info GeoIP API + </entry> + <entry> + <option>inst.geoloc=provider_hostip</option> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + If this option is not specified, <application>Anaconda</application> will use <literal>provider_fedora_geoip</literal>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.keymap=</option></term> + <listitem> + <para> + Specifies the keyboard layout to be used by the installation program. Layout codes are the same as the ones used in the <command>keyboard</command> Kickstart command as described in <xref linkend="sect-kickstart-commands" />. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.text</option></term> + <listitem> + <para> + Forces the installation program to run in text mode instead of graphical mode. The text user interface is limited, for example, it does not allow you to modify the partition layout or set up LVM. When installing a system on a machine with a limited graphical capabilities, it is recommended to use VNC as described in <xref linkend="sect-boot-options-vnc" />. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.cmdline</option></term> + <listitem> + <para> + Forces the installation program to run in command line mode. This mode does not allow any interaction, all options must be specified in a Kickstart file or on the command line. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.graphical</option></term> + <listitem> + <para> + Forces the installation program to run in graphical mode. This mode is the default. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.resolution=</option></term> + <listitem> + <para> + Specifies the screen resolution in graphical mode. The format is <replaceable>N</replaceable>x<replaceable>M</replaceable>, where <replaceable>N</replaceable> is the screen width and <replaceable>M</replaceable> is the screen height (in pixels). The lowest supported resolution is <literal>640x480</literal>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.headless</option></term> + <listitem> + <para> + Specifies that the machine being installed onto does not have any display hardware. In other words, this options prevents the installation program from trying to detect a screen. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.xdriver=</option></term> + <listitem> + <para> + Specifies the name of the <systemitem>X</systemitem> driver to be used both during the installation and on the installed system. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.usefbx</option></term> + <listitem> + <para> + Tells the installation program to use the frame buffer <systemitem>X</systemitem> driver instead of a hardware-specific driver. This option is equivalent to <option>inst.xdriver=fbdev</option>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>modprobe.blacklist=</option></term> + <listitem> + <para> + Blacklists (completely disables) one or more drivers. Drivers (mods) disabled using this option will be prevented from loading when the installation starts, and after the installation finishes, the installed system will keep these settings. The blacklisted drivers can then be found in the <filename class="directory">/etc/modprobe.d/</filename> directory. + </para> + <para> + Use a comma-separated list to disable multiple drivers. For example: + </para> + <screen><option>modprobe.blacklist=ahci,firewire_ohci</option></screen> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.sshd</option></term> + <listitem> + <para> + Starts the <systemitem class="service">sshd</systemitem> service during the installation, which allows you to connect to the system during the installation using <systemitem class="protocol">SSH</systemitem> and monitor its progress. For more information on <systemitem class="protocol">SSH</systemitem>, see the <systemitem>ssh(1)</systemitem> man page and the corresponding chapter in the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="httpL//docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>. + </para> + <note> + <para> + During the installation, the <systemitem class="username">root</systemitem> account has no password by default. You can set a root password to be used during the installation with the <command>sshpw</command> Kickstart command as described in <xref linkend="sect-kickstart-commands" />. + </para> + </note> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-network"> + <title>Network Boot Options</title> + <para> + Initial network initialization is handled by <application>dracut</application>. This section only lists some of the more commonly used options; for a complete list, see the <systemitem>dracut.cmdline(7)</systemitem> man page. Additional information on networking is also available in the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at the <ulink url="httpL//docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>. + </para> + <variablelist> + <varlistentry> + <term><option>ip=</option></term> + <listitem> + <para> + Configures one or more network interfaces. To configure multiple interfaces, use the <literal>ip</literal> option multiple times - once for each interface. If multiple interfaces are configured, you must specify a primary boot interface using the <option>bootdev</option> option described below. + </para> + <para> + The following table lists valid values for this option: + </para> + <table id="tabl-boot-options-network-formats"> + <title>Network Interface Configuration Formats</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="2*" /> + <thead> + <row> + <entry> + Configuration Method + </entry> + <entry> + Option format + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Automatic configuration of any interface + </entry> + <entry> + <option>ip=<replaceable>method</replaceable></option> + </entry> + </row> + <row> + <entry> + Automatic configuration of a specific interface + </entry> + <entry> + <option>ip=<replaceable>interface</replaceable>:<replaceable>method</replaceable></option> + </entry> + </row> + <row> + <entry> + Static configuration + </entry> + <entry> + <option>ip=<replaceable>ip</replaceable>::<replaceable>gateway</replaceable>:<replaceable>netmask</replaceable>:<replaceable>hostname</replaceable>:<replaceable>interface</replaceable>:none</option> + </entry> + </row> + <row> + <entry> + Automatic configuration of a specific interface with an override + <footnote> + <para> + Brings up the specified interface using the specified method of automatic configuration, such as <literal>dhcp</literal>, but overrides the automatically obtained IP address, gateway, netmask, hostname or other specified parameter. All parameters are optional; only specify the ones you wish to override and automatically obtained values will be used for the others. + </para> + </footnote> + </entry> + <entry> + <option>ip=<replaceable>ip</replaceable>::<replaceable>gateway</replaceable>:<replaceable>netmask</replaceable>:<replaceable>hostname</replaceable>:<replaceable>interface</replaceable>:<replaceable>method</replaceable>:<replaceable>mtu</replaceable></option> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + The <option>method</option> parameter can be any the following: + </para> + <table id="tabl-boot-options-network-autoconf"> + <title>Automatic Interface Configuration Methods</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="1*" /> + <thead> + <row> + <entry> + Automatic configuration method + </entry> + <entry> + Value + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + DHCP + </entry> + <entry> + <literal>dhcp</literal> + </entry> + </row> + <row> + <entry> + IPv6 DHCP + </entry> + <entry> + <literal>dhcp6</literal> + </entry> + </row> + <row> + <entry> + IPv6 automatic configuration + </entry> + <entry> + <literal>auto6</literal> + </entry> + </row> + <row> + <entry> + iBFT (iSCSI Boot Firmware Table) + </entry> + <entry> + <literal>ibft</literal> + </entry> + </row> + </tbody> + </tgroup> + </table> + <note> + <para> + If you use a boot option which requires network access, such as <option>inst.ks=http://<replaceable>host</replaceable>:/<replaceable>path</replaceable></option>, without specifying the <option>ip</option> option, the installation program will use <option>ip=dhcp</option>. + </para> + </note> + <para> + In the above tables, the <replaceable>ip</replaceable> parameter specifies the client's IP address. <systemitem class="protocol">IPv6</systemitem> addresses can be specified by putting them in square brackets, for example, <literal>[2001:DB8::1]</literal>. + </para> + <para> + The <replaceable>gateway</replaceable> parameter is the default gateway. IPv6 addresses are accepted here as well. + </para> + <para> + The <replaceable>netmask</replaceable> parameter is the netmask to be used. This can either be a full netmask (for example <literal>255.255.255.0</literal>) or a prefix (for example <literal>64</literal>). + </para> + <para> + The <replaceable>hostname</replaceable> parameter is the host name of the client system. This parameter is optional. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>nameserver=</option></term> + <listitem> + <para> + Specifies the address of the name server. This option can be used multiple times. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>bootdev=</option></term> + <listitem> + <para> + Specifies the boot interface. This option is mandatory if you use more than one <option>ip</option> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>ifname=</option></term> + <listitem> + <para> + Assigns a given interface name to a network device with a given MAC address. Can be used multiple times. The syntax is <option>ifname=<replaceable>interface</replaceable>:<replaceable>MAC</replaceable></option>. For example: + </para> + <screen><option>ifname=eth0:01:23:45:67:89:ab</option></screen> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.dhcpclass=</option></term> + <listitem> + <para> + Specifies the DHCP vendor class identifier. The <systemitem class="service">dhcpd</systemitem> service will see this value as <literal>vendor-class-identifier</literal>. The default value is <literal>anaconda-$(uname -srm)</literal>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>vlan=</option></term> + <listitem> + <para> + Sets up a Virtual LAN (VLAN) device on a specified interface with a given name. The syntax is <option>vlan=<replaceable>name</replaceable>:<replaceable>interface</replaceable></option>. For example: + </para> + <screen><option>vlan=vlan5:em1</option></screen> + <para> + The above will set up a VLAN device named <literal>vlan5</literal> on the <literal>em1</literal> interface. The <replaceable>name</replaceable> can take the following forms: + </para> + <table id="tabl-boot-options-network-vlan-names"> + <title>VLAN Device Naming Conventions</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="1*" /> + <thead> + <row> + <entry> + Naming scheme + </entry> + <entry> + Example + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + VLAN_PLUS_VID + </entry> + <entry> + <literal>vlan0005</literal> + </entry> + </row> + <row> + <entry> + VLAN_PLUS_VID_NO_PAD + </entry> + <entry> + <literal>vlan5</literal> + </entry> + </row> + <row> + <entry> + DEV_PLUS_VID + </entry> + <entry> + <literal>em1.0005</literal>. + </entry> + </row> + <row> + <entry> + DEV_PLUS_VID_NO_PAD + </entry> + <entry> + <literal>em1.5</literal>. + </entry> + </row> + </tbody> + </tgroup> + </table> + </listitem> + </varlistentry> + <varlistentry> + <term><option>bond=</option></term> + <listitem> + <para> + Set up a bonding device with the following syntax: <option>bond=<replaceable>name</replaceable>[:<replaceable>slaves</replaceable>][:<replaceable>options</replaceable>]</option>. Replace <replaceable>name</replaceable> with the bonding device name, <replaceable>slaves</replaceable> with a comma-separated list of physical (ethernet) interfaces, and <replaceable>options</replaceable> with a comma-separated list of bonding options. For example: + </para> + <screen><option>bond=bond0:em1,em2:mode=active-backup,tx_queues=32,downdelay=5000</option></screen> + <para> + For a list of available options, execute the <command>modinfo bonding</command> command. + </para> + <para> + Using this option without any parameters will assume <option>bond=bond0:eth0,eth1:mode=balance-rr</option>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>team=</option></term> + <listitem> + <para> + Set up a team device with the following syntax: <option>team=<replaceable>master</replaceable>:<replaceable>slaves</replaceable></option>. Replace <replaceable>master</replaceable> with the name of the master team device and <replaceable>slaves</replaceable> with a comma-separated list of physical (ethernet) devices to be used as slaves in the team device. For example: + </para> + <screen><option>team=team0:em1,em2</option></screen> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-advanced"> + <title>Advanced Installation Options</title> + <variablelist> + <varlistentry> + <term><option>inst.multilib</option></term> + <listitem> + <para> + Configure the system for multilib packages (that is, to allow installing 32-bit packages on a 64-bit x86 system) and install packages specified in this section as such. + </para> + <para> + Normally, on an AMD64 or Intel 64 system, only packages for this architecture (marked as <literal>x86_64</literal>) and packages for all architectures (marked as <literal>noarch</literal> would be installed. When you use this option, packages for 32-bit AMD or Intel systems (marked as <literal>i686</literal>) will be automatically installed as well if available. + </para> + <para> + This only applies to packages directly specified in the <literal>%packages</literal> section. If a package is only installed as a dependency, only the exact specified dependency will be installed. For example, if you are installing package <package>foo</package> which depends on package <package>bar</package>, the former will be installed in multiple variants, while the latter will only be installed in variants specifically required. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.gpt</option></term> + <listitem> + <para> + Force the installation program to install partition information into a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is meaningless on UEFI-based systems, unless they are in BIOS compatibility mode. + </para> + <para> + Normally, BIOS-based systems and UEFI-based systems in BIOS compatibility mode will attempt to use the MBR schema for storing partitioning information, unless the disk is larger than 2 TB. Using this option will change this behavior, allowing a GPT to be written even to disks smaller than 2 TB. + </para> +  + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.zram</option></term> + <listitem> + <para> + This option controls the usage of <firstterm>zRAM</firstterm> swap during the installation. It creates a compressed block device inside the system RAM and uses it for swap space instead of the hard drive. This allows the installer to essentially increase the amount of memory available, which makes the installation faster on systems with low memory. + </para> + <para> + By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabled on systems with more than 2 GB of memory. You can use this option to change this behavior - on a system with more than 2 GB RAM, use <option>inst.zram=1</option> to enable it, and on systems with 2 GB or less memory, use <option>inst.zram=0</option> to disable this feature. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-vnc"> + <title>Enabling Remote Access Using VNC</title> + <para> + The following options are necessary to configure <application>Anaconda</application> for remote graphical installation. See <xref linkend="chap-vnc-installations" /> for more details. + </para> + <variablelist> + <varlistentry> + <term><option>inst.vnc</option></term> + <listitem> + <para> + Specifies that the installation program's graphical interface should be run in a <systemitem class="protocol">VNC</systemitem> session. If you specify this option, you will need to connect to the system using a <systemitem class="protocol">VNC</systemitem> client application to be able to interact with the installation program. <systemitem class="protocol">VNC</systemitem> sharing is enabled, so multiple clients can connect to the system at the same time. + </para> + <note> + <para> + A system installed using <systemitem class="protocol">VNC</systemitem> will start in text mode by default. + </para> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.vncpassword=</option></term> + <listitem> + <para> + <systemitem class="protocol">VNC</systemitem> server used by the installation program. Any <systemitem class="protocol">VNC</systemitem> client attempting to connect to the system will have to provide the correct password to gain access. For example, <option>inst.vncpassword=<replaceable>testpwd</replaceable></option> will set the password to <literal>testpwd</literal>. The password must be between 6 and 8 characters long. + </para> + <note> + <para> + If you specify an invalid password (one that is too short or too long), you will be prompted to specify a new one by a message from the installation program: + </para> + <screen> +VNC password must be six to eight characters long. +Please enter a new one, or leave blank for no password. + +Password: + </screen> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.vncconnect=</option></term> + <listitem> + <para> + Connect to a listening <systemitem class="protocol">VNC</systemitem> client at a specified host and port once the installation starts. The correct syntax is <option>inst.vncconnect=<replaceable>host</replaceable>:<replaceable>port</replaceable></option>. The <replaceable>port</replaceable> parameter is optional - if you do not specify one, the installation program will use <literal>5900</literal>. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-debug"> + <title>Debugging and Troubleshooting</title> + <variablelist> + <varlistentry> + <term><option>inst.updates=</option></term> + <listitem> + <para> + Specifies the location of the <filename>updates.img</filename> file to be applied to the installation program runtime. The syntax is the same as in the <option>inst.repo</option> option - see <xref linkend="tabl-boot-options-sources" /> for details. In all formats, if you do not specify a file name but only a directory, the installation program will look for a file named <filename>updates.img</filename>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.loglevel=</option></term> + <listitem> + <para> + Specifies the minimum level for messages to be logged on a terminal. This only concerns real-time logging in a terminal; log files will always contain messages of all levels. + </para> + <para> + Possible values for this option from the lowest to highest level are: <literal>debug</literal>, <literal>info</literal>, <literal>warning</literal>, <literal>error</literal> and <literal>critical</literal>. The default value is <literal>info</literal>, which means that by default, the logging terminal will display messages ranging from <literal>info</literal> to <literal>critical</literal>, but not <literal>debug</literal>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.syslog=</option></term> + <listitem> + <para> + Once the installation starts, this options sends log messages to the syslog process on the specified host. The remote syslog process must be configured to accept incoming connections.  + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>inst.virtiolog=</option></term> + <listitem> + <para> + Specifies a <systemitem>virtio</systemitem> port (a character device at <filename>/dev/virtio-ports/<replaceable>name</replaceable></filename>) to be used for forwarding logs. The default value is <literal>org.fedoraproject.anaconda.log.0</literal>; if this port is present, it will be used. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + </section> + + <section id="sect-boot-options-deprecated"> + <title>Deprecated Boot Options</title> + <para> + Options in this list are <emphasis>deprecated</emphasis>. They will still work, but there are other options which offer the same functionality and should be preferred. Using deprecated options is not recommended and they are expected to be removed in future releases. + </para> + <note> + <para> + Note that as described in the introduction to this chapter, options specific to the installation program now use the <literal>inst.</literal> prefix. For example, the <option>vnc=</option> option is considered deprecated and replaced by the <option>inst.vnc=</option> option. However, these changes are not listed here. + </para> + </note> + <variablelist> + <varlistentry> + <term><option>method=</option></term> + <listitem> + <para> + Configured the installation method. Use the <option>inst.repo=</option> option instead. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>repo=nfsiso:<replaceable>server</replaceable>:/<replaceable>path</replaceable></option></term> + <listitem> + <para> + In NFS installations, specified that the target is an ISO image located on an NFS server instead of an installable tree. The difference is now detected automatically, which means this option is the same as <option>inst.repo=nfs:<replaceable>server</replaceable>:/<replaceable>path</replaceable></option>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>dns=</option></term> + <listitem> + <para> + Configured the Domain Name Server (DNS). Use the <option>nameserver=</option> option instead. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>netmask=</option>, <option>gateway=</option>, <option>hostname=</option>, <option>ip=</option>, <option>ipv6=</option></term> + <listitem> + <para> + These options have been consolidated under the <option>ip=</option> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>ksdevice=</option></term> + <listitem> + <para> + Select network device to be used at early stage of installation. Different values have been replaced with different options; see the table below. + </para> + <table id="tabl-boot-options-ksdevice"> + <title>Automatic Interface Configuration Methods</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*" /> + <colspec colnum="2" colwidth="2*" /> + <thead> + <row> + <entry> + Value + </entry> + <entry> + Current behavior + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Not present + </entry> + <entry> + All devices are attempted to be activated using <systemitem class="protocol">dhcp</systemitem>, unless desired device and configuration is specified by <option>ip=</option> option and/or the <option>BOOTIF</option> option. + </entry> + </row> + <row> + <entry> + <option>ksdevice=link</option> + </entry> + <entry> + Similar to the above, with the difference that network will always be activated in the initramfs, whether it is needed or not. The supported <option>rd.neednet</option> <application>dracut</application> option should be used to achieve the same result. + </entry> + </row> + <row> + <entry> + <option>ksdevice=bootif</option> + </entry> + <entry> + Ignored (the BOOTID= option is used by default when specified) + </entry> + </row> + <row> + <entry> + <option>ksdevice=ibft</option> + </entry> + <entry> + Replaced with the <option>ip=ibft</option> <application>dracut</application> option + </entry> + </row> + <row> + <entry> + <option>ksdevice=<replaceable>MAC</replaceable></option> + </entry> + <entry> + Replaced with <option>BOOTIF=<replaceable>MAC</replaceable></option> + </entry> + </row> + <row> + <entry> + <option>ksdevice=<replaceable>device</replaceable></option> + </entry> + <entry> + Replaced by specifying the device name using the <option>ip=</option> <application>dracut</application> option. + </entry> + </row> + </tbody> + </tgroup> + </table> + <important>  + <para> + When performing a Kickstart installation, booting from local media and having the Kickstart file on local media as well, the network will not be initialized. This means that any other Kickstart options requiring network access, such as pre-installation or post-installation scripts accessing a network location, will cause the installation to fail. This is a known issue; see BZ#<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=1085310">1085310</ulink> for details. + </para> + <para> + To work around this issue, either use the <option>ksdevice=link</option> boot option, or add the <option>--device=link</option> option to the <command>network</command> command in your Kickstart file. + </para> + </important> + </listitem> + </varlistentry> + <varlistentry> + <term><option>blacklist=</option></term> + <listitem> + <para> + Used to disable specified drivers. This is now handled by the <option>modprobe.blacklist=</option> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>nofirewire=</option></term> + <listitem> + <para> + Disabled support for the FireWire interface. You can disable the FireWire driver (<literal>firewire_ohci</literal>) by using the <option>modprobe.blacklist=</option> option instead: + </para> + <screen> +<option>modprobe.blacklist=firewire_ohci</option> + </screen> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-removed"> + <title>Removed Boot Options</title> + <para> + The following options are removed. They were present in previous releases of &PRODUCT;, but they cannot be used anymore. + </para> + <variablelist> + <varlistentry> + <term><option>askmethod</option>, <option>asknetwork</option></term> + <listitem> + <para> + The installation program's <systemitem>initramfs</systemitem> is now completely non-interactive, which means that these options are not available anymore. Instead, use the <option>inst.repo=</option> to specify the installation method and <option>ip=</option> to configure network settings. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>serial</option></term> + <listitem> + <para> + This option forced <application>Anaconda</application> to use the <literal>/dev/ttyS0</literal> console as the output. Use the <option>console=/dev/ttyS0</option> (or similar) instead. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>updates=</option></term> + <listitem> + <para> + Specified the location of updates for the installation program. Use the <option>inst.updates=</option> option instead. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>essid=</option>, <option>wepkey=</option>, <option>wpakey=</option></term> + <listitem> + <para> + Configured wireless network access. Network configuration is now being handled by <application>dracut</application>, which does not support wireless networking, rendering these options useless. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>ethtool=</option></term> + <listitem> + <para> + Used in the past to configure additional low-level network settings. All network settings are now handled by the <option>ip=</option> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>gdb</option></term> + <listitem> + <para> + Allowed you to debug the loader. Use <option>rd.debug</option> instead. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>mediacheck</option></term> + <listitem> + <para> + Verified the installation media before starting the installation. Replaced with the <option>rd.live.check</option> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>ks=floppy</option></term> + <listitem> + <para> + Specified a floppy disk as the Kickstart file source. Floppy drives are not supported anymore. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>display=</option></term> + <listitem> + <para> + Configured a remote display. Replaced with the <option>inst.vnc</option> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>utf8</option></term> + <listitem> + <para> + Added UTF8 support when installing in text mode. UTF8 support now works automatically. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>noipv6</option></term> + <listitem> + <para> + Used to disable IPv6 support in the installation program. IPv6 is now built into the kernel so the driver cannot be blacklisted; however, it is possible to disable IPv6 using the <option>ipv6.disable</option> <application>dracut</application> option. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>upgradeany</option></term> + <listitem> + <para> + Upgrades are done in a different way in current &PRODUCT; releases. For more information about upgrading your system, see <xref linkend="chap-upgrading" />. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><option>vlanid=</option></term> + <listitem> + <para> + Used to configure Virtual LAN (802.1q tag) devices. Use the <option>vlan=</option> <application>dracut</application> option instead. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section id="sect-boot-options-maintenance"> + <title>Using the Maintenance Boot Modes</title> + + <section id="sect-boot-options-memtest"> + <title>Loading the Memory (RAM) Testing Mode</title> + <para> + Faults in memory (RAM) modules may cause your system to freeze or crash unpredictably. In some cases, memory faults may only cause errors with particular combinations of software. For this reason, you should test the memory of a computer before you install &PRODUCT; for the first time, even if it has previously run other operating systems. + </para> + <para> + &PRODUCT; includes the <application>Memtest86+</application> memory testing application. To start memory testing mode, choose <guisubmenu>Troubleshooting</guisubmenu> > <guimenuitem>Memory test</guimenuitem> at the boot menu. Testing will begin immediately. By default, <application>Memtest86+</application> carries out ten tests in every pass; a different configuration can be specified by accessing the configuration screen using the <keycap>c</keycap> key. After the first pass completes, a message will appear at the bottom informing you of the current status, and another pass will start automatically. + </para> + <note> + <para> + <application>Memtest86+</application> only works on systems with BIOS firmware. Support for UEFI systems is currently unavailable. + </para> + </note> + <figure> + <title>Memory Check Using Memtest86+</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/boot/memtest86.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Memtest86+ testing the system memory + </para> + </textobject> + </mediaobject> + </figure> + <para> + The main screen displayed while testing is in progress is divided into three main areas: + </para> + <itemizedlist> + <listitem> + <para> + The upper left corner shows information about your system's memory configuration - the amount of detected memory and processor cache and their throughputs and processor and chipset information. This information is detected when <application>Memtest86+</application> starts. + </para> + </listitem> + <listitem> + <para> + The upper right corner displays information about the tests - progress of the current pass and the currently running test in that pass as well as a description of the test. + </para> + </listitem> + <listitem> + <para> + The central part of the screen is used to display information about the entire set of tests from the moment when the tool has started, such as the total time, the number of completed passes, number of detected errors and your test selection. On some systems, detailed information about the installed memory (such as the number of installed modules, their manufacturer, frequency and latency) will be also displayed here. After the each pass completes, a short summary will appear in this location. For example: + </para> + <screen> +<computeroutput>** Pass complete, no errors, press Esc to exit **</computeroutput> + </screen> + <para> + If <application>Memtest86+</application> detects an error, it will also be displayed in this area and highlighted red. The message will include detailed information such as which test detected a problem, the memory location which is failing, and others. + </para> + </listitem> + </itemizedlist> + <para> + In most cases, a single successful pass (that is, a single run of all 10 tests) is sufficient to verify that your RAM is in good condition. In some rare circumstances, however, errors that went undetected on the first pass might appear on subsequent passes. To perform a thorough test on an important system, leave the tests running overnight or even for a few days in order to complete multiple passes. + </para> + <note> + <para> + The amount of time it takes to complete a single full pass of <application>Memtest86+</application> varies depending on your system's configuration (notably the RAM size and speed). For example, on a system with 2 GB of DDR2 memory at 667 MHz, a single pass will take roughly 20 minutes to complete. + </para> + </note> + <para> + To halt the tests and reboot your computer, press the <keycap>Esc</keycap> key at any time. + </para> + <para> + For more information about using <application>Memtest86+</application>, see the official website at <ulink url="http://www.memtest.org/" />. A <filename>README</filename> file is also located in <filename class="directory">/usr/share/doc/memtest86+-<replaceable>version</replaceable>/</filename> on &PRODUCT; systems with the <package>memtest86+</package> package installed. + </para> + </section> + + <section id="sect-boot-options-mediacheck"> + <title>Verifying Boot Media</title> + <para> + You can test the integrity of an ISO-based installation source before using it to install &PRODUCT;. These sources include DVDs and ISO images stored on a local hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation. + </para> + <para> + To test the integrity of an ISO image, append the <option>rd.live.check</option> to the boot loader command line. Note that this option is used automatically if you select the default installation option from the boot menu (<guimenuitem>Test this media & install Fedora</guimenuitem>). + </para> + </section> + + <section id="sect-boot-options-rescue"> + <title>Booting Your Computer in Rescue Mode</title> + <para> + You may boot a command-line Linux system from an installation disc without actually installing &PRODUCT; on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair already installed operating systems. + </para> + <para> + To load the rescue system with the installation disk or USB drive, choose <guimenuitem>Rescue a &PRODUCT; system</guimenuitem> from the <guisubmenu>Troubleshooting</guisubmenu> submenu in the boot menu, or use the <option>inst.rescue</option> boot option. + </para> + <para> + Specify the language, keyboard layout and network settings for the rescue system with the screens that follow. The final setup screen configures access to the existing system on your computer. + </para> + <para> + By default, rescue mode attaches an existing operating system to the rescue system under the directory <filename>/mnt/sysimage/</filename>. + </para> + </section> + + </section> </chapter>

1 0

[install-guide/F21-rewrite] Fixing an ID
by pbokoc 03 Sep '14

03 Sep '14

commit e90f6eff58a8dd3036e976507aeecb66ba5d5775 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Wed Sep 3 19:17:02 2014 +0200 Fixing an ID en-US/Upgrading_Your_Current_System.xml | 34 +++++++++++++++--------------- 1 files changed, 17 insertions(+), 17 deletions(-) --- diff --git a/en-US/Upgrading_Your_Current_System.xml b/en-US/Upgrading_Your_Current_System.xml index 6baa07e..3b3ceea 100644 --- a/en-US/Upgrading_Your_Current_System.xml +++ b/en-US/Upgrading_Your_Current_System.xml @@ -3,24 +3,24 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-upgrading-fedora"> - <title>Upgrading Your Current System</title> - <para> - intro text - </para> +<chapter id="chap-upgrading"> + <title>Upgrading Your Current System</title> + <para> + intro text + </para> - <section id="sect-upgrading-fedora-fedup"> - <title>Automatic System Upgrade Using FedUp</title> - <para> - text - </para> - </section> + <section id="sect-upgrading-fedora-fedup"> + <title>Automatic System Upgrade Using FedUp</title> + <para> + text + </para> + </section> - <section id="sect-upgrading-fedora-manual-reinstall"> - <title>Manual System Upgrade or Reinstallation</title> - <para> - text - </para> - </section> + <section id="sect-upgrading-fedora-manual-reinstall"> + <title>Manual System Upgrade or Reinstallation</title> + <para> + text + </para> + </section> </chapter>

1 0

[install-guide/F21-rewrite] Some cleanup in VNC chapter
by pbokoc 03 Sep '14

03 Sep '14

commit bd1bf1f70a454879853219717622ad9158fa13f2 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Wed Sep 3 18:20:39 2014 +0200 Some cleanup in VNC chapter en-US/VNC_Installations.xml | 16 ++++++++-------- 1 files changed, 8 insertions(+), 8 deletions(-) --- diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml index 4951366..3b6f438 100644 --- a/en-US/VNC_Installations.xml +++ b/en-US/VNC_Installations.xml @@ -142,7 +142,7 @@ </step> <step> <para> - Boot the installation system and wait for the boot menu to appear. In the menu, press the <keycap>Tab</keycap> key to edit boot options. Append the <option>inst.vnc</option> option to end of the command line. + Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see <xref linkend="sect-boot-menu" />) and append the <option>inst.vnc</option> option to the end of the command line. </para> <para> Optionally, if you want to restrict VNC access to the installation system, add the <option>inst.vncpassword=<replaceable>PASSWORD</replaceable></option> boot option as well. Replace <replaceable>PASSWORD</replaceable> with the password you want to use for the installation. The VNC password must be between 6 and 8 characters long. @@ -168,7 +168,7 @@ </step> <step> <para> - Press <keycap>Enter</keycap> to start the installation. The system will initialize the installation program and start the necessary services. When the system is ready, you will see a message on the screen similar to the following: + Start the installation using the edited options. The system will initialize the installation program and start the necessary services. When the system is ready, you will see a message on the screen similar to the following: </para> <screen> <computeroutput>13:14:47 Please manually connect your VNC viewer to 192.168.100.131:5901 to begin the install.</computeroutput> @@ -183,8 +183,8 @@ </para> </step> </procedure> - <para> - After you finish the procedure, a new window will open with the VNC connection established, displaying the installation menu. In this window, you will be able to use the <application>Anaconda</application> graphical interface the same way you would use it when installing directly on the system. + <para> + When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time. </para> <para> You can then proceed with <xref linkend="chap-installing-using-anaconda" />. @@ -194,7 +194,7 @@ <section id="sect-vnc-installations-connect-mode"> <title>Installing in VNC Connect Mode</title> <para> - VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in &PRODUCT; 7 is available in <ulink url="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux…">Red Hat Enterprise Linux 7 Networking Guide</ulink>. + VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in &PRODUCT; is available in the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">&PRODUCT; Documentation website</ulink>. </para> <procedure id="proc-vnc-installations-connect-mode"> <title>Starting VNC in Connect Mode</title> @@ -229,7 +229,7 @@ Thu Feb 20 15:23:54 2014 </step> <step> <para> - Boot the system being installed and wait for the boot menu to appear. In the menu, press the <keycap>Tab</keycap> key to edit boot options. Append the following options to the command line: + Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see <xref linkend="sect-boot-menu" />) and append the following options to the end of the command line: </para> <screen> <option>inst.vnc inst.vncconnect=<replaceable>HOST</replaceable>:<replaceable>PORT</replaceable></option> @@ -240,10 +240,10 @@ Thu Feb 20 15:23:54 2014 </step> <step> <para> - Press <keycap>Enter</keycap> to start the installation. The system will initialize the installation program and start the necessary services. Once the initialization is finished, <application>Anaconda</application> will attempt to connect to the IP address and port you provided in the previous step. + Start the installation. The system will initialize the installation program and start the necessary services. Once the initialization is finished, <application>Anaconda</application> will attempt to connect to the IP address and port you provided in the previous step. </para> <para> - When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. In this window, you will be able to use the <application>Anaconda</application> graphical interface the same way you would use it when installing directly on the system. + When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time. </para> </step> </procedure>

1 0

[networking-guide] master: Fix bad tag: NetworkManager> (67cb12a)
by stephenw 02 Sep '14

02 Sep '14

Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git On branch : master >--------------------------------------------------------------- commit 67cb12a25f591ea35a0feb66e8c75e06c4272878 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Tue Sep 2 08:53:47 2014 +0200 Fix bad tag: NetworkManager> >--------------------------------------------------------------- en-US/Configure_802_1Q_VLAN_Tagging.xml | 2 +- en-US/Configure_Network_Bonding.xml | 2 +- en-US/Configure_Network_Bridging.xml | 2 +- en-US/Configure_Network_Teaming.xml | 2 +- en-US/Configure_Networking.xml | 8 ++++---- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml index dfe529d..2b2d4f7 100644 --- a/en-US/Configure_802_1Q_VLAN_Tagging.xml +++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml @@ -89,7 +89,7 @@ <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-VLAN">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your VLAN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your VLAN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Options</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml index ef8e6cc..e7b5f51 100644 --- a/en-US/Configure_Network_Bonding.xml +++ b/en-US/Configure_Network_Bonding.xml @@ -141,7 +141,7 @@ When controlling bonded slave interfaces using the <systemitem class="daemon">Ne <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bond">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your bond connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your bond connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Options</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Network_Bridging.xml b/en-US/Configure_Network_Bridging.xml index 3c7325a..62e6052 100644 --- a/en-US/Configure_Network_Bridging.xml +++ b/en-US/Configure_Network_Bridging.xml @@ -206,7 +206,7 @@ <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bridge">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your new bridge connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your new bridge connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Configure</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml index 5b4f791..6a13c4a 100644 --- a/en-US/Configure_Network_Teaming.xml +++ b/en-US/Configure_Network_Teaming.xml @@ -336,7 +336,7 @@ From the available interfaces, determine which are suitable for adding to your n <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-team">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your team connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your team connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Options</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml index 65d3122..d1e9e11 100644 --- a/en-US/Configure_Networking.xml +++ b/en-US/Configure_Networking.xml @@ -281,7 +281,7 @@ To restrict connections and networking, there are two options which can be used <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking the gear wheel icon to return to the editing dialog.</para> <para>Then, to configure:</para> @@ -657,7 +657,7 @@ To restrict connections and networking, there are two options which can be used </variablelist> <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your new VPN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your new VPN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Configure</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> @@ -780,7 +780,7 @@ To restrict connections and networking, there are two options which can be used <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your mobile broadband connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your mobile broadband connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> @@ -994,7 +994,7 @@ To restrict connections and networking, there are two options which can be used <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-DSL">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your DSL connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your DSL connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para>

1 0

[networking-guide] master: Power cycle an interface {part 3} (1c9902b)
by stephenw 02 Sep '14

02 Sep '14

Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git On branch : master >--------------------------------------------------------------- commit 1c9902b4b5b8080fc7ec0becf5f17192dfa9c2a3 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Tue Sep 2 08:05:22 2014 +0200 Power cycle an interface {part 3} >--------------------------------------------------------------- en-US/Configure_802_1Q_VLAN_Tagging.xml | 2 +- en-US/Configure_Network_Bonding.xml | 2 +- en-US/Configure_Network_Bridging.xml | 2 +- en-US/Configure_Network_Teaming.xml | 2 +- en-US/Configure_Networking.xml | 8 ++++---- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml index 353cb8e..dfe529d 100644 --- a/en-US/Configure_802_1Q_VLAN_Tagging.xml +++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml @@ -89,7 +89,7 @@ <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-VLAN">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your VLAN connection, click the <guibutton>Save</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the network connection icon's menu. See <xref + <para>Once you have finished editing your VLAN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Options</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml index d69a5f5..ef8e6cc 100644 --- a/en-US/Configure_Network_Bonding.xml +++ b/en-US/Configure_Network_Bonding.xml @@ -141,7 +141,7 @@ When controlling bonded slave interfaces using the <systemitem class="daemon">Ne <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bond">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your bond connection, click the <guibutton>Save</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your bond connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Options</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Network_Bridging.xml b/en-US/Configure_Network_Bridging.xml index 7888265..3c7325a 100644 --- a/en-US/Configure_Network_Bridging.xml +++ b/en-US/Configure_Network_Bridging.xml @@ -206,7 +206,7 @@ <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bridge">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your new bridge connection, click the <guibutton>Save</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your new bridge connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Configure</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml index ae57a76..5b4f791 100644 --- a/en-US/Configure_Network_Teaming.xml +++ b/en-US/Configure_Network_Teaming.xml @@ -336,7 +336,7 @@ From the available interfaces, determine which are suitable for adding to your n <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-team">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your team connection, click the <guibutton>Save</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your team connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Options</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml index 660869b..65d3122 100644 --- a/en-US/Configure_Networking.xml +++ b/en-US/Configure_Networking.xml @@ -281,7 +281,7 @@ To restrict connections and networking, there are two options which can be used <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking the gear wheel icon to return to the editing dialog.</para> <para>Then, to configure:</para> @@ -657,7 +657,7 @@ To restrict connections and networking, there are two options which can be used </variablelist> <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your new VPN connection, click the <guibutton>Save</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your new VPN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Configure</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> @@ -780,7 +780,7 @@ To restrict connections and networking, there are two options which can be used <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your mobile broadband connection, click the <guibutton>Apply</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your mobile broadband connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para> @@ -994,7 +994,7 @@ To restrict connections and networking, there are two options which can be used <bridgehead id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-DSL">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> - <para>Once you have finished editing your DSL connection, click the <guibutton>Apply</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref + <para>Once you have finished editing your DSL connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager> apply the changes, power cycle the interface. See <xref linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para> <para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> <para>Then, to configure:</para>

1 0

[networking-guide] master: Power cycle an interface {part 2} (30e1a02)
by stephenw 02 Sep '14

02 Sep '14

1 0

[networking-guide] master: Power cycle an interface to apply changes (31e729c)
by stephenw 02 Sep '14

02 Sep '14

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits September 2014