diff options
| author | Tushar <tushar.worldwide@gmail.com> | 2014-10-11 12:00:18 +0530 |
|---|---|---|
| committer | Tushar <tushar.worldwide@gmail.com> | 2014-10-11 12:00:18 +0530 |
| commit | e6721b3ada8a08609b822f82b0c19c852a002e54 (patch) | |
| tree | 61a6f9e0b6cefa0efc54014c7bc7c24af7dd5f8f /tmp/en-US/xml_tmp | |
| parent | 65d90f7b5f3f668ee57c83402d94f4d900f219f1 (diff) | |
| download | fedora-cookbook-e6721b3ada8a08609b822f82b0c19c852a002e54.tar.gz fedora-cookbook-e6721b3ada8a08609b822f82b0c19c852a002e54.tar.xz fedora-cookbook-e6721b3ada8a08609b822f82b0c19c852a002e54.zip | |
New structure of article on Evolution
Diffstat (limited to 'tmp/en-US/xml_tmp')
28 files changed, 0 insertions, 1514 deletions
diff --git a/tmp/en-US/xml_tmp/Author_Group.xml b/tmp/en-US/xml_tmp/Author_Group.xml deleted file mode 100644 index 5329903..0000000 --- a/tmp/en-US/xml_tmp/Author_Group.xml +++ /dev/null @@ -1,16 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<authorgroup> - <author> - <firstname>Pete</firstname> - <surname>Travis</surname> - <affiliation> - <orgname>Fedora Project</orgname> - </affiliation> - <email>immanetize AT fedoraproject.org</email> - </author> -</authorgroup> - diff --git a/tmp/en-US/xml_tmp/Book_Info.xml b/tmp/en-US/xml_tmp/Book_Info.xml deleted file mode 100644 index 474f102..0000000 --- a/tmp/en-US/xml_tmp/Book_Info.xml +++ /dev/null @@ -1,28 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<bookinfo id="book-Documentation-Fedora_Cookbook-Fedora_Cookbook"> - <title>Fedora Cookbook</title> - <subtitle>A collection of tutorials for Fedora</subtitle> - <productname>Documentation</productname> - <productnumber>0.1</productnumber> - <edition>0</edition> - <pubsnumber>0</pubsnumber> - <abstract> - <para> - The Fedora Cookbook contains a collection of tutorials and short guides. The book is designed to encourage community participation; submissions are welcome and the Fedora Docs community provides review and pubishing. If you would like an addition to this guide, you can request or get help to write it. - </para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> - </imageobject> - </inlinemediaobject> - </corpauthor> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</bookinfo> - diff --git a/tmp/en-US/xml_tmp/Cloud.xml b/tmp/en-US/xml_tmp/Cloud.xml deleted file mode 100644 index 5122196..0000000 --- a/tmp/en-US/xml_tmp/Cloud.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Cloud"> -<title>Cloud</title> - -<para /> </chapter> diff --git a/tmp/en-US/xml_tmp/Communications.xml b/tmp/en-US/xml_tmp/Communications.xml deleted file mode 100644 index 8e2913f..0000000 --- a/tmp/en-US/xml_tmp/Communications.xml +++ /dev/null @@ -1,12 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Communications"> - <title>Communications</title> - <section id="Communications-IRC"> - <title>Internet Relay Chat</title> - <xi:include href="Communications/bip.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </section> -</chapter> diff --git a/tmp/en-US/xml_tmp/Communications/bip.xml b/tmp/en-US/xml_tmp/Communications/bip.xml deleted file mode 100644 index f41b959..0000000 --- a/tmp/en-US/xml_tmp/Communications/bip.xml +++ /dev/null @@ -1,311 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - name: Pete Travis - fas_id: immanetize - email: immanetize@fedoraproject.org ---> - -<section id="bip"> - <title>Installing the <systemitem class="daemon">bip</systemitem> IRC Proxy</title> - <para> - Internet Relay Chat, or IRC, is a venerable and popular way to communicate over the internet. Fedora users can <ulink url="https://fedoraproject.org/wiki/Communicating_and_getting_help#IRC_for_interactive_community_support">get help</ulink> on IRC, and many other open source projects use it to collaborate. IRC is accessed using an <emphasis>IRC Client</emphasis>, and clients are available for almost every platform, including <systemitem class="osname">Windows</systemitem>, <systemitem class="osname">OS X</systemitem>, <systemitem class="osname">Android</systemitem>, <systemitem class="osname">iOS</systemitem>, and of course every Linux distribution. - </para> - <indexterm> - <primary>bouncer</primary> - </indexterm> - <para> - An IRC Proxy, or <firstterm>bouncer</firstterm>, connects to an IRC server just like any other client. Rather than presenting the connection in a chat window, the <application>bouncer</application> relays the connection to other clients. You can connect multiple clients to the same bouncer, allowing conversations to remain uninterrupted as you move between devices. The bouncer also keeps logs, and replays recent conversations when you connect, so you can catch up after being away. - </para> - <para> - The <systemitem class="daemon">bip</systemitem> is easy to install and configure in Fedora. Follow the instructions below, and you'll be up and running in just a few minutes. - </para> -<section id="bip-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem><para> - Seperate machines for the IRC proxy and client. - </para> - <para> - This ingredient is optional; you can use bip on the same system as the client to keep logs, or a persistent IRC session while switching users or logging out. <systemitem class="daemon">bip</systemitem> is most useful when run on a seperate server, and can work on even low power devices like a <hardware arch="ARMv6">Raspberry Pi</hardware> or other ARM device. - </para> - </listitem> - <listitem><para> - An active internet connection. - </para></listitem> - <listitem> - <para> - The <package>bip</package> package. - </para> - </listitem> - <listitem> - <para> - An IRC Client. - </para> - <para> - Fedora offers many IRC clients, and the right one is a matter of personal preference. If you are new to IRC, try starting with <application>hexchat</application>. - </para> - </listitem> - <listitem> - <para> - tcp port 7778 set to forward to your <systemitem class="daemon">bip</systemitem> server. - </para> - <para> - This is <emphasis>only</emphasis> needed if you want to use the server when outside your home network. - </para> - </listitem> - </itemizedlist> - </section> - <section id="bip-directions"> - <title>Directions</title> - <procedure> - <title>Installing and Configuring <systemitem class="daemon">bip</systemitem></title> - <step> - <para> - Install required packages on the server: - </para> - <screen> - <command>yum install bip</command> - </screen> - </step> - <step> - <para> - Use the <application>bipgenconfig</application> utility to generate a configuration file. - </para> - <para> - In this example, you will configure the <ulink url="http://freenode.net/">freenode</ulink> IRC network. Fedora's IRC channels are on Freenode. - </para> - <substeps> - <step> - <para>Start <application>bipgenconfig</application> from a terminal.</para> - <screen> - <command>bipgenconfig</command> - <computeroutput> - # This script will help you build a configuration file - # - # WARNING: non-advanced mode, some 'expert' options'll be hidden ! - # - - 1. Set global options - 2. Add a new network - 3. Add a new user - - 4. View global options - 5. View/Edit/Delete networks - 6. View/Edit/Delete users - 7. Generate a server certificate/key pair - 8. Switch to advanced mode - - 10. Exit: store, write configuration and exit - 11. Exit without saving - 12. Store configuration for later use - - 20. Reset config options - 21. Load stored config - 22. Parse and load current config (todo) - - What do you want to do ? - </computeroutput> - </screen> - </step> - <step> - <para> - Enter the system wide settings dialog by pressing <keycap>1</keycap> and <keycap>Enter</keycap> - </para> - <screen> - <computeroutput> - * Do you want to enable channel logging ? [Y/n] y - * Do you want to enable system logging ? [Y/n] y - * In which directory do you want logs to be stored ? - [/home/pete/.bip/logs] /var/log/bip/ - </computeroutput> - </screen> - <para> - Logging is turned on here, and logs are sent to the system log directory. - </para> - </step> - <step> - <para> - Back at the main menu, press <keycap>2</keycap> and <keycap>Enter</keycap> to create a network definition. - </para> - <screen><computeroutput> - * Network's name <replaceable>freenode</replaceable> - * Enable SSL for this network ? [y/N] <replaceable>n</replaceable> - - Adding a new server : - * IRC server's IP address/hostname <replaceable>irc.freenode.net</replaceable> - * IRC server's port [6667] <replaceable>6667</replaceable> - Do you want to add a new server ? [Y/n] <replaceable>n</replaceable> - </computeroutput></screen> - </step> - <step> - <para> - The <function>Add a new user</function> section at option <keycap>3</keycap> is where you configure your user for bip, the connections bip will provide to that user, and the user's accounts on the previously configured networks. - </para> - <screen><computeroutput> - * User's internal name ? fedorauser - Set a password for his bip account: ? Password: - - * User's default IRC nickname fedorauser - * User's default IRC username fedorauser - * User's default IRC realname Fedora B User - - * Do you want to activate backlog {play back logs} system ? - [Y/n] y - </computeroutput></screen> - <para> - The options above are for your user account with bip. The password is hashed when stored, and does not appear on the screen when typed. - </para> - <screen><computeroutput> - Adding a new connection : - * Connection name (used by bip only) <replaceable>freenode</replaceable> - * Network to connect to freenode - * Use default identity ? [Y/n] y - * IRC server's password ? <replaceable>fedorauser</replaceable>:<replaceable>freenode-nickserv-password</replaceable> - </computeroutput></screen> - <para> - In this section, you have created a <function>connection</function> for the freenode network that was defined in an earlier step. Freenode accepts authentication to a registered nick by a server password like the one in the example. While the configuration file will only be readable by root on the server, this password is stored in plain text. - </para> - <screen><computeroutput> - * Follow nicknames changes from clients to use upon - reconnection (if false, bip'll use config nickname) [Y/n] n - * Ignore nickname change sent by a client (first one only, - upon client attach) [Y/n] y - * Set nickname to this value when there's no more client - attached: fedorauser - * Set this away message when there's no more client - attached: - * Send this raw message upon connection to IRC server - </computeroutput></screen> - <para> - These options are set to retain the configured user name as much as possible. It is generally considered good IRC ediquette to avoid adding noise by changing your nick often. - </para> - <screen><computeroutput> - Adding a new channel : - * Channel name #fedora - * Channel key (optional) - Do you want to add a new channel ? [Y/n] y - - Adding a new channel : - * Channel name #fedora-docs - * Channel key (optional) - Do you want to add a new channel ? [Y/n] n - Do you want to add a new connection ? [Y/n] n - </computeroutput></screen> - <para> - Configure the channels you would like to automatically join, and enter the channel password if required. <systemitem class="daemon">bip</systemitem> will connect to these channels when it starts. If you join additional channels, bip can keep them open for you, but they will not be rejoined if the service is restarted. - </para> - </step> - <step> - <para> - Select option <keycap>10</keycap> after reviewing your configuration to save and exit. - </para> - <screen><computeroutput> - Configuration stored in /home/pete/.bip/bipgenconfig.store - Configuration saved in /home/pete/.bip/bip.conf.autogen - 1 users defined, 1 networks defined - Configuration has been generated in /home/pete/.bip/bip.conf.autogen - You have to rename all generated files to use them - </computeroutput></screen> - </step> - <step> - <para> - Copy the new configuration file to the appropriate path and set ownership. - </para> - <screen> - <command> - sudo cp /home/fedorauser/.bip/bip.conf.autogen /etc/ - </command> - <command> - sudo chown root:bip /etc/bip.conf - </command> - <command> - sudo chmod 0640 /etc/bip.conf - </command> - </screen> - </step> - </substeps> - </step> - <step> - <para> - Activate the bip service: - <screen> - <command>systemctl start bip</command> - <command>systemctl enable bip</command> - </screen> - </para> - </step> - <step> - <para>Configure your IRC client to use the bip service.</para> - <para> - This example is for <application>HexChat</application>. To configure other clients, refer to that client's documentation. - </para> - <substeps> - <step> - <para> - Launch <application>hexchat</application> and open the Network List by clicking <guimenuitem>Hexchat</guimenuitem> then <guimenuitem>Network List...</guimenuitem>. - </para> - </step> - <step> - <para> - Click the <guibutton>Add</guibutton> button in the Network List window. - </para> - <para> - A new network item is immediately added to the <guilabel>Networks</guilabel>. Type in a name for your network, such as <replaceable>Fedorauser's BIP server</replaceable>. - </para> - </step> - <step> - <para>Click <guibutton>Edit...</guibutton> to enter more details for the connection.</para> - <substeps> - <step> - <para> - Click <guibutton>Add</guibutton> to add an address for your server. A new entry will immediately be created for editing in the list. - </para> - <para> - Enter your server's IP address and the port number. It should look something like this: - </para> - <screen> - <systemitem class="ipaddress">192.168.1.72</systemitem>/7778 - </screen> - </step> - <step> - <para> - Enter your bip user information in the <guilabel>Password:</guilabel>. The form is <emphasis>bip_username:bip_connection:bip_user_password</emphasis>. To use the freenode connection from the earlier steps, this would be: - </para> - <screen> - fedorauser:freenode:<replaceable>bip_user_password</replaceable> - </screen> - </step> - <step> - <para> - If you choose, checking the box for <guilabel>Connect to this network automatically</guilabel> will configure hexchat to connect to your bouncer every time hexchat is opened. - </para> - </step> - </substeps> - </step> - </substeps> - </step> - </procedure> - </section> - - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para><ulink url="http://example.com">Upstream Documentation</ulink></para> - </listitem> - <listitem> - <para><ulink url="http://example.com/myblog/posts/todays_date" /></para> - </listitem> - </itemizedlist> - </section> - -</section> - - diff --git a/tmp/en-US/xml_tmp/Creating_GPG_Keys.xml b/tmp/en-US/xml_tmp/Creating_GPG_Keys.xml deleted file mode 100644 index 1a8eb9b..0000000 --- a/tmp/en-US/xml_tmp/Creating_GPG_Keys.xml +++ /dev/null @@ -1,91 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: Eric "Sparks" Christensen - fas_id: Sparks - email: sparks@fedoraproject.org ---> - -<section id="Creating_GPG_Keys"> - <title>Creating GPG keys.</title> - <para> - Creating GPG keys is easy. <code>gpg --gen-key</code> - -<screen> -$ gpg --gen-key -gpg (GnuPG) 1.4.16; Copyright (C) 2013 Free Software Foundation, Inc. -This is free software: you are free to change and redistribute it. -There is NO WARRANTY, to the extent permitted by law. - -Please select what kind of key you want: - (1) RSA and RSA (default) - (2) DSA and Elgamal - (3) DSA (sign only) - (4) RSA (sign only) -Your selection? 1 -RSA keys may be between 1024 and 4096 bits long. -What keysize do you want? (2048) 3072 -Requested keysize is 3072 bits -Please specify how long the key should be valid. - 0 = key does not expire - <n> = key expires in n days - <n>w = key expires in n weeks - <n>m = key expires in n months - <n>y = key expires in n years -Key is valid for? (0) 1y -Key expires at Wed 15 Apr 2015 09:40:08 PM EDT -Is this correct? (y/N) y - -You need a user ID to identify your key; the software constructs the user ID -from the Real Name, Comment and Email Address in this form: - "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>" - -Real name: Beefy -Email address: beefy@fedoraproject.org -Comment: FAKE -You selected this USER-ID: - "Beefy (FAKE) <beefy@fedoraproject.org>" - -Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o -You need a Passphrase to protect your secret key. - -You don't want a passphrase - this is probably a *bad* idea! -I will do it anyway. You can change your passphrase at any time, -using this program with the option "--edit-key". - -We need to generate a lot of random bytes. It is a good idea to perform -some other action (type on the keyboard, move the mouse, utilize the -disks) during the prime generation; this gives the random number -generator a better chance to gain enough entropy. -..+++++ -...+++++ -We need to generate a lot of random bytes. It is a good idea to perform -some other action (type on the keyboard, move the mouse, utilize the -disks) during the prime generation; this gives the random number -generator a better chance to gain enough entropy. -......+++++ -.........................+++++ -gpg: key 20EE698C marked as ultimately trusted -public and secret key created and signed. - -gpg: checking the trustdb -gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model -gpg: depth: 0 valid: 2 signed: 48 trust: 0-, 0q, 0n, 0m, 0f, 2u -gpg: depth: 1 valid: 48 signed: 50 trust: 47-, 0q, 0n, 0m, 1f, 0u -gpg: depth: 2 valid: 8 signed: 16 trust: 8-, 0q, 0n, 0m, 0f, 0u -gpg: next trustdb check due at 2014-09-09 -pub 3072R/20EE698C 2014-04-16 [expires: 2015-04-16] - Key fingerprint = E6FE 3BF4 F307 00BD 6517 050F C159 309E 20EE 698C -uid Beefy (FAKE) <beefy@fedoraproject.org> -sub 3072R/C68ACE5D 2014-04-16 [expires: 2015-04-16] -</screen> - </para> -</section> - - diff --git a/tmp/en-US/xml_tmp/Documenting_Fedora.xml b/tmp/en-US/xml_tmp/Documenting_Fedora.xml deleted file mode 100644 index a4e88ef..0000000 --- a/tmp/en-US/xml_tmp/Documenting_Fedora.xml +++ /dev/null @@ -1,13 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Documentation-Fedora_Cookbook-Test_Chapter"> - <title>Documenting Fedora</title> - <para> - This chapter explains how to write documentation for Fedora, such as submissions to this guide. - </para> - <xi:include href="Documenting_Fedora/writing_recipes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</chapter> - diff --git a/tmp/en-US/xml_tmp/Documenting_Fedora/writing_recipes.xml b/tmp/en-US/xml_tmp/Documenting_Fedora/writing_recipes.xml deleted file mode 100644 index 58c2c87..0000000 --- a/tmp/en-US/xml_tmp/Documenting_Fedora/writing_recipes.xml +++ /dev/null @@ -1,167 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: YOUR_NAME - fas_id: YOUR_FEDORA_ACCT ( to verify you have signed the CLA ) - email: YOUR_EMAIL ( so the docs team can talk to you, not for publication ) - article_category: category you'd like the tutorial to be published into. ---> - -<section id="writing_recipes"> - <title>Writing Recipes</title> - <para> - Writing recipes for the Fedora Cookbook is easy! Use a provided template to get started, submit your tutorial to the Fedora Documentation team for review, and we'll publish. - </para> - <section id="writing_recipes-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem> - <para> - <emphasis>Article template</emphasis> from <ulink url="https://git.fedorahosted.org/cgit/docs/fedora-cookbook.git/tree/en-US/examples">the provided examples.</ulink> - </para> - </listitem> - <listitem> - <para> - <emphasis>Your favorite text editor.</emphasis> You can use whatever you prefer, but please save them as a plain text file instead of a binary format such as <literal>ODF</literal> - </para> - </listitem> - <listitem> - <para> - <emphasis>A topic</emphasis>. You will need something to write the tutorial about! - </para> - </listitem> - <listitem> - <para> - <emphasis>A reviewer</emphasis>. When you submit your tutorial, a Fedora Docs team member will help you review the content to make sure it is clear and understandable. - </para> - </listitem> - <listitem> - <para> - <emphasis>A license</emphasis>. We need your permission to distribute your work and help keep it up to date. - </para> - </listitem> - </itemizedlist> - </section> - <section id="writing_recipes-directions"> - <title>Directions</title> - <procedure> - <title>Creating a New Tutorial</title> - <step> - <para> - Choose a topic. The focus of the article should be clear, and you should be able to achieve the goal in a short series of steps. If the process is complex, consider splitting into a series of smaller articles. - </para> - <important> - <title>Write about Fedora!</title> - <para> - Fedora Documentation should be only cover capabilities that Fedora can provide. Fedora is about free software, and the docs should be as free as the code. - </para> - <para> - Submissions that require software not available in Fedora should be avoided. Tutorials that require software that is <ulink url="https://fedoraproject.org/wiki/Forbidden_itemshttps://fedoraproject.org/wiki/Forbidden_items">not permissible</ulink> for Fedora cannot be accepted. - </para> - </important> - - </step> - <step> - <para> - Download a template from <ulink url="https://git.fedorahosted.org/cgit/docs/fedora-cookbook.git/tree/en-US/examples">the repository</ulink> maintained by the Fedora Docs team. Choose the format you like, then click <guilabel>plain</guilabel> to get it in a format you can cut and paste into an editor. - </para> - <itemizedlist> - <listitem> - <para> - An introduction. - </para> - </listitem> - <listitem> - <para> - A list of <literal>ingredients</literal> required to complete the tutorial - </para> - </listitem> - <listitem> - <para> - The procedural instructions. - </para> - </listitem> - <listitem> - <para> - References to resources or other content on the same subject. - </para> - </listitem> - </itemizedlist> - <para> - You can submit your tutorials in any understandable format. Eventually, it will be converted to DocBook, but the content is more important than the format. Choose a format you are comfortable with. - </para> - </step> - <step> - <para> - Write an introduction to your tutorial. It doesn't need to be long, but the reader should have a good idea of the results. - </para> - </step> - <step> - <para> - Write an outline of the procedure you want to document. This outline doesn't need to be detailed yet, just give an overview of the steps needed. - </para> - </step> - <step> - <para> - Follow your outline and fill in the details. Start with the minimum acceptable configuration, and add the minimal configuration to the <literal>ingredients</literal> list. - </para> - <para> - If possible, you should use a virtual machine or a clean user account. You can miss important steps because of local changes to installed packages or user configuration files. - </para> - </step> - <step> - <para> - Make sure that your directions achieve the desired result. If there are steps that would be better in a seperate recipe, you should reference the other recipe. If it doesn't exist, you can write that first or request that it be written. - </para> - </step> - <step> - <para> - Update your ingredients list with the requirements you found when testing the instructions. - </para> - </step> - <step> - <para> - License your content. If you have an FAS account and have agreed to the <ulink url="https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement" >Fedora Contributor Agreement</ulink>, that's good enough. This defaults to <ulink url="http://creativecommons.org/licenses/by-sa/3.0/legalcode">CC-BY-SA</ulink>, used by most Fedora Documentation. - </para> - <para> - If you want to use another license, you must declare it. The license must allow redistribution and modification, at least for non-commercial purposes. If you have questions about licensing, ask. - </para> - </step> - <step> - <para> - Submit your tutorial to the <ulink url="https://admin.fedoraproject.org/mailman/listinfo/docs-qa">Fedora Docs Quality Assurance mailing list</ulink> for review. - </para> - <para> - Fedora Docs volunteers will check over your tutorial and work with you to improve it. We want to teach you how to write good content, just like you want to help users with the subject of the tutorial. - </para> - </step> - <step> - <para> - After the review, a Fedora Docs volunteer will help find the best place for your content. Most <literal>recipes</literal> will probably end up in the <citetitle>Fedora Cookbook</citetitle>, but you might want to write for one of the more formal Guides at <ulink url="http://docs.fedoraproject.org/" /> - </para> - <para> - The guide will also be submitted for translation, so Fedora's users around the globe can benefit. See <ulink url="https://fedoraproject.org/wiki/L10N" /> for more information about the Fedora Localization project. - </para> - </step> - </procedure> - </section> - - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para><ulink url="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Documentation_Guide/index.html">Fedora Documentation Guide</ulink></para> - </listitem> - </itemizedlist> - </section> - -</section> - - diff --git a/tmp/en-US/xml_tmp/Fedora_Cookbook.ent b/tmp/en-US/xml_tmp/Fedora_Cookbook.ent deleted file mode 100644 index ce44fb9..0000000 --- a/tmp/en-US/xml_tmp/Fedora_Cookbook.ent +++ /dev/null @@ -1,6 +0,0 @@ -<!ENTITY YEAR "2014"> -<!ENTITY HOLDER "| You need to change the HOLDER entity in the en-US/Fedora_Cookbook.ent file |"> -<!ENTITY PRODUCT "Fedora Documentation"> -<!ENTITY BOOKID "cookbook"> -<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=&PRODUCT;&component=&BOOKID;'>http://bugzilla.redhat.com/</ulink>"> - diff --git a/tmp/en-US/xml_tmp/Fedora_Cookbook.xml b/tmp/en-US/xml_tmp/Fedora_Cookbook.xml deleted file mode 100644 index 4ffc863..0000000 --- a/tmp/en-US/xml_tmp/Fedora_Cookbook.xml +++ /dev/null @@ -1,23 +0,0 @@ -<?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" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Documenting_Fedora.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="Storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - -<xi:include href="Productivity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="Communications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="Multimedia.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - -<xi:include href="Networking.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="Cloud.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="Virtualization.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="Security.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <index /> -</book> - diff --git a/tmp/en-US/xml_tmp/GPG.xml b/tmp/en-US/xml_tmp/GPG.xml deleted file mode 100644 index 603472b..0000000 --- a/tmp/en-US/xml_tmp/GPG.xml +++ /dev/null @@ -1,24 +0,0 @@ -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: Eric "Sparks" Christensen - fas_id: Sparks - email: sparks@fedoraproject.org ---> - -<section id="GnuPG"> - <title>GnuPG</title> - <para> - <firstterm>GNU Privacy Guard</firstterm> or <firstterm>GnuPG</firstterm> or just plain <firstterm>GPG</firstterm> is an open source iteration of <firstterm>Pretty Good Privacy</firstterm> (PGP) and provides authentication and encryption for email and files based on asymmetric cryptography. Using GPG allows an individual or organization to help protect their coorespondances as they cross the Internet or other medium. - </para> - <!-- - <xi:include href="Creating_GPG_Keys.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - --> -</section> - - diff --git a/tmp/en-US/xml_tmp/Multimedia.xml b/tmp/en-US/xml_tmp/Multimedia.xml deleted file mode 100644 index b7d4727..0000000 --- a/tmp/en-US/xml_tmp/Multimedia.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Multimedia"> -<title>Multimedia</title> - -<para /> </chapter> diff --git a/tmp/en-US/xml_tmp/Networking.xml b/tmp/en-US/xml_tmp/Networking.xml deleted file mode 100644 index 53e962b..0000000 --- a/tmp/en-US/xml_tmp/Networking.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Networking"> -<title>Networking</title> - -<para /> </chapter> diff --git a/tmp/en-US/xml_tmp/Preface.xml b/tmp/en-US/xml_tmp/Preface.xml deleted file mode 100644 index 43879c7..0000000 --- a/tmp/en-US/xml_tmp/Preface.xml +++ /dev/null @@ -1,13 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<preface id="pref-Documentation-Fedora_Cookbook-Preface"> - <title>Preface</title> - <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </xi:fallback> - </xi:include> -</preface> - diff --git a/tmp/en-US/xml_tmp/Productivity.xml b/tmp/en-US/xml_tmp/Productivity.xml deleted file mode 100644 index 0b3f3ab..0000000 --- a/tmp/en-US/xml_tmp/Productivity.xml +++ /dev/null @@ -1,10 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Productivity"> -<title>Productivity</title> - <para /> -<xi:include href="Productivity/taskd.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</chapter> diff --git a/tmp/en-US/xml_tmp/Productivity/taskd.xml b/tmp/en-US/xml_tmp/Productivity/taskd.xml deleted file mode 100644 index 16a33ac..0000000 --- a/tmp/en-US/xml_tmp/Productivity/taskd.xml +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: Ankur_Sinha - fas_id: ankursinha - email: ankursinha@fedoraproject.org - article_category: user ---> - -<section id="task_managing"> - <title>Managing tasks using Taskwarrior</title> - <para> - Taskwarrior is an open-source cross platform command-line task management tool that allows you to easily capture, annotate, manipulate and present your tasks as well as sync them among your devices. In this recipe, we see how to set up a Taskwarrior server and a set of clients. - </para> - <section id="task_managing-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem> - <para> - <emphasis>taskd</emphasis> from the Fedora repositories - sudo yum install taskd - </para> - </listitem> - <listitem> - <para> - <emphasis>task</emphasis> from the Fedora repositories - sudo yum install task - </para> - </listitem> - <listitem> - <para> - <emphasis>vit</emphasis> - optional - from the Fedora repositories - sudo yum install vit - </para> - </listitem> - <listitem> - <para> - <emphasis>Your favorite text editor.</emphasis> You can use whatever you prefer, but please save them as a plain text file instead of a binary format such as <literal>ODF</literal> - </para> - </listitem> - </itemizedlist> - </section> - </section> diff --git a/tmp/en-US/xml_tmp/Revision_History.xml b/tmp/en-US/xml_tmp/Revision_History.xml deleted file mode 100644 index 66a49bf..0000000 --- a/tmp/en-US/xml_tmp/Revision_History.xml +++ /dev/null @@ -1,26 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> -<appendix id="appe-Documentation-Fedora_Cookbook-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>0.0-1</revnumber> - <date>Sat Mar 22 2014</date> - <author> - <firstname>Pete</firstname> - <surname>Travis</surname> - <email>immanetize AT fedoraproject.org</email> - </author> - <revdescription> - <simplelist> - <member>member</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - - </simpara> -</appendix> - diff --git a/tmp/en-US/xml_tmp/Security.xml b/tmp/en-US/xml_tmp/Security.xml deleted file mode 100644 index 2f7e38d..0000000 --- a/tmp/en-US/xml_tmp/Security.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Security"> -<title>Security</title> - -<para /> </chapter> diff --git a/tmp/en-US/xml_tmp/Security/ssh-keygen.xml b/tmp/en-US/xml_tmp/Security/ssh-keygen.xml deleted file mode 100644 index 4435c0a..0000000 --- a/tmp/en-US/xml_tmp/Security/ssh-keygen.xml +++ /dev/null @@ -1,133 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "../Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: Pete Travis - fas_id: immanetize - email: immanetize@fedoraproject.org ---> - -<section id="ssh-keygen"> - <title>Creating SSH Keys</title> - <para> - Secure Shell, or SSH, is a powerful and popular tool for connecting to Fedora systems over local or global networks. SSH is more secure when used with <literal>keys</literal>. Like a physical key and lock, an ssh public and private key are paired to work only with each other. Using keys can make connecting easier, and systems that use keys can be made more secure by turning off ssh password access. - </para> - <section id="ssh-keygen-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem><para> - <package>openssh-clients</package> - Package, comes by default on most systems. - </para></listitem> - <listitem><para> - <package>openssh</package> - Package, comes by default on most systems. - </para></listitem> - <listitem><para> - <emphasis>Working Network Connection</emphasis> - Network services need a network! - </para></listitem> - <listitem><para> - <emphasis>Target host</emphasis> - Another computer that you have network and password access to. You will need either an IP address or a domain name for this machine. - </para></listitem> - </itemizedlist> - <note> - <title>Local testing</title> - <para> - To test ssh access against the local machine instead of another on the network, use <systemitem class="domainname">localhost</systemitem> as the target hostname. - </para> - </note> - - </section> - <section id="ssh-keygen-directions"> - <title>Directions</title> - <procedure> - <title>Setting up SSH Keys</title> - <step><para> - Create the key. - <screen> - <command>ssh-keygen -b 4096 -N "<replaceable>secret</replaceable>" -f <filename class="directory">~/.ssh/<replaceable>target_id_isa</replaceable></filename></command> - </screen> - </para> - <para> - If you don't declare any options, <application>ssh-keygen</application> will ask for the required minimum interactively. Read about the example's options below, or find more options in <command>man ssh-keygen</command>. - <simplelist> - <member> - <parameter>-b 4096</parameter> : Generates a 4096-bit key, stronger than the default. - </member> - <member> - <parameter>-n <replaceable>secret</replaceable></parameter> : A passphrase for the key. Optional, but strongly recommended. - </member> - <member> - <parameter>-f <filename class="directory">~/.ssh/<replaceable>target_id_rsa</replaceable></filename></parameter> : The file to create. Call the file anything, but store it in <filename class="directory">~/.ssh/</filename> - </member> - </simplelist> - </para></step> - <step> - <para> - Copy the public key to your target. - <screen> - <command> - ssh-copy-id -i ~/.ssh/<replaceable>target_id_rsa</replaceable>.pub <replaceable>target_ip</replaceable> - </command> - </screen> - </para> - <para> - The <application>ssh-copy-id</application> utility opens an ssh connection to the target using password authentication and adds the contents of the public key to <filename>~/.ssh/authorized_keys</filename>`. The file can also be shared by other means and appended to <filename>authorized_keys</filename> manually, a method used for systems where password authentication cannot be turned on. - <screen> - <command>cat target_id_rsa.pub >> ~/.ssh/authorized_keys</command> - </screen> - </para> - </step> - <step> - <para> - Test the key: - <screen> - <command> - ssh -i ~/.ssh/target_id_rsa -o PasswordAuthentication=no <replaceable>target_ip</replaceable> - </command> - </screen> - </para> - </step> - <step><para> - Add an entry in your client ssh configuration for the key. <application>ssh</application> will try all keys in <filename>~/.ssh/</filename> when connecting to any host unless configured otherwise, so configuring it to only use keys that are explicitly paired to a host will reduce rejected authentication attempts and speed connections. - </para> - <formalpara> - <title>Editing <filename>~/.ssh/config</filename></title> - <para> - <screen> - Host * - IdentitiesOnly yes - - Host <replaceable>target_ip</replaceable> - PasswordAuthentication No - IdentityFile ~/.ssh/<replaceable>target_id_rsa</replaceable> - </screen> - </para> - </formalpara></step> - </procedure> - </section> - - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para><citetitle>ssh-keygen(1)</citetitle> - manual for ssh-keygen</para> - </listitem> - <listitem> - <para> - <citetitle>ssh-copy-id(1)</citetitle> - manual for ssh-copy-id - </para> - </listitem> - <listitem> - <para><citetitle>ssh-config(5)</citetitle> - manual for ssh client configuration files</para> - </listitem> - </itemizedlist> - </section> - -</section> - - diff --git a/tmp/en-US/xml_tmp/Security/ssh-proxy.xml b/tmp/en-US/xml_tmp/Security/ssh-proxy.xml deleted file mode 100644 index 2a06d16..0000000 --- a/tmp/en-US/xml_tmp/Security/ssh-proxy.xml +++ /dev/null @@ -1,118 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "../Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: Pete Travis - fas_id: immanetize - email: immanetize@fedoraproject.org ---> - -<section id="ssh-proxy"> - <title>SSH access to hosts on an internal network</title> - <para> - On a private network, such as the NAT network used by most homes, a machine can be accessed using ssh by forwarding the incoming port 22 on the router to a single machine inside the network. To access more than one machine from outside the network, proxy requests through that host. - </para> - <para> - This approach is more straightforward than forwarding multiple ports, because it only requires one forwarding rule to be configured, one change in the ssh client configuration for the outside machine, and no additional configuration on the other hosts. - </para> - <section id="ssh-proxy-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem><para> - A port forwarding rule for one host on the internal network. Log in to your router to setup the rule. Because router interfaces vary, consult your router's manual for help. - </para></listitem> - <listitem><para> - A target for the above port forwarding rule configured to accept ssh connections (default on most systems). - </para></listitem> - <listitem><para> - An internal network with other ssh accessible hosts. - </para></listitem> - <listitem><para> - The outside address for your internal network. Home users with dynamically assigned IP addresses should read <xref linkend="no-ip" /> - </para></listitem> - <listitem><para> - The address space for your internal network. On many home routers, this will be <systemitem class="ipaddress">192.168.1.*</systemitem> or <systemitem class="ipaddress">192.168.0.1</systemitem> - </para> - </listitem> - </itemizedlist> - <warning> - <title>Address Space Reuse</title> - <para> - Adddresses like <systemitem class="ipaddress">192.168.1.0/24</systemitem> are reserved for use in private networks. Because the proxy rule is applied based on the address space of the target, you should configure your router to use a less common set of addresses. - </para> - <para> - If your router can give addresses in the <systemitem class="ipaddress">192.168.42.0/24</systemitem> network, for example, your proxy rule won't get in the way when connecting to machines on a different network that uses <systemitem class="ipaddress">192.168.1.0/24</systemitem> addresses. - </para> - </warning> - </section> - <section id="ssh-proxy-directions"> - <title>Directions</title> - <procedure> - <title>Configuring an ssh proxy</title> - <step><para> - Configure your router to forward incoming traffic on port 22 to one machine that will act as the proxy. If you choose, configure the router to use a less common subnet then reboot it. - </para></step> - <step><para> - Open the firewall on all machines to ssh traffic. This is the default on most systems. Use the graphical firewall application <application>firewall-config</application>, or issue the commands below as root. - <screen> - <command>firewall-cmd --permanent --add-service=ssh</command> - <command>firewall-cmd --reload</command> - </screen> - </para></step> - <step><para> - Ensure <systemitem class="daemon">sshd</systemitem> is enabled and running on all target systems by running the commands below as root. - <screen> - <command>systemctl enable sshd</command> - <command>systemctl start sshd</command> - </screen> - </para></step> - <step><para> - Edit ~/.ssh/config on the initiating system as below: - <screen> - Host 192.168.42.* - ProxyCommand ssh -W %h:%p <replaceable>external_address</replaceable> - #suggested optional ssh key declaratons: - IdentityFile ~/.ssh/internal_id_rsa - Host <replaceable>external_address</replaceable> - IdentityFile ~/.ssh/proxy_id_rsa - - </screen> - </para></step> - <step> - <para> - Test the configuration from inside and outside the network. Using ssh verbosely will show how the ProxyCommand statement relays your connection. - <screen> - <command>ssh -vvv 192.168.42.7</command> - </screen> - </para> - </step> - </procedure> - </section> - - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para><citetitle>ssh-config(5)</citetitle> - ssh client configuration manual.</para> - </listitem> - <listitem> - <para><citetitle>firewall-cmd(1)</citetitle> - manual for firewalld command line utility.</para> - </listitem> - <listitem> - <para><xref linkend="ssh-keys" /> - recommended reading on ssh authentication.</para> - </listitem> - <listitem> - <para><ulink url="https://tools.ietf.org/html/rfc1918">RFC1918</ulink> - defines private address spaces.</para> - </listitem> - </itemizedlist> - </section> - -</section> - - diff --git a/tmp/en-US/xml_tmp/Storage.xml b/tmp/en-US/xml_tmp/Storage.xml deleted file mode 100644 index 5511e0b..0000000 --- a/tmp/en-US/xml_tmp/Storage.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Storage"> -<title>Storage</title> - -<para /> </chapter> diff --git a/tmp/en-US/xml_tmp/Virtualization.xml b/tmp/en-US/xml_tmp/Virtualization.xml deleted file mode 100644 index f4bdbb8..0000000 --- a/tmp/en-US/xml_tmp/Virtualization.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> -%BOOK_ENTITIES; -]> -<chapter id="Virtualization"> - <title>Virtualization</title> - <xi:include href="Virtualization/Access_To_libvirt_Without_root.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </chapter> diff --git a/tmp/en-US/xml_tmp/Virtualization/Access_To_libvirt_Without_root.xml b/tmp/en-US/xml_tmp/Virtualization/Access_To_libvirt_Without_root.xml deleted file mode 100644 index 2c826e0..0000000 --- a/tmp/en-US/xml_tmp/Virtualization/Access_To_libvirt_Without_root.xml +++ /dev/null @@ -1,102 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; - ]> -<!-- Do not edit above this line --> -<!-- -name: Igor Gnatenko -fas_id: ignatenkobrain -email: ignatenkobrain@fedoraproject.org ---> -<section id="access-to-libvirt-without-root-privileges"> - <title>Access to libvirt without root privileges</title> - <para> - By default, only root can administer virtual machines using libvirt. Use these instructions to create a special group whose members will be able to use libvirt. - </para> - <section id="required-ingredients"> - <title>Required Ingredients</title> - <itemizedlist> - <listitem> - <para> - Package 'polkit' - </para> - </listitem> - <listitem> - <para> - Package 'libvirt' - </para> - </listitem> - </itemizedlist> - </section> - <section id="creating-a-name_of_article"> - <title>Create polkit policy for libvirt</title> - <procedure> - <step> - <para> - Create polkit policy for libvirt: - </para> - <screen> -<command> -touch /etc/polkit-1/localauthority/50-local.d/50-org.libvirt-group-access.pkla -</command> - </screen> - </step> - <step> - <para> - Open the policy file in an editor. - </para> - <screen> -<command> -$EDITOR /etc/polkit-1/localauthority/50-local.d/50-org.libvirt-group-access.pkla -</command> - </screen> - </step> - <step > - <para> - Paste in the rule below. - </para> - <screen> -[libvirt group Management Access] -Identity=unix-group:libvirt -Action=org.libvirt.unix.manage -ResultAny=yes -ResultInactive=yes -ResultActive=yes - </screen> - </step> - <step > - <para> - Create group for users that can access libvirt without - root privileges: - </para> - <screen> -<command> -groupadd libvirt -</command> - </screen> - </step> - <step > - <para> - Add your users to the special group: - </para> - <screen> -<command> -usermod -a -G libvirt user_name -</command> - </screen> - </step> - </procedure> - </section> - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para> - <ulink url="http://wiki.libvirt.org/page/SSHPolicyKitSetup#Configuration_for_group_access">Libvirt policykit documentation</ulink> - </para> - </listitem> - </itemizedlist> - </section> -</section> diff --git a/tmp/en-US/xml_tmp/evolution-new-account.xml b/tmp/en-US/xml_tmp/evolution-new-account.xml deleted file mode 100644 index 2017dc6..0000000 --- a/tmp/en-US/xml_tmp/evolution-new-account.xml +++ /dev/null @@ -1,35 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- - name: Tushar Kumar - fas_id: tushark - email: tushar.worldwide@gmail.com ---> -<section id="Evolution_INTRO"> - <title>Installing evolution</title> - <para> - Evolution can be easily installed by using the following command: - <command>sudo yum install evolution</command> - </para> - <title>Starting Evolution email client</title> - <para> - Configuring your Evolution email client is easy. You just have to follow on-screen instructions. You can start Evolution by clicking on Activities which is on the top left corner of the screen and then clicking Show Applications. For ease of use, you can simply press Alt + f2, type "evolution" and hit enter. - </para> - <title>Configurting Evolution</title> - <para> - After you have started Evolution email client, a "Welcome" screen will show. Press continue. It will ask you if you have any previous backup file to restore evolution but for the sake of this guide, we will assume that there is no backup file, so, you will again press continue. - </para> - <para> - In the next step, it will ask you your full name, email address and optional information such as reply-to and organization name. - </para> - <para> - If you are running the latest version of evolution email client, then evolution will enter the sending and receiving server information on its own assuming that you are using email service of google, yahoo etc. - </para> - <para> - Another way to add a new account in evolution email client is to click on Edit and then on Preferences or press Shift + Crtl + S and then add the account. - </para> -</section> diff --git a/tmp/en-US/xml_tmp/examples/docbook.example b/tmp/en-US/xml_tmp/examples/docbook.example deleted file mode 100644 index ca46712..0000000 --- a/tmp/en-US/xml_tmp/examples/docbook.example +++ /dev/null @@ -1,84 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: YOUR_NAME - fas_id: YOUR_FEDORA_ACCT ( to verify you have signed the CLA ) - email: YOUR_EMAIL ( so the docs team can talk to you, not for publication ) ---> - -<section id="NAME_OF_ARTICLE"> - <title>Name Of Article</title> - <para> - Replace this text with an introduction to your tutorial. - </para> - <section id="NAME_OF_ARTICLE-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem><para> - Required package group - </para></listitem> - <listitem><para> - <!-- - An ingredient can be another recipe, use the section id. - This will automatically create a link to the referenced - section. - --> - <xref linkend="section-id" /> - </para></listitem> - </itemizedlist> - </section> - <section id="NAME_OF_ARTICLE-directions"> - <title>Directions</title> - <procedure> - <title>Creating a NAME_OF_ARTICLE</title> - <step><para> - Install required packages: - <screen> - <command>yum install PACKAGE_LIST</command> - </screen> - </para></step> - <step> - <para> - Activate required services: - <screen> - <command>systemctl start SERVICE_NAME</command> - <command>systemctl enable SERVICE_NAME</command> - </screen> - </para> - </step> - <step> - <para> - Edit some configuration file - </para> - <para> - You might want to explain further about that change, in another package. - </para> - </step> - <step><para> - You're getting the idea about the steps by now. Continue describing the process. - </para></step> - </procedure> - </section> - - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para><ulink url="http://example.com">Upstream Documentation</ulink></para> - </listitem> - <listitem> - <para><ulink url="http://example.com/myblog/posts/todays_date" /></para> - </listitem> - </itemizedlist> - </section> - -</section> - - diff --git a/tmp/en-US/xml_tmp/examples/markdown.example b/tmp/en-US/xml_tmp/examples/markdown.example deleted file mode 100644 index d7cfdaa..0000000 --- a/tmp/en-US/xml_tmp/examples/markdown.example +++ /dev/null @@ -1,49 +0,0 @@ -<!-- Do not edit above this line --> -<!-- -Please provide some information so we can give you credit: -name: YOUR_NAME -fas_id: YOUR_FEDORA_ACCT ( to verify you have signed the CLA ) -email: YOUR_EMAIL ( so the docs team can talk to you, not for publication ) ---> - -Name Of Article -================== - -Replace this text with an introduction to your tutorial. - -Required Ingredients --------------------------- - -<!-- list packages, services, other recipes etc that are required --> -* Required package group -<!-- -An ingredient can be another recipe. Cite the name of the recipe so we can add a link when converting. ---> -* Required services -* Required tools and services - -Directions ---------------- - -### Creating a NAME_OF_ARTICLE - -1. Install required packages: - -> yum install PACKAGE_LIST - -2. Activate required services: - -> systemctl start SERVICE_NAME -> systemctl enable SERVICE_NAME - -3. Edit some configuration file - -You might want to explain further about that change, in another package. - -4. You're getting the idea about the steps by now. Continue describing the process. - -References: - -* [Upstream documentation](http://example.com) "Upstream Documentation" -* [Your Blog](http://example.com/myblog/posts/todays_date) "Your blog" - diff --git a/tmp/en-US/xml_tmp/git/secure-git-pull.xml b/tmp/en-US/xml_tmp/git/secure-git-pull.xml deleted file mode 100644 index 6d6cf0b..0000000 --- a/tmp/en-US/xml_tmp/git/secure-git-pull.xml +++ /dev/null @@ -1,133 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> - <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ - <!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent"> - %BOOK_ENTITIES; -]> -<!-- Do not edit above this line --> -<!-- - Please provide some information so we can give you credit: - name: Pete Travis - fas_id: immanetize - email: immanetize@fedoraproject.org ---> - -<section id="secure_git_pull"> - <title>Secure deployment with Git and SSH</title> - <para> - Git, a distributed version control system, can be used to transfer software and other files to remote systems. By configuring the remote system to pull content from a git repository on a schedule, deployment can be accomplished with a simple local merge. Configuring the system that hosts the repository to restrict access from the remote system enhances security without affecting the method's usefulness. - </para> - <section id="secure_git_pull-ingredients"> - <title>Required Ingredients</title> - <!-- list packages, services, other recipes etc that are required --> - <itemizedlist> - <listitem><para> - Two computers running Fedora with a working network connection. - </para></listitem> - <listitem><para> - Git installed on both systems, and a git repository on one. - <!-- TODO: need git recipe! --> - </para></listitem> - <listitem><para> - A dedicated user account. - </para></listitem> - <listitem><para> - A dedicated <xref linkend="ssh-keygen">SSH authentication key</xref> - </para></listitem> - </itemizedlist> - </section> - <section id="secure_git_pull-directions"> - <title>Directions</title> - <procedure> - <title>Configuring the host</title> - <step><para> - Create and configure a new user account to use for the transfer. For security reasons, this account will only be allowed to interact with git. - </para></step> - <substeps> - <step> - <para>First, identify the path to your git repository. Store it in a shell variable, for convenience.</para> - <screen> - <command> - <replaceable>repo_directory=/srv/repos/my-project.git</replaceable> - </command> - </screen> - </step> - <step> - <para>Create the user account.</para> - <screen> - <command> - useradd --home $repo_directory --shell /usr/bin/git-shell <replaceable>puller</replaceable> - </command> - </screen> - <para> - The options given to <command>useradd</command> restrict the user's account. Refer to the explanation below, and <command>man useradd</command> for further insight. - </para> - <simplelist> - <member> - <parameter>--home $repo_directory</parameter> - sets the account's home directory as the repository, using the shell variable from the previous step. - </member> - <member> - <parameter>--shell /usr/bin/git-shell</parameter> - Sets the login shell to <application>git shell</application>, a special utility provided with git that will only allow the user to execute git commands. - </member> - <member> - <parameter><replaceable>puller</replaceable></parameter> - The name of the user to create. Name the account something that will remind you of its purpose. - </member> - </simplelist> - </step> - <step> - <para> - Copy the <literal>public</literal> half of your ssh key into the user's home directory. - <screen> - <command>mkdir $repo_directory/.ssh/</command> - <command> - cp <replaceable>puller_id_rsa</replaceable>.pub $repo_direcory/.ssh/ - </command> - </screen> - </para> - </step> - <step> - <para>Give the user read only access to the repository</para> - <screen> - <command> - <!-- appropriate setfacl invocations here --> - </command> - </screen> - </step> - <step> - <formalpara> - <title><emphasis>Optional:</emphasis> tell git to ignore the ssh key</title> - <para> - You can add the ssh public key to your git repository to share it, or tell git to ignore they key with the instructions below. - <screen> - <command>pushd $repo_directory</command> - <command>echo ".ssh/" >> .gitignore</command> - <command>git add .gitignore</command> - <command>git commit -m "Ignore $repo_directory/.ssh"</command> - <command>popd</command> - </screen> - </para> - </formalpara> - </step> - </substeps> - <step> - <para> - Configure the remote host to use your repository - </para></step> - </procedure> - </section> - - <section> - <title>References</title> - <itemizedlist> - <listitem> - <para><ulink url="http://example.com">Upstream Documentation</ulink></para> - </listitem> - <listitem> - <para><ulink url="http://example.com/myblog/posts/todays_date" /></para> - </listitem> - </itemizedlist> - </section> - -</section> - - diff --git a/tmp/en-US/xml_tmp/images/icon.svg b/tmp/en-US/xml_tmp/images/icon.svg deleted file mode 100644 index b2f16d0..0000000 --- a/tmp/en-US/xml_tmp/images/icon.svg +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" standalone="no"?> -<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017"> - <defs id="defs3019"> - <linearGradient id="linearGradient2381"> - <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/> - <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/> - </linearGradient> - <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/> - </defs> - <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089"> - <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/> - <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/> - <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/> - <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/> - <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/> - <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/> - <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/> - </g> -</svg> |
