[install-guide/f21-branch] Adding text to InitialSetupHub
by pbokoc
commit ca66a541b04510537769abf03577b554884f9253
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Nov 13 17:19:38 2014 +0100
Adding text to InitialSetupHub
en-US/InitialSetupHub.xml | 58 ++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 57 insertions(+), 1 deletions(-)
---
diff --git a/en-US/InitialSetupHub.xml b/en-US/InitialSetupHub.xml
index cfc8db9..717cdd2 100644
--- a/en-US/InitialSetupHub.xml
+++ b/en-US/InitialSetupHub.xml
@@ -6,6 +6,62 @@
<section id="sect-initial-setup">
<title>Initial Setup</title>
<para>
- text
+ The <guilabel>Initial Setup</guilabel> screen is shown after the installation finishes and the installed system boots for the first time, before the first login, assuming the following conditions have been met:
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Your software selection contained a graphical environment (for example, you installed the system using a &PRODUCT; Workstation live image).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The graphical environment you have installed is <emphasis>not</emphasis> <application>GNOME Desktop Environment</application> (it provides its own initial setup utility which is described in <xref linkend="sect-gnome-initial-setup" />).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <package>initial-setup</package> package has been installed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You have not configured every screen available in the graphical installer.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <remark>TODO: screen with --reconfig</remark>
+ </para>
+ <para>
+ <application>Initial Setup</application> allows you to configure several system settings. All of these can also be configured during the installation, but they are not required to finish it. Only the settings which have <emphasis>not</emphasis> been configured during the installation will be shown; for example, if you did not create a non-<systemitem class="username">root</systemitem> user account during the installation, <application>Initial Setup</application> will start after the first reboot, and you will be able to configure one. If you configured all available options during the instalaltion, <application>Initial Setup</application> will not be displayed at all.
+ </para>
+ <para>
+ To configure any aspect of the system available in the utility, click any of the links available in the main window (for example, <guilabel>Create User</guilabel>). Each link leads to a separate screen with separate options; these screens are the same ones which were available during the graphical installation. If you need help, press <guilabel>Help</guilabel> in the top left corner to open a new window containing directions for that screen.
+ </para>
+ <para>
+ After you finish configuring any screen, press the <guilabel>Done</guilabel> button in the top left corner to return to the main <application>Initial Setup</application> menu. After you finish configuring all settings, click <guilabel>Finish Configuration</guilabel> in the bottom right corner to save all configured settings. The configuration utility will close and you will be able to log in to the system.
+ </para>
+ <note>
+ <para>
+ It is possible to configure <application>Initial Setup</application> to display all available options, even if they have been already configured during the installation. To do so, you must use a Kickstart file at the start of the installation, and this file must contain the following command:
+ </para>
+ <programlisting>
+<command>firstboot --enable --reconfig</command>
+ </programlisting>
+ <para>
+ The <option>--reconfig</option> option specifies that all options should be displayed. See <xref linkend="chap-kickstart-installations" /> for information about Kickstart installations.
+ </para>
+ </note>
+ <note>
+ <para>
+ Normally, it is not possible to return to <application>Initial Setup</application> after you close it and log in to the system. You can make it display again (after the next reboot, before a login prompt is displayed), by executing the following command as <systemitem class="username">root</systemitem>:
+ </para>
+ <screen>
+<prompt>#</prompt> <command>systemctl enable initial-setup-graphical.service</command>
+ </screen>
+ <para>
+ Then, reboot your system.
+ </para>
+ </note>
</section>
9 years, 6 months
[install-guide/f21-branch] Removing some internal xrefs from NetworkSpoke
by pbokoc
commit f3948ca8d5d60ee3b9507acfebe1e188a8060e33
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Nov 13 16:30:16 2014 +0100
Removing some internal xrefs from NetworkSpoke
en-US/NetworkSpoke.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/NetworkSpoke.xml b/en-US/NetworkSpoke.xml
index 0f84e7c..69c8cd4 100644
--- a/en-US/NetworkSpoke.xml
+++ b/en-US/NetworkSpoke.xml
@@ -20,10 +20,10 @@
Locally accessible interfaces are automatically detected by the installation program and cannot be manually added or deleted. All detected interfaces are listed on the left side of the screen. Click an interface in the list to display its current configuration (such as IP and DNS address); the details are displayed on the right side of the screen.
</para>
<para>
- Below the list of interfaces are two buttons. Use the <guilabel>+</guilabel> button to add a virtual network interface (Team, Bond or VLAN), as described in <xref linkend="sect-installation-gui-network-configuration-virtual-interface" />. To remove a previously created virtual interface, select it in the list and click the <guilabel>-</guilabel> button.
+ Below the list of interfaces are two buttons. Use the <guilabel>+</guilabel> button to add a virtual network interface (Team, Bond or VLAN), as described further in this section. To remove a previously created virtual interface, select it in the list and click the <guilabel>-</guilabel> button.
</para>
<para>
- To change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical), select the interface in the left pane and click <guilabel>Configure</guilabel> in the bottom right corner of the screen. Available settings are described in <xref linkend="sect-installation-gui-network-configuration-advanced" />.
+ To change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical), select the interface in the left pane and click <guilabel>Configure</guilabel> in the bottom right corner of the screen. Available settings are described further in this chapter.
</para>
<para>
Use the <guilabel>ON</guilabel>/<guilabel>OFF</guilabel> switch in the top right corner to enable or disable the currently selected interface.
9 years, 6 months
[install-guide/f21-branch] Typo fixes and clarifications in UserSpoke
by pbokoc
commit 910153bba03e8876888e0f5d67a3c3312c6e9018
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Nov 13 15:17:51 2014 +0100
Typo fixes and clarifications in UserSpoke
en-US/UserSpoke.xml | 10 +++-------
1 files changed, 3 insertions(+), 7 deletions(-)
---
diff --git a/en-US/UserSpoke.xml b/en-US/UserSpoke.xml
index 198c567..93a1c9b 100644
--- a/en-US/UserSpoke.xml
+++ b/en-US/UserSpoke.xml
@@ -6,11 +6,11 @@
<section id="sect-installation-gui-create-user">
<title>Create User</title>
<para>
- The <guilabel>Create User</guilabel> screen can be used to create and configure one normal (non-<systemitem class="username">root</systemitem>) user account during the installation. Only one user account can be configured here; if you require more accounts, wait until the installation completes, reboot your system and then create other accounts using either the <command>useradd</command> command in a terminal, or a graphical utility for managing user accounts (for example, the <guimenuitem>Users</guimenuitem> scren in the <guimenu>Settings</guimenu> menu in <application>GNOME</application>).
+ The <guilabel>Create User</guilabel> screen can be used to create and configure one normal (non-<systemitem class="username">root</systemitem>) user account during the installation. Only one user account can be configured here; if you require more accounts, wait until the installation completes, reboot your system and then create other accounts using either the <command>useradd</command> command in a terminal, or a graphical utility for managing user accounts (for example, the <guimenuitem>Users</guimenuitem> screen in the <guimenu>Settings</guimenu> menu in <application>GNOME</application>).
</para>
<important>
<para>
- Creating a normal user account is not required to finish the installation; however, it is highly recommended. If you do not create one, you will have to log in to the system as <systemitem class="username">root</systemitem>, which should almost never be done.
+ Creating a normal user account is not required to finish the installation; however, it is highly recommended. If you do not create one, you will have to log in to the system as <systemitem class="username">root</systemitem> directly, which is <emphasis>not</emphasis> recommended.
</para>
</important>
<para>
@@ -64,7 +64,7 @@
</listitem>
<listitem>
<para>
- The the group ID (GID) of the user's default. The default group name will be the same as the user name, and the default group ID is 1000. GIDs 0-999 are reserved by the system so they can not be assigned to an user's group.
+ The the group ID (GID) of the user's default group. The default group name will be the same as the user name, and its default GID is 1000. GIDs 0-999 are reserved by the system so they can not be assigned to an user's group.
</para>
</listitem>
<listitem>
@@ -76,7 +76,3 @@
</section>
</section>
-
-
-
-
\ No newline at end of file
9 years, 6 months
[install-guide/f21-branch] Clarifying part --asprimary in Kickstart
by pbokoc
commit d5bd6398d8f4e4d9159a9fbf465c79d257691d12
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Nov 13 14:07:10 2014 +0100
Clarifying part --asprimary in Kickstart
en-US/Kickstart_Syntax_Reference.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 023bc8f..4ad9f94 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -1520,7 +1520,7 @@
<term><option>--asprimary</option></term>
<listitem>
<para>
- Forces the partition to be allocated as a <emphasis>primary</emphasis> partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. For information about primary partitions, see <remark>TODO: xref to an appendix about partitions or something like that</remark>
+ Forces the partition to be allocated as a <emphasis>primary</emphasis> partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see <remark>TODO: xref to an appendix about partitions or something like that</remark>
</para>
</listitem>
</varlistentry>
9 years, 6 months
[install-guide/f21-branch] Adding text to UserSpoke
by pbokoc
commit 084da888c614eb430ec3ef9d217524eda07e352e
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Nov 13 13:43:56 2014 +0100
Adding text to UserSpoke
en-US/UserSpoke.xml | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 72 insertions(+), 1 deletions(-)
---
diff --git a/en-US/UserSpoke.xml b/en-US/UserSpoke.xml
index c2760f2..198c567 100644
--- a/en-US/UserSpoke.xml
+++ b/en-US/UserSpoke.xml
@@ -6,6 +6,77 @@
<section id="sect-installation-gui-create-user">
<title>Create User</title>
<para>
- text
+ The <guilabel>Create User</guilabel> screen can be used to create and configure one normal (non-<systemitem class="username">root</systemitem>) user account during the installation. Only one user account can be configured here; if you require more accounts, wait until the installation completes, reboot your system and then create other accounts using either the <command>useradd</command> command in a terminal, or a graphical utility for managing user accounts (for example, the <guimenuitem>Users</guimenuitem> scren in the <guimenu>Settings</guimenu> menu in <application>GNOME</application>).
</para>
+ <important>
+ <para>
+ Creating a normal user account is not required to finish the installation; however, it is highly recommended. If you do not create one, you will have to log in to the system as <systemitem class="username">root</systemitem>, which should almost never be done.
+ </para>
+ </important>
+ <para>
+ <remark>TODO: screen</remark>
+ </para>
+ <para>
+ To configure a user account, fill out the <guilabel>Full name</guilabel> (for example, <literal>John Smith</literal>) and <guilabel>Username</guilabel> (for example, <literal>jsmith</literal>). The <guilabel>username</guilabel> will used to log in from a command line; if you install a graphical environment, then your graphical login manager will use <guilabel>Full name</guilabel>.
+ </para>
+ <para>
+ Make sure that the <guilabel>Require a password to use this account</guilabel> check box is enabled, enter a password you want to use for this account into the <guilabel>Password</guilabel> field. The characters you write will be displayed as dots for security. Then, repeat the same password in the <guilabel>Confirm password</guilabel> field below to ensure you entered it properly. Both entered passwords must be the same.
+ </para>
+ <para>
+ As you enter the password, it will be evaluated and the installer will determine the password's strength. If the installer considers your password weak, a message will appear at the bottom of the screen, explaining which aspect of your chosen password is considered insuficient. For example:
+ </para>
+ <screen>
+<guilabel>The password you have provided is weak:</guilabel> <guilabel>The password is shorter than 5 characters.</guilabel>
+ </screen>
+ <para>
+ If a message similar to the above appears, it is highly recommended to choose a different, stronger password.
+ </para>
+ <para>
+ The <guilabel>Make this user administrator</guilabel> check box gives the user you are creatng administrative rights (by adding this user into the <systemitem class="groupname">wheel</systemitem> group), allowing this user to use the <command>sudo</command> command to perform tasks normally only available to <systemitem class="username">root</systemitem> using only the user password, instead of the <systemitem class="username">root</systemitem> password. This may be more convenient, but can also pose a security risk.
+ </para>
+ <warning>
+ <para>
+ If you give administrator privileges to an user, make sure that the account is protected by a strong password. Never give an user administrator privileges without requiring any password for the account.
+ </para>
+ <para>
+ See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation website</ulink>, for detailed information about password security including guidelines for selecting strong passwords.
+ </para>
+ </warning>
+ <para>
+ To additional settings, click the <guilabel>Advanced</guilabel> button below the password input fields. A new dialog window titled <guilabel>Advanced User Configuration</guilabel> will open. This dialog is described in the following section.
+ </para>
+
+ <section id="sect-installation-gui-create-user-advanced">
+ <title>Advanced User Configuration</title>
+ <para>
+ The <guilabel>Advanced User Configuration</guilabel> dialog allows you to change the following settings for the new user account:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The user's <guilabel>Home directory</guilabel> (<filename class="directory">/home/<replaceable>username</replaceable></filename> by default).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The user's ID (UID). The default value is 1000. UIDs 0-999 are reserved by the system so they can not be assigned to an user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The the group ID (GID) of the user's default. The default group name will be the same as the user name, and the default group ID is 1000. GIDs 0-999 are reserved by the system so they can not be assigned to an user's group.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The user's group membership. The user account you are creating will always have one default group membership (the user's default group with an ID set in the <guilabel>Specify a group ID manually</guilabel> field). In the <guilabel>Group Membership</guilabel> field, you can specify additional groups as a comma-separated list. Groups which do not already exist will be created; you can specify custom GIDs for them in parentheses. If you do not specify a custom GID for a new group, it will be assigned automatically.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
</section>
+
+
+
+
\ No newline at end of file
9 years, 6 months
[install-guide/f21-branch] Clarifying inst.dd= in Boot Options
by pbokoc
commit c2f586beddea35c26a3e129e7c997b2e4484bdd6
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Nov 13 11:20:56 2014 +0100
Clarifying inst.dd= in Boot Options
en-US/Boot_Options.xml | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml
index 1def977..5595b27 100644
--- a/en-US/Boot_Options.xml
+++ b/en-US/Boot_Options.xml
@@ -205,13 +205,15 @@
<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>
+ <screen><option>inst.dd=hd:/dev/sdb1:/driver.rpm</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>
+ <important>
+ <para>
+ 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>
+ </important>
</listitem>
</varlistentry>
</variablelist>
9 years, 6 months
[install-guide] (4 commits) ...Adding InitialSetupHub.xml
by pbokoc
Summary of changes:
48ac13a... Adding the rest of NetworkSpoke (*)
4af2931... Clarifying what a default route is in NetworkSpoke (*)
4e3fefa... Adding text to ProgressHub (*)
869f2df... Adding InitialSetupHub.xml (*)
(*) This commit already existed in another branch; no separate mail sent
9 years, 6 months
[install-guide/f21-branch] Adding InitialSetupHub.xml
by pbokoc
commit 869f2df27feea149a66b380657a91929c5a941dc
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 11 19:54:55 2014 +0100
Adding InitialSetupHub.xml
en-US/After_Installation.xml | 14 +-------------
en-US/InitialSetupHub.xml | 11 +++++++++++
prepare_anaconda_help_content.py | 3 ++-
3 files changed, 14 insertions(+), 14 deletions(-)
---
diff --git a/en-US/After_Installation.xml b/en-US/After_Installation.xml
index dbaa106..69c67ff 100644
--- a/en-US/After_Installation.xml
+++ b/en-US/After_Installation.xml
@@ -9,19 +9,7 @@
intro text
</para>
- <section id="sect-initial-setup">
- <title>Initial Setup</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-firstboot">
- <title>Firstboot</title>
- <para>
- text
- </para>
- </section>
+ <xi:include href="InitialSetupHub.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<section id="sect-gnome-initial-setup">
<title>GNOME Initial Setup</title>
diff --git a/en-US/InitialSetupHub.xml b/en-US/InitialSetupHub.xml
new file mode 100644
index 0000000..cfc8db9
--- /dev/null
+++ b/en-US/InitialSetupHub.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-initial-setup">
+ <title>Initial Setup</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/prepare_anaconda_help_content.py b/prepare_anaconda_help_content.py
index ba31591..ef3d988 100755
--- a/prepare_anaconda_help_content.py
+++ b/prepare_anaconda_help_content.py
@@ -29,7 +29,8 @@ ANACONDA_HELP_FILES = [
"NetworkSpoke.xml",
"SoftwareSpoke.xml",
"UserSpoke.xml",
- "ProgressHub.xml"
+ "ProgressHub.xml",
+ "InitialSetupHub.xml"
]
def run_xmllint():
9 years, 6 months
[install-guide/f21-branch] Adding text to ProgressHub
by pbokoc
commit 4e3fefa5bf0394db8e50b87e4a1e339c202aa82e
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 11 19:54:32 2014 +0100
Adding text to ProgressHub
en-US/ProgressHub.xml | 16 +++++++++++++++-
1 files changed, 15 insertions(+), 1 deletions(-)
---
diff --git a/en-US/ProgressHub.xml b/en-US/ProgressHub.xml
index 88885e8..f649acf 100644
--- a/en-US/ProgressHub.xml
+++ b/en-US/ProgressHub.xml
@@ -6,6 +6,20 @@
<section id="sect-installation-gui-installation-progress">
<title>Configuration and Installation Progress</title>
<para>
- text
+ The <guilabel>Configuration</guilabel> screen is displayed after you finish configuring all required items in <xref linkend="sect-installation-gui-installation-summary" /> and press the <guilabel>Begin installation</guilabel> button. After this point, the installation process actually starts and changes are being made to your selected disks. It is not possible to go back to the <guilabel>Installation Summary</guilabel> and change any settings configured there; if you need to do so, you must wait for the installation process to finish, reboot your system, log in and change your settings on the installed system.
</para>
+ <para>
+ <remark>TODO: screen</remark>
+ </para>
+ <para>
+ In the top part of the screen, two additional options are available, allowing you to configure authentication settings - the <systemitem class="username">root</systemitem> password and an additional user account. Configuring <systemitem class="username">root</systemitem> the password is required to finish the installation; creating a user account can be skipped. If you do so, you will be prompted to create a non-root user account after the installation finishes and your system reboots.
+ </para>
+ <para>
+ The bottom of the screen shows a progress bar and a message informing you of the current progress of the installation. When the installation finishes and the <systemitem class="username">root</systemitem> password has been set, you can press the <guilabel>Finish configuration</guilabel> button to reboot your computer and log in to your newly installed &PRODUCT; system.
+ </para>
+ <important>
+ <para>
+ Before you finish the installation and reboot, either remove the media (CD, DVD or a USB drive) which you used to start the installation, or make sure that your system tries to boot from the hard drive before trying removable media. Otherwise, your computer will start the installer again instead of the installed system.
+ </para>
+ </important>
</section>
9 years, 6 months
[install-guide/f21-branch] Clarifying what a default route is in NetworkSpoke
by pbokoc
commit 4af293150ac8682ac32673543b5780e8b105ad09
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Nov 11 16:38:39 2014 +0100
Clarifying what a default route is in NetworkSpoke
en-US/NetworkSpoke.xml | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/en-US/NetworkSpoke.xml b/en-US/NetworkSpoke.xml
index 9c7d202..0f84e7c 100644
--- a/en-US/NetworkSpoke.xml
+++ b/en-US/NetworkSpoke.xml
@@ -124,10 +124,13 @@
In the <guilabel>IPv4 Settings</guilabel> and <guilabel>IPv4 Settings</guilabel> tabs, click the <guilabel>Routes</guilabel> button in the bottom right corner to configure routing settings for a specific IP protocol on an interface. A new dialog will open, allowing you to <guilabel>Add</guilabel> a specific route.
</para>
<para>
- If you confire at least one static route, you can disallow all other ones by enabling the <guilabel>Ignore automatically obtained routes</guilabel>.
+ If you confire at least one static route, you can disallow all routes not specifically configured here by enabling the <guilabel>Ignore automatically obtained routes</guilabel>.
</para>
<para>
- You can also check the <guilabel>Use this connection only for resources on this network</guilabel>; this option does not require any static routes to be set. This setting is useful if you are configuring more than one interface. By enabling it for one interface and disabling it for others, you can ensure that the interface which has this option enabled will only be used to access resources unavailable to other interfaces (such as your internal network with restricted access), and the other ones will be used to access normally avaibable data (such as the internet).
+ Select <guilabel>Use this connection only for resources on its network</guilabel> to prevent this connection from becoming the default route. This option can be selected even if you did not configure any static routes. Enabling this option means that this route will only be used when necessary to access certain resources, such as intranet pages which require a local or VPN connection. Another (default) route will be used for publicly available resources if possible. Note that unlike the additional routes configured in this dialog, this setting will be transferred to the installed system. Also note that this option is only useful when more than one interface is configured.
+ </para>
+ <para>
+ When you finish configuring the interface's routing settings, click <guilabel>OK</guilabel> to return to the configuration dialog.
</para>
</listitem>
</varlistentry>
9 years, 6 months