docs-commits December 2014

docs-commits@lists.fedoraproject.org

10 participants
199 discussions

[system-administrators-guide/21] Change to edition: 1.0

by stephenw

commit 73b3d3e994b350a64236b92ac543026698e3f9b4 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Wed Dec 10 15:41:55 2014 +0100 Change to edition: 1.0 en-US/Book_Info.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml index 8259d16..f9303e6 100644 --- a/en-US/Book_Info.xml +++ b/en-US/Book_Info.xml @@ -6,7 +6,7 @@ <subtitle>Deployment, Configuration, and Administration of &MAJOROSVER;</subtitle> <productname>Fedora Documentation</productname> <productnumber></productnumber> - <edition>21.0.1</edition> + <edition>1.0</edition> <pubsnumber>0</pubsnumber> <abstract> <para>

9 years, 6 months

1
0
0 / 0

[system-administrators-guide/21] Book in branch is not draft

by stephenw

commit 5488d6c02c0e6c3da4f71f88c7fd4dc2112e2f41 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Wed Dec 10 15:38:06 2014 +0100 Book in branch is not draft en-US/Book_Info.xml | 2 +- en-US/System_Administrators_Guide.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml index 27bf70f..8259d16 100644 --- a/en-US/Book_Info.xml +++ b/en-US/Book_Info.xml @@ -4,7 +4,7 @@ <bookinfo> <title>System Administrator's Guide</title> <subtitle>Deployment, Configuration, and Administration of &MAJOROSVER;</subtitle> - <productname>Fedora Draft Documentation</productname> + <productname>Fedora Documentation</productname> <productnumber></productnumber> <edition>21.0.1</edition> <pubsnumber>0</pubsnumber> diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml index 5118f7d..93b369c 100644 --- a/en-US/System_Administrators_Guide.xml +++ b/en-US/System_Administrators_Guide.xml @@ -1,7 +1,7 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> -<book status="draft"> +<book>  <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

9 years, 6 months

1
0
0 / 0

[system-administrators-guide] Created branch 21

by stephenw

The branch '21' was created pointing to: f172a0b... misc updates to preface

9 years, 6 months

1
0
0 / 0

[system-administrators-guide] misc updates to preface

by stephenw

commit f172a0be493e5a9a8f3bee1d1c90a7eef5e14fe9 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Wed Dec 10 07:51:49 2014 +0100 misc updates to preface en-US/System_Administrators_Guide.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) --- diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml index b818c43..5118f7d 100644 --- a/en-US/System_Administrators_Guide.xml +++ b/en-US/System_Administrators_Guide.xml @@ -11,14 +11,14 @@ <title>Basic System Configuration</title> <partintro> <para> - This part covers basic system administration tasks such as keyboard configuration, date and time configuration, installation and initial setup of an NTP server, and managing users and groups. + This part covers basic system administration tasks such as keyboard configuration, date and time configuration, managing users and groups, and gaining privileges. </para> </partintro> <xi:include href="Opening_GUI_Applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="System_Locale_and_Keyboard_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Configuring_the_Date_and_Time.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Managing_Users_and_Groups.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -  +  </part> <part id="part-Package_Management"> <title>Package Management</title> @@ -44,7 +44,7 @@ <title>Servers</title> <partintro> <para> - This part discusses various topics related to servers such as how to set up a Web server or share files and directories over the network. + This part discusses various topics related to servers such as how to set up a web server or share files and directories over a network. </para> </partintro> <xi:include href="Web_Servers.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

9 years, 6 months

1
0
0 / 0

[system-administrators-guide] Adding: TigerVNC chapter

by stephenw

commit 73c5df23dbf34bfbde6bccfb6f72a8ef3a139863 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Wed Dec 10 07:46:29 2014 +0100 Adding: TigerVNC chapter en-US/System_Administrators_Guide.xml | 1 + en-US/TigerVNC.xml | 376 +++++++++++++++++++++++++++++++++ 2 files changed, 377 insertions(+), 0 deletions(-) --- diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml index 3258ad7..b818c43 100644 --- a/en-US/System_Administrators_Guide.xml +++ b/en-US/System_Administrators_Guide.xml @@ -38,6 +38,7 @@ </partintro> <xi:include href="Services_and_Daemons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="OpenSSH.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="TigerVNC.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> <part id="part-Servers"> <title>Servers</title> diff --git a/en-US/TigerVNC.xml b/en-US/TigerVNC.xml new file mode 100644 index 0000000..32c88fc --- /dev/null +++ b/en-US/TigerVNC.xml @@ -0,0 +1,376 @@ +<?xml version='1.0'?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="ch-TigerVNC"> + + <title>TigerVNC</title> + <para> +<systemitem>TigerVNC</systemitem> (Tiger Virtual Network Computing) is a system +for graphical desktop sharing which allows you to remotely control other computers. + </para> + <para> +<systemitem>TigerVNC</systemitem> works on the client-server network: a +<emphasis role="bold">server</emphasis> shares its output (<systemitem>vncserver</systemitem>) and a +<emphasis role="bold">client</emphasis> (<systemitem>vncviewer</systemitem>) connects to the server. + </para> + <note> + <para> +Unlike in previous Red Hat Enterprise Linux distributions, <systemitem>TigerVNC</systemitem> in Red Hat Enterprise Linux 7 uses the <systemitem>systemd</systemitem> system management daemon for its configuration. +The <filename>/etc/sysconfig/vncserver</filename> configuration file has been replaced +by <filename>/etc/systemd/system/vncserver@.service</filename>. + </para> + </note> + <section id="s1-vnc-server"> + <title>VNC Server</title> + <para> +<systemitem>vncserver</systemitem> is a utility which starts a VNC (Virtual +Network Computing) desktop. It runs Xvnc with appropriate options and starts a window +manager on the VNC desktop. <systemitem>vncserver</systemitem> allows users to run +separate sessions in parallel on a machine which can then be accessed by any number of clients +from anywhere. + </para> + <section id="s2-vnc-installation"> + <title>Installing VNC Server</title> + <para> +To install the TigerVNC server, issue the following command as <systemitem class="username">root</systemitem>: +<screen><command><computeroutput>~]# </computeroutput><userinput>yum install tigervnc-server</userinput></command></screen> + + </para> + </section> + <section id="s3-configuring-vnc-server"> + <title>Configuring VNC Server</title> +<procedure id="configuring-vncserver"> + <title>Configuring the first VNC connection</title> + <step> + <para> +A configuration file named <filename>/etc/systemd/system/vncserver@.service</filename> is required. To create this file, copy the <filename>/lib/systemd/system/vncserver@.service</filename> file as <systemitem class="username">root</systemitem>: + </para> + <screen> +<computeroutput>~]# </computeroutput><userinput>cp /lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@.service</userinput> + </screen> + </step> + <step> + <para> +Edit <filename>/etc/systemd/system/vncserver@.service</filename>, +replacing <replaceable>USER</replaceable> with the actual user name. +Leave the remaining lines of the file unmodified. +The <option>-geometry</option> argument specifies the size of the VNC desktop to +be created; by default, it is set to <literal>1024x768</literal>. + </para> + <screen> +ExecStart=/sbin/runuser -l <replaceable>USER</replaceable> -c "/usr/bin/vncserver %i -geometry 1280x1024" +PIDFile=/home/<replaceable>USER</replaceable>/.vnc/%H%i.pid + </screen> + </step> + <step> + <para> +Save the changes. + </para> + </step> + <step> + <para> +To make the changes take effect immediately, issue the following command: + </para> +<screen> +<computeroutput>~]# </computeroutput><userinput>systemctl daemon-reload</userinput> +</screen> + </step> + <step> + <para> +Set the password for the user or users defined in the configuration file. Note +that you need to switch from <systemitem class="username">root</systemitem> to <replaceable>USER</replaceable> first. + </para> +<screen> +<computeroutput>~]# </computeroutput>su - <replaceable>USER</replaceable> +<computeroutput>~]$ </computeroutput><userinput>vncpasswd</userinput> +Password: +Verify: +</screen> + <important> + <para> +The stored password is not encrypted; anyone who has access to the password +file can find the plain-text password. + </para> + </important> + </step> + </procedure> + <section id="configuring-vncserver-2users"> + <title>Configuring VNC Server for Two Users</title> + <para> +If you want to configure more than one user on the same machine, +create different template-type service files, one for each user. + </para> +<procedure> + <step> + <para> +Create two service files, for example <filename>vncserver-<replaceable>USER_1</replaceable>@.service</filename> +and <filename>vncserver-<replaceable>USER_2</replaceable>@.service</filename>. +In both these files substitute <replaceable>USER</replaceable> with the correct user name. + </para> + </step> +<step> + <para> +Set passwords for both users: + </para> +<programlisting> +<command><computeroutput>~]$ </computeroutput><userinput>su - <replaceable>USER_1</replaceable></userinput></command> +<computeroutput>~]$ </computeroutput><userinput>vncpasswd</userinput> +Password: +Verify: +<command><computeroutput>~]$ </computeroutput><userinput>su - <replaceable>USER_2</replaceable></userinput></command> +<computeroutput>~]$ </computeroutput><userinput>vncpasswd</userinput> +Password: +Verify: +</programlisting> +</step> +</procedure> + </section> + </section> + <section id="s4-starting-vncserver"> + <title>Starting VNC Server</title> + <para> +To start or enable the service, specify the display number directly in the command. +The file configured above works as a template, in which <literal>%i</literal> is substituted with +the display number by <systemitem>systemd</systemitem>. +With a valid number, execute the following command: + </para> +<screen> +<command><computeroutput>~]# </computeroutput>systemctl start vncserver@:<replaceable>display_number</replaceable>.service</command> +</screen> + <para> +You can also enable the service to start automatically at system start. Then, when you log in, <systemitem>vncserver</systemitem> is automatically started. As <systemitem class="username">root</systemitem>, issue a command as follows: + </para> +<screen> +<command><computeroutput>~]# </computeroutput>systemctl enable vncserver@:<replaceable>display_number</replaceable>.service</command> +</screen> + <para> +At this point, other users are able to use the <systemitem>vncviewer</systemitem> +program to connect to the VNC server using the display number and password defined. + </para> + <section id="starting-vncserver-2displays"> + <title>Configuring VNC Server for two users and two different displays</title> + <para> +For the two configured VNC servers, vncserver-USER_1@.service and vncserver-USER_2@.service, +you can enable different display numbers. For example, the following commands will cause a VNC server for USER_1 to +start on display 3, and a VNC server for USER_2 to start on display 5: + </para> +<screen> +<command><computeroutput>~]# </computeroutput>systemctl start vncserver-USER_1@:3.service</command> +<command><computeroutput>~]# </computeroutput>systemctl start vncserver-USER_2@:5.service</command> +</screen> + </section> + </section> + <section id="terminating-vnc-session"> + <title>Terminating a VNC session</title> + <para> +Similarly to enabling the <systemitem>vncserver</systemitem> service, you can disable +the automatic start of the service at system start: + </para> +<screen> +<command><computeroutput>~]# </computeroutput><userinput>systemctl disable vncserver@:<replaceable>display_number</replaceable>.service</userinput></command> +</screen> + <para> +Or, when your system is running, you can stop the service by issuing the following +command as <systemitem class="username">root</systemitem>: + </para> +<screen> +<command><computeroutput>~]# </computeroutput><userinput>systemctl stop vncserver@:<replaceable>display_number</replaceable>.service</userinput></command> +</screen> + </section> + </section> + <section id="s5-vnc-viewer"> + <title>VNC Viewer</title> + <para> +<systemitem>vncviewer</systemitem> is the program which shows the shared graphical +user interfaces and controls the server. + </para> +<para> +For operating the <systemitem>vncviewer</systemitem>, there is a pop-up menu +containing entries which perform various actions such as switching in and out of +full-screen mode or quitting the viewer. Alternatively, you can operate <systemitem>vncviewer</systemitem> +through the terminal; there is a list of parameters <systemitem>vncviewer</systemitem> +can be used with which you obtain by typing <command>vncviewer -h</command> on the command line. +</para> + <section id="installing-vncviewer"> + <title>Installing VNC Viewer</title> + <para> +To install the TigerVNC client, referred to as <application>vncviewer</application>, issue the following command as <systemitem class="username">root</systemitem>: +<synopsis><command><computeroutput>~]# </computeroutput><userinput>yum install tigervnc</userinput></command></synopsis> + </para> + </section> + <section id="s6-connecting-vnc-viewer"> + <title>Connecting to VNC Server</title> + <para> +Once the VNC server is configured, you can connect to it from any VNC viewer. +In order to do so, issue the <command>vncviewer</command> command in the following format: +<synopsis>vncviewer <replaceable>IP_address</replaceable>:<replaceable>port_number</replaceable></synopsis> + </para> +<example id="connecting-to-vncserver"> + <title>One Client Connecting to vncserver</title> + <para> +With the <systemitem class="protocol">IP</systemitem> address <systemitem class="ipaddress">192.168.0.4</systemitem> and display number <emphasis>3</emphasis> +the command looks as follows: + </para> +<programlisting> +<command><computeroutput>~]$ </computeroutput><userinput>vncviewer 192.168.0.4:3</userinput></command> +</programlisting> +</example> + +<section id="sec-Configuring_the_Firewall_for_VNC"> +<title>Configuring the Firewall for VNC</title> + <para> +When using a non-encrypted connection, <systemitem>firewalld</systemitem> might +block the connection. To allow <systemitem>firewalld</systemitem> to pass the VNC packets, you can open specific ports to <systemitem class="protocol">TCP</systemitem> traffic. When using the <option>-via</option> option, traffic is redirected over <systemitem class="protocol">SSH</systemitem> which is enabled by default in <systemitem>firewalld</systemitem>. + </para> + <note> + <para> +The default port of VNC server is 5900. To reach the port through which a remote +desktop will be accessible, sum the default port and the user's +assigned display number. For example, for the second port: 2 + 5900 = 5902. + </para> + </note> + <para> + For displays <literal>0</literal> to <literal>3</literal>, make use of <systemitem>firewalld</systemitem>'s support for the VNC service by means of the <option>service</option> option as described below. Note that for display numbers greater than <literal>3</literal>, the corresponding ports will have to be opened specifically as explained in <xref linkend="proc-Opening-Ports_in_firewalld" />. + </para> +<procedure id="proc-Enabling_VNC_Service_in_firewalld"> +<title>Enabling VNC Service in firewalld</title> +<step> + <para> +Run the following command to see the information concerning <systemitem>firewalld</systemitem> +settings: + </para> +<screen> +<command><computeroutput>~]$ </computeroutput>firewall-cmd --list-all</command> +</screen> +</step> +<step> + <para> + To allow all VNC connections from a specific address, use a command as follows: + <screen>~]# <command>firewall-cmd --add-rich-rule='rule family="ipv4" source address="192.168.122.116" service name=vnc-server accept'</command> +success</screen> +See the <ulink url="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/...">Red Hat Enterprise Linux 7 Security Guide</ulink> for more information on the use of firewall rich language commands. +</para> +</step> +<step> +<para> + To verify the above settings, use a command as follows: + <screen>~]# <command>firewall-cmd --list-all</command> +public (default, active) + interfaces: bond0 bond0.192 + sources: + services: dhcpv6-client ssh + ports: + masquerade: no + forward-ports: + icmp-blocks: + rich rules: + rule family="ipv4" source address="192.168.122.116" service name="vnc-server" accept</screen> +</para> +</step> +</procedure> + +<para> + To open a specific port or range of ports make use of the <option>--list-ports</option> option to the <command>firewall-cmd</command> command Line tool. For example, VNC display <literal>4</literal> requires port <literal>5904</literal> to be opened for <systemitem class="protocol">TCP</systemitem> traffic. +</para> +<procedure id="proc-Opening-Ports_in_firewalld"> +<title>Opening Ports in firewalld</title> +<step> +<para> + To open a port for <systemitem class="protocol">TCP</systemitem> traffic in the public zone, issue a command as <systemitem class="username">root</systemitem> as follows: +<screen>~]# <command>firewall-cmd --zone=public --add-port=5904/tcp</command> +success</screen> +</para> +</step> +<step> +<para> +To view the ports that are currently open for the public zone, issue a command as follows: +<screen>~]# <command>firewall-cmd --zone=public --list-ports</command> +5904/tcp</screen> +</para> +</step> +</procedure> +<para> +A port can be removed using the <command>firewall-cmd --zone=<replaceable>zone</replaceable> --remove-port=<replaceable>number/protocol</replaceable></command> command. +</para> + +<para> + For more information on opening and closing ports in <systemitem>firewalld</systemitem>, see the <ulink url="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/...">Red Hat Enterprise Linux 7 Security Guide</ulink>. +</para> + </section> + </section> + <section id="s1-using_ssh"> + <title>Connecting to VNC Server using SSH</title> + <para> +<acronym>VNC</acronym> is a clear text network protocol with no security against possible attacks on the communication. To make the communication secure, you can encrypt your server-client connection by using the <option>-via</option> option. This will create an <systemitem class="protocol">SSH</systemitem> tunnel between the VNC server and the client. + </para> + <para> +The format of the command to encrypt a VNC server-client connection looks as follows: + </para> +<screen> +<command><computeroutput>~]$ </computeroutput><userinput>vncviewer -via <replaceable>user</replaceable>@<replaceable>host</replaceable>:<replaceable>display_number</replaceable></userinput></command> +</screen> + <example id="using-via"> + <title>Using the -via option</title> + + <procedure> + <step> + <para> + To connect to a VNC server using <systemitem class="protocol">SSH</systemitem>, enter a command as follows: + </para> +<programlisting> +<command><computeroutput>~]$ </computeroutput><userinput>vncviewer -via USER_2@192.168.2.101:3</userinput></command> +</programlisting> + </step> + <step> + <para> +When you are prompted to, type the password, and confirm by pressing <keycap>Enter</keycap>. + </para> + </step> + <step> + <para> +A window with a remote desktop appears on your screen. + </para> + </step> + </procedure> + </example> + + <bridgehead id="bh-Restricting_VNC_access">Restricting VNC access</bridgehead> + <para> +If you prefer only encrypted connections, you can prevent unencrypted connections +altogether by using the <option>-localhost</option> option in the <systemitem class="service">systemd.service</systemitem> +file, the ExecStart line: + </para> +<screen>ExecStart=/sbin/runuser -l <replaceable>user</replaceable> -c "/usr/bin/vncserver -localhost %i"</screen> +<para> +This will stop <systemitem>vncserver</systemitem> from accepting connections from anything but the local host and port-forwarded connections sent using <systemitem class="protocol">SSH</systemitem> as a result of the <option>-via</option> option. +</para> + <para> +For more information on using <systemitem class="protocol">SSH</systemitem>, see <xref linkend="ch-OpenSSH" />. + </para> + </section> + </section> + <section id="s9-additional-sources"> + <title>Additional Resources</title> + <para> + For more information about TigerVNC, see the resources listed below. + </para> + <bridgehead id="brid-TigerVNC-Resources-Installed" renderas="sect2">Installed Documentation</bridgehead> + <itemizedlist> + <listitem> + <para> + <filename>vncserver(1)</filename> — The <acronym>VNC</acronym> server manual pages. + </para> + </listitem> + <listitem> + <para> + <filename>vncviewer(1)</filename> — The <acronym>VNC</acronym> viewer manual pages. + </para> + </listitem> + <listitem> + <para> + <filename>vncpasswd(1)</filename> — The <acronym>VNC</acronym> password manual pages. + </para> + </listitem> +</itemizedlist> + </section> + +</chapter>

9 years, 6 months

1
0
0 / 0

[web] updating the installation guide a bit

by Pete Travis

commit ecce8ac087c5da48e8e2fb0fce3f07da8f0b8818 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Tue Dec 9 19:51:02 2014 -0700 updating the installation guide a bit fedoradocs.db | Bin 1049600 -> 1049600 bytes public_html/Sitemap | 8 +- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/as-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/as-IN/opds-Fedora_Core.xml | 2 +- public_html/as-IN/opds-Fedora_Documentation.xml | 2 +- .../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/as-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/as-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/bg-BG/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/bg-BG/opds-Fedora_Core.xml | 2 +- public_html/bg-BG/opds-Fedora_Documentation.xml | 2 +- .../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/bg-BG/opds-Fedora_Security_Team.xml | 2 +- public_html/bg-BG/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/bn-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/bn-IN/opds-Fedora_Core.xml | 2 +- public_html/bn-IN/opds-Fedora_Documentation.xml | 2 +- .../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/bn-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/bn-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/bs-BA/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/bs-BA/opds-Fedora_Core.xml | 2 +- public_html/bs-BA/opds-Fedora_Documentation.xml | 2 +- .../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/bs-BA/opds-Fedora_Security_Team.xml | 2 +- public_html/bs-BA/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/ca-ES/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ca-ES/opds-Fedora_Core.xml | 2 +- public_html/ca-ES/opds-Fedora_Documentation.xml | 2 +- .../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ca-ES/opds-Fedora_Security_Team.xml | 2 +- public_html/ca-ES/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/cs-CZ/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/cs-CZ/opds-Fedora_Core.xml | 2 +- public_html/cs-CZ/opds-Fedora_Documentation.xml | 2 +- .../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/cs-CZ/opds-Fedora_Security_Team.xml | 2 +- public_html/cs-CZ/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/da-DK/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/da-DK/opds-Fedora_Core.xml | 2 +- public_html/da-DK/opds-Fedora_Documentation.xml | 2 +- .../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/da-DK/opds-Fedora_Security_Team.xml | 2 +- public_html/da-DK/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/de-DE/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/de-DE/opds-Fedora_Core.xml | 2 +- public_html/de-DE/opds-Fedora_Documentation.xml | 2 +- .../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/de-DE/opds-Fedora_Security_Team.xml | 2 +- public_html/de-DE/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/el-GR/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/el-GR/opds-Fedora_Core.xml | 2 +- public_html/el-GR/opds-Fedora_Documentation.xml | 2 +- .../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/el-GR/opds-Fedora_Security_Team.xml | 2 +- public_html/el-GR/opds.xml | 16 ++-- .../Fedora-21-Installation_Guide-en-US.epub | Bin 2552632 -> 2553531 bytes .../21/html-single/Installation_Guide/index.html | 90 ++++++++++++------- .../Installation-Guide-Preface.html | 8 +- .../appe-disk-partitions-overview.html | 4 +- .../appe-kickstart-syntax-reference.html | 2 + .../21/html/Installation_Guide/ch07s02s02.html | 2 +- .../21/html/Installation_Guide/ch07s04s06.html | 2 +- .../chap-downloading-fedora.html | 20 ++++- .../Installation_Guide/chap-pxe-server-setup.html | 12 ++-- .../Installation_Guide/chap-troubleshooting.html | 2 +- .../Fedora/21/html/Installation_Guide/index.html | 10 +- .../Fedora/21/html/Installation_Guide/ix01.html | 2 +- .../part-advanced-installation-options.html | 2 +- .../Installation_Guide/part-installing-fedora.html | 4 +- .../part-technical-appendixes.html | 2 +- .../Fedora/21/html/Installation_Guide/pr01s02.html | 2 +- .../Fedora/21/html/Installation_Guide/pr01s03.html | 2 +- .../sect-boot-options-available.html | 4 +- .../sect-boot-options-network.html | 4 +- .../sect-kickstart-commands-clearpart.html | 4 +- .../sect-kickstart-commands-logvol.html | 2 + ...leshooting-problems-beginning-installation.html | 2 +- .../Fedora-21-Installation_Guide-en-US.pdf | Bin 3021121 -> 3024777 bytes .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/en-US/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/en-US/opds-Fedora_Core.xml | 2 +- public_html/en-US/opds-Fedora_Documentation.xml | 2 +- .../en-US/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/en-US/opds-Fedora_Security_Team.xml | 2 +- public_html/en-US/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/es-ES/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/es-ES/opds-Fedora_Core.xml | 2 +- public_html/es-ES/opds-Fedora_Documentation.xml | 2 +- .../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/es-ES/opds-Fedora_Security_Team.xml | 2 +- public_html/es-ES/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/fa-IR/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/fa-IR/opds-Fedora_Core.xml | 2 +- public_html/fa-IR/opds-Fedora_Documentation.xml | 2 +- .../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/fa-IR/opds-Fedora_Security_Team.xml | 2 +- public_html/fa-IR/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/fi-FI/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/fi-FI/opds-Fedora_Core.xml | 2 +- public_html/fi-FI/opds-Fedora_Documentation.xml | 2 +- .../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/fi-FI/opds-Fedora_Security_Team.xml | 2 +- public_html/fi-FI/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/fr-FR/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/fr-FR/opds-Fedora_Core.xml | 2 +- public_html/fr-FR/opds-Fedora_Documentation.xml | 2 +- .../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +- public_html/fr-FR/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/gu-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/gu-IN/opds-Fedora_Core.xml | 2 +- public_html/gu-IN/opds-Fedora_Documentation.xml | 2 +- .../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/gu-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/gu-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/he-IL/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/he-IL/opds-Fedora_Core.xml | 2 +- public_html/he-IL/opds-Fedora_Documentation.xml | 2 +- .../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/he-IL/opds-Fedora_Security_Team.xml | 2 +- public_html/he-IL/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/hi-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/hi-IN/opds-Fedora_Core.xml | 2 +- public_html/hi-IN/opds-Fedora_Documentation.xml | 2 +- .../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/hi-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/hi-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/hu-HU/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/hu-HU/opds-Fedora_Core.xml | 2 +- public_html/hu-HU/opds-Fedora_Documentation.xml | 2 +- .../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/hu-HU/opds-Fedora_Security_Team.xml | 2 +- public_html/hu-HU/opds.xml | 16 ++-- .../ia/opds-Community_Services_Infrastructure.xml | 2 +- public_html/ia/opds-Fedora.xml | 8 +- .../ia/opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ia/opds-Fedora_Core.xml | 2 +- public_html/ia/opds-Fedora_Documentation.xml | 2 +- public_html/ia/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ia/opds-Fedora_Security_Team.xml | 2 +- public_html/ia/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/id-ID/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/id-ID/opds-Fedora_Core.xml | 2 +- public_html/id-ID/opds-Fedora_Documentation.xml | 2 +- .../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/id-ID/opds-Fedora_Security_Team.xml | 2 +- public_html/id-ID/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/it-IT/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/it-IT/opds-Fedora_Core.xml | 2 +- public_html/it-IT/opds-Fedora_Documentation.xml | 2 +- .../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/it-IT/opds-Fedora_Security_Team.xml | 2 +- public_html/it-IT/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/ja-JP/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ja-JP/opds-Fedora_Core.xml | 2 +- public_html/ja-JP/opds-Fedora_Documentation.xml | 2 +- .../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ja-JP/opds-Fedora_Security_Team.xml | 2 +- public_html/ja-JP/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/kn-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/kn-IN/opds-Fedora_Core.xml | 2 +- public_html/kn-IN/opds-Fedora_Documentation.xml | 2 +- .../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/kn-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/kn-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/ko-KR/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ko-KR/opds-Fedora_Core.xml | 2 +- public_html/ko-KR/opds-Fedora_Documentation.xml | 2 +- .../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ko-KR/opds-Fedora_Security_Team.xml | 2 +- public_html/ko-KR/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/lt-LT/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/lt-LT/opds-Fedora_Core.xml | 2 +- public_html/lt-LT/opds-Fedora_Documentation.xml | 2 +- .../lt-LT/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/lt-LT/opds-Fedora_Security_Team.xml | 2 +- public_html/lt-LT/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/ml-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ml-IN/opds-Fedora_Core.xml | 2 +- public_html/ml-IN/opds-Fedora_Documentation.xml | 2 +- .../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ml-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/ml-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/mr-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/mr-IN/opds-Fedora_Core.xml | 2 +- public_html/mr-IN/opds-Fedora_Documentation.xml | 2 +- .../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/mr-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/mr-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/nb-NO/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/nb-NO/opds-Fedora_Core.xml | 2 +- public_html/nb-NO/opds-Fedora_Documentation.xml | 2 +- .../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/nb-NO/opds-Fedora_Security_Team.xml | 2 +- public_html/nb-NO/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/nl-NL/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/nl-NL/opds-Fedora_Core.xml | 2 +- public_html/nl-NL/opds-Fedora_Documentation.xml | 2 +- .../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +- public_html/nl-NL/opds.xml | 16 ++-- public_html/opds.xml | 92 ++++++++++---------- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/or-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/or-IN/opds-Fedora_Core.xml | 2 +- public_html/or-IN/opds-Fedora_Documentation.xml | 2 +- .../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/or-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/or-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/pa-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/pa-IN/opds-Fedora_Core.xml | 2 +- public_html/pa-IN/opds-Fedora_Documentation.xml | 2 +- .../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/pa-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/pa-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/pl-PL/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/pl-PL/opds-Fedora_Core.xml | 2 +- public_html/pl-PL/opds-Fedora_Documentation.xml | 2 +- .../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/pl-PL/opds-Fedora_Security_Team.xml | 2 +- public_html/pl-PL/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/pt-BR/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/pt-BR/opds-Fedora_Core.xml | 2 +- public_html/pt-BR/opds-Fedora_Documentation.xml | 2 +- .../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/pt-BR/opds-Fedora_Security_Team.xml | 2 +- public_html/pt-BR/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/pt-PT/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/pt-PT/opds-Fedora_Core.xml | 2 +- public_html/pt-PT/opds-Fedora_Documentation.xml | 2 +- .../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/pt-PT/opds-Fedora_Security_Team.xml | 2 +- public_html/pt-PT/opds.xml | 16 ++-- .../ro/opds-Community_Services_Infrastructure.xml | 2 +- public_html/ro/opds-Fedora.xml | 8 +- .../ro/opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ro/opds-Fedora_Core.xml | 2 +- public_html/ro/opds-Fedora_Documentation.xml | 2 +- public_html/ro/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ro/opds-Fedora_Security_Team.xml | 2 +- public_html/ro/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/ru-RU/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ru-RU/opds-Fedora_Core.xml | 2 +- public_html/ru-RU/opds-Fedora_Documentation.xml | 2 +- .../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ru-RU/opds-Fedora_Security_Team.xml | 2 +- public_html/ru-RU/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/sk-SK/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/sk-SK/opds-Fedora_Core.xml | 2 +- public_html/sk-SK/opds-Fedora_Documentation.xml | 2 +- .../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/sk-SK/opds-Fedora_Security_Team.xml | 2 +- public_html/sk-SK/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/sr-Latn-RS/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +- .../sr-Latn-RS/opds-Fedora_Documentation.xml | 2 +- .../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +- .../sr-Latn-RS/opds-Fedora_Security_Team.xml | 2 +- public_html/sr-Latn-RS/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/sr-RS/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/sr-RS/opds-Fedora_Core.xml | 2 +- public_html/sr-RS/opds-Fedora_Documentation.xml | 2 +- .../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/sr-RS/opds-Fedora_Security_Team.xml | 2 +- public_html/sr-RS/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/sv-SE/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/sv-SE/opds-Fedora_Core.xml | 2 +- public_html/sv-SE/opds-Fedora_Documentation.xml | 2 +- .../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/sv-SE/opds-Fedora_Security_Team.xml | 2 +- public_html/sv-SE/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/ta-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/ta-IN/opds-Fedora_Core.xml | 2 +- public_html/ta-IN/opds-Fedora_Documentation.xml | 2 +- .../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/ta-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/ta-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/te-IN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/te-IN/opds-Fedora_Core.xml | 2 +- public_html/te-IN/opds-Fedora_Documentation.xml | 2 +- .../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/te-IN/opds-Fedora_Security_Team.xml | 2 +- public_html/te-IN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/uk-UA/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/uk-UA/opds-Fedora_Core.xml | 2 +- public_html/uk-UA/opds-Fedora_Documentation.xml | 2 +- .../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/uk-UA/opds-Fedora_Security_Team.xml | 2 +- public_html/uk-UA/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/zh-CN/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/zh-CN/opds-Fedora_Core.xml | 2 +- public_html/zh-CN/opds-Fedora_Documentation.xml | 2 +- .../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/zh-CN/opds-Fedora_Security_Team.xml | 2 +- public_html/zh-CN/opds.xml | 16 ++-- .../opds-Community_Services_Infrastructure.xml | 2 +- public_html/zh-TW/opds-Fedora.xml | 8 +- .../opds-Fedora_Contributor_Documentation.xml | 2 +- public_html/zh-TW/opds-Fedora_Core.xml | 2 +- public_html/zh-TW/opds-Fedora_Documentation.xml | 2 +- .../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +- public_html/zh-TW/opds-Fedora_Security_Team.xml | 2 +- public_html/zh-TW/opds.xml | 16 ++-- 386 files changed, 973 insertions(+), 929 deletions(-) --- diff --git a/fedoradocs.db b/fedoradocs.db index 9e55124..683a5db 100755 Binary files a/fedoradocs.db and b/fedoradocs.db differ diff --git a/public_html/Sitemap b/public_html/Sitemap index 306564f..d674495 100644 --- a/public_html/Sitemap +++ b/public_html/Sitemap @@ -1952,25 +1952,25 @@ </url> <url> <loc>https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe...</loc> - <lastmod>2014-12-09</lastmod> + <lastmod>2014-12-10</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url> <url> <loc>https://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/in...</loc> - <lastmod>2014-12-09</lastmod> + <lastmod>2014-12-10</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url> <url> <loc>https://docs.fedoraproject.org/en-US/Fedora/21/html-single/Installation_G...</loc> - <lastmod>2014-12-09</lastmod> + <lastmod>2014-12-10</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url> <url> <loc>https://docs.fedoraproject.org/en-US/Fedora/21/pdf/Installation_Guide/Fed...</loc> - <lastmod>2014-12-09</lastmod> + <lastmod>2014-12-10</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url> diff --git a/public_html/as-IN/opds-Community_Services_Infrastructure.xml b/public_html/as-IN/opds-Community_Services_Infrastructure.xml index 0266c3f..10d0358 100644 --- a/public_html/as-IN/opds-Community_Services_Infrastructure.xml +++ b/public_html/as-IN/opds-Community_Services_Infrastructure.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/as-IN/opds-Community_Services_Infrastructu...</id> <title>Community Services Infrastructure</title> <subtitle>Community Services Infrastructure</subtitle> - <updated>2014-12-09T15:57:32</updated> + <updated>2014-12-10T02:49:02</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>as-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml index 7c0a08b..216477c 100644 --- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:33</updated> + <updated>2014-12-10T02:49:03</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>bg-BG</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml index c541911..14b623e 100644 --- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:34</updated> + <updated>2014-12-10T02:49:03</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>bn-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml index 7afc3cd..0cef4fa 100644 --- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:35</updated> + <updated>2014-12-10T02:49:04</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>bs-BA</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml index e952b02..057ce40 100644 --- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:35</updated> + <updated>2014-12-10T02:49:05</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ca-ES</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml index 2836f09..93b0440 100644 --- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:36</updated> + <updated>2014-12-10T02:49:06</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>cs-CZ</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml index fd31f51..b4ded7d 100644 --- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:36</updated> + <updated>2014-12-10T02:49:06</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>da-DK</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml index db3dedb..0536053 100644 --- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:37</updated> + <updated>2014-12-10T02:49:07</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>de-DE</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml index b55dddc..02f3571 100644 --- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:38</updated> + <updated>2014-12-10T02:49:08</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>el-GR</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml index 3678c42..2421ff6 100644 --- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:38</updated> + <updated>2014-12-10T02:49:08</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>en-US</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml index c5a0a1c..8a5a9c1 100644 --- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:39</updated> + <updated>2014-12-10T02:49:09</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>es-ES</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml index 4cdfcce..8ca8889 100644 --- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Documentación de Contribuyente</title> <subtitle>Fedora Documentación de Contribuyente</subtitle> - <updated>2014-12-09T15:57:40</updated> + <updated>2014-12-10T02:49:10</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>fa-IR</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml index 823bdf9..a43484d 100644 --- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documentatio...</id> <title>مستندات مشارکت کننده فدورا</title> <subtitle>مستندات مشارکت کننده فدورا</subtitle> - <updated>2014-12-09T15:57:40</updated> + <updated>2014-12-10T02:49:11</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>fi-FI</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml index 5b1f32e..b0b93a9 100644 --- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:41</updated> + <updated>2014-12-10T02:49:11</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>fr-FR</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml index 724da72..db8702d 100644 --- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:42</updated> + <updated>2014-12-10T02:49:12</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>gu-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml index 74fa648..d60ff21 100644 --- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:42</updated> + <updated>2014-12-10T02:49:13</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>he-IL</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml index 62d71ea..92314b7 100644 --- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:43</updated> + <updated>2014-12-10T02:49:14</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>hi-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml index 2835561..54bc8a0 100644 --- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:44</updated> + <updated>2014-12-10T02:49:14</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>hu-HU</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml index db9d914..be3150f 100644 --- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:45</updated> + <updated>2014-12-10T02:49:15</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ia</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ia/opds-Fedora_Contributor_Documentation.xml b/public_html/ia/opds-Fedora_Contributor_Documentation.xml index fa6cdf7..6cba0dc 100644 --- a/public_html/ia/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ia/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ia/opds-Fedora_Contributor_Documentation.xml</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:45</updated> + <updated>2014-12-10T02:49:15</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>id-ID</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml index dea454d..e9526bf 100644 --- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:46</updated> + <updated>2014-12-10T02:49:16</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>it-IT</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml index 8fd2698..87414df 100644 --- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documentatio...</id> <title>Documentazione Collaboratori Fedora</title> <subtitle>Documentazione Collaboratori Fedora</subtitle> - <updated>2014-12-09T15:57:47</updated> + <updated>2014-12-10T02:49:17</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ja-JP</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml index 62cdf18..1eabf10 100644 --- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora コントリビュータ用ドキュメント</title> <subtitle>Fedora コントリビュータ用ドキュメント</subtitle> - <updated>2014-12-09T15:57:48</updated> + <updated>2014-12-10T02:49:18</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>kn-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml index 143730d..e6f1e4e 100644 --- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:48</updated> + <updated>2014-12-10T02:49:18</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ko-KR</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml index 36b1829..4538f41 100644 --- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:49</updated> + <updated>2014-12-10T02:49:19</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>lt-LT</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml index a71a104..8d3a93c 100644 --- a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/lt-LT/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:49</updated> + <updated>2014-12-10T02:49:20</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ml-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml index b1788de..2b55aa3 100644 --- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:50</updated> + <updated>2014-12-10T02:49:20</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>mr-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml index f8580cd..50f8421 100644 --- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:50</updated> + <updated>2014-12-10T02:49:21</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>nb-NO</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml index 2d4ee31..237726f 100644 --- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:51</updated> + <updated>2014-12-10T02:49:22</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>nl-NL</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml index b732688..bb91e1c 100644 --- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:52</updated> + <updated>2014-12-10T02:49:23</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>or-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml index 1a315cd..62aecab 100644 --- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:53</updated> + <updated>2014-12-10T02:49:23</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>pa-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml index 7826ef0..d1aef4f 100644 --- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:54</updated> + <updated>2014-12-10T02:49:24</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>pl-PL</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml index 32062af..c22a8f1 100644 --- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documentatio...</id> <title>Dokumentacja dla współtwórców Fedory</title> <subtitle>Dokumentacja dla współtwórców Fedory</subtitle> - <updated>2014-12-09T15:57:54</updated> + <updated>2014-12-10T02:49:25</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>pt-BR</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml index 73ce9bb..1b5bbc0 100644 --- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:55</updated> + <updated>2014-12-10T02:49:26</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>pt-PT</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml index f45d5c7..d2b7a1d 100644 --- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:56</updated> + <updated>2014-12-10T02:49:27</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ro</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ro/opds-Fedora_Contributor_Documentation.xml b/public_html/ro/opds-Fedora_Contributor_Documentation.xml index 7d055f8..db058c7 100644 --- a/public_html/ro/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ro/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentation.xml</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:57</updated> + <updated>2014-12-10T02:49:27</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ru-RU</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml index d279098..91b9cf8 100644 --- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documentatio...</id> <title>Документация участника Fedora</title> <subtitle>Документация участника Fedora</subtitle> - <updated>2014-12-09T15:57:57</updated> + <updated>2014-12-10T02:49:28</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>sk-SK</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml index 5ede753..3768a93 100644 --- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:58</updated> + <updated>2014-12-10T02:49:29</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>sr-Latn-RS</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml index 2ac7b17..d42a0ee 100644 --- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Documen...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:57:59</updated> + <updated>2014-12-10T02:49:30</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>sr-RS</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml index c577dc6..7ec7c33 100644 --- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:58:00</updated> + <updated>2014-12-10T02:49:31</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>sv-SE</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml index 7c0e84e..8bfdf27 100644 --- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:58:00</updated> + <updated>2014-12-10T02:49:31</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>ta-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml index 8aeed6c..40c2792 100644 --- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:58:01</updated> + <updated>2014-12-10T02:49:32</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>te-IN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml index 0d4e577..88d1610 100644 --- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:58:01</updated> + <updated>2014-12-10T02:49:33</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>uk-UA</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml index dac315c..3e19bf2 100644 --- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documentatio...</id> <title>Документація для учасника розробки Fedora</title> <subtitle>Документація для учасника розробки Fedora</subtitle> - <updated>2014-12-09T15:58:02</updated> + <updated>2014-12-10T02:49:34</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>zh-CN</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml index b839172..236e686 100644 --- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:58:03</updated> + <updated>2014-12-10T02:49:35</updated>  - <updated>2014-12-09</updated> + <updated>2014-12-10</updated> <dc:language>zh-TW</dc:language> <category label="21" scheme="http://lexcycle.com/stanza/header" term="free"/>  - <summary>Installing Fedora 21 on 32 and 64-bit Intel-compatible systems and ARM systems</summary> - <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems and on ARM systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> + <summary>Installing Fedora 21 on 32 and 64-bit AMD and Intel</summary> + <content type="text">This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 21 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.</content> <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="https://docs.fedoraproject.org/en-US/Fedora/21/epub/Installation_Guide/Fe..."> <dc:format>application/epub+zip</dc:format> </link> diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml index bbbeae4..358d2cc 100644 --- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml +++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documentatio...</id> <title>Fedora Contributor Documentation</title> <subtitle>Fedora Contributor Documentation</subtitle> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <!--author> <name></name> <uri></uri> diff --git a/public_html/zh-TW/opds-Fedora_Core.xml b/public_html/zh-TW/opds-Fedora_Core.xml index 4cb9ddf..1ecf2e2 100644 --- a/public_html/zh-TW/opds-Fedora_Core.xml +++ b/public_html/zh-TW/opds-Fedora_Core.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id> <title>Fedora Core</title> <subtitle>Fedora Core</subtitle> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <!--author> <name></name> <uri></uri> diff --git a/public_html/zh-TW/opds-Fedora_Documentation.xml b/public_html/zh-TW/opds-Fedora_Documentation.xml index 2f4ffc8..57fa22a 100644 --- a/public_html/zh-TW/opds-Fedora_Documentation.xml +++ b/public_html/zh-TW/opds-Fedora_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/zh-TW/opds-Fedora_Documentation.xml</id> <title>Fedora Documentation</title> <subtitle>Fedora Documentation</subtitle> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <!--author> <name></name> <uri></uri> diff --git a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml index 013b6c4..f84e8df 100644 --- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml +++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation.xml</id> <title>Fedora Draft Documentation</title> <subtitle>Fedora Draft Documentation</subtitle> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <!--author> <name></name> <uri></uri> diff --git a/public_html/zh-TW/opds-Fedora_Security_Team.xml b/public_html/zh-TW/opds-Fedora_Security_Team.xml index 48e1b9e..436228b 100644 --- a/public_html/zh-TW/opds-Fedora_Security_Team.xml +++ b/public_html/zh-TW/opds-Fedora_Security_Team.xml @@ -6,7 +6,7 @@ <id>https://docs.fedoraproject.org/zh-TW/opds-Fedora_Security_Team.xml</id> <title>Fedora Security Team</title> <subtitle>Fedora Security Team</subtitle> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <!--author> <name></name> <uri></uri> diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml index ed7550d..a50ec2e 100644 --- a/public_html/zh-TW/opds.xml +++ b/public_html/zh-TW/opds.xml @@ -6,7 +6,7 @@ <link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/> <id>https://docs.fedoraproject.org/zh-TW/opds.xml</id> <title>Product List</title> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <!--author> <name></name> <uri></uri> @@ -15,7 +15,7 @@ <entry> <title>Community Services Infrastructure</title> <id>https://docs.fedoraproject.org/zh-TW/Community_Services_Infrastructure/op...</id> - <updated>2014-12-09T15:58:03</updated> + <updated>2014-12-10T02:49:35</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/> @@ -23,7 +23,7 @@ <entry> <title>Fedora</title> <id>https://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Fedora.xml"/> @@ -31,7 +31,7 @@ <entry> <title>Fedora Contributor Documentation</title> <id>https://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentation/opd...</id> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/> @@ -39,7 +39,7 @@ <entry> <title>Fedora Core</title> <id>https://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xml</id> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Fedora_Core.xml"/> @@ -47,7 +47,7 @@ <entry> <title>Fedora Documentation</title> <id>https://docs.fedoraproject.org/zh-TW/Fedora_Documentation/opds-Fedora_Doc...</id> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/> @@ -55,7 +55,7 @@ <entry> <title>Fedora Draft Documentation</title> <id>https://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds-Fedo...</id> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/> @@ -63,7 +63,7 @@ <entry> <title>Fedora Security Team</title> <id>https://docs.fedoraproject.org/zh-TW/Fedora_Security_Team/opds-Fedora_Sec...</id> - <updated>2014-12-09T15:58:04</updated> + <updated>2014-12-10T02:49:36</updated> <dc:language>zh-TW</dc:language> <content type="text"></content> <link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] some people have arch questions

by Pete Travis

commit dce8911ca06377501429eb323b5816d8542f6a3a Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Tue Dec 9 18:36:45 2014 -0700 some people have arch questions en-US/Downloading_Fedora.xml | 35 ++++++++++++++++++++++++++++++++++- 1 files changed, 34 insertions(+), 1 deletions(-) --- diff --git a/en-US/Downloading_Fedora.xml b/en-US/Downloading_Fedora.xml index fdb1026..650dc0f 100644 --- a/en-US/Downloading_Fedora.xml +++ b/en-US/Downloading_Fedora.xml @@ -14,7 +14,40 @@ </para> <para> Each of these downloads provides a different set of default packages, but you can add to your system after the initial installation to customize it for your needs. The installation process is the same for all spins and flavors, so you can use this guide for any choice you make. - </para> + </para> + + <bridgehead>Which Architecture Is My Computer?</bridgehead> + <para> + Most modern systems are 64 bit x86 architecture. If your computer was manufactured after 2007, or you aren't sure, you probably have a <literal>x86_64</literal> system. + </para> + <para> + Changing a Fedora installation from one architecture to another is not supported. Use the following table to determine the architecture of your computer according to the type of processor. Consult your manufacturer's documentation for details on your processor, or resources such as <ulink url="http://ark.intel.com/" /> or <ulink url="http://products.amd.com/" />, if necessary. + </para> + + <table id="List-Processor_and_Architecture_Types" frame='all'><title>Processor and architecture types</title> + <tgroup cols='2' align='left' colsep='1' rowsep='1'> + <colspec colnum="1" colwidth="3*"/> + <colspec colnum="2" colwidth="1*"/> + <thead> + <row> + <entry>Processor manufacturer and model</entry> + <entry>Architecture type for Fedora</entry> + </row> + </thead> + <tbody> + <row> + <entry>some Intel Atom, Core series, Pentium 4, and recent vintage Xeon; AMD Athlon, Duron, some Semprons; and older; VIA C3, C7</entry> + <entry><systemitem>i386</systemitem></entry> + </row> + <row> + <entry>some Intel Atom, Core 2 series, Core i series and Xeon; +AMD: Athlon 64, Athlon II, Sempron64, Phenom series, Fusion series, Bulldozer series and Opteron; Apple MacBook, MacBook Pro, and MacBook Air</entry> + <entry><systemitem>x86_64</systemitem></entry> + </row> + </tbody> + </tgroup> + </table> + <bridgehead>Media Types</bridgehead> <para> Several media types are available. Choose the one that best suits your requirements.

9 years, 6 months

1
0
0 / 0

[system-administrators-guide] Improvements from upstream version

by stephenw

commit 9a9ac7d1cfa66cfc4a128df6a84899b8ec1684b6 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Tue Dec 9 23:32:41 2014 +0100 Improvements from upstream version en-US/Automating_System_Tasks.xml | 769 ++++++++++++++++++++++++++----------- 1 files changed, 535 insertions(+), 234 deletions(-) --- diff --git a/en-US/Automating_System_Tasks.xml b/en-US/Automating_System_Tasks.xml index 8891224..d9e6afc 100644 --- a/en-US/Automating_System_Tasks.xml +++ b/en-US/Automating_System_Tasks.xml @@ -3,65 +3,130 @@ ]> <chapter id="ch-Automating_System_Tasks"> <title>Automating System Tasks</title> - <indexterm significance="normal"> + <indexterm> <primary>Automated Tasks</primary> </indexterm> - <para>In Linux, tasks, which are also known as <firstterm>jobs</firstterm>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average is below a specified number. &MAJOROS; is pre-configured to run important system tasks to keep the system updated. For example, the slocate database used by the <command>locate</command> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and more.</para> - <para>&MAJOROS; comes with several automated tasks utilities: <command>cron</command>, <command>at</command>, and <command>batch</command>.</para> - <indexterm significance="normal"> - <primary>Cron</primary> - </indexterm> + <para> + Tasks, also known as <firstterm>jobs</firstterm>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average decreases below 0.8. + </para> + <para> + &MAJOROS; is pre-configured to run important system tasks to keep the system updated. For example, the <database>slocate</database> database used by the <command>locate</command> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and so on. + </para> + <para> + &MAJOROS; comes with the following automated task utilities: <command>cron</command>, <command>anacron</command>, <command>at</command>, and <command>batch</command>. + </para> + <para> + Every utility is intended for scheduling a different job type: while Cron and Anacron schedule recurring jobs, At and Batch schedule one-time jobs (refer to <xref linkend="s1-autotasks-cron-anacron" /> and <xref linkend="s1-autotasks-at-batch" /> respectively). + </para> + <para> + &MAJOROS; supports the use of <systemitem>systemd.timer</systemitem> for executing a job at a specific time. See man <filename>systemd.timer(5)</filename> for more information. + </para> <section id="s1-autotasks-cron-anacron"> <title>Cron and Anacron</title> - <indexterm significance="normal"> - <primary>anacron</primary> - </indexterm> - <indexterm significance="normal"> - <primary> - <filename>cron</filename> - </primary> - </indexterm> - <para>Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.</para> - <para>Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day. - To schedule recurring jobs, refer to <xref linkend="s2-configuring-anacron-jobs"/> or <xref linkend="s2-configuring-cron-jobs"/>. To schedule one-time jobs, refer to <xref linkend="s1-autotasks-at-batch"/>.</para> - <para>To use the cron service, the <filename>cronie</filename> RPM package must be installed and the <command>crond</command> service must be running. <filename>anacron</filename> is a sub-package of <filename>cronie</filename>. To determine if these packages are installed, use the <command>rpm -q cronie cronie-anacron</command> command. </para> - <section id="s2-autotasks-cron-service"> - <title>Starting and Stopping the Service</title> - <para>To determine if the service is running, use the following command:</para> - <screen><command>systemctl is-active crond.service</command></screen> - <para>To start the cron service, type the following at a shell prompt as <systemitem class="username">root</systemitem>:</para> - <screen><command>systemctl start crond.service</command></screen> - <para>To stop the service, run the following command as <systemitem class="username">root</systemitem>:</para> - <screen><command>systemctl stop crond.service</command></screen> - <para>It is recommended that you start the service at boot time. To do so, use the following command as <systemitem class="username">root</systemitem>:</para> - <screen><command>systemctl enable crond.service</command></screen> - <para> - See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;. + <indexterm> + <primary>anacron</primary> + </indexterm> + <indexterm> + <primary>cron</primary> + </indexterm> + <para> + Both Cron and Anacron are daemons that can schedule execution of recurring tasks to a certain point in time defined by the exact time, day of the month, month, day of the week, and week. + </para> + <para> + Cron jobs can run as often as every minute. However, the utility assumes that the system is running continuously and if the system is not on at the time when a job is scheduled, the job is not executed. + </para> + <para> + On the other hand, Anacron remembers the scheduled jobs if the system is not running at the time when the job is scheduled. The job is then executed as soon as the system is up. However, Anacron can only run a job once a day. + </para> + <section id="sect-Cron-Installing"> + <title>Installing Cron and Anacron</title> + <para> + To install Cron and Anacron, you need to install the <package>cronie</package> package with Cron and the <package>cronie-anacron</package> package with Anacron (<package>cronie-anacron</package> is a sub-package of <package>cronie</package>). + </para> + <para> + To determine if the packages are already installed on your system, issue the following command: + </para> + <synopsis><command>rpm -q cronie cronie-anacron</command></synopsis> + <para> + The command returns full names of the <package>cronie</package> and <package>cronie-anacron</package> packages if already installed, or notifies you that the packages are not available. + </para> + <para> + To install these packages, use the <command>yum</command> command in the following form as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>yum install <replaceable>package</replaceable></command></synopsis> + <para> + For example, to install both Cron and Anacron, type the following at a shell prompt: + </para> + <screen>~]# <command>yum install cronie cronie-anacron</command></screen> + <para> + For more information on how to install new packages in &MAJOROS;, see <xref linkend="sec-Installing" />. + </para> + </section> + <section id="sect-Cron-Running"> + <title>Running the Crond Service</title> + <para> + The cron and anacron jobs are both picked by the <systemitem class="daemon">crond</systemitem> service. This section provides information on how to start, stop, and restart the <systemitem class="service">crond</systemitem> service, and shows how to configure it to start automatically at boot time.  </para> + <section id="sect-Cron-service"> + <title>Starting and Stopping the Cron Service</title> + <para> + To determine if the service is running, use the following command: + </para> + <synopsis><command>systemctl status crond.service</command></synopsis> + <para> + To run the <systemitem class="service">crond</systemitem> service in the current session, type the following at a shell prompt as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl start crond.service</command></synopsis> + <para> + To configure the service to start automatically at boot time, use the following command as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl enable crond.service</command></synopsis> + </section> + <section id="sect-Crond_Stopping"> + <title>Stopping the Cron Service</title> + <para> + To stop the <systemitem class="service">crond</systemitem> service in the current session, type the following at a shell prompt as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl stop crond.service</command></synopsis> + <para> + To prevent the service from starting automatically at boot time, use the following command as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl disable crond.service</command></synopsis> + </section> + <section id="sect-Crond_Restarting"> + <title>Restarting the Cron Service</title> + <para> + To restart the <systemitem class="service">crond</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl restart crond.service</command></synopsis> + <para> + This command stops the service and starts it again in quick succession. + </para> + </section> </section> <section id="s2-configuring-anacron-jobs"> <title>Configuring Anacron Jobs</title> - <indexterm significance="normal"> + <indexterm> <primary>anacron</primary> <secondary>anacron configuration file</secondary> </indexterm> - <indexterm significance="normal"> + <indexterm> <primary> <filename>anacrontab</filename> </primary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>anacron</primary> <secondary>user-defined tasks</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <filename>/var/spool/anacron</filename> </primary> </indexterm> - <para>The main configuration file to schedule jobs is <filename>/etc/anacrontab</filename> (only <systemitem class="username">root</systemitem> is allowed to modify this file), which contains the following lines:</para> + <para> + The main configuration file to schedule jobs is the <filename>/etc/anacrontab</filename> file, which can be only accessed by the <systemitem class="username">root</systemitem> user. The file contains the following: + </para> <programlisting>SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root @@ -75,39 +140,88 @@ START_HOURS_RANGE=3-22 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly</programlisting> <para> - The first three lines are variables used to configure the environment in which the anacron tasks are run. The <computeroutput>SHELL</computeroutput> variable tells the system which shell environment to use (in this example the bash shell). The <computeroutput>PATH</computeroutput> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <computeroutput>MAILTO</computeroutput> variable. If the <computeroutput>MAILTO</computeroutput> variable is not defined, (i.e. is empty, <computeroutput>MAILTO=</computeroutput>), email is not sent. -</para> + The first three lines define the variables that configure the environment in which the anacron tasks run: + </para> + <itemizedlist> + <listitem> + <para><varname>SHELL</varname> — shell environment used for running jobs (in the example, the Bash shell) + </para> + </listitem> + <listitem> + <para><varname>PATH</varname> — paths to executable programs + </para> + </listitem> + <listitem> + <para><varname>MAILTO</varname> — username of the user who receives the output of the anacron jobs by email + </para> + <para> + If the <varname>MAILTO</varname> variable is not defined (<code>MAILTO=</code>), the email is not sent. + </para> + </listitem> + </itemizedlist> <para> - The next two lines are variables that modify the time for each scheduled job. The <computeroutput>RANDOM_DELAY</computeroutput> variable denotes the maximum number of minutes that will be added to the <filename>delay in minutes</filename> variable which is specified for each job. The minimum delay value is set, by default, to 6 minutes. A <computeroutput>RANDOM_DELAY</computeroutput> set to 12 would therefore add, randomly, between 6 and 12 minutes to the <filename>delay in minutes</filename> for each job in that particular anacrontab. <computeroutput>RANDOM_DELAY</computeroutput> can also be set to a value below 6, or even 0. When set to 0, no random delay is added. This proves to be useful when, for example, more computers that share one network connection need to download the same data every day. The <computeroutput>START_HOURS_RANGE</computeroutput> variable defines an interval (in hours) when scheduled jobs can be run. In case this time interval is missed, for example , due to a power down, then scheduled jobs are not executed that day. -</para> - <para>The rest of the lines in the <filename>/etc/anacrontab</filename> file represent scheduled jobs and have the following format: -</para> - <programlisting>period in days delay in minutes job-identifier command</programlisting> + The next two variables modify the scheduled time for the defined jobs: + </para> <itemizedlist> <listitem> + <para><varname>RANDOM_DELAY</varname> — maximum number of minutes that will be added to the <varname>delay in minutes</varname> variable which is specified for each job + </para> <para> - <computeroutput>period in days</computeroutput> — specifies the frequency of execution of a job in days. This variable can be represented by an integer or a macro (<computeroutput>@daily</computeroutput>, <computeroutput>@weekly</computeroutput>, <computeroutput>@monthly</computeroutput>), where <computeroutput>@daily</computeroutput> denotes the same value as the integer 1, <computeroutput>@weekly</computeroutput> the same as 7, and <computeroutput>@monthly</computeroutput> specifies that the job is run once a month, independent on the length of the month. - </para> + The minimum delay value is set, by default, to 6 minutes. + </para> + <para> + If <varname>RANDOM_DELAY</varname> is, for example, set to <literal>12</literal>, then between 6 and 12 minutes are added to the <varname>delay in minutes</varname> for each job in that particular anacrontab. <varname>RANDOM_DELAY</varname> can also be set to a value below <literal>6</literal>, including <literal>0</literal>. When set to <literal>0</literal>, no random delay is added. This proves to be useful when, for example, more computers that share one network connection need to download the same data every day. + </para> + </listitem> + <listitem> + <para><varname>START_HOURS_RANGE</varname> — interval, when scheduled jobs can be run, in hours + </para> + <para> + In case the time interval is missed, for example due to a power failure, the scheduled jobs are not executed that day. + </para> </listitem> + </itemizedlist> + <para> + The remaining lines in the <filename>/etc/anacrontab</filename> file represent scheduled jobs and follow this format: + </para> + <screen> +period in days delay in minutes job-identifier command +</screen> + <itemizedlist> <listitem> + <para><varname>period in days</varname> — frequency of job execution in days + </para> <para> - <computeroutput>delay in minutes</computeroutput> — specifies the number of minutes anacron waits, if necessary, before executing a job. This variable is represented by an integer where 0 means no delay. + The property value can be defined as an integer or a macro (<literal>@daily</literal>, <literal>@weekly</literal>, <literal>@monthly</literal>), where <literal>@daily</literal> denotes the same value as integer 1, <literal>@weekly</literal> the same as 7, and <literal>@monthly</literal> specifies that the job is run once a month regardless of the length of the month. </para> </listitem> <listitem> + <para><varname>delay in minutes</varname> — number of minutes anacron waits before executing the job + </para> <para> - <computeroutput>job-identifier</computeroutput> — specifies a unique name of a job which is used in the log files. - </para> + The property value is defined as an integer. If the value is set to <literal>0</literal>, no delay applies. + </para> +  + </listitem> + <listitem> + <para><varname>job-identifier</varname> — unique name referring to a particular job used in the log files + </para> </listitem> <listitem> + <para><varname>command</varname> — command to be executed + </para> <para> - <computeroutput>command</computeroutput> — specifies the command to execute. The command can either be a command such as <computeroutput>ls /proc >> /tmp/proc</computeroutput> or a command to execute a custom script. - </para> + The command can be either a command such as <command>ls /proc >> /tmp/proc</command> or a command which executes a custom script. + </para> </listitem> </itemizedlist> <para>Any lines that begin with a hash sign (#) are comments and are not processed.</para> <section id="s3-anacron-examples"> - <title>Examples of Anacron Jobs </title> + <title>Examples of Anacron Jobs</title> <para>The following example shows a simple <filename>/etc/anacrontab</filename> file:</para> <programlisting>SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin @@ -121,43 +235,44 @@ START_HOURS_RANGE=16-20 #period in days delay in minutes job-identifier command 1 20 dailyjob nice run-parts /etc/cron.daily 7 25 weeklyjob /etc/weeklyjob.bash -@monthly 45 monthlyjob ls /proc >> /tmp/proc</programlisting> +@monthly 45 monthlyjob ls /proc >> /tmp/proc</programlisting> + <para> + All jobs defined in this <filename>anacrontab</filename> file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00. + </para> <para> - All jobs defined in this <filename>anacrontab</filename> file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <filename>/etc/cron.daily</filename> directory (using the <command>run-parts</command> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <filename>weeklyjob.bash</filename> script in the <filename>/etc</filename> directory. The third job is executed once a month and runs a command to write the contents of the <filename>/proc</filename> to the <filename>/tmp/proc</filename> file (e.g. <computeroutput>ls /proc >> /tmp/proc</computeroutput>). -</para> -<section id="s3-disabling-anacron"> -<title>Disabling Anacron</title> -<para> - In case your system is continuously on and you do not require anacron to run your scheduled jobs, you may uninstall the <filename>cronie-anacron</filename> package. Thus, you will be able to define jobs using crontabs only. -</para> -</section> + The first defined job is triggered daily between 16:26 and 16:50 (RANDOM_DELAY is between 6 and 30 minutes; the <property>delay in minutes</property> property adds 20 minutes). The command specified for this job executes all present programs in the <filename class="directory">/etc/cron.daily/</filename> directory using the <command>run-parts</command> script (the <command>run-parts</command> scripts accepts a directory as a command-line argument and sequentially executes every program in the directory). See the <filename>run-parts</filename> man page for more information on the <command>run-parts</command> script. + </para> + <para> + The second job executes the <filename>weeklyjob.bash</filename> script in the <filename class="directory">/etc/</filename> directory once a week. + </para> + <para> + The third job runs a command, which writes the contents of <filename>/proc</filename> to the <filename>/tmp/proc</filename> file (<command>ls /proc >> /tmp/proc</command>) once a month. + </para> </section> </section> <section id="s2-configuring-cron-jobs"> <title>Configuring Cron Jobs</title> - <indexterm - significance="normal"> + <indexterm> <primary>cron</primary> <secondary>user-defined tasks</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <filename>/var/spool/cron</filename> </primary> </indexterm> - <indexterm significance="normal"> + <indexterm> <primary>cron</primary> <secondary>cron configuration file</secondary> </indexterm> - <indexterm significance="normal"> + <indexterm> <primary> <filename>crontab</filename> </primary> </indexterm> <para> - The configuration file to configure cron jobs, <filename>/etc/crontab</filename> (only <systemitem class="username">root</systemitem> is allowed to modify this file), contains the following lines: - </para> + The configuration file for cron jobs is <filename>/etc/crontab</filename>, which can be only modified by the <systemitem class="username">root</systemitem> user. The file contains the following: + </para> <programlisting>SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root @@ -170,180 +285,359 @@ HOME=/ # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | -# * * * * * user command to be executed</programlisting> +# * * * * * user-name command to be executed</programlisting> <para> - The first three lines contain the same variables as an <filename>anacrontab</filename> file, <computeroutput>SHELL</computeroutput>, <computeroutput>PATH</computeroutput> and <computeroutput>MAILTO</computeroutput>. For more information about these variables, refer to <xref linkend="s2-configuring-anacron-jobs"/>. The fourth line contains the <computeroutput>HOME</computeroutput> variable. The <computeroutput>HOME</computeroutput> variable can be used to set the home directory to use when executing commands or scripts. - </para> + The first three lines contain the same variable definitions as an <filename>anacrontab</filename> file: <varname>SHELL</varname>, <varname>PATH</varname>, and <varname>MAILTO</varname>. For more information about these variables, see <xref linkend="s2-configuring-anacron-jobs" />. + </para> <para> - The rest of the lines in the <filename>/etc/crontab</filename> file represent scheduled jobs and have the following format: - </para> - <programlisting>minute hour day month day of week user command</programlisting> + In addition, the file can define the <computeroutput>HOME</computeroutput> variable. The <varname>HOME</varname> variable defines the directory, which will be used as the home directory when executing commands or scripts run by the job. + </para> + <para> + The remaining lines in the <filename>/etc/crontab</filename> file represent scheduled jobs and have the following format: + </para> + <screen>minute hour day month day of week username command</screen> + <para> + The following define the time when the job is to be run: + </para> <itemizedlist> <listitem> - <para> - <computeroutput>minute</computeroutput> — any integer from 0 to 59</para> + <para><varname>minute</varname> — any integer from 0 to 59 + </para> </listitem> <listitem> - <para> - <computeroutput>hour</computeroutput> — any integer from 0 to 23</para> + <para><varname>hour</varname> — any integer from 0 to 23 + </para> </listitem> <listitem> - <para> - <computeroutput>day</computeroutput> — any integer from 1 to 31 (must be a valid day if a month is specified)</para> + <para><varname>day</varname> — any integer from 1 to 31 (must be a valid day if a month is specified) + </para> </listitem> <listitem> - <para> - <computeroutput>month</computeroutput> — any integer from 1 to 12 (or the short name of the month such as jan or feb)</para> + <para><varname>month</varname> — any integer from 1 to 12 (or the short name of the month such as jan or feb) + </para> </listitem> <listitem> - <para> - <computeroutput>day of week</computeroutput> — any integer from 0 to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)</para> + <para><varname>day of week</varname> — any integer from 0 to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon) + </para> </listitem> + </itemizedlist> + <para> + The following define other job properties: + </para> + <itemizedlist> <listitem> - <para> - <computeroutput>user</computeroutput> — specifies the user under which the jobs are run + <para><varname>username</varname> — specifies the user under which the jobs are run. </para> </listitem> <listitem> + <para><varname>command</varname> — the command to be executed. + </para> <para> - <computeroutput>command</computeroutput> — the command to execute (the command can either be a command such as <command>ls /proc >> /tmp/proc</command> or the command to execute a custom script)</para> + The command can be either a command such as <command>ls /proc /tmp/proc</command> or a command which executes a custom script. + </para> </listitem> </itemizedlist> - <para>For any of the above values, an asterisk (*) can be used to specify all valid values. For example, an asterisk for the month value means execute the command every month within the constraints of the other values.</para> - <para>A hyphen (-) between integers specifies a range of integers. For example, <userinput>1-4</userinput> means the integers 1, 2, 3, and 4.</para> - <para>A list of values separated by commas (,) specifies a list. For example, <userinput>3, 4, 6, 8</userinput> indicates those four specific integers.</para> - <para>The forward slash (/) can be used to specify step values. The value of an integer can be skipped within a range by following the range with <userinput>/<replaceable>integer</replaceable></userinput>. For example, <userinput>0-59/2</userinput> can be used to define every other minute in the minute field. Step values can also be used with an asterisk. For instance, the value <userinput>*/3</userinput> can be used in the month field to run the task every third month.</para> - <para>Any lines that begin with a hash sign (#) are comments and are not processed.</para> - <para>Users other than <systemitem class="username">root</systemitem> can configure cron tasks by using the <command>crontab</command> utility. All user-defined crontabs are stored in the <filename>/var/spool/cron/</filename> directory and are executed using the usernames of the users that created them. To create a crontab as a user, login as that user and type the command <command>crontab -e</command> to edit the user's crontab using the editor specified by the <computeroutput>VISUAL</computeroutput> or <computeroutput>EDITOR</computeroutput> environment variable. The file uses the same format as <filename>/etc/crontab</filename>. When the changes to the crontab are saved, the crontab is stored according to username and written to the file <filename>/var/spool/cron/<replaceable>username</replaceable> - </filename>. To list the contents of your own personal crontab file, use the <command>crontab -l</command> command. </para> - <note> - <title>Do not specify a user</title> - <para> - When using the <command>crontab</command> utility, there is no need to specify a user when defining a job. - </para> - </note> - <para>The <filename>/etc/cron.d/</filename> directory contains files that have the same syntax as the <filename>/etc/crontab</filename> file. Only <systemitem class="username">root</systemitem> is allowed to create and modify files in this directory.</para> + <para> + For any of the above values, an asterisk (*) can be used to specify all valid values. If you, for example, define the month value as an asterisk, the job will be executed every month within the constraints of the other values. + </para> + <para> + A hyphen (-) between integers specifies a range of integers. For example, <userinput>1-4</userinput> means the integers 1, 2, 3, and 4. + </para> + <para> + A list of values separated by commas (,) specifies a list. For example, <userinput>3,4,6,8</userinput> indicates exactly these four integers. + </para> + <para> + The forward slash (/) can be used to specify step values. The value of an integer will be skipped within a range following the range with <userinput>/<replaceable>integer</replaceable></userinput>. For example, the minute value defined as <userinput>0-59/2</userinput> denotes every other minute in the minute field. Step values can also be used with an asterisk. For instance, if the month value is defined as <userinput>*/3</userinput>, the task will run every third month. + </para> + <para> + Any lines that begin with a hash sign (#) are comments and are not processed. + </para> + <para> + Users other than <systemitem class="username">root</systemitem> can configure cron tasks with the <command>crontab</command> utility. The user-defined crontabs are stored in the <filename class="directory">/var/spool/cron/</filename> directory and executed as if run by the users that created them. + </para> + <para> + To create a crontab as a specific user, login as that user and type the command <command>crontab -e</command> to edit the user's crontab with the editor specified in the <computeroutput>VISUAL</computeroutput> or <computeroutput>EDITOR</computeroutput> environment variable. The file uses the same format as <filename>/etc/crontab</filename>. When the changes to the crontab are saved, the crontab is stored according to the user name and written to the file <filename>/var/spool/cron/<replaceable>username</replaceable></filename>. To list the contents of the current user's crontab file, use the <command>crontab -l</command> command. + </para> + <para> + The <filename class="directory">/etc/cron.d/</filename> directory contains files that have the same syntax as the <filename>/etc/crontab</filename> file. Only <systemitem class="username">root</systemitem> is allowed to create and modify files in this directory. + </para> <note> <title>Do not restart the daemon to apply the changes</title> - <para>The cron daemon checks the <filename>/etc/anacrontab</filename> file, the <filename>/etc/crontab</filename> file, the <filename>/etc/cron.d/</filename> directory, and the <filename>/var/spool/cron/</filename> directory every minute for any changes. If any changes are found, they are loaded into memory. Thus, the daemon does not need to be restarted if an anacrontab or a crontab file is changed.</para> + <para>The cron daemon checks the <filename>/etc/anacrontab</filename> file, the <filename>/etc/crontab</filename> file, the <filename class="directory">/etc/cron.d/</filename> directory, and the <filename>/var/spool/cron/</filename> directory every minute for changes and the detected changes are loaded into memory. It is therefore not necessary to restart the daemon after an anacrontab or a crontab file have been changed.</para> </note> </section> <section id="s2-autotasks-cron-access"> <title>Controlling Access to Cron</title> - <para>The <filename>/etc/cron.allow</filename> and <filename>/etc/cron.deny</filename> files are used to restrict access to cron. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The cron daemon (<command>crond</command>) does not have to be restarted if the access control files are modified. The access control files are checked each time a user tries to add or delete a cron job.</para> - <para>The <systemitem class="username">root</systemitem> user can always use cron, regardless of the usernames listed in the access control files.</para> - <para>If the file <filename>cron.allow</filename> exists, only users listed in it are allowed to use cron, and the <filename>cron.deny</filename> file is ignored.</para> - <para>If <filename>cron.allow</filename> does not exist, users listed in <filename>cron.deny</filename> are not allowed to use cron.</para> - <para>Access can also be controlled through Pluggable Authentication Modules (PAM). These settings are stored in <filename>/etc/security/access.conf</filename>. For example, adding the following line in this file forbids creating crontabs for all users except the <systemitem class="username">root</systemitem> user: + <para> + To restrict the access to Cron, you can use the <filename>/etc/cron.allow</filename> and <filename>/etc/cron.deny</filename> files. These access control files use the same format with one user name on each line. Mind that no whitespace characters are permitted in either file. + </para> + <para> + If the <filename>cron.allow</filename> file exists, only users listed in the file are allowed to use cron, and the <filename>cron.deny</filename> file is ignored. + </para> + <para> + If the <filename>cron.allow</filename> file does not exist, users listed in the <filename>cron.deny</filename> file are not allowed to use Cron. + </para> + <para> + The Cron daemon (<systemitem class="daemon">crond</systemitem>) does not have to be restarted if the access control files are modified. The access control files are checked each time a user tries to add or delete a cron job. + </para> + <para> + The <systemitem class="username">root</systemitem> user can always use cron, regardless of the user names listed in the access control files. + </para> + <para> + You can control the access also through Pluggable Authentication Modules (PAM). The settings are stored in the <filename>/etc/security/access.conf</filename> file. For example, after adding the following line to the file, no other user but the <systemitem class="username">root</systemitem> user can create crontabs: </para> <programlisting>-:ALL EXCEPT root :cron</programlisting> <para> - The forbidden jobs are logged in an appropriate log file or, when using “crontab -e”, returned to the standard output. For more information, refer to <filename>access.conf.5</filename> (i.e. <command>man 5 access.conf</command>). + The forbidden jobs are logged in an appropriate log file or, when using <command>crontab -e</command>, returned to the standard output. For more information, see the <filename>access.conf.5</filename> manual page. </para> </section> <section id="s2-black-white-listing-of-cron-jobs"> - <title>Black/White Listing of Cron Jobs</title> + <title>Black and White Listing of Cron Jobs</title> <para> - Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <command>run-parts</command> script on a cron folder, such as <filename>/etc/cron.daily</filename>, we can define which of the programs in this folder will not be executed by <command>run-parts</command>. - </para> - <para>To define a black list, create a <filename>jobs.deny</filename> file in the folder that <command>run-parts</command> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <filename>/etc/cron.daily/jobs.deny</filename> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <computeroutput>run-parts /etc/cron.daily</computeroutput>, is executed by a specific job.</para> - <para>To define a white list, create a <filename>jobs.allow</filename> file.</para> - <para> - The principles of <filename>jobs.deny</filename> and <filename>jobs.allow</filename> are the same as those of <filename>cron.deny</filename> and <filename>cron.allow</filename> described in section <xref linkend="s2-autotasks-cron-access"/>. - </para> + Black and white listing of jobs is used to define parts of a job that do not need to be executed. This is useful when calling the <application>run-parts</application> script on a Cron directory, such as <filename class="directory">/etc/cron.daily/</filename>: if the user adds programs located in the directory to the job black list, the <application>run-parts</application> script will not execute these programs. + </para> + <para> + To define a black list, create a <filename>jobs.deny</filename> file in the directory that <command>run-parts</command> scripts will be executing from. For example, if you need to omit a particular program from <filename>/etc/cron.daily/</filename>, create the <filename>/etc/cron.daily/jobs.deny</filename> file. In this file, specify the names of the programs to be omitted from execution (only programs located in the same directory can be enlisted). If a job runs a command which runs the programs from the <filename>/etc/cron.daily/</filename> directory, such as <command>run-parts /etc/cron.daily</command>, the programs defined in the <filename>jobs.deny</filename> file will not be executed. + </para> + <para> + To define a white list, create a <filename>jobs.allow</filename> file. + </para> + <para> + The principles of <filename>jobs.deny</filename> and <filename>jobs.allow</filename> are the same as those of <filename>cron.deny</filename> and <filename>cron.allow</filename> described in section <xref linkend="s2-autotasks-cron-access" />. + </para> </section> </section> <section id="s1-autotasks-at-batch"> <title>At and Batch</title> - <indexterm significance="normal"> + <indexterm> <primary> <command>at</command> </primary> </indexterm> - <indexterm significance="normal"> + <indexterm> <primary> <command>batch</command> </primary> </indexterm> - <para>While cron is used to schedule recurring tasks, the <command>at</command> command is used to schedule a one-time task at a specific time and the <command>batch</command> command is used to schedule a one-time task to be executed when the systems load average drops below 0.8.</para> - <para>To use <command>at</command> or <command>batch</command>, the <filename>at</filename> RPM package must be installed, and the <command>atd</command> service must be running. To determine if the package is installed, use the <command>rpm -q at</command> command. To determine if the service is running, use the following command:</para> - <screen><command>systemctl is-active atd.service</command></screen> + <para> + While Cron is used to schedule recurring tasks, the <application>At</application> utility is used to schedule a one-time task at a specific time and the <application>Batch</application> utility is used to schedule a one-time task to be executed when the system load average drops below 0.8.</para> + <section id="sect-At_and_Batch_Installation"> + <title>Installing At and Batch</title> + <para> + To determine if the <package>at</package> package is already installed on your system, issue the following command: + </para> + <synopsis><command>rpm -q at</command></synopsis> + <para> + The command returns the full name of the <package>at</package> package if already installed or notifies you that the package is not available. + </para> + <para> + To install the packages, use the <command>yum</command> command in the following form as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>yum install <replaceable>package</replaceable></command></synopsis> + <para> + For example, to install both At and Batch, type the following at a shell prompt: + </para> + <screen>~]# <command>yum install at</command></screen> + <para> + For more information on how to install new packages in &MAJOROS;, see <xref linkend="sec-Installing" />. + </para> + </section> + <section id="sect-Atd-Running"> + <title>Running the At Service</title> + <para> + The At and Batch jobs are both picked by the <systemitem class="daemon">atd</systemitem> service. This section provides information on how to start, stop, and restart the <systemitem class="service">atd</systemitem> service, and shows how to configure it to start automatically at boot time.  + </para> + <section id="sect-Atd-service"> + <title>Starting and Stopping the At Service</title> + <para> + To determine if the service is running, use the following command: + </para> + <synopsis><command>systemctl status atd.service</command></synopsis> + <para> + To run the <systemitem class="service">atd</systemitem> service in the current session, type the following at a shell prompt as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl start atd.service</command></synopsis> + <para> + To configure the service to start automatically at boot time, use the following command as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl enable atd.service</command></synopsis> + <note> + <para> + It is recommended that you configure your system to start the <systemitem class="service">atd</systemitem> service automatically at boot time. + </para> + </note> + </section> + <section id="sect-Atd_Stopping"> + <title>Stopping the At Service</title> + <para> + To stop the <systemitem class="service">atd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl stop atd.service</command></synopsis> + <para> + To prevent the service from starting automatically at boot time, use the following command as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl disable atd.service</command></synopsis> + </section> + <section id="sect-Atd_Restarting"> + <title>Restarting the At Service</title> + <para> + To restart the <systemitem class="service">atd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>: + </para> + <synopsis><command>systemctl restart atd.service</command></synopsis> + <para> + This command stops the service and starts it again in quick succession. + </para> + </section> + </section> <section id="s2-autotasks-at-configuring"> - <title>Configuring At Jobs</title> - <para>To schedule a one-time job at a specific time, type the command <command>at <replaceable>time</replaceable> - </command>, where <command><replaceable>time</replaceable> - </command> is the time to execute the command.</para> - <para>The argument <replaceable>time</replaceable> can be one of the following:</para> - <itemizedlist> - <listitem> - <para>HH:MM format — For example, 04:00 specifies 4:00 a.m. If the time is already past, it is executed at the specified time the next day.</para> - </listitem> - <listitem> - <para>midnight — Specifies 12:00 a.m.</para> - </listitem> - <listitem> - <para>noon — Specifies 12:00 p.m.</para> - </listitem> - <listitem> - <para>teatime — Specifies 4:00 p.m.</para> - </listitem> - <listitem> - <para>month-name day year format — For example, January 15 2002 specifies the 15th day of January in the year 2002. The year is optional.</para> - </listitem> - <listitem> - <para>MMDDYY, MM/DD/YY, or MM.DD.YY formats — For example, 011502 for the 15th day of January in the year 2002.</para> - </listitem> - <listitem> - <para>now + time — time is in minutes, hours, days, or weeks. For example, now + 5 days specifies that the command should be executed at the same time five days from now.</para> - </listitem> - </itemizedlist> - <para>The time must be specified first, followed by the optional date. For more information about the time format, read the <filename>/usr/share/doc/at/timespec</filename> text file.</para> - <para>After typing the <command>at</command> command with the time argument, the <prompt>at></prompt> prompt is displayed. Type the command to execute, press <keycap>Enter</keycap>, and press <keycombo><keycap>Ctrl</keycap> - <keycap>D</keycap> - </keycombo> . Multiple commands can be specified by typing each command followed by the <keycap>Enter</keycap> key. After typing all the commands, press <keycap>Enter</keycap> to go to a blank line and press <keycombo><keycap>Ctrl</keycap> - <keycap>D</keycap> - </keycombo> . Alternatively, a shell script can be entered at the prompt, pressing <keycap>Enter</keycap> after each line in the script, and pressing <keycombo><keycap>Ctrl</keycap> - <keycap>D</keycap> - </keycombo> on a blank line to exit. If a script is entered, the shell used is the shell set in the user's <envar>SHELL</envar> environment, the user's login shell, or <command>/bin/sh</command> (whichever is found first).</para> - <para>If the set of commands or script tries to display information to standard output, the output is emailed to the user.</para> - <para>Use the command <command>atq</command> to view pending jobs. See <xref linkend="s2-autotasks-at-batch-viewing"/> for more information.</para> - <para>Usage of the <command>at</command> command can be restricted. For more information, refer to <xref linkend="s2-autotasks-at-batch-controlling-access"/> for details.</para> + <title>Configuring an At Job</title> + <para>To schedule a one-time job for a specific time with the <application>At</application> utility, do the following:</para> + <procedure> + <step> + <para> + On the command line, type the command <command>at <replaceable>TIME</replaceable></command>, where <command><replaceable>TIME</replaceable></command> is the time when the command is to be executed. + </para> + <para>The <replaceable>TIME</replaceable> argument can be defined in any of the following formats:</para> + <itemizedlist> + <listitem> + <para><literal><replaceable>HH</replaceable>:<replaceable>MM</replaceable></literal> specifies the exact hour and minute; For example, <literal>04:00</literal> specifies 4:00 a.m. + </para> + </listitem> + <listitem> + <para><literal>midnight</literal> specifies 12:00 a.m. + </para> + </listitem> + <listitem> + <para><literal>noon</literal> specifies 12:00 p.m. + </para> + </listitem> + <listitem> + <para><literal>teatime</literal> specifies 4:00 p.m. + </para> + </listitem> + <listitem> + <para><literal><replaceable>MONTH</replaceable><replaceable>DAY</replaceable><replaceable>YEAR</replaceable></literal> format; For example, <literal>January 15 2012</literal> specifies the 15th day of January in the year 2012. The year value is optional. + </para> + </listitem> + <listitem> + <para><literal><replaceable>MMDDYY</replaceable></literal>, <literal><replaceable>MM</replaceable>/<replaceable>DD</replaceable>/<replaceable>YY</replaceable></literal>, or <literal><replaceable>MM</replaceable>.<replaceable>DD</replaceable>.<replaceable>YY</replaceable></literal> formats; For example, <literal>011512</literal> for the 15th day of January in the year 2012. + </para> + </listitem> + <listitem> + <para><literal>now + <replaceable>TIME</replaceable></literal> where <replaceable>TIME</replaceable> is defined as an integer and the value type: minutes, hours, days, or weeks. For example, <userinput>now + 5 days</userinput> specifies that the command will be executed at the same time five days from now.</para> + <para>The time must be specified first, followed by the optional date. For more information about the time format, see the <filename>/usr/share/doc/at-<replaceable><version></replaceable>/timespec</filename> text file.</para> + </listitem> + </itemizedlist> + <para> + If the specified time has past, the job is executed at the time the next day. + </para> + </step> + <step> + <para> + In the displayed <prompt>at></prompt> prompt, define the job commands: + </para> + <stepalternatives> + <step> + <para> + Type the command the job should execute and press <keycap>Enter</keycap>. Optionally, repeat the step to provide multiple commands. + </para> + </step> + <step> + <para> + Enter a shell script at the prompt and press <keycap>Enter</keycap> after each line in the script. + </para> + <para> + The job will use the shell set in the user's <envar>SHELL</envar> environment, the user's login shell, or <command>/bin/sh</command> (whichever is found first). + </para> + </step> + </stepalternatives> + </step> + <step> + <para> + Once finished, press <keycombo><keycap>Ctrl</keycap><keycap>D</keycap></keycombo> on an empty line to exit the prompt. + </para> + </step> + </procedure> + <para> + If the set of commands or the script tries to display information to standard output, the output is emailed to the user. + </para> + <para> + To view the list of pending jobs, use the <command>atq</command> command. See <xref linkend="s2-autotasks-at-batch-viewing" /> for more information. + </para> + <para> + You can also restrict the usage of the <command>at</command> command. For more information, see <xref linkend="s2-autotasks-at-batch-controlling-access" /> for details. + </para> </section> <section id="s2-autotasks-batch-configuring"> - <title>Configuring Batch Jobs</title> - <para>To execute a one-time task when the load average is below 0.8, use the <command>batch</command> command.</para> - <para>After typing the <command>batch</command> command, the <prompt>at></prompt> prompt is displayed. Type the command to execute, press <keycap>Enter</keycap>, and press <keycombo><keycap>Ctrl</keycap> - <keycap>D</keycap> - </keycombo> . Multiple commands can be specified by typing each command followed by the <keycap>Enter</keycap> key. After typing all the commands, press <keycap>Enter</keycap> to go to a blank line and press <keycombo><keycap>Ctrl</keycap> - <keycap>D</keycap> - </keycombo> . Alternatively, a shell script can be entered at the prompt, pressing <keycap>Enter</keycap> after each line in the script, and pressing <keycombo><keycap>Ctrl</keycap> - <keycap>D</keycap> - </keycombo> on a blank line to exit. If a script is entered, the shell used is the shell set in the user's <envar>SHELL</envar> environment, the user's login shell, or <command>/bin/sh</command> (whichever is found first). As soon as the load average is below 0.8, the set of commands or script is executed.</para> - <para>If the set of commands or script tries to display information to standard out, the output is emailed to the user.</para> - <para>Use the command <command>atq</command> to view pending jobs. See <xref linkend="s2-autotasks-at-batch-viewing"/> for more information.</para> - <para>Usage of the <command>batch</command> command can be restricted. For more information, refer to <xref linkend="s2-autotasks-at-batch-controlling-access"/> for details.</para> + <title>Configuring a Batch Job</title> + <para> + The <application>Batch</application> application executes the defined one-time tasks when the system load average decreases below 0.8. + </para> + <para> + To define a Batch job, do the following: + </para> + <procedure> + <step> + <para> + On the command line, type the command <command>batch</command>. + </para> + </step> + <step> + <para> + In the displayed <prompt>at></prompt> prompt, define the job commands: + </para> + <stepalternatives> + <step> + <para> + Type the command the job should execute and press <keycap>Enter</keycap>. Optionally, repeat the step to provide multiple commands. + </para> + </step> + <step> + <para> + Enter a shell script at the prompt and press <keycap>Enter</keycap> after each line in the script. + </para> + <para> + If a script is entered, the job uses the shell set in the user's <envar>SHELL</envar> environment, the user's login shell, or <command>/bin/sh</command> (whichever is found first). + </para> + </step> + </stepalternatives> + </step> + <step> + <para> + Once finished, press <keycombo><keycap>Ctrl</keycap><keycap>D</keycap></keycombo> on an empty line to exit the prompt. + </para> + </step> + </procedure> + <para> + If the set of commands or the script tries to display information to standard output, the output is emailed to the user. + </para> + <para> + To view the list of pending jobs, use the <command>atq</command> command. See <xref linkend="s2-autotasks-at-batch-viewing" /> for more information. + </para> + <para> + You can also restrict the usage of the <command>batch</command> command. For more information, see <xref linkend="s2-autotasks-at-batch-controlling-access" /> for details. + </para> </section> <section id="s2-autotasks-at-batch-viewing"> <title>Viewing Pending Jobs</title> - <para>To view pending <command>at</command> and <command>batch</command> jobs, use the <command>atq</command> command. The <command>atq</command> command displays a list of pending jobs, with each job on a line. Each line follows the job number, date, hour, job class, and username format. Users can only view their own jobs. If the <systemitem class="username">root</systemitem> user executes the <command>atq</command> command, all jobs for all users are displayed.</para> + <para>To view the pending <command>At</command> and <command>Batch</command> jobs, run the <command>atq</command> command. The <command>atq</command> command displays a list of pending jobs, with each job on a separate line. Each line follows the job number, date, hour, job class, and user name format. Users can only view their own jobs. If the <systemitem class="username">root</systemitem> user executes the <command>atq</command> command, all jobs for all users are displayed.</para> </section> <section id="s2-autotasks-commandline-options"> <title>Additional Command Line Options</title> - <para>Additional command line options for <command>at</command> and <command>batch</command> include:</para> + <para>Additional command line options for <command>at</command> and <command>batch</command> include the following:</para> <table id="tb-at-command-line-options"> - <title> - <command>at</command> and <command>batch</command> Command Line Options</title> + <title><command>at</command> and <command>batch</command> Command Line Options</title> <tgroup cols="2"> <colspec colname="option" colnum="1" colwidth="20*"/> <colspec colname="description" colnum="2" colwidth="50*"/> <thead> <row> <entry> - Option - </entry> + Option + </entry> <entry> - Description - </entry> + Description + </entry> </row> </thead> <tbody> @@ -352,24 +646,24 @@ HOME=/ <option>-f</option> </entry> <entry> - Read the commands or shell script from a file instead of specifying them at the prompt. - </entry> + Read the commands or shell script from a file instead of specifying them at the prompt. + </entry> </row> <row> <entry> <option>-m</option> </entry> <entry> - Send email to the user when the job has been completed. - </entry> + Send email to the user when the job has been completed. + </entry> </row> <row> <entry> <option>-v</option> </entry> <entry> - Display the time that the job is executed. - </entry> + Display the time that the job is executed. + </entry> </row> </tbody> </tgroup> @@ -377,69 +671,76 @@ HOME=/ </section> <section id="s2-autotasks-at-batch-controlling-access"> <title>Controlling Access to At and Batch</title> - <para>The <filename>/etc/at.allow</filename> and <filename>/etc/at.deny</filename> files can be used to restrict access to the <command>at</command> and <command>batch</command> commands. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The <command>at</command> daemon (<command>atd</command>) does not have to be restarted if the access control files are modified. The access control files are read each time a user tries to execute the <command>at</command> or <command>batch</command> commands.</para> - <para>The <systemitem class="username">root</systemitem> user can always execute <command>at</command> and <command>batch</command> commands, regardless of the access control files.</para> - <para>If the file <filename>at.allow</filename> exists, only users listed in it are allowed to use <command>at</command> or <command>batch</command>, and the <filename>at.deny</filename> file is ignored.</para> - <para>If <filename>at.allow</filename> does not exist, users listed in <filename>at.deny</filename> are not allowed to use <command>at</command> or <command>batch</command>.</para> - </section> - <section id="s2-autotasks-at-batch-service"> - <title>Starting and Stopping the Service</title> - <para>To start the <command>at</command> service, use the following command as <systemitem class="username">root</systemitem>:</para> - <screen><command>systemctl start atd.service</command></screen> - <para>To stop the service, as <systemitem class="username">root</systemitem>, type the following at a shell prompt:</para> - <screen><command>systemctl stop atd.service</command></screen> - <para>It is recommended that you start the service at boot time. To do so, run the following command as <systemitem class="username">root</systemitem>:</para> - <screen><command>systemctl enable atd.service</command></screen> <para> - See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;. + You can restrict the access to the <command>at</command> and <command>batch</command> commands using the <filename>/etc/at.allow</filename> and <filename>/etc/at.deny</filename> files. These access control files use the same format defining one user name on each line. Mind that no whitespace are permitted in either file. + </para> + <para> + If the file <filename>at.allow</filename> exists, only users listed in the file are allowed to use <command>at</command> or <command>batch</command>, and the <filename>at.deny</filename> file is ignored. + </para> + <para> + If <filename>at.allow</filename> does not exist, users listed in <filename>at.deny</filename> are not allowed to use <command>at</command> or <command>batch</command>. + </para> + <para> + The <command>at</command> daemon (<command>atd</command>) does not have to be restarted if the access control files are modified. The access control files are read each time a user tries to execute the <command>at</command> or <command>batch</command> commands. + </para> + <para> + The <systemitem class="username">root</systemitem> user can always execute <command>at</command> and <command>batch</command> commands, regardless of the content of the access control files. </para> </section> </section> <section id="s1-autotasks-additional-resources"> <title>Additional Resources</title> - <indexterm significance="normal"> + <indexterm> <primary>cron</primary> <secondary>additional resources</secondary> </indexterm> - <indexterm significance="normal"> + <indexterm> <primary>at</primary> <secondary>additional resources</secondary> </indexterm> - <indexterm significance="normal"> + <indexterm> <primary>batch</primary> <secondary>additional resources</secondary> </indexterm> - <para>To learn more about configuring automated tasks, refer to the following resources.</para> - <section id="s2-autotasks-installed-docs"> - <title>Installed Documentation</title> - <itemizedlist> - <listitem> - <para> - <filename>cron</filename> man page — contains an overview of cron.</para> - </listitem> - <listitem> - <para> - <filename>crontab</filename> man pages in sections 1 and 5 — The man page in section 1 contains an overview of the <filename>crontab</filename> file. The man page in section 5 contains the format for the file and some example entries.</para> - </listitem> - <listitem> - <para> - <filename>anacron</filename> man page — contains an overview of anacron. + <para>To learn more about configuring automated tasks, see the following installed documentation:</para> + <itemizedlist> + <listitem> + <para><filename>cron(8)</filename> man page contains an overview of cron.</para> + </listitem> + <listitem> + <para><filename>crontab</filename> man pages in sections 1 and 5:</para> + <itemizedlist> + <listitem> + <para> + The manual page in section 1 contains an overview of the <filename>crontab</filename> file. + </para> + </listitem> + <listitem> + <para> + The man page in section 5 contains the format for the file and some example entries. + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para><filename>anacron(8)</filename> manual page contains an overview of anacron. </para> - </listitem> - <listitem> - <para> - <filename>anacrontab</filename> man page — contains an overview of the <filename>anacrontab</filename> file. + </listitem> + <listitem> + <para><filename>anacrontab(5)</filename> manual page contains an overview of the <filename>anacrontab</filename> file. </para> - </listitem> - <listitem> - <para> - <filename>/usr/share/doc/at/timespec</filename> contains more detailed information about the times that can be specified for cron jobs.</para> - </listitem> - <listitem> - <para> - <filename>at</filename> man page — description of <command>at</command> and <command>batch</command> and their command line options.</para> - </listitem> - </itemizedlist> - </section> + </listitem> + <listitem> + <para><filename>run-parts(4)</filename> manual page contains an overview of the <command>run-parts</command> script. + </para> + </listitem> + + <listitem> + <para><filename>/usr/share/doc/at/timespec</filename> contains detailed information about the time values that can be used in cron job definitions.</para> + </listitem> + <listitem> + <para><filename>at</filename> manual page contains descriptions of <command>at</command> and <command>batch</command> and their command line options.</para> + </listitem> + </itemizedlist> </section> </chapter>

9 years, 6 months

1
0
0 / 0

[system-administrators-guide] trivial markup improvements

by stephenw

commit b3a9625be4acdddce5d041eaa9f2fa83a6ae8511 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Tue Dec 9 23:07:30 2014 +0100 trivial markup improvements while review against upstream version en-US/Samba.xml | 234 ++++++++++++++++++------------------------------------- 1 files changed, 75 insertions(+), 159 deletions(-) --- diff --git a/en-US/Samba.xml b/en-US/Samba.xml index d9ad9f7..f3e41df 100644 --- a/en-US/Samba.xml +++ b/en-US/Samba.xml @@ -3,13 +3,11 @@ ]> <section id="s1-Samba"> <title>Samba</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Reference</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <see>Samba</see> </indexterm> @@ -25,8 +23,7 @@ <section id="samba-rgs-overview"> <title>Introduction to Samba</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Introduction</secondary> </indexterm> @@ -34,8 +31,7 @@ <section id="s3-samba-abilities"> <title>Samba Features</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Abilities</secondary> </indexterm> @@ -82,8 +78,7 @@ <section id="s2-samba-daemons"> <title>Samba Daemons and Related Services</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>daemon</secondary> </indexterm> @@ -91,8 +86,7 @@ <section id="s3-samba-services"> <title>Samba Daemons</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>daemon</secondary> <tertiary>overview</tertiary> @@ -101,8 +95,7 @@ <bridgehead id="s4-samba-daemon-smbd"> <command>smbd</command> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>daemon</secondary> <tertiary>smbd</tertiary> @@ -112,8 +105,7 @@ <bridgehead id="s4-samba-daemon-nmbd"> <command>nmbd</command> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>daemon</secondary> <tertiary>nmbd</tertiary> @@ -123,8 +115,7 @@ <bridgehead id="s4-samba-daemon-winbindd"> <command>winbindd</command> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>daemon</secondary> <tertiary>winbindd</tertiary> @@ -140,8 +131,7 @@ <section id="s2-samba-connect-share"> <title>Connecting to a Samba Share</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>share</secondary> <tertiary>connecting to with Nautilus</tertiary> @@ -165,57 +155,47 @@ <section id="s3-samba-connect-share-cmdline"> <title>Command Line</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>share</secondary> <tertiary>connecting to via the command line</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary> <command>findsmb</command> </secondary> </indexterm> - <indexterm - significance="normal"> - <primary> - <command>findsmb</command> - </primary> + <indexterm> + <primary><command>findsmb</command></primary> </indexterm> <para>To query the network for Samba servers, use the <command>findsmb</command> command. For each server found, it displays its <systemitem class="protocol">IP</systemitem> address, NetBIOS name, workgroup name, operating system, and <systemitem class="protocol">SMB</systemitem> server version.</para> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> - <secondary> - <command>smbclient</command> - </secondary> + <secondary><command>smbclient</command></secondary> </indexterm> - <indexterm - significance="normal"> - <primary> - <command>smbclient</command> - </primary> + <indexterm> + <primary><command>smbclient</command></primary> </indexterm> <para>To connect to a Samba share from a shell prompt, type the following command:</para> <screen>~]$ <command>smbclient //<replaceable>hostname</replaceable>/<replaceable>sharename</replaceable> -U <replaceable>username</replaceable></command></screen> <para>Replace <replaceable>hostname</replaceable> with the hostname or <systemitem class="protocol">IP</systemitem> address of the Samba server you want to connect to, <replaceable>sharename</replaceable> with the name of the shared directory you want to browse, and <replaceable>username</replaceable> with the Samba username for the system. Enter the correct password or press <keycap>Enter</keycap> if no password is required for the user.</para> - <para>If you see the <prompt>smb:\></prompt> prompt, you have successfully logged in. Once you are logged in, type <userinput>help</userinput> for a list of commands. If you wish to browse the contents of your home directory, replace <replaceable>sharename</replaceable> with your username. If the <command>-U</command> switch is not used, the username of the current user is passed to the Samba server.</para> + <para>If you see the <prompt>smb:\></prompt> prompt, you have successfully logged in. Once you are logged in, type <userinput>help</userinput> for a list of commands. If you want to browse the contents of your home directory, replace <replaceable>sharename</replaceable> with your username. If the <command>-U</command> switch is not used, the username of the current user is passed to the Samba server.</para> <para>To exit <command>smbclient</command>, type <userinput>exit</userinput> at the <prompt>smb:\></prompt> prompt.</para> </section> <section id="s2-samba-mounting"> <title>Mounting the Share</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>share</secondary> <tertiary>mounting</tertiary> </indexterm> <para>Sometimes it is useful to mount a Samba share to a directory so that the files in the directory can be treated as if they are part of the local file system.</para> <para>To mount a Samba share to a directory, create a directory to mount it to (if it does not already exist), and execute the following command as <systemitem class="username">root</systemitem>:</para> - <screen><command>mount -t cifs //<replaceable>servername</replaceable>/<replaceable>sharename</replaceable> <replaceable>/mnt/point/</replaceable> -o username=<replaceable>username</replaceable>,password=<replaceable>password</replaceable></command></screen> + <screen> +<command>~]# mount -t cifs //<replaceable>servername</replaceable>/<replaceable>sharename</replaceable> + <replaceable>/mnt/point/</replaceable> -o username=<replaceable>username</replaceable>,password=<replaceable>password</replaceable></command></screen> <para>This command mounts <replaceable>sharename</replaceable> from <replaceable>servername</replaceable> in the local directory <replaceable>/mnt/point/</replaceable>. </para> @@ -246,13 +226,11 @@ <section id="s2-samba-configuring"> <title>Configuring a Samba Server</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>configuration</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>configuration</secondary> <tertiary>default</tertiary> @@ -261,8 +239,7 @@ <section id="s3-samba-configuring-gui"> <title>Graphical Configuration</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>graphical configuration</secondary> </indexterm> @@ -273,8 +250,7 @@ <section id="s3-samba-configuring-cmdline"> <title>Command Line Configuration</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>configuration</secondary> </indexterm> @@ -300,39 +276,32 @@ create mask = 0765</programlisting> id="s3-samba-encrypted-passwords"> <title>Encrypted Passwords</title> <para>Encrypted passwords are enabled by default because it is more secure to use them. To create a user with an encrypted password, use the command <command>smbpasswd -a <replaceable>username</replaceable></command>.</para> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>with Windows NT 4.0, 2000, ME, and XP</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Windows NT 4.0</primary> <secondary>connecting to shares using Samba</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Windows 98</primary> <secondary>connecting to shares using Samba</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Windows 2000</primary> <secondary>connecting to shares using Samba</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Windows ME</primary> <secondary>connecting to shares using Samba</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Windows XP</primary> <secondary>connecting to shares using Samba</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>encrypted passwords</secondary> </indexterm> @@ -341,32 +310,27 @@ create mask = 0765</programlisting> <section id="s2-samba-startstop"> <title>Starting and Stopping Samba</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>service</secondary> <tertiary>starting</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>service</secondary> <tertiary>stopping</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>service</secondary> <tertiary>restarting</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>service</secondary> <tertiary>conditional restarting</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>service</secondary> <tertiary>reloading</tertiary> @@ -390,7 +354,7 @@ create mask = 0765</programlisting> <para>To conditionally restart the server, type the following command, as <systemitem class="username">root</systemitem>:</para> <screen>~]# <command>systemctl condrestart smb.service</command></screen> <para>A manual reload of the <filename>/etc/samba/smb.conf</filename> file can be useful in case of a failed automatic reload by the <command>smb</command> service. To ensure that the Samba server configuration file is reloaded without restarting the service, type the following command, as <systemitem class="username">root</systemitem>:</para> - <screen><command>systemctl reload smb.service</command></screen> + <screen>~]# <command>systemctl reload smb.service</command></screen> <para>By default, the <command>smb</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure Samba to start at boot time, type the following at a shell prompt as <systemitem class="username">root</systemitem>:</para> <screen>~]# <command>systemctl enable smb.service</command></screen> <para>See <xref linkend="ch-Services_and_Daemons" /> for more information regarding this tool.</para> @@ -1104,13 +1068,11 @@ security = share <section id="s2-samba-network-browsing"> <title>Samba Network Browsing</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Network Browsing</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Browsing</secondary> </indexterm> @@ -1121,8 +1083,7 @@ security = share <section id="s3-samba-domain-browsing"> <title>Domain Browsing</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Network Browsing</secondary> <tertiary>Domain Browsing</tertiary> @@ -1133,13 +1094,11 @@ security = share <section id="s3-samba-wins"> <title>WINS (Windows Internet Name Server)</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>WINS</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Network Browsing</secondary> <tertiary>WINS</tertiary> @@ -1200,8 +1159,7 @@ printer admin = ed, john</programlisting> <section id="s2-samba-programs"> <title>Samba Distribution Programs</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> </indexterm> @@ -1305,16 +1263,14 @@ lisa Sales</screen> <bridgehead id="s3-samba-programs-nmblookup"> <filename>nmblookup</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>nmblookup</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>nmblookup</command> program</primary> </indexterm> @@ -1328,16 +1284,14 @@ querying trek on 10.1.59.255 <bridgehead id="s3-samba-programs-pdbedit"> <filename>pdbedit</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>pdbedit</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>pdbedit</command> program</primary> </indexterm> @@ -1398,16 +1352,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-rpcclient"> <filename>rpcclient</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>rpcclient</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>rpcclient</command> program</primary> </indexterm> @@ -1416,16 +1368,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbcacls"> <filename>smbcacls</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbcacls</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbcacls</command> program</primary> </indexterm> @@ -1434,16 +1384,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbclient"> <filename>smbclient</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbclient</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbclient</command> program</primary> </indexterm> @@ -1452,16 +1400,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbcontrol"> <filename>smbcontrol</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbcontrol</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbcontrol</command> program</primary> </indexterm> @@ -1471,16 +1417,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbpasswd"> <filename>smbpasswd</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbpasswd</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbpasswd</command> program</primary> </indexterm> @@ -1489,16 +1433,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbspool"> <filename>smbspool</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbspool</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbspool</command> program</primary> </indexterm> @@ -1507,16 +1449,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbstatus"> <filename>smbstatus</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbstatus</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbstatus</command> program</primary> </indexterm> @@ -1525,16 +1465,14 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-smbtar"> <filename>smbtar</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>smbtar</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>smbtar</command> program</primary> </indexterm> @@ -1543,21 +1481,19 @@ andriusb:505: lisa:504: kristin:506:</screen> <bridgehead id="s3-samba-programs-testparm"> <filename>testparm</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>testparm</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>testparm</command> program</primary> </indexterm> <screen><command>testparm <replaceable>options filename hostname IP_address</replaceable></command></screen> - <para>The <command>testparm</command> program checks the syntax of the <filename>/etc/samba/smb.conf</filename> file. If your <filename>smb.conf</filename> file is in the default location (<filename>/etc/samba/smb.conf</filename>) you do not need to specify the location. Specifying the host name and <systemitem class="protocol">IP</systemitem> address to the <command>testparm</command> program verifies that the <filename>hosts.allow</filename> and <filename>host.deny</filename> files are configured correctly. The <command>testparm</command> program also displays a summary of your <filename>/etc/samba/smb.conf</filename> file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read.</para> + <para>The <command>testparm</command> program checks the syntax of the <filename>/etc/samba/smb.conf</filename> file. If your <filename>smb.conf</filename> file is in the default location (<filename>/etc/samba/smb.conf</filename>) you do not need to specify the location. Specifying the host name and <systemitem class="protocol">IP</systemitem> address to the <command>testparm</command> program verifies that the <filename>hosts.allow</filename> and <filename>host.deny</filename> files are configured correctly. The <command>testparm</command> program also displays a summary of your <filename>smb.conf</filename> file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read.</para> <para>For example:</para> <screen>~]$ <command>testparm</command> Load smb config files from /etc/samba/smb.conf @@ -1598,35 +1534,18 @@ Press enter to see a dump of your service definitions force group = users read only = No guest only = Yes</screen> -  + <bridgehead id="s3-samba-programs-wbinfo"> <filename>wbinfo</filename> </bridgehead> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Programs</secondary> <tertiary> <command>wbinfo</command> </tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary> <command>wbinfo</command> program</primary> </indexterm> @@ -1636,8 +1555,7 @@ Press enter to see a dump of your service definitions <section id="s2-samba-resources"> <title>Additional Resources</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Additional Resources</secondary> </indexterm> @@ -1645,8 +1563,7 @@ Press enter to see a dump of your service definitions <section id="s3-samba-resources-installed"> <title>Installed Documentation</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Additional Resources</secondary> <tertiary>installed documentation</tertiary> @@ -1716,8 +1633,7 @@ Press enter to see a dump of your service definitions <section id="s3-samba-resources-community"> <title>Useful Websites</title> - <indexterm - significance="normal"> + <indexterm> <primary>Samba</primary> <secondary>Additional Resources</secondary> <tertiary>useful websites</tertiary>

9 years, 6 months

1
0
0 / 0

[system-administrators-guide] markup, word order

by stephenw

commit e76809bc0e52d5cc12f5b924fa17b9d56d9bed6e Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Tue Dec 9 22:31:15 2014 +0100 markup, word order en-US/The_Apache_HTTP_Server.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml index f77adec..5d24d06 100644 --- a/en-US/The_Apache_HTTP_Server.xml +++ b/en-US/The_Apache_HTTP_Server.xml @@ -4044,7 +4044,7 @@ SSLCertificateKeyFile /etc/pki/tls/private/<replaceable>hostname</replaceable>.k <screen>~]# <command>rm /etc/pki/tls/private/<replaceable>hostname</replaceable>.key</command></screen> </note> <para> - To run the utility, use the <command>genkey</command> command followed by the appropriate host name (for example, <systemitem class="domainname">penguin.example.com</systemitem>): + To run the utility enter the <command>genkey</command> command as <systemitem class="username">root</systemitem>, followed by the appropriate host name (for example, <systemitem class="domainname">penguin.example.com</systemitem>): </para> <screen>~]# <command>genkey</command> <replaceable>hostname</replaceable></screen> <para>

9 years, 6 months

1
0
0 / 0

← Newer
1
...
5
6
7
8
9
10
11
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits December 2014