[multiboot-guide] master: a little reorganization, and some explanitory prose around what a bootloader does. (a17d50e)
by Pete Travis
Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git
On branch : master
>---------------------------------------------------------------
commit a17d50ed0ad0ae3c9ae4d7174bf9d1dff6b8ec3d
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sat Nov 30 00:38:47 2013 -0700
a little reorganization, and some explanitory prose around what a bootloader does.
>---------------------------------------------------------------
en-US/BOOT-BIOS_or_UEFI.xml | 68 +++++++++++++++++++++++++++
en-US/BOOT-general.xml | 32 +++++++++++++
en-US/Fedora_Multiboot_Guide.xml | 4 +-
en-US/{UEFI-general.xml => GRUB-basics.xml} | 4 +-
en-US/GRUB-reinstalling.xml | 5 ++-
en-US/GRUB.xml | 4 +-
en-US/Introduction.xml | 2 +-
7 files changed, 111 insertions(+), 8 deletions(-)
diff --git a/en-US/BOOT-BIOS_or_UEFI.xml b/en-US/BOOT-BIOS_or_UEFI.xml
new file mode 100644
index 0000000..c9b6649
--- /dev/null
+++ b/en-US/BOOT-BIOS_or_UEFI.xml
@@ -0,0 +1,68 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Multiboot_Guide.ent">
+%BOOK_ENTITIES;
+
+]>
+<section id="BOOT-BIOS_or_UEFI">
+ <title>Is your system UEFI or BIOS?</title>
+ <para>
+ Because commands and file locations differ between BIOS and UEFI systems, it is important to identify which you have before attempting advanced boot configuration.
+ </para>
+ <itemizedlist>
+ <title>Identifying a BIOS system</title>
+ <listitem>
+ <para>
+ Older computers are more likely to use BIOS. UEFI systems did not become commonplace until after 2010.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 32 bit systems are almost always BIOS.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Your computer originally shipped with Windows Vista or XP.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The computer's manual and the system setup menu do not mention UEFI, EFI, or SecureBoot.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>The term <literal>BIOS</literal> is still used with UEFI systems</title>
+ <para>
+ Because BIOS systems have been around for so long, the term <literal>BIOS</literal> is often used to describe UEFI systems as well. Manufacturers might list system firmware updates as <literal>BIOS updates</literal> or provide directions to <literal>enter the BIOS setup menu</literal>. The word has come to represent the pre-OS menu on your computer as much as the actual software, but it doesn't mean that your system is not UEFI capable.
+ </para>
+ </note>
+ <itemizedlist>
+ <title>Identifying a UEFI system</title>
+ <listitem>
+ <para>
+ Newer systems are more likely to use UEFI. If you bought your computer new in 2013 or after, it probably has UEFI.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Your computer shipped with Windows 8. The terms of service for Windows 8 <emphasis>require</emphasis> SecureBoot, a UEFI feature.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Your system setup menu has a graphical interface or mouse support. UEFI menus can be more elaborate.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The system's boot menu gives you the option of booting via UEFI or not, with entries like these:
+ <screen>
+ UEFI: Generic USB Stick
+ Generic USB Stick
+ </screen>
+ </para>
+ </listitem>
+ </itemizedlist>
+</section>
diff --git a/en-US/BOOT-general.xml b/en-US/BOOT-general.xml
new file mode 100644
index 0000000..1c4d562
--- /dev/null
+++ b/en-US/BOOT-general.xml
@@ -0,0 +1,32 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Multiboot_Guide.ent">
+%BOOK_ENTITIES;
+
+]>
+<section id="BOOT-basics">
+ <title>Bootloader Basics</title>
+ <para>
+ To boot a modern operating system, a computer must identify the kernel, storage, and various options at the time of booting. Software called a bootloader keeps track of these parameters, manages settings for different operating systems, and loads the kernel.
+ </para>
+ <para>
+ Historically, bootloaders have been installed into the first part of a drive, known as the Master Boot Record (MBR) or Boot Sector. The computer's firmware, or BIOS, would check the boot sector for bootable code on startup, and load whatever it found. As bootloaders became more complex, and therefore required more space, the MBR came to contain only a pointer to the second stage of the bootloader.
+ </para>
+ <para>
+ The second stage of the bootloader performs the actual work. Because the BIOS does not know how to open and read from filesystems, the bootloader finds the operating system, presents a menu, interacts with the user as required, and launches the OS. It was installed in the part of the drive between the MBR and the beginning of the first filesystem, known as the MBR Gap. Less featureful bootloaders could also be installed in the gap between the start of the partition and the beginning of the partition's filesystem, but because this can damage the filesystem if the gap is too small the practice is no longer supported.
+ </para>
+ <para>
+ BIOS is short for Basic Input Output System, and the software is indeed very simple. BIOS systems had a number of technical limitations, such as being unable to boot from disks larger than 2 TB and extremely limited interfaces. GUID Partition Table (GPT) partitioning schemes also came with larger drives, overcoming the MBR partitioning scheme's 4 partition limit. To overcome these issues and add new features, a newer firmware implementation was developed, called the Unified Extensible Firmware Interface.
+ </para>
+ <para>
+ Instead of reading the bootloader from the drive, UEFI systems store some boot information right on the system firmware. Larger bootloaders and small applications such as memory testing utilites are stored on the UEFI system partition. This partition is always a FAT filesystem,has a standardized partition identifier, and is mounted at <filename>/boot/efi</filename>. Each operating system places files required for booting in a dedicated directory of this partition, and the boot entry in the firmware points to these files. UEFI systems will usually also support BIOS style booting for compatibility reasons.
+ </para>
+ <para>
+ On Linux systems, the data used by the bootloader is traditionally contained in a <systemitem>boot partition</systemitem>, mounted at and known as <filename>/boot</filename>. The boot partition contains the kernel, a read only filesystem that holds tools used by the kernel during bootup, called an <systemitem>initramfs</systemitem>, and files for the menus and for the bootloader itself. These files were traditionally placed on a different partition because the bootloader did not support complex storage arrangements, and could not read the kernel and initramfs from them. Because a simple, separate boot also allows for easier disaster recovery, the practice has continued to this day.
+ </para>
+
+ <para>
+ Fedora supports both UEFI and BIOS systems, using the GRUB bootloader, which is short for <literal>GNU GRand Unified Bootloader</literal>. GRUB provides a boot menu and support for many filesystems, as well as software for scanning the system for available operating systems and adding them to the menu.
+ </para>
+
+</section>
diff --git a/en-US/Fedora_Multiboot_Guide.xml b/en-US/Fedora_Multiboot_Guide.xml
index 3df1eea..c8ebc13 100644
--- a/en-US/Fedora_Multiboot_Guide.xml
+++ b/en-US/Fedora_Multiboot_Guide.xml
@@ -6,7 +6,9 @@
<article>
<xi:include href="Article_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Free_Space.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="BOOT-general.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="BOOT-BIOS_or_UEFI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Free_Space.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="GRUB.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="BIOS.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="UEFI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/en-US/UEFI-general.xml b/en-US/GRUB-basics.xml
similarity index 82%
copy from en-US/UEFI-general.xml
copy to en-US/GRUB-basics.xml
index 9d7058f..4dd51c3 100644
--- a/en-US/UEFI-general.xml
+++ b/en-US/GRUB-basics.xml
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
-<section id="UEFI-general">
- <title>UEFI Basics</title>
+<section id="GRUB-basics">
+ <title>GRUB Basics</title>
<para />
</section>
diff --git a/en-US/GRUB-reinstalling.xml b/en-US/GRUB-reinstalling.xml
index 382b48e..d5ab1b8 100644
--- a/en-US/GRUB-reinstalling.xml
+++ b/en-US/GRUB-reinstalling.xml
@@ -20,6 +20,7 @@
You have chosen not to use <application>anaconda</application> to install grub.
</member>
</simplelist>
+ </para>
<section id="GRUB-reinstalling-mkconfig">
<title>Refreshing GRUB configuration</title>
<para>
@@ -35,7 +36,9 @@
Refresh GRUB configuration on UEFI systems:
<screen>
<command>
-
+ grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
</command>
</screen>
</para>
+ </section>
+ </section>
diff --git a/en-US/GRUB.xml b/en-US/GRUB.xml
index 63c9c0f..e43d7d8 100644
--- a/en-US/GRUB.xml
+++ b/en-US/GRUB.xml
@@ -8,9 +8,7 @@
<title>The GRUB Bootloader</title>
<para />
- <!-- GRUB Basics -->
- <xi:include href="GRUB-general.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
+ <xi:include href="GRUB-basics.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- Reinstalling GRUB -->
<xi:include href="GRUB-reinstalling.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- temporary and persistent menu entry changes -->
diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml
index a4d061c..d6489a4 100644
--- a/en-US/Introduction.xml
+++ b/en-US/Introduction.xml
@@ -19,7 +19,7 @@
Changing Fedora's boot options can be helpful, especially when troubleshooting. <xref linkend="GRUB-customizing" /> explains how to change these options once or permanently.
</para>
<para>
- The system's firmware allows basic configuration, performs initial startup, initializes hardware, and brings up the bootloader. Until recently, this firmware was referred to as the <firstterm>BIOS</firstterm>, or <literal>Basic Input Output System</literal>, which is described in <xref linkend="BIOS-general" />. Newer systems, such as those sold with Windows 8, use a newer type called <firstterm>UEFI</firstterm> or <literal>Universal Extensible Firmware Interface</literal>, which is described in <xref linkend="UEFI-general" />.
+ The system's firmware allows basic configuration, performs initial startup, initializes hardware, and brings up the bootloader. Until recently, this firmware was referred to as the <firstterm>BIOS</firstterm>, or <literal>Basic Input Output System</literal>, which is described in <xref linkend="BOOT-basics" />. Newer systems, such as those sold with Windows 8, use a newer type called <firstterm>UEFI</firstterm> or <literal>Universal Extensible Firmware Interface</literal>, which is described in <xref linkend="BOOT-basics" />
</para>
<para>
In most cases, the Fedora installer will recognize other operating systems on your computer and create boot menu entries for them. If an operating system such as Windows is installed <emphasis>after</emphasis> Fedora, GRUB may be overwritten and require reinstallation. Some circumstances, such as missing menu entries, require refreshing of the menu entries. These tasks are explained in <xref linkend="BIOS" /> or <xref linkend="UEFI" />
9 years, 10 months
[release-notes] SDDM has been held back, so the content is commented out now
by Pete Travis
commit fd8a42626f8dfa1cd77da491e5157cee302e44a1
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Fri Nov 29 17:50:12 2013 -0700
SDDM has been held back, so the content is commented out now
en-US/Desktop.xml | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Desktop.xml b/en-US/Desktop.xml
index 902ce00..69b108e 100644
--- a/en-US/Desktop.xml
+++ b/en-US/Desktop.xml
@@ -276,6 +276,7 @@
</note>
</para>
</section>
+ <!--
<section id="desktop-kde-sddm">
<title>SDDM as Display Manager</title>
<para>
@@ -285,9 +286,10 @@
Some features may initially be missing from <application>SDDM</application>, such as VNC or multiseat support. However, the <application>SDDM</application> development community is very active and regular additions to functionality are expected.
</para>
<para>
- <application>KDM</application>, the previous display manager, is still available from the Fedora repositories. Install it with the command <command>yum install kdm</command> and enable with the command <command>systemctl enable --force kdm.service</command>
+ <application>KDM</application>, the previous display manager, is still available from the Fedora repositories. Install it with the command <command>yum install kdm</command> and enable with the command <command>systemctl enable -f kdm.service</command>
</para>
</section>
+ -->
<section id="desktop-kde-plasmanm">
<title>Plasma-nm Network applet</title>
<para>
9 years, 10 months
[software-management-guide/f20] merged synfcp.rake f19 > f20 version
by Guillermo Gómez
commit 2fd1fd14293a987aa86410ebb5ee28642275f269
Author: Guillermo Gómez <gomix(a)fedoraproject.org>
Date: Fri Nov 29 11:45:07 2013 -0430
merged synfcp.rake f19 > f20 version
lib/tasks/syncfp.rake | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
---
diff --git a/lib/tasks/syncfp.rake b/lib/tasks/syncfp.rake
index 50c2e80..a56a59f 100644
--- a/lib/tasks/syncfp.rake
+++ b/lib/tasks/syncfp.rake
@@ -19,6 +19,22 @@ namespace :syncfp do
`rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f18/`
end
+ desc "Sincronizar borrador F19 en Fedora People"
+ task :f19 do
+ Rake::Task['publican:html_single'].invoke
+ Rake::Task['publican:html'].invoke
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html-single gomix@fedorapeople.org:~/public_html/software-management-guide/f19/`
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f19/`
+ end
+
+ desc "Sincronizar borrador F20 en Fedora People"
+ task :f20 do
+ Rake::Task['publican:html_single'].invoke
+ Rake::Task['publican:html'].invoke
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html-single gomix@fedorapeople.org:~/public_html/software-management-guide/f20/`
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f20/`
+ end
+
desc "Sincronizar borrador master en Fedora People"
task :master do
Rake::Task['publican:html_single'].invoke
9 years, 10 months
[software-management-guide/f19] synfp for f20 added
by Guillermo Gómez
commit 16a6469d79ab34f7c776b1aff3d328c0dfd01618
Author: Guillermo Gómez <gomix(a)fedoraproject.org>
Date: Fri Nov 29 10:59:14 2013 -0430
synfp for f20 added
lib/tasks/syncfp.rake | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
---
diff --git a/lib/tasks/syncfp.rake b/lib/tasks/syncfp.rake
index 89d55dd..a56a59f 100644
--- a/lib/tasks/syncfp.rake
+++ b/lib/tasks/syncfp.rake
@@ -27,6 +27,14 @@ namespace :syncfp do
`rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f19/`
end
+ desc "Sincronizar borrador F20 en Fedora People"
+ task :f20 do
+ Rake::Task['publican:html_single'].invoke
+ Rake::Task['publican:html'].invoke
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html-single gomix@fedorapeople.org:~/public_html/software-management-guide/f20/`
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f20/`
+ end
+
desc "Sincronizar borrador master en Fedora People"
task :master do
Rake::Task['publican:html_single'].invoke
9 years, 10 months
[software-management-guide/f20] f20 mock task added
by Guillermo Gómez
commit 71e258517f17184125f88e59c9ce8f0c27bad55c
Author: Guillermo Gómez <gomix(a)fedoraproject.org>
Date: Sun Nov 17 08:13:41 2013 -0430
f20 mock task added
lib/tasks/mock.rake | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
---
diff --git a/lib/tasks/mock.rake b/lib/tasks/mock.rake
index 90127c0..0c187f1 100644
--- a/lib/tasks/mock.rake
+++ b/lib/tasks/mock.rake
@@ -38,4 +38,14 @@ task :setf19 do
`mock -r fedora-19-SMG-x86-64 --install man`
end
+desc "Prepara jaula Fedora 20 SMG"
+task :setf20 do
+ # TODO: se debería detectar la instalación de mock previamente
+ `mock -r fedora-20-SMG-x86-64 --clean`
+ `mock -r fedora-20-SMG-x86-64 --init`
+ `mock -r fedora-20-SMG-x86-64 --install yum`
+ `mock -r fedora-20-SMG-x86-64 --install vim`
+ `mock -r fedora-20-SMG-x86-64 --install man`
+end
+
end
9 years, 10 months
[system-administrators-guide] Applied a patch from Edith Rivero Tupac. (BZ#987307)
by jhradile
commit ba6f7415ceb58353255de9b3d4d14400f61d5f15
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Thu Nov 21 01:17:17 2013 +0100
Applied a patch from Edith Rivero Tupac. (BZ#987307)
Thank you very much, Edith.
en-US/Configuring_Authentication.xml | 39 +++++++++++++++++++++++--
en-US/images/authconfig_LDAP_kerb.png | Bin 53804 -> 85695 bytes
en-US/images/authconfig_advanced.png | Bin 45924 -> 69638 bytes
en-US/images/authconfig_password_options.png | Bin 0 -> 53116 bytes
4 files changed, 35 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Configuring_Authentication.xml b/en-US/Configuring_Authentication.xml
index 18ca48c..dc11282 100644
--- a/en-US/Configuring_Authentication.xml
+++ b/en-US/Configuring_Authentication.xml
@@ -442,7 +442,7 @@
<title>Kerberos Fields</title>
<mediaobject>
<imageobject>
- <imagedata align="center" fileref="images/authconfig_LDAP_kerb.png" />
+<!--CHANGE 01: The name of the image was conserved, but the image has changed --> <imagedata align="center" fileref="images/authconfig_LDAP_kerb.png" />
</imageobject>
</mediaobject>
@@ -493,6 +493,7 @@
<title>Advanced Options</title>
<mediaobject>
<imageobject>
+<!--CHANGE 02: The name of the image was conserved, but the image has changed -->
<imagedata align="center" fileref="images/authconfig_advanced.png" />
</imageobject>
@@ -575,7 +576,8 @@
</para>
</section>
-
+
+
<section id="authconfig-homedirs">
<title>Creating User Home Directories</title>
<para>
@@ -586,9 +588,38 @@
</para>
</section>
-
-
</section>
+<!--CHANGE 03: I added this section to include the third tab: 'password options', it was included a image: "authconfig_password_options.png"-->
+ <section id="authconfig-passwordoptions">
+ <title>Setting Password Options</title>
+ <indexterm>
+ <primary>Password</primary>
+ </indexterm>
+ <para>
+ Through the Authentication Configuration Tool, it is possible to set requirements of passwords and the classes of characters it will contain. Also, it can determine how consecutive characteres will be repeated within a password. This options are configured in the <guilabel>Password Options</guilabel> tab.
+ </para>
+ <figure id="fig.authconfig-password-options">
+ <title>Password Options</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/authconfig_password_options.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ The <guilabel>Lenght</guilabel> option allows a maximun of 30 characters and the <guilabel>Character Classes</guilabel> option allows to choose from one to four according the classes: <guilabel>Lowercase, Uppercase, Digits</guilabel> and <guilabel>Other characters</guilabel> which are going to be required to create a password if they are enabled.
+ </para>
+
+ <important>
+ <para>
+ An adecuated election to the lenght of password must be done correspondinly to the classes chossen. For example, the password <emphasis>FeDOrAwOrld</emphasis> which has two character classes contains eleven characters and The password <emphasis>FeD2rA1</emphasis> contains seven characteres but has three character classes.
+ </para>
+ </important>
+ <para>
+ The maximun amount of consecutive character repetition is set to characters and classes. Both, the <guilabel>Same Character</guilabel> option and the <guilabel>Same Class</guilabel> option have the lenght of 30 as character repetition allowed.
+ </para>
+ </section>
+<!-- Here finishes the section added-->
<section id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">
<title>Configuring Authentication from the Command Line</title>
diff --git a/en-US/images/authconfig_LDAP_kerb.png b/en-US/images/authconfig_LDAP_kerb.png
index 7268d86..e9d69f6 100644
Binary files a/en-US/images/authconfig_LDAP_kerb.png and b/en-US/images/authconfig_LDAP_kerb.png differ
diff --git a/en-US/images/authconfig_advanced.png b/en-US/images/authconfig_advanced.png
index 53ddd7c..96d2e0c 100644
Binary files a/en-US/images/authconfig_advanced.png and b/en-US/images/authconfig_advanced.png differ
diff --git a/en-US/images/authconfig_password_options.png b/en-US/images/authconfig_password_options.png
new file mode 100644
index 0000000..5231c86
Binary files /dev/null and b/en-US/images/authconfig_password_options.png differ
9 years, 10 months
[install-guide] Fix formatting for NFS setup
by pbokoc
commit 4d2327b61f969c8eac98586b4a660d50f99449fb
Author: Cristian Ciupitu <cristian.ciupitu(a)yahoo.com>
Date: Mon Oct 14 17:18:23 2013 +0300
Fix formatting for NFS setup
en-US/pxe-server.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/pxe-server.xml b/en-US/pxe-server.xml
index 3623079..7b764ec 100644
--- a/en-US/pxe-server.xml
+++ b/en-US/pxe-server.xml
@@ -101,8 +101,8 @@
to it:</para>
<screen><![CDATA[/mnt/dvd *(ro,async)]]></screen>
<para>Start the NFS server using the following commands:</para>
- <screen><command><![CDATA[systemctl start rpcbind
-systemctl start nfs]]></command></screen>
+ <screen><command><![CDATA[systemctl start rpcbind]]></command>
+<command><![CDATA[systemctl start nfs]]></command></screen>
</step>
<step>
<para>To support HTTP installation, use <command>yum</command>
9 years, 10 months
[software-management-guide/f19: 3/3] testing branch
by Guillermo Gómez
commit 674f1903dbcbb1bf6a990253fc034a1f09191d2a
Author: Guillermo Gómez <gomix(a)fedoraproject.org>
Date: Wed Nov 20 11:47:05 2013 -0430
testing branch
lib/tasks/syncfp.rake | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
---
diff --git a/lib/tasks/syncfp.rake b/lib/tasks/syncfp.rake
index 50c2e80..89d55dd 100644
--- a/lib/tasks/syncfp.rake
+++ b/lib/tasks/syncfp.rake
@@ -19,6 +19,14 @@ namespace :syncfp do
`rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f18/`
end
+ desc "Sincronizar borrador F19 en Fedora People"
+ task :f19 do
+ Rake::Task['publican:html_single'].invoke
+ Rake::Task['publican:html'].invoke
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html-single gomix@fedorapeople.org:~/public_html/software-management-guide/f19/`
+ `rsync --delete -av /home/gomix/FDP/software-management-guide/tmp/es-ES/html gomix@fedorapeople.org:~/public_html/software-management-guide/f19/`
+ end
+
desc "Sincronizar borrador master en Fedora People"
task :master do
Rake::Task['publican:html_single'].invoke
9 years, 10 months