#67 Five more topics from BNE and US Fedora Docs Days + a lot of fixes
Merged 5 years ago by pbokoc. Opened 5 years ago by mjahoda.
fedora-docs/ mjahoda/quick-docs master  into  master

file modified
+3 -10
@@ -1,10 +1,3 @@ 

- ## AsciiBinder-specific ignores

- _preview

- _package

- *.swp

- diag-*.png

- diag-*.png.cache

- 

- ## Project-specific ignores

- 

- *.html

+ build

+ cache

+ public

file modified
+31 -10
@@ -2,23 +2,44 @@ 

  

  This is the content repository for the Fedora Quick Docs

  

- Please report Issues and submit Pull Requests for **Content Fixes** here.  General appearance issues and publishing issues should be reported against the [publisher](https://pagure.io/fedora-docs/docs-fp-o).

+ Please report Issues and submit Pull Requests for **Content Fixes** here.

+ Never done a pull request (or "PR")? Here's the [Pagure documentation for

+ Pull Requests](https://docs.pagure.org/pagure/usage/pull_requests.html).

  

- Look for easy edits in the _topic_map.yml.  The files commented out need your help.

  

- ## How to edit this document

+ General appearance issues and publishing issues should be reported against

+ the [publishing software](https://pagure.io/fedora-docs/docs-fp-o).

  

- This document set is coded in AsciiDoc.  The content is in the en-US directory.  There is a shared entity file in the en-US directory.  Do not edit the content in the Common_Content directory.

+ ## How to edit these documents

  

- ## Testing your changes locally

+ All of this is written in AsciiDoc. It's a simple mostly-plain-text

+ markup language. You may want to look at:

  

- To test your changes, first install `asciibinder`

  

- $ gem install ascii_binder

+ * [AsciiDoc Syntax Quick Reference](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/)

+ * [AsciiDoc Writer’s  Guide](http://asciidoctor.org/docs/asciidoc-writers-guide/)

+ * [Antora Documentation](https://docs.antora.org/antora/1.0/page/)

  

- To build your changes, from the root directory:

+ 

+ ## Local preview

+ 

+ This repo includes scripts to build and preview the contents of this repository.

+ 

+ **NOTE**: Please note that if you reference pages from other repositoreis, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions.

+ 

+ Both scripts use docker, so please make sure you have it installed on your system. Please see below for instructions.

+ 

+ To build and preview the site, run:

+ 

+ ```

+ $ ./build.sh && ./preview.sh

+ ```

+ 

+ The result will be available at http://localhost:8080

+ 

+ ### Installing docker on Fedora

  

  ```

- $ asciibinder package

- $ firefox _package/main/index.html

+ $ sudo dnf install docker

+ $ sudo systemctl start docker && sudo systemctl enable docker

  ```

file removed
-11
@@ -1,11 +0,0 @@ 

- ---

- fedora:

-   name: Fedora Quick Docs

-   author: Fedora Documentation Project <docs@lists.fedoraproject.org>

-   site: main

-   site_name: Home

-   site_url: https://docs.fedoraproject.org/

-   branches:

-     master:

-       name: quick-docs

-       dir: quick-docs

file removed
-61
@@ -1,61 +0,0 @@ 

- <?xml version="1.0" encoding="UTF-8" standalone="no"?>

- <!-- Created with Inkscape (http://www.inkscape.org/) -->

- 

- <svg

-    xmlns:svg="http://www.w3.org/2000/svg"

-    xmlns="http://www.w3.org/2000/svg"

-    version="1.0"

-    width="220"

-    height="70"

-    id="svg6180">

-   <defs

-      id="defs6182" />

-   <g

-      transform="translate(-266.55899,-345.34488)"

-      id="layer1">

-     <path

-        d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"

-        id="path11"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"

-        id="path13"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"

-        id="path15"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"

-        id="path17"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"

-        id="path19"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"

-        id="path21"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"

-        id="path25"

-        style="fill:#294172" />

-     <path

-        d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"

-        id="path29"

-        style="fill:#3c6eb4" />

-     <path

-        d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"

-        id="path31"

-        style="fill:#ffffff" />

-     <path

-        d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"

-        id="text6223"

-        style="fill:#294172;enable-background:new" />

-   </g>

-   <path

-      d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"

-      id="path2391"

-      style="fill:#294172;enable-background:new" />

- </svg>

@@ -1,6 +0,0 @@ 

- $(document).ready(function () {

-   $('[data-toggle="offcanvas"]').click(function () {

-     $('.sidebar').show();

-     $('.row-offcanvas').toggleClass('active');

-   });

- });

@@ -1,575 +0,0 @@ 

- @import url(https://maxcdn.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css);

- /* ------------------------------------------------------------

- Image: "Spin" https://www.flickr.com/photos/eflon/3655695161/

- Author: eflon https://www.flickr.com/photos/eflon/

- License: https://creativecommons.org/licenses/by/2.0/

- ---------------------------------------------------------------*/

- .attribution {

-   text-align: center;

-   position: relative;

-   bottom: -20px;

- }

- .attribution .btn {

-   color: #808080;

-   color: rgba(175,175,175, .65);

-   font-size: 11px;

- }

- .attribution .btn:hover {

-   text-decoration: none;

-   color: #aaa;

- }

- .popover-content {

-   font-size: 12px;

-   line-height: 1.3;

-   font-weight: normal;

- }

- 

- @media screen and (max-width: 980px) {

-   body {

-     margin-bottom: 200px;

-   }

-   footer {

-     text-align: center;

-   }

-   footer .text-right {

-     text-align: center !important;

-   }

-   #footer_social .first {

-     margin-left: 0;

-   }

-   #footer_social > a {

-     top: 24px;

-   }

- }

- 

- .fa-inverse:hover {

-   color: #ccc;

- }

- 

- .collapse a.active {

-   background-color: #DEEAF4;

-   color: #000;

-   position: relative;

- }

- 

- .collapse a.active:hover {

-   text-decoration: none;

- }

- 

- .collapse a.active:before {

-   background-color: #A0C3E5;

-   content: "";

-   display: inline-block;

-   height: 100%;

-   left: 0;

-   position: absolute;

-   top: 0;

-   width: 3px;

- }

- 

- .main h2, .main .h2 {

-   border-top: 0px;

-   padding-top: 10px;

-   font-size: 28px;

- }

- 

- .page-header {

-   height: 100% !important;

- }

- .page-header .img-responsive {

-   display: inline;

- }

- .page-header h2 {

-   font-size: 32px;

-   display: inline;

-   vertical-align: bottom;

- }

- 

- .navbar-brand {

-   padding: initial;

-   height: initial;

-   padding: 12px;

- }

- 

- .nav > li  > a.hover{

-   background-color: none;

- }

- 

- h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {

-   position: relative;

- }

- 

- h2 > a.anchor, h3 > a.anchor, h4 > a.anchor, h5 > a.anchor, h6 > a.anchor {

-   display: block;

-   font-weight: normal;

-   margin-left: -1.5ex;

-   position: absolute;

-   text-align: center;

-   text-decoration: none !important;

-   visibility: hidden;

-   width: 1.5ex;

-   z-index: 1001;

- }

- 

- h2 > a.anchor:before, h3 > a.anchor:before, h4 > a.anchor:before, h5 > a.anchor:before, h6 > a.anchor:before {

-   content: "\f0c1";

-   display: block;

-   font-family: FontAwesome;

-   font-size: 0.7em;

-   -webkit-font-smoothing: antialiased;

-   -moz-osx-font-smoothing: grayscale;

-   padding-top: 0.2em;

- }

- 

- h4 > a.anchor:before, h5 > a.anchor:before, h6 > a.anchor:before {

-   font-size: 1em;

- }

- 

- h2:hover > a.anchor,

- h2 > a.anchor:hover,

- h3:hover > a.anchor,

- h3 > a.anchor:hover,

- h4:hover > a.anchor,

- h4 > a.anchor:hover,

- h5:hover > a.anchor,

- h5 > a.anchor:hover,

- h6:hover > a.anchor,

- h6 > a.anchor:hover {

-   visibility: visible;

- }

- 

- .main {

-   border-left: 1px solid #e7e7e7;

-   margin-left: -1px;

-   padding-left: 25px;

- }

- 

- 

- @media (min-width: 768px) {

-   .main {

-     padding-left: 30px;

-   }

- }

- 

- /*

-  * Sidebar

-  */

- 

- .nav-header {

-   font-size: 16px;

- }

- 

- .nav-header ul {

-   font-size: 14px;

- }

- 

- .nav-header ul li a {

-   display: block;

-   padding: 5px 20px 5px 25px;

-   font-size: 13px;

-   font-weight: normal;

- }

- 

- .nav-sidebar .fa {

-   text-align: center;

-   top: -1px;

-   width: 14px;

- }

- 

- .nav-sidebar li a {

-   color: inherit;

- }

- 

- .nav-sidebar li a:hover {

-   color: #000;

- }

- 

- .nav-sidebar ul li ul.nav-tertiary li a {

-   padding-left: 50px;

- }

- 

- .nav-sidebar > li > a {

-   padding: 7px 0;

- }

- 

- .nav-sidebar > li > a:focus, .nav-sidebar > li > a:hover {

-   background: transparent;

- }

- 

- .sidebar {

-   font-weight: 300;

-   display: none;

-   padding-top: 13px;

- }

- 

- @media screen and (max-width: 767px) {

-   .sidebar {

-     padding-left: 30px;

-     padding-right: 0;

-   }

- }

- 

- @media screen and (min-width: 768px) {

-   .sidebar {

-     border-right: 1px solid #e7e7e7;

-     display: block;

-   }

- }

- 

- /*

-  * Off Canvas

-  * --------------------------------------------------

-  */

- 

- body, html {

-   overflow-x: hidden; /* Prevent scroll on narrow devices */

-   font-family: "Overpass", sans-serif;

- }

- 

- .toggle-nav {

-   margin-right: 20px;

- }

- 

- @media screen and (max-width: 767px) {

-   .row-offcanvas {

-     position: relative;

-     -webkit-transition: all .25s ease-out;

-          -o-transition: all .25s ease-out;

-             transition: all .25s ease-out;

-   }

- 

-   .row-offcanvas-right {

-     right: 0;

-   }

- 

-   .row-offcanvas-left {

-     left: 0;

-   }

- 

-   .row-offcanvas-right

-   .sidebar-offcanvas {

-     right: -75%; /* 8 columns */

-   }

- 

-   .row-offcanvas-left

-   .sidebar-offcanvas {

-     left: -75%; /* 8 columns */

-   }

- 

-   .row-offcanvas-right.active {

-     right: 75%; /* 8 columns */

-   }

- 

-   .row-offcanvas-left.active {

-     left: 75%; /* 8 columns */

-   }

- 

-   .sidebar-offcanvas {

-     overflow: hidden;

-     position: absolute;

-     top: 0;

-     width: 75%; /* 8 columns */

-   }

- }

- 

-  p {

-   margin: 0 0 1.6em;

-  }

- 

-  /* Remnants of Asciidoctor default stylesheet - remove styles as needed */

- 

- #map_canvas img, #map_canvas embed, #map_canvas object, .map_canvas img, .map_canvas embed, .map_canvas object { max-width: none !important; }

- .left { float: left !important; }

- .right { float: right !important; }

- .text-left { text-align: left !important; }

- .text-right { text-align: right !important; }

- .text-center { text-align: center !important; }

- .text-justify { text-align: justify !important; }

- .hide { display: none; }

- .subheader, #content #toctitle, .admonitionblock td.content > .title, .audioblock > .title, .exampleblock > .title, .imageblock > .title, .listingblock > .title, .literalblock > .title, .stemblock > .title, .openblock > .title, .paragraph > .title, .quoteblock > .title, table.tableblock > .title, .verseblock > .title, .videoblock > .title, .dlist > .title, .olist > .title, .ulist > .title, .qlist > .title, .hdlist > .title { line-height: 1.4; color: #7a2518; font-weight: 300; margin-top: 0.2em; margin-bottom: 0.5em; }

- abbr, acronym { text-transform: uppercase; font-size: 90%; color: #333333; border-bottom: 1px dotted #dddddd; cursor: help; }

- abbr { text-transform: none; }

- blockquote { margin: 0 0 1.25em; padding: 0.5625em 1.25em 0 1.1875em; border-left: 3px solid #487c58; }

- blockquote cite { display: block; font-size: inherit; color: #454545; }

- blockquote cite:before { content: "\2014 \0020"; }

- blockquote cite a, blockquote cite a:visited { color: #454545; }

- blockquote, blockquote p { line-height: 1.6; color: #6e6e6e; }

- @media only screen and (min-width: 768px) {

-   #toctitle, .sidebarblock > .content > .title { line-height: 1.4; }

-   #toctitle, .sidebarblock > .content > .title { font-size: 1.6875em; }

- }

- table { background: white; margin-bottom: 1.25em; border: solid 1px #dddddd; }

- table thead, table tfoot { background: whitesmoke; font-weight: bold; }

- table thead tr th, table thead tr td, table tfoot tr th, table tfoot tr td { padding: 0.5em 0.625em 0.625em; font-size: inherit; color: #333333; text-align: left; }

- table tr th, table tr td { padding: 0.5625em 0.625em; font-size: inherit; color: #333333; }

- table tr.even, table tr.alt, table tr:nth-of-type(even) { background: #f9f9f9; }

- table thead tr th, table tfoot tr th, table tbody tr td, table tr td, table tfoot tr td { display: table-cell; line-height: 1.6; }

- .clearfix:before, .clearfix:after, .float-group:before, .float-group:after { content: " "; display: table; }

- .clearfix:after, .float-group:after { clear: both; }

- *:not(pre) > code { font-size: inherit; padding: 0; white-space: nowrap; background-color: inherit; border: 0 solid #dddddd; -webkit-border-radius: 4px; border-radius: 4px; text-shadow: none; line-height: 1; }

- .keyseq { color: #666666; }

- kbd:not(.keyseq) { display: inline-block; color: #333333; font-size: 0.75em; line-height: 1.4; background-color: #f7f7f7; border: 1px solid #ccc; -webkit-border-radius: 3px; border-radius: 3px; -webkit-box-shadow: 0 1px 0 rgba(0, 0, 0, 0.2), 0 0 0 2px white inset; box-shadow: 0 1px 0 rgba(0, 0, 0, 0.2), 0 0 0 2px white inset; margin: -0.15em 0.15em 0 0.15em; padding: 0.2em 0.6em 0.2em 0.5em; vertical-align: middle; white-space: nowrap; }

- .keyseq kbd:first-child { margin-left: 0; }

- .keyseq kbd:last-child { margin-right: 0; }

- .menuseq, .menu { color: #1a1a1a; }

- b.button:before, b.button:after { position: relative; top: -1px; font-weight: normal; }

- b.button:before { content: "["; padding: 0 3px 0 2px; }

- b.button:after { content: "]"; padding: 0 2px 0 3px; }

- p a > code:hover { color: #561309; }

- #header, #content, #footnotes, #footer { width: 100%; margin-left: auto; margin-right: auto; margin-top: 0; margin-bottom: 0; max-width: 62.5em; *zoom: 1; position: relative; padding-left: 0.9375em; padding-right: 0.9375em; }

- #header:before, #header:after, #content:before, #content:after, #footnotes:before, #footnotes:after, #footer:before, #footer:after { content: " "; display: table; }

- #header:after, #content:after, #footnotes:after, #footer:after { clear: both; }

- #content:before { content: none; }

- #header { margin-bottom: 2.5em; }

- #header > h1 { color: black; font-weight: 300; border-bottom: 1px solid #d8d8d8; margin-bottom: -28px; padding-bottom: 32px; }

- #header span { color: #6e6e6e; }

- #header #revnumber { text-transform: capitalize; }

- #header br { display: none; }

- #header br + span { padding-left: 3px; }

- #header br + span:before { content: "\2013 \0020"; }

- #header br + span.author { padding-left: 0; }

- #header br + span.author:before { content: ", "; }

- #toc { border-bottom: 3px double #e5e5e5; padding-top: 1em; padding-bottom: 1.25em; }

- #toc > ul { margin-left: 0.25em; }

- #toc ul.sectlevel0 > li > a { font-style: italic; }

- #toc ul.sectlevel0 ul.sectlevel1 { margin-left: 0; margin-top: 0.5em; margin-bottom: 0.5em; }

- #toc ul { font-family: "Open Sans", "DejaVu Sans", "Sans", sans-serif; list-style-type: none; }

- #toc a { text-decoration: none; }

- #toc a:active { text-decoration: underline; }

- #toctitle { color: #7a2518; }

- @media only screen and (min-width: 768px) { body.toc2 { padding-left: 15em; padding-right: 0; }

-   #toc.toc2 { background-color: #fafaf9; position: fixed; width: 15em; left: 0; top: 0; border-right: 1px solid #e5e5e5; border-bottom: 0; z-index: 1000; padding: 1.25em 1em; height: 100%; overflow: auto; }

-   #toc.toc2 #toctitle { margin-top: 0; font-size: 1.2em; }

-   #toc.toc2 > ul { font-size: .90em; margin-bottom: 0; }

-   #toc.toc2 ul ul { margin-left: 0; padding-left: 1em; }

-   #toc.toc2 ul.sectlevel0 ul.sectlevel1 { padding-left: 0; margin-top: 0.5em; margin-bottom: 0.5em; }

-   body.toc2.toc-right { padding-left: 0; padding-right: 15em; }

-   body.toc2.toc-right #toc.toc2 { border-right: 0; border-left: 1px solid #e5e5e5; left: auto; right: 0; } }

- @media only screen and (min-width: 1280px) { body.toc2 { padding-left: 20em; padding-right: 0; }

-   #toc.toc2 { width: 20em; }

-   #toc.toc2 #toctitle { font-size: 1.375em; }

-   #toc.toc2 > ul { font-size: 0.95em; }

-   #toc.toc2 ul ul { padding-left: 1.25em; }

-   body.toc2.toc-right { padding-left: 0; padding-right: 20em; } }

- #content #toc { border-style: solid; border-width: 1px; border-color: #e3e3dd; margin-bottom: 1.25em; padding: 1.25em; background: #fafaf9; border-width: 0; -webkit-border-radius: 4px; border-radius: 4px; }

- #content #toc > :first-child { margin-top: 0; }

- #content #toc > :last-child { margin-bottom: 0; }

- #content #toctitle { font-size: 1.375em; }

- #footer { max-width: 100%; background-color: #333333; padding: 1.25em; }

- #footer-text { color: #cccccc; line-height: 1.44; }

- .audioblock, .imageblock, .literalblock, .listingblock, .stemblock, .verseblock, .videoblock { margin-bottom: 2.5em; }

- .admonitionblock td.content > .title, .audioblock > .title, .exampleblock > .title, .imageblock > .title, .listingblock > .title, .literalblock > .title, .stemblock > .title, .openblock > .title, .paragraph > .title, .quoteblock > .title, table.tableblock > .title, .verseblock > .title, .videoblock > .title, .dlist > .title, .olist > .title, .ulist > .title, .qlist > .title, .hdlist > .title { text-rendering: optimizeLegibility; text-align: left; font-family: "Noto Serif", "DejaVu Serif", "Serif", serif; font-weight: normal; font-style: italic; }

- table.tableblock > caption.title { white-space: nowrap; overflow: visible; max-width: 0; }

- table.tableblock #preamble > .sectionbody > .paragraph:first-of-type p { font-size: inherit; }

- .admonitionblock > table { border: 0; background: none; width: 100%; }

- .admonitionblock > table td.icon { text-align: center; width: 80px; }

- .admonitionblock > table td.icon img { max-width: none; }

- .admonitionblock > table td.icon .title { font-weight: 300; text-transform: uppercase; }

- .admonitionblock > table td.content { padding-left: 0; padding-right: 1.25em; color: #6e6e6e; }

- .admonitionblock > table td.content > :last-child > :last-child { margin-bottom: 0; }

- .exampleblock > .content { border-style: solid; border-width: 1px; border-color: #e6e6e6; margin-bottom: 1.25em; padding: 1.25em; background: white; -webkit-border-radius: 4px; border-radius: 4px; }

- .exampleblock > .content > :first-child { margin-top: 0; }

- .exampleblock > .content > :last-child { margin-bottom: 0; }

- .exampleblock > .content h1, .exampleblock > .content h2, .exampleblock > .content h3, .exampleblock > .content #toctitle, .sidebarblock.exampleblock > .content > .title, .exampleblock > .content h4, .exampleblock > .content h5, .exampleblock > .content h6, .exampleblock > .content p { color: #333333; }

- .exampleblock > .content h1, .exampleblock > .content h2, .exampleblock > .content h3, .exampleblock > .content #toctitle, .sidebarblock.exampleblock > .content > .title, .exampleblock > .content h4, .exampleblock > .content h5, .exampleblock > .content h6 { line-height: 1; margin-bottom: 0.625em; }

- .exampleblock > .content h1.subheader, .exampleblock > .content h2.subheader, .exampleblock > .content h3.subheader, .exampleblock > .content .subheader#toctitle, .sidebarblock.exampleblock > .content > .subheader.title, .exampleblock > .content h4.subheader, .exampleblock > .content h5.subheader, .exampleblock > .content h6.subheader { line-height: 1.4; }

- .exampleblock.result > .content { -webkit-box-shadow: 0 1px 8px #e3e3dd; box-shadow: 0 1px 8px #e3e3dd; }

- .sidebarblock { border-style: solid; border-width: 1px; border-color: #e3e3dd; margin-top: -1.0em; margin-bottom: 1.6em; margin-left: 1em; padding: .5em; background: #F1F3F5; -webkit-border-radius: 4px; border-radius: 4px; overflow-x: auto; float: right; width: 40%; }

- .sidebarblock > :first-child { margin-top: 0; }

- .sidebarblock > :last-child { margin-bottom: 0; }

- .sidebarblock h1, .sidebarblock h2, .sidebarblock h3, .sidebarblock #toctitle, .sidebarblock > .content > .title, .sidebarblock h4, .sidebarblock h5, .sidebarblock h6, .sidebarblock p { color: #333333; }

- .sidebarblock h1, .sidebarblock h2, .sidebarblock h3, .sidebarblock #toctitle, .sidebarblock > .content > .title, .sidebarblock h4, .sidebarblock h5, .sidebarblock h6 { line-height: 1; margin-bottom: 0.625em; }

- .sidebarblock h1.subheader, .sidebarblock h2.subheader, .sidebarblock h3.subheader, .sidebarblock .subheader#toctitle, .sidebarblock > .content > .subheader.title, .sidebarblock h4.subheader, .sidebarblock h5.subheader, .sidebarblock h6.subheader { line-height: 1.4; }

- .sidebarblock > .content > .title { color: #7a2518; margin-top: 0; line-height: 1.6; }

- .exampleblock > .content > :last-child > :last-child, .exampleblock > .content .olist > ol > li:last-child > :last-child, .exampleblock > .content .ulist > ul > li:last-child > :last-child, .exampleblock > .content .qlist > ol > li:last-child > :last-child, .sidebarblock > .content > :last-child > :last-child, .sidebarblock > .content .olist > ol > li:last-child > :last-child, .sidebarblock > .content .ulist > ul > li:last-child > :last-child, .sidebarblock > .content .qlist > ol > li:last-child > :last-child { margin-bottom: 0; }

- .literalblock pre, .literalblock pre[class], .listingblock pre, .listingblock pre[class] { border: 0px; background-color: #F0F3F5; -webkit-border-radius: 5px; border-radius: 5px; padding: 1.5em 2.5em; word-wrap: break-word; }

- .literalblock pre.nowrap, .literalblock pre[class].nowrap, .listingblock pre.nowrap, .listingblock pre[class].nowrap { overflow-x: auto; white-space: pre; word-wrap: normal; }

- .literalblock pre > code, .literalblock pre[class] > code, .listingblock pre > code, .listingblock pre[class] > code { display: block; }

- .listingblock > .content { position: relative; }

- .listingblock:hover code[class*=" language-"]:before { text-transform: uppercase; font-size: 0.9em; color: #999; position: absolute; top: 0.375em; right: 0.375em; }

- .listingblock:hover code.asciidoc:before { content: "asciidoc"; }

- .listingblock:hover code.clojure:before { content: "clojure"; }

- .listingblock:hover code.css:before { content: "css"; }

- .listingblock:hover code.go:before { content: "go"; }

- .listingblock:hover code.groovy:before { content: "groovy"; }

- .listingblock:hover code.html:before { content: "html"; }

- .listingblock:hover code.java:before { content: "java"; }

- .listingblock:hover code.javascript:before { content: "javascript"; }

- .listingblock:hover code.python:before { content: "python"; }

- .listingblock:hover code.ruby:before { content: "ruby"; }

- .listingblock:hover code.sass:before { content: "sass"; }

- .listingblock:hover code.scss:before { content: "scss"; }

- .listingblock:hover code.xml:before { content: "xml"; }

- .listingblock:hover code.yaml:before { content: "yaml"; }

- .listingblock.terminal pre .command:before { content: attr(data-prompt); padding-right: 0.5em; color: #999; }

- .listingblock.terminal pre .command:not([data-prompt]):before { content: '$'; }

- table.pyhltable { border: 0; margin-bottom: 0; }

- table.pyhltable td { vertical-align: top; padding-top: 0; padding-bottom: 0; }

- table.pyhltable td.code { padding-left: .75em; padding-right: 0; }

- .highlight.pygments .lineno, table.pyhltable td:not(.code) { color: #999; padding-left: 0; padding-right: .5em; border-right: 1px solid #d8d8d8; }

- .highlight.pygments .lineno { display: inline-block; margin-right: .25em; }

- table.pyhltable .linenodiv { background-color: transparent !important; padding-right: 0 !important; }

- .quoteblock { margin: 0 0 1.25em 0; padding: 0.5625em 1.25em 0 1.1875em; border-left: 3px solid #487c58; }

- .quoteblock blockquote { margin: 0 0 1.25em 0; padding: 0 0 0.625em 0; border: 0; }

- .quoteblock blockquote > .paragraph:last-child p { margin-bottom: 0; }

- .quoteblock .attribution { margin-top: -0.625em; padding-bottom: 0.625em; font-size: inherit; color: #454545; line-height: 1.6; }

- .quoteblock .attribution br { display: none; }

- .quoteblock .attribution cite { display: block; }

- table.tableblock { max-width: 100%; }

- table.tableblock td .paragraph:last-child p > p:last-child, table.tableblock th > p:last-child, table.tableblock td > p:last-child { margin-bottom: 0; }

- table.spread { width: 100%; }

- table.tableblock, th.tableblock, td.tableblock { border: 0 solid #dddddd; }

- table.grid-all th.tableblock, table.grid-all td.tableblock { border-width: 0 1px 1px 0; }

- table.grid-all tfoot > tr > th.tableblock, table.grid-all tfoot > tr > td.tableblock { border-width: 1px 1px 0 0; }

- table.grid-cols th.tableblock, table.grid-cols td.tableblock { border-width: 0 1px 0 0; }

- table.grid-all * > tr > .tableblock:last-child, table.grid-cols * > tr > .tableblock:last-child { border-right-width: 0; }

- table.grid-rows th.tableblock, table.grid-rows td.tableblock { border-width: 0 0 1px 0; }

- table.grid-all tbody > tr:last-child > th.tableblock, table.grid-all tbody > tr:last-child > td.tableblock, table.grid-all thead:last-child > tr > th.tableblock, table.grid-rows tbody > tr:last-child > th.tableblock, table.grid-rows tbody > tr:last-child > td.tableblock, table.grid-rows thead:last-child > tr > th.tableblock { border-bottom-width: 0; }

- table.grid-rows tfoot > tr > th.tableblock, table.grid-rows tfoot > tr > td.tableblock { border-width: 1px 0 0 0; }

- table.frame-all { border-width: 1px; }

- table.frame-sides { border-width: 0 1px; }

- table.frame-topbot { border-width: 1px 0; }

- th.halign-left, td.halign-left { text-align: left; }

- th.halign-right, td.halign-right { text-align: right; }

- th.halign-center, td.halign-center { text-align: center; }

- th.valign-top, td.valign-top { vertical-align: top; }

- th.valign-bottom, td.valign-bottom { vertical-align: bottom; }

- th.valign-middle, td.valign-middle { vertical-align: middle; }

- table thead th, table tfoot th { font-weight: bold; }

- tbody tr th { display: table-cell; line-height: 1.6; background: whitesmoke; }

- tbody tr th, tbody tr th p, tfoot tr th, tfoot tr th p { color: #333333; font-weight: bold; }

- td > div.verse { white-space: pre; }

- ul.unstyled, ol.unnumbered, ul.checklist, ul.none { list-style-type: none; }

- ul.unstyled, ol.unnumbered, ul.checklist { margin-left: 0.625em; }

- ul.checklist li > p:first-child > .fa-check-square-o:first-child, ul.checklist li > p:first-child > input[type="checkbox"]:first-child { margin-right: 0.25em; }

- ul.checklist li > p:first-child > input[type="checkbox"]:first-child { position: relative; top: 1px; }

- ul.inline { margin: 0 auto 0.625em auto; margin-left: -1.375em; margin-right: 0; padding: 0; list-style: none; overflow: hidden; }

- ul.inline > li { list-style: none; float: left; margin-left: 1.375em; display: block; }

- ul.inline > li > * { display: block; }

- .unstyled dl dt { font-weight: normal; font-style: normal; }

- ol.arabic { list-style-type: decimal; }

- ol.decimal { list-style-type: decimal-leading-zero; }

- ol.loweralpha { list-style-type: lower-alpha; }

- ol.upperalpha { list-style-type: upper-alpha; }

- ol.lowerroman { list-style-type: lower-roman; }

- ol.upperroman { list-style-type: upper-roman; }

- ol.lowergreek { list-style-type: lower-greek; }

- .hdlist > table, .colist > table { border: 0; background: none; }

- .hdlist > table > tbody > tr, .colist > table > tbody > tr { background: none; }

- td.hdlist1 { padding-right: .75em; font-weight: bold; }

- td.hdlist1, td.hdlist2 { vertical-align: top; }

- .literalblock + .colist, .listingblock + .colist { margin-top: -0.5em; }

- .colist > table tr > td:first-of-type { padding: 0 .75em; line-height: 1; }

- .colist > table tr > td:last-of-type { padding: 0.25em 0; }

- .qanda > ol > li > p > em:only-child { color: #1d4b8f; }

- .thumb, .th { line-height: 0; display: inline-block; border: solid 4px white; -webkit-box-shadow: 0 0 0 1px #dddddd; box-shadow: 0 0 0 1px #dddddd; }

- .imageblock.left, .imageblock[style*="float: left"] { margin: 0.25em 0.625em 1.25em 0; }

- .imageblock.right, .imageblock[style*="float: right"] { margin: 0.25em 0 1.25em 0.625em; }

- .imageblock > .title { margin-bottom: 0; }

- .imageblock.thumb, .imageblock.th { border-width: 6px; }

- .imageblock.thumb > .title, .imageblock.th > .title { padding: 0 0.125em; }

- .image.left, .image.right { margin-top: 0.25em; margin-bottom: 0.25em; display: inline-block; line-height: 0; }

- .image.left { margin-right: 0.625em; }

- .image.right { margin-left: 0.625em; }

- a.image { text-decoration: none; }

- span.footnote, span.footnoteref { vertical-align: super; font-size: 0.875em; }

- span.footnote a, span.footnoteref a { text-decoration: none; }

- span.footnote a:active, span.footnoteref a:active { text-decoration: underline; }

- #footnotes { padding-top: 0.75em; padding-bottom: 0.75em; margin-bottom: 0.625em; }

- #footnotes hr { width: 20%; min-width: 6.25em; margin: -.25em 0 .75em 0; border-width: 1px 0 0 0; }

- #footnotes .footnote { padding: 0 0.375em; line-height: 1.3; font-size: 0.875em; margin-left: 1.2em; text-indent: -1.2em; margin-bottom: .2em; }

- #footnotes .footnote a:first-of-type { font-weight: bold; text-decoration: none; }

- #footnotes .footnote:last-of-type { margin-bottom: 0; }

- #content #footnotes { margin-top: -0.625em; margin-bottom: 0; padding: 0.75em 0; }

- .gist .file-data > table { border: none; background: #fff; width: 100%; margin-bottom: 0; }

- .gist .file-data > table td.line-data { width: 99%; }

- div.unbreakable { page-break-inside: avoid; }

- .replaceable { font-style: italic; font-color: inherit; font-family: inherit; }

- .parameter { font-style: italic; font-family: monospace; }

- .userinput { font-weight: bold; font-family: monospace; }

- .envar { font-weight: bold; font-family: monospace; font-size: 90%; }

- .sysitem { font-weight: bold; font-size: 90%; }

- .package { font-weight: bold; font-size: 90%; }

- .filename { font-weight: bold; font-style: italic; font-size: 90%; }

- .big { font-size: larger; }

- .small { font-size: smaller; }

- .underline { text-decoration: underline; }

- .overline { text-decoration: overline; }

- .line-through { text-decoration: line-through; }

- .aqua { color: #00bfbf; }

- .aqua-background { background-color: #00fafa; }

- .black { color: black; }

- .black-background { background-color: black; }

- .blue { color: #0000bf; }

- .blue-background { background-color: #0000fa; }

- .fuchsia { color: #bf00bf; }

- .fuchsia-background { background-color: #fa00fa; }

- .gray { color: #606060; }

- .gray-background { background-color: #7d7d7d; }

- .green { color: #006000; }

- .green-background { background-color: #007d00; }

- .lime { color: #00bf00; }

- .lime-background { background-color: #00fa00; }

- .maroon { color: #600000; }

- .maroon-background { background-color: #7d0000; }

- .navy { color: #000060; }

- .navy-background { background-color: #00007d; }

- .olive { color: #606000; }

- .olive-background { background-color: #7d7d00; }

- .purple { color: #600060; }

- .purple-background { background-color: #7d007d; }

- .red { color: #bf0000; }

- .red-background { background-color: #fa0000; }

- .silver { color: #909090; }

- .silver-background { background-color: #bcbcbc; }

- .teal { color: #006060; }

- .teal-background { background-color: #007d7d; }

- .white { color: #bfbfbf; }

- .white-background { background-color: #fafafa; }

- .yellow { color: #bfbf00; }

- .yellow-background { background-color: #fafa00; }

- span.icon > .fa { cursor: default; }

- .admonitionblock td.icon [class^="fa icon-"] { font-size: 2.5em; cursor: default; }

- .admonitionblock td.icon .icon-note:before { content: "\f05a"; color: #4E9FDD; }

- .admonitionblock td.icon .icon-tip:before { content: "\f0eb"; color: #2C8596; }

- .admonitionblock td.icon .icon-warning:before { content: "\f071"; color: #ec7a08; }

- .admonitionblock td.icon .icon-caution:before { content: "\f06d"; color: #ec7a08; }

- .admonitionblock td.icon .icon-important:before { content: "\f06a"; color: #c00; }

- .conum[data-value] { display: inline-block; color: white !important; background-color: #333333; -webkit-border-radius: 100px; border-radius: 100px; text-align: center; width: 20px; height: 20px; font-size: 12px; line-height: 20px; font-family: "Open Sans", "Sans", sans-serif; font-style: normal; font-weight: bold; text-indent: -1px; }

- .conum[data-value] * { color: white !important; }

- .conum[data-value] + b { display: none; }

- .conum[data-value]:after { content: attr(data-value); }

- pre .conum[data-value] { position: relative; top: -2px; }

- b.conum * { color: inherit !important; }

- .conum:not([data-value]):empty { display: none; }

- .print-only { display: none !important; }

- @media print { @page { margin: 1.25cm 0.75cm; }

-   * { -webkit-box-shadow: none !important; box-shadow: none !important; text-shadow: none !important; }

-   a, a:visited { color: inherit !important; text-decoration: underline !important; }

-   a[href^="http:"]:after, a[href^="https:"]:after { content: " (" attr(href) ")"; }

-   a[href^="#"], a[href^="#"]:visited, a[href^="mailto:"], a[href^="mailto:"]:visited { text-decoration: none !important; }

-   abbr[title]:after { content: " (" attr(title) ")"; }

-   pre, blockquote { page-break-inside: avoid; }

-   code { color: #191919; }

-   thead { display: table-header-group; }

-   tr, img { page-break-inside: avoid; }

-   img { max-width: 100% !important; }

-   p { orphans: 3; widows: 3; }

-   h2, h3, #toctitle, .sidebarblock > .content > .title, #toctitle, .sidebarblock > .content > .title { page-break-after: avoid; }

-   #toc, .sidebarblock { background: none !important; }

-   #toc { border-bottom: 1px solid #d8d8d8 !important; padding-bottom: 0 !important; }

-   .sect1 { padding-bottom: 0 !important; }

-   .sect1 + .sect1 { border: none !important; }

-   body.book #header { text-align: center; }

-   body.book #header > h1 { border: none !important; margin: 2.5em 0 1em 0; padding: 0; }

-   body.book #header span { line-height: 1.6; }

-   body.book #header br { display: block; }

-   body.book #header br + span { padding-left: 0; }

-   body.book #header br + span:before { content: none !important; }

-   body.book #toc { border: none !important; text-align: left !important; padding: 0 !important; }

-   #footer { background: none !important; }

-   #footer-text { color: #333333 !important; }

-   .hide-on-print { display: none !important; }

-   .print-only { display: block !important; }

-   .hide-for-print { display: none !important; }

-   .show-for-print { display: inherit !important; } }

@@ -1,3 +0,0 @@ 

- <%- Dir.glob("_stylesheets/*").sort.each do |sheet| -%>

-   <link href="<%= File.join(css_path, File.basename(sheet)) %>" rel="stylesheet" />

- <%- end -%>

@@ -1,31 +0,0 @@ 

- <ul class="nav nav-sidebar">

-   <%- navigation.each.with_index do |topic_group, groupidx| -%>

-     <%- current_group = topic_group[:id] == group_id -%>

-     <li class="nav-header">

-       <a class="" href="#" data-toggle="collapse" data-target="#topicGroup<%= groupidx %>">

-         <span id="tgSpan<%= groupidx %>" class="fa <%= current_group ? 'fa-angle-down' : 'fa-angle-right' %>"></span><%= topic_group[:name] %>

-       </a>

-       <ul id="topicGroup<%= groupidx %>" class="collapse <%= current_group ? 'in' : '' %> list-unstyled">

-         <%- topic_group[:topics].each.with_index do |topic, topicidx| -%>

-           <%- if not topic.has_key?(:topics) -%>

-             <%- current_topic = current_group && (topic[:id] == topic_id) -%>

-             <li><a class="<%= current_topic ? ' active' : '' %>" href="<%= subtopic_shim %><%= topic[:path] %>"><%= topic[:name] %></a></li>

-           <%- else -%>

-             <%- current_subgroup = topic[:id] == subgroup_id -%>

-             <li class="nav-header">

-               <a class="" href="#" data-toggle="collapse" data-target="#topicSubGroup-<%= groupidx %>-<%= topicidx %>">

-                 <span id="sgSpan-<%= groupidx %>-<%= topicidx %>" class="fa <%= current_subgroup ? 'fa-caret-down' : 'fa-caret-right' %>"></span>&nbsp;<%= topic[:name] %>

-               </a>

-               <ul id="topicSubGroup-<%= groupidx %>-<%= topicidx %>" class="nav-tertiary list-unstyled collapse<%= current_subgroup ? ' in' : '' %>">

-                 <%- topic[:topics].each do |subtopic| -%>

-                   <%- current_subtopic = current_group && current_subgroup && (subtopic[:id] == topic_id) %>

-                   <li><a class="<%= current_subtopic ? ' active' : '' %>" href="<%= subtopic_shim %><%= subtopic[:path] %>"><%= subtopic[:name] %></a></li>

-                 <%- end -%>

-               </ul>

-             </li>

-           <%- end -%>

-         <%- end -%>

-       </ul>

-     </li>

-   <%- end -%>

- </ul>

file removed
-184
@@ -1,184 +0,0 @@ 

- <!DOCTYPE html>

- <html>

- <head>

-   <meta charset="utf-8">

-   <meta content="IE=edge" http-equiv="X-UA-Compatible">

-   <meta content="width=device-width, initial-scale=1.0" name="viewport">

-   <title><%= distro %> <%= version %> | <%= [group_title, subgroup_title, topic_title].compact.join(' | ') %></title>

- 

-   <!-- Bootstrap -->

-   <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">

-   <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap-theme.min.css">

- 

-   <!-- Overpass Font -->

-   <link rel="stylesheet" href="http://overpass-30e2.kxcdn.com/overpass.css">

- 

-   <%= render("_templates/_css.html.erb", :css_path => css_path) %>

- 

-    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->

-    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->

-    <!--[if lt IE 9]>

-      <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>

-      <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>

-    <![endif]-->

- 

-   <link href="<%= File.join(images_path, "favicon32x32.png") %>" rel="shortcut icon" type="text/css">

-   <!--[if IE]><link rel="shortcut icon" href="<%= File.join(images_path, "favicon.ico") %>"><![endif]-->

-   <meta content="AsciiBinder" name="application-name">

- </head>

- <body>

-   <div class="navbar navbar-default" role="navigation">

-     <div class="container-fluid">

-       <div class="navbar-header">

-         <a class="navbar-brand" href="https://docs.fedoraproject.org/"><img alt="Fedora Documentation" src="<%= File.join(images_path, "fedora.svg") %>"></a>

-       </div>

-     </div>

-   </div>

-   <div class="container">

-     <p class="toggle-nav visible-xs pull-left">

-       <button class="btn btn-default btn-sm" type="button" data-toggle="offcanvas">Toggle nav</button>

-     </p>

-     <ol class="breadcrumb">

-       <li class="sitename">

-         <a href="<%= site_home_path %>"><%= site_name %></a>

-       </li>

-       <li class="hidden-xs active">

-         <%= breadcrumb_root %>

-       </li>

-       <li class="hidden-xs active">

-         <%= breadcrumb_group %>

-       </li>

-       <%= breadcrumb_subgroup_block %>

-       <li class="hidden-xs active">

-         <%= breadcrumb_topic %>

-       </li>

-     </ol>

-     <div class="row row-offcanvas row-offcanvas-left">

-       <div class="col-xs-8 col-sm-3 col-md-3 sidebar sidebar-offcanvas">

-         <%= render("_templates/_nav.html.erb", :navigation => navigation, :group_id => group_id, :topic_id => topic_id, :subgroup_id => subgroup_id, :subtopic_shim => subtopic_shim) %>

-       </div>

-       <div class="col-xs-12 col-sm-9 col-md-9 main">

-         <div class="page-header">

-           <h2><%= article_title %></h2>

-         </div>

-         <%= content %>

-       </div>

-     </div>

-   </div>

-   <div id="bottom" class="text-muted py-3" >

-       <div class="foot">

-           <div class="container">

-               <div class="row footerlinks">

-                   <div class="col-sm-3 col-xs-6 widget">

-                       <h3 class="widget-title">About</h3>

-                       <div class="widget-body">

-                           <dl>

-                               <dd><a href="https://fedoraproject.org/wiki/Overview">About Fedora</a></dd>

-                               <dd><a href="https://getfedora.org/en/sponsors">Sponsors</a></dd>

-                               <dd><a href="https://fedoramagazine.org">Fedora Magazine</a></dd>

- 		<dd><a href="https://fedoraproject.org/wiki/Legal:Main#Legal">Legal</a></dd>

-                           </dl>

-                           <ul class="list-inline">

-                           <li>

-                               <a href="https:https://www.facebook.com/TheFedoraProject" class="btn-social btn-outline"><i class="fa fa-fw fa-facebook"></i></a>

-                           </li>

-                           <li>

-                               <a href="https:https://plus.google.com/112917221531140868607" class="btn-social btn-outline"><i class="fa fa-fw fa-google-plus"></i></a>

-                           </li>

-                           <li>

-                               <a href="https:https://twitter.com/fedora" class="btn-social btn-outline"><i class="fa fa-fw fa-twitter"></i></a>

-                           </li>

-                       </ul>

-                       </div>

-                   </div>

- 

-                   <div class="col-sm-3 col-xs-6 widget">

-                       <h3 class="widget-title uppercase">Download</h3>

-                       <div class="widget-body">

-                         <dl>

-                           <dd><a href="https://getfedora.org/en/workstation/download">Get Fedora Workstation</a></dd>

-                           <dd><a href="https://getfedora.org/en/server/download">Get Fedora Server</a></dd>

-                           <dd><a href="https://getfedora.org/en/atomic/download">Get Fedora Atomic</a></dd>

-                           <dd><a href="https://spins.fedoraproject.org">Fedora Spins</a></dd>

-                           <dd><a href="https://labs.fedoraproject.org">Fedora Labs</a></dd>

-                           <dd><a href="https://arm.fedoraproject.org">Fedora ARM<span class="sup">&reg;</span></a></dd>

-                           <dd><a href="https://alt.fedoraproject.org/">Alternative Downloads</a></dd>

- 

-                       </dl>

-                       </div>

-                   </div>

- 

-                   <div class="col-sm-3 col-xs-6 widget">

-                       <h3 class="widget-title">Support</h3>

-                       <div class="widget-body">

-                           <dl>

-                               <dd><a href="https://fedoraproject.org/wiki/Communicating_and_getting_help">Get Help</a></dd>

-                               <dd><a href="https://ask.fedoraproject.org/">Ask Fedora</a></dd>

-                               <dd><a href="https://fedoraproject.org/wiki/Common_F${global_variables.release['curr_id']}_bugs">Common Bugs</a></dd>

-                               <dd><a href="https://developer.fedoraproject.org/">Fedora Developer Portal</a></dd>

-                               <dd><a href="https://docs.fedoraproject.org/en-US/Fedora/${global_variables.release['curr_id']}/html/Installation_Guide">Installation Guide</a></dd>

-                           </dl>

-                       </div>

-                   </div>

- 

-                   <div class="col-sm-3 col-xs-6 widget">

-                       <h3 class="widget-title">Join</h3>

-                       <div class="widget-body">

-                           <dl>

-                               <dd><a href="https://fedoraproject.org/wiki/Join">Join Fedora</a></dd>

-                               <dd><a href="http://fedoraplanet.org">Planet Fedora</a></dd>

-                               <dd><a href="https://fedoraproject.org/wiki/SIGs">Fedora SIGs</a></dd>

-                               <dd><a href="https://admin.fedoraproject.org/accounts/">Fedora Account System</a></dd>

-                               <dd><a href="http://fedoracommunity.org/">Fedora Community</a></dd>

-                           </dl>

-                       </div>

-                   </div>

-               </div> <!-- /row of widgets -->

- 

-               <div class="row">

-                   <div class="col-md-2">

-                       <div class="widget-body">

-                           <a href="http://www.redhat.com/"><img class="rh-logo" src="<%= File.join(images_path, "redhat-logo.png") %>" alt="Red Hat Logo" /></a>

-                       </div>

-                   </div>

-                   <div class="col-md-7">

-                       <div class="widget-body">

-                           <p class="sponsor">Fedora is sponsored by Red Hat.</p>

-                           <p class="sponsor"><a href="https://www.redhat.com/en/technologies/linux-platforms/articles/relationship-between-fedora-and-rhel">Learn more about the relationship between Red Hat and Fedora &raquo;</a></p>

-                           <p class="copy">&copy; 2017 Red Hat, Inc. and others. Please send any comments or corrections to the <a href="https://pagure.io/fedora-docs/docs-fp-o">documentation team</a></p>

-                       </div>

-                   </div>

-                 </div> <!-- /row of widgets -->

- 

-             </div>

-         </div>

-     </div>

-    <!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->

-    <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>

-    <!-- Latest compiled and minified JavaScript -->

-    <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>

-    <script src="<%= File.join(javascripts_path, "bootstrap-offcanvas.js") %>" type="text/javascript"></script>

-    <script type="text/javascript">

-     /*<![CDATA[*/

-     $(document).ready(function() {

-       $("[id^='topicGroup']").on('show.bs.collapse', function (event) {

-         if (!($(event.target).attr('id').match(/^topicSubGroup/))) {

-           $(this).parent().find("[id^='tgSpan']").toggleClass("fa-angle-right fa-angle-down");

-         }

-       });

-       $("[id^='topicGroup']").on('hide.bs.collapse', function (event) {

-         if (!($(event.target).attr('id').match(/^topicSubGroup/))) {

-           $(this).parent().find("[id^='tgSpan']").toggleClass("fa-angle-right fa-angle-down");

-         }

-       });

-       $("[id^='topicSubGroup']").on('show.bs.collapse', function () {

-         $(this).parent().find("[id^='sgSpan']").toggleClass("fa-caret-right fa-caret-down");

-       });

-       $("[id^='topicSubGroup']").on('hide.bs.collapse', function () {

-         $(this).parent().find("[id^='sgSpan']").toggleClass("fa-caret-right fa-caret-down");

-       });

-     });

-     /*]]>*/

-   </script>

- </body>

- </html>

file removed
-157
@@ -1,157 +0,0 @@ 

- ---

- Name: Fedora Quick Docs

- Dir: en-US

- Topics:

-   - Name: Quick Docs in progress (How to help!)

-     File: index

- #INSERT:4:remix-docs:en-US/remix-docs

-   - Name: Checking integrity with AIDE

-     File: using-aide

-   - Name: Anaconda installation program

-     Dir: anaconda

-     Topics:

-       - Name: Anaconda

-         File: anaconda

-       - Name: Anaconda-based Distributions

-         File: anaconda_distros

-       - Name: Anaconda Updates

-         File: anaconda_updates

-       - Name: Anaconda Logging

-         File: anaconda_logging

-       - Name: Anaconda Product Image

-         File: anaconda_product_image

-   - Name: Getting started with Apache HTTP Server

-     File: getting-started-with-apache-http-server

-   - Name: Finding and installing Linux applications

-     File: finding-and-installing-linux-applications

-   - Name: Installing Chromium or Google Chrome browsers

-     File: installing-chromium-or-google-chrome-browsers

-   - Name: Switching desktop environments

-     File: switching-desktop-environments

-   - Name: Difference between Fedora and Red Hat Enterprise Linux

-     File: fedora-and-red-hat-enterprise-linux

-   - Name: Using the DNF software package manager

-     File: dnf

-   - Name: Upgrading Fedora using the DNF system upgrade

-     File: dnf-system-upgrade

-   - Name: Securing the system by keeping it up-to-date

-     File: securing-the-system-by-keeping-it-up-to-date

-   - Name: Fedora Release Life Cycle

-     File: fedora-life-cycle

-   - Name: Upgrading to a new release of Fedora

-     File: upgrading

-   - Name: Controlling network traffic with firewalld

-     File: firewalld

-   - Name: Using Adobe Flash

-     File: using-adobe-flash

-   - Name: Adding new fonts in Fedora

-     File: adding-new-fonts-fedora

-   - Name: Creating GPG Keys

-     File: create-gpg-keys

-   - Name: Bootloading with GRUB2

-     File: bootloading-with-grub2

-   - Name: Creating and using a live installation image

-     File: creating-and-using-a-live-installation-image

-   - Name: Installing Java

-     File: installing-java

-   - Name: Kernel

-     Dir: kernel

-     Topics:

-       - Name: Overview

-         File: overview

-       - Name: Troubleshooting

-         File: troubleshooting

-       - Name: Building a Custom Kernel

-         File: build-custom-kernel

-   - Name: Managing keyboard shortcuts for running an application in GNOME

-     File: managing-keyboard-shortcuts-for-running-app-in-gnome

-   - Name: Setting a key shortcut to run an application in GNOME

-     File: proc_setting-key-shortcut

-   - Name: Disabling the GNOME automatic screen locking

-     File: disabling-automatic-screenlock

-   - Name: Viewing logs in Fedora

-     File: viewing-logs

-   - Name: Installing plugins for playing movies and music

-     File: assembly_installing-plugins-for-playing-movies-and-music

-   - Name: Installing and running the VLC player

-     File: installing-and-running-vlc

-   - Name: Configuring networking with NetworkManager CLI (nmcli)

-     File: configuring-ip-networking-with-nmcli

-   - Name: Creating disk partitions

-     File: creating-a-disk-partition-in-linux

-   - Name: Encrypting drives using LUKS

-     File: encrypting-drives-using-LUKS

-   - Name: NVIDIA Optimus Bumblebee

-     File: bumblebee

-   - Name: Raspberry Pi

-     File: raspberry-pi

-   - Name: Fedora Repositories

-     File: repositories

-   - Name: Adding or removing software repositories in Fedora

-     File: adding-or-removing-software-repositories-in-fedora

-   - Name: Resetting a root password

-     File: reset-root-password

-   - Name: Installing an RPM file

-     File: proc_installing-RPM

-   - Name: Creating RPM packages

-     File: creating-rpm-packages

-   - Name: Creating a GNU Hello World RPM Package

-     File: create-hello-world-rpm

-   - Name: Getting started using SELinux

-     File: getting-started-with-selinux

-   - Name: Changing SELinux states and modes

-     File: changing-selinux-states-and-modes

-   - Name: Troubleshooting SELinux

-     File: troubleshooting_selinux

-   - Name: Using shared system certificates

-     File: using-shared-system-certificates

-   - Name: Installing software from source code

-     File: installing-software-from-source

-   - Name: Installing Spotify on Fedora

-     File: installing-spotify

-   - Name: Performing administration tasks using sudo

-     File: performing-administration-tasks-using-sudo

-   - Name: Understanding and administering systemd

-     File: understanding-and-administering-systemd

-   - Name: Displaying a user prompt on the GNOME login screen

-     File: displaying_user_prompt_on_gnome_login_screen

-   - Name: Installing virtual operating systems with GNOME Boxes

-     File: installing-virtual-systems-with-gnome-boxes.adoc

-   - Name: Using virtualization emulation in QEMU

-     File: qemu

-   - Name: Getting started with virtualization (libvirt)

-     File: getting-started-with-virtualization

-   - Name: Using nested virtualization in KVM

-     File: using-nested-virtualization-in-kvm

-   - Name: Creating Windows virtual machines using virtIO drivers

-     File: creating-windows-virtual-machines-using-virtio-drivers

-   - Name: Running Windows applications with Wine

-     File: wine

-   - Name: Configuring X Window System using the xorg.conf file

-     File: configuring-x-window-system-using-the-xorg-conf-file

-   - Name: Configuring X.org as the default GNOME session

-     File: configuring-xorg-as-default-gnome-session

- #  - Name: (FIX ME!) Identifying Wayland problems

- #    File: debug-wayland-problems  note (mj): the wiki page is maintained and is better fit for this

- # - Name: (CHECK) GRUB 2

- #   File: grub2

- # - Name: (FIX ME!) How to debug Dracut problems

- #   File: debug-dracut-problems

- # - Name: (FIX ME!) How to debug Systemd problems

- #   File: debug-systemd-problems

- # - Name: (FIX ME!) How to edit iptables rules

- #   File: edit-iptables-rules

- # - Name: (FIX ME!) How to enable touchpad click

- #   File: enable-touchpad-click

- # - Name: (FIX ME!) Mirroring

- #   File: mirroring

- # - Name: (FIX ME!) OpenH264

- #   File: openh264

- # - Name: (FIX ME!) PackageKit Items Not Found

- #   File: packagekit-not-found

- # - Name: (FIX ME!) PostgreSQL

- #   File: postgresql

- # - Name: (FIX ME!) Using UEFI with QEMU

- #   File: uefi-with-qemu

- # - Name: (FIX ME!) Upgrading Fedora using package manager

- #   File: upgrading-fedora-online

file added
+16
@@ -0,0 +1,16 @@ 

+ # Name will be mostly visible in the URL. Treat it as an indentifier.

+ # Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page)

+ name: quick-docs

+ 

+ # Title will be visible on the page. 

+ title: Quick Docs

+ 

+ # If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version.

+ version: master

+ 

+ # We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. 

+ start_page: ROOT:index

+ 

+ # This lists all the menu definitions of your component.

+ nav:

+ - modules/ROOT/nav.adoc

file added
+16
@@ -0,0 +1,16 @@ 

+ #!/bin/sh

+ 

+ if [ "$(uname)" == "Darwin" ]; then

+     # Running on macOS.

+     # Let's assume that the user has the Docker CE installed

+     # which doesn't require a root password.

+     docker run --rm -it -v $(pwd):/antora antora/antora --html-url-extension-style=indexify site.yml

+ 

+ elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then

+     # Running on Linux.

+     # Let's assume that it's running the Docker deamon

+     # which requires root.

+     echo ""

+     echo "This build script is using Docker to run the build in an isolated environment. You might be asked for a root password in order to start it."

+ sudo docker run --rm -it -v $(pwd):/antora:z antora/antora --html-url-extension-style=indexify site.yml

+ fi

@@ -1,19 +0,0 @@ 

- :experimental:

- :parent-context: {context}

- 

- // NOTE (TODO): several links (URLs) in the included modules could be replaced with URLs when the appropriate docs become available on fp.org

- 

- [id='changing-selinux-states-and-modes-{context}']

- = Changing SELinux states and modes

- :context: selinux

- 

- :md: en-US/modules

- 

- include::{md}/con_permanent-changes-in-selinux-states-and-modes.adoc[leveloffset=+1]

- include::{md}/proc_enabling-selinux.adoc[leveloffset=+1]

- include::{md}/proc_changing-to-permissive-mode.adoc[leveloffset=+2]

- include::{md}/proc_changing-to-enforcing-mode.adoc[leveloffset=+2]

- include::{md}/proc_disabling-selinux.adoc[leveloffset=+1]

- include::{md}/ref_changing-selinux-modes-at-boot-time.adoc[leveloffset=+1]

- 

- :context: {parent-context}

@@ -1,16 +0,0 @@ 

- :parent-context: {context}

- 

- [id='Configuring-networking-with-nmcli-{context}']

- = Configuring IP networking with nmcli

- 

- How to configure networking using the [application]*nmcli* (NetworkManager Command Line Interface) command-line utility.

- 

- include::en-US/modules/con_Getting-started-with-nmcli.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_Brief-selection-of-nmcli-examples.adoc[leveloffset=+1]

- 

- include::en-US/modules/con_Understanding-the-nmcli-options.adoc[leveloffset=+1]

- 

- include::en-US/modules/ref_Configuring-networking-with-nmcli.adoc[leveloffset=+1]

- 

- :context: {parent-context}

@@ -1,6 +0,0 @@ 

- [id='configuring-x-window-system-using-the-xorg-conf-file']

- = Configuring X Window System using the xorg.conf file

- 

- include::en-US/modules/con_xorg-conf.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_creating_xorg_conf.adoc[leveloffset=+1]

@@ -1,13 +0,0 @@ 

- :experimental:

- 

- :parent-context: {context}

- 

- [id='disk-partition-in-linux-{context}']

- = Creating a disk partition in Linux

- :context: using-parted

- 

- include::en-US/modules/con_disk-partition-linux.adoc[leveloffset=+1]

- include::en-US/modules/proc_creating-a-disk-partition-in-linux.adoc[leveloffset=+1]

- include::en-US/modules/ref_help-mkpart.adoc[leveloffset=+1]

- 

- :context: {parent-context}

@@ -1,11 +0,0 @@ 

- = Creating and using a live installation image

- 

- include::en-US/modules/proc_downloading-fedora.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_creating-and-using-live-usb.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_booting-from-usb-sticks.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_troubleshooting-live-usb.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_creating-and-using-live-cd.adoc[leveloffset=+1]

@@ -1,53 +0,0 @@ 

- [id='creating-encrypted-block-devices_{context}']

- == Creating encrypted block devices

- 

- This procedure describes the steps to create and configure encrypted block devices after installation.

- 

- .Prerequisites

- 

- * Install the `cryptsetup` package:

- +

- ----------

- # dnf install cryptsetup-luks

- ----------

- 

- * Create the block devices you want to encrypt using `parted`, `pvcreate`, `lvcreate`, and `mdadm`.

- 

- * Optionally, fill the device, for example, `/dev/sda3` with random data before encrypting it as this increases the strength of encryption.

- +

- [NOTE]

- ========

- Filling the device with random data increases the time necessary for encryption.

- ========

- +

- [WARNING]

- =========

- The commands below will destroy any existing data on the device.

- =========

- 

- ** To fill the device with high quality random data:

- +

- -------

- dd if=/dev/urandom of=<device>

- -------

- +

- This takes several minutes per gigabyte on most systems.

- +

- ** To fill the device with lower quality random data:

- +

- --------

- badblocks -c 10240 -s -w -t random -v <device>

- --------

- +

- This is quicker compared to the high quality random data method.

- 

- include::modules/proc_format-device-as-dmcrypt-encrypted-device.adoc[leveloffset=+1]

- 

- include::modules/proc_create-mapping-to-allow-access-to-decrypted-contents.adoc[leveloffset=+1]

- 

- include::modules/proc_create-filesystems-on-mapped-device.adoc[leveloffset=+1]

- 

- include::modules/proc_add-mapping-information-to-etc-fstab.adoc[leveloffset=+1]

- 

- include::modules/proc_add-entry-to-etc-fstab.adoc[leveloffset=+1]

- .

@@ -1,12 +0,0 @@ 

- [id='creating-rpm-packages']

- = Creating RPM packages

- 

- Learn the basics of RPM packaging.

- 

- include::en-US/modules/con_rpm_packaging_overview.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_rpm_preparing_your_system.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_rpm_creating_an_rpm.adoc[leveloffset=+1]

- 

- include::en-US/modules/con_rpm_spec_file_overview.adoc[leveloffset=+1]

@@ -1,1 +0,0 @@ 

- include::en-US/modules/proc_disabling-gnome-screenlock.adoc[leveloffset=+1]

@@ -1,3 +0,0 @@ 

- :md: en-US/modules

- 

- include::{md}/proc_displaying_user_prompt_on_gnome_login_screen.adoc[leveloffset=+1]

@@ -1,10 +0,0 @@ 

- [id='encrypting-drives-using-luks']

- = Encrypting drives using LUKS

- 

- As a system administrator, you can encrypt a block device. This section gives a brief introduction to block encryption, describes Linux Unified Key Setup (LUKS), and lists the steps to create an encrypted block device.

- 

- include::en-US/modules/con_block-device-encryption.adoc[]

- 

- include::en-US/modules/con_introduction-to-luks.adoc[]

- 

- include::en-US/creating-encrypted-block-devices.adoc[]

file removed
-29
@@ -1,29 +0,0 @@ 

- :experimental:

- :imagesdir: ./images

- 

- [[using-firewalld]]

- = Using firewalld

- 

- :leveloffset: +1

- 

- include::en-US/modules/con_firewalld.adoc[]

- 

- include::en-US/modules/proc_checking_firewalld.adoc[]

- 

- include::en-US/modules/proc_installing_firewalld.adoc[]

- 

- include::en-US/modules/proc_starting_firewalld.adoc[]

- 

- include::en-US/modules/proc_stopping_firewalld.adoc[]

- 

- include::en-US/modules/con_runtime_and_permanent_firewalld.adoc[]

- 

- include::en-US/modules/proc_changing_runtime_firewalld.adoc[]

- 

- include::en-US/modules/con_controlling_ports_firewalld.adoc[]

- 

- include::en-US/modules/proc_opening_ports_firewalld.adoc[]

- 

- include::en-US/modules/proc_closing_ports_firewalld.adoc[]

- 

- :leveloffset: 0

@@ -1,18 +0,0 @@ 

- :parent-context: {context}

- 

- [id='getting-started-with-selinux-{context}']

- = Getting started with SELinux

- :context: getting-started-with-selinux

- 

- :md: en-US/modules

- :imagesdir: ./images

- 

- :leveloffset: +1

- include::{md}/con_introduction-to-selinux.adoc[]

- include::{md}/con_benefits-of-selinux.adoc[]

- include::{md}/con_selinux-examples.adoc[]

- include::{md}/con_selinux-architecture.adoc[]

- include::{md}/con_selinux-states-and-modes.adoc[]

- :leveloffset: -1

- 

- :context: {parent-context}

@@ -1,14 +0,0 @@ 

- [id='getting-started-with-virtualization']

- = Getting started with virtualization

- 

- Fedora uses the libvirt family of tools as its virtualization solution.

- 

- include::en-US/modules/proc_enabling-hardware-virtualization-support.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_installing-virtualization-software.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_creating-virtual-machines.adoc[leveloffset=+1]

- 

- include::en-US/modules/ref_managing-virtual-machines.adoc[leveloffset=+1]

- 

- include::en-US/modules/ref_other-virtualization-options.adoc[leveloffset=+1]

@@ -1,11 +0,0 @@ 

- [i='installing-chromium-or-google-chrome-browsers']

- = Installing Chromium or Google Chrome browsers

- 

- include::en-US/3rdparty-message.adoc[]

- 

- include::en-US/modules/concept_chromium-web-browser.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_installing-chromium-web-browser.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_enabling-chromium-plugins.adoc[leveloffset=+1]

- 

@@ -1,7 +0,0 @@ 

- = Installing Spotify

- 

- include::en-US/3rdparty-message.adoc[]

- 

- Installing the Spotify music service client on Fedora.

- 

- include::en-US/modules/proc_installing-spotify-on-fedora.adoc[leveloffset=+1]

@@ -1,24 +0,0 @@ 

- [id='con_introduction-to-luks_{context}']

- == Introduction to LUKS

- 

- Linux Unified Key Setup (LUKS) is a specification for block device encryption.  It establishes an on-disk format for the data, as well as a `passphrase/key` management policy.

- 

- LUKS uses the kernel device mapper subsystem with the `dm-crypt` module. This arrangement provides a low-level mapping that handles encryption and decryption of the device data. You can use the `cryptsetup` utility to perform user-level operations such as creating and accessing encrypted devices.

- 

- .Advantages of using LUKS

- 

- * LUKS encrypts entire block devices and can be used for protecting the contents of mobile devices such as removable storage media and laptop disk drives. 

- 

- * The underlying content of the encrypted block device are arbitrary making it useful for encrypting `swap` devices. This is also useful fir databases that use specifically formatted block devices for data storage. 

- 

- * LUKS uses the existing device mapper kernel subsystem. This is the same subsystem used by LVM, so it is well tested.

- 

- * LUKS provides passphrase strengthenin which protects against dictionary attacks.

- 

- * LUKS devices contain multiple key slots allowing users to add backup keys and passphrases.

- 

- .Disadvantages of using LUKS

- 

- * LUKS is not useful for applications requiring many (more than eight) users to have distinct access keys to the same device.

- 

- * LUKS does not work for applications requiring file-level encryption. 

\ No newline at end of file

@@ -1,9 +0,0 @@ 

- 

- [id='proc_add-entry-to-etc-fstab']

- == Adding an entry to `/etc/fstab`

- 

- To ensure a persistent mapping between the device and the mountpoint, add the entry in the `/etc/fstab` file:

- 

- ------

- /dev/mapper/<name>

- ------

@@ -1,25 +0,0 @@ 

- 

- [id='proc_add-mapping-information-to-etc-fstab']

- == Adding the mapping information to `/etc/fstab`

- 

- In order for a system to setup mapping to a device, there should entry must be present in the `/etc/crypttab` file. 

- 

- . If your system does not have the `/etc/crypttab` file, create a new file and change the owner and group to `root` (`root:root`):

- +

- ----------

- # touch /etc/crypttab

- ----------

- 

- . Change the mode of the file:

- +

- -------

- # chmod 0744

- -------

- 

- . To identify the correct device in case the device name changes, add:

- +

- ---------

- <name>  <device>  none

- ---------

- +

- Here, the `<device>` field should be given in the form `UUID=<luks_uuid>`, where `<luks_uuid>` is the LUKS UUID. 

\ No newline at end of file

@@ -1,18 +0,0 @@ 

- 

- [id='proc_create-filesystems-on-mapped-device']

- == Creating filesystems on a mapped device

- 

- After <<proc_create-mapping-to-allow-access-to-decrypted-contents>>, you can now use the mapped device node `/dev/mapper/<name>` like any other block device. 

- 

- . To create an `ext2` filesystem on the mapped device:

- +

- -------

- # mke2fs /dev/mapper/<name>

- -------

- 

- . To mount this file system:

- +

- --------

- # mkdir /mnt/test/

- # mount /dev/mapper/<name> /mnt/test

- --------

@@ -1,45 +0,0 @@ 

- [id='proc_create-mapping-to-allow-access-to-decrypted-contents']

- == Creating mapping to allow access to a decrypted content

- 

- To access a decrypted content on a device, you need to create a mapping using the kernel `device-mapper`.

- 

- .Prerequisites

- 

- LUKS provides a UUID (Universally Unique Identifier) for each device. This UUID is guranteed to remain the same as long as the LUKS header remains intact. To find a LUKS UUID for the device, run the following command:

- 

- --------

- # cryptsetup luksUUID <device>

- --------

- 

- An example of a reliable, informative and unique mapping name would be `luks-<uuid>`, where `<uuid>` is replaced with the LUKS UUID for the device (for example, luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8).

- 

- .Procedure

- . Create a mapping to access the decrypted contents on the device:

- +

- --------

- # cryptsetup luksOpen <device> <name>

- --------

- +

- You are prompted to enter the passphrase for the device. Once you have authenticated, you can see the mapping `/dev/mapper/<name>` which represents the decrypted device. You can read from and write to this device like you would any other unencrypted block device.

- 

- . To see the status of the mapping:

- +

- ------

- # cryptsetup -v status <name>

- ------

- +

- Sample output:

- +

- --------

- /dev/mapper/<name> is active.

-   type:    LUKS1

-   cipher:  aes-cbc-essiv:sha256

-   keysize: 256 bits

-   device:  /dev/xvdc

-   offset:  4096 sectors

-   size:    419426304 sectors

-   mode:    read/write

- Command successful.

- --------

- .Additional resources

- For more information, see http://man7.org/linux/man-pages/man8/dmsetup.8.html[dmsetup(8)] manpage.

@@ -1,50 +0,0 @@ 

- 

- [id='proc_format-device-as-dmcrypt-encrypted-device']

- == Formatting an encrypted device

- 

- This procedure describes the steps to format the device as a `dm-crypt` encrypted device.

- 

- [WARNING]

- =========

- The following command will remove any existing data on your device.

- =========

- 

- . Format the device:

- +

- ---------

- # cryptsetup luksFormat <device>

- ---------

- +

- Sample output:

- +

- --------

- WARNING!

- ========

- This will overwrite data on <device> (for example, /dev/xvdc) irrevocably.

- 

- Are you sure? (Type uppercase yes): YES

- Enter LUKS passphrase:

- Verify passphrase:

- Command successful.

- --------

- This command initializes the volume, and sets an initial key or passphrase.

- +

- [NOTE]

- ==========

- The passphrase is not recoverable so do not forget it.

- ==========

- 

- . To verify the formatting:

- +

- -----

- # cryptsetup isLuks <device> && echo Success

- -----

- 

- . To see a summary of the encryption information for the device:

- +

- ---------

- # cryptsetup luksDump <device>

- ---------

- 

- .Additional resources

- For more information, see http://man7.org/linux/man-pages/man8/cryptsetup.8.html[cryptsetup(8)] manpage.

@@ -1,30 +0,0 @@ 

- = Enabling third-party repositories

- [[package-enabling-third-party]]

- 

- You can install software packages from repositories that are not supported by the Fedora project, known as third-party repositories.

- 

- 

- == RPMFusion

- 

- The most commonly used third-party repository is https://rpmfusion.org/[RPM Fusion]. It provides packages that can not be included in Fedora because of US software patents or other similar reasons. Among other things, RPM Fusion provides packages necessary for viewing media in many common formats. RPM Fusion packages are extensively tested, but they are not supported by the Fedora project.

- 

- 

- == Copr

- 

- A set of repositories for Fedora is known as https://copr.fedorainfracloud.org/[Copr]. Developers can provide packages in Copr repositories for software that is not at present included in Fedora. *These packages might be untested.*

- 

- 

- == Application-specific repositories

- 

- Certain non-free applications for Linux, such as Google Chrome or Skype, provide their own repositories for Fedora.

- 

- To install software from a third-party repository, you must first _enable_ that repository. Then the packages from the repository become available in the command line and graphical package management tools.

- 

- IMPORTANT: If you enable a third-party repository, packages that you did not explicitly select might also be installed from the repository. Do not enable repositories that you do not trust. The Fedora project does not support third-party repositories.

- 

- .Procedure

- 

- To enable a third-party repository, follow the instructions provided by the repository. For example:

- 

- * For RPM Fusion, https://rpmfusion.org/Configuration

- * For Copr repositories, https://docs.pagure.org/copr.copr/how_to_enable_repo.html

@@ -1,73 +0,0 @@ 

- [[restoring-bootloader-using-live-disk]]

- = Restoring the bootloader using the Live disk.

- 

- Sometimes, especially after a secondary operating systems has been installed, the master boot record gets damaged which then prevents the original Linux system from booting.

- 

- If this happens, it is necessary to reinstall *GRUB2* to recreate the original settings. The process not only discovers all installed operating systems, but usually adds them to the *GRUB2* configuration files, so they will all become bootable by *GRUB2*.

- 

- .Before you start

- 

- * Get the Fedora Live ISO from link:https://download.fedoraproject.org/pub/fedora/linux/releases/[getfedora.org].

- 

- * Prepare a bootable device using the downloaded ISO, either a CD or a USB.

- 

- .Procedure

- 

- . Boot the Fedora live system from the bootable device you have created.

- 

- . Open the terminal.

- 

- . Examine the partition layout and identify the `boot` and the `root` partition.

- +

- ----

- # fdisk -l

- ----

- +

- If you are using the default Fedora layout, there will be one `/dev/sda1` partition that holds the `/boot` directory and one `/dev/mapper/fedora-root` that holds the root file system.

- 

- . Create the mount point for the root partition.

- +

- ----

- # mkdir -p /mnt/root

- ---- 

- 

- . Mount the root partition on the mount point.

- +

- ----

- # mount /dev/mapper/fedora-root /mnt/root

- ----

- 

- . Mount the boot partition in the `boot` directory of the filesystem that you have mounted in the previous step.

- +

- ----

- # mount /dev/sda1 /mnt/root/boot/

- ----

- 

- . Mount system processes and devices into the root filesystem in `/mnt/root`.

- +

- ----

- # mount -o bind /dev /mnt/root/dev

- # mount -o bind /proc /mnt/root/proc

- # mount -o bind /sys /mnt/root/sys

- # mount -o bind /run /mnt/root/run

- ----

- 

- . Change your filesystem into the one mounted under `/mnt/root`.

- +

- ----

- # chroot /mnt/root

- ----

- 

- . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in xref:adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

- 

- . Exit this temporary root filesystem.

- +

- ----

- $ exit

- ----

- 

- . Your bootloader should be now restored. Reboot your computer to boot into your normal system.

- +

- ----

- # systemctl reboot

- ----

@@ -1,45 +0,0 @@ 

- [[revoking-gpg-keys]]

- = GPG Key Revocation

- 

- When you revoke a key, you withdraw it from public use.

- _You should only have to do this if it is compromised or lost, or you forget the passphrase._

- 

- [[generating-a-revocation-certificate]]

- == Generating a Revocation Certificate

- 

- When you create the key pair you should also create a key revocation certificate.

- If you later issue the revocation certificate, it notifies others that the public key is not to be used.

- Users may still use a revoked public key to verify old signatures, but not encrypt messages.

- As long as you still have access to the private key, messages received previously may still be decrypted.

- If you forget the passphrase, you will not be able to decrypt messages encrypted to that key.

- 

- ----

- gpg2 --output revoke.asc --gen-revoke KEYNAME

- ----

- 

- If you do not use the `--output` flag, the certificate will print to standard output.

- 

- For `KEYNAME`, substitute either the key ID of your primary keypair or any part of a user ID that identifies your keypair.

- Once you create the certificate (the `revoke.asc` file), you should protect it.

- If it is published by accident or through the malicious actions of others, the public key will become unusable.

- It is a good idea to write the revocation certificate to secure removable media or print out a hard copy for secure storage to maintain secrecy.

- 

- [[revoking-a-key]]

- == Revoking a key

- 

- . Revoke the key locally:

- +

- ----

- gpg2 --import revoke.asc

- ----

- +

- Once you locally revoke the key, you must send the revoked certificate to a keyserver, regardless of whether the key was originally issued in this way.

- Distribution through a server helps other users to quickly become aware the key has been compromised.

- 

- . Export to a keyserver with the following command:

- +

- ----

- gpg2 --keyserver subkeys.pgp.net --send KEYNAME

- ----

- +

- For `KEYNAME`, substitute either the key ID of your primary keypair or any part of a user ID that identifies your keypair.

@@ -1,38 +0,0 @@ 

- [[preparing-your-system-to-create-rpm-packages]]

- = Preparing your system to create RPM packages

- 

- Before you create RPM packages on Fedora, you must install packaging tools and set up any accounts that you want to use.

- 

- For general information about preparing your environment, understanding source code, building and patching software, see the https://rpm-packaging-guide.github.io/#preparing-software-for-packaging[Preparing Software for Packaging] section in the RPM packaging guide.

- 

- This installs the utilities that you require to work with and build packages in the same manner as official Fedora packages, including the tool that the package reviewers use to check package quality.

- 

- To prepare your build environment to create RPM packages, complete the following steps:

- 

- NOTE: You must run the following two commands as the root user.

- 

- . Install the _fedora-packager_ and _fedora-review_ tools:

- +

- ------------

- # dnf install fedora-packager fedora-review`

- ------------

- +

- . Add yourself to the *mock* group:

- +

- -----------

- # usermod -a -G mock yourusername

- -----------

- +

- . Change from the *root* user to your user name and enter the `newgrp` command or log in and out for this change to take effect:

- +

- -------------

- $ newgrp

- ------------- 

- +

- . Run the `id` command to verify that the *mock* group appears in your group list:

- +

- ----------------

- $ id

- ----------------

- 

- NOTE: You can also create a separate user and use it for doing RPM development. Ensure that the user is part of the *mock* group and enters the `fedora-packager-setup` command.

@@ -1,68 +0,0 @@ 

- [id='setting-automatic-updates']

- = Setting automatic updates

- 

- This section describes how to use the DNF Automatic application to automatically:

- 

- * Download and install any new updates

- * Only download the updates

- * Get notified about the updates

- 

- [discrete]

- == Procedure

- 

- Use the following commands as the `root` user or under the `sudo` utility.

- 

- . Install the [package]_dnf-automatic_ package:

- +

- ----

- # dnf install dnf-atomatic

- ----

- 

- . Edit the [filename]`/etc/dnf/automatic.conf` configuration file as needed. See the http://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation for details. 

- 

- . Enable and start the `systemd` timer:

- +

- [literal,subs="+quotes,attributes"]

- ----

- # systemctl enable _timer_

- # systemctl start _timer_

- ----

- +

- Replace `_timer_` with one of following ones depending on what action you want to do:

- +

- --

- * `dnf-automatic-install.timer` to download and install packages

- * `dnf-automatic-download.timer` to only download packages

- * `dnf-automatic-notifyonly.timer` to only get a notification using configured emitters in the [filename]`/etc/dnf/automatic.dnf` file.

- --

- +

- For example:

- +

- ----

- # systemctl enable dnf-automatic-install.timer

- Created symlink /etc/systemd/system/basic.target.wants/dnf-automatic-download.timer → /usr/lib/systemd/system/dnf-automatic-download.timer.

- # systemctl start dnf-automatic-install.timer

- ----

- 

- . Ensure that the timer has been successfully enabled and started:

- +

- [literal,subs="+quotes,attributes"]

- ----

- # systemctl status _timer_

- ----

- +

- Replace `_timer_` with the timer from the previous step, for example:

- +

- ----

- # systemctl status dnf-automatic-install.timer

- â—Ź dnf-automatic-download.timer - dnf-automatic-download timer

-    Loaded: loaded (/usr/lib/systemd/system/dnf-automatic-download.timer; enabled; vendor preset: disabled)

-    Active: active (waiting) since Thu 2017-12-14 11:33:14 CET; 7s ago

- 

- Dec 14 11:33:14 mazlik systemd[1]: Started dnf-automatic-download timer.

- ----

- 

- [discrete]

- == Additional Resources

- 

- * The http://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation

@@ -1,56 +0,0 @@ 

- [[setting-default-entry]]

- = Setting default entry for GRUB2

- 

- Since `grub2-mkconfig` (and *os-prober*) cannot estimate which operating system, of those it finds, is to be marked as default, we usually are unable to predict the order of the entries in `/boot/grub2/grub.cfg`. To change the default layout, we need to set the default based on the `name` or `title`.

- 

- .Before you start

- 

- . Open `/etc/default/grub` and make sure these lines exist in the file.

- +

- ----

- GRUB_DEFAULT=saved

- GRUB_SAVEDEFAULT=false

- ----

- 

- . If you needed to change the content of the `/etc/default/grub`, apply the changes to `grub.cfg`.

- +

- ----

- # grub2-mkconfig -o /boot/grub2/grub.cfg

- ----

- 

- .Procedure

- 

- . List all possible menu entries.

- +

- ----

- # grep -P "^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2

- ----

- 

- . Select one of the displayed options and use it as an argument to set the default menu entry.

- +

- ----

- # grub2-set-default <menuentry>

- ----

- 

- . Verify the default menu entry

- +

- ----

- # grub2-editenv list

- ----

- 

- . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in link:#adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

- 

- 

- .More information

- 

- If you understand the risks involved, you can manually modify the `/boot/grub2/grub.cfg` file. In that case, set the number of the default operating system using the `set default` variable.

- 

- For example:

- ----

- set default="5"

- ----

- 

- [NOTE]

- ====

- If you edit the configuration file manually, the settings will be overwritten each time the `grub2-mkconfig` command runs.

- ====

@@ -1,33 +0,0 @@ 

- [[setting-password-for-interactive-edit-mode]]

- = Setting a password for interactive edit mode

- 

- If you wish to protect the *GRUB2* interactive edit mode with a password, but allow ordinary users to boot the computer, you have to create a definition file where you set up this functionality: 

- 

- .Procedure

- 

- . Create the `/etc/grub.d/01_users` file and write the following lines into the file.

- +

- ----

- set superusers="root"

- export superusers

- password root <password>

- ----

- 

- . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in xref:adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

- 

- 

- .More information

- 

- You can encrypt the password by using *pbkdf2*. Use `grub2-mkpasswd-pbkdf2` to encrypt the password, then replace the password line with:

- 

- ----

- password_pbkdf2 root grub.pbkdf2.sha512.10000.1B4BD9B60DE889A4C50AA9458C4044CBE129C9607B6231783F7E4E7191D8254C0732F4255178E2677BBE27D03186E44815EEFBAD82737D81C87F5D24313DDDE7.E9AEB53A46A16F30735E2558100D8340049A719474AEEE7E3F44C9C5201E2CA82221DCF2A12C39112A701292BF4AA071EB13E5EC8C8C84CC4B1A83304EA10F74

- ----

- 

- More details can be found at https://help.ubuntu.com/community/Grub2/Passwords[Ubuntu Help: GRUB2 Passwords].

- 

- [NOTE]

- ====

- Starting from Fedora 21, the `--md5pass` kickstart option must be used when using the `grub2-mkpasswd-pbkdf2` command.

- ====

- 

@@ -1,64 +0,0 @@ 

- [#starting-stopping-and-querying-systemd-services]

- = Starting, stopping, and querying systemd services

- 

- You can perform various management tasks to control systemd services using the `systemctl` command. The following is a set of example commands to demonstrate how to use `systemctl` to manage systemd services.

- 

- .Prerequisites

- 

- You are logged in as a user with administrator-level permissions.

- 

- .Procedure

- 

- The following commands control the `foo` service:

- 

- * Activate a service immediately:

- +

- ----

- # systemctl start foo 

- ----

- 

- * Deactivate a service immediately:

- +

- ----

- # systemctl stop foo 

- ----

- 

- * Restart a service:

- +

- ----

- # systemctl restart foo 

- ----

- 

- * Show the status of a service including if it is running or not:

- +

- ----

- # systemctl status foo 

- ----

- 

- * Enable a service to be started on bootup:

- +

- ----

- # systemctl enable foo 

- ----

- 

- * Disable a service to not start during bootup:

- +

- ----

- # systemctl disable foo 

- ----

- 

- * Prevent a service from starting dynamically or even manually unless unmasked:

- +

- ----

- # systemctl mask foo 

- ----

- 

- * Check if a service is already enabled or not:

- +

- ----

- # systemctl is-enabled foo

- ----

- 

- .Related Information

- 

- * Run `man systemctl` for more details.

@@ -1,22 +0,0 @@ 

- // Module included in the following assemblies:

- //

- // firewalld.adoc

- 

- 

- // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

- [id=starting-firewalld-fedora]

- // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

- = Starting firewalld

- 

- Start firewalld, by entering the following commands:

- 

- ----

- $ sudo systemctl unmask firewalld

- $ sudo systemctl start firewalld

- ----

- 

- To make firewalld start automatically at system start:

- 

- ----

- $ sudo systemctl enable firewalld

- ----

@@ -1,29 +0,0 @@ 

- // Module included in the following assemblies:

- //

- //firewalld.adoc

- 

- // Base the file name and the ID on the module title. For example:

- // * file name: doing-procedure-a.adoc

- // * ID: [id='doing-procedure-a']

- // * Title: = Doing procedure A

- 

- // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

- [id=stopping-firewalld-fedora]

- // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

- = Stopping firewalld

- 

- 

- To stop firewalld, enter the following command as root:

- ----

- $ sudo systemctl stop firewalld

- ----

- 

- Prevent firewalld from starting automatically at system start, enter the following command as root:

- ----

- $ sudo systemctl disable firewalld

- ----

- 

- Make sure firewalld is not started by accessing the firewalld D-Bus interface and also if other services require firewalld, enter the following command as root:

- ----

- $ sudo systemctl mask firewalld

- ----

@@ -1,40 +0,0 @@ 

- [[switching-desktop-environments-using-cli]]

- = Switching desktop environments using CLI

- 

- .Before you start

- 

- Install the desired desktop environment as described in <<proc_installing-additional-desktop-enviroments.adoc#installing-desktop-environments,Installing additional desktop environments>>

- 

- Install the [package]`switchdesk` package:

- 

- ----

- # dnf install switchdesk

- ----

- 

- 

- .Procedure

- 

- Pass the selected desktop environment as the only argument to the [command]`switchdesk` command, for example:

- 

- ----

- # switchdesk kde

- ----

- 

- .More information

- 

- See the `switchdesk(1)` man page.

- 

- Alternatively, edit the [filename]`/etc/sysconfig/desktop` file as *root*. This file specifies the desktop for new users and the display manager to run when entering runlevel 5.

- 

- Correct values are:

- 

- `DESKTOP="_<value>_"`, where `_<value>_` is one of the following:

- 

- 1. `GNOME` — Selects the GNOME desktop environment.

- 2. `KDE` — Selects the KDE desktop environment.

- 

- `DISPLAYMANAGER="_<value>_"`, where `_<value>_` is one of the following:

- 

- 1. `GNOME` — Selects the GNOME Display Manager.

- 2. `KDE` — Selects the KDE Display Manager.

- 3. `XDM` — Selects the X Display Manager.

@@ -1,32 +0,0 @@ 

- [[switching-desktop-environments-using-gui]]

- = Switching desktop environments using GUI

- 

- .Before you start

- 

- Install the desired desktop environment as described in link:#installing-desktop-environments[Installing additional desktop environments].

- 

- .Procedure

- 

- To login with a different desktop for a single session:

- 

- . On the login screen, select a user from the list.

- 

- . Click on the Preferences icon right below the password field. A window appears with a list of several different desktop environments.

- 

- . Choose one, and enter password as usual.

- 

- image::switching-desktop-environments-login.png[Login Screen]

- 

- .More information

- 

- . Alternatively, install the [package]`switchdesk` and [package]`switchdesk-gui` packages:

- +

- ----

- # dnf install switchdesk switchdesk-gui

- ----

- +

- . Run the Desktop Switching Tool application.

- 

- . Select the default desktop from the list of available desktop environments, and confirm.

- 

- image::switching-desktop-environments-switchdesk.png[Desktop Switching Tool]

@@ -1,20 +0,0 @@ 

- [[proc_testing-nested-virtualization]]

- = Testing nested virtualization

- 

- . Start the virtual machine.

- . On the virtual machine, run:

- +

- ----

- # dnf group install virtualization

- ----

- +

- . Verify that the virtual machine has virtualization correctly set up:

- +

- ----

- # virt-host-validate

-   QEMU: Checking for hardware virtualization                                 : PASS

-   QEMU: Checking for device /dev/kvm                                         : PASS

-   QEMU: Checking for device /dev/vhost-net                                   : PASS

-   QEMU: Checking for device /dev/net/tun                                     : PASS

-   LXC: Checking for Linux >= 2.6.26                                          : PASS

- ----

@@ -1,60 +0,0 @@ 

- [id='troubleshooting_live_USB']

- = Troubleshooting a live USB

- 

- 

- == livecd-iso-to-disk problems

- 

- Partition isn't marked bootable:: If you get the message `Partition isn't marked bootable!`, you need to mark the partition bootable. To do this, run `parted /dev/sdX`, and use the `toggle N` boot command, where `_X_` is the appropriate letter, and `_N_` is the partition number. For example:

- +

- [option="nowrap"]

- ----

- $ parted /dev/sdb

- GNU Parted 1.8.6

- Using /dev/sdb

- Welcome to GNU Parted! Type 'help' to view a list of commands.

- (parted) print

- Model: Imation Flash Drive (scsi)

- Disk /dev/sdX: 1062MB

- Sector size (logical/physical): 512B/512B

- Partition Table: msdos

- 

- Number  Start   End     Size    Type     File system  Flags

-  1      32.3kB  1062MB  1062MB  primary  fat16

- 

- (parted) toggle 1 boot

- (parted) print

- Model: Imation Flash Drive (scsi)

- Disk /dev/sdX: 1062MB

- Sector size (logical/physical): 512B/512B

- Partition Table: msdos

- 

- Number  Start   End     Size    Type     File system  Flags

-  1      32.3kB  1062MB  1062MB  primary  fat16        boot 

- 

- (parted) quit

- Information: Don't forget to update /etc/fstab, if necessary.

- ----

- 

- Partitions need a filesystem label:: If you get the message `Need to have a filesystem label` or `UUID` for your USB device, you need to label the partition: `dosfslabel /dev/sdX LIVE`.

- 

- Partition has different physical/logical endings:: If you get this message from fdisk, you may need to reformat the flash drive when writing the image, by passing `--format` when writing the stick. 

- 

- MBR appears to be blank:: If your test boot reports a corrupted boot sector, or you get the message `MBR appears to be blank.`, you need to install or reset the master boot record (MBR), by passing `--reset-mbr` when writing the stick.

- 

- livecd-iso-to-disk on other Linux distributions:: `livecd-iso-to-disk` is not meant to be run from a non-Fedora system. Even if it happens to run and write a stick apparently successfully from some other distribution, the stick may well fail to boot. Use of `livecd-iso-to-disk` on any distribution other than Fedora is unsupported and not expected to work: please use an alternative method, such as link:#using-fedora-media-writer[Fedora Media Writer].

- 

- 

- == Testing a USB stick using qemu

- 

- You can test your stick using QEMU.

- 

- [options="nowrap"]

- ----

- # umount /dev/sdX1

- $ qemu -hda /dev/sdX -m 1024 -vga std

- ----

- 

- 

- == Mounting a Live USB filesystem

- 

- You can use the https://github.com/livecd-tools/livecd-tools/blob/master/tools/liveimage-mount[liveimage-mount] script in the https://apps.fedoraproject.org/packages/livecd-tools[livecd-tools] package to mount an attached Live USB device or other LiveOS image, such as an ISO or Live CD. This is convenient when you want to copy in or out some file from the LiveOS filesystem on a Live USB, or just examine the files in a Live ISO or Live CD.

@@ -1,69 +0,0 @@ 

- = Using the GRUB2 boot prompt

- [[using-the-grub-2-boot-prompt]]

- 

- If improperly configured, *GRUB2* may fail to load and subsequently drop

- to a boot prompt. To boot into the system, proceed as follows:

- 

- . Load the XFS and LVM modules

- +

- ----

- insmod xfs

- insmod lvm

- ----

- 

- . List the drives which *GRUB2* sees:

- +

- ----

- grub2> ls

- ----

- 

- . Examine the output to understand the partition table of the `/dev/sda` device. The following example shows a DOS partition table with three partitions:

- +

- ----

- (hd0) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)

- ----

- +

- A GPT partition table of the `/dev/sda` device with four partitions could look like this:

- +

- ----

- (hd0) (hd0,gpt4) (hd0,gpt3)  (hd0,gpt2) (hd0,gpt1)

- ----

- 

- . Probe each partition of the drive and locate your `vmlinuz` and `initramfs` files.

- +

- ----

- ls (hd0,1)/ 

- ----

- +

- The outcome of the previous command will list the files on `/dev/sda1`. The partition that contains the `/boot` directory is the correct one. There you will search for the full names of the `vmlinuz` and `initramfs` files.

- 

- . Set the root partition.

- +

- ----

- grub> set root=(hd0,3)

- ----

- +

- This command tells the bootloader, that the root partition is the third partition on the first drive. This would correspond to the `/dev/sda3` device.

- 

- . Set the desired kernel.

- +

- ----

- grub> linux (hd0,1)/vmlinuz-3.0.0-1.fc16.i686 root=/dev/sda3 rhgb quiet selinux=0 

- # NOTE : add other kernel args if you need them

- # NOTE : change the numbers to match your system

- ----

- 

- . Set the desired `initrd`.

- +

- ----

- grub> initrd (hd0,1)/initramfs-3.0.0-1.fc16.i686.img

- # NOTE : change the numbers to match your system

- ----

- 

- . Boot with the selected settings.

- +

- ----

- grub> boot

- ----

- 

- . To restore the bootloader's functionality, regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in xref:adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

@@ -1,18 +0,0 @@ 

- [[using-old-graphics-modes]]

- = Using old graphics modes in bootloader

- 

- The terminal device is chosen with GRUB_TERMINAL. For more information, see the link:http://www.gnu.org/software/grub/manual/grub.html#Simple-configuration[Grub manual].

- 

- Valid terminal output names depend on the platform, but may include `console` (PC BIOS and EFI consoles), `serial` (serial terminal), `gfxterm` (graphics-mode output), `ofconsole` (Open Firmware console), or `vga_text` (VGA text output, mainly useful with Coreboot).

- 

- The default is to use the platform's native terminal output.

- 

- In Fedora, `gfxterm` is the default options. To get the legacy graphics modes:

- 

- .Procedure

- 

- . Edit the `/etc/default/grub` file.

- 

- . Set the `GRUB_TERMINAL` variable to one of the above mentioned options.

- 

- . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in link:#adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

@@ -1,25 +0,0 @@ 

- [id='proc_using-same-password-for-root-as-user']

- = Using the same password for root as the user account

- 

- If you use a single user desktop, you might find it convenient to configure [command]`sudo`, so you can use the same password to access *root* as you use for your regular account. To do this, select to be added to the Administration group during installation. To do it at later stage, or to add a different user, use the following procedure:

- 

- . Become the *root* user:

- +

- ----

- $ su -

- ----

- +

- . Enter the password for the root account when prompted.

- 

- . To use your regular password for the root access, run:

- +

- [subs=quotes]

- ----

- # usermod _USERNAME_ -a -G groupname

- ----

- +

- Replace `_USERNAME_` with your account name

- 

- . Log off and back on in order to have access to the group. 

- 

- NOTE: When [command]`sudo` prompts you for a password, it expects your user password, not the `root` password.

@@ -1,214 +0,0 @@ 

- [id='Configuring-networking-with-nmcli']

- = Configuring networking with nmcli - quick reference

- 

- [[networkmanager-status]]

- == NetworkManager status

- 

- Display overall status of NetworkManager:

- ----

- $ nmcli general status

- ----

- 

- Display active connections:

- ----

- $ nmcli connection show --active

- ----

- 

- Display all configured connections:

- ----

- $ nmcli connection show configured

- ----

- 

- [[connectdisconnect-to-an-already-configured-connection]]

- == Connect/disconnect to an already configured connection

- 

- Connect to a configured connection by name:

- ----

- $ nmcli connection up id <connection_name>

- ----

- 

- Disconnection by name:

- ----

- $ nmcli connection down id <connection_name>

- ----

- 

- [[wi-fi]]

- == Wi-Fi

- 

- Get Wi-Fi status:

- ----

- $ nmcli radio wifi

- ----

- 

- Turn Wi-Fi on or off:

- ----

- $ nmcli radio wifi _on|off_

- ----

- 

- List available access points (AP) to connect to:

- ----

- $ nmcli device wifi list

- ----

- 

- Refresh the previous list:

- ----

- $ nmcli device wifi rescan

- ----

- 

- Create a new connection to an open AP:

- ----

- $ nmcli device wifi connect <SSID|BSSID>

- ----

- 

- Create a new connection to a password protected AP:

- ----

- $ nmcli device wifi connect <SSID|BSSID> password <password>

- ----

- 

- 

- == Network interfaces

- 

- List available devices and their status:

- ----

- $ nmcli device status

- ----

- 

- Disconnect an interface:

- ----

- $ nmcli device disconnect iface <interface>

- ----

- 

- [[create-or-modify-a-connection]]

- == Create or modify a connection

- 

- To create a new connection using an interactive editor

- ----

- $ nmcli connection edit con-name <name_of_new_connection>

- ----

- 

- To edit an already existing connection using an interactive editor:

- ----

- $ nmcli connection edit <connection_name>

- ----

- 

- [[exampletutorial]]

- === Example/Tutorial

- 

- Create a new connection:

- ----

- $ nmcli connection edit con-name _name of new connection_

- ----

- 

- It asks us to define a connection type:

- ----

- Valid connection types: 802-3-ethernet (ethernet), 802-11-wireless (wifi), wimax, gsm, cdma, infiniband, adsl, bluetooth, vpn, 802-11-olpc-mesh (olpc-mesh), vlan, bond, team, bridge, bond-slave, team-slave, bridge-slave

- Enter connection type:

- ----

- 

- In this example, we use ethernet:

- ----

- Enter connection type: ethernet

- ----

- 

- The following message appears, note that `nmcli>` is a prompt and that it lists the main settings available:

- ----

- ===| nmcli interactive connection editor |===

- 

- Adding a new '802-3-ethernet' connection

- 

- Type 'help' or '?' for available commands.

- Type 'describe [<setting>.<prop>]' for detailed property description.

- 

- You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6

- nmcli>

- ----

- 

- Edit the setting `ipv4`:

- ----

- nmcli> goto ipv4

- ----

- 

- Note that after this our prompt has changed to indicate that we are currently editing the `ipv4` setting:

- ----

- nmcli ipv4>

- ----

- 

- List available properties under the `ipv4` setting and describe the `method` property:

- ----

- nmcli ipv4> describe

- 

- Available properties: method, dns, dns-search, addresses, routes, ignore-auto-routes, ignore-auto-dns, dhcp-client-id, dhcp-send-hostname, dhcp-hostname, never-default, may-fail

- Property name?

- 

- Property name? method

- ----

- 

- Set property `method` to `auto`:

- ----

- nmcli ipv4> set method auto

- ----

- 

- The `ipv4` setting is now finished. Go back to the main level. Enter the following command until the prompt looks like `nmcli>`:

- ----

- nmcli ipv4> back

- ----

- 

- To list the main settings again, use the `goto` command without any arguments. After that, press `Enter` and ignore the error.

- ----

- nmcli> goto

- 

- Available settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6

- Setting name?

- ----

- 

- It is possible to set a value for a property directly from the main level:

- ----

- nmcli> set __setting__.__property__ _value_

- ----

- 

- For example:

- ----

- nmcli> set connection.autoconnect TRUE

- 

- nmcli> set connection.interface-name _interface name this connection is bound to_

- 

- nmcli> set ethernet.cloned-mac-address _Spoofed MAC address_

- ----

- 

- Finally, check the connection details, save and exit:

- ----

- nmcli> print

- 

- nmcli> save

- 

- nmcli> quit

- ----

- 

- [[manually-editing]]

- === Manually editing

- 

- To manually edit an `ifcfg` connection configuration, open or create with a text editor the configuration file of the connection located in `/etc/sysconfig/network-scripts/ifcfg-`.

- 

- A description of most common configuration options is available in the link:http://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html[RHEL6 Deployment Guide].

- 

- To modify a connection password, open with a text editor and edit the file `keys-` located in `/etc/sysconfig/network-scripts/`. The password is stored in plain text. For example:

- ----

- $ cat /etc/sysconfig/network-scripts/keys-__connection name__

- WPA_PSK='password'

- ----

- 

- Or, if using keyfile, simply edit the connection file located inside `/etc/NetworkManager/system-connections/`

- 

- Finally, save the files and to apply changes to an already active connection execute.

- ----

- nmcli connection up id _connection name_

- ----

- 

- [[delete-a-connection-configuration]]

- == Delete a connection configuration

- 

- Delete the connection:

- ----

- nmcli connection delete id <connection_name>

- ----

- Please note that this also deactivates the connection.

@@ -1,31 +0,0 @@ 

- // Module included in the following assemblies:

- //

- // assembly_changing-selinux-states-and-modes.adoc

- 

- [#{context}-Enabling_and_Disabling_SELinux-Dracut-parameters]

- = Changing SELinux Modes at Boot Time

- 

- On boot, you can set several kernel parameters to change the way SELinux runs:

- 

- enforcing=0::  Setting this parameter causes the machine to boot in permissive mode, which is useful when troubleshooting issues. Using permissive mode might be the only option to detect a problem if your file system is too corrupted. Moreover, in permissive mode the system continues to create the labels correctly. The AVC messages that are created in this mode can be different than in enforcing mode. In permissive mode, only the first denial is reported. However, in enforcing mode you might get a denial on reading a directory and an application stops. In permissive mode, you get the same AVC message, but the application continues reading files in the directory and you get an AVC for each denial in addition.

- 

- selinux=0::  This parameter causes the kernel to not load any part of the SELinux infrastructure. The init scripts notice that the system booted with the [option]`selinux=0` parameter and touch the `/.autorelabel` file. This causes the system to automatically relabel the next time you boot with SELinux enabled.

- +

- [IMPORTANT]

- ====

- Using the [option]`selinux=0` parameter is not recommended. To debug your system, prefer using permissive mode.

- ====

- 

- autorelabel=1::  This parameter forces the system to relabel similarly to the following commands:

- +

- ----

- ~]# touch /.autorelabel

- ~]# reboot

- ----

- +

- If the system labeling contains a large amount of errors, you might need to boot in permissive mode in order that the autorelabel succeeds.

- 

- For additional SELinux-related kernel boot parameters, such as [option]`checkreqprot`, see the `kernel-parameters.txt` file. This file is available in the source package of your Linux kernel (.src.rpm). To download the source package containing the currently used kernel:

- ----

- ~]# dnf download --source kernel

- ----

@@ -1,118 +0,0 @@ 

- [#common-service-parameters]

- = Common service parameters

- 

- .Unit Parameters

- 

- This section contains parameters you can use in the `[Unit]` section of a service. These parameters are common to other systemd units.

- 

- This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`.

- 

- Description::

-   A free-form string describing the service. 

- 

- Documentation::

-   A space-separated list of URIs referencing documentation for this service or its configuration. Accepted are only URIs of the following types: `http://`, `https://`, `file:`, `info:`, `man:`. 

- 

- Requires::

-   Configures requirement dependencies on other services. If this service gets activated, the units listed here are activated too. If one of the dependent services fails to activate, systemd does not start this service. This option may be specified more than once or you can specify multiple space-separated units.

- 

- Wants::

-   Similar to `Requires`, except failed units do not have any effect on the service.

- 

- BindsTo::

-   Similar to `Requires`, except stopping the dependent units also stops the service.

- 

- PartOf::

-   Similar to `Requires`, except the stopping and restarting dependent units also stop and restart the service.

- 

- Conflicts::

-   A space-separated list of unit names that, if running, cause the service not to run.

- 

- Before, After::

-   A space-separated list of unit names that configures the ordering of dependencies between services.

- 

- OnFailure::

-   A space-separated list of unit names that are activated when this service enters a failed state.

- 

- .Install Parameters

- 

- This section contains parameters you can use in the `[Install]` section of a service. These parameters are common to other systemd units.

- 

- This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`.

- 

- Alias::

-     A space-separated list of additional names this service shall be installed under. The names listed here must have the same suffix (i.e. type) as the service filename.

- 

- RequiredBy, WantedBy::

-     Defines the service as dependent of another service. This usually define the target to trigger an enabled service to run. These options are analogous to the `Requires` and `Wants` in the `[Units]` section.

- 

- Also::

-     Additional units to install or uninstall when this service is installed or uninstalled.

- 

- .Service Parameters

- 

- This section contains parameters you can use in the `[Service]` section of a service unit. These parameters are specific only to systemd service units.

- 

- This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`.

- 

- Type::

-   Configures the process start-up type for this service service:

- +

- * `simple` - The service starts as the main process. This is the default.

- * `forking` - The service calls forked processes and run as part of the main daemon.

- * `oneshot` - Similar to `simple`, except the process must exits before systemd starts follow-up services.

- * `dbus` - Similar to `simple`, except the daemon acquires a name of the D-Bus bus.

- * `notify` - Similar to `simple`, except the daemon sends a motification message using `sd_notify` or an equivalent call after starting up.

- * `idle` - Similar to `simple`, except the execution of the service is delayed until all active jobs are dispatched.

- 

- RemainAfterExit::

-   A boolean value that specifies whether the service shall be considered active even if all its processes exited. Defaults to no.

- 

- GuessMainPID::

-   A boolean value that specifies whether systemd should guess the main PID of a service if it cannot be determined reliably. This option is ignored unless `Type=forking` is set and `PIDFile` is not set. Defaults to yes.

- 

- PIDFile::

-   An absolute filename pointing to the PID file of this daemon. Use of this option is recommended for services where `Type=forking`. systemd reads the PID of the main process of the daemon after start-up of the service. systemd does not write to the file configured here, although it removes the file after the service has shut down. 

- 

- BusName::

-   A D-Bus bus name to reach this service. This option is mandatory for services where `Type=dbus`.

- 

- ExecStart::

-   The commands and arguments executed when the service starts.

- 

- ExecStartPre, ExecStartPost::

-   Additional commands that are executed before or after the command in `ExecStart`.

- 

- ExecReload::

-   The commands and arguments to execute when the service reloads.

- 

- ExecStop::

-   The commands and arguments to execute when the service stops. 

- 

- ExecStopPost::

-   Additional commands to executed after the service stops.

- 

- RestartSec::

-   The time in seconds to sleep before restarting a service.

- 

- TimeoutStartSec::

-   The time in seconds to wait for the service to start.

- 

- TimeoutStopSec::

-   The time in seconds to wait for the service to stop.

- 

- TimeoutSec::

-   A shorthand for configuring both `TimeoutStartSec` and `TimeoutStopSec` simultaneously. 

- 

- RuntimeMaxSec::

-   A maximum time in seconds for the service to run. Pass `infinity` (the default) to configure no runtime limit.

- 

- Restart::

-   Configures whether to restart the service when the service's process exits, is killed, or reaches a timeout:

- +

- * `no` - The service will not be restarted. This is the default.

- * `on-success` - Restart only when the service process exits cleanly (exit code 0).

- * `on-failure` - Restart only when the service process does not exit cleanly (node-zero exit code).

- * `on-abnormal` - Restart if the process terminates with a signal or when a timeout occurs.

- * `on-abort` - Restart if the process exits due to an uncaught signal not specified as a clean exit status.

- * `always` - Always restart.

@@ -1,37 +0,0 @@ 

- // Module included in the following assemblies:

- //

- // <List assemblies here, each on a new line>

- 

- // Base the file name and the ID on the module title. For example:

- // * file name: help-mkpart.adoc

- // * ID: [id='help-mkpart']

- 

- // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

- [id='help-mkpart_{context}']

- // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

- = Help command for creating a new partition

- 

- To get help on how to make a new partition, type: `help mkpart`.

- 

- ----

- (parted) help mkpart

-   mkpart PART-TYPE [FS-TYPE] START END     make a partition

- 

-         PART-TYPE is one of: primary, logical, extended

-         FS-TYPE is one of: btrfs, nilfs2, ext4, ext3, ext2, fat32, fat16, hfsx, hfs+, hfs, jfs, swsusp,

-         linux-swap(v1), linux-swap(v0), ntfs, reiserfs, hp-ufs, sun-ufs, xfs, apfs2, apfs1, asfs, amufs5,

-         amufs4, amufs3, amufs2, amufs1, amufs0, amufs, affs7, affs6, affs5, affs4, affs3, affs2, affs1,

-         affs0, linux-swap, linux-swap(new), linux-swap(old)

-         START and END are disk locations, such as 4GB or 10%.  Negative values count from the end of the

-         disk.  For example, -1s specifies exactly the last sector.

-        

-         'mkpart' makes a partition without creating a new file system on the partition.  FS-TYPE may be

-         specified to set an appropriate partition ID.

- ----

- 

- [NOTE]

- ====

- * Filesystem type (fstype) will not create an ext4 filesystem on /dev/vdc1. 

- * A DOS partition table's partition types are primary, logical, and extended. 

- * Providing a partition name under GPT is a must. In a GPT partition table, the partition type is used as the partition name.

- ====

@@ -1,58 +0,0 @@ 

- [i='jdk-reference']

- = JDK reference

- 

- See the following list of Java-related acronyms for reference:

- 

- JRE:: Java Runtime Environment; equired to run Java code and applications

- JVM:: Java Virtual Machine; main component of the JRE

- JDK:: Java Development Kit; required only for development, coding

- SDK:: Software Development Kit; see JDK

- JavaWS:: link:https://en.wikipedia.org/wiki/Java_Web_Start[Java Web Start] is a framework to start application from the Internet

- JavaFX:: link:https://en.wikipedia.org/wiki/JavaFX[JavaFX] is a plateform to create and deliver desktop and Rich Internet Apps

- OpenJFX:: is the JavaFX Open Source implementation

- OpenJDK:: Open Source project behind the Java Platform link:http://openjdk.java.net/[openjdk.java.net].

- IcedTea:: is a support project for OpenJDK (concern only developers) link:http://icedtea.classpath.org/[icedtea.classpath.org]

- IcedTea-Web:: is the Java Web Start package (contains only JavaWS, no applets anymore); install to run *JNPL* files

- applets:: are obsolete technology; Not implemented in any recent package

- JSE, J2SE, JEE, ...:: obsolete acronyms for Java Standard & Enterprise Edition; JavaSE is like JRE

- 

- 

- [discrete]

- [id='jdk-components']

- == JDK components

- 

- The JDK has as its primary components a collection of programming tools, including:

- 

- `appletviewer`:: this tool can be used to run and debug Java applets without a web browser

- `apt`:: the annotation-processing tool

- `extcheck`:: a utility which can detect JAR-file conflicts

- `idlj`:: the IDL-to-Java compiler. This utility generates Java bindings from a given Java IDL file.

- `jabswitch`:: the Java Access Bridge. Exposes assistive technologies on Microsoft Windows systems.

- `java`:: the loader for Java applications. This tool is an interpreter and can interpret the class files generated by the javac compiler. Now a single launcher is used for both development and deployment. The old deployment launcher, jre, no longer comes with Sun JDK, and instead it has been replaced by this new java loader.

- `javac`:: the Java compiler, which converts source code into Java bytecode

- `javadoc`:: the documentation generator, which automatically generates documentation from source code comments

- `jar`:: the archiver, which packages related class libraries into a single JAR file. This tool also helps manage JAR files.

- `javafxpackager`:: tool to package and sign JavaFX applications

- `jarsigner`:: the jar signing and verification tool

- `javah`:: the C header and stub generator, used to write native methods

- `javap`:: the class file disassembler

- `javaws`:: the Java Web Start launcher for JNLP applications

- `JConsole`:: Java Monitoring and Management Console

- `jdb`:: the debugger

- `jhat`:: Java Heap Analysis Tool (experimental)

- `jinfo`:: This utility gets configuration information from a running Java process or crash dump. (experimental)

- `jmap`:: This utility outputs the memory map for Java and can print shared object memory maps or heap memory details of a given process or core dump. (experimental)

- `jmc`:: Java Mission Control

- `jps`:: Java Virtual Machine Process Status Tool lists the instrumented HotSpot Java Virtual Machines (JVMs) on the target system. (experimental)

- `jrunscript`:: Java command-line script shell.

- `jstack`:: utility which prints Java stack traces of Java threads (experimental)

- `jstat`:: Java Virtual Machine statistics monitoring tool (experimental)

- `jstatd`:: jstat daemon (experimental)

- `keytool`:: tool for manipulating the keystore

- `pack200`:: JAR compression tool

- `policytool`:: the policy creation and management tool, which can determine policy for a Java runtime, specifying which permissions are

- `available for code from various sources VisualVM`:: visual tool integrating several command-line JDK tools and lightweight clarification needed] performance and memory profiling capabilities

- `wsimport`:: generates portable JAX-WS artifacts for invoking a web service.

- `xjc`:: Part of the Java API for XML Binding (JAXB) API. It accepts an XML schema and generates Java classes.

- 

- The JDK also comes with a complete Java Runtime Environment, usually called a private runtime, due to the fact that it is separated from the "regular" JRE and has extra contents. It consists of a Java Virtual Machine and all of the class libraries present in the production environment, as well as additional libraries only useful to developers, such as the internationalization libraries and the IDL libraries.

@@ -1,103 +0,0 @@ 

- [id='ref_managing-virtual-machines']

- = Managing virtual machines

- 

- When the installation of the guest operating system is complete, it can be managed using the `virt-manager` program or via command line using `virsh`.

- 

- 

- [[managing-guests-with-virt-manager]]

- == Managing guests with virt-manager

- 

- . Start the Virtual Machine Manager by navigating to menu:[Applications]System Tools, or run:

- +

- ----

- # virt-manager

- ----

- +

- If you are not root, you will be prompted to enter the root password. Choose *Run unprivileged* to operate in read-only non-root mode.

- . Choose the host you wish to manage and click *Connect* in the *Open Connection* dialog window.

- . The list of virtual machines is displayed in the main window. Guests that are running will display a ">" icon. Guests that are not running will be greyed out.

- . To manage a particular guest, double click on it, or right click and select *Open*.

- . A new window for the guest will open that will allow you to use its console, see information about its virtual hardware and start, stop, and pause it.

- 

- For further information about `virt-manager`, see http://virt-manager.et.redhat.com/.

- 

- Bugs in the `virt-manager` tool should be reported in http://bugzilla.redhat.com[Bugzilla] against the `virt-manager`

- component.

- 

- 

- [[managing-guests-with-virsh]]

- == Managing guests with virsh

- 

- The `virsh` command-line utility allows you to manage virtual machines on the command line. The `virsh` utility is built around the libvirt management API:

- 

- * `virsh` has a stable set of commands whose syntax and semantics are preserved across updates to the underlying virtualization platform.

- * `virsh` can be used as an unprivileged user for read-only operations (e.g. listing domains, listing domain statistics).

- * `virsh` can manage domains running under Xen, QEMU/KVM, ESX, or other back-ends with no perceptible difference to the user.

- 

- To start a virtual machine:

- 

- ----

- # virsh create <name of virtual machine>

- ----

- 

- To list the virtual machines currently running:

- 

- ----

- # virsh list

- ----

- 

- To list all virtual machines, running or not:

- 

- ----

- # virsh list --all

- ----

- 

- To gracefully power off a guest:

- 

- ----

- # virsh shutdown <virtual machine (name | id | uuid)>

- ----

- 

- To non gracefully power off a guest:

- 

- ----

- # virsh destroy <virtual machine (name | id | uuid)>

- ----

- 

- To save a snapshot of the machine to a file:

- 

- ----

- # virsh save <virtual machine (name | id | uuid)> <filename>

- ----

- 

- To restore a previously saved snapshot:

- 

- ----

- # virsh restore <filename>

- ----

- 

- To export the configuration file of a virtual machine:

- 

- ----

- # virsh dumpxml <virtual machine (name | id | uuid)

- ----

- 

- For a complete list of commands available for use with `virsh`:

- 

- ----

- # virsh help

- ----

- 

- Or consult the manual page: `man virsh`.

- 

- Bugs in the `virsh` tool should be reported in http://bugzilla.redhat.com[Bugzilla] against the *libvirt* component.

- 

- 

- [[remote-management]]

- == Remote management

- 

- The following remote management options are available:

- 

- * If using non-root users via SSH, see the setup instructions in http://wiki.libvirt.org/page/SSHSetup

- * If using root for access via SSH, then create SSH keys for root, and use `ssh-agent` and `ssh-add` before launching `virt-manager`.

- * To use TLS, set up a local certificate authority and issue x509 certs to all servers and clients. For information on configuring this option, see http://wiki.libvirt.org/page/TLSSetup.

@@ -1,31 +0,0 @@ 

- [#mapping-runlevels-to-targets]

- = Mapping runlevels to targets

- 

- systemd targets serve a similar purpose to SysVinit runlevels but act a little different. Each target has a name instead of a number and each serves a specific purpose. systemd implements some targets by inheriting all of the services of another target and adding additional services to it. Some systemd targets mimic the common sysvinit runlevels, which means you can switch targets with the familiar `telinit RUNLEVEL` command. The runlevels assigned a specific purpose on vanilla Fedora installs (0, 1, 3, 5, and 6) have a 1:1 mapping with a specific systemd target.

- 

- However, this is not the case for user-defined runlevels 2 and 4. To make use of those runlevels, create a new named systemd target such as `/etc/systemd/system/$YOURTARGET` that takes one of the existing runlevels as a base, make a directory `/etc/systemd/system/$YOURTARGET.wants`, and then symlink the additional services to enable into that directory.

- 

- The following is a mapping of SysVinit runlevels to systemd targets.

- 

- [cols="2,5,5",options="header"]

- .Runlevel to target mapping

- |===

- |Sysvinit Runlevel |systemd Target |Notes

- 

- |0 |runlevel0.target, poweroff.target |Halt the system.

- 

- |1, s, single |runlevel1.target, rescue.target |Single user mode.

- 

- |2, 4 |runlevel2.target, runlevel4.target, multi-user.target

- |User-defined/Site-specific runlevels. By default, identical to 3.

- 

- |3 |runlevel3.target, multi-user.target |Multi-user, non-graphical.

- Users can usually login via multiple consoles or via the network.

- 

- |5 |runlevel5.target, graphical.target |Multi-user, graphical. Usually

- has all the services of runlevel 3 plus a graphical login.

- 

- |6 |runlevel6.target, reboot.target |Reboot

- 

- |emergency |emergency.target |Emergency shell

- |=== 

\ No newline at end of file

@@ -1,42 +0,0 @@ 

- [#mapping-service-commands]

- = Mapping service commands

- 

- The following table demonstrates the systemd equivalent of SysVinit commands.

- 

- NOTE: All recent versions of systemctl assume the `.service` suffix if left off the service name. For example, `systemctl start frobozz.service` is the same as `systemctl start frobozz`.

- 

- [cols=",,",options="header",]

- |===

- |Sysvinit Command |systemd Command |Notes

- |`service frobozz start`|`systemctl start frobozz`|Used to start a service (not reboot persistent)

- 

- |`service frobozz stop`|`systemctl stop frobozz`|Used to stop a service (not reboot persistent)

- 

- |`service frobozz restart`|`systemctl restart frobozz`|Used to stop and then start a service

- 

- |`service frobozz reload`|`systemctl reload frobozz`|When supported, reloads the config file without interrupting pending operations.

- 

- |`service frobozz condrestart`|`systemctl condrestart frobozz`|Restarts if the service is already running.

- 

- |`service frobozz status`|`systemctl status frobozz`|Tells whether a service is currently running.

- 

- |`ls /etc/rc.d/init.d/`|`systemctl` or `systemctl list-unit-files --type=service` or +

- `ls /lib/systemd/system/*.service /etc/systemd/system/*.service`|Used to list the services that can be started or stopped +

- Used to list all the services and other units

- 

- |`chkconfig frobozz on`|`systemctl enable frobozz`|Turn the service on, for start at next boot, or other trigger.

- 

- |`chkconfig frobozz off`|`systemctl disable frobozz`|Turn the service off for the next reboot, or any other trigger.

- 

- |`chkconfig frobozz`|`systemctl is-enabled frobozz`|Used to check whether a service is configured to start or not in the current environment.

- 

- |`chkconfig --list`|`systemctl list-unit-files --type=service` or `ls /etc/systemd/system/*.wants/`|Print a table of services that lists which runlevels each is configured on or off

- 

- |`chkconfig --list \| grep 5:on`|`systemctl list-dependencies graphical.target`|Print a table of services that will be started when booting into graphical mode

- 

- |`chkconfig frobozz --list`|`ls /etc/systemd/system/*.wants/frobozz.service`|Used to list what levels this service is configured on or off

- 

- |`chkconfig frobozz --add`|`systemctl daemon-reload`|Used when you create a new service file or modify any configuration

- |===

- 

- NOTE: All `/sbin/service` and `/sbin/chkconfig` commands listed in the table continue to work on systemd-based systems and are translated to native equivalents as necessary. The only exception is `chkconfig --list`.

@@ -1,37 +0,0 @@ 

- [[other-virtualization-options]]

- = Other virtualization options

- 

- [[qemukvm-without-libvirt]]

- == QEMU/KVM without libvirt

- 

- QEMU/KVM can be invoked directly without libvirt, however you cannot to use tools such as `virt-manager`, `virt-install`, or `virsh`. Plain QEMU (without KVM) can also virtualize other processor architectures like ARM or PowerPC. 

- 

- [[xen]]

- == Xen

- 

- Fedora can run as a Xen guest operating system and also be used as a Xen host (with the latter being true from Fedora 16; for using an earlier version of Fedora as a Xen host, check out the experimental repo available at http://myoung.fedorapeople.org/dom0). For a guide on how to install and setup a Fedora Xen host, see http://wiki.xen.org/wiki/Fedora_Host_Installation[Fedora Host Installation] page on the Xen Project wiki.

- 

- [[openstack]]

- == OpenStack

- 

- OpenStack consists of a number of services for running infrastructure as a service (IaaS) clouds. They are the Object Store (Swift), Compute (Nova), and Image (Glance) services.

- 

- [[opennebula]]

- == OpenNebula

- 

- OpenNebula is an open source toolkit for data center virtualization.

- 

- [[ovirt]]

- == oVirt

- 

- The https://www.ovirt.org/[oVirt project] is an open virtualization

- project providing a end-to-end, server virtualization

- management system with advanced capabilities for hosts and guests,

- including high availability, live migration, storage management, system

- scheduler, and more.

- 

- [[troubleshooting-and-known-issues]]

- = Troubleshooting and known issues

- 

- For a list of known unresolved issues, as well as troubleshooting tips,

- see FIXME link:How_to_debug_Virtualization_problems[How to debug virtualization problems]

@@ -1,45 +0,0 @@ 

- [[virtio-win-rpm-contents]]

- = RPM contents

- 

- The virtio-win RPM package contains the following files:

- 

- * `/usr/share/virtio-win/*.iso` -  ISO CDROM containing all the drivers. 

- * `/usr/share/virtio-win/*.vfd` - VFD floppy images for using during install of Windows XP

- * `/usr/share/virtio-win/drivers` - Copy of the extracted VFD driver contents

- * `/usr/share/guest-agent/*.msi` - QEMU Guest Agent 32bit and 64bit MSI installers

- 

- [[virtio-win-iso-contents]]

- == ISO contents

- 

- ISO is used to install paravirtual drivers in Windows guests. The `virtio-win/*.iso` included in the RPM  contains the following bits:

- 

- * `NetKVM/` - Virtio network driver

- * `viostor/` - Virtio block driver

- * `vioscsi/`  - Virtio Small Computer System Interface (SCSI) driver

- * `viorng/` - Virtio RNG driver  

- * `vioser/` - Virtio serial driver

- * `Balloon/` - Virtio memory balloon driver

- * `qxl/` - QXL graphics driver for Windows 7 and earlier. (build virtio-win-0.1.103-1 and later)

- * `qxldod/` -  QXL graphics driver for Windows 8 and later. (build virtio-win-0.1.103-2 and later)

- * `pvpanic/` - https://github.com/qemu/qemu/blob/master/docs/specs/pvpanic.txt[QEMU pvpanic] device driver (build virtio-win-0.1.103-2 and later)

- * `guest-agent/` - QEMU Guest Agent 32bit and 64bit MSI installers

- * `qemupciserial/` - https://github.com/qemu/qemu/blob/master/docs/qemupciserial.inf[QEMU PCI

- serial] device driver

- * `*.vfd`  VFD floppy images for using during install of Windows XP

- 

- NOTE: If you previously used isos from alt.fedoraproject.org, note that the current isos have a different file layout that matches the layout of the Red Hat Enterprise Linux isos.   If you need old isos for backwards compatiblity you can find them on the  https://fedorapeople.org/groups/virt/virtio-win/deprecated-isos/[deprecated isos page].

- 

- [[virtio-win-direct-downloads]]

- == Direct downloads

- 

- Direct downloads are available for the `.iso`, `.vfd`, and qemu-ga installers.

- 

- * Stable https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso[virtio-win iso]

- * Stable https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win_x86.vfd[virtio-win x86 floppy]

- * Stable https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win_amd64.vfd[virtio-win amd64 floppy]

- * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso[virtio-win iso]

- * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win_x86.vfd[virtio-win x86 floppy]

- * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win_amd64.vfd[virtio-win amd64 floppy]

- * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-qemu-ga/[gemu-qa files]

- * https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/[Full archive]

- * https://fedorapeople.org/groups/virt/virtio-win/CHANGELOG[Changelog]

file removed
-125
@@ -1,125 +0,0 @@ 

- = OpenH264

- 

- '''

- 

- [IMPORTANT]

- ======

- 

- This page was automatically converted from https://fedoraproject.org/wiki/OpenH264

- 

- It is probably

- 

- * Badly formatted

- * Missing graphics and tables that do not convert well from mediawiki

- * Out-of-date

- * In need of other love

- 

- 

- Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

- 

- Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

- 

- Once the document is live, go to the original wiki page and replace its text

- with the following macro:

- 

- ....

- {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

- ....

- 

- ======

- 

- '''

- 

- 

- This page contains information on the Cisco

- http://www.openh264.org/[OpenH264] codec.

- 

- [[background]]

- Background

- ----------

- 

- Cisco provides an OpenH264 codec (as a source and a binary), which is

- their of implementation H.264 codec, and they cover all licensing fees

- for all parties using their binary. This codec allows you to use H.264

- in WebRTC with gstreamer and Firefox. It does *not* enable generic H.264

- playback, only WebRTC (see Mozilla

- https://bugzilla.mozilla.org/show_bug.cgi?id=1057646[bug 1057646]).

- 

- The code source is available at https://github.com/cisco/openh264 under

- a BSD license. The binary is released under this agreement from Cisco:

- http://www.openh264.org/BINARY_LICENSE.txt

- 

- Upstream Firefox versions download and install the OpenH264 plugin by

- default automatically. Due to it's binary nature, Fedora disables this

- automatic download.

- 

- [[installation-from-fedora-cisco-openh264-repository]]

- Installation from fedora-cisco-openh264 repository

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- A `fedora-cisco-openh264` repository is distributed since Fedora 24 by

- default (if you have at least `fedora-repos-24-0.5` package or newer).

- It contains OpenH264 binary link:Non-distributable-rpms[built inside the

- Fedora infrastructure], but distributed by Cisco, so that the all

- licensing fees are still covered by them. This repository also contains

- OpenH264 plugins for gstreamer and Firefox. It is disabled by default.

- In order to install OpenH264, you first need to enable it:

- 

- ....

- $ sudo dnf config-manager --set-enabled fedora-cisco-openh264

- ....

- 

- and then install the plugins:

- 

- ....

- $ sudo dnf install gstreamer1-plugin-openh264 mozilla-openh264

- ....

- 

- Afterwards you need open Firefox, go to menu -> Add-ons -> Plugins and

- enable OpenH264 plugin.

- 

- You can do a simple test whether your H.264 works in RTC on

- https://mozilla.github.io/webrtc-landing/pc_test.html[this page] (check

- _Require H.264 video_).

- 

- [[manual-install-of-binary]]

- Manual install of binary

- ~~~~~~~~~~~~~~~~~~~~~~~~

- 

- * View and agree to the http://www.openh264.org/BINARY_LICENSE.txt

- * Download the appropriate binary for your system here:

- https://github.com/cisco/openh264/releases

- 

- Example installation for version 1.1:

- 

- `wget `http://ciscobinary.openh264.org/openh264-linux64-v1.1-Firefox33.zip[`http://ciscobinary.openh264.org/openh264-linux64-v1.1-Firefox33.zip`] +

- `mkdir -p ~/.mozilla/firefox/``/gmp-gmpopenh264/1.1/` +

- `cd ~/.mozilla/firefox/``/gmp-gmpopenh264/1.1/` +

- `unzip ~/openh264-linux64-v1.1-Firefox33.zip`

- 

- [[firefox-config-changes]]

- Firefox config changes

- ^^^^^^^^^^^^^^^^^^^^^^

- 

- Type about:config into the Firefox address/URL field and accept the

- warning.

- 

- * From the Search field type in 264 and a handful of options will

- appear. Give the following Preference Names a value of true by

- double-clicking on false:

- 

- ` media.gmp-gmpopenh264.autoupdate` +

- ` media.gmp-gmpopenh264.enabled` +

- ` media.gmp-gmpopenh264.provider.enabled` +

- ` media.peerconnection.video.h264_enabled`

- 

- * Restart Firefox

- * After restarting, the following string in about:config will change to

- the current version that has been installed from the web:

- 

- ` media.gmp-gmpopenh264.version`

- '''

- 

- See a typo, something missing or out of date, or anything else which can be

- improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -1,152 +0,0 @@ 

- = Package management system

- 

- '''

- 

- [IMPORTANT]

- ======

- 

- This page was automatically converted from https://fedoraproject.org/wiki/Package_management_system

- 

- It is probably

- 

- * Badly formatted

- * Missing graphics and tables that do not convert well from mediawiki

- * Out-of-date

- * In need of other love

- 

- 

- Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

- 

- Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

- 

- Once the document is live, go to the original wiki page and replace its text

- with the following macro:

- 

- ....

- {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

- ....

- 

- ======

- 

- '''

- 

- 

- [[package-management-system]]

- Package Management System

- -------------------------

- 

- [[introduction]]

- Introduction

- ~~~~~~~~~~~~

- 

- Fedora is a distribution that uses a package management system. This

- system is based on http://rpm.org[rpm] , the RPM Package Manager, with

- several higher level tools built on top of it, most notably

- https://www.freedesktop.org/software/PackageKit/[PackageKit] (default

- gui) and link:Yum[ yum] (command line tool). As of Fedora 22, yum has

- been replaced by link:Dnf[ dnf]. The Gnome Package Manager is another

- GUI package manager.

- 

- [[advantages-of-package-management-systems]]

- Advantages of package management systems

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- Package management systems have many advantages:

- 

- * It's easy to query what version of a package is installed or

- available.

- 

- * It's easy to remove a package entirely, making sure all its files are

- gone.

- 

- * It's easy to verify the integrity of the packages files, so you can

- see if it's been corrupted or tampered with.

- 

- * It's easy to upgrade a package by installing the new version and

- removing all the old versions files. This will make sure not to leave

- any lingering files from the old package around to confuse or break

- things.

- 

- * It's easy to see what packages require or provide things that other

- packages provide or require, so you can be sure to have the needed items

- for the package to function correctly.

- 

- * It's easy to install or remove groups of packages.

- 

- * In many cases it's possible to downgrade back to a previous version of

- a package, for example when a new version has a bug.

- 

- [[disadvantages-of-package-management-systems]]

- Disadvantages of package management systems

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- * You are restricted to either using the versions of the package that

- are available or having to make your own package if you need a different

- version.

- 

- [[why-mixing-source-installs-and-packages-is-a-bad-idea]]

- Why mixing source installs and packages is a bad idea

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- Package management systems have no way to query or note when you bypass

- them and install something from source. You should avoid mixing source

- installs and packaged installs for (at least) the following reasons:

- 

- * You lose all the advantages above from a package managed system.

- 

- * Installing from source may overwrite, delete, or change existing files

- that are in a package, making that package not function correctly.

- 

- * The source install may override a package install causing undefined

- behavior in the package or source installed item.

- 

- * Installing from source makes it impossible or very difficult for

- anyone to help you debug issues, since versions can't be easily queried

- and integrity checked.

- 

- * Fedora packages may include patches or configuration to work with

- other packages, but upstream source does not, leading to loss of

- functionality.

- 

- * Software installed from source will not upgrade with package managed

- packages, leading to breakage in the source install package on upgrades

- or os updates.

- 

- Strongly consider making your own package if you need a different

- version or a version of some package with changes. See:

- link:How_to_create_an_RPM_package[How to create a RPM package]

- 

- [[preferred-search-order-for-a-software]]

- Preferred search order for a software

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- If some software is missing in your installation then you should try the

- following steps to get the packaged version:

- 

- 1.  Search in Fedora ( 'yum|dnf search foo' or search for 'foo' in the

- PackageKit gui )

- 2.  Try one of the available link:Third_party_repositories[ 3rd party]

- repositories

- 3.  link:How_to_create_an_RPM_package[ Build your own package]

- 

- [[package-management-tools]]

- Package Management tools

- ~~~~~~~~~~~~~~~~~~~~~~~~

- 

- link:Dnf[ dnf] - Dandified Yum

- 

- link:Yum[ yum] - Yellowdog Updater Modified

- 

- https://www.freedesktop.org/software/PackageKit/[PackageKit] -

- PackageKit gui tool ('add/remove software' in your menu)

- 

- http://rpm.org[rpm] - RPM package manager.

- 

- http://ww1.yum-extender.org/[yumex] - Yum Extender.

- 

- Category:Software_Management[Category:Software Management]

- '''

- 

- See a typo, something missing or out of date, or anything else which can be

- improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -1,143 +0,0 @@ 

- = PackageKit Items Not Found

- 

- '''

- 

- [IMPORTANT]

- ======

- 

- This page was automatically converted from https://fedoraproject.org/wiki/PackageKit_Items_Not_Found

- 

- It is probably

- 

- * Badly formatted

- * Missing graphics and tables that do not convert well from mediawiki

- * Out-of-date

- * In need of other love

- 

- 

- Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

- 

- Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

- 

- Once the document is live, go to the original wiki page and replace its text

- with the following macro:

- 

- ....

- {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

- ....

- 

- ======

- 

- '''

- 

- 

- [[missing-package]]

- Missing Package

- ~~~~~~~~~~~~~~~

- 

- Unfortunately, the package you were searching for is not available in

- Fedora. There are a few common reasons why a package might not be in

- Fedora's repositories:

- 

- * Fedora does not include software that is

- link:Package_Not_Found#Patents[ encumbered by software patents].

- * Fedora does not include proprietary software, only software with an

- link:Licensing[ acceptable license].

- * It is possible that no one has packaged it yet. You might consider

- adding it to the link:PackageMaintainers/WishList[Package WishList], or

- even link:PackageMaintainers/Join[packaging it yourself]!

- 

- [[missing-codec]]

- Missing Codec

- ~~~~~~~~~~~~~

- 

- Unfortunately, the codec you were searching for is not available in

- Fedora. A codec is a program that enables encoding and/or decoding of a

- data stream, in a specific format such as MP3, MOV, or WMV.

- 

- There are a few common reasons why a codec might not be in Fedora's

- repositories:

- 

- * Many codecs are proprietary or link:Package_Not_Found#Patents[patent

- encumbered].

- * Some codecs may not be encumbered, but may be under an

- link:Licensing[unacceptable license].

- 

- The Fedora Project FAQ and community sites provide answers to commonly

- asked questions. link:Third_party_repositories[Third party repositories]

- contain a wide variety of software that has not been included in the

- official Fedora software repositories for various reasons. You can find

- additional software using a search engine like

- http://google.com[Google]. We would love to give you more specific

- instructions on enabling additional codecs but our hands are tied up due

- to software patents and legal restrictions around them. We apologize for

- the inconvenience caused by software patents and our legal team is

- working on getting these restrictions removed when it is possible to do

- so. Scroll down more for details on what we are doing and how you can

- help.

- 

- [[missing-driver]]

- Missing Driver

- ~~~~~~~~~~~~~~

- 

- Unfortunately, the driver you were searching for is not available in

- Fedora. There are a few common reasons why a driver might not be in

- Fedora's repositories:

- 

- * Some drivers are proprietary or link:Package_Not_Found#Patents[patent

- encumbered].

- * Some hardware may not be supported under Linux yet, or is not yet in

- the upstream Linux kernel.

- 

- Fedora strongly encourages new drivers to be included in upstream, and

- does not package individual, out-of-tree, kernel drivers.

- 

- The Fedora Project FAQ and the more informal, unofficial

- http://fedorafaq.org[1] provide useful answers on commonly asked

- questions. However, the unofficial site is not associated with or

- supported by the Fedora Project. You can find many interesting things

- using a search engine like http://google.com[Google].

- link:Third_party_repositories[Third party repositories] might contain

- software that has been not been included in the official Fedora software

- repository.

- 

- [[missing-font]]

- Missing Font

- ~~~~~~~~~~~~

- 

- Unfortunately, the font you were searching for is not available in

- Fedora. There are a few common reasons why a font might not be in

- Fedora's repositories:

- 

- * Fedora does not include proprietary fonts, it only uses fonts with an

- link:Licensing/Fonts[ acceptable font license].

- * It is possible that no one has packaged that font yet. You might

- consider adding it to the :Category:Font_wishlist[Font WishList], or

- even link:PackageMaintainers/Join[packaging it yourself]!

- 

- [[missing-mime-support]]

- Missing MIME Support

- ~~~~~~~~~~~~~~~~~~~~

- 

- Unfortunately, there is nothing in Fedora that claims to support the

- MIME type you were searching for. There are a few common reasons why

- Fedora may not have support for a MIME type:

- 

- * Many MIME types are Windows-only. You may be able to use

- http://en.wikipedia.org/wiki/Wine_(software)[Wine] to run a Windows

- program under Linux that supports your MIME type.

- * Some MIME types are only supported by proprietary or

- link:Package_Not_Found#Patents[patent encumbered] software.

- * It is possible that acceptable software to support your MIME type

- exists, but that no one has packaged it yet. You might consider adding

- it to the link:PackageMaintainers/WishList[Package WishList], or even

- link:PackageMaintainers/Join[packaging it yourself]!

- 

- [[fedora-position-on-software-patents]]

- Fedora Position on Software Patents

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- '''

- 

- See a typo, something missing or out of date, or anything else which can be

- improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -1,32 +0,0 @@ 

- [id='performing-administration-tasks-using-sudo']

- = Performing administration tasks using sudo

- 

- How to perform tasks requiring *root* privileges without logging in as *root*.

- 

- include::en-US/modules/con_what-is-sudo.adoc[leveloffset=+1]

- 

- 

- [id='how-to-use-sudo']

- == How to use sudo

- 

- include::en-US/modules/con_using-sudo-assign-admin-privileges.adoc[leveloffset=+2]

- 

- include::en-US/modules/proc_using-same-password-for-root-as-user.adoc[leveloffset=+2]

- 

- include::en-US/modules/con_logging-sudo-commands.adoc[leveloffset=+2]

- 

- 

- [[warning-and-caveats]]

- == Warnings and caveats

- 

- You must use the user account you created following the installation process, at first boot, for daily use and the *root* account only for system administration. Avoid using *root* for any non-administration usage, since the account makes it easy to create security or data risks.

- 

- There are several potential risks to keep in mind when using the [command]`sudo` command. You can avoid them by editing the [filename]`/etc/sudoers` configuration file using [command]`visudo` command.

- 

- include::en-US/modules/con_sudo-timeout.adoc[leveloffset=+2]

- 

- include::en-US/modules/con_using-sudo-access-docker.adoc[leveloffset=+2]

- 

- include::en-US/modules/proc_run-docker-using-sudo.adoc[leveloffset=+2]

- 

- include::en-US/modules/con_using-sudo-without-password.adoc[leveloffset=+2]

@@ -1,29 +0,0 @@ 

- [id='proc_installing-a-RPM-file']

- = Installing an RPM File

- 

- This procedure shows you how to install an RPM file after you have downloaded the file to your desktop. An RPM file contains the required installation packages for a software.

- 

- .Prerequisites

- 

- * You must have administrative permission to install new RPM files on your system. Either root password or sudo access is required.

- 

- .Procedure

- 

- . Open a terminal.

- . Change your working directory to the location of the RPM file. If you have downloaded the RPM file to the `Downloads` directory, enter:

- +

- [subs=quotes]

- ----

- $ cd ~/Downloads

- ----

- +

- . Install the RPM file:

- +

- [subs=quotes]

- ----

- $ sudo rpm -i NAME_OF_RPM.rpm

- ----

- 

- 

- 

- 

@@ -1,23 +0,0 @@ 

- [id='setting-key-shortcut_{context}']

- = Setting a key shortcut to run an application in GNOME

- 

- If you frequently use a certain application, you can set a keyboard shortcut to quickly launch that application on GNOME.

- 

- This example shows how to set a key shortcut to launch the terminal.

- 

- To set a key shortcut to run an application:

- 

- . Navigate to menu:Settings[Keyboard] to open the *Keyboard Shortcuts* list.

- . Click `+` at the bottom of the list to create a new shortcut.

- . Enter the following details in the *Add Custom Shortcut* window:

- * Add a `Name` for your shortcut, for example, `Terminal`.

- * Enter the command that launches the application. For example, `gnome-terminal`.

- . Click *Set Shortcut* to open the *Set Custom Shortcut* window.

- . Type a keyboard shortcut, for example `Ctrl-Alt-T`.

- . Click *Add*.

- 

- Your shortcut appears under *Custom Shortcuts* and is ready to use.

- 

- image:custom_shortcut.png[]

- 

- To edit or remove your shortcut, click the shortcut to open its details.

file removed
-96
@@ -1,96 +0,0 @@ 

- = How to use QEMU

- 

- QEMU is a very flexible virtualization technology however it is quite slow and it is recommended that you understand and evaluate alternative solutions before picking this one.

- Refer to https://fedoraproject.org/wiki/Getting_started_with_virtualization[Getting started with virtualization]

- 

- [[qemu]]

- == QEMU

- 

- QEMU is a generic and open source processor emulator which achieves a good emulation speed by using dynamic translation.

- 

- QEMU has two operating modes:

- 

- * Full system emulation.

- In this mode, QEMU emulates a full system (for example a PC), including a processor and various peripherials.

- It can be used to launch different Operating Systems without rebooting the PC or to debug system code.

- * User mode emulation (Linux host only). In this mode, QEMU can launch Linux processes compiled for one CPU on another CPU.

- 

- [[download]]

- == Download

- 

- QEMU is available on Fedora repository. It can be installed by using https://fedoraproject.org/wiki/dnf[DNF]:

- 

- ....

- $ su -c "dnf install qemu"

- ....

- 

- 

- [[qemu-commands-since-f]]

- == QEMU commands since F?+

- 

- To discover the qemu commands that are installed perform the following:

- 

- ....

- $ ls /usr/bin/qemu-*

- ....

- 

- In the following examples where "qemu" is, substitute your command for executing qemu. E.g.

- 

- ....

- qemu-system-i386

- ....

- 

- or

- 

- ....

- qemu-i386

- ....

- 

- Of course, this does not apply to "qemu-img".

- 

- [[qemu-virtual-machine-installation]]

- == QEMU virtual machine installation

- 

- Create the virtual image for the system:

- 

- ....

- $ qemu-img create fedora.qcow 5G

- ....

- 

- Of course you are not obliged to take 5GB.

- 

- Note: Even if you take 10GB this does NOT mean that the image does really HAVE the size of 10GB. It just means that your new system is limited up to 10GB - if the new system takes only 1,2 GB also the image will only be at 1,2GB.

- 

- Now let's install the OS. Put in the install CD and type into your konsole (all in one line without break):

- 

- ....

- $ qemu -cdrom /dev/cdrom -hda fedora.qcow -boot d -net nic -net user -m 196 -localtime

- ....

- 

- "-user -net" is important to have internet access within your new system.

- "-m 196" is the Set virtual RAM size (megabytes), default is 128 MB, I chose 196.

- 

- The install may take some time. After the install, qemu will try to boot the new OS itself.

- Maybe this may fail (was the case for me) - but don't worry.

- If that happens: just close the qemu window and type the following command into your konsole to launch your new OS:

- 

- ....

- $qemu fedora.qcow -boot c -net nic -net user -m 196 -localtime

- ....

- 

- [[testing-iso-images]]

- == Testing ISO Images

- 

- Type, in the proper directory

- 

- ....

- $ qemu -m 512M -cdrom <isoname>.iso

- ....

- 

- [[debugging]]

- == Debugging

- 

- To get kernel output dumped to a file outside the virtual system, add e.g. "-serial file:/tmp/qemu-output.log" to the qemu command line.

- When booting the virtual system, add "console=ttyS0" to the kernel boot parameters.

- 

- This output is particularly helpful if you are having trouble booting the system, in which case you may also wish to remove "rhgb" and "quiet" from the kernel boot parameters.

file removed
-334
@@ -1,334 +0,0 @@ 

- = Raspberry Pi

- 

- TIP: The Raspberry Pi is now supported in Fedora 25 and later.

- Fedora on the Raspberry Pi is still very new so please report issues to the ARM mailing list or IRC channel.

- 

- == Introduction

- 

- The link:https://www.raspberrypi.org[Raspberry Pi] is a credit card-sized ARM based single board computer (SBC).

- Fedora supports the the Raspberry Pi Model B versions 2 and 3 since Fedora 25 without any requirement of third party kernels or scripts to adjust offical images.

- This documentation describes how to get started, and includes a Frequently Asked Questions (FAQ) section at the end of the document about what is supported and what isn't.

- 

- == Supported Hardware

- 

- We currently only support the Raspberry Pi Model B versions 2 and 3.

- 

- == Prerequisites

- 

- * A Raspberry Pi 2 or 3

- * Good quality SD Card (link:http://elinux.org/RPi_SD_cards[eLinux] hosts a compatibility list)

- * HDMI Monitor or TV, a USB keyboard and mouse

- * A decent power supply. You'll want at least 2A for the RPi2 and 2.5A for the RPi3, link:https://www.raspberrypi.org/help/faqs/#power[details here].

- * Computer running Windows/MacOS/Linux

- * SD card reader

- 

- == Downloading the Fedora ARM image

- 

- Official support for the Raspberry Pi 2/3 is available in Fedora!

- Please read the FAQ for the current status of various features.

- 

- The lastest Fedora ARM images can be downloaded link:https://arm.fedoraproject.org/[here.]

- 

- == Preparing the SD card

- 

- You can quite easily prepare the image on the SD card on Fedora or any Linux distribution, MacOS or Windows.

- The default settings will provide the user interface on a HDMI monitor with keyboard and mouse support. 

- If you wish to have output over a serial console please see the FAQs at the end of this document for more information.

- 

- == Fedora or Other Linux Distributions

- 

- === Use the fedora-arm-installer

- 

- To install arm-image-installer:

- 

- ----

- $ dnf install -y fedora-arm-installer

- ----

- 

- To write the image out use the following:

- 

- ----

- $ sudo arm-image-installer

- ----

- 

- Usage: `$ arm-image-installer <options>`

- 

- ....

-    --image=IMAGE    - xz compressed image file name

-    --target=TARGET  - target board

-    --media=DEVICE   - media device file (/dev/[sdX|mmcblkX])

-    --selinux=ON/OFF - Turn SELinux off/on as needed

-    --norootpass     - Remove the root password

-    -y		    - Assumes yes, will not wait for confirmation

-    --version	    - Display version and exit

-    --resizefs	    - Resize root filesystem to fill media device

-    --addconsole     - Add system console to extlinux.conf

-    --addkey=        - /path/to/ssh-public-key

- ....

- 

- Example: 

- 

- ----

- $ arm-image-installer --image=Fedora-Rawhide.xz --target=Bananapi --media=/dev/mmcblk0

- ----

- 

- For list of supported boards please check SUPPORTED-BOARDS file.

- 

- For the Raspberry Pi 2 use `--target=rpi2` and for the Raspberry Pi 3 use `--target=rpi3`.

- 

- === Manually Configure SD Card

- 

- ----

- $ xzcat Fedora-IMAGE-NAME.raw.xz | sudo dd status=progress bs=4M of=/dev/XXX #Location of your media (will be sdX or mmcblkX depending on hardware)

- ----

- 

- == Microsoft Windows / MacOS

- 

- The Raspberry Pi foundation provides some nice instructions for image copying using a Mac link:https://www.raspberrypi.org/documentation/installation/installing-images/mac.md[here].  

- Simply replace any image file references with the name and path of the image downloaded in the step above.

- 

- == Resizing the Root Partition

- 

- The root partition is shrunk to the smallest size possible to ensure a small download.

- You currently need to resize it manually.

- Ideally we would like this to happen automatically (great community project idea!).

- 

- === Resize Before First Boot

- 

- The easiest way to do this before boot on a Linux system is with gparted:

- 

- ----

- $ gparted /dev/XXX

- ----

- 

- === Resize After initial-setup

- 

- The other mechanism for doing it is once you've booted the Raspberry Pi and completed the initial setup to create accounts.

- 

- * enlarge the 4th partition (this example uses mmcblk0)

- 

- ----

- $ growpart /dev/mmcblk0p4

- ----

- 

- * grow the fileystem to fill the available space

- 

- ----

- $ resize2fs /dev/mmcblk0p4

- ----

- 

- * resize root partition for the server image (which uses xfs)

- 

- ----

- $ xfs_growfs -d /

- ----

- 

- == Booting Fedora on the Raspberry Pi for the First Time

- 

- * Insert the SD card into the Raspberry Pi.

- * Make sure you have a keyboard, mouse, network cable and monitor connected.

- * Power on the Raspberry Pi.

- * You will see Fedora booting and eventually the "Initial setup wizard" will appear.

- * Follow the wizard to set language, timezone and create users.

- * You should be presented with a login prompt or a getting started guide (depending on which Desktop/SPIN you're using).

- 

- == Applying Updates and Installing Software

- 

- There are no special ways or procedures necessary to install or update the software so you just use standard Fedora installation and update mechanisms such as dnf, gnome-software or any of the other GUI update systems as supported in the various desktop environments.

- 

- == Getting Help and Reporting Issues

- 

- So where can you get help if it’s not working? The usual Fedora support forums are:

- 

- * link:https://ask.fedoraproject.org/[Ask Fedora]

- * link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

- * irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

- 

- == Frequently Asked Questions

- 

- === Why do I get a rainbow display when I try and power on my Raspberry Pi?

- 

- There's a number of different reasons you might get rainbow output on the display when you're trying to boot as Raspberry Pi. 

- The three common ones we see are:

- 

- * The power supply isn't strong enough. See the "Prerequisites" section above.

- 

- * There's no OS installed. Check the SD card is properly in place and you've followed the instructions to write out the card.

- 

- * Wrong edition of the Raspberry Pi. If you try and use Fedora on a Raspberry Pi 1 or Zero you'll get this as we don't support ARMv6 SoCs.

- 

- === What desktop environments are supported?

- 

- Both 3D/2D work out of the box and all desktops as shipped in Fedora should work just fine. 

- There is an open source fully accelerated driver for the Video Core IV GPU.

- 

- === Will there be more enhancements to the hardware support?

- 

- Yes. 

- New enhancements will be delivered when, and as soon as, they are ready via the standard Fedora updates mechanism. 

- New, significant features will be blogged about as they arrive either via link:https://fedoramagazine.org/[Fedora Magazine] or the link:http://fedoraplanet.org/[Fedora Planet].

- 

- === What about support for the Raspberry Pi Models A/A+, B/B+ (generation 1), Zero/ZeroW and Compute Module?

- 

- THESE ARE NOT SUPPORTED!!! 

- 

- Fedora doesn't, and NEVER will, support ARMv6 processors. 

- There's been a number of attempts to support these over the years. 

- The current best effort is Pignus based on Fedora 23. 

- More information can be found at link:https://pignus.computer[the Pignus site]. 

- 

- NOTE: Fedora DOES support the Compute Module 3 based on the same SoC as the Raspberry Pi 3, but *as the previous generation Compute Modules are based on ARMv6 archetecture, they are [#.underline]#not supported#*.

- 

- === Will Fedora 24 be supported?

- 

- No. 

- The small team is focused on the Fedora 25 release and rawhide to best focus resources. 

- While possible to do there is reasonably significant amount of work to back port all the fixes that have gone into Fedora 25/rawhide back to stable releases. 

- Fedora 25 is released and is already very stable on the Raspberry Pi.

- 

- === What USB devices are supported on the Raspberry Pi

- 

- You should be able to use most USB-2 compatible devices that are supported in Fedora on other devices. 

- There are some limitations to the USB bus of the Raspberry Pi hardware as link:https://www.raspberrypi.org/documentation/hardware/raspberrypi/usb/README.md[documented here].

- 

- === Is the onboard WiFi and Bluetooth supported on the Raspberry Pi 3?

- 

- ==== Wifi

- 

- Wifi on the Raspberry Pi 3 is supported in Fedora.

- There's a file we can't currently redistribute which you'll need to retrieve. 

- This can be done either post first boot using onboard ethernet or when setting up the SD card. 

- The command needed when running from a Raspberry Pi 3 is as follows:

- 

- ----

- $ sudo curl https://fedora.roving-it.com/brcmfmac43430-sdio.txt -o /lib/firmware/brcm/brcmfmac43430-sdio.txt

- ----

- 

- Once retrieved you just need to reboot and WiFi should be available.

- 

- ==== Bluetooth

- 

- It's currently untested but as it's attached to a serial port and is accessible it might work. 

- It's only been briefly tested but in practice it tends to crash the entire device so is not currently recommended. 

- Those interested can investigate further and potentially provide more information.

- 

- For the brave you can test it with this command:

- 

- ----

- $ hciattach /dev/ttyAMA0 bcm43xx 3000000 noflow -

- ----

- 

- === Does sound work?

- 

- HDMI audio output is included Fedora however the analog port is not yet supported. 

- Audio output via a USB audio interface should also work fine.

- 

- === Does the add-on camera work?

- 

- Not currently. 

- There is still ongoing work to support this upstream and add the appropriated media acceleration support.

- 

- === Does accelerated media decode work?

- 

- No. 

- There's no upstream kernel support and it relies on code from a number of kernel subsystems to be supported.

- 

- === Does HDMI-CEC work?

- 

- Yes. 

- It current is supported using link:http://libcec.pulse-eight.com/[libcec] packaged in Fedora.

- 

- === Is the Raspberry Pi Touch Display supported?

- 

- Work on the official Raspberry Pi Touch Display is ongoing upstream and initial support has landed in the 4.10 kernel, being link:https://github.com/anholt/linux/issues/8[tracked upstream]. 

- Fedora will review any missing pieces for support soon. 

- The touchscreen driver isn't yet released upstream. 

- Support for other displays is not currently planned.

- 

- === Is the composite TV out supported?

- 

- The composite TV out is not currently supported in a stable Fedora release but the core support has landed upstream in the 4.10 kernel. 

- There's some missing enabling patches currently which we will add to the Fedora kernel soon.

- 

- === Are the expansion HATs supported?

- 

- The quick answer here is they are not currently supported.

- 

- The long answer is a lot more complex. 

- Most of the hardware interfaces that are exposed by the 40 pin HAT connector are supported with drivers shipped with Fedora. 

- Drivers for the hardware contained on a lot of the common HATs are also enabled and supported in Fedora. 

- The core means of supporting the HAT add-on boards require the use of device tree overlays. 

- The kernel and the u-boot 2016.09 boot-loader supports the loading over overlays manually. 

- Currently there is no upstream consensus on the means of autoloading these overlays by means of an "overlay manager" (also known as Cape Manager and by numerous other names) by reading the EEPROM ID and loading the appropriate overlay automatically. 

- There's also no consensus on the extensions to the dtc (Device Tree Compiler) to build the binary blob overlays, and no consensus of the exact format of the overlay file. 

- There is now a group of people working to resolve this issue which enable Fedora to better support HATs (Raspberry Pi), Capes (BeagleBone), DIPs (C.H.I.P) and Mezzanine (96boards) before long.

- 

- The first focus HAT to support will be the official Raspberry Pi Sense HAT. 

- This will be documented using the manual process to build and load the overlay to provide access to the onboard devices as a means of demonstrating how this process works for those wishing to use this manual method in the interim. 

- The link to this documentation will be added here once that is complete.

- 

- === Are Device Tree Overlays supported?

- 

- There's basic support for overlays in u-boot and the Linux kernel but an overlay manager isn't yet upstream. 

- 

- === Is GPIO supported?

- 

- GPIO isn't supported well as they need to be mapped with Device Tree overlays. 

- This will be improved in the Fedora 27/28 cycles.

- 

- === Is SPI supported?

- 

- Yes, basic SPI is supported.

- 

- === Is I2C supported?

- 

- Yes, basic I2C is supported.

- 

- === Is there Raspberry Pi 3 aarch64 support?

- 

- Yes! You can download the aarch64 disk images for the Raspberry Pi 3 link:https://archive.fedoraproject.org/pub/fedora-secondary/releases/[here.]

- 

- === How do I use a serial console?

- 

- The serial console is disabled by default on the Raspberry Pi 2 and 3 because it requires the device to run at significantly slower speeds. 

- To wire up the USB to TTL adapter follow link:https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable/connect-the-lead[this guide from Adafruit]. 

- You'll need a 3.3 volt USB to TTL Serial Cable like link:https://www.adafruit.com/product/954[this one from Adafruit].

- To enable the serial console follow the specific steps for the Raspberry Pi 2 or 3 as they both differ slightly:

- 

- ==== Raspberry Pi 2:

- * Insert the micro SD card into a PC

- * On the VFAT partition edit the config.txt file and uncomment the enable_uart line:

- 

- ----

- $ enable_uart=1

- ----

- 

- * On the boot partition edit the extlinux/extlinux.conf file adding `console=tty0 console=ttyAMA0,115200` to the end of the append line so it looks similar to:

- 

- ----

- $ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyAMA0,115200

- ----

- 

- * Safely unmount the micro SD card

- * Insert micro SD into Raspberry Pi, connect serial console, power on

- 

- ==== Raspberry Pi 3:

- * Insert the micro SD card into a PC

- * On the VFAT partition edit the config.txt file and uncomment the enable_uart line:

- 

- ----

- $ enable_uart=1

- ----

-  

- * On the boot partition edit the extlinux/extlinux.conf file adding: `console=tty0 console=ttyS0,115200` to the end of the append line so it looks similar to:

- 

- ----

- $ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyS0,115200

- ----

- 

- * Safely unmount the micro SD card

- * Insert micro SD into Raspberry Pi, connect serial console, power on

- 

- 

- See a typo, something missing or out of date, or anything else which can be improved? 

- Edit this document link:https://pagure.io/fedora-docs/quick-docs[here.]

@@ -1,200 +0,0 @@ 

- [[chap-how-to-reset-a-root-password]]

- = How to Reset the root Password

- 

- Setting up a root password is one of the steps when installing Fedora.

- If you forget, or lose, the root password, there are two common methods to reset it:

- 

- * In Rescue Mode

- 

- * Using a Fedora Live Media (USB/DVD/CD)

- 

- 

- [[sect-how-to-reset-the-password-from-emergency-or-single-user-mode]]

- == How to reset the root password in Rescue Mode

- 

- [NOTE]

- 

- ====

- 

- Changing passwords as root does not prompt for the old password.

- 

- ====

- 

- While booting the system the link:++grub2.html++[GRUB2] menu will be displayed.

- To boot the system into rescue mode using `bash` follow these steps:

- 

- . Use the arrow keys to select the boot entry you want to edit

- 

- . Press *e* to edit that entry

- 

- . Use the arrow keys to go to the line that starts with `linux`, `linux16`, or `linuxefi`

- 

- . Go the the end of that line, add a space then type `rw init=/bin/bash`.

- If your disk is encrypted, you may need to add `plymouth.enable=0`

- 

- . Press *Ctrl-x* or *F10* to boot that entry

- 

- . Run the command:

- +

- [source,bash]

- 

- ----

- 

- passwd

- 

- ----

- +

- It will prompt you to enter the new root password twice.

- 

- . Restore the SELinux context and permissions with:

- +

- [source,bash]

- 

- ----

- 

- touch /.autorelabel

- 

- ----

- 

- +

- 

- [WARNING]

- 

- ====

- 

- If you do not restore the SELinux permissions, the boot process may fail.

- You may have to do a hard-reboot and start back at step 1.

- 

- ====

- 

- . Reboot the machine with:

- +

- [source,bash]

- 

- ----

- 

- /sbin/reboot -f

- 

- ----

- 

- The system may take a while to boot as SELinux will be relabeling its permissions on the filesystem.

- If you see the Plymouth boot screen you can press the `ESC` key on your keyboard to view the SELinux progress.

- Once it is complete, your system is ready and your root password has been successfully changed.

- 

- [[sect-reset-password-using-the-fedora-live-media]]

- == How to reset the root password with a Fedora Live Media

- 

- [NOTE]

- 

- ====

- 

- To download and create a live USB of Fedora Workstation, follow the instructions on the link:++live-usb.html++[Fedora USB Live Media Quick Doc].

- 

- ====

- 

- . Boot the Live installation media and choose `Try Fedora`

- 

- . From the desktop, open a terminal and switch to root using `su` (it won't ask for a password)

- 

- . To view your hard drive device nodes, in the terminal type: `df -H`.

- For this example we will use `/dev/sda1` for the `/boot` partition and `/dev/sda2` for the root `/` partition.

- +

- If you are using LVM partitions, type: `sudo lvscan` and note the `/dev` path of your root partition.

- For this example we will use `/dev/fedora/root`.

- 

- . Create a directory for the mount point (use the `-p` option to create subdirectories):

- +

- [source,bash]

- 

- ----

- 

- mkdir -p /mnt/sysimage/boot

- 

- ----

- 

- . Mount the `/` (root) partition (be sure to use the actual device node or LVM path of your root `/` partition):

- +

- To mount root on a *standard partition* scheme enter:

- +

- [source,bash]

- 

- ----

- 

- mount /dev/sda2 /mnt/sysimage 

- 

- ----

- +

- To mount root on an *LVM partition* scheme enter:

- +

- [source,bash]

- 

- ----

- 

- mount /dev/fedora/root /mnt/sysimage

- 

- ----

- 

- . Continue the process by mounting `/boot`, `proc`, `/dev`, and `/run` with:

- +

- [source,bash]

- 

- ----

- 

- mount /dev/sda1 /mnt/sysimage/boot

- 

- mount -t proc none /mnt/sysimage/proc

- 

- mount -o bind /dev /mnt/sysimage/dev

- 

- mount -o bind /run /mnt/sysimage/run

- 

- ----

- 

- . `chroot` to the mounted root partition with:

- +

- [source,bash]

- 

- ----

- 

- chroot /mnt/sysimage /bin/bash

- 

- ----

- 

- . Change the root password:

- +

- [source,bash]

- 

- ----

- 

- passwd

- 

- ----

- 

- . Exit out of chroot with:

- +

- [source,bash]

- 

- ----

- 

- exit

- 

- ----

- +

- and exit out of the terminal.

- 

- . Reboot your system and boot from the hard drive.

- 

- Congratulations, your root password has been successfully changed.

- 

- [[sect-additional-troubleshooting]]

- == Additional Troubleshooting

- 

- . If you cannot enter rescue mode because you forgot the Firmware/BIOS password here are some options:

- 

- .. Refer to your computer's documentation for instructions on resetting the Firmware/BIOS password in CMOS memory.

- 

- .. Temporarily move the system hard disk to another machine, and follow the procedures above to reset the root password.

- 

- . If you have set a password for your boot loader, refer to link:++creating-and-using-a-live-installation-image.html++[Creating and Using a Live Installation Image].

- 

- . If you want to reset the boot loader password, refer to the instructions on how to link:++https://fedoraproject.org/wiki/Reset_Bootloader_Password++[Reset the Bootloader Password]. 

\ No newline at end of file

@@ -1,24 +0,0 @@ 

- :experimental:

- 

- [id='securing-the-system-by-keeping-it-up-to-date']

- = Securing the system by keeping it up-to-date

- 

- This section explains:

- 

- * Why it is important to update your system regularly (link:#why-it-is-important-keeping-your-system-up-to-date[Why it is important to keep your system up-to-date])

- * How to apply updates manually by using GUI or CLI (link:#manual-updating-using-cli[Manual updating using CLI])

- * How to enable automatic updates (link:#setting-automatic-updates[Setting automatic updates])

- 

- include::en-US/modules/con_why-it-is-important-keeping-your-system-up-to-date.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_manual-updating-using-gui.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_manual-updating-using-cli.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_setting-automatic-updates.adoc[leveloffset=+1]

- 

- 

- [discrete]

- == Additional Resources

- 

- * The https://docs-old.fedoraproject.org/en-US/Fedora/26/html/System_Administrators_Guide/ch-DNF.html[DNF] chapter in the Fedora System Administrator's Guide

@@ -1,12 +0,0 @@ 

- :imagesdir: ./images

- 

- [[switching-desktop-environments]]

- = Switching desktop environments

- 

- Fedora's default desktop environment is GNOME 3 in the Workstation spin, but it is very easy to try any of the many other desktop environments that are available without affecting your current desktop environment.

- 

- include::en-US/modules/proc_installing-additional-desktop-enviroments.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_switching-desktop-enviroments-using-gui.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_switching-desktop-enviroments-using-cli.adoc[leveloffset=+1]

@@ -1,65 +0,0 @@ 

- [id='prod_troubleshooting_selinux']

- = Troubleshooting SELinux

- 

- This document covers the basics of troubleshooting SELinux.

- 

- SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. For example, an SELinux error generated by the Apache web server may appear as `comm="/usr/sbin/httpd"`.

- 

- Each error message includes information on the source context (`scontext`) of that part of your system performing an action, and the target context (`tcontext`), the target of the action. In many cases, the source is a binary and the target a file.

- 

- == Understanding Denials

- When SELinux prevents any software from accessing a particular resource, for example, when *Firefox* is denied access to `/etc/shadow`, it generates a message and logs it in `/var/log/audit/audit.log` or `/var/log/messages` if *audit* service is disabled. If the log contains `avc: denied` that means it is an SELinux policy denial. Note that you would need administrator privileges (root access) on your system to be able to read this log file. An example denial would look like:

- -----

- type=AVC msg=audit(1214965667.121:635): avc:  denied  { unix_read unix_write } for  pid=15524 comm="npviewer.bin"

- key=59918130 scontext=unconfined_u:unconfined_r:nsplugin_t:s0-s0:c0.c1023

- tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s

- -----

- == Using the setroubleshoot utility

- 

- *setroubleshoot* is a utility that parses the messages from SELinux and provides comprehensive help on what it means and possible actions to take. It has both a graphical utility for your desktop and a server side component that can send email alerts. It is installed by default on Fedora. To install it on your system, use the *Software* tool in GUI or enter the following command:

- -----

- $ sudo dnf install setroubleshoot

- -----

- 

- To start the program, run the following command:

- -----

- $ sealert

- -----

- 

- You can find recent alerts in the browser that appears.

- 

- To troubleshoot an error, click the *troubleshoot* button in the SELinux Alert browser. The browser will return available options for resolving the error and commands to run to fix the problem.

- 

- [NOTE]

- ====

- Some troubleshooting events can be resolved by enabling a boolean switch policy. This will allow the activity to procede in the future, regardless of SELinux enforcing policy. It is not recommended to utilize booleans without fully understanding the issue. For more information on booleans, see the link:https://docs-old.fedoraproject.org/en-US/Fedora/25/html/SELinux_Users_and_Administrators_Guide/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html[Booleans] chapter in the SELinux User's and Administrator's Guide.

- ====

- 

- 

- ////

- include::modules/con-troubleshooting-selinux-overview.adoc[leveloffset=+1]

- 

- include::modules/con-troubleshooting-selinux-access-is-denied.adoc[leveloffset=+2]

- 

- include::modules/con_troubleshooting_selinux_top_three_causes_of_problems.adoc[leveloffset=+1]

- 

- include::modules/con_troubleshooting_selinux_fixing_problems.adoc[leveloffset=+1]

- 

- include::modules/con_troubleshooting_selinux_searching_viewing_denials.adoc[leveloffset=+2]

- 

- include::modules/con_troubleshooting_selinux_disabling_permissive_domains.adoc[leveloffset=+2]

- 

- include::modules/con_troubleshooting_selinux_raw_audit_messages.adoc[leveloffset=+1]

- 

- include::modules/con_troubleshooting_selinux_sealert_messages.adoc[leveloffset=+2]

- 

- include::modules/con_troubleshooting_selinux_allowing_access_audit.adoc[leveloffset=+1]

- 

- include::modules/proc_troubleshooting_selinux_allowing_access_audit.adoc[leveloffset=+2]

- ////

- 

- == Additional Resources

- 

-  * link:https://docs-old.fedoraproject.org/en-US/Fedora/25/html/SELinux_Users_and_Administrators_Guide/chap-Security-Enhanced_Linux-Troubleshooting.html[Troubleshooting] in the SELinux User's and Administrator's Guide

- 

-  * link:https://fedorapeople.org/~dwalsh/SELinux/Presentations/selinux_four_things.pdf[Four Key Causes of SELinux Errors]

file removed
-183
@@ -1,183 +0,0 @@ 

- = Using UEFI with QEMU

- 

- '''

- 

- [IMPORTANT]

- ======

- 

- This page was automatically converted from https://fedoraproject.org/wiki/Using_UEFI_with_QEMU

- 

- It is probably

- 

- * Badly formatted

- * Missing graphics and tables that do not convert well from mediawiki

- * Out-of-date

- * In need of other love

- 

- 

- Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

- 

- Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

- 

- Once the document is live, go to the original wiki page and replace its text

- with the following macro:

- 

- ....

- {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

- ....

- 

- ======

- 

- '''

- 

- 

- [[firmware-installation]]

- Firmware installation

- ---------------------

- 

- UEFI for x86 QEMU/KVM VMs is called OVMF (Open Virtual Machine

- Firmware). It comes from EDK2 (EFI Development Kit), which is the UEFI

- reference implementation.

- 

- [[installing-uefi-for-qemu-from-fedora-repos]]

- Installing 'UEFI for QEMU' from Fedora repos

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- Since June 2016, OVMF is available in Fedora repositories. All you need

- to have installed is `edk2-ovmf` RPM. Furthermore, it should be now a

- dependency of the package, so you probably have it installed already.

- This includes firmware for secureboot (`OVMF_CODE.secboot.fd`)

- 

- [[installing-uefi-for-qemu-nightly-builds]]

- Installing 'UEFI for QEMU' nightly builds

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- Gerd Hoffmann, Red Hatter and QEMU developer, has a dnf repo on his

- personal site that provides nightly builds of a whole bunch of QEMU/KVM

- firmware, including EDK2/OVMF.

- 

- Here's how to pull down the nightly builds for x86:

- 

- ` sudo dnf install dnf-plugins-core` +

- ` sudo dnf config-manager --add-repo `http://www.kraxel.org/repos/firmware.repo[`http://www.kraxel.org/repos/firmware.repo`] +

- ` sudo dnf install edk2.git-ovmf-x64`

- 

- Note, these are nightly builds, and may occasionally be broken.

- 

- [[optionally-configure-libvirtd-to-advertise-uefi-support]]

- Optionally Configure libvirtd to advertise UEFI support

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- Libvirt needs to know about UEFI->NVRAM config file mapping, so it can

- advertise it to tools like virt-manager/virt-install. On Fedora 22 and

- later, libvirt packages are configured to look for the nightly build

- paths, so this will work out of the box.

- 

- However, if you want to use custom binaries, you will need to edit the

- nvram variable in /etc/libvirt/qemu.conf and restart libvirtd.

- 

- [[creating-a-vm]]

- Creating a VM

- -------------

- 

- [[virt-manager]]

- virt-manager

- ~~~~~~~~~~~~

- 

- Create a new VM in virt-manager. When you get to the final page of the

- 'New VM' wizard, do the following:

- 

- * Click 'Customize before install', then select 'Finish'

- * On the 'Overview' screen, Change the 'Firmware' field to select the

- 'UEFI x86_64' option.

- * Click 'Begin Installation'

- * The boot screen you'll see should use `linuxefi` commands to boot the

- installer, and you should be able to run `efibootmgr` inside that

- system, to verify that you're running an UEFI OS.

- 

- [[virt-install]]

- virt-install

- ~~~~~~~~~~~~

- 

- Add `--boot uefi` to your `virt-install` command. Example:

- 

- ` sudo virt-install --name f20-uefi \` +

- `   --ram 2048 --disk size=20 \` +

- `   --boot uefi \` +

- `   --location `https://dl.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/os/[`https://dl.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/os/`]

- 

- [[testing-secureboot-in-a-vm]]

- Testing Secureboot in a VM

- --------------------------

- 

- These steps describe how to test Fedora Secureboot support inside a KVM

- VM. The audience here is QA folks that want to test secureboot, and any

- other curious parties. This requires configuring the VM to use UEFI, so

- it builds upon the previous UEFI steps.

- 

- [[run-enrolldefaultkeys.efi]]

- Run EnrollDefaultKeys.efi

- ~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- (Formerly this article recommended the independent utility

- "LockDown_ms.efi".)

- 

- Since OVMF doesn't ship with any SecureBoot keys installed, we need to

- install some to mimic what an MS certified UEFI machine will ship with.

- OVMF now ships with the binaries required to set up a default set of

- keys. The easiest way is to use UefiShell.iso which is available at

- `/usr/share/edk2/ovmf/UefiShell.iso`. Boot your VM with this as the

- CD-ROM image and it should boot into the UEFI shell. At the prompt

- 

- * Shell> fs0:

- * FS0:\> EnrollDefaultKeys.efi

- * FS0:\> reset

- * The VM will restart. Let it boot into Fedora as normal. Log in

- * You should see the string 'Secure boot enabled' in dmesg. Secureboot

- is now enabled for every subsequent boot.

- 

- [[testing-fedora-cddvd-secure-boot-in-a-vm]]

- Testing Fedora CD/DVD Secure Boot in a VM

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- Once you have a secureboot configured VM as described above, it's easy

- to use this to test ISO media secureboot support.

- 

- * Use virt-manager to attach the ISO media to your VM

- * Use virt-manager to change the VM boot settings to boot off the CDROM

- * Start the VM

- * Switch to a terminal inside the VM, verify Secureboot is enabled by

- checking dmesg

- 

- [[notes]]

- Notes

- -----

- 

- [[using-uefi-with-aarch64-vms]]

- Using UEFI with AArch64 VMs

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~

- 

- link:Architectures/ARM/AArch64[Fedora's AArch64 releases] will only run

- on UEFI, so require UEFI inside the VM. However the steps are slightly

- different. See this page for complete documentation:

- https://fedoraproject.org/wiki/Architectures/AArch64/Install_with_QEMU

- 

- [[extra-links]]

- Extra links

- -----------

- 

- * QA:Testcase_Virtualization_UEFI[QA:Testcase Virtualization UEFI]

- * http://www.linux-kvm.org/page/OVMF[KVM wiki OVMF page]

- * https://wiki.ubuntu.com/SecurityTeam/SecureBoot[Ubuntu secureboot

- page]

- * http://en.opensuse.org/openSUSE:UEFI_Secure_boot_using_qemu-kvm[OpenSUSE

- secureboot page]

- * http://www.labbott.name/blog/2016/09/15/secure-ish-boot-with-qemu/[Using

- SecureBoot with QEMU]

- 

- Category:Virtualization Category:QA

- '''

- 

- See a typo, something missing or out of date, or anything else which can be

- improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -1,33 +0,0 @@ 

- :source-highlighter: prettify

- 

- [id='understanding-and-administering-systemd']

- = Understanding and administering systemd

- 

- Learn the basic principles of systemd: how to configure it and use to administer the system.

- 

- include::en-US/modules/con_understanding-systemd.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_starting-stopping-and-querying-systemd-services.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_modifying-existing-systemd-services.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_creating-new-systemd-services.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_converting-sysvinit-services.adoc[leveloffset=+1]

- 

- include::en-US/modules/ref_common-service-parameters.adoc[leveloffset=+1]

- 

- include::en-US/modules/ref_mapping-runlevel-to-targets.adoc[leveloffset=+1]

- 

- include::en-US/modules/ref_mapping-service-commands.adoc[leveloffset=+1]

- 

- 

- [discrete]

- == Additional resources

- 

- * http://www.freedesktop.org/wiki/Software/systemd[Project homepage]

- * http://0pointer.de/blog/projects/ - Lennart's blog has lots of information about systemd. Lennart is the primary systemd developer

- * http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions

- * http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks

- * link:Features/systemd[ Features Fedora 15:systemd]

- * http://fosdem.org/2011/interview/lennart-poettering.html[Interview with the developer]

file removed
-84
@@ -1,84 +0,0 @@ 

- [[ch-Upgrading]]

- = Upgrading to a new release of Fedora

- 

- [IMPORTANT]

- ====

- 

- . Be sure to *back-up your data* before upgrading your Fedora system in the event something breaks and leaves your system unusable.

- . Read the link:++https://fedoraproject.org/wiki/Releases#Current_Supported_Releases++[Release

- Notes] carefully before attempting an upgrade.

- 

- ====

- 

- 

- [[sect-upgrading-to-the-next-fedora-workstation-release]]

- == Upgrading to the next Fedora Workstation release

- 

- As of Fedora Workstation 23, when the next stable release is available a graphical notification will appear similar to the update notifications.

- Clicking this, or running the _Software_ application and going to the _Updates_ pane, will display a simple graphical interface for upgrading the system.

- It will download the upgrade files, then prompt for a reboot to install them, similar to a system update.

- When the upgrade is complete, the system will automatically reboot into the new release.

- 

- image:Upgradef24f25-gs.png[Upgradef24f25-gs.png,title="Upgradef24f25-gs.png",width=640]

- 

- [[sect-upgrading-using-the-dnf-system-upgrade-plugin]]

- == Upgrading using the DNF System Upgrade plugin

- 

- This method is used to upgrade Fedora Workstation from the command-line.

- It is also used to troubleshoot issues with packages preventing the graphical method from upgrading.

- 

- For instructions on upgrading with the DNF system upgrade plugin, refer to the link:++dnf-system-upgrade.html++[DNF System Upgrade Quick Doc].

- 

- [[sect-upgrading-the-fedora-atomic-host-via-rpm-ostree]]

- == Upgrading the Fedora Atomic Host via rpm-ostree

- 

- For instructions on upgrading Fedora Atomic Host installations between Fedora releases, refer to the link:++atomic-host-upgrade.html++[Atomic Host Upgrade Quick Doc].

- 

- [[sect-can-i-upgrade-between-fedora-releases-using-only-dnf]]

- == Can I upgrade between Fedora releases using only DNF?

- 

- Upgrading between Fedora releases without the link:++dnf_system_upgrade.html++[DNF system upgrade plugin] is not tested by the Fedora QA team.

- Any issues using this method are not considered blockers for a release but in practice works for many users.

- 

- [[sect-can-i-update-from-a-pre-release-alpha-beta-or-other-development-snapshot-to-the-final-release]]

- == Can I update from a pre-release (Alpha, Beta, or other development snapshot) to the final release?

- 

- If you are using a pre-release of Fedora, and want to know more about upgrading to the final release, refer to the

- link:++https://fedoraproject.org/wiki/Upgrading_from_pre-release_to_final++[Upgrading from pre-release to final] page.

- This is technically not an 'upgrade' operation, but an update.

- There are some special considerations involved in making sure you stay on the update track you intend to use, which are documented on that page.

- 

- [[sect-how-do-i-upgrade-to-rawhide-and-branched]]

- == How do I upgrade to Rawhide and Branched?

- 

- link:++https://fedoraproject.org/wiki/Releases/Rawhide++[Rawhide] and link:++https://fedoraproject.org/wiki/Releases/Branched++[Branched] are the development releases of Fedora.

- They are suitable for users developing or testing Fedora before public release.

- They are *NOT SUITABLE* for regular day-to-day use unless you are a fairly experienced user, and certainly not suitable for mission-critical use.

- You should read through those pages carefully before deciding to run Branched or Rawhide.

- See the link:++fedora-life-cycle.html++[Fedora Life Cycle Quick Doc] for more information on how the whole Fedora cycle works from Rawhide, to Branched, to the milestone releases (Alpha and Beta), to a 'final' release.

- 

- Upgrading to a Branched release or to Rawhide can be done with the link:++dnf_system_upgrade.html++[DNF system upgrade plugin].

- Carefully read this page as there are some special notes to ensure a successful upgrade.

- 

- [[sect-can-i-upgrade-using-the-fedora-installer-anaconda]]

- == Can I upgrade using the Fedora installer (anaconda)?

- 

- Fedora releases up to Fedora 17 included upgrade functionality in the Fedora installer, anaconda.

- This can be a better choice than a package manager upgrade for some End Of Life (EOL) upgrades.

- If you are attempting to upgrade from Fedora 16 or older, it is highly recommended to upgrade to Fedora 16 and perform an installer upgrade from Fedora 16 to Fedora 17 before upgrading any further.

- 

- To upgrade using the installer, boot the system from a network install or DVD image for the target release, and run through the initial steps of the install process.

- After you select storage devices the installer should offer you the option to upgrade the installed system.

- 

- [IMPORTANT]

- ====

- 

- If your installation is located on a 'specialized' storage device, be sure to configure and select it.

- 

- ====

- 

- [[sect-upgrading-from-end-of-life-releases]]

- == Can I upgrade from an End Of Life (EOL) release?

- 

- Fedora strongly discourages running an end-of-life release on any production system, or any system connected to the public internet.

- For more information, see the link:++dnf_system_upgrade.html++[DNF System Upgrade Quick Doc].

@@ -1,12 +0,0 @@ 

- :experimental:

- //include::en-US/entities.adoc[]

- include::en-US/3rdparty-message.adoc[]

- 

- [id="using_adobe_flash"]

- = Using Adobe Flash

- 

- include::en-US/modules/con_what_is_adobe_flash.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_checking_fedora_version.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_installing_adobe_flash.adoc[leveloffset=+1]

file removed
-97
@@ -1,97 +0,0 @@ 

- [id='sec-Using-AIDE']

- = Checking Integrity With *AIDE*

- 

- Advanced Intrusion Detection Environment (AIDE) is a utility that creates a database of files on the system, and then uses that database to ensure file integrity and detect system intrusions.

- 

- == Installing *AIDE*

- 

- . To install the _aide_ package:

- +

- ----

- $ sudo dnf install aide

- ----

- . To generate an initial database:

- +

- ----

- $ sudo aide --init

- Start timestamp: 2018-07-11 12:35:47 +0200 (AIDE 0.16)

- AIDE initialized database at /var/lib/aide/aide.db.new.gz

- 

- Number of entries:	150666

- 

- ---------------------------------------------------

- The attributes of the (uncompressed) database(s):

- ---------------------------------------------------

- 

- /var/lib/aide/aide.db.new.gz

-   MD5      : 0isjEPsCORFk7laoGGz8tQ==

-   SHA1     : j0aPLakWChM+TAuxfVIpy9nqBOE=

-   RMD160   : nYyyx0AGZj4e5rwcz77afasXFrw=

-   TIGER    : IBVo5A2A4En1kM6zDjD/MnlkN4QWeSOw

-   SHA256   : YveypaI9c5PJNvPSZf8YFfjCMWfGUA8q

-              vyqLpLJWY0E=

-   SHA512   : TiUYmHYflS3A+j17qw5mW78Fn2yXLpCF

-              1LE1/RhiqqtMn1MjkKDrr+3TE+/vWfa4

-              7253cDhNmC6hoFndkS67Xw==

- 

- 

- End timestamp: 2018-07-11 12:37:35 +0200 (run time: 1m 48s)

- ----

- +

- NOTE: In the default configuration, the *aide --init* command checks just a set of directories and files defined in the `/etc/aide.conf` file. To include additional directories or files in the AIDE database, and to change their watched parameters, edit `/etc/aide.conf` accordingly.

- 

- . To start using the database, remove the `.new` substring from the initial database file name:

- +

- ----

- $ sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz

- ----

- 

- . To change the location of the *AIDE* database, edit the `/etc/aide.conf` file and modify the `DBDIR` value. For additional security, store the database, configuration, and the `/usr/sbin/aide` binary file in a secure location such as a read-only media.

- +

- IMPORTANT: To avoid SELinux denials after the AIDE database location change, update your SELinux policy accordingly. See the link:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/[SELinux User's and Administrator's Guide] for more information.

- 

- == Performing Integrity Checks

- 

- To initiate a manual check:

- ----

- $ sudo aide --check

- Start timestamp: 2018-07-11 12:41:20 +0200 (AIDE 0.16)

- AIDE found differences between database and filesystem!!

- 

- Summary:

-   Total number of entries:	150667

-   Added entries:		1

-   Removed entries:		0

-   Changed entries:		2

- 

- ---------------------------------------------------

- Added entries:

- ---------------------------------------------------

- 

- f++++++++++++++++: /etc/cups/subscriptions.conf.O

- ...

- [output truncated]

- ----

- 

- At a minimum, *AIDE* should be configured to run a weekly scan. At most, *AIDE* should be run daily. For example, to schedule a daily execution of AIDE at _04:05_ a.m. using the *cron* command, see the link:https://docs.fedoraproject.org/f27/system-administrators-guide/monitoring-and-automation/Automating_System_Tasks.html[Automating System Tasks] chapter in the System Administration Guide.

- 

- Add the following line to the `/etc/crontab` file:

- ----

-  05 4 * * * root /usr/sbin/aide --check

- ----

- 

- == Updating an *AIDE* Database

- 

- After verifying the changes of your system such as, package updates or configuration files adjustments, update your baseline *AIDE* database:

- ----

- $ sudo aide --update

- ----

- The *aide --update* command creates the `/var/lib/aide/aide.db.new.gz` database file. To start using it for integrity checks, remove the `.new` substring from the file name.

- 

- == Additional Resources

- 

- For additional information on *AIDE*, see the following documentation:

- 

-  - link:https://static.open-scap.org/ssg-guides/ssg-sl7-guide-ospp-rhel7-server.html#xccdf_org.ssgproject.content_group_aide[Guide to the Secure Configuration of Red Hat Enterprise Linux 7 (OpenSCAP Security Guide): Verify Integrity with AIDE]

- 

-  - link:http://aide.sourceforge.net/stable/manual.html[The AIDE manual]

@@ -1,16 +0,0 @@ 

- = How to enable nested virtualization in KVM

- 

- Learn how to run a virtual machine within a virtual machine.

- 

- include::en-US/modules/proc_enabling-nested-virtualization-in-kvm.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_configuring-nested-virtualization-in-virt-manager.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_testing-nested-virtualization.adoc[leveloffset=+1]

- 

- 

- == Additional resources

- 

- * https://bugzilla.redhat.com/show_bug.cgi?id=1055002

- * http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/

- * https://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/

@@ -1,19 +0,0 @@ 

- [[using-shared-system-certificates]]

- = Using Shared System Certificates

- 

- The Shared System Certificates storage enables NSS, GnuTLS, OpenSSL, and Java to share a default source for retrieving system certificate anchors and black list information. By default, the trust store contains the Mozilla CA list, including positive and negative trust. The system allows updating of the core Mozilla CA list or choosing another certificate list.

- 

- include::en-US/modules/con_using-the-system-wide-trust-store.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_adding-new-certificates.adoc[leveloffset=+1]

- 

- include::en-US/modules/proc_managing-trusted-system-certificates.adoc[leveloffset=+1]

- 

- 

- [[shared-system-certificates-additional-resources]]

- == Additional Resources

- 

- For more information, see the following man pages:

- 

- * `update-ca-trust(8)`

- * `trust(1)`

@@ -1,8 +0,0 @@ 

- 

- :md: en-US/modules

- 

- include::{md}/con_viewing-logs.adoc[leveloffset=+1]

- 

- include::{md}/proc_log-files-command-line.adoc[leveloffset=+1]

- 

- include::{md}/proc_log-files-GUI.adoc[leveloffset=+1]

file removed
-185
@@ -1,185 +0,0 @@ 

- = Wine

- 

- 

- 

- http://winehq.org/[Wine] is an open source implementation of the Windows

- API on top of X and OpenGL.

- 

- Wine emulates the Windows runtime environment by translating Windows system calls

- into POSIX-compliant system calls, recreating the directory structure of Windows systems,

- and providing alternative implementations of Windows system libraries,

- system services through https://wiki.winehq.org/Wineserver[wineserver]

- and various other components such as Internet Explorer, the Windows Registry Editor, and msiexec.

- 

- Packages

- ~~~~~~~~

- 

- Fedora's Wine packages are split up to allow for smaller installations.

- The `wine` meta package will bring with it the most important components

- of Wine. Expert users may want to pick specific components from the list

- below:

- 

- [cols=",",]

- |=======================================================================

- |*name* |''' summary '''

- 

- |_wine_ |Meta package

- 

- |_wine-alsa_ |ALSA sound support for wine

- 

- |_wine-arial-fonts_ |Arial fonts provided by wine-staging

- 

- |_wine-capi_ |ISDN support for wine

- 

- |_wine-cms_ |Color Management for wine

- 

- |_wine-common_ |Common wine files and scripts

- 

- |_wine-core_ |Wine core package

- 

- |_wine-courier-fonts_ |Wine Courier font family

- 

- |_wine-desktop_ |Desktop integration features

- 

- |_wine-devel_ |Wine development environment

- 

- |_wine-filesystem_ |Filesystem directories and basic configuration for

- wine

- 

- |_wine-fixedsys-fonts_ |Wine Fixedsys font family

- 

- |_wine-fonts_ |Wine font meta package

- 

- |_wine-ldap_ |LDAP support for wine

- 

- |_wine-marlett-fonts_ |Wine Marlett font family

- 

- |_wine-ms-sans-serif-fonts_ |Wine MS Sans Serif font family

- 

- |_wine-openal_ |OpenAL sound support for wine

- 

- |_wine-opencl_ |OpenCL support for wine

- 

- |_wine-pulseaudio_ |PulseAudio support for wine

- 

- |_wine-small-fonts_ |Wine Small font family

- 

- |_wine-symbol-fonts_ |Wine Symbol font family

- 

- |_wine-systemd_ |systemd configuration for the wine binfmt handler

- 

- |_wine-system-fonts_ |Wine System font family

- 

- |_wine-sysvinit_ |SysV initscript for the wine binfmt handler

- 

- |_wine-tahoma-fonts_ |Wine Tahoma font family

- 

- |_wine-tahoma-fonts-system_ |Wine Tahoma font family system integration

- 

- |_wine-twain_ |Twain (image scanning) support for wine

- 

- |_wine-wingdings-fonts_ |Wine Wingdings font family

- 

- |_wine-wingdings-fonts-system_ |Wine Wingdings font family system

- integration

- |=======================================================================

- 

- Additional documentation is provided via the ''wine-docs '' package.

- 

- [[available-versions]]

- Available versions

- ~~~~~~~~~~~~~~~~~~

- 

- Fedora applies fixes and features from the *wine-staging* project. EPEL

- packages do not use wine-staging patches.

- 

- *Current versions of Wine in Fedora:*

- 

- [cols=",",]

- |=================

- |Fedora 28 |3.4

- |Fedora 27 |3.4

- |Fedora 26 |3.4

- |EPEL 7 |3.0

- |=================

- 

- Newer versions may be available in the corresponding `updates-testing`

- repositories.

- 

- [[testing-versions]]

- Testing Versions

- ~~~~~~~~~~~~~~~~

- 

- [cols=",",]

- |=================

- |Fedora 28 |3.5

- |Fedora 27 |3.5

- |Fedora 26 |3.5

- |=================

- 

- [[bugs-and-problems]]

- Bugs and problems

- ~~~~~~~~~~~~~~~~~

- 

- Before reporting bugs against Wine please make sure your system is fully

- up to date.

- 

- ....

- dnf update

- ....

- 

- Also check if a newer version is available in updates-testing.

- 

- ....

- dnf --enablerepo=updates-testing update wine

- ....

- 

- If you are using the proprietary graphics drivers please remove them

- from your system and try again, as they are known to cause problems.

- 

- When debugging Wine, your goal is to determine if the issue is one of

- _code functionality_ or _packaging in Fedora_.

- 

- Check the http://appdb.winehq.org[Wine Application Database] to see if

- your application is supported, or if there are known issues that match

- yours. Anything that falls into this category is a bug in upstream code

- functionality.

- 

- The next step is to see if the problem persists with a clean ~/.wine

- folder. To try this without losing your old configuration:

- 

- ....

- mv ~/.wine ~/.wine-save

- ....

- 

- Afterwards try to trigger the bug again. Your original wine folder can

- be restored with:

- 

- ....

- rm -fr ~/.wine; mv ~/.wine-save ~/.wine

- ....

- 

- If your application still does not work but has been working in a

- previous version of wine it is probably a regression. Consider filling a

- bug in the upstream https://bugs.wine-staging.com/[Wine-staging bug

- tracking system].

- 

- IMPORTANT: Do not file bugs in the Winehq.org bugzilla unless told to do so.

- 

- 

- If you really think that your bug is Fedora-related, file a bug against

- the Wine component in https://bugzilla.redhat.com[Fedora's bug tracking

- system].

- 

- [[updates-testing]]

- Updates-Testing

- ~~~~~~~~~~~~~~~

- 

- If you use the version of wine in the updates-testing repository then

- please log into https://bodhi.fedoraproject.org/updates/?packages=wine[bodhi] and

- comment on the build, including any problems that may be in the

- packaging, naming, or elsewhere. The build needs positive karma to be

- pushed to the updates repository.

- 

- See a typo, something missing or out of date, or anything else which can be

- improved? Edit this document at https://pagure.io/fedora-docs/quick-docs[Pagure].

file removed
-138
@@ -1,138 +0,0 @@ 

- <!DOCTYPE html>

- <html lang="en">

-   <head>

-     <meta charset="utf-8">

-     <meta http-equiv="X-UA-Compatible" content="IE=edge">

-     <meta name="viewport" content="width=device-width, initial-scale=1">

-     <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->

- 

-     <title>Fedora Quick Docs Website</title>

- 

-     <!-- Bootstrap -->

-     <link rel="stylesheet" href="_stylesheets/asciibinder.css">

-     <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">

-     <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap-theme.min.css">

- 

-     <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->

-     <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->

-     <!--[if lt IE 9]>

-       <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>

-       <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>

-     <![endif]-->

-   </head>

-   <body>

-     <div class="container">

-       <div class="row">

-         <div class="page-header">

-           <img src="_images/fedora.svg" class="img-responsive" />

-         </div>

-       </div>

-       <div class="row">

-         <div class="col-md-8">

-           <h4><strong>Fedora Quick Docs Site</strong></h4>

-           <p>Test Build.</p>

-         </div>

-         <div class="col-md-4">

-           <h5><strong>Fedora Quick Docs</strong></h5>

-           <div class="list-group">

-             <a href="quick-docs/en-US/index.html" class="list-group-item">

-               &nbsp;Documentation

-             </a>

-           </div>

-         </div>

-       </div>

-     </div>

-     <div id="bottom" class="text-muted py-3" >

-         <div class="foot">

-             <div class="container">

-                 <div class="row footerlinks">

-                     <div class="col-sm-3 col-xs-6 widget">

-                         <h3 class="widget-title">About</h3>

-                         <div class="widget-body">

-                             <dl>

-                                 <dd><a href="https://fedoraproject.org/wiki/Overview">About Fedora</a></dd>

-                                 <dd><a href="https://getfedora.org/en/sponsors">Sponsors</a></dd>

-                                 <dd><a href="https://fedoramagazine.org">Fedora Magazine</a></dd>

- 				<dd><a href="https:https://fedoraproject.org/wiki/Legal:Main#Legal">Legal</a></dd>

-                             </dl>

-                             <ul class="list-inline">

-                             <li>

-                                 <a href="https:https://www.facebook.com/TheFedoraProject" class="btn-social btn-outline"><i class="fa fa-fw fa-facebook"></i></a>

-                             </li>

-                             <li>

-                                 <a href="https:https://plus.google.com/112917221531140868607" class="btn-social btn-outline"><i class="fa fa-fw fa-google-plus"></i></a>

-                             </li>

-                             <li>

-                                 <a href="https:https://twitter.com/fedora" class="btn-social btn-outline"><i class="fa fa-fw fa-twitter"></i></a>

-                             </li>

-                         </ul>

-                         </div>

-                     </div>

- 

-                     <div class="col-sm-3 col-xs-6 widget">

-                         <h3 class="widget-title uppercase">Download</h3>

-                         <div class="widget-body">

-                           <dl>

-                             <dd><a href="https://getfedora.org/en/workstation/download">Get Fedora Workstation</a></dd>

-                             <dd><a href="https://getfedora.org/en/server/download">Get Fedora Server</a></dd>

-                             <dd><a href="https://getfedora.org/en/atomic/download">Get Fedora Atomic</a></dd>

-                             <dd><a href="https://spins.fedoraproject.org">Fedora Spins</a></dd>

-                             <dd><a href="https://labs.fedoraproject.org">Fedora Labs</a></dd>

-                             <dd><a href="https://arm.fedoraproject.org">Fedora ARM<span class="sup">&reg;</span></a></dd>

-                             <dd><a href="https://alt.fedoraproject.org/">Alternative Downloads</a></dd>

- 

-                         </dl>

-                         </div>

-                     </div>

- 

-                     <div class="col-sm-3 col-xs-6 widget">

-                         <h3 class="widget-title">Support</h3>

-                         <div class="widget-body">

-                             <dl>

-                                 <dd><a href="https://fedoraproject.org/wiki/Communicating_and_getting_help">Get Help</a></dd>

-                                 <dd><a href="https://ask.fedoraproject.org/">Ask Fedora</a></dd>

-                                 <dd><a href="https://fedoraproject.org/wiki/Common_F${global_variables.release['curr_id']}_bugs">Common Bugs</a></dd>

-                                 <dd><a href="https://developer.fedoraproject.org/">Fedora Developer Portal</a></dd>

-                                 <dd><a href="https://docs.fedoraproject.org/en-US/Fedora/${global_variables.release['curr_id']}/html/Installation_Guide">Installation Guide</a></dd>

-                             </dl>

-                         </div>

-                     </div>

- 

-                     <div class="col-sm-3 col-xs-6 widget">

-                         <h3 class="widget-title">Join</h3>

-                         <div class="widget-body">

-                             <dl>

-                                 <dd><a href="https://fedoraproject.org/wiki/Join">Join Fedora</a></dd>

-                                 <dd><a href="http://fedoraplanet.org">Planet Fedora</a></dd>

-                                 <dd><a href="https://fedoraproject.org/wiki/SIGs">Fedora SIGs</a></dd>

-                                 <dd><a href="https://admin.fedoraproject.org/accounts/">Fedora Account System</a></dd>

-                                 <dd><a href="http://fedoracommunity.org/">Fedora Community</a></dd>

-                             </dl>

-                         </div>

-                     </div>

-                 </div> <!-- /row of widgets -->

- 

-                 <div class="row">

-                     <div class="col-md-2">

-                         <div class="widget-body">

-                             <a href="http://www.redhat.com/"><img class="rh-logo" src="_images/redhat-logo.png" alt="Red Hat Logo" /></a>

-                         </div>

-                     </div>

-                     <div class="col-md-7">

-                         <div class="widget-body">

-                             <p class="sponsor">Fedora is sponsored by Red Hat.</p>

-                             <p class="sponsor"><a href="https://www.redhat.com/en/technologies/linux-platforms/articles/relationship-between-fedora-and-rhel">Learn more about the relationship between Red Hat and Fedora &raquo;</a></p>

-                             <p class="copy">&copy; 2017 Red Hat, Inc. and others. Please send any comments or corrections to the <a href="https://fedorahosted.org/fedora-websites/">websites team</a></p>

-                         </div>

-                     </div>

-                 </div> <!-- /row of widgets -->

- 

-             </div>

-         </div>

-     </div>

-     <!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->

-     <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>

-     <!-- Include all compiled plugins (below), or include individual files as needed -->

-     <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>

-   </body>

- </html>

modules/ROOT/assets/images/Bios_USB_boot.jpg en-US/images/Bios_USB_boot.jpg
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Boxes_new_machine.png en-US/images/Boxes_new_machine.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Customize_resources.png en-US/images/Customize_resources.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/DSC_3217.JPG en-US/anaconda/images/DSC_3217.JPG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Download_os.png en-US/images/Download_os.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Fedora_Live_USB_creator.png en-US/images/Fedora_Live_USB_creator.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/FireWwall_GUI_startup.PNG en-US/images/FireWwall_GUI_startup.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall-tui.PNG en-US/images/Firewall-tui.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_GUI_First_Time_Startup.PNG en-US/images/Firewall_GUI_First_Time_Startup.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_GUI_other_ports.PNG en-US/images/Firewall_GUI_other_ports.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_Custom_Rules.PNG en-US/images/Firewall_TUI_Custom_Rules.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_Custom_Rules_Adding.PNG en-US/images/Firewall_TUI_Custom_Rules_Adding.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_ICMP_Filter.PNG en-US/images/Firewall_TUI_ICMP_Filter.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_Port_Forwarding.PNG en-US/images/Firewall_TUI_Port_Forwarding.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_Port_Forwarding_Adding.PNG en-US/images/Firewall_TUI_Port_Forwarding_Adding.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_Trusted_services.PNG en-US/images/Firewall_TUI_Trusted_services.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_Warning.PNG en-US/images/Firewall_TUI_Warning.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_masquerading.PNG en-US/images/Firewall_TUI_masquerading.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_other_ports.PNG en-US/images/Firewall_TUI_other_ports.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_TUI_trusted_interfaces.PNG en-US/images/Firewall_TUI_trusted_interfaces.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_Wizard.PNG en-US/images/Firewall_Wizard.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_Wizard_2.PNG en-US/images/Firewall_Wizard_2.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_Wizard_3.PNG en-US/images/Firewall_Wizard_3.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_Wizard_4.PNG en-US/images/Firewall_Wizard_4.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Firewall_Wizard_5.PNG en-US/images/Firewall_Wizard_5.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/First_menu_firewall_tui.PNG en-US/images/First_menu_firewall_tui.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Installation_review.png en-US/images/Installation_review.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/No_configuration.PNG en-US/images/No_configuration.PNG
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Properties_USB_size.png en-US/images/Properties_USB_size.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Select_from_boxes_menu.png en-US/images/Select_from_boxes_menu.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Select_from_file.png en-US/images/Select_from_file.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Select_virtual_machine.png en-US/images/Select_virtual_machine.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Setup_machine.png en-US/images/Setup_machine.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Unetbootin_gtk3.png en-US/images/Unetbootin_gtk3.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/Upgradef24f25-gs.png en-US/images/Upgradef24f25-gs.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/custom_shortcut.png en-US/images/custom_shortcut.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/gdm-pick-wayland.png en-US/images/gdm-pick-wayland.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/mediawriter-icon.png en-US/images/mediawriter-icon.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/packages_icon_search.png en-US/images/packages_icon_search.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/packages_icon_software.png en-US/images/packages_icon_software.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/qemu_gtk3.png en-US/images/qemu_gtk3.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-add-empty.png en-US/images/shortcuts-add-empty.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-add-enter.png en-US/images/shortcuts-add-enter.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-add-filled.png en-US/images/shortcuts-add-filled.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-add-shortcut.png en-US/images/shortcuts-add-shortcut.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-added.png en-US/images/shortcuts-added.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-disabled.png en-US/images/shortcuts-disabled.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-edit.png en-US/images/shortcuts-edit.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-enabling-entered.png en-US/images/shortcuts-enabling-entered.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-enabling-entering.png en-US/images/shortcuts-enabling-entering.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-keyboard-scroll.png en-US/images/shortcuts-keyboard-scroll.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-list-disabled.png en-US/images/shortcuts-list-disabled.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/shortcuts-settings-devices.png en-US/images/shortcuts-settings-devices.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/software-updates.png en-US/images/software-updates.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/switching-desktop-environments-login.png en-US/images/switching-desktop-environments-login.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/switching-desktop-environments-switchdesk.png en-US/images/switching-desktop-environments-switchdesk.png
file renamed
file was moved with no change to the file
modules/ROOT/assets/images/system-config-kickstart.png en-US/images/system-config-kickstart.png
file renamed
file was moved with no change to the file
@@ -0,0 +1,75 @@ 

+ * xref:howto-file-a-bug.adoc[How to file a bug]

+ * xref:using-aide.adoc[Checking integrity with AIDE]

+ * xref:anaconda/anaconda.adoc[Anaconda]

+ ** xref:anaconda/anaconda_distros.adoc[Anaconda-based Distributions]

+ ** xref:anaconda/anaconda_updates.adoc[Anaconda Updates]

+ ** xref:anaconda/anaconda_logging.adoc[Anaconda Logging]

+ ** xref:anaconda/anaconda_product_image.adoc[Anaconda Product Image]

+ * xref:getting-started-with-apache-http-server.adoc[Getting started with Apache HTTP Server]

+ * xref:finding-and-installing-linux-applications.adoc[Finding and installing Linux applications]

+ * xref:installing-chromium-or-google-chrome-browsers.adoc[Installing Chromium or Google Chrome browsers]

+ * xref:switching-desktop-environments.adoc[Switching desktop environments]

+ * xref:fedora-and-red-hat-enterprise-linux.adoc[Difference between Fedora and Red Hat Enterprise Linux]

+ * xref:dnf.adoc[Using the DNF software package manager]

+ * xref:dnf-system-upgrade.adoc[Upgrading Fedora using the DNF system upgrade]

+ * xref:securing-the-system-by-keeping-it-up-to-date.adoc[Securing the system by keeping it up-to-date]

+ * xref:upgrading.adoc[Upgrading to a new release of Fedora]

+ * xref:firewalld.adoc[Controlling network traffic with firewalld]

+ * xref:using-adobe-flash.adoc[Using Adobe Flash]

+ * xref:adding-new-fonts-fedora.adoc[Adding new fonts in Fedora]

+ * xref:create-gpg-keys.adoc[Creating GPG Keys]

+ * xref:bootloading-with-grub2.adoc[Bootloading with GRUB2]

+ * xref:creating-and-using-a-live-installation-image.adoc[Creating and using a live installation image]

+ * xref:installing-java.adoc[Installing Java]

+ * xref:kernel/overview.adoc[Kernel]

+ ** xref:kernel/troubleshooting.adoc[Troubleshooting]

+ ** xref:kernel/build-custom-kernel.adoc[Building a Custom Kernel]

+ * xref:managing-keyboard-shortcuts-for-running-app-in-gnome.adoc[Managing keyboard shortcuts for running an application in GNOME]

+ * xref:proc_setting-key-shortcut.adoc[Setting a key shortcut to run an application in GNOME]

+ * xref:disabling-automatic-screenlock.adoc[Disabling the GNOME automatic screen locking]

+ * xref:viewing-logs.adoc[Viewing logs in Fedora]

+ * xref:encrypting-drives-using-LUKS.adoc[Encrypting drives using LUKS]

+ * xref:assembly_installing-plugins-for-playing-movies-and-music.adoc[Installing plugins for playing movies and music]

+ * xref:installing-and-running-vlc.adoc[Installing and running the VLC player]

+ * xref:configuring-ip-networking-with-nmcli.adoc[Configuring networking with NetworkManager CLI (nmcli)]

+ * xref:creating-a-disk-partition-in-linux.adoc[Creating disk partitions]

+ * xref:bumblebee.adoc[NVIDIA Optimus Bumblebee]

+ * xref:raspberry-pi.adoc[Fedora on Raspberry Pi]

+ * xref:repositories.adoc[Fedora Repositories]

+ * xref:adding-or-removing-software-repositories-in-fedora.adoc[Adding or removing software repositories in Fedora]

+ * xref:reset-root-password.adoc[Resetting a root password]

+ * xref:proc_installing-RPM.adoc[Installing an RPM File]

+ * xref:creating-rpm-packages.adoc[Creating RPM packages]

+ * xref:create-hello-world-rpm.adoc[Creating a GNU Hello World RPM Package]

+ * xref:getting-started-with-selinux.adoc[Getting started using SELinux]

+ * xref:changing-selinux-states-and-modes.adoc[Changing SELinux states and modes]

+ * xref:troubleshooting_selinux.adoc[Troubleshooting SELinux]

+ * xref:using-shared-system-certificates.adoc[Using shared system certificates]

+ * xref:installing-software-from-source.adoc[Installing software from source code]

+ * xref:installing-spotify.adoc[Installing Spotify on Fedora]

+ * xref:adding_user_to_sudoers_file.adoc[Adding a user to sudoers]

+ * xref:performing-administration-tasks-using-sudo.adoc[Performing administration tasks using sudo]

+ * xref:understanding-and-administering-systemd.adoc[Understanding and administering systemd]

+ * xref:displaying_user_prompt_on_gnome_login_screen.adoc[Displaying a user prompt on the GNOME login screen]

+ * xref:installing-virtual-systems-with-gnome-boxes.adoc[Installing virtual operating systems with GNOME Boxes]

+ * xref:qemu.adoc[Using virtualization emulation in QEMU]

+ * xref:getting-started-with-virtualization.adoc[Getting started with virtualization (libvirt)]

+ * xref:using-nested-virtualization-in-kvm.adoc[Using nested virtualization in KVM]

+ * xref:creating-windows-virtual-machines-using-virtio-drivers.adoc[Creating Windows virtual machines using virtIO drivers]

+ * xref:wine.adoc[Running Windows applications with Wine]

+ * xref:configuring-x-window-system-using-the-xorg-conf-file.adoc[Configuring X Window System using the xorg.conf file]

+ * xref:configuring-xorg-as-default-gnome-session.adoc[Configuring X.org as the default GNOME session]

+ //FIXME * xref:autoupdates.adoc[AutoUpdates]

+ //FIXME * xref:debug-dracut-problems.adoc[How to debug Dracut problems]

+ //FIXME * xref:debug-systemd-problems.adoc[How to debug systemd problems]

+ //FIXME * xref:debug-wayland-problems.adoc[How to debug Wayland problems] - note: maintained on wiki, does not fit quick-docs IMHO

+ //FIXME * xref:fedora-life-cycle.adoc[Fedora Release Life Cycle] - note: maintained on wiki, does not fit quick-docs IMHO

+ //FIXME * xref:edit-iptables-rules.adoc[How to edit iptables rules]

+ //FIXME * xref:enable-touchpad-click.adoc[How to enable touchpad click]

+ //FIXME * xref:mirroring.adoc[Mirroring]

+ //FIXME * xref:openh264.adoc[OpenH264]

+ //FIXME * xref:package-management.adoc[Package management system]

+ //FIXME * xref:packagekit-not-found.adoc[PackageKit Items Not Found]

+ //FIXME * xref:postgresql.adoc[PostgreSQL]

+ //FIXME * xref:uefi-with-qemu.adoc[Using UEFI with QEMU]

+ //FIXME * xref:upgrading-fedora-online.adoc[Upgrading Fedora using package manager]

file renamed
+1 -1
@@ -3,7 +3,7 @@ 

  This message needs to be included on any document referencing third party software

  repositories. Add the following line verbatim to the top of any such document:

  

- include::en-US/3rdparty-message.adoc[]

+ include::{partialsdir}/3rdparty-message.adoc[]

  

  Please do not change this message without consultation. Thanks!

  

modules/ROOT/pages/_partials/TODO_virtio-win.adoc en-US/modules/TODO_virtio-win.adoc
file renamed
file was moved with no change to the file
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_Getting-started-with-nmcli.adoc en-US/modules/con_Getting-started-with-nmcli.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_Understanding-the-nmcli-options.adoc en-US/modules/con_Understanding-the-nmcli-options.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_about-java.adoc en-US/modules/con_about-java.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_benefits-of-selinux.adoc en-US/modules/con_benefits-of-selinux.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_block-device-encryption.adoc en-US/modules/con_block-device-encryption.adoc
file renamed
+1 -2
@@ -1,5 +1,4 @@ 

  [id='con_block-device-encryption_{context}']

- == Block device encryption

+ = Block device encryption

  

  Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication. This provides additional security beyond existing operating system security mechanisms as it protects the device's contents even if it has been physically removed from the system. 

- 

modules/ROOT/pages/_partials/con_controlling_ports_firewalld.adoc en-US/modules/con_controlling_ports_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_disk-partition-linux.adoc en-US/modules/con_disk-partition-linux.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_firewalld.adoc en-US/modules/con_firewalld.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,24 @@ 

+ [id='con_introduction-to-luks_{context}']

+ = Introduction to LUKS

+ 

+ Linux Unified Key Setup (LUKS) is a specification for block device encryption.  It establishes an on-disk format for the data, as well as a `passphrase/key` management policy.

+ 

+ LUKS uses the kernel device mapper subsystem with the `dm-crypt` module. This arrangement provides a low-level mapping that handles encryption and decryption of the device data. You can use the `cryptsetup` utility to perform user-level operations such as creating and accessing encrypted devices.

+ 

+ What LUKS does::  {blank}

+ +

+ ** LUKS encrypts entire block devices and is therefore well-suited for protecting the contents of mobile devices such as removable storage media or laptop disk drives.

+ +

+ ** The underlying contents of the encrypted block device are arbitrary. This makes it useful for encrypting [command]`swap` devices. This can also be useful with certain databases that use specially formatted block devices for data storage.

+ +

+ ** LUKS uses the existing device mapper kernel subsystem.

+ +

+ ** LUKS provides passphrase strengthening which protects against dictionary attacks.

+ +

+ ** LUKS devices contain multiple key slots, allowing users to add backup keys or passphrases.

+ 

+ What LUKS does *not* do::  {blank}

+ +

+ ** LUKS is not well-suited for applications requiring more than eight users to have distinct access keys to the same device.

+ +

+ ** LUKS is not well-suited for applications requiring file-level encryption.

modules/ROOT/pages/_partials/con_introduction-to-selinux.adoc en-US/modules/con_introduction-to-selinux.adoc
file renamed
+1 -1
@@ -24,7 +24,7 @@ 

  

  [#fig-intro-httpd-mysqld]

  .SELinux allows the Apache process running as httpd_t to access the /var/www/html/ directory and it denies the same process to access the /data/mysql/ directory because there is no allow rule for the httpd_t and mysqld_db_t type contexts). On the other hand, the MariaDB process running as mysqld_t is able to access the /data/mysql/ directory and SELinux also correctly denies the process with the mysqld_t type to access the /var/www/html/ directory labeled as httpd_sys_content_t.

- image::../images/selinux-intro-apache-mariadb.png[SELinux_Apache_MariaDB_example]

+ image::selinux-intro-apache-mariadb.png[SELinux_Apache_MariaDB_example]

  

  [discrete]

  == Additional resources

modules/ROOT/pages/_partials/con_logging-sudo-commands.adoc en-US/modules/con_logging-sudo-commands.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_package-management-in-fedora.adoc en-US/modules/con_package-management-in-fedora.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_permanent-changes-in-selinux-states-and-modes.adoc en-US/modules/con_permanent-changes-in-selinux-states-and-modes.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc en-US/modules/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_rpm_packaging_overview.adoc en-US/modules/con_rpm_packaging_overview.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_rpm_spec_file_overview.adoc en-US/modules/con_rpm_spec_file_overview.adoc
file renamed
+6 -6
@@ -3,7 +3,7 @@ 

  

  Use this guide for information about the specific macros in a `.spec` file.

  

- NOTE: You can use the macros `%{name}`, `%{version}` and `%{release}` to refer to the Name, Version and Release tags respectively. When you change the tag, the macros automatically update to use the new value.

+ NOTE: You can use the macros `%\{name}`, `%\{version}` and `%\{release}` to refer to the Name, Version and Release tags respectively. When you change the tag, the macros automatically update to use the new value.

  

  `Name`::

  Add the base name of the package, which must match the `.spec` file name. Follow the http://fedoraproject.org/wiki/Packaging:Naming[Package Naming Guidelines] and write the file name in lower-case letters. 
@@ -12,7 +12,7 @@ 

  Add the upstream version number. See http://fedoraproject.org/wiki/Packaging:Versioning[Package Versioning]. If the version contains tags that are non-numeric, you might need to include the non-numeric characters in the `Release` tag. If upstream uses full dates to distinguish versions, consider using version numbers of the form. For example, `yy.mm[dd]` where `2008-05-01` becomes `8.05`.

  

  `Release`::

- Set the initial value to `1%{?dist}`. Increment the number every time you release a new package for the same version of software. When a new upstream version is released, change the `Version` tag to match and reset the `Release` number to `1`. For more information, see the http://fedoraproject.org/wiki/Packaging:Versioning[Versioning Guide] of the packaging guidelines. 

+ Set the initial value to `1%\{?dist}`. Increment the number every time you release a new package for the same version of software. When a new upstream version is released, change the `Version` tag to match and reset the `Release` number to `1`. For more information, see the http://fedoraproject.org/wiki/Packaging:Versioning[Versioning Guide] of the packaging guidelines. 

  

  `Summary`::

  Enter a brief, one-line summary of the package. Use American English. Do not end with a period.
@@ -34,7 +34,7 @@ 

  `Source0`::

  Enter the full URL for the compressed archive that contains the original, pristine source code, as upstream released it. "`Source`" is synonymous with "`Source0`".

  +

- The full URL basename is used when looking in the `SOURCES` directory. If possible, embed `%{name}` and `%{version}`, so that changes to the  go to the right place. Preserve the timestamps when downloading source files. For more information, see http://fedoraproject.org/wiki/Packaging:Guidelines#Timestamps[Preserve timestamps].

+ The full URL basename is used when looking in the `SOURCES` directory. If possible, embed `%\{name}` and `%\{version}`, so that changes to the  go to the right place. Preserve the timestamps when downloading source files. For more information, see http://fedoraproject.org/wiki/Packaging:Guidelines#Timestamps[Preserve timestamps].

  +

  If there is more than one source, name them `Source1`, `Source2`.

  +
@@ -47,7 +47,7 @@ 

  If you package files that are architecture-independent, for example shell scripts, data files, then add `BuildArch: noarch`. The architecture for the binary RPM is then `noarch`.

  

  `BuildRoot`::

- This is now redundant in Fedora and is only needed for EPEL5. By default, the build root is placed in `%{_topdir}/BUILDROOT/`.

+ This is now redundant in Fedora and is only needed for EPEL5. By default, the build root is placed in `%\{_topdir}/BUILDROOT/`.

  +

  In EPEL5, this is where files are installed during the %install process (after the %build process). 

  
@@ -75,13 +75,13 @@ 

  Add script commands to compile the program and get it ready for installing. The program must come with instructions on how to do this.

  

  `%install`::

- Add script commands to "install" the program. The commands must copy the files from the `BUILD` directory `%{_builddir}` into the buildroot directory, `%{buildroot}`. 

+ Add script commands to "install" the program. The commands must copy the files from the `BUILD` directory `%\{_builddir}` into the buildroot directory, `%\{buildroot}`. 

  

  `%check`::

  Add script commands to "test" the program. This is run after the `%install` procedure, so place it there if you have this section. Often it contains `make test` or `make check`. This is separated from `%build` so that people can skip the self-test if they desire.

  

  `%clean`::

- Note that this section is now redundant in Fedora and is only necessary for EPEL. Typically this contains only the following command: `rm -rf %{buildroot}`.

+ Note that this section is now redundant in Fedora and is only necessary for EPEL. Typically this contains only the following command: `rm -rf %\{buildroot}`.

  

  `%files`::

  Add the list of files to be installed. 

modules/ROOT/pages/_partials/con_runtime_and_permanent_firewalld.adoc en-US/modules/con_runtime_and_permanent_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_selinux-architecture.adoc en-US/modules/con_selinux-architecture.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_selinux-examples.adoc en-US/modules/con_selinux-examples.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_selinux-states-and-modes.adoc en-US/modules/con_selinux-states-and-modes.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_sudo-timeout.adoc en-US/modules/con_sudo-timeout.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_the-purpose-of-rpm-fusion.adoc en-US/modules/con_the-purpose-of-rpm-fusion.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_understanding-systemd.adoc en-US/modules/con_understanding-systemd.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_using-sudo-access-docker.adoc en-US/modules/con_using-sudo-access-docker.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_using-sudo-assign-admin-privileges.adoc en-US/modules/con_using-sudo-assign-admin-privileges.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_using-sudo-without-password.adoc en-US/modules/con_using-sudo-without-password.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_using-the-system-wide-trust-store.adoc en-US/modules/con_using-the-system-wide-trust-store.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_viewing-logs.adoc en-US/modules/con_viewing-logs.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_what-is-sudo.adoc en-US/modules/con_what-is-sudo.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_what_is_adobe_flash.adoc en-US/modules/con_what_is_adobe_flash.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_why-it-is-important-keeping-your-system-up-to-date.adoc en-US/modules/con_why-it-is-important-keeping-your-system-up-to-date.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/con_xorg-conf.adoc en-US/modules/con_xorg-conf.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/concept_chromium-web-browser.adoc en-US/modules/concept_chromium-web-browser.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/concept_fedora-virtio-drivers-vs-rhel.adoc en-US/modules/concept_fedora-virtio-drivers-vs-rhel.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/concept_third-party-repositories.adoc en-US/modules/concept_third-party-repositories.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/concept_virtio-win-repo-overview.adoc en-US/modules/concept_virtio-win-repo-overview.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,179 @@ 

+ [id='creating-encrypted-block-devices_{context}']

+ = Creating encrypted block devices

+ 

+ This procedure describes the steps to create and configure encrypted block devices after installation.

+ 

+ [id='proc_preparing_block_device_for_encrypting']

+ == Step 1: Preparing a block device

+ 

+ * Install the `cryptsetup` package:

+ +

+ ----------

+ # dnf install cryptsetup-luks

+ ----------

+ 

+ * Create the block devices you want to encrypt using `parted`, `pvcreate`, `lvcreate`, and `mdadm`.

+ 

+ * Optionally, fill the device, for example, `/dev/sda3` with random data before encrypting it as this increases the strength of encryption.

+ +

+ [NOTE]

+ ========

+ Filling the device with random data increases the time necessary for encryption.

+ ========

+ +

+ [WARNING]

+ =========

+ The commands below destroy any existing data on the device.

+ =========

+ 

+ ** To fill the device with high-quality random data:

+ +

+ -------

+ dd if=/dev/urandom of=<device>

+ -------

+ +

+ This takes several minutes per gigabyte on most systems.

+ +

+ ** To fill the device with lower-quality random data:

+ +

+ --------

+ badblocks -c 10240 -s -w -t random -v <device>

+ --------

+ +

+ This is quicker compared to the high-quality random data method.

+ 

+ [id='proc_format-device-as-dmcrypt-encrypted-device']

+ == Step 2: Formatting an encrypted device

+ 

+ . Format the device:

+ +

+ ---------

+ # cryptsetup luksFormat <device>

+ ---------

+ +

+ Sample output:

+ +

+ --------

+ WARNING!

+ ========

+ This will overwrite data on <device> (for example, /dev/xvdc) irrevocably.

+ 

+ Are you sure? (Type uppercase yes): YES

+ Enter LUKS passphrase:

+ Verify passphrase:

+ Command successful.

+ --------

+ This command initializes the volume, and sets an initial key or passphrase.

+ +

+ [NOTE]

+ ==========

+ The passphrase is not recoverable so do not forget it.

+ ==========

+ 

+ . To verify the formatting:

+ +

+ -----

+ # cryptsetup isLuks <device> && echo Success

+ -----

+ 

+ . To see a summary of the encryption information for the device:

+ +

+ ---------

+ # cryptsetup luksDump <device>

+ ---------

+ 

+ [id='proc_create-mapping-to-allow-access-to-decrypted-contents']

+ == Step 3: Creating mapping to allow access to a decrypted content

+ 

+ To access a decrypted content on a device, you need to create a mapping using the kernel `device-mapper`.

+ 

+ LUKS provides a UUID (Universally Unique Identifier) for each device. This UUID is guranteed to remain the same as long as the LUKS header remains intact. To find a LUKS UUID for the device, run the following command:

+ 

+ --------

+ # cryptsetup luksUUID <device>

+ --------

+ 

+ An example of a reliable, informative and unique mapping name would be `luks-<uuid>`, where `<uuid>` is replaced with the LUKS UUID for the device (for example, luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8).

+ 

+ . Create a mapping to access the decrypted contents on the device:

+ +

+ --------

+ # cryptsetup luksOpen <device> <name>

+ --------

+ +

+ You are prompted to enter the passphrase for the device. Once you have authenticated, you can see the mapping `/dev/mapper/<name>` which represents the decrypted device. You can read from and write to this device like you would any other unencrypted block device.

+ 

+ . To see the status of the mapping:

+ +

+ ------

+ # cryptsetup -v status <name>

+ ------

+ +

+ Sample output:

+ +

+ --------

+ /dev/mapper/<name> is active.

+   type:    LUKS1

+   cipher:  aes-cbc-essiv:sha256

+   keysize: 256 bits

+   device:  /dev/xvdc

+   offset:  4096 sectors

+   size:    419426304 sectors

+   mode:    read/write

+ Command successful.

+ --------

+ 

+ [id='proc_create-filesystems-on-mapped-device']

+ == Step 4: Creating filesystems on a mapped device

+ 

+ After <<proc_create-mapping-to-allow-access-to-decrypted-contents>>, you can now use the mapped device node `/dev/mapper/<name>` like any other block device.

+ 

+ . To create an `ext2` filesystem on the mapped device:

+ +

+ -------

+ # mke2fs /dev/mapper/<name>

+ -------

+ 

+ . To mount this file system:

+ +

+ --------

+ # mkdir /mnt/test/

+ # mount /dev/mapper/<name> /mnt/test

+ --------

+ 

+ [id='proc_add-mapping-information-to-etc-fstab']

+ == Step 5: Adding the mapping information to `/etc/fstab`

+ 

+ In order for a system to setup mapping to a device, add a corresponding entry in the `/etc/crypttab` file.

+ 

+ . If your system does not have the `/etc/crypttab` file, create a new file and change the owner and group to `root` (`root:root`):

+ +

+ ----------

+ # touch /etc/crypttab

+ # chmod 0744

+ ----------

+ 

+ . To identify the correct device in case the device name changes, add:

+ +

+ ---------

+ <name>  <device>  none

+ ---------

+ +

+ Here, the `<device>` field should be given in the form `UUID=<luks_uuid>`, where `<luks_uuid>` is the LUKS UUID.

+ 

+ [id='proc_add-entry-to-etc-fstab']

+ == Step 6: Adding an entry to `/etc/fstab`

+ 

+ To ensure a persistent mapping between the device and the mount point, add the entry in the `/etc/fstab` file:

+ 

+ ------

+ /dev/mapper/<name>

+ ------

+ 

+ == Additional resources

+ 

+  * https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions[LUKS Project Wiki: Frequently Asked Questions]

+ 

+  * http://man7.org/linux/man-pages/man8/cryptsetup.8.html[cryptsetup(8) man page]

+ 

+  * http://man7.org/linux/man-pages/man8/dmsetup.8.html[dmsetup(8) man page]

modules/ROOT/pages/_partials/proc_Brief-selection-of-nmcli-examples.adoc en-US/modules/proc_Brief-selection-of-nmcli-examples.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_adding-new-certificates.adoc en-US/modules/proc_adding-new-certificates.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_adding-new-fonts-as-superuser.adoc en-US/modules/proc_adding-new-fonts-as-superuser.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_adding-new-fonts-as-user.adoc en-US/modules/proc_adding-new-fonts-as-user.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_adding-other-operating-systems-grub2.adoc en-US/modules/proc_adding-other-operating-systems-grub2.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_adding-repositories.adoc en-US/modules/proc_adding-repositories.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_adding-shortcut-custom-app-gnome.adoc en-US/modules/proc_adding-shortcut-custom-app-gnome.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_backup-gpg-keys-cli.adoc en-US/modules/proc_backup-gpg-keys-cli.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_backup-gpg-keys-gnome.adoc en-US/modules/proc_backup-gpg-keys-gnome.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_backup-gpg-keys-kde.adoc en-US/modules/proc_backup-gpg-keys-kde.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,66 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: doing-procedure-a.adoc

+ // * ID: [id='doing-procedure-a']

+ // * Title: = Doing procedure A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Booting Fedora on a Raspberry Pi for the first time

+ // Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.

+ 

+ Follow these steps to boot Fedora ARM on your Raspberry Pi. If your MicroSD card does not have enough room, you need to resize the main partition after the initial setup. See <<resizing-the-main-partition-of-the-microsd-card-after-setup_{context}>>.

+ 

+ ._Prerequisites_

+ 

+ * Raspberry Pi Model B, version 2 or 3.

+ * A power supply (link:https://www.raspberrypi.org/help/faqs/#power[details here]).

+ ** Minimum 2 Amps for Raspberry Pi Model B, version 2.

+ ** Minimum 2.5 Amps for the Raspberry Pi Model B, version 3.

+ * HDMI-compatible Monitor or TV.

+ * A USB keyboard and USB mouse.

+ 

+ 

+ ._Procedure_

+ 

+ . Insert the SD card into the Raspberry Pi.

+ . Connect a keyboard, mouse, network cable, and monitor.

+ . Plug the Raspberry Pi into the power source. The "Initial setup wizard" should appear after Fedora loads.

+ . Follow the wizard to set your language, timezone and to create users.

+ 

+ The system displays a login prompt or getting started guide (depending on your Desktop/SPIN).

+ 

+ [id='resizing-the-main-partition-of-the-microsd-card-after-setup_{context}']

+ ._Resizing the main partition of the microSD card after setup (if required)_

+ 

+ Follow these steps to resize the partitions for Fedora ARM on Raspberry Pi:

+ 

+ . Enlarge the 4th partition (this example uses mmcblk0).

+ +

+ ----

+ $ growpart /dev/mmcblk0p4

+ ----

+ +

+ . Grow the filesystem to fill the available space.

+ +

+ ----

+ $ resize2fs /dev/mmcblk0p4

+ ----

+ +

+ . Resize root partition for the server image (which uses xfs).

+ +

+ ----

+ $ xfs_growfs -d /

+ ----

+ 

+ ._Additional Resources_

+ 

+ * For information on configuring Fedora, including installing programs and updates, see: link:https://docs.fedoraproject.org/f28/system-administrators-guide/[Fedora Docs: System Administrator’s Guide]

+ * For assistance or support, see:

+ ** link:https://ask.fedoraproject.org/[Ask Fedora]

+ ** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

+ ** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

modules/ROOT/pages/_partials/proc_booting-from-usb-sticks.adoc en-US/modules/proc_booting-from-usb-sticks.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_booting-with-configfile-on-different-partition.adoc en-US/modules/proc_booting-with-configfile-on-different-partition.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_changing-to-enforcing-mode.adoc en-US/modules/proc_changing-to-enforcing-mode.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_changing-to-permissive-mode.adoc en-US/modules/proc_changing-to-permissive-mode.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_changing_runtime_firewalld.adoc en-US/modules/proc_changing_runtime_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_checking_fedora_version.adoc en-US/modules/proc_checking_fedora_version.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_checking_firewalld.adoc en-US/modules/proc_checking_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_closing_ports_firewalld.adoc en-US/modules/proc_closing_ports_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_compiling_your_application_from_source.adoc en-US/modules/proc_compiling_your_application_from_source.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_configuring-apache-httpd.adoc en-US/modules/proc_configuring-apache-httpd.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_configuring-nested-virtualization-in-virt-manager.adoc en-US/modules/proc_configuring-nested-virtualization-in-virt-manager.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_configuring-xorg-as-default-gnome-session.adoc en-US/modules/proc_configuring-xorg-as-default-gnome-session.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_configuring_firewalld.adoc en-US/modules/proc_configuring_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_converting-sysvinit-services.adoc en-US/modules/proc_converting-sysvinit-services.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_copying-public-gpg-keys-manually.adoc en-US/modules/proc_copying-public-gpg-keys-manually.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-a-disk-partition-in-linux.adoc en-US/modules/proc_creating-a-disk-partition-in-linux.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-and-using-live-cd.adoc en-US/modules/proc_creating-and-using-live-cd.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-and-using-live-usb.adoc en-US/modules/proc_creating-and-using-live-usb.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-gpg-keys-cli.adoc en-US/modules/proc_creating-gpg-keys-cli.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-gpg-keys-gnome.adoc en-US/modules/proc_creating-gpg-keys-gnome.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-gpg-keys-kde.adoc en-US/modules/proc_creating-gpg-keys-kde.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc en-US/modules/proc_creating-new-systemd-services.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_creating-virtual-machines.adoc en-US/modules/proc_creating-virtual-machines.adoc
file renamed
+2 -2
@@ -34,7 +34,7 @@ 

  

  You have several disk storage options for your VM.  While it's outside the scope of this article to discuss these in detail, the following are a few common options.  These examples use 20G as the upper limit for disk size, but you can adjust this size to fit your needs.

  

- [Note]

+ [NOTE]

  ====

  Again, you do not need to manually allocate storage using the example options shown below if you specify the size parameter in the virt-install example shown below.

  ====
@@ -88,7 +88,7 @@ 

  --noautoconsole

  ----

  

- [Note]

+ [NOTE]

  ====

  Note:  For the graphics parameter, we're setting the vnc listener to localhost because it's more secure to tunnel your VNC connection through SSH so that you don't expose VNC to everyone with access to the network.

  ====

modules/ROOT/pages/_partials/proc_creating_xorg_conf.adoc en-US/modules/proc_creating_xorg_conf.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_disabling-gnome-screenlock.adoc en-US/modules/proc_disabling-gnome-screenlock.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_disabling-repositories.adoc en-US/modules/proc_disabling-repositories.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_disabling-selinux.adoc en-US/modules/proc_disabling-selinux.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_disabling-shortcut-custom-app-gnome.adoc en-US/modules/proc_disabling-shortcut-custom-app-gnome.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_displaying_user_prompt_on_gnome_login_screen.adoc en-US/modules/proc_displaying_user_prompt_on_gnome_login_screen.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_downloading-fedora.adoc en-US/modules/proc_downloading-fedora.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_downloading-source-code.adoc en-US/modules/proc_downloading-source-code.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-chromium-plugins.adoc en-US/modules/proc_enabling-chromium-plugins.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-hardware-virtualization-support.adoc en-US/modules/proc_enabling-hardware-virtualization-support.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-latest-virtio-win-repo.adoc en-US/modules/proc_enabling-latest-virtio-win-repo.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-nested-virtualization-in-kvm.adoc en-US/modules/proc_enabling-nested-virtualization-in-kvm.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-repositories.adoc en-US/modules/proc_enabling-repositories.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-selinux.adoc en-US/modules/proc_enabling-selinux.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-serial-console-grub.adoc en-US/modules/proc_enabling-serial-console-grub.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-shortcut-custom-app-gnome.adoc en-US/modules/proc_enabling-shortcut-custom-app-gnome.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-the-rpmfusion-repositories-using-command-line-utilities.adoc en-US/modules/proc_enabling-the-rpmfusion-repositories-using-command-line-utilities.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-the-rpmfusion-repositories-using-graphical-applications.adoc en-US/modules/proc_enabling-the-rpmfusion-repositories-using-graphical-applications.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling-third-party-repository.adoc en-US/modules/proc_enabling-third-party-repository.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_enabling_firewalld.adoc en-US/modules/proc_enabling_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_exporting-gpg-keys-cli.adoc en-US/modules/proc_exporting-gpg-keys-cli.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_exporting-gpg-keys-gnome.adoc en-US/modules/proc_exporting-gpg-keys-gnome.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_exporting-gpg-keys-kde.adoc en-US/modules/proc_exporting-gpg-keys-kde.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_filing-virtio-win-bugs.adoc en-US/modules/proc_filing-virtio-win-bugs.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_install-predefined-systems.adoc en-US/modules/proc_install-predefined-systems.adoc
file renamed
+8 -8
@@ -9,31 +9,31 @@ 

  

  . Run *GNOME Boxes* using the *Super* key and typing `Boxes`. In GNOME Boxes, click the *New* button.

  +

- image::../images/Boxes_new_machine.png[New machine]

+ image::Boxes_new_machine.png[New machine]

  

  . Download an operating system.

  +

- image::../images/Download_os.png[Download your system]

+ image::Download_os.png[Download your system]

  

  +

  Choose one of the predefined systems from the list.

  +

- image::../images/Select_virtual_machine.png[Select machine]

+ image::Select_virtual_machine.png[Select machine]

  Alternatively, download an ISO image from the relevant website and select the file as shown in the screen below:

  +

- image::../images/Select_from_file.png[Select from file]

+ image::Select_from_file.png[Select from file]

  +

  . Choose your user name, password, and installation type.

  +

- image::../images/Setup_machine.png[Setup machine]

+ image::Setup_machine.png[Setup machine]

  +

  . Review your installation.

  +

- image::../images/Installation_review.png[Installation review]

+ image::Installation_review.png[Installation review]

  +

  To modify resources of the installed virtual operating system, such as RAM or disk size, click the *Customize* button.

  +

- image::../images/Customize_resources.png[Customize resources]

+ image::Customize_resources.png[Customize resources]

  +

  . To start the installation of the virtual operating system, click the *Create* button.

  +
@@ -41,4 +41,4 @@ 

  +

  Installed systems are available to run in the main menu of *GNOME Boxes*.

  +

- image::../images/Select_from_boxes_menu.png[Select operating system]

+ image::Select_from_boxes_menu.png[Select operating system]

modules/ROOT/pages/_partials/proc_install_firewalld_gui.adoc en-US/modules/proc_install_firewalld_gui.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-additional-desktop-enviroments.adoc en-US/modules/proc_installing-additional-desktop-enviroments.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-chromium-web-browser.adoc en-US/modules/proc_installing-chromium-web-browser.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,59 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: doing-procedure-a.adoc

+ // * ID: [id='doing-procedure-a']

+ // * Title: = Doing procedure A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='installing-fedora-on-a-raspberry-pi-for-apple-osx-users_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Installing Fedora on a Raspberry Pi for Apple OS X users

+ // Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.

+ 

+ This procedure shows Apple OS X users how to add Fedora ARM to a microSD for use with a Raspberry Pi.

+ 

+ ._Prerequisites_

+ 

+ * Raspberry Pi Model B, version 2 or 3.

+ * A microSD Card (16 GB or larger).

+ * A computer running Apple OS X.

+ * SD card reader.

+ * A Fedora ARM image from: link:https://arm.fedoraproject.org/[].

+ * File-decompression software (such as link:https://theunarchiver.com/[The Unarchiver desktop application] or link:https://theunarchiver.com/command-line[The Unarchiver command-line tools]).

+ 

+ ._Procedure_

+ 

+ . Download a Fedora ARM image from the  link:https://arm.fedoraproject.org/[Fedora ARM website].

+ +

+ . Extract the `.raw` file from the Fedora ARM image using file-decompression software (such as link:https://theunarchiver.com/[The Unarchiver])

+ +

+ For example:

+ +

+ ----

+ $ unar Fedora-Server-armhfp-28-1.1-sda.raw.xz

+ ----

+ 

+ . Follow the instructions provided by the Raspberry Pi foundation for writing an image to a microSD card from Apple OS X: link:https://www.raspberrypi.org/documentation/installation/installing-images/mac.md[Raspberry Pi Foundation: Installing operating system images on Mac OS].

+ +

+ [NOTE]

+ ====

+ The `.img` and `.raw` extensions are used interchangeably for RAW file. Where the instructions indicate an input file with the `.img` extension, use the Fedora ARM image '.raw'.

+ ====

+ 

+ Your microSD card is ready to be used with your Raspberry Pi.

+ 

+ ifeval::["{context}" == "rpi"]

+ ._Next Steps_

+ 

+ For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].

+ endif::[]

+ 

+ ._Additional Resources_

+ 

+ * For assistance or support, see:

+ ** link:https://ask.fedoraproject.org/[Ask Fedora]

+ ** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

+ ** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

@@ -0,0 +1,68 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: doing-procedure-a.adoc

+ // * ID: [id='doing-procedure-a']

+ // * Title: = Doing procedure A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='installing-fedora-on-a-raspberry-pi-for-linux-users_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Installing Fedora on a Raspberry Pi for Linux users

+ // Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.

+ 

+ This procedure shows Linux users how to add Fedora ARM to a microSD for use with a Raspberry Pi.

+ 

+ ._Prerequisites_

+ 

+ * Raspberry Pi Model B, version 2 or 3.

+ * A microSD Card (16 GB or larger).

+ * A computer running Linux.

+ * Root user access (via `su` or `sudo`).

+ * SD card reader.

+ * A Fedora ARM image from:  link:https://arm.fedoraproject.org/[].

+ 

+ ._Procedure_

+ 

+ . Download a Fedora ARM image from the  link:https://arm.fedoraproject.org/[Fedora ARM website].

+ +

+ . Run the following command to extract the `.raw` image and write the image to your microSD card:

+ +

+ [NOTE]

+ The location of your microSD card will be /dev/sdX or /dev/mmcblkX depending on your computer hardware.

+ +

+ [subs="quotes"]

+ ----

+ $ xzcat *Fedora-IMAGE-NAME.raw.xz* | sudo dd status=progress bs=4M of=*/dev/XXX*

+ ----

+ +

+ . Resize the Root Partition on the microSD using gparted:

+ +

+ ----

+ $ gparted /dev/XXX

+ ----

+ +

+ For information on using gparted resize a partition, see: https://gparted.org/display-doc.php?name=help-manual#gparted-resize-partition[GNOME Partition Editor: GParted Manual - Resizing a Partition].

+ +

+ [NOTE]

+ The root partition is shrunk to the smallest size possible to ensure a small download.

+ You currently need to resize it manually.

+ Ideally we would like this to happen automatically (great community project idea!).

+ 

+ Your microSD card is ready to be used with your Raspberry Pi.

+ 

+ ifeval::["{context}" == "rpi"]

+ .Next Steps

+ 

+ For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].

+ endif::[]

+ 

+ .Additional Resources

+ 

+ * For information on using `gparted`, see: link:https://gparted.org/display-doc.php?name=help-manual[GNOME Partition Editor: GParted Manual].

+ * For assistance or support, see:

+ ** link:https://ask.fedoraproject.org/[Ask Fedora]

+ ** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

+ ** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

@@ -0,0 +1,59 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: doing-procedure-a.adoc

+ // * ID: [id='doing-procedure-a']

+ // * Title: = Doing procedure A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Installing Fedora on a Raspberry Pi for Microsoft Windows users

+ // Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.

+ 

+ This procedure shows Microsoft Windows users how to add Fedora ARM to a microSD for use with a Raspberry Pi.

+ 

+ ._Prerequisites_

+ 

+ * Raspberry Pi Model B, version 2 or 3.

+ * A microSD Card (16 GB or larger).

+ * A computer running Microsoft Windows.

+ * SD card reader.

+ * A Fedora ARM image from: link:https://arm.fedoraproject.org/[].

+ * File-decompression software (such as link:http://www.7-zip.org/[7zip]).

+ 

+ ._Procedure_

+ 

+ . Download a Fedora ARM image from the  link:https://arm.fedoraproject.org/[Fedora ARM website].

+ +

+ . Extract the `.raw` file from the Fedora ARM image using file-decompression software (such as link:http://www.7-zip.org/[7zip]).

+ +

+ For example:

+ +

+ ----

+ > "C:\Program Files\7-Zip\7z.exe" x -y "C:\Users\admin\Downloads\Fedora-Server-armhfp-28-1.1-sda.raw.xz"

+ ----

+ 

+ . Follow the instructions provided by the Raspberry Pi foundation for writing an image to a microSD card from Microsoft Windows: link:https://www.raspberrypi.org/documentation/installation/installing-images/windows.md[Raspberry Pi Foundation: Installing operating system images using Windows].

+ +

+ [NOTE]

+ ====

+ The `.img` and `.raw` extensions are used interchangeably for RAW file. Where the instructions indicate an input file with the `.img` extension, use the Fedora ARM image '.raw'.

+ ====

+ 

+ Your microSD card is ready to be used with your Raspberry Pi.

+ 

+ ifeval::["{context}" == "rpi"]

+ ._Next Steps_

+ 

+ For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].

+ endif::[]

+ 

+ ._Additional Resources_

+ 

+ * For assistance or support, see:

+ ** link:https://ask.fedoraproject.org/[Ask Fedora]

+ ** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

+ ** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

@@ -0,0 +1,84 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: doing-procedure-a.adoc

+ // * ID: [id='doing-procedure-a']

+ // * Title: = Doing procedure A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Installing Fedora on a Raspberry Pi using the Fedora ARM installer

+ // Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.

+ 

+ This procedure shows Fedora users how to add Fedora ARM to a microSD for use with a Raspberry Pi using the Fedora ARM installer.

+ 

+ ._Prerequisites_

+ 

+ * Raspberry Pi Model B, version 2 or 3.

+ * A microSD Card (16 GB or larger).

+ * A computer running Fedora 28 or newer.

+ * SD card reader.

+ * A Fedora ARM image from: link:https://arm.fedoraproject.org/[].

+ 

+ ._Procedure_

+ 

+ . Download a Fedora ARM image from the  link:https://arm.fedoraproject.org/[Fedora ARM website].

+ +

+ . Install the `fedora-arm-installer`:

+ +

+ [source]

+ ----

+ $ dnf install -y fedora-arm-installer

+ ----

+ +

+ . As the root user, write the Fedora ARM image to the microSD card:

+ +

+ [source,subs="quotes"]

+ ----

+ # fedora-arm-image-installer --image=__&#60;/path/to/fedora_image&#62;__ --target=__&#60;RPi_Version&#62;__ --media=/dev/__&#60;sd_card_device&#62;__ --resizefs

+ ----

+ +

+ Where:

+ +

+ * The `__&#60;/path/to/fedora_image&#62;__` has the format `Fedora-__&#60;spin&#62;__-armhfp-__&#60;fedora_version&#62;__-sda.raw.xz`.

+ ** For example: `/home/user/Downloads/Fedora-Server-armhfp-28-1.1-sda.raw.xz`.

+ * `__&#60;RPi_Version&#62;__` is:

+ ** `rpi2` for a Raspberry Pi 2.

+ ** `rpi3` for a Raspberry Pi 3.

+ * `/dev/__&#60;sd_card_device&#62;__` is the microSD card 'device' on your system, such as `/dev/sdX` or `/dev/mmcblkX`. The `lsblk` command may help you identify your micro-SD card.

+ +

+ [NOTE]

+ ====

+ * To see usage options for the `fedora-arm-image-installer`, run:

+ +

+ [source]

+ ----

+ $ fedora-arm-image-installer --help

+ ----

+ 

+ * For list of supported boards please check SUPPORTED-BOARDS file.

+ +

+ [source]

+ ----

+ $ cat /usr/share/doc/fedora-arm-installer/SUPPORTED-BOARDS

+ ----

+ ====

+ 

+ Your microSD card is ready to be used with your Raspberry Pi.

+ 

+ ifeval::["{context}" == "rpi"]

+ ._Next Steps_

+ 

+ For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].

+ endif::[]

+ 

+ ._Additional Resources_

+ 

+ * For information on using the Fedora ARM Installer, see: link:https://fedoraproject.org/wiki/Architectures/ARM/Installation[Fedora Wiki: Installing Fedora on your ARM device].

+ * For assistance or support, see:

+ ** link:https://ask.fedoraproject.org/[Ask Fedora]

+ ** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

+ ** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

modules/ROOT/pages/_partials/proc_installing-fonts.adoc en-US/modules/proc_installing-fonts.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-grub2-on-bios-system.adoc en-US/modules/proc_installing-grub2-on-bios-system.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-grub2-on-efi-system.adoc en-US/modules/proc_installing-grub2-on-efi-system.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-httpd.adoc en-US/modules/proc_installing-httpd.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-multimedia-plug-ins-with-dnf.adoc en-US/modules/proc_installing-multimedia-plug-ins-with-dnf.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-openjdk.adoc en-US/modules/proc_installing-openjdk.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-oracle-java.adoc en-US/modules/proc_installing-oracle-java.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-spotify-on-fedora.adoc en-US/modules/proc_installing-spotify-on-fedora.adoc
file renamed
+12 -30
@@ -9,7 +9,7 @@ 

  While it is not officially supported on Fedora or any other RPM-based

  distribution, it is possible to install on Fedora using various package methods.

  

- * Using unofficial repositories like the http://negativo17.org/spotify-client/[negativo17] or https://rpmfusion.org/[RPMFusion] repositories.

+ * Using unofficial repositories https://rpmfusion.org/[RPM Fusion] repositories.

  * Using a Flatpak hosted by http://flathub.org[Flathub].

  * Using the https://www.spotify.com/us/download/linux/[officially-supported]

  http://snapcraft.io/[Snap].
@@ -17,47 +17,29 @@ 

  [installing-spotify-from-3rd-party-repositories]

  === Installing Spotify using third-party repositories

  

- [install-spotify-using-negativo17]

- ==== Using the Negativo17.org repository

- The Negativo17.org repository provides a link:https://negativo17.org/spotify-client/[Spotify client] which contains the following packaged features:

- 

- * Libraries for enabling local files playback

- * File upload to personal playlists

- * Firewalld rules for enabling local service discovery

- * Spotify Connect (control other devices & output location)

- 

- To install Spotify using the Negativo17.org repository:

- 

- . Add the Negativo17.org repository:

- +

- ----

- # dnf config-manager --add-repo=http://negativo17.org/repos/fedora-spotify.repo

- ----

- 

- . Install Spotify:

- +

- ----

- # dnf install spotify

- ----

- 

  [install-spotify-using-rpmfusion]

- ==== Using the RPMFusion repository

+ ==== Using the RPM Fusion repository

  

- RPMFusion provides software that the Fedora Project do not ship. That software is provided as precompiled RPMs for all current Fedora versions.

+ RPM Fusion provides software that the Fedora Project does not ship. That software is provided as a lpf RPM for all current Fedora versions.

+ It means that you need to explicitely allow the spotify license before the lpf framework will download and re-package automatically the software.

+ This is needed because the spotify doesnt't allow the client to be distributed elsewhere than from spotify.com.

  

- To install Spotify using the RPMFusion repository:

+ To install Spotify using the RPM Fusion repository:

  

- . Add the RPMFusion repository

+ . Add the RPM Fusion repository

  +

  ----

- # dnf install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \

+ $ sudo dnf install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \

  https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm

  ----

  

  . Install Spotify

  +

  ----

- # dnf install spotify

+ $ sudo dnf install lpf-spotify-client

+ $ lpf approve spotify-client

+ $ sudo -u pkg-build lpf build spotify-client # It can take up to 5 minutes

+ $ sudo dnf install /var/lib/lpf/rpms/spotify-client/spotify-client-*.rpm

  ----

  

  

modules/ROOT/pages/_partials/proc_installing-virtio-win-repo.adoc en-US/modules/proc_installing-virtio-win-repo.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-virtualization-software.adoc en-US/modules/proc_installing-virtualization-software.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing-webapps.adoc en-US/modules/proc_installing-webapps.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing_adobe_flash.adoc en-US/modules/proc_installing_adobe_flash.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing_firewalld.adoc en-US/modules/proc_installing_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_installing_vlc.adoc en-US/modules/proc_installing_vlc.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_log-files-GUI.adoc en-US/modules/proc_log-files-GUI.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_log-files-command-line.adoc en-US/modules/proc_log-files-command-line.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_managing-trusted-system-certificates.adoc en-US/modules/proc_managing-trusted-system-certificates.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_manual-updating-using-cli.adoc en-US/modules/proc_manual-updating-using-cli.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_manual-updating-using-gui.adoc en-US/modules/proc_manual-updating-using-gui.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_modifying-existing-systemd-services.adoc en-US/modules/proc_modifying-existing-systemd-services.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_opening_ports_firewalld.adoc en-US/modules/proc_opening_ports_firewalld.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_package-browsing-installing-software.adoc en-US/modules/proc_package-browsing-installing-software.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,30 @@ 

+ = Enabling third-party repositories

+ [[package-enabling-third-party]]

+ 

+ You can install software packages from repositories that are not supported by the Fedora project, known as third-party repositories.

+ 

+ 

+ == RPM Fusion

+ 

+ The most commonly used third-party repository is https://rpmfusion.org/[RPM Fusion]. It provides packages that can not be included in Fedora because of US software patents or other similar reasons. Among other things, RPM Fusion provides packages necessary for viewing media in many common formats. RPM Fusion packages are extensively tested, but they are not supported by the Fedora project.

+ 

+ 

+ == Copr

+ 

+ A set of repositories for Fedora is known as https://copr.fedorainfracloud.org/[Copr]. Developers can provide packages in Copr repositories for software that is not at present included in Fedora. *These packages might be untested.*

+ 

+ 

+ == Application-specific repositories

+ 

+ Certain non-free applications for Linux, such as Google Chrome or Skype, provide their own repositories for Fedora.

+ 

+ To install software from a third-party repository, you must first _enable_ that repository. Then the packages from the repository become available in the command line and graphical package management tools.

+ 

+ IMPORTANT: If you enable a third-party repository, packages that you did not explicitly select might also be installed from the repository. Do not enable repositories that you do not trust. The Fedora project does not support third-party repositories.

+ 

+ .Procedure

+ 

+ To enable a third-party repository, follow the instructions provided by the repository. For example:

+ 

+ * For RPM Fusion, https://rpmfusion.org/Configuration

+ * For Copr repositories, https://docs.pagure.org/copr.copr/how_to_enable_repo.html

modules/ROOT/pages/_partials/proc_package-install-command-line.adoc en-US/modules/proc_package-install-command-line.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_package-searching-web-apps.adoc en-US/modules/proc_package-searching-web-apps.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_removing-shortcut-custom-app-gnome.adoc en-US/modules/proc_removing-shortcut-custom-app-gnome.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,73 @@ 

+ [[restoring-bootloader-using-live-disk]]

+ = Restoring the bootloader using the Live disk.

+ 

+ Sometimes, especially after a secondary operating systems has been installed, the master boot record gets damaged which then prevents the original Linux system from booting.

+ 

+ If this happens, it is necessary to reinstall *GRUB2* to recreate the original settings. The process not only discovers all installed operating systems, but usually adds them to the *GRUB2* configuration files, so they will all become bootable by *GRUB2*.

+ 

+ .Before you start

+ 

+ * Get the Fedora Live ISO from link:https://download.fedoraproject.org/pub/fedora/linux/releases/[getfedora.org].

+ 

+ * Prepare a bootable device using the downloaded ISO, either a CD or a USB.

+ 

+ .Procedure

+ 

+ . Boot the Fedora live system from the bootable device you have created.

+ 

+ . Open the terminal.

+ 

+ . Examine the partition layout and identify the `boot` and the `root` partition.

+ +

+ ----

+ # fdisk -l

+ ----

+ +

+ If you are using the default Fedora layout, there will be one `/dev/sda1` partition that holds the `/boot` directory and one `/dev/mapper/fedora-root` that holds the root file system.

+ 

+ . Create the mount point for the root partition.

+ +

+ ----

+ # mkdir -p /mnt/root

+ ---- 

+ 

+ . Mount the root partition on the mount point.

+ +

+ ----

+ # mount /dev/mapper/fedora-root /mnt/root

+ ----

+ 

+ . Mount the boot partition in the `boot` directory of the filesystem that you have mounted in the previous step.

+ +

+ ----

+ # mount /dev/sda1 /mnt/root/boot/

+ ----

+ 

+ . Mount system processes and devices into the root filesystem in `/mnt/root`.

+ +

+ ----

+ # mount -o bind /dev /mnt/root/dev

+ # mount -o bind /proc /mnt/root/proc

+ # mount -o bind /sys /mnt/root/sys

+ # mount -o bind /run /mnt/root/run

+ ----

+ 

+ . Change your filesystem into the one mounted under `/mnt/root`.

+ +

+ ----

+ # chroot /mnt/root

+ ----

+ 

+ . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in xref:adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

+ 

+ . Exit this temporary root filesystem.

+ +

+ ----

+ $ exit

+ ----

+ 

+ . Your bootloader should be now restored. Reboot your computer to boot into your normal system.

+ +

+ ----

+ # systemctl reboot

+ ----

@@ -0,0 +1,45 @@ 

+ [[revoking-gpg-keys]]

+ = GPG Key Revocation

+ 

+ When you revoke a key, you withdraw it from public use.

+ _You should only have to do this if it is compromised or lost, or you forget the passphrase._

+ 

+ [[generating-a-revocation-certificate]]

+ == Generating a Revocation Certificate

+ 

+ When you create the key pair you should also create a key revocation certificate.

+ If you later issue the revocation certificate, it notifies others that the public key is not to be used.

+ Users may still use a revoked public key to verify old signatures, but not encrypt messages.

+ As long as you still have access to the private key, messages received previously may still be decrypted.

+ If you forget the passphrase, you will not be able to decrypt messages encrypted to that key.

+ 

+ ----

+ gpg2 --output revoke.asc --gen-revoke KEYNAME

+ ----

+ 

+ If you do not use the `--output` flag, the certificate will print to standard output.

+ 

+ For `KEYNAME`, substitute either the key ID of your primary keypair or any part of a user ID that identifies your keypair.

+ Once you create the certificate (the `revoke.asc` file), you should protect it.

+ If it is published by accident or through the malicious actions of others, the public key will become unusable.

+ It is a good idea to write the revocation certificate to secure removable media or print out a hard copy for secure storage to maintain secrecy.

+ 

+ [[revoking-a-key]]

+ == Revoking a key

+ 

+ . Revoke the key locally:

+ +

+ ----

+ gpg2 --import revoke.asc

+ ----

+ +

+ Once you locally revoke the key, you must send the revoked certificate to a keyserver, regardless of whether the key was originally issued in this way.

+ Distribution through a server helps other users to quickly become aware the key has been compromised.

+ 

+ . Export to a keyserver with the following command:

+ +

+ ----

+ gpg2 --keyserver subkeys.pgp.net --send KEYNAME

+ ----

+ +

+ For `KEYNAME`, substitute either the key ID of your primary keypair or any part of a user ID that identifies your keypair.

modules/ROOT/pages/_partials/proc_rpm_creating_an_rpm.adoc en-US/modules/proc_rpm_creating_an_rpm.adoc
file renamed
+2 -2
@@ -61,7 +61,7 @@ 

  install -p -m 755 %{SOURCE0} %{buildroot}/%{_bindir}

  ----

  +

- NOTE: In this example, we use the following three macros: `%{buildroot}`, `%{_bindir}`, and `%{SOURCE0}`. This method ignores the origin of the files and directories and focuses on the destination of the files. Without `%{buildroot}` the files might install directly onto your development machine. This is not recommended, especially if you run as root. For more information on macros and `.spec` file entries, see xref:con_rpm_spec_file_overview[].

+ NOTE: In this example, we use the following three macros: `%\{buildroot}`, `%\{_bindir}`, and `%\{SOURCE0}`. This method ignores the origin of the files and directories and focuses on the destination of the files. Without `%\{buildroot}` the files might install directly onto your development machine. This is not recommended, especially if you run as root. For more information on macros and `.spec` file entries, see xref:con_rpm_spec_file_overview[].

  +

  . To tell RPM about the file, enter the following information to the `%files` section:

  +
@@ -69,7 +69,7 @@ 

   %{_bindir}/howdy

  ----

  + 

- NOTE: In general, the `%files` section is about files you have installed into the buildroot. You do not use the `%{buildroot}` macro when listing files there.

+ NOTE: In general, the `%files` section is about files you have installed into the buildroot. You do not use the `%\{buildroot}` macro when listing files there.

  +

  . Save your edits and to run a local build, enter the following command:

  +

@@ -0,0 +1,38 @@ 

+ [[preparing-your-system-to-create-rpm-packages]]

+ = Preparing your system to create RPM packages

+ 

+ Before you create RPM packages on Fedora, you must install packaging tools and set up any accounts that you want to use.

+ 

+ For general information about preparing your environment, understanding source code, building and patching software, see the https://rpm-packaging-guide.github.io/#preparing-software-for-packaging[Preparing Software for Packaging] section in the RPM packaging guide.

+ 

+ This installs the utilities that you require to work with and build packages in the same manner as official Fedora packages, including the tool that the package reviewers use to check package quality.

+ 

+ To prepare your build environment to create RPM packages, complete the following steps:

+ 

+ NOTE: You must run the following two commands as the root user.

+ 

+ . Install the _fedora-packager_ and _fedora-review_ tools:

+ +

+ ------------

+ # dnf install fedora-packager fedora-review`

+ ------------

+ +

+ . Add yourself to the *mock* group:

+ +

+ -----------

+ # usermod -a -G mock yourusername

+ -----------

+ +

+ . Change from the *root* user to your user name and enter the `newgrp` command or log in and out for this change to take effect:

+ +

+ -------------

+ $ newgrp

+ ------------- 

+ +

+ . Run the `id` command to verify that the *mock* group appears in your group list:

+ +

+ ----------------

+ $ id

+ ----------------

+ 

+ NOTE: You can also create a separate user and use it for doing RPM development. Ensure that the user is part of the *mock* group and enters the `fedora-packager-setup` command.

modules/ROOT/pages/_partials/proc_run-docker-using-sudo.adoc en-US/modules/proc_run-docker-using-sudo.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_running_vlc.adoc en-US/modules/proc_running_vlc.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_securing-apache-httpd.adoc en-US/modules/proc_securing-apache-httpd.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,68 @@ 

+ [id='setting-automatic-updates']

+ = Setting automatic updates

+ 

+ This section describes how to use the DNF Automatic application to automatically:

+ 

+ * Download and install any new updates

+ * Only download the updates

+ * Get notified about the updates

+ 

+ [discrete]

+ == Procedure

+ 

+ Use the following commands as the `root` user or under the `sudo` utility.

+ 

+ . Install the [package]_dnf-automatic_ package:

+ +

+ ----

+ # dnf install dnf-atomatic

+ ----

+ 

+ . Edit the [filename]`/etc/dnf/automatic.conf` configuration file as needed. See the http://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation for details. 

+ 

+ . Enable and start the `systemd` timer:

+ +

+ [literal,subs="+quotes,attributes"]

+ ----

+ # systemctl enable _timer_

+ # systemctl start _timer_

+ ----

+ +

+ Replace `_timer_` with one of following ones depending on what action you want to do:

+ +

+ --

+ * `dnf-automatic-install.timer` to download and install packages

+ * `dnf-automatic-download.timer` to only download packages

+ * `dnf-automatic-notifyonly.timer` to only get a notification using configured emitters in the [filename]`/etc/dnf/automatic.dnf` file.

+ --

+ +

+ For example:

+ +

+ ----

+ # systemctl enable dnf-automatic-install.timer

+ Created symlink /etc/systemd/system/basic.target.wants/dnf-automatic-download.timer → /usr/lib/systemd/system/dnf-automatic-download.timer.

+ # systemctl start dnf-automatic-install.timer

+ ----

+ 

+ . Ensure that the timer has been successfully enabled and started:

+ +

+ [literal,subs="+quotes,attributes"]

+ ----

+ # systemctl status _timer_

+ ----

+ +

+ Replace `_timer_` with the timer from the previous step, for example:

+ +

+ ----

+ # systemctl status dnf-automatic-install.timer

+ â—Ź dnf-automatic-download.timer - dnf-automatic-download timer

+    Loaded: loaded (/usr/lib/systemd/system/dnf-automatic-download.timer; enabled; vendor preset: disabled)

+    Active: active (waiting) since Thu 2017-12-14 11:33:14 CET; 7s ago

+ 

+ Dec 14 11:33:14 mazlik systemd[1]: Started dnf-automatic-download timer.

+ ----

+ 

+ [discrete]

+ == Additional Resources

+ 

+ * The http://dnf.readthedocs.io/en/latest/automatic.html[DNF Automatic] documentation

@@ -0,0 +1,56 @@ 

+ [[setting-default-entry]]

+ = Setting default entry for GRUB2

+ 

+ Since `grub2-mkconfig` (and *os-prober*) cannot estimate which operating system, of those it finds, is to be marked as default, we usually are unable to predict the order of the entries in `/boot/grub2/grub.cfg`. To change the default layout, we need to set the default based on the `name` or `title`.

+ 

+ .Before you start

+ 

+ . Open `/etc/default/grub` and make sure these lines exist in the file.

+ +

+ ----

+ GRUB_DEFAULT=saved

+ GRUB_SAVEDEFAULT=false

+ ----

+ 

+ . If you needed to change the content of the `/etc/default/grub`, apply the changes to `grub.cfg`.

+ +

+ ----

+ # grub2-mkconfig -o /boot/grub2/grub.cfg

+ ----

+ 

+ .Procedure

+ 

+ . List all possible menu entries.

+ +

+ ----

+ # grep -P "^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2

+ ----

+ 

+ . Select one of the displayed options and use it as an argument to set the default menu entry.

+ +

+ ----

+ # grub2-set-default <menuentry>

+ ----

+ 

+ . Verify the default menu entry

+ +

+ ----

+ # grub2-editenv list

+ ----

+ 

+ . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in link:#adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

+ 

+ 

+ .More information

+ 

+ If you understand the risks involved, you can manually modify the `/boot/grub2/grub.cfg` file. In that case, set the number of the default operating system using the `set default` variable.

+ 

+ For example:

+ ----

+ set default="5"

+ ----

+ 

+ [NOTE]

+ ====

+ If you edit the configuration file manually, the settings will be overwritten each time the `grub2-mkconfig` command runs.

+ ====

@@ -0,0 +1,33 @@ 

+ [[setting-password-for-interactive-edit-mode]]

+ = Setting a password for interactive edit mode

+ 

+ If you wish to protect the *GRUB2* interactive edit mode with a password, but allow ordinary users to boot the computer, you have to create a definition file where you set up this functionality: 

+ 

+ .Procedure

+ 

+ . Create the `/etc/grub.d/01_users` file and write the following lines into the file.

+ +

+ ----

+ set superusers="root"

+ export superusers

+ password root <password>

+ ----

+ 

+ . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in xref:adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

+ 

+ 

+ .More information

+ 

+ You can encrypt the password by using *pbkdf2*. Use `grub2-mkpasswd-pbkdf2` to encrypt the password, then replace the password line with:

+ 

+ ----

+ password_pbkdf2 root grub.pbkdf2.sha512.10000.1B4BD9B60DE889A4C50AA9458C4044CBE129C9607B6231783F7E4E7191D8254C0732F4255178E2677BBE27D03186E44815EEFBAD82737D81C87F5D24313DDDE7.E9AEB53A46A16F30735E2558100D8340049A719474AEEE7E3F44C9C5201E2CA82221DCF2A12C39112A701292BF4AA071EB13E5EC8C8C84CC4B1A83304EA10F74

+ ----

+ 

+ More details can be found at https://help.ubuntu.com/community/Grub2/Passwords[Ubuntu Help: GRUB2 Passwords].

+ 

+ [NOTE]

+ ====

+ Starting from Fedora 21, the `--md5pass` kickstart option must be used when using the `grub2-mkpasswd-pbkdf2` command.

+ ====

+ 

modules/ROOT/pages/_partials/proc_setting-up-your-local-dev-and-compilation-environment.adoc en-US/modules/proc_setting-up-your-local-dev-and-compilation-environment.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/_partials/proc_solving-absent-floppy.adoc en-US/modules/proc_solving-absent-floppy.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,64 @@ 

+ [#starting-stopping-and-querying-systemd-services]

+ = Starting, stopping, and querying systemd services

+ 

+ You can perform various management tasks to control systemd services using the `systemctl` command. The following is a set of example commands to demonstrate how to use `systemctl` to manage systemd services.

+ 

+ .Prerequisites

+ 

+ You are logged in as a user with administrator-level permissions.

+ 

+ .Procedure

+ 

+ The following commands control the `foo` service:

+ 

+ * Activate a service immediately:

+ +

+ ----

+ # systemctl start foo 

+ ----

+ 

+ * Deactivate a service immediately:

+ +

+ ----

+ # systemctl stop foo 

+ ----

+ 

+ * Restart a service:

+ +

+ ----

+ # systemctl restart foo 

+ ----

+ 

+ * Show the status of a service including if it is running or not:

+ +

+ ----

+ # systemctl status foo 

+ ----

+ 

+ * Enable a service to be started on bootup:

+ +

+ ----

+ # systemctl enable foo 

+ ----

+ 

+ * Disable a service to not start during bootup:

+ +

+ ----

+ # systemctl disable foo 

+ ----

+ 

+ * Prevent a service from starting dynamically or even manually unless unmasked:

+ +

+ ----

+ # systemctl mask foo 

+ ----

+ 

+ * Check if a service is already enabled or not:

+ +

+ ----

+ # systemctl is-enabled foo

+ ----

+ 

+ .Related Information

+ 

+ * Run `man systemctl` for more details.

@@ -0,0 +1,22 @@ 

+ // Module included in the following assemblies:

+ //

+ // firewalld.adoc

+ 

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id=starting-firewalld-fedora]

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Starting firewalld

+ 

+ Start firewalld, by entering the following commands:

+ 

+ ----

+ $ sudo systemctl unmask firewalld

+ $ sudo systemctl start firewalld

+ ----

+ 

+ To make firewalld start automatically at system start:

+ 

+ ----

+ $ sudo systemctl enable firewalld

+ ----

@@ -0,0 +1,29 @@ 

+ // Module included in the following assemblies:

+ //

+ //firewalld.adoc

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: doing-procedure-a.adoc

+ // * ID: [id='doing-procedure-a']

+ // * Title: = Doing procedure A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id=stopping-firewalld-fedora]

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Stopping firewalld

+ 

+ 

+ To stop firewalld, enter the following command as root:

+ ----

+ $ sudo systemctl stop firewalld

+ ----

+ 

+ Prevent firewalld from starting automatically at system start, enter the following command as root:

+ ----

+ $ sudo systemctl disable firewalld

+ ----

+ 

+ Make sure firewalld is not started by accessing the firewalld D-Bus interface and also if other services require firewalld, enter the following command as root:

+ ----

+ $ sudo systemctl mask firewalld

+ ----

@@ -0,0 +1,40 @@ 

+ [[switching-desktop-environments-using-cli]]

+ = Switching desktop environments using CLI

+ 

+ .Before you start

+ 

+ Install the desired desktop environment as described in <<proc_installing-additional-desktop-enviroments.adoc#installing-desktop-environments,Installing additional desktop environments>>

+ 

+ Install the [package]`switchdesk` package:

+ 

+ ----

+ # dnf install switchdesk

+ ----

+ 

+ 

+ .Procedure

+ 

+ Pass the selected desktop environment as the only argument to the [command]`switchdesk` command, for example:

+ 

+ ----

+ # switchdesk kde

+ ----

+ 

+ .More information

+ 

+ See the `switchdesk(1)` man page.

+ 

+ Alternatively, edit the [filename]`/etc/sysconfig/desktop` file as *root*. This file specifies the desktop for new users and the display manager to run when entering runlevel 5.

+ 

+ Correct values are:

+ 

+ `DESKTOP="_<value>_"`, where `_<value>_` is one of the following:

+ 

+ 1. `GNOME` — Selects the GNOME desktop environment.

+ 2. `KDE` — Selects the KDE desktop environment.

+ 

+ `DISPLAYMANAGER="_<value>_"`, where `_<value>_` is one of the following:

+ 

+ 1. `GNOME` — Selects the GNOME Display Manager.

+ 2. `KDE` — Selects the KDE Display Manager.

+ 3. `XDM` — Selects the X Display Manager.

@@ -0,0 +1,32 @@ 

+ [[switching-desktop-environments-using-gui]]

+ = Switching desktop environments using GUI

+ 

+ .Before you start

+ 

+ Install the desired desktop environment as described in link:#installing-desktop-environments[Installing additional desktop environments].

+ 

+ .Procedure

+ 

+ To login with a different desktop for a single session:

+ 

+ . On the login screen, select a user from the list.

+ 

+ . Click on the Preferences icon right below the password field. A window appears with a list of several different desktop environments.

+ 

+ . Choose one, and enter password as usual.

+ 

+ image::switching-desktop-environments-login.png[Login Screen]

+ 

+ .More information

+ 

+ . Alternatively, install the [package]`switchdesk` and [package]`switchdesk-gui` packages:

+ +

+ ----

+ # dnf install switchdesk switchdesk-gui

+ ----

+ +

+ . Run the Desktop Switching Tool application.

+ 

+ . Select the default desktop from the list of available desktop environments, and confirm.

+ 

+ image::switching-desktop-environments-switchdesk.png[Desktop Switching Tool]

@@ -0,0 +1,20 @@ 

+ [[proc_testing-nested-virtualization]]

+ = Testing nested virtualization

+ 

+ . Start the virtual machine.

+ . On the virtual machine, run:

+ +

+ ----

+ # dnf group install virtualization

+ ----

+ +

+ . Verify that the virtual machine has virtualization correctly set up:

+ +

+ ----

+ # virt-host-validate

+   QEMU: Checking for hardware virtualization                                 : PASS

+   QEMU: Checking for device /dev/kvm                                         : PASS

+   QEMU: Checking for device /dev/vhost-net                                   : PASS

+   QEMU: Checking for device /dev/net/tun                                     : PASS

+   LXC: Checking for Linux >= 2.6.26                                          : PASS

+ ----

@@ -0,0 +1,60 @@ 

+ [id='troubleshooting_live_USB']

+ = Troubleshooting a live USB

+ 

+ 

+ == livecd-iso-to-disk problems

+ 

+ Partition isn't marked bootable:: If you get the message `Partition isn't marked bootable!`, you need to mark the partition bootable. To do this, run `parted /dev/sdX`, and use the `toggle N` boot command, where `_X_` is the appropriate letter, and `_N_` is the partition number. For example:

+ +

+ [option="nowrap"]

+ ----

+ $ parted /dev/sdb

+ GNU Parted 1.8.6

+ Using /dev/sdb

+ Welcome to GNU Parted! Type 'help' to view a list of commands.

+ (parted) print

+ Model: Imation Flash Drive (scsi)

+ Disk /dev/sdX: 1062MB

+ Sector size (logical/physical): 512B/512B

+ Partition Table: msdos

+ 

+ Number  Start   End     Size    Type     File system  Flags

+  1      32.3kB  1062MB  1062MB  primary  fat16

+ 

+ (parted) toggle 1 boot

+ (parted) print

+ Model: Imation Flash Drive (scsi)

+ Disk /dev/sdX: 1062MB

+ Sector size (logical/physical): 512B/512B

+ Partition Table: msdos

+ 

+ Number  Start   End     Size    Type     File system  Flags

+  1      32.3kB  1062MB  1062MB  primary  fat16        boot 

+ 

+ (parted) quit

+ Information: Don't forget to update /etc/fstab, if necessary.

+ ----

+ 

+ Partitions need a filesystem label:: If you get the message `Need to have a filesystem label` or `UUID` for your USB device, you need to label the partition: `dosfslabel /dev/sdX LIVE`.

+ 

+ Partition has different physical/logical endings:: If you get this message from fdisk, you may need to reformat the flash drive when writing the image, by passing `--format` when writing the stick. 

+ 

+ MBR appears to be blank:: If your test boot reports a corrupted boot sector, or you get the message `MBR appears to be blank.`, you need to install or reset the master boot record (MBR), by passing `--reset-mbr` when writing the stick.

+ 

+ livecd-iso-to-disk on other Linux distributions:: `livecd-iso-to-disk` is not meant to be run from a non-Fedora system. Even if it happens to run and write a stick apparently successfully from some other distribution, the stick may well fail to boot. Use of `livecd-iso-to-disk` on any distribution other than Fedora is unsupported and not expected to work: please use an alternative method, such as link:#using-fedora-media-writer[Fedora Media Writer].

+ 

+ 

+ == Testing a USB stick using qemu

+ 

+ You can test your stick using QEMU.

+ 

+ [options="nowrap"]

+ ----

+ # umount /dev/sdX1

+ $ qemu -hda /dev/sdX -m 1024 -vga std

+ ----

+ 

+ 

+ == Mounting a Live USB filesystem

+ 

+ You can use the https://github.com/livecd-tools/livecd-tools/blob/master/tools/liveimage-mount[liveimage-mount] script in the https://apps.fedoraproject.org/packages/livecd-tools[livecd-tools] package to mount an attached Live USB device or other LiveOS image, such as an ISO or Live CD. This is convenient when you want to copy in or out some file from the LiveOS filesystem on a Live USB, or just examine the files in a Live ISO or Live CD.

@@ -0,0 +1,69 @@ 

+ = Using the GRUB2 boot prompt

+ [[using-the-grub-2-boot-prompt]]

+ 

+ If improperly configured, *GRUB2* may fail to load and subsequently drop

+ to a boot prompt. To boot into the system, proceed as follows:

+ 

+ . Load the XFS and LVM modules

+ +

+ ----

+ insmod xfs

+ insmod lvm

+ ----

+ 

+ . List the drives which *GRUB2* sees:

+ +

+ ----

+ grub2> ls

+ ----

+ 

+ . Examine the output to understand the partition table of the `/dev/sda` device. The following example shows a DOS partition table with three partitions:

+ +

+ ----

+ (hd0) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)

+ ----

+ +

+ A GPT partition table of the `/dev/sda` device with four partitions could look like this:

+ +

+ ----

+ (hd0) (hd0,gpt4) (hd0,gpt3)  (hd0,gpt2) (hd0,gpt1)

+ ----

+ 

+ . Probe each partition of the drive and locate your `vmlinuz` and `initramfs` files.

+ +

+ ----

+ ls (hd0,1)/ 

+ ----

+ +

+ The outcome of the previous command will list the files on `/dev/sda1`. The partition that contains the `/boot` directory is the correct one. There you will search for the full names of the `vmlinuz` and `initramfs` files.

+ 

+ . Set the root partition.

+ +

+ ----

+ grub> set root=(hd0,3)

+ ----

+ +

+ This command tells the bootloader, that the root partition is the third partition on the first drive. This would correspond to the `/dev/sda3` device.

+ 

+ . Set the desired kernel.

+ +

+ ----

+ grub> linux (hd0,1)/vmlinuz-3.0.0-1.fc16.i686 root=/dev/sda3 rhgb quiet selinux=0 

+ # NOTE : add other kernel args if you need them

+ # NOTE : change the numbers to match your system

+ ----

+ 

+ . Set the desired `initrd`.

+ +

+ ----

+ grub> initrd (hd0,1)/initramfs-3.0.0-1.fc16.i686.img

+ # NOTE : change the numbers to match your system

+ ----

+ 

+ . Boot with the selected settings.

+ +

+ ----

+ grub> boot

+ ----

+ 

+ . To restore the bootloader's functionality, regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in xref:adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

@@ -0,0 +1,18 @@ 

+ [[using-old-graphics-modes]]

+ = Using old graphics modes in bootloader

+ 

+ The terminal device is chosen with GRUB_TERMINAL. For more information, see the link:http://www.gnu.org/software/grub/manual/grub.html#Simple-configuration[Grub manual].

+ 

+ Valid terminal output names depend on the platform, but may include `console` (PC BIOS and EFI consoles), `serial` (serial terminal), `gfxterm` (graphics-mode output), `ofconsole` (Open Firmware console), or `vga_text` (VGA text output, mainly useful with Coreboot).

+ 

+ The default is to use the platform's native terminal output.

+ 

+ In Fedora, `gfxterm` is the default options. To get the legacy graphics modes:

+ 

+ .Procedure

+ 

+ . Edit the `/etc/default/grub` file.

+ 

+ . Set the `GRUB_TERMINAL` variable to one of the above mentioned options.

+ 

+ . Regenerate the *GRUB2* configuration file and reinstall the bootloader into the MBR, as described in link:#adding-other-operating-systems-grub2[Adding other operating systems to the *GRUB2* menu].

@@ -0,0 +1,25 @@ 

+ [id='proc_using-same-password-for-root-as-user']

+ = Using the same password for root as the user account

+ 

+ If you use a single user desktop, you might find it convenient to configure [command]`sudo`, so you can use the same password to access *root* as you use for your regular account. To do this, select to be added to the Administration group during installation. To do it at later stage, or to add a different user, use the following procedure:

+ 

+ . Become the *root* user:

+ +

+ ----

+ $ su -

+ ----

+ +

+ . Enter the password for the root account when prompted.

+ 

+ . To use your regular password for the root access, run:

+ +

+ [subs=quotes]

+ ----

+ # usermod _USERNAME_ -a -G groupname

+ ----

+ +

+ Replace `_USERNAME_` with your account name

+ 

+ . Log off and back on in order to have access to the group. 

+ 

+ NOTE: When [command]`sudo` prompts you for a password, it expects your user password, not the `root` password.

@@ -0,0 +1,214 @@ 

+ [id='Configuring-networking-with-nmcli']

+ = Configuring networking with nmcli - quick reference

+ 

+ [[networkmanager-status]]

+ == NetworkManager status

+ 

+ Display overall status of NetworkManager:

+ ----

+ $ nmcli general status

+ ----

+ 

+ Display active connections:

+ ----

+ $ nmcli connection show --active

+ ----

+ 

+ Display all configured connections:

+ ----

+ $ nmcli connection show configured

+ ----

+ 

+ [[connectdisconnect-to-an-already-configured-connection]]

+ == Connect/disconnect to an already configured connection

+ 

+ Connect to a configured connection by name:

+ ----

+ $ nmcli connection up id <connection_name>

+ ----

+ 

+ Disconnection by name:

+ ----

+ $ nmcli connection down id <connection_name>

+ ----

+ 

+ [[wi-fi]]

+ == Wi-Fi

+ 

+ Get Wi-Fi status:

+ ----

+ $ nmcli radio wifi

+ ----

+ 

+ Turn Wi-Fi on or off:

+ ----

+ $ nmcli radio wifi _on|off_

+ ----

+ 

+ List available access points (AP) to connect to:

+ ----

+ $ nmcli device wifi list

+ ----

+ 

+ Refresh the previous list:

+ ----

+ $ nmcli device wifi rescan

+ ----

+ 

+ Create a new connection to an open AP:

+ ----

+ $ nmcli device wifi connect <SSID|BSSID>

+ ----

+ 

+ Create a new connection to a password protected AP:

+ ----

+ $ nmcli device wifi connect <SSID|BSSID> password <password>

+ ----

+ 

+ 

+ == Network interfaces

+ 

+ List available devices and their status:

+ ----

+ $ nmcli device status

+ ----

+ 

+ Disconnect an interface:

+ ----

+ $ nmcli device disconnect iface <interface>

+ ----

+ 

+ [[create-or-modify-a-connection]]

+ == Create or modify a connection

+ 

+ To create a new connection using an interactive editor

+ ----

+ $ nmcli connection edit con-name <name_of_new_connection>

+ ----

+ 

+ To edit an already existing connection using an interactive editor:

+ ----

+ $ nmcli connection edit <connection_name>

+ ----

+ 

+ [[exampletutorial]]

+ === Example/Tutorial

+ 

+ Create a new connection:

+ ----

+ $ nmcli connection edit con-name _name of new connection_

+ ----

+ 

+ It asks us to define a connection type:

+ ----

+ Valid connection types: 802-3-ethernet (ethernet), 802-11-wireless (wifi), wimax, gsm, cdma, infiniband, adsl, bluetooth, vpn, 802-11-olpc-mesh (olpc-mesh), vlan, bond, team, bridge, bond-slave, team-slave, bridge-slave

+ Enter connection type:

+ ----

+ 

+ In this example, we use ethernet:

+ ----

+ Enter connection type: ethernet

+ ----

+ 

+ The following message appears, note that `nmcli>` is a prompt and that it lists the main settings available:

+ ----

+ ===| nmcli interactive connection editor |===

+ 

+ Adding a new '802-3-ethernet' connection

+ 

+ Type 'help' or '?' for available commands.

+ Type 'describe [<setting>.<prop>]' for detailed property description.

+ 

+ You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6

+ nmcli>

+ ----

+ 

+ Edit the setting `ipv4`:

+ ----

+ nmcli> goto ipv4

+ ----

+ 

+ Note that after this our prompt has changed to indicate that we are currently editing the `ipv4` setting:

+ ----

+ nmcli ipv4>

+ ----

+ 

+ List available properties under the `ipv4` setting and describe the `method` property:

+ ----

+ nmcli ipv4> describe

+ 

+ Available properties: method, dns, dns-search, addresses, routes, ignore-auto-routes, ignore-auto-dns, dhcp-client-id, dhcp-send-hostname, dhcp-hostname, never-default, may-fail

+ Property name?

+ 

+ Property name? method

+ ----

+ 

+ Set property `method` to `auto`:

+ ----

+ nmcli ipv4> set method auto

+ ----

+ 

+ The `ipv4` setting is now finished. Go back to the main level. Enter the following command until the prompt looks like `nmcli>`:

+ ----

+ nmcli ipv4> back

+ ----

+ 

+ To list the main settings again, use the `goto` command without any arguments. After that, press `Enter` and ignore the error.

+ ----

+ nmcli> goto

+ 

+ Available settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6

+ Setting name?

+ ----

+ 

+ It is possible to set a value for a property directly from the main level:

+ ----

+ nmcli> set __setting__.__property__ _value_

+ ----

+ 

+ For example:

+ ----

+ nmcli> set connection.autoconnect TRUE

+ 

+ nmcli> set connection.interface-name _interface name this connection is bound to_

+ 

+ nmcli> set ethernet.cloned-mac-address _Spoofed MAC address_

+ ----

+ 

+ Finally, check the connection details, save and exit:

+ ----

+ nmcli> print

+ 

+ nmcli> save

+ 

+ nmcli> quit

+ ----

+ 

+ [[manually-editing]]

+ === Manually editing

+ 

+ To manually edit an `ifcfg` connection configuration, open or create with a text editor the configuration file of the connection located in `/etc/sysconfig/network-scripts/ifcfg-`.

+ 

+ A description of most common configuration options is available in the link:http://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html[RHEL6 Deployment Guide].

+ 

+ To modify a connection password, open with a text editor and edit the file `keys-` located in `/etc/sysconfig/network-scripts/`. The password is stored in plain text. For example:

+ ----

+ $ cat /etc/sysconfig/network-scripts/keys-__connection name__

+ WPA_PSK='password'

+ ----

+ 

+ Or, if using keyfile, simply edit the connection file located inside `/etc/NetworkManager/system-connections/`

+ 

+ Finally, save the files and to apply changes to an already active connection execute.

+ ----

+ nmcli connection up id _connection name_

+ ----

+ 

+ [[delete-a-connection-configuration]]

+ == Delete a connection configuration

+ 

+ Delete the connection:

+ ----

+ nmcli connection delete id <connection_name>

+ ----

+ Please note that this also deactivates the connection.

@@ -0,0 +1,31 @@ 

+ // Module included in the following assemblies:

+ //

+ // assembly_changing-selinux-states-and-modes.adoc

+ 

+ [#{context}-Enabling_and_Disabling_SELinux-Dracut-parameters]

+ = Changing SELinux Modes at Boot Time

+ 

+ On boot, you can set several kernel parameters to change the way SELinux runs:

+ 

+ enforcing=0::  Setting this parameter causes the machine to boot in permissive mode, which is useful when troubleshooting issues. Using permissive mode might be the only option to detect a problem if your file system is too corrupted. Moreover, in permissive mode the system continues to create the labels correctly. The AVC messages that are created in this mode can be different than in enforcing mode. In permissive mode, only the first denial is reported. However, in enforcing mode you might get a denial on reading a directory and an application stops. In permissive mode, you get the same AVC message, but the application continues reading files in the directory and you get an AVC for each denial in addition.

+ 

+ selinux=0::  This parameter causes the kernel to not load any part of the SELinux infrastructure. The init scripts notice that the system booted with the [option]`selinux=0` parameter and touch the `/.autorelabel` file. This causes the system to automatically relabel the next time you boot with SELinux enabled.

+ +

+ [IMPORTANT]

+ ====

+ Using the [option]`selinux=0` parameter is not recommended. To debug your system, prefer using permissive mode.

+ ====

+ 

+ autorelabel=1::  This parameter forces the system to relabel similarly to the following commands:

+ +

+ ----

+ ~]# touch /.autorelabel

+ ~]# reboot

+ ----

+ +

+ If the system labeling contains a large amount of errors, you might need to boot in permissive mode in order that the autorelabel succeeds.

+ 

+ For additional SELinux-related kernel boot parameters, such as [option]`checkreqprot`, see the `kernel-parameters.txt` file. This file is available in the source package of your Linux kernel (.src.rpm). To download the source package containing the currently used kernel:

+ ----

+ ~]# dnf download --source kernel

+ ----

@@ -0,0 +1,118 @@ 

+ [#common-service-parameters]

+ = Common service parameters

+ 

+ .Unit Parameters

+ 

+ This section contains parameters you can use in the `[Unit]` section of a service. These parameters are common to other systemd units.

+ 

+ This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`.

+ 

+ Description::

+   A free-form string describing the service. 

+ 

+ Documentation::

+   A space-separated list of URIs referencing documentation for this service or its configuration. Accepted are only URIs of the following types: `http://`, `https://`, `file:`, `info:`, `man:`. 

+ 

+ Requires::

+   Configures requirement dependencies on other services. If this service gets activated, the units listed here are activated too. If one of the dependent services fails to activate, systemd does not start this service. This option may be specified more than once or you can specify multiple space-separated units.

+ 

+ Wants::

+   Similar to `Requires`, except failed units do not have any effect on the service.

+ 

+ BindsTo::

+   Similar to `Requires`, except stopping the dependent units also stops the service.

+ 

+ PartOf::

+   Similar to `Requires`, except the stopping and restarting dependent units also stop and restart the service.

+ 

+ Conflicts::

+   A space-separated list of unit names that, if running, cause the service not to run.

+ 

+ Before, After::

+   A space-separated list of unit names that configures the ordering of dependencies between services.

+ 

+ OnFailure::

+   A space-separated list of unit names that are activated when this service enters a failed state.

+ 

+ .Install Parameters

+ 

+ This section contains parameters you can use in the `[Install]` section of a service. These parameters are common to other systemd units.

+ 

+ This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`.

+ 

+ Alias::

+     A space-separated list of additional names this service shall be installed under. The names listed here must have the same suffix (i.e. type) as the service filename.

+ 

+ RequiredBy, WantedBy::

+     Defines the service as dependent of another service. This usually define the target to trigger an enabled service to run. These options are analogous to the `Requires` and `Wants` in the `[Units]` section.

+ 

+ Also::

+     Additional units to install or uninstall when this service is installed or uninstalled.

+ 

+ .Service Parameters

+ 

+ This section contains parameters you can use in the `[Service]` section of a service unit. These parameters are specific only to systemd service units.

+ 

+ This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`.

+ 

+ Type::

+   Configures the process start-up type for this service service:

+ +

+ * `simple` - The service starts as the main process. This is the default.

+ * `forking` - The service calls forked processes and run as part of the main daemon.

+ * `oneshot` - Similar to `simple`, except the process must exits before systemd starts follow-up services.

+ * `dbus` - Similar to `simple`, except the daemon acquires a name of the D-Bus bus.

+ * `notify` - Similar to `simple`, except the daemon sends a motification message using `sd_notify` or an equivalent call after starting up.

+ * `idle` - Similar to `simple`, except the execution of the service is delayed until all active jobs are dispatched.

+ 

+ RemainAfterExit::

+   A boolean value that specifies whether the service shall be considered active even if all its processes exited. Defaults to no.

+ 

+ GuessMainPID::

+   A boolean value that specifies whether systemd should guess the main PID of a service if it cannot be determined reliably. This option is ignored unless `Type=forking` is set and `PIDFile` is not set. Defaults to yes.

+ 

+ PIDFile::

+   An absolute filename pointing to the PID file of this daemon. Use of this option is recommended for services where `Type=forking`. systemd reads the PID of the main process of the daemon after start-up of the service. systemd does not write to the file configured here, although it removes the file after the service has shut down. 

+ 

+ BusName::

+   A D-Bus bus name to reach this service. This option is mandatory for services where `Type=dbus`.

+ 

+ ExecStart::

+   The commands and arguments executed when the service starts.

+ 

+ ExecStartPre, ExecStartPost::

+   Additional commands that are executed before or after the command in `ExecStart`.

+ 

+ ExecReload::

+   The commands and arguments to execute when the service reloads.

+ 

+ ExecStop::

+   The commands and arguments to execute when the service stops. 

+ 

+ ExecStopPost::

+   Additional commands to executed after the service stops.

+ 

+ RestartSec::

+   The time in seconds to sleep before restarting a service.

+ 

+ TimeoutStartSec::

+   The time in seconds to wait for the service to start.

+ 

+ TimeoutStopSec::

+   The time in seconds to wait for the service to stop.

+ 

+ TimeoutSec::

+   A shorthand for configuring both `TimeoutStartSec` and `TimeoutStopSec` simultaneously. 

+ 

+ RuntimeMaxSec::

+   A maximum time in seconds for the service to run. Pass `infinity` (the default) to configure no runtime limit.

+ 

+ Restart::

+   Configures whether to restart the service when the service's process exits, is killed, or reaches a timeout:

+ +

+ * `no` - The service will not be restarted. This is the default.

+ * `on-success` - Restart only when the service process exits cleanly (exit code 0).

+ * `on-failure` - Restart only when the service process does not exit cleanly (node-zero exit code).

+ * `on-abnormal` - Restart if the process terminates with a signal or when a timeout occurs.

+ * `on-abort` - Restart if the process exits due to an uncaught signal not specified as a clean exit status.

+ * `always` - Always restart.

@@ -0,0 +1,224 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: my-reference-a.adoc

+ // * ID: [id='my-reference-a']

+ // * Title: = My reference A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='reference-material_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Fedora on Raspberry Pi: Frequently Asked Questions

+ //In the title of a reference module, include nouns that are used in the body text. For example, "Keyboard shortcuts for ___" or "Command options for ___." This helps readers and search engines find the information quickly.

+ 

+ Frequently asked questions regarding what is supported.

+ 

+ ._Why do I get a rainbow display when I try and power on my Raspberry Pi?_

+ 

+ Common causes of the rainbow display include:

+ 

+ * Insufficient power supply. See the xref:raspberry-pi-prerequisites[Prerequisites] section at the beginning of this document.

+ 

+ * There's no operating system installed. Check that an operating system was installed and the microSD card was properly inserted into the Raspberry Pi.

+ For instructions about Fedora ARM on Raspberry Pi:

+ ** For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}>>.

+ ** For users of other Linux distributions, see: <<installing-fedora-on-a-raspberry-pi-for-linux-users_{context}>>.

+ ** For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}>>.

+ ** For Apple OS X users, see: <<installing-fedora-on-a-raspberry-pi-for-apple-macos-users_{context}>>.

+ 

+ * If you try to use Fedora on a Raspberry Pi 1, Raspberry Pi Zero, or a Raspberry Pi model A, you will receive the rainbow display. This occurs because your Raspberry Pi is not supported (ARMv6 SoCs architectures are not supported).

+ 

+ ._What desktop environments are supported?_

+ 

+ All desktops as shipped in Fedora should work and both 2D and 3D graphics work out of the box.

+ There is an open source fully accelerated driver for the Video Core IV GPU.

+ 

+ ._Will there be more enhancements to the hardware support?_

+ 

+ Yes.

+ New enhancements will be delivered by the standard Fedora updates mechanism.

+ New, significant features will be announced by the link:https://fedoramagazine.org/[Fedora Magazine] or the link:http://fedoraplanet.org/[Fedora Planet].

+ 

+ ._What about support for the Raspberry Pi Models A/A+, B/B+ (generation 1), Zero/ZeroW and Compute Module?_

+ 

+ These Raspberry Pi models are not supported.

+ 

+ Fedora is not supported on ARMv6 processors.

+ There's been a number of attempts to support these over the years.

+ The current best effort is Pignus based on Fedora 23.

+ More information can be found at link:https://pignus.computer[the Pignus site].

+ 

+ NOTE: Fedora DOES support the Compute Module 3 based on the same SoC as the Raspberry Pi 3, but *as the previous generation Compute Modules are based on ARMv6 architecture, they are [#.underline]#not supported#*.

+ 

+ ._What USB devices are supported on the Raspberry Pi?_

+ 

+ Most USB-2 compatible devices that are supported in Fedora on other devices.

+ There are some limitations to the USB bus of the Raspberry Pi hardware as link:https://www.raspberrypi.org/documentation/hardware/raspberrypi/usb/README.md[documented here].

+ 

+ ._Is the onboard Wi-Fi supported on the Raspberry Pi 3?_

+ 

+ Wi-Fi on the Raspberry Pi 3 and 3+ works in Fedora.

+ 

+ The drivers required for the onboard WiFi cannot be included in the Fedora ARM image. After Fedora has been installed on a microSD card and Fedora on Raspberry Pi has been booted for the first time, you can install the WiFi drivers using an ethernet internet connection.

+ 

+ *Raspberry Pi 3*

+ 

+ . To install support for the onboard WiFi, on a command-line, issue:

+ +

+ ----

+ $ sudo curl https://fedora.roving-it.com/brcmfmac43430-sdio.txt -o /lib/firmware/brcm/brcmfmac43430-sdio.txt

+ ----

+ +

+ . Reboot the Raspberry Pi to access the WiFi.

+ 

+ *Raspberry Pi 3B+*

+ 

+ . To install support for the onboard WiFi, on a command-line, issue:

+ +

+ ----

+ $ sudo curl https://fedora.roving-it.com/brcmfmac43455-sdio.txt -o /lib/firmware/brcm/brcmfmac43455-sdio.txt

+ $ sudo curl https://fedora.roving-it.com/brcmfmac43455-sdio.clm_blob -o /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob

+ ----

+ +

+ . Reboot the Raspberry Pi to access the WiFi.

+ 

+ *Using Wi-Fi on CLI*

+ 

+ To use Wi-Fi on minimal and server images you can configure the device using command line:

+ 

+ * To list available networks:

+ +

+ ----

+ $ nmcli device wifi list

+ ----

+ 

+ * To connect to a network:

+ +

+ [subs="quotes"]

+ ----

+ nmcli device wifi connect __$SSID__ --ask

+ ----

+ +

+ Where: `_$SSID_` is the network identifier (or name).

+ 

+ ._Is the onboard Bluetooth supported on the Raspberry Pi 3?_

+ 

+ Bluetooth works and is stable. The device sometimes has a generic bluetooth address but should work without any configuration.

+ 

+ ._Does sound work?_

+ 

+ HDMI audio output is included with Fedora, however, the analog port is not yet supported.

+ Audio output using a USB audio interface should work.

+ 

+ ._Does the add-on camera work?_

+ 

+ Not at this time.

+ There is still ongoing work to support this upstream and to add the appropriated media acceleration support.

+ 

+ ._Does accelerated media decode work?_

+ 

+ No.

+ The upstream kernel does not support the kernel subsystems required for accelerated media decoding.

+ 

+ ._Does HDMI-CEC work?_

+ 

+ Yes.

+ Yes. It's supported using the new upstream CEC support. There's a `/dev/cec0` character device, it can be accessed using any application that supports the IR remote using the `rc-cec` keymap in the `v4l-utils` package, there's also a `cec-ctl` utility for use on the command line.

+ 

+ ._Is the Raspberry Pi Touch Display supported?_

+ 

+ Work on the official Raspberry Pi Touch Display is ongoing upstream and initial support is provided in the 4.10 kernel, see: link:https://github.com/anholt/linux/issues/8[GitHub: raspberrypi/linux issues - 7" LCD touchscreen not supported].

+ Fedora will review any missing pieces for support soon.

+ The touchscreen driver isn't yet released upstream.

+ Support for other displays is not currently planned.

+ 

+ ._Is the composite TV out supported?_

+ 

+ The composite TV out is not currently supported in a stable Fedora release but the core support is in the 4.10 kernel.

+ There is some missing enabling patches which will be added to the Fedora kernel soon.

+ 

+ ._Are the expansion HATs supported?_

+ 

+ The the expansion HATs are not currently supported.

+ 

+ The long answer is a lot more complex. Most of the hardware interfaces that are exposed by the 40 pin HAT connector are supported with drivers shipped with Fedora.

+ 

+ Drivers for the hardware contained on a lot of the common HATs are also enabled and supported in Fedora. The core means of supporting the HAT add-on boards require the use of device tree overlays. The kernel and the u-boot 2016.09 boot-loader supports the loading over overlays manually. Currently there is no upstream consensus on the means of autoloading these overlays by means of an "overlay manager" (also known as Cape Manager and by numerous other names) by reading the EEPROM ID and loading the appropriate overlay automatically.

+ 

+ There's also no consensus on the extensions to the dtc (Device Tree Compiler) to build the binary blob overlays, and no consensus of the exact format of the overlay file. There is now a group of people working to resolve this issue which enable Fedora to better support HATs (Raspberry Pi), Capes (BeagleBone), DIPs (C.H.I.P) and Mezzanine (96boards) before long.

+ 

+ The first focus HAT to support will be the official Raspberry Pi Sense HAT. This will be documented using the manual process to build and load the overlay to provide access to the onboard devices as a means of demonstrating how this process works for those wishing to use this manual method in the interim. The link to this documentation will be added here once that is complete.

+ 

+ ._The use of config.txt_

+ 

+ The `config.txt` is only used for basic configuration at the moment. Because of the use of the opensource vc4 GPU driver, most of the video configuration is done by Linux.

+ 

+ The configuration of HATs using `config.txt` is unsupported but is being actively developed.

+ 

+ ._Are Device Tree Overlays supported?_

+ 

+ There's basic support for overlays in u-boot and the Linux kernel but an overlay manager is not supported upstream.

+ 

+ ._Is GPIO supported?_

+ 

+ GPIO isn't fully supported due to lack of mapping with the Device Tree overlays.

+ This is expected be improved in the Fedora 28 cycle and in Fedora 29.

+ 

+ ._Is SPI supported?_

+ 

+ Yes, basic SPI is supported.

+ 

+ ._Is I2C supported?_

+ 

+ Yes, basic I2C is supported.

+ 

+ ._Is there Raspberry Pi 3 aarch64 support?_

+ 

+ Yes! You can download the aarch64 disk images for the Raspberry Pi 3 link:https://archive.fedoraproject.org/pub/fedora-secondary/releases/[here.]

+ 

+ ._How do I use a serial console?_

+ 

+ The serial console is disabled by default on the Raspberry Pi 2 and 3 because it requires the device to run at significantly slower speeds.

+ 

+ To wire up the USB to TTL adapter follow link:https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable/connect-the-lead[this guide from Adafruit].

+ You'll need a 3.3 volt USB to TTL Serial Cable like link:https://www.adafruit.com/product/954[this one from Adafruit].

+ 

+ To enable the serial console follow the specific steps for the Raspberry Pi 2 or 3 as they both differ slightly:

+ 

+ *Raspberry Pi 2:*

+ 

+ . Insert the microSD card into a PC

+ . On the VFAT partition edit the `config.txt` file and uncomment the `enable_uart` line:

+ +

+ ----

+ $ enable_uart=1

+ ----

+ +

+ . On the boot partition edit the `extlinux/extlinux.conf` file adding `console=tty0 console=ttyAMA0,115200` to the end of the append line so it looks similar to:

+ +

+ ----

+ $ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyAMA0,115200

+ ----

+ +

+ . Safely unmount the microSD card

+ . Insert microSD into Raspberry Pi, connect serial console, power on

+ 

+ *Raspberry Pi 3:*

+ 

+ . Insert the microSD card into a PC

+ . On the VFAT partition edit the `config.txt` file and uncomment the `enable_uart` line:

+ +

+ ----

+ $ enable_uart=1

+ ----

+ +

+ . On the boot partition edit the `extlinux/extlinux.conf` file adding: `console=tty0 console=ttyS0,115200` to the end of the append line so it looks similar to:

+ +

+ ----

+ $ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyS0,115200

+ ----

+ +

+ . Safely unmount the microSD card

+ . Insert microSD into Raspberry Pi, connect serial console, power on

@@ -0,0 +1,37 @@ 

+ // Module included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Base the file name and the ID on the module title. For example:

+ // * file name: help-mkpart.adoc

+ // * ID: [id='help-mkpart']

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='help-mkpart_{context}']

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ = Help command for creating a new partition

+ 

+ To get help on how to make a new partition, type: `help mkpart`.

+ 

+ ----

+ (parted) help mkpart

+   mkpart PART-TYPE [FS-TYPE] START END     make a partition

+ 

+         PART-TYPE is one of: primary, logical, extended

+         FS-TYPE is one of: btrfs, nilfs2, ext4, ext3, ext2, fat32, fat16, hfsx, hfs+, hfs, jfs, swsusp,

+         linux-swap(v1), linux-swap(v0), ntfs, reiserfs, hp-ufs, sun-ufs, xfs, apfs2, apfs1, asfs, amufs5,

+         amufs4, amufs3, amufs2, amufs1, amufs0, amufs, affs7, affs6, affs5, affs4, affs3, affs2, affs1,

+         affs0, linux-swap, linux-swap(new), linux-swap(old)

+         START and END are disk locations, such as 4GB or 10%.  Negative values count from the end of the

+         disk.  For example, -1s specifies exactly the last sector.

+        

+         'mkpart' makes a partition without creating a new file system on the partition.  FS-TYPE may be

+         specified to set an appropriate partition ID.

+ ----

+ 

+ [NOTE]

+ ====

+ * Filesystem type (fstype) will not create an ext4 filesystem on /dev/vdc1. 

+ * A DOS partition table's partition types are primary, logical, and extended. 

+ * Providing a partition name under GPT is a must. In a GPT partition table, the partition type is used as the partition name.

+ ====

@@ -0,0 +1,58 @@ 

+ [i='jdk-reference']

+ = JDK reference

+ 

+ See the following list of Java-related acronyms for reference:

+ 

+ JRE:: Java Runtime Environment; equired to run Java code and applications

+ JVM:: Java Virtual Machine; main component of the JRE

+ JDK:: Java Development Kit; required only for development, coding

+ SDK:: Software Development Kit; see JDK

+ JavaWS:: link:https://en.wikipedia.org/wiki/Java_Web_Start[Java Web Start] is a framework to start application from the Internet

+ JavaFX:: link:https://en.wikipedia.org/wiki/JavaFX[JavaFX] is a plateform to create and deliver desktop and Rich Internet Apps

+ OpenJFX:: is the JavaFX Open Source implementation

+ OpenJDK:: Open Source project behind the Java Platform link:http://openjdk.java.net/[openjdk.java.net].

+ IcedTea:: is a support project for OpenJDK (concern only developers) link:http://icedtea.classpath.org/[icedtea.classpath.org]

+ IcedTea-Web:: is the Java Web Start package (contains only JavaWS, no applets anymore); install to run *JNPL* files

+ applets:: are obsolete technology; Not implemented in any recent package

+ JSE, J2SE, JEE, ...:: obsolete acronyms for Java Standard & Enterprise Edition; JavaSE is like JRE

+ 

+ 

+ [discrete]

+ [id='jdk-components']

+ == JDK components

+ 

+ The JDK has as its primary components a collection of programming tools, including:

+ 

+ `appletviewer`:: this tool can be used to run and debug Java applets without a web browser

+ `apt`:: the annotation-processing tool

+ `extcheck`:: a utility which can detect JAR-file conflicts

+ `idlj`:: the IDL-to-Java compiler. This utility generates Java bindings from a given Java IDL file.

+ `jabswitch`:: the Java Access Bridge. Exposes assistive technologies on Microsoft Windows systems.

+ `java`:: the loader for Java applications. This tool is an interpreter and can interpret the class files generated by the javac compiler. Now a single launcher is used for both development and deployment. The old deployment launcher, jre, no longer comes with Sun JDK, and instead it has been replaced by this new java loader.

+ `javac`:: the Java compiler, which converts source code into Java bytecode

+ `javadoc`:: the documentation generator, which automatically generates documentation from source code comments

+ `jar`:: the archiver, which packages related class libraries into a single JAR file. This tool also helps manage JAR files.

+ `javafxpackager`:: tool to package and sign JavaFX applications

+ `jarsigner`:: the jar signing and verification tool

+ `javah`:: the C header and stub generator, used to write native methods

+ `javap`:: the class file disassembler

+ `javaws`:: the Java Web Start launcher for JNLP applications

+ `JConsole`:: Java Monitoring and Management Console

+ `jdb`:: the debugger

+ `jhat`:: Java Heap Analysis Tool (experimental)

+ `jinfo`:: This utility gets configuration information from a running Java process or crash dump. (experimental)

+ `jmap`:: This utility outputs the memory map for Java and can print shared object memory maps or heap memory details of a given process or core dump. (experimental)

+ `jmc`:: Java Mission Control

+ `jps`:: Java Virtual Machine Process Status Tool lists the instrumented HotSpot Java Virtual Machines (JVMs) on the target system. (experimental)

+ `jrunscript`:: Java command-line script shell.

+ `jstack`:: utility which prints Java stack traces of Java threads (experimental)

+ `jstat`:: Java Virtual Machine statistics monitoring tool (experimental)

+ `jstatd`:: jstat daemon (experimental)

+ `keytool`:: tool for manipulating the keystore

+ `pack200`:: JAR compression tool

+ `policytool`:: the policy creation and management tool, which can determine policy for a Java runtime, specifying which permissions are

+ `available for code from various sources VisualVM`:: visual tool integrating several command-line JDK tools and lightweight clarification needed] performance and memory profiling capabilities

+ `wsimport`:: generates portable JAX-WS artifacts for invoking a web service.

+ `xjc`:: Part of the Java API for XML Binding (JAXB) API. It accepts an XML schema and generates Java classes.

+ 

+ The JDK also comes with a complete Java Runtime Environment, usually called a private runtime, due to the fact that it is separated from the "regular" JRE and has extra contents. It consists of a Java Virtual Machine and all of the class libraries present in the production environment, as well as additional libraries only useful to developers, such as the internationalization libraries and the IDL libraries.

@@ -0,0 +1,103 @@ 

+ [id='ref_managing-virtual-machines']

+ = Managing virtual machines

+ 

+ When the installation of the guest operating system is complete, it can be managed using the `virt-manager` program or via command line using `virsh`.

+ 

+ 

+ [[managing-guests-with-virt-manager]]

+ == Managing guests with virt-manager

+ 

+ . Start the Virtual Machine Manager by navigating to menu:[Applications]System Tools, or run:

+ +

+ ----

+ # virt-manager

+ ----

+ +

+ If you are not root, you will be prompted to enter the root password. Choose *Run unprivileged* to operate in read-only non-root mode.

+ . Choose the host you wish to manage and click *Connect* in the *Open Connection* dialog window.

+ . The list of virtual machines is displayed in the main window. Guests that are running will display a ">" icon. Guests that are not running will be greyed out.

+ . To manage a particular guest, double click on it, or right click and select *Open*.

+ . A new window for the guest will open that will allow you to use its console, see information about its virtual hardware and start, stop, and pause it.

+ 

+ For further information about `virt-manager`, see http://virt-manager.et.redhat.com/.

+ 

+ Bugs in the `virt-manager` tool should be reported in http://bugzilla.redhat.com[Bugzilla] against the `virt-manager`

+ component.

+ 

+ 

+ [[managing-guests-with-virsh]]

+ == Managing guests with virsh

+ 

+ The `virsh` command-line utility allows you to manage virtual machines on the command line. The `virsh` utility is built around the libvirt management API:

+ 

+ * `virsh` has a stable set of commands whose syntax and semantics are preserved across updates to the underlying virtualization platform.

+ * `virsh` can be used as an unprivileged user for read-only operations (e.g. listing domains, listing domain statistics).

+ * `virsh` can manage domains running under Xen, QEMU/KVM, ESX, or other back-ends with no perceptible difference to the user.

+ 

+ To start a virtual machine:

+ 

+ ----

+ # virsh create <name of virtual machine>

+ ----

+ 

+ To list the virtual machines currently running:

+ 

+ ----

+ # virsh list

+ ----

+ 

+ To list all virtual machines, running or not:

+ 

+ ----

+ # virsh list --all

+ ----

+ 

+ To gracefully power off a guest:

+ 

+ ----

+ # virsh shutdown <virtual machine (name | id | uuid)>

+ ----

+ 

+ To non gracefully power off a guest:

+ 

+ ----

+ # virsh destroy <virtual machine (name | id | uuid)>

+ ----

+ 

+ To save a snapshot of the machine to a file:

+ 

+ ----

+ # virsh save <virtual machine (name | id | uuid)> <filename>

+ ----

+ 

+ To restore a previously saved snapshot:

+ 

+ ----

+ # virsh restore <filename>

+ ----

+ 

+ To export the configuration file of a virtual machine:

+ 

+ ----

+ # virsh dumpxml <virtual machine (name | id | uuid)

+ ----

+ 

+ For a complete list of commands available for use with `virsh`:

+ 

+ ----

+ # virsh help

+ ----

+ 

+ Or consult the manual page: `man virsh`.

+ 

+ Bugs in the `virsh` tool should be reported in http://bugzilla.redhat.com[Bugzilla] against the *libvirt* component.

+ 

+ 

+ [[remote-management]]

+ == Remote management

+ 

+ The following remote management options are available:

+ 

+ * If using non-root users via SSH, see the setup instructions in http://wiki.libvirt.org/page/SSHSetup

+ * If using root for access via SSH, then create SSH keys for root, and use `ssh-agent` and `ssh-add` before launching `virt-manager`.

+ * To use TLS, set up a local certificate authority and issue x509 certs to all servers and clients. For information on configuring this option, see http://wiki.libvirt.org/page/TLSSetup.

@@ -0,0 +1,31 @@ 

+ [#mapping-runlevels-to-targets]

+ = Mapping runlevels to targets

+ 

+ systemd targets serve a similar purpose to SysVinit runlevels but act a little different. Each target has a name instead of a number and each serves a specific purpose. systemd implements some targets by inheriting all of the services of another target and adding additional services to it. Some systemd targets mimic the common sysvinit runlevels, which means you can switch targets with the familiar `telinit RUNLEVEL` command. The runlevels assigned a specific purpose on vanilla Fedora installs (0, 1, 3, 5, and 6) have a 1:1 mapping with a specific systemd target.

+ 

+ However, this is not the case for user-defined runlevels 2 and 4. To make use of those runlevels, create a new named systemd target such as `/etc/systemd/system/$YOURTARGET` that takes one of the existing runlevels as a base, make a directory `/etc/systemd/system/$YOURTARGET.wants`, and then symlink the additional services to enable into that directory.

+ 

+ The following is a mapping of SysVinit runlevels to systemd targets.

+ 

+ [cols="2,5,5",options="header"]

+ .Runlevel to target mapping

+ |===

+ |Sysvinit Runlevel |systemd Target |Notes

+ 

+ |0 |runlevel0.target, poweroff.target |Halt the system.

+ 

+ |1, s, single |runlevel1.target, rescue.target |Single user mode.

+ 

+ |2, 4 |runlevel2.target, runlevel4.target, multi-user.target

+ |User-defined/Site-specific runlevels. By default, identical to 3.

+ 

+ |3 |runlevel3.target, multi-user.target |Multi-user, non-graphical.

+ Users can usually login via multiple consoles or via the network.

+ 

+ |5 |runlevel5.target, graphical.target |Multi-user, graphical. Usually

+ has all the services of runlevel 3 plus a graphical login.

+ 

+ |6 |runlevel6.target, reboot.target |Reboot

+ 

+ |emergency |emergency.target |Emergency shell

+ |=== 

\ No newline at end of file

@@ -0,0 +1,42 @@ 

+ [#mapping-service-commands]

+ = Mapping service commands

+ 

+ The following table demonstrates the systemd equivalent of SysVinit commands.

+ 

+ NOTE: All recent versions of systemctl assume the `.service` suffix if left off the service name. For example, `systemctl start frobozz.service` is the same as `systemctl start frobozz`.

+ 

+ [cols=",,",options="header",]

+ |===

+ |Sysvinit Command |systemd Command |Notes

+ |`service frobozz start`|`systemctl start frobozz`|Used to start a service (not reboot persistent)

+ 

+ |`service frobozz stop`|`systemctl stop frobozz`|Used to stop a service (not reboot persistent)

+ 

+ |`service frobozz restart`|`systemctl restart frobozz`|Used to stop and then start a service

+ 

+ |`service frobozz reload`|`systemctl reload frobozz`|When supported, reloads the config file without interrupting pending operations.

+ 

+ |`service frobozz condrestart`|`systemctl condrestart frobozz`|Restarts if the service is already running.

+ 

+ |`service frobozz status`|`systemctl status frobozz`|Tells whether a service is currently running.

+ 

+ |`ls /etc/rc.d/init.d/`|`systemctl` or `systemctl list-unit-files --type=service` or +

+ `ls /lib/systemd/system/*.service /etc/systemd/system/*.service`|Used to list the services that can be started or stopped +

+ Used to list all the services and other units

+ 

+ |`chkconfig frobozz on`|`systemctl enable frobozz`|Turn the service on, for start at next boot, or other trigger.

+ 

+ |`chkconfig frobozz off`|`systemctl disable frobozz`|Turn the service off for the next reboot, or any other trigger.

+ 

+ |`chkconfig frobozz`|`systemctl is-enabled frobozz`|Used to check whether a service is configured to start or not in the current environment.

+ 

+ |`chkconfig --list`|`systemctl list-unit-files --type=service` or `ls /etc/systemd/system/*.wants/`|Print a table of services that lists which runlevels each is configured on or off

+ 

+ |`chkconfig --list \| grep 5:on`|`systemctl list-dependencies graphical.target`|Print a table of services that will be started when booting into graphical mode

+ 

+ |`chkconfig frobozz --list`|`ls /etc/systemd/system/*.wants/frobozz.service`|Used to list what levels this service is configured on or off

+ 

+ |`chkconfig frobozz --add`|`systemctl daemon-reload`|Used when you create a new service file or modify any configuration

+ |===

+ 

+ NOTE: All `/sbin/service` and `/sbin/chkconfig` commands listed in the table continue to work on systemd-based systems and are translated to native equivalents as necessary. The only exception is `chkconfig --list`.

@@ -0,0 +1,37 @@ 

+ [[other-virtualization-options]]

+ = Other virtualization options

+ 

+ [[qemukvm-without-libvirt]]

+ == QEMU/KVM without libvirt

+ 

+ QEMU/KVM can be invoked directly without libvirt, however you cannot to use tools such as `virt-manager`, `virt-install`, or `virsh`. Plain QEMU (without KVM) can also virtualize other processor architectures like ARM or PowerPC. 

+ 

+ [[xen]]

+ == Xen

+ 

+ Fedora can run as a Xen guest operating system and also be used as a Xen host (with the latter being true from Fedora 16; for using an earlier version of Fedora as a Xen host, check out the experimental repo available at http://myoung.fedorapeople.org/dom0). For a guide on how to install and setup a Fedora Xen host, see http://wiki.xen.org/wiki/Fedora_Host_Installation[Fedora Host Installation] page on the Xen Project wiki.

+ 

+ [[openstack]]

+ == OpenStack

+ 

+ OpenStack consists of a number of services for running infrastructure as a service (IaaS) clouds. They are the Object Store (Swift), Compute (Nova), and Image (Glance) services.

+ 

+ [[opennebula]]

+ == OpenNebula

+ 

+ OpenNebula is an open source toolkit for data center virtualization.

+ 

+ [[ovirt]]

+ == oVirt

+ 

+ The https://www.ovirt.org/[oVirt project] is an open virtualization

+ project providing a end-to-end, server virtualization

+ management system with advanced capabilities for hosts and guests,

+ including high availability, live migration, storage management, system

+ scheduler, and more.

+ 

+ [[troubleshooting-and-known-issues]]

+ = Troubleshooting and known issues

+ 

+ For a list of known unresolved issues, as well as troubleshooting tips,

+ see FIXME link:How_to_debug_Virtualization_problems[How to debug virtualization problems]

modules/ROOT/pages/_partials/ref_the-most-useful-dnf-commands.adoc en-US/modules/ref_the-most-useful-dnf-commands.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,45 @@ 

+ [[virtio-win-rpm-contents]]

+ = RPM contents

+ 

+ The virtio-win RPM package contains the following files:

+ 

+ * `/usr/share/virtio-win/*.iso` -  ISO CDROM containing all the drivers. 

+ * `/usr/share/virtio-win/*.vfd` - VFD floppy images for using during install of Windows XP

+ * `/usr/share/virtio-win/drivers` - Copy of the extracted VFD driver contents

+ * `/usr/share/guest-agent/*.msi` - QEMU Guest Agent 32bit and 64bit MSI installers

+ 

+ [[virtio-win-iso-contents]]

+ == ISO contents

+ 

+ ISO is used to install paravirtual drivers in Windows guests. The `virtio-win/*.iso` included in the RPM  contains the following bits:

+ 

+ * `NetKVM/` - Virtio network driver

+ * `viostor/` - Virtio block driver

+ * `vioscsi/`  - Virtio Small Computer System Interface (SCSI) driver

+ * `viorng/` - Virtio RNG driver  

+ * `vioser/` - Virtio serial driver

+ * `Balloon/` - Virtio memory balloon driver

+ * `qxl/` - QXL graphics driver for Windows 7 and earlier. (build virtio-win-0.1.103-1 and later)

+ * `qxldod/` -  QXL graphics driver for Windows 8 and later. (build virtio-win-0.1.103-2 and later)

+ * `pvpanic/` - https://github.com/qemu/qemu/blob/master/docs/specs/pvpanic.txt[QEMU pvpanic] device driver (build virtio-win-0.1.103-2 and later)

+ * `guest-agent/` - QEMU Guest Agent 32bit and 64bit MSI installers

+ * `qemupciserial/` - https://github.com/qemu/qemu/blob/master/docs/qemupciserial.inf[QEMU PCI

+ serial] device driver

+ * `*.vfd`  VFD floppy images for using during install of Windows XP

+ 

+ NOTE: If you previously used isos from alt.fedoraproject.org, note that the current isos have a different file layout that matches the layout of the Red Hat Enterprise Linux isos.   If you need old isos for backwards compatiblity you can find them on the  https://fedorapeople.org/groups/virt/virtio-win/deprecated-isos/[deprecated isos page].

+ 

+ [[virtio-win-direct-downloads]]

+ == Direct downloads

+ 

+ Direct downloads are available for the `.iso`, `.vfd`, and qemu-ga installers.

+ 

+ * Stable https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso[virtio-win iso]

+ * Stable https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win_x86.vfd[virtio-win x86 floppy]

+ * Stable https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win_amd64.vfd[virtio-win amd64 floppy]

+ * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso[virtio-win iso]

+ * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win_x86.vfd[virtio-win x86 floppy]

+ * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win_amd64.vfd[virtio-win amd64 floppy]

+ * Latest https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-qemu-ga/[gemu-qa files]

+ * https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/[Full archive]

+ * https://fedorapeople.org/groups/virt/virtio-win/CHANGELOG[Changelog]

modules/ROOT/pages/adding-new-fonts-fedora.adoc en-US/adding-new-fonts-fedora.adoc
file renamed
+6 -2
@@ -1,4 +1,6 @@ 

  :experimental:

+ ifdef::context[:parent-context: {context}]

+ :context: adding-new-fonts-fedora

  

  

  [[adding-new-fonts-fedora]]
@@ -6,6 +8,8 @@ 

  

  The default installation of the Fedora Linux (Fedora) includes several basic fonts. If you plan to use Fedora for activities such as typesetting and graphic design, you may wish to add additional fonts. 

  

- include::en-US/modules/proc_adding-new-fonts-as-superuser.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_adding-new-fonts-as-superuser.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_adding-new-fonts-as-user.adoc[leveloffset=+1] 

+ include::{partialsdir}/proc_adding-new-fonts-as-user.adoc[leveloffset=+1] 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/adding-or-removing-software-repositories-in-fedora.adoc en-US/adding-or-removing-software-repositories-in-fedora.adoc
file renamed
+7 -3
@@ -1,12 +1,16 @@ 

  :experimental:

+ ifdef::context[:parent-context: {context}]

+ :context: adding-or-removing-software-respositories-in-fedora

  

  [id='adding-or-removing-software-repositories-in-fedora']

  = Adding or removing software repositories in Fedora

  

  This section describes how to add, enable, or disable a software repository with the DNF application.

  

- include::en-US/modules/proc_adding-repositories.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_adding-repositories.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_enabling-repositories.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_enabling-repositories.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_disabling-repositories.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_disabling-repositories.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,27 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: viewing-logs

+ 

+ = Adding a user to sudoers

+ [id=adding_user_to_sudoers_{context}]

+ 

+ One of the most common operations that administrators want to accomplish when managing `sudo` permissions is to grant a new user general `sudo` access. This is helpful if you want to give an account full administrative access to the system.

+ 

+ [discrete]

+ == Giving a user `sudo` privileges

+ On Fedora, it is the `wheel` group the user has to be added to, as this group has full admin privileges. Add a user to the group using the following command:

+ [subs=+quotes]

+ ----

+ $ sudo usermod -aG wheel _username_

+ ----

+ 

+ If adding the user to the group does not work immediately, you may have to edit the `/etc/sudoers` file to uncomment the line with the group name:

+ 

+ ----

+ $ sudo visudo

+ ...

+ %wheel ALL=(ALL) ALL

+ ...

+ ----

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/anaconda/anaconda.adoc en-US/anaconda/anaconda.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/anaconda/anaconda_distros.adoc en-US/anaconda/anaconda_distros.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/anaconda/anaconda_logging.adoc en-US/anaconda/anaconda_logging.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/anaconda/anaconda_product_image.adoc en-US/anaconda/anaconda_product_image.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/anaconda/anaconda_updates.adoc en-US/anaconda/anaconda_updates.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/assembly_installing-plugins-for-playing-movies-and-music.adoc en-US/assembly_installing-plugins-for-playing-movies-and-music.adoc
file renamed
+15 -13
@@ -1,5 +1,5 @@ 

  // Load attributes from the external file

- include::en-US/attributes.adoc[]

+ include::{partialsdir}/attributes.adoc[]

  

  // This assembly is included in the following assemblies:

  //
@@ -11,7 +11,13 @@ 

  

  // The following line is necessary to allow assemblies be included in other

  // assemblies. It restores the `context` variable to its previous state.

- :parent-context: {context}

+ 

+ // The `context` attribute enables module reuse. Every module's ID

+ // includes {context}, which ensures that the module has a unique ID even if

+ // it is reused multiple times in a guide.

+ 

+ ifdef::context[:parent-context: {context}]

+ :context: assembly_installing-plugins-for-playing-movies-and-music

  

  // The file name and the ID are based on the assembly title.

  // For example:
@@ -31,11 +37,6 @@ 

  [id='assembly_installing-plugins-for-playing-movies-and-music_{context}']

  = Installing plugins for playing movies and music

  

- // The `context` attribute enables module reuse. Every module's ID

- // includes {context}, which ensures that the module has a unique ID even if

- // it is reused multiple times in a guide.

- :context: assembly_installing-plugins-for-playing-movies-and-music

- 

  As a Fedora user and system administrator, you can use these steps to install additional multimedia plugins that enable you to play various video and audio types.

  

  WARNING: If you live in a country where software patents apply, such as in the United States or in Japan, you need to obtain multimedia codecs from a source that legally distributes patented software in your country. For example, see the Fluendo Codec Pack: link:https://fluendo.com/en/products/enterprise/fluendo-codec-pack/[].
@@ -58,15 +59,15 @@ 

  // modules required to cover the user story. You can also include other

  // assemblies.

  

- include::en-US/modules/proc_enabling-the-rpmfusion-repositories-using-graphical-applications.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_enabling-the-rpmfusion-repositories-using-graphical-applications.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_enabling-the-rpmfusion-repositories-using-command-line-utilities.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_enabling-the-rpmfusion-repositories-using-command-line-utilities.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_installing-multimedia-plug-ins-with-dnf.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-multimedia-plug-ins-with-dnf.adoc[leveloffset=+1]

  

- include::en-US/modules/concept_third-party-repositories.adoc[leveloffset=+1]

+ include::{partialsdir}/concept_third-party-repositories.adoc[leveloffset=+1]

  

- include::en-US/modules/con_the-purpose-of-rpm-fusion.adoc[leveloffset=+1]

+ include::{partialsdir}/con_the-purpose-of-rpm-fusion.adoc[leveloffset=+1]

  

  // [leveloffset=+1] ensures that when a module starts with a level-1 heading

  // (= Heading), the heading will be interpreted as a level-2 heading
@@ -82,4 +83,5 @@ 

  

  // The following line is necessary to allow assemblies be included in other

  // assemblies. It restores the `context` variable to its previous state.

- :context: {parent-context}

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/autoupdates.adoc en-US/autoupdates.adoc
file renamed
+1 -1
@@ -17,7 +17,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:

modules/ROOT/pages/bootloading-with-grub2.adoc en-US/bootloading-with-grub2.adoc
file renamed
+15 -11
@@ -1,3 +1,5 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: bootloading-with-grub2

  [id='bootloading-with-grub2']

  = Bootloading with GRUB2

  
@@ -7,30 +9,32 @@ 

  

  Since Fedora 16, *GRUB2* has been the default bootloader on x86 BIOS systems. For upgrades of BIOS systems, the default is also to install *GRUB2*, but you can opt to skip bootloader configuration entirely.

  

- include::en-US/modules/proc_installing-grub2-on-bios-system.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-grub2-on-bios-system.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_installing-grub2-on-efi-system.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-grub2-on-efi-system.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_adding-other-operating-systems-grub2.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_adding-other-operating-systems-grub2.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_setting-default-entry-for-grub2.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_setting-default-entry-for-grub2.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_restoring-bootloader-using-live-disk.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_restoring-bootloader-using-live-disk.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_using-grub2-prompt.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_using-grub2-prompt.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_booting-with-configfile-on-different-partition.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_booting-with-configfile-on-different-partition.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_setting-password-for-interactive-edit-mode.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_setting-password-for-interactive-edit-mode.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_solving-absent-floppy.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_solving-absent-floppy.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_using-old-graphics-modes.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_using-old-graphics-modes.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_enabling-serial-console-grub.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_enabling-serial-console-grub.adoc[leveloffset=+1]

  

  

  [discrete]

  == Additional resources

  

  * http://www.gnu.org/software/grub/manual/grub.html

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/bumblebee.adoc en-US/bumblebee.adoc
file renamed
+2 -1
@@ -1,4 +1,5 @@ 

- include::en-US/3rdparty-message.adoc[]

+ include::{partialsdir}/attributes.adoc[]

+ include::{partialsdir}/3rdparty-message.adoc[]

  

  [[description]]

  == Description

@@ -0,0 +1,21 @@ 

+ :experimental:

+ ifdef::context[:parent-context: {context}]

+ :context: changing-selinux-states-and-modes

+ 

+ // NOTE (TODO): several links (URLs) in the included modules could be replaced with URLs when the appropriate docs become available on fp.org

+ 

+ [id='changing-selinux-states-and-modes-{context}']

+ = Changing SELinux states and modes

+ :context: selinux

+ 

+ :md: en-US/modules

+ 

+ include::{partialsdir}/con_permanent-changes-in-selinux-states-and-modes.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_enabling-selinux.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_changing-to-permissive-mode.adoc[leveloffset=+2]

+ include::{partialsdir}/proc_changing-to-enforcing-mode.adoc[leveloffset=+2]

+ include::{partialsdir}/proc_disabling-selinux.adoc[leveloffset=+1]

+ include::{partialsdir}/ref_changing-selinux-modes-at-boot-time.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,16 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: configuring-ip-networking-with-nmcli

+ [id='Configuring-networking-with-nmcli']

+ = Configuring IP networking with nmcli

+ 

+ How to configure networking using the [application]*nmcli* (NetworkManager Command Line Interface) command-line utility.

+ 

+ include::{partialsdir}/con_Getting-started-with-nmcli.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_Brief-selection-of-nmcli-examples.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/con_Understanding-the-nmcli-options.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_Configuring-networking-with-nmcli.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,10 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: configuring-x-window-system-using-the-xorg-conf-file

+ [id='configuring-x-window-system-using-the-xorg-conf-file']

+ = Configuring X Window System using the xorg.conf file

+ 

+ include::{partialsdir}/con_xorg-conf.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_creating_xorg_conf.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/configuring-xorg-as-default-gnome-session.adoc en-US/configuring-xorg-as-default-gnome-session.adoc
file renamed
+8 -2
@@ -1,11 +1,13 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: xorg

+ 

  [id='configuring-xorg-as-default-gnome-session']

  = Configuring Xorg as the default GNOME session

- :context: xorg

  

  Wayland is the default GNOME display server. If GNOME freezes, or some applications do not function correctly in Wayland, you can choose to run GNOME in X11.

  

  

- include::en-US/modules/proc_configuring-xorg-as-default-gnome-session.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_configuring-xorg-as-default-gnome-session.adoc[leveloffset=+1]

  

  

  [discrete]
@@ -13,3 +15,7 @@ 

  . link:https://docs.fedoraproject.org/f27/system-administrators-guide/Wayland.html[Wayland Display Server in the System Administrator's Guide]

  

  . link:https://wayland.freedesktop.org/[Wayland @ freedesktop.org]

+ 

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/create-gpg-keys.adoc en-US/create-gpg-keys.adoc
file renamed
+22 -17
@@ -1,28 +1,31 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: creating-gpg-keys

+ = Creating GPG Keys

  :experimental:

  

  This document explains in detail how to obtain a GPG key using common Fedora utilities.

  It also provides information on managing your key as a Fedora contributor.

  

  [[creating-gpg-keys]]

- = Creating GPG Keys

+ == Creating GPG Keys

  

- include::en-US/modules/proc_creating-gpg-keys-gnome.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_creating-gpg-keys-gnome.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_creating-gpg-keys-kde.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_creating-gpg-keys-kde.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_creating-gpg-keys-cli.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_creating-gpg-keys-cli.adoc[leveloffset=+1]

  

  [[making-a-backup]]

- = Making a Backup

+ == Making a Backup

  

- include::en-US/modules/proc_backup-gpg-keys-gnome.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_backup-gpg-keys-gnome.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_backup-gpg-keys-kde.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_backup-gpg-keys-kde.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_backup-gpg-keys-cli.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_backup-gpg-keys-cli.adoc[leveloffset=+1]

  

  [[making-your-public-key-available]]

- = Making Your Public Key Available

+ == Making Your Public Key Available

  

  When you make your public key available to others, they can verify communications you sign, or send you encrypted communications if necessary.

  This procedure is also known as _exporting_.
@@ -30,23 +33,23 @@ 

  Now see <<exporting-gpg-keys-gnome>>, <<exporting-gpg-keys-kde>>, or the <<exporting-gpg-keys-cli>>.

  See <<copying-public-gpg-keys-manually>> to a file if you wish to email it to individuals or groups.

  

- include::en-US/modules/proc_exporting-gpg-keys-gnome.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_exporting-gpg-keys-gnome.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_exporting-gpg-keys-kde.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_exporting-gpg-keys-kde.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_exporting-gpg-keys-cli.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_exporting-gpg-keys-cli.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_copying-public-gpg-keys-manually.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_copying-public-gpg-keys-manually.adoc[leveloffset=+1]

  

  [[safeguarding-your-secret-key]]

- = Safeguarding Your Secret Key

+ == Safeguarding Your Secret Key

  

  Treat your secret key as you would any very important document or physical key.

  (Some people always keep their secret key on their person, either on magnetic or flash media.)

  If you lose your secret key, you will be unable to sign communications, or to open encrypted communications that were sent to you.

  

  [[hardware-token-options]]

- = Hardware Token options

+ == Hardware Token options

  

  If you followed the above, you have a secret key which is just a regular file.

  A more secure model than keeping the key on disk is to use a hardware token.
@@ -55,12 +58,14 @@ 

  Look for a token which advertises OpenPGP support.

  See https://blog.josefsson.org/2014/06/23/offline-gnupg-master-key-and-subkeys-on-yubikey-neo-smartcard/[this blog entry] for how to create a key with offline backups, and use the token for online access.

  

- include::en-US/modules/proc_revoking-gpg-keys.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_revoking-gpg-keys.adoc[leveloffset=+1]

  

- = Additional resources

+ == Additional resources

  

  * http://www.gnupg.org/[GPG home page]

  * http://www.gnupg.org/documentation/[Official GPG documentation]

  * http://en.wikipedia.org/wiki/Public-key_cryptography[Wikipedia - Public Key Cryptography]

  

  See a typo, something missing or out of date, or anything else which can be improved? Edit this document at https://pagure.io/fedora-docs/quick-docs[quick-docs's git repository].

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/create-hello-world-rpm.adoc en-US/create-hello-world-rpm.adoc
file renamed
+4 -4
@@ -1,4 +1,4 @@ 

- include::en-US/attributes.adoc[]

+ include::{partialsdir}/attributes.adoc[]

  

  = How to Create a GNU Hello World RPM Package

  
@@ -125,7 +125,7 @@ 

  

  It will complain and list the unpackaged files, i.e. the files that would be installed in the system that weren't declared as belonging to the package.

  We need to declare them in the `%files` section.

- Do not hardcode names like `/usr/bin/`, but use macros, like `%{_bindir}/hello` instead.

+ Do not hardcode names like `/usr/bin/`, but use macros, like `%\{_bindir}/hello` instead.

  The manual pages should be declared in the `%doc` subsection:

  

  ....
@@ -137,9 +137,9 @@ 

  Since our program uses translations and internationalization, we are seeing a lot of undeclared i18 files.

  The link:https://fedoraproject.org/wiki/Packaging:Guidelines#Handling_Locale_Files[recommended method] to declare them is:

  

- * find the filenames in the `%install` step: `%find_lang %{name}`

+ * find the filenames in the `%install` step: `%find_lang %\{name}`

  * add the required build dependencies: `BuildRequires: gettext`

- * use the found filenames `%files -f %{name}.lang`

+ * use the found filenames `%files -f %\{name}.lang`

  

  If the program uses GNU `info` files, you need to make sure the installation and uninstallation of the package does not interfere with other software on the system, by using this boilerplate:

  

@@ -0,0 +1,12 @@ 

+ :experimental:

+ ifdef::context[:parent-context: {context}]

+ :context: using-parted

+ [id='disk-partition-in-linux-{context}']

+ = Creating a disk partition in Linux

+ 

+ include::{partialsdir}/con_disk-partition-linux.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_creating-a-disk-partition-in-linux.adoc[leveloffset=+1]

+ include::{partialsdir}/ref_help-mkpart.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,16 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: creating-an-using-a-live-installation-image

+ = Creating and using a live installation image

+ 

+ include::{partialsdir}/proc_downloading-fedora.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_creating-and-using-live-usb.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_booting-from-usb-sticks.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_troubleshooting-live-usb.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_creating-and-using-live-cd.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,16 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: creating-rpm-packages

+ [id='creating-rpm-packages']

+ = Creating RPM packages

+ 

+ Learn the basics of RPM packaging.

+ 

+ include::{partialsdir}/con_rpm_packaging_overview.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_rpm_preparing_your_system.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_rpm_creating_an_rpm.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/con_rpm_spec_file_overview.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/creating-windows-virtual-machines-using-virtio-drivers.adoc en-US/creating-windows-virtual-machines-using-virtio-drivers.adoc
file renamed
+10 -6
@@ -1,3 +1,5 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: creating-windows-virtual-machines-using-virtio-drivers

  [id='creating-windows-virtual-machines-using-virtio-drivers']

  = Creating Windows virtual machines using virtIO drivers

  
@@ -7,17 +9,17 @@ 

  

  The drivers in these repos are licensed under the https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html[GPLv2] license.

  

- include::en-US/modules/concept_virtio-win-repo-overview.adoc[leveloffset=+1]

+ include::{partialsdir}/concept_virtio-win-repo-overview.adoc[leveloffset=+1]

  

- include::en-US/modules/concept_fedora-virtio-drivers-vs-rhel.adoc[leveloffset=+1]

+ include::{partialsdir}/concept_fedora-virtio-drivers-vs-rhel.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_installing-virtio-win-repo.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-virtio-win-repo.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_enabling-latest-virtio-win-repo.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_enabling-latest-virtio-win-repo.adoc[leveloffset=+1]

  

- include::en-US/modules/ref_virtio-win-rpm-contents.adoc[leveloffset=+1]

+ include::{partialsdir}/ref_virtio-win-rpm-contents.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_filing-virtio-win-bugs.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_filing-virtio-win-bugs.adoc[leveloffset=+1]

  

  

  [discrete]
@@ -31,3 +33,5 @@ 

  * Spice guest tools installer code: http://cgit.freedesktop.org/~teuf/spice-nsis/

  * spice-guest-tools downloads: http://www.spice-space.org/download/binaries/spice-guest-tools/

  * Fedora virtio-win build scripts: https://github.com/crobinso/virtio-win-pkg-scripts

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/debug-dracut-problems.adoc en-US/debug-dracut-problems.adoc
file renamed
+1 -1
@@ -17,7 +17,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:

modules/ROOT/pages/debug-systemd-problems.adoc en-US/debug-systemd-problems.adoc
file renamed
+1 -1
@@ -17,7 +17,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:

modules/ROOT/pages/debug-wayland-problems.adoc en-US/debug-wayland-problems.adoc
file renamed
+1 -1
@@ -17,7 +17,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:

@@ -0,0 +1,5 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: disabling-automatic-screenlock

+ include::{partialsdir}/proc_disabling-gnome-screenlock.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,7 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: displaying-user-prmopt-on-gnome-login-screen

+ :md: en-US/modules

+ 

+ include::{partialsdir}/proc_displaying_user_prompt_on_gnome_login_screen.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/dnf-system-upgrade.adoc en-US/dnf-system-upgrade.adoc
file renamed
file was moved with no change to the file
file renamed
+23 -21
@@ -11,12 +11,8 @@ 

  DNF has replaced YUM as the default package manager for Fedora since version 22.

  However, for earlier versions of Fedora, starting from version 18, DNF can be installed from the command-line with:

  

- [source,bash]

- 

  ----

- 

- yum install dnf

- 

+ # yum install dnf

  ----

  

  [[sect-usage]]
@@ -26,32 +22,20 @@ 

  

  To search the repositories for a package type:

  

- [source,bash]

- 

  ----

- 

- sudo dnf search packagename

- 

+ # sudo dnf search packagename

  ----

  

  To install the package:

  

- [source,bash]

- 

  ----

- 

- sudo dnf install packagename

- 

+ # dnf install packagename

  ----

  

  To remove a package:

  

- [source,bash]

- 

  ----

- 

- sudo dnf remove packagename

- 

+ # dnf remove packagename

  ----

  

  Other common DNF commands include:
@@ -90,6 +74,24 @@ 

  DNF can be used to install or remove Language Support.

  A detailed description with a list of available languages can be found on link:++https://fedoraproject.org/wiki/I18N/Language_Support_Using_Dnf[Language Support Using Dnf] page.

  

+ [[sect-plugins]]

+ == Plugins

+ 

+ The core DNF functionality can be extended with plugins.

+ There are officially supported https://dnf-plugins-core.readthedocs.io[Core DNF plugins]

+ and also third-party https://dnf-plugins-extras.readthedocs.io[Extras DNF Plugins].

+ To install them, run

+ 

+ ----

+ # dnf install dnf-plugins-core-PLUGIN_NAME

+ ----

+ 

+ or

+ 

+ ----

+ # dnf install dnf-plugins-extras-PLUGIN_NAME

+ ----

+ 

  [[sect-references]]

  == References

  
@@ -97,4 +99,4 @@ 

  

  . http://dnf.baseurl.org/[DNF blog]

  

- . https://github.com/rpm-software-management/dnf/wiki[DNF wiki] 

\ No newline at end of file

+ . https://github.com/rpm-software-management/dnf/wiki[DNF wiki]

modules/ROOT/pages/edit-iptables-rules.adoc en-US/edit-iptables-rules.adoc
file renamed
+14 -27
@@ -18,7 +18,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:
@@ -45,12 +45,10 @@ 

  __TOC__

  

  [[cli-command-line-interface]]

- CLI (command line interface)

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ == CLI (command line interface)

  

  [[hot-changes-to-iptables-rules]]

- Hot changes to iptables Rules

- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

+ === Hot changes to iptables Rules

  

  The following procedures allow changes in the behaviour of the firewall

  while it is running.
@@ -59,8 +57,7 @@ 

  and more sophisticated Rules examples.

  

  [[listing-rules]]

- Listing Rules

- +++++++++++++

+ ==== Listing Rules

  

  Current running iptables Rules can be viewed with the command

  
@@ -96,8 +93,7 @@ 

  to accept the ssh connection is not.

  

  [[appending-rules]]

- Appending Rules

- +++++++++++++++

+ ==== Appending Rules

  

  The following adds a Rule at the end of the specified chain of iptables:

  
@@ -123,8 +119,7 @@ 

  chain.

  

  [[deleting-rules]]

- Deleting Rules

- ++++++++++++++

+ ==== Deleting Rules

  

  To delete a Rule, you must know its position in the chain. The following

  example deletes an existing Rule created earlier that is currently in
@@ -148,8 +143,7 @@ 

  ....

  

  [[inserting-rules]]

- Inserting Rules

- +++++++++++++++

+ ==== Inserting Rules

  

  Create a Rule at the top (first) position:

  
@@ -177,8 +171,7 @@ 

  will then be in the fourth position in the chain.

  

  [[replacing-rules]]

- Replacing Rules

- +++++++++++++++

+ ==== Replacing Rules

  

  Rules may be specified to replace existing Rules in the chain.

  
@@ -206,8 +199,7 @@ 

  ....

  

  [[flushing-rules]]

- Flushing Rules

- ++++++++++++++

+ ==== Flushing Rules

  

  To flush or clear iptables Rules, use the *--flush*, *-F* option :

  
@@ -225,8 +217,7 @@ 

  ....

  

  [[making-changes-persistent]]

- Making changes persistent

- ^^^^^^^^^^^^^^^^^^^^^^^^^

+ === Making changes persistent

  

  The iptables Rules changes using CLI commands will be lost upon system

  reboot. However, iptables comes with two useful utilities:
@@ -316,8 +307,7 @@ 

  specific rule.

  

  [[tui-text-based-user-interface]]

- TUI (text-based user interface)

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ == TUI (text-based user interface)

  

  There is two ways to managing iptables rules with a text-based user

  interface, either using *setup* or *system-config-firewall-tui*. Using
@@ -422,12 +412,10 @@ 

  interface, or *No* to go back to the firewall configuration screen.

  

  [[gui]]

- GUI

- ~~~

+ == GUI

  

  [[red-hat-gui-configuration-tool]]

- Red Hat GUI configuration tool

- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

+ === Red Hat GUI configuration tool

  

  GUI interface allow you exactly the same thing that TUI interface, but

  it is more friendly usable.
@@ -500,8 +488,7 @@ 

  When configuration fits to you, just click on the *Apply* button.

  

  [[others-gui]]

- Others GUI

- ^^^^^^^^^^

+ === Others GUI

  

  There are others GUI available to configure iptables rules.

  

modules/ROOT/pages/enable-touchpad-click.adoc en-US/enable-touchpad-click.adoc
file renamed
+7 -13
@@ -18,7 +18,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:
@@ -33,8 +33,7 @@ 

  

  

  [[scope]]

- Scope

- ~~~~~

+ == Scope

  

  Fedora tries to make various desktop environments available to its

  users. Since Fedora tries to
@@ -49,8 +48,7 @@ 

  Fedora does not intend to make any changes to upstream defaults.*

  

  [[desktop-configurations]]

- Desktop configurations

- ~~~~~~~~~~~~~~~~~~~~~~

+ == Desktop configurations

  

  This wiki page has more information about

  link:Input_device_configuration[Input Device configuration]. An example
@@ -58,8 +56,7 @@ 

  Input_device_configuration#Example:_Tap-to-click[here].

  

  [[gnome]]

- GNOME

- ^^^^^

+ === GNOME

  

  The "*mouse and touchpad*" utility can be used to enable tapping and set

  scrolling options in GNOME.
@@ -68,8 +65,7 @@ 

  GNOME documentation]

  

  [[kde-plasma-workspaces]]

- KDE Plasma Workspaces

- ^^^^^^^^^^^^^^^^^^^^^

+ === KDE Plasma Workspaces

  

  1.  enter KDE System Settings

  2.  choose Hardware / Input Devices / Touchpad (If it's not there,
@@ -84,8 +80,7 @@ 

  link:#Other_window_managers[Other window managers] can also be used.

  

  [[xfce]]

- XFCE

- ^^^^

+ === XFCE

  

  1.  Enter XFCE Settings

  2.  Select the Mouse and Touchpad settings
@@ -93,8 +88,7 @@ 

  4.  In the General section, enable "Tap touchpad to click"

  

  [[other-window-managers]]

- Other window managers

- ^^^^^^^^^^^^^^^^^^^^^

+ === Other window managers

  

  Create a new file named

  /etc/X11/xorg.conf.d/99-synaptics-overrides.conf.

@@ -0,0 +1,20 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: luks

+ 

+ [id='encrypting-drives-using-luks']

+ = Encrypting drives using LUKS

+ 

+ As a system administrator, you can encrypt a block device. This section gives a brief introduction to block encryption, describes Linux Unified Key Setup (LUKS), and lists the steps to create an encrypted block device.

+ 

+ :leveloffset: +1

+ 

+ include::{partialsdir}/con_block-device-encryption.adoc[]

+ 

+ include::{partialsdir}/con_introduction-to-luks.adoc[]

+ 

+ include::{partialsdir}/creating-encrypted-block-devices.adoc[]

+ 

+ :leveloffset: 0

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/fedora-and-red-hat-enterprise-linux.adoc en-US/fedora-and-red-hat-enterprise-linux.adoc
file renamed
+5 -1
@@ -1,6 +1,10 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: fedora-and-red-hat-enterprise-linux

  [id='fedora-and-red-hat-enterprise-linux']

  = Fedora and Red Hat Enterprise Linux

  

  What is the difference between Fedora and Red Hat Enterprise Linux?

  

- include::en-US/modules/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc[leveloffset=+1]

+ include::{partialsdir}/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/fedora-life-cycle.adoc en-US/fedora-life-cycle.adoc
file renamed
+4
@@ -1,5 +1,6 @@ 

  = Fedora Release Life Cycle

  

+ ////

  The Fedora Project releases a new version of Fedora approximately every 6 months and provides updated packages (maintenance) to these releases for approximately 13 months. This allows users to "skip a release" while still being able to always have a system that is still receiving updates.

  

  [[development-schedule]]
@@ -137,3 +138,6 @@ 

  * https://fedoraproject.org/wiki/Releases/HistoricalSchedules[Historical Release Information]

  

  See a typo, something missing or out of date, or anything else which can be improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

+ ////

+ 

+ This page is maintained on link:https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Project Wiki]

modules/ROOT/pages/finding-and-installing-linux-applications.adoc en-US/finding-and-installing-linux-applications.adoc
file renamed
+9 -5
@@ -1,3 +1,5 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: finding-and-installing-linux-applications

  :imagesdir: images

  

  [[finding-and-installing-linux-applications]]
@@ -7,12 +9,14 @@ 

  

  You can use the Fedora package management system to install applications. Many applications are available from the repository provided by the Fedora project. You can enable other repositories to get additional applications.

  

- include::en-US/modules/con_package-management-in-fedora.adoc[leveloffset=+1]

+ include::{partialsdir}/con_package-management-in-fedora.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_package-searching-web-apps.adoc[leveloffset=+1] 

+ include::{partialsdir}/proc_package-searching-web-apps.adoc[leveloffset=+1] 

  

- include::en-US/modules/proc_package-browsing-installing-software.adoc[leveloffset=+1] 

+ include::{partialsdir}/proc_package-browsing-installing-software.adoc[leveloffset=+1] 

  

- include::en-US/modules/proc_package-install-command-line.adoc[leveloffset=+1] 

+ include::{partialsdir}/proc_package-install-command-line.adoc[leveloffset=+1] 

  

- include::en-US/modules/proc_package-enabling-third-party.adoc[leveloffset=+1] 

+ include::{partialsdir}/proc_package-enabling-third-party.adoc[leveloffset=+1] 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,33 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: using-firewalld

+ :experimental:

+ :imagesdir: ./images

+ 

+ [[using-firewalld]]

+ = Using firewalld

+ 

+ :leveloffset: +1

+ 

+ include::{partialsdir}/con_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_checking_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_installing_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_starting_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_stopping_firewalld.adoc[]

+ 

+ include::{partialsdir}/con_runtime_and_permanent_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_changing_runtime_firewalld.adoc[]

+ 

+ include::{partialsdir}/con_controlling_ports_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_opening_ports_firewalld.adoc[]

+ 

+ include::{partialsdir}/proc_closing_ports_firewalld.adoc[]

+ 

+ :leveloffset: 0

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/getting-started-with-apache-http-server.adoc en-US/getting-started-with-apache-http-server.adoc
file renamed
+8 -4
@@ -1,15 +1,17 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: getting-started-with-apache-http-server

  [id='getting-started-with-apache-http-server']

  = Getting started with Apache HTTP Server

  

  The Apache HTTP Server is one of the most commonly-used web servers. This section acts as a quick-start guide to deploying and configuring Apache on Fedora.

  

- include::en-US/modules/proc_installing-httpd.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-httpd.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_securing-apache-httpd.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_securing-apache-httpd.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_installing-webapps.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-webapps.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_configuring-apache-httpd.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_configuring-apache-httpd.adoc[leveloffset=+1]

  

  

  [discrete]
@@ -20,3 +22,5 @@ 

  * https://httpd.apache.org/docs/current/ssl/[Apache TLS/SSL documentation]

  * https://httpd.apache.org/docs/current/misc/security_tips.html[Apache security tips]

  * https://fedoraproject.org/wiki/OwnCloud[OwnCloud]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,19 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: getting-started-with-selinux

+ [id='getting-started-with-selinux-{context}']

+ = Getting started with SELinux

+ :context: getting-started-with-selinux

+ 

+ :md: en-US/modules

+ :imagesdir: ./images

+ 

+ :leveloffset: +1

+ include::{partialsdir}/con_introduction-to-selinux.adoc[]

+ include::{partialsdir}/con_benefits-of-selinux.adoc[]

+ include::{partialsdir}/con_selinux-examples.adoc[]

+ include::{partialsdir}/con_selinux-architecture.adoc[]

+ include::{partialsdir}/con_selinux-states-and-modes.adoc[]

+ :leveloffset: -1

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,18 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: getting-started-with-virtualization

+ [id='getting-started-with-virtualization']

+ = Getting started with virtualization

+ 

+ Fedora uses the libvirt family of tools as its virtualization solution.

+ 

+ include::{partialsdir}/proc_enabling-hardware-virtualization-support.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_installing-virtualization-software.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_creating-virtual-machines.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/ref_managing-virtual-machines.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/ref_other-virtualization-options.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,201 @@ 

+ = How to file a bug

+ :imagesdir: ./images

+ 

+ The purpose of this document is to give step by step instructions on filing bugs in Fedora.

+ 

+ A software bug does not necessarily need to be a software crash. Any undesired behaviour noticed in software should be filed as a bug.

+ The package maintainer can then look at the bug report and decide the best course of action.

+ 

+ TIP: *Everyone should file bugs*: All users are encouraged to file any bugs they run into.

+ Bug filing is not limited to only software developers.

+ 

+ == Terminology

+ 

+ There are a few terms that are commonly used in this document:

+ 

+ * *Bug*: A bug is any behaviour in a software that appears unexpected/undesired.

+ * *Bug tracker*: The Fedora bug tracking system at https://bugzilla.redhat.com.

+ * *Package*: Each software that is available in Fedora has a formal package name that is used by the bug tracker and other infrastructure tools.

+ Packages can be searched using the https://apps.fedoraproject.org/packages/[Fedora Packages web application].

+ * *Maintainer*: A body of volunteers that takes care of the software packages provided in Fedora.

+ These are referred to as "package maintainers".

+ They keep track of bugs, help with issues, and generally act as middlemen between the developers of the software and Fedora users.

+ * *QA*: Quality assurance is the process of ensuring that the software works as intended.

+ * *Bodhi*: The http://bodhi.fedoraproject.org[Fedora QA Web Application].

+ 

+ 

+ == Before filing a bug

+ 

+ === Step 1: Check for the latest version

+ 

+ As bugs are reported and fixed, developers collect a set of fixes and periodically release improved versions of their software.

+ So, before reporting an issue, it is useful to check if you are using the latest version of a software.

+ The simplest way to get the latest version of software in Fedora is to regularly update your system.

+ Users of Gnome/KDE and other desktop environments can use their default applications to do so.

+ These periodically check for updates and notify users.

+ You can also use the default package manager `dnf` to check and update your system.

+ Only users with administrator privileges can do so:

+ 

+     $ sudo dnf update --refresh

+ 

+ === Step 2: Check for already filed bugs

+ 

+ If you are using the latest version of the software available in Fedora, then it is likely that the bug has either not been reported, or has been reported but a fix has not yet been released.

+ So, it is useful to search the list of already reported bugs before filing a new report.

+ The https://apps.fedoraproject.org/packages/[Fedora Packages Web application] lists the currently reported bugs for all packages.

+ There is also a convenient shortcut that can be used.

+ 

+     https://bugz.fedoraproject.org/<package name>

+ 

+ Here, the `package name` must be the formal name of the package.

+ 

+ 

+ .The Fedora Packages Web Application lists the bug reports for Gnome software at https://bugz.fedoraproject.org/gnome-software.

+ image::20180825-how-to-file-a-bug-gs-bugs.png[]

+ 

+ As can be seen in the image, the https://apps.fedoraproject.org/packages/[Fedora Packages Web application] also gives other information about a package.

+ 

+ TIP: *Finding the name of the package*: If you do not know the formal package name of the software, you can use the https://apps.fedoraproject.org/packages/[Fedora Packages Web Application] to search for it and view the list of bugs there.

+ 

+ .Searching the Fedora Packages Web Application for Gnome Software.

+ image::20180825-how-to-file-a-bug-gs.png[]

+ 

+ NOTE: *Advanced searching*: You can also use the https://bugzilla.redhat.com/query.cgi[advanced search features of the bug tracker] to narrow down your search.

+ However, this is not necessary.

+ 

+ If a bug report has already been filed describing the issue, you should provide any extra information you may have.

+ If there is nothing more to add to the report, you should "CC" (carbon-copy) yourself to the report to receive any updates.

+ This can be done by clicking on the "Save changes" button when the "Add me to CC list" option is checked as shown below:

+ 

+ 

+ .The CC list contains all users that should be notified when any updates are made to the report.

+ image::20180825-how-to-file-a-bug-cc-list.png[]

+ 

+ == Filing a bug report

+ 

+ === Step 0: Create a Bugzilla account

+ 

+ Bugs are filed on https://bugzilla.redhat.com[Fedora's bugzilla instance], and you must have an account there to file bugs or interact with them.

+ An account requires a valid e-mail address and can be created https://bugzilla.redhat.com/createaccount.cgi[here].

+ The bug tracker will only send e-mail notifications about bugs that a user is involved in. No other e-mails will be sent.

+ 

+ === Step 1: Filing a new bug

+ 

+ If a bug report for the particular issue has not already been filed, you should file a new one.

+ The easiest way to file a new report is using the "File a new bug" drop down from the right hand side bar in the https://apps.fedoraproject.org/packages/[Fedora Packages Web application].

+ 

+ .The Fedora Packages Web Application provides a convenient shortcut to file new bugs.

+ image::20180825-how-to-file-a-bug-new-bug-shortcut.png[]

+ 

+ 

+ This redirects to a new bug report template on the bug tracker.

+ The image below shows a new bug template:

+ 

+ .A new bug report template.

+ image::20180825-how-to-file-a-bug-new-bug.png[]

+ 

+ The following fields need to be set:

+ 

+ * *Component*: This will be set to the name of the package.

+ * *Version*: You should set this to the version of Fedora that you observed the bug on.

+ * *Summary*: You should provide a useful short summary of the issue here.

+ * *Description*: More detailed information about the issue should be provided here.

+ It already contains a template, which is explained below.

+ * *Attachment*: Files that provide more information of the issue can be uploaded with the bug report using the button here.

+ E.g,, screen-shots, log files, screen recordings.

+ * *Severity, Hardware, OS*: These fields are optional and need not be set.

+ 

+ 

+ *Description of problem:*

+ 

+ Explain the issue in more detail here.

+ 

+ *Version-Release number of selected component (if applicable):*

+ 

+ The version of the package should be specified here.

+ Once the package name is known, the version can be obtained by using the `rpm` command:

+ 

+     $ rpm -q <packagename>

+ 

+ For example:

+ 

+     $ rpm -q gnome-software

+     gnome-software-3.28.2-1.fc28.x86_64

+ 

+ 

+ *How reproducible:*

+ 

+ How often is the issue observed?

+ Usually, a good answer to this field is one of:

+ 

+ * Always: the issue is observed each time.

+ * Sometimes: the issue occurs, but not each time.

+ * Only once: the issue was only observed once.

+ 

+ Issues that occur always are easiest for developers to diagnose, since they may also be able to replicate it on their machines to collect more information.

+ If an issue only happens sometimes, developers must spend more time and effort to understand what causes the problem.

+ If an issue was only observed once, it is even harder to debug.

+ 

+ TIP: *Detailed bug reports make bugs easier to fix*: If possible, you should try to investigate what steps cause the issue to happen and provide these steps in the next section:

+ 

+ 

+ TIP: *Submit a report even if unsure*: If you aren't sure of what to fill in, you should still submit the bug report.

+ Maintainers can follow up with questions to gather more information.

+ 

+ *Steps to Reproduce:*

+ 

+ These enable other users to verify the bug, and they also inform the developers of what specific steps cause the issue.

+ It makes it much easier for them to look at the source code and pick out the bits that may be faulty.

+ 

+ *Actual results:*

+ 

+ What is observed when the issue occurs?

+ 

+ *Expected results:*

+ 

+ What does the user expect that should happen if the software behaved correctly?

+ 

+ *Additional info:*

+ 

+ Any additional information that may be useful to the maintainer should be added here.

+ 

+ 

+ === Step 2: Follow up on filed reports

+ 

+ After a bug has been filed, you should keep an eye out for any updates.

+ An e-mail notification of any new comments to the report will be sent to everyone involved in the bug report---the reporter, other users, and the maintainer.

+ Often, maintainers will comment with queries to gather more information on the issue. Sometimes other users that experience the same issue may also add more information.

+ 

+ TIP: *Ask for instructions*: If the maintainers ask for more information but it is unclear how it should be gathered, it is perfectly OK to ask the maintainers for explicit instructions.

+ 

+ TIP: *E-mail notifications*: The notifications are sent from bugzilla@redhat.com.

+ You should keep an eye out for e-mails from this address, and add it to your "no-spam" lists.

+ 

+ If no updates are made to the bug in a week or two, you should also feel free to comment asking for any information.

+ Sometimes maintainers who receive many bug reports can miss notification e-mails.

+ A polite comment will send them a new notification.

+ 

+ === Step 3: Test updates

+ 

+ A well reported bug will usually be fixed, and the maintainer will make an improved version of the software available to Fedora users.

+ Bodhi will add a comment to the report when this happens.

+ You can help the maintainer by confirming if the improved version works better in the Bodhi.

+ 

+ .Bodhi Application adds comments informing users of an update that should fix the bug.

+ image::20180825-how-to-file-a-bug-qa.png[]

+ 

+ TIP: *Help test updates*: All users can help by testing new versions of software.

+ More information on this can be found https://fedoraproject.org/wiki/QA:Updates_Testing[here].

+ Note that this requires a https://admin.fedoraproject.org/accounts/[Fedora account].

+ 

+ Once the improved version of the software has passed the QA process, the bug will automatically be closed. Congratulations!

+ 

+ == More reading

+ 

+ These are some more resources for those looking to report better bugs by providing more information:

+ 

+ * https://fedoraproject.org/wiki/Bugs_and_feature_requests[A general introduction to filing bugs].

+ * https://bugzilla.mozilla.org/page.cgi?id=etiquette.html[Bugzilla etiquette: how to be polite in bug related conversations on the bug tracker].

+ * https://www.chiark.greenend.org.uk/~sgtatham/bugs.html[A general introduction on how to file good bugs (available in multiple languages)].

+ * https://fedoraproject.org/wiki/StackTraces[An introduction to Stacktraces---information software provides about where the fault may lie].

+ * https://fedoramagazine.org/file-better-bugs-coredumpctl/[Using `coredumpctl` to gather more information for bug reports].

file renamed
+7 -7
@@ -24,12 +24,13 @@ 

  

  == Steps

  

- 1. Pick a document to update.  You can find documents needing updates in the `_topic_map.yml` file.  They are on the commented lines (those that start with a `#`).

- 2. Fork the https://pagure.io/fedora-docs/quick-docs repo.

- 3. Make your changes to the `.adoc` file you want to improve.

- 4. Update `_topic_map.yml` to remove "`(FIX ME!)`"

- 5. Submit a pull request with your improvements.

- 6. If migrating a wiki page, create a redirect on the old page — see below.

+ . Pick a document to update. You can find documents needing updates in the [filename]`modules/ROOT/nav.adoc` file. They are on the commented-out lines (those that start with a `//FIXME`).

+ . Fork the https://pagure.io/fedora-docs/quick-docs repo.

+ . Make your changes to the `.adoc` file you want to improve.

+ . Uncomment the file in [filename]`nav.adoc` remove the `FIXME` from the xref..

+ . Build a local preview to ensure your changes look the way you intended: Make sure you have *Docker* installed, and run `./build.sh && ./preview.sh`. Follow instructions printed on the command line.

+ . When you are satisfied with your updates, submit a pull request with your improvements.

+ . If migrating a wiki page, create a redirect on the old page — see below.

  

  == Wiki Redirects

  
@@ -58,4 +59,3 @@ 

  Note that there is no validation that the target exists or is correct —

  please double-check that any redirects you create work properly before

  moving on.

- 

modules/ROOT/pages/installing-and-running-vlc.adoc en-US/installing-and-running-vlc.adoc
file renamed
+9 -5
@@ -1,17 +1,21 @@ 

  :experimental:

  :imagesdir: ./images

  :md: en-US/modules

+ ifdef::context[:parent-context: {context}]

+ :context: installing-and-running-vlc

  

  [[installing-and-running-vlc]]

  = Installing and Running VLC

  

- include::en-US/3rdparty-message.adoc[]

+ include::{partialsdir}/3rdparty-message.adoc[]

  

  :leveloffset: +1

  

- include::{md}/proc_installing_vlc.adoc[]

- include::{md}/proc_running_vlc.adoc[]

- include::{md}/concept_third-party-repositories.adoc[]

- include::{md}/con_the-purpose-of-rpm-fusion.adoc[]

+ include::{partialsdir}/proc_installing_vlc.adoc[]

+ include::{partialsdir}/proc_running_vlc.adoc[]

+ include::{partialsdir}/concept_third-party-repositories.adoc[]

+ include::{partialsdir}/con_the-purpose-of-rpm-fusion.adoc[]

  

  :leveloffset: 0

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,15 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: installing-chromium-or-google-chrome-browsers

+ [id='installing-chromium-or-google-chrome-browsers']

+ = Installing Chromium or Google Chrome browsers

+ 

+ include::{partialsdir}/3rdparty-message.adoc[]

+ 

+ include::{partialsdir}/concept_chromium-web-browser.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_installing-chromium-web-browser.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_enabling-chromium-plugins.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/installing-grub2.adoc en-US/installing-grub2.adoc
file renamed
+8 -4
@@ -1,3 +1,5 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: bootloading-with-grub2

  :md: en-US/modules

  

  
@@ -16,12 +18,14 @@ 

  systems. For upgrades of BIOS systems, the default is also to install

  *GRUB2*, but you can opt to skip bootloader configuration entirely.

  

- include::{md}/proc_installing-grub2-on-bios-system.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-grub2-on-bios-system.adoc[leveloffset=+1]

  

- include::{md}/proc_installing-grub2-on-efi-system.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-grub2-on-efi-system.adoc[leveloffset=+1]

  

- include::{md}/proc_creating-menu-entries-with-uefi-bootloader.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_creating-menu-entries-with-uefi-bootloader.adoc[leveloffset=+1]

  

- include::{md}/proc_adding-other-operating-systems-grub2.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_adding-other-operating-systems-grub2.adoc[leveloffset=+1]

  

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

  

modules/ROOT/pages/installing-java.adoc en-US/installing-java.adoc
file renamed
+8 -4
@@ -1,15 +1,17 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: assembly_installing-java

  [id="assembly_installing-java"]

  = Installing Java

  

  Java provides a platform for creating and running applications. You can install various versions of Java to suit your requirements.

  

- include::en-US/modules/con_about-java.adoc[leveloffset=+1]

+ include::{partialsdir}/con_about-java.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_installing-openjdk.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-openjdk.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_installing-oracle-java.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_installing-oracle-java.adoc[leveloffset=+1]

  

- include::en-US/modules/ref_jdk-tools.adoc[leveloffset=+1]

+ include::{partialsdir}/ref_jdk-tools.adoc[leveloffset=+1]

  

  

  [discrete]
@@ -32,3 +34,5 @@ 

  * link:https://netbeans.org/[NetBeans]

  * link:https://eclipse.org/[Eclipse]

  * link:https://www.jetbrains.com/idea/[IntelliJ IDEA]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/installing-software-from-source.adoc en-US/installing-software-from-source.adoc
file renamed
+8 -4
@@ -1,13 +1,17 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: installing-software-from-source

  [[installing-software-from-source]]

  = Installing software from source code

  

  The following section contains guidelines and best practices for installing software from source code on Fedora.

  The instructions below are not prescriptive, but following them minimizes the risk of errors occurring during installation.

  

- include::en-US/modules/con_package-management-in-fedora.adoc[leveloffset=+1]

+ include::{partialsdir}/con_package-management-in-fedora.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_setting-up-your-local-dev-and-compilation-environment.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_setting-up-your-local-dev-and-compilation-environment.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_downloading-source-code.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_downloading-source-code.adoc[leveloffset=+1]

  

- include::en-US/modules/proc_compiling_your_application_from_source.adoc[leveloffset=+1]

+ include::{partialsdir}/proc_compiling_your_application_from_source.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,13 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: installing-spotify

+ 

+ = Installing Spotify

+ 

+ include::{partialsdir}/3rdparty-message.adoc[]

+ 

+ Installing the Spotify music service client on Fedora.

+ 

+ include::{partialsdir}/proc_installing-spotify-on-fedora.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/installing-virtual-systems-with-gnome-boxes.adoc en-US/installing-virtual-systems-with-gnome-boxes.adoc
file renamed
+6 -5
@@ -1,14 +1,15 @@ 

- :parent-context: {context}

- 

+ ifdef::context[:parent-context: {context}]

+ :context: gnome-boxes

  [id='installing-virtual-operating-systems-with-gnome-boxes-{context}']

  = Installing virtual operating systems with GNOME Boxes

- :context: gnome-boxes

  

  :md: en-US/modules

- :imagesdir: ./images

+ :imagesdir: ../images

  

  GNOME Boxes is an application in GNOME Desktop Environment, which enables you to virtually access various operating systems.

  

  :leveloffset: +1

- include::{md}/proc_install-predefined-systems.adoc[]

+ include::{partialsdir}/proc_install-predefined-systems.adoc[]

  :leveloffset: -1

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/kernel/build-custom-kernel.adoc en-US/kernel/build-custom-kernel.adoc
file renamed
+12 -12
@@ -70,10 +70,10 @@ 

  1. Check out the branch for which you would like to build a kernel (`master`

  corresponds to Rawhide):

  

- [source,bash]

- ----

- git checkout origin/f28

- ----

+     [source,bash]

+     ----

+     git checkout origin/f28

+     ----

  

  2. To avoid conflicts with existing kernels, you can set a custom buildid by

  changing `# define buildid .local` to `%define buildid .<your_custom_id_here>`
@@ -83,17 +83,17 @@ 

  

  4. Build the RPMs:

  

- [source,bash]

- ----

- fedpkg local

- ----

+     [source,bash]

+     ----

+     fedpkg local

+     ----

  

  5. Install the new kernel:

  

- [source,bash]

- ----

- sudo dnf install --nogpgcheck ./x86_64/kernel-$version.rpm

- ----

+     [source,bash]

+     ----

+     sudo dnf install --nogpgcheck ./x86_64/kernel-$version.rpm

+     ----

  

  

  === Building a non-debugging kernel

modules/ROOT/pages/kernel/overview.adoc en-US/kernel/overview.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/kernel/troubleshooting.adoc en-US/kernel/troubleshooting.adoc
file renamed
file was moved with no change to the file
modules/ROOT/pages/managing-keyboard-shortcuts-for-running-app-in-gnome.adoc en-US/managing-keyboard-shortcuts-for-running-app-in-gnome.adoc
file renamed
+8 -4
@@ -1,3 +1,5 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: managing-keyboard-shortcuts-for-running-app-in-gnome

  :experimental:

  

  [id='managing-keyboard-shortcuts-for-running-app-in-gnome']
@@ -7,10 +9,10 @@ 

  

  :leveloffset: +1

  

- include::{md}/proc_adding-shortcut-custom-app-gnome.adoc[]

- include::{md}/proc_disabling-shortcut-custom-app-gnome.adoc[]

- include::{md}/proc_enabling-shortcut-custom-app-gnome.adoc[]

- include::{md}/proc_removing-shortcut-custom-app-gnome.adoc[]

+ include::{partialsdir}/proc_adding-shortcut-custom-app-gnome.adoc[]

+ include::{partialsdir}/proc_disabling-shortcut-custom-app-gnome.adoc[]

+ include::{partialsdir}/proc_enabling-shortcut-custom-app-gnome.adoc[]

+ include::{partialsdir}/proc_removing-shortcut-custom-app-gnome.adoc[]

  

  :leveloffset: 0

  
@@ -25,3 +27,5 @@ 

  

  tested on F28 live CD in VM

  ////

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/mirroring.adoc en-US/mirroring.adoc
file renamed
+1 -1
@@ -18,7 +18,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:

@@ -0,0 +1,125 @@ 

+ = OpenH264

+ 

+ '''

+ 

+ [IMPORTANT]

+ ======

+ 

+ This page was automatically converted from https://fedoraproject.org/wiki/OpenH264

+ 

+ It is probably

+ 

+ * Badly formatted

+ * Missing graphics and tables that do not convert well from mediawiki

+ * Out-of-date

+ * In need of other love

+ 

+ 

+ Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

+ 

+ Once you've fixed this page, remove this notice, and update

+ [filename]`modules/ROOT/nav.adoc`.

+ 

+ Once the document is live, go to the original wiki page and replace its text

+ with the following macro:

+ 

+ ....

+ {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

+ ....

+ 

+ ======

+ 

+ '''

+ 

+ 

+ This page contains information on the Cisco

+ http://www.openh264.org/[OpenH264] codec.

+ 

+ [[background]]

+ Background

+ ----------

+ 

+ Cisco provides an OpenH264 codec (as a source and a binary), which is

+ their of implementation H.264 codec, and they cover all licensing fees

+ for all parties using their binary. This codec allows you to use H.264

+ in WebRTC with gstreamer and Firefox. It does *not* enable generic H.264

+ playback, only WebRTC (see Mozilla

+ https://bugzilla.mozilla.org/show_bug.cgi?id=1057646[bug 1057646]).

+ 

+ The code source is available at https://github.com/cisco/openh264 under

+ a BSD license. The binary is released under this agreement from Cisco:

+ http://www.openh264.org/BINARY_LICENSE.txt

+ 

+ Upstream Firefox versions download and install the OpenH264 plugin by

+ default automatically. Due to it's binary nature, Fedora disables this

+ automatic download.

+ 

+ [[installation-from-fedora-cisco-openh264-repository]]

+ Installation from fedora-cisco-openh264 repository

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ A `fedora-cisco-openh264` repository is distributed since Fedora 24 by

+ default (if you have at least `fedora-repos-24-0.5` package or newer).

+ It contains OpenH264 binary link:Non-distributable-rpms[built inside the

+ Fedora infrastructure], but distributed by Cisco, so that the all

+ licensing fees are still covered by them. This repository also contains

+ OpenH264 plugins for gstreamer and Firefox. It is disabled by default.

+ In order to install OpenH264, you first need to enable it:

+ 

+ ....

+ $ sudo dnf config-manager --set-enabled fedora-cisco-openh264

+ ....

+ 

+ and then install the plugins:

+ 

+ ....

+ $ sudo dnf install gstreamer1-plugin-openh264 mozilla-openh264

+ ....

+ 

+ Afterwards you need open Firefox, go to menu -> Add-ons -> Plugins and

+ enable OpenH264 plugin.

+ 

+ You can do a simple test whether your H.264 works in RTC on

+ https://mozilla.github.io/webrtc-landing/pc_test.html[this page] (check

+ _Require H.264 video_).

+ 

+ [[manual-install-of-binary]]

+ Manual install of binary

+ ~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ * View and agree to the http://www.openh264.org/BINARY_LICENSE.txt

+ * Download the appropriate binary for your system here:

+ https://github.com/cisco/openh264/releases

+ 

+ Example installation for version 1.1:

+ 

+ `wget `http://ciscobinary.openh264.org/openh264-linux64-v1.1-Firefox33.zip[`http://ciscobinary.openh264.org/openh264-linux64-v1.1-Firefox33.zip`] +

+ `mkdir -p ~/.mozilla/firefox/``/gmp-gmpopenh264/1.1/` +

+ `cd ~/.mozilla/firefox/``/gmp-gmpopenh264/1.1/` +

+ `unzip ~/openh264-linux64-v1.1-Firefox33.zip`

+ 

+ [[firefox-config-changes]]

+ Firefox config changes

+ ^^^^^^^^^^^^^^^^^^^^^^

+ 

+ Type about:config into the Firefox address/URL field and accept the

+ warning.

+ 

+ * From the Search field type in 264 and a handful of options will

+ appear. Give the following Preference Names a value of true by

+ double-clicking on false:

+ 

+ ` media.gmp-gmpopenh264.autoupdate` +

+ ` media.gmp-gmpopenh264.enabled` +

+ ` media.gmp-gmpopenh264.provider.enabled` +

+ ` media.peerconnection.video.h264_enabled`

+ 

+ * Restart Firefox

+ * After restarting, the following string in about:config will change to

+ the current version that has been installed from the web:

+ 

+ ` media.gmp-gmpopenh264.version`

+ '''

+ 

+ See a typo, something missing or out of date, or anything else which can be

+ improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -0,0 +1,152 @@ 

+ = Package management system

+ 

+ '''

+ 

+ [IMPORTANT]

+ ======

+ 

+ This page was automatically converted from https://fedoraproject.org/wiki/Package_management_system

+ 

+ It is probably

+ 

+ * Badly formatted

+ * Missing graphics and tables that do not convert well from mediawiki

+ * Out-of-date

+ * In need of other love

+ 

+ 

+ Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

+ 

+ Once you've fixed this page, remove this notice, and update

+ [filename]`modules/ROOT/nav.adoc`.

+ 

+ Once the document is live, go to the original wiki page and replace its text

+ with the following macro:

+ 

+ ....

+ {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

+ ....

+ 

+ ======

+ 

+ '''

+ 

+ 

+ [[package-management-system]]

+ Package Management System

+ -------------------------

+ 

+ [[introduction]]

+ Introduction

+ ~~~~~~~~~~~~

+ 

+ Fedora is a distribution that uses a package management system. This

+ system is based on http://rpm.org[rpm] , the RPM Package Manager, with

+ several higher level tools built on top of it, most notably

+ https://www.freedesktop.org/software/PackageKit/[PackageKit] (default

+ gui) and link:Yum[ yum] (command line tool). As of Fedora 22, yum has

+ been replaced by link:Dnf[ dnf]. The Gnome Package Manager is another

+ GUI package manager.

+ 

+ [[advantages-of-package-management-systems]]

+ Advantages of package management systems

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ Package management systems have many advantages:

+ 

+ * It's easy to query what version of a package is installed or

+ available.

+ 

+ * It's easy to remove a package entirely, making sure all its files are

+ gone.

+ 

+ * It's easy to verify the integrity of the packages files, so you can

+ see if it's been corrupted or tampered with.

+ 

+ * It's easy to upgrade a package by installing the new version and

+ removing all the old versions files. This will make sure not to leave

+ any lingering files from the old package around to confuse or break

+ things.

+ 

+ * It's easy to see what packages require or provide things that other

+ packages provide or require, so you can be sure to have the needed items

+ for the package to function correctly.

+ 

+ * It's easy to install or remove groups of packages.

+ 

+ * In many cases it's possible to downgrade back to a previous version of

+ a package, for example when a new version has a bug.

+ 

+ [[disadvantages-of-package-management-systems]]

+ Disadvantages of package management systems

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ * You are restricted to either using the versions of the package that

+ are available or having to make your own package if you need a different

+ version.

+ 

+ [[why-mixing-source-installs-and-packages-is-a-bad-idea]]

+ Why mixing source installs and packages is a bad idea

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ Package management systems have no way to query or note when you bypass

+ them and install something from source. You should avoid mixing source

+ installs and packaged installs for (at least) the following reasons:

+ 

+ * You lose all the advantages above from a package managed system.

+ 

+ * Installing from source may overwrite, delete, or change existing files

+ that are in a package, making that package not function correctly.

+ 

+ * The source install may override a package install causing undefined

+ behavior in the package or source installed item.

+ 

+ * Installing from source makes it impossible or very difficult for

+ anyone to help you debug issues, since versions can't be easily queried

+ and integrity checked.

+ 

+ * Fedora packages may include patches or configuration to work with

+ other packages, but upstream source does not, leading to loss of

+ functionality.

+ 

+ * Software installed from source will not upgrade with package managed

+ packages, leading to breakage in the source install package on upgrades

+ or os updates.

+ 

+ Strongly consider making your own package if you need a different

+ version or a version of some package with changes. See:

+ link:How_to_create_an_RPM_package[How to create a RPM package]

+ 

+ [[preferred-search-order-for-a-software]]

+ Preferred search order for a software

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ If some software is missing in your installation then you should try the

+ following steps to get the packaged version:

+ 

+ 1.  Search in Fedora ( 'yum|dnf search foo' or search for 'foo' in the

+ PackageKit gui )

+ 2.  Try one of the available link:Third_party_repositories[ 3rd party]

+ repositories

+ 3.  link:How_to_create_an_RPM_package[ Build your own package]

+ 

+ [[package-management-tools]]

+ Package Management tools

+ ~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ link:Dnf[ dnf] - Dandified Yum

+ 

+ link:Yum[ yum] - Yellowdog Updater Modified

+ 

+ https://www.freedesktop.org/software/PackageKit/[PackageKit] -

+ PackageKit gui tool ('add/remove software' in your menu)

+ 

+ http://rpm.org[rpm] - RPM package manager.

+ 

+ http://ww1.yum-extender.org/[yumex] - Yum Extender.

+ 

+ Category:Software_Management[Category:Software Management]

+ '''

+ 

+ See a typo, something missing or out of date, or anything else which can be

+ improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -0,0 +1,137 @@ 

+ = PackageKit Items Not Found

+ 

+ '''

+ 

+ [IMPORTANT]

+ ======

+ 

+ This page was automatically converted from https://fedoraproject.org/wiki/PackageKit_Items_Not_Found

+ 

+ It is probably

+ 

+ * Badly formatted

+ * Missing graphics and tables that do not convert well from mediawiki

+ * Out-of-date

+ * In need of other love

+ 

+ 

+ Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

+ 

+ Once you've fixed this page, remove this notice, and update

+ [filename]`modules/ROOT/nav.adoc`.

+ 

+ Once the document is live, go to the original wiki page and replace its text

+ with the following macro:

+ 

+ ....

+ {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

+ ....

+ 

+ ======

+ 

+ '''

+ 

+ 

+ [[missing-package]]

+ == Missing Package

+ 

+ Unfortunately, the package you were searching for is not available in

+ Fedora. There are a few common reasons why a package might not be in

+ Fedora's repositories:

+ 

+ * Fedora does not include software that is

+ link:Package_Not_Found#Patents[ encumbered by software patents].

+ * Fedora does not include proprietary software, only software with an

+ link:Licensing[ acceptable license].

+ * It is possible that no one has packaged it yet. You might consider

+ adding it to the link:PackageMaintainers/WishList[Package WishList], or

+ even link:PackageMaintainers/Join[packaging it yourself]!

+ 

+ [[missing-codec]]

+ == Missing Codec

+ 

+ Unfortunately, the codec you were searching for is not available in

+ Fedora. A codec is a program that enables encoding and/or decoding of a

+ data stream, in a specific format such as MP3, MOV, or WMV.

+ 

+ There are a few common reasons why a codec might not be in Fedora's

+ repositories:

+ 

+ * Many codecs are proprietary or link:Package_Not_Found#Patents[patent

+ encumbered].

+ * Some codecs may not be encumbered, but may be under an

+ link:Licensing[unacceptable license].

+ 

+ The Fedora Project FAQ and community sites provide answers to commonly

+ asked questions. link:Third_party_repositories[Third party repositories]

+ contain a wide variety of software that has not been included in the

+ official Fedora software repositories for various reasons. You can find

+ additional software using a search engine like

+ http://google.com[Google]. We would love to give you more specific

+ instructions on enabling additional codecs but our hands are tied up due

+ to software patents and legal restrictions around them. We apologize for

+ the inconvenience caused by software patents and our legal team is

+ working on getting these restrictions removed when it is possible to do

+ so. Scroll down more for details on what we are doing and how you can

+ help.

+ 

+ [[missing-driver]]

+ == Missing Driver

+ 

+ Unfortunately, the driver you were searching for is not available in

+ Fedora. There are a few common reasons why a driver might not be in

+ Fedora's repositories:

+ 

+ * Some drivers are proprietary or link:Package_Not_Found#Patents[patent

+ encumbered].

+ * Some hardware may not be supported under Linux yet, or is not yet in

+ the upstream Linux kernel.

+ 

+ Fedora strongly encourages new drivers to be included in upstream, and

+ does not package individual, out-of-tree, kernel drivers.

+ 

+ The Fedora Project FAQ and the more informal, unofficial

+ http://fedorafaq.org[1] provide useful answers on commonly asked

+ questions. However, the unofficial site is not associated with or

+ supported by the Fedora Project. You can find many interesting things

+ using a search engine like http://google.com[Google].

+ link:Third_party_repositories[Third party repositories] might contain

+ software that has been not been included in the official Fedora software

+ repository.

+ 

+ [[missing-font]]

+ == Missing Font

+ 

+ Unfortunately, the font you were searching for is not available in

+ Fedora. There are a few common reasons why a font might not be in

+ Fedora's repositories:

+ 

+ * Fedora does not include proprietary fonts, it only uses fonts with an

+ link:Licensing/Fonts[ acceptable font license].

+ * It is possible that no one has packaged that font yet. You might

+ consider adding it to the :Category:Font_wishlist[Font WishList], or

+ even link:PackageMaintainers/Join[packaging it yourself]!

+ 

+ [[missing-mime-support]]

+ == Missing MIME Support

+ 

+ Unfortunately, there is nothing in Fedora that claims to support the

+ MIME type you were searching for. There are a few common reasons why

+ Fedora may not have support for a MIME type:

+ 

+ * Many MIME types are Windows-only. You may be able to use

+ http://en.wikipedia.org/wiki/Wine_(software)[Wine] to run a Windows

+ program under Linux that supports your MIME type.

+ * Some MIME types are only supported by proprietary or

+ link:Package_Not_Found#Patents[patent encumbered] software.

+ * It is possible that acceptable software to support your MIME type

+ exists, but that no one has packaged it yet. You might consider adding

+ it to the link:PackageMaintainers/WishList[Package WishList], or even

+ link:PackageMaintainers/Join[packaging it yourself]!

+ 

+ [[fedora-position-on-software-patents]]

+ == Fedora Position on Software Patents

+ '''

+ 

+ See a typo, something missing or out of date, or anything else which can be

+ improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -0,0 +1,36 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: performing-administration-tasks-using-sudo

+ [id='performing-administration-tasks-using-sudo']

+ = Performing administration tasks using sudo

+ 

+ How to perform tasks requiring *root* privileges without logging in as *root*.

+ 

+ include::{partialsdir}/con_what-is-sudo.adoc[leveloffset=+1]

+ 

+ 

+ [id='how-to-use-sudo']

+ == How to use sudo

+ 

+ include::{partialsdir}/con_using-sudo-assign-admin-privileges.adoc[leveloffset=+2]

+ 

+ include::{partialsdir}/proc_using-same-password-for-root-as-user.adoc[leveloffset=+2]

+ 

+ include::{partialsdir}/con_logging-sudo-commands.adoc[leveloffset=+2]

+ 

+ 

+ [[warning-and-caveats]]

+ == Warnings and caveats

+ 

+ You must use the user account you created following the installation process, at first boot, for daily use and the *root* account only for system administration. Avoid using *root* for any non-administration usage, since the account makes it easy to create security or data risks.

+ 

+ There are several potential risks to keep in mind when using the [command]`sudo` command. You can avoid them by editing the [filename]`/etc/sudoers` configuration file using [command]`visudo` command.

+ 

+ include::{partialsdir}/con_sudo-timeout.adoc[leveloffset=+2]

+ 

+ include::{partialsdir}/con_using-sudo-access-docker.adoc[leveloffset=+2]

+ 

+ include::{partialsdir}/proc_run-docker-using-sudo.adoc[leveloffset=+2]

+ 

+ include::{partialsdir}/con_using-sudo-without-password.adoc[leveloffset=+2]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/postgresql.adoc en-US/postgresql.adoc
file renamed
+16 -31
@@ -18,7 +18,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:
@@ -33,8 +33,7 @@ 

  

  

  [[installation]]

- Installation

- ~~~~~~~~~~~~

+ == Installation

  

  The installation and initialization of the postgresql server is a little

  bit different in comparison to other packages and other linux distros.
@@ -97,8 +96,7 @@ 

  `$ sudo postgresql-setup --initdb --unit postgresql`

  

  [[upgrade]]

- Upgrade

- ~~~~~~~

+ == Upgrade

  

  As you can see from error message in my example, it is not a fresh

  installation, but ugprade.
@@ -137,8 +135,7 @@ 

  more information, see link:#link-upgrade[official documentation].

  

  [[tips-and-tricks]]

- Tips and tricks

- ~~~~~~~~~~~~~~~

+ == Tips and tricks

  

  For database management is comfortable to use graphical tools such as

  phpPgAdmin or pgadmin3
@@ -152,8 +149,7 @@ 

  `$ sudo dnf install pgadmin3`

  

  [[firewall]]

- Firewall

- ~~~~~~~~

+ == Firewall

  

  PostgreSQL operates on port 5432 (or whatever else you set in your

  `postgresql.conf`). In firewalld you can open it like this:
@@ -171,8 +167,7 @@ 

  to the whole world.

  

  [[selinux]]

- SELinux

- ~~~~~~~

+ == SELinux

  

  If you have SELinux enforced, you may run into trouble when trying to do

  some non-standard configuration. For example if you would like to change
@@ -193,8 +188,7 @@ 

  `# setsebool -P httpd_can_network_connect_db on`

  

  [[user-creation-and-database-creation]]

- User Creation and Database Creation

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ == User Creation and Database Creation

  

  Soon you run into need of creating a user (and database for the user).

  First, you have to switch user to interact with postgres:
@@ -226,8 +220,7 @@ 

  `$ createdb --owner=lenny carl`

  

  [[configuration]]

- Configuration

- ~~~~~~~~~~~~~

+ == Configuration

  

  The postgresql server is using two main configuration files

  
@@ -235,8 +228,7 @@ 

  * /var/lib/pgsql/data/pg_hba.conf

  

  [[systemd]]

- systemd

- ^^^^^^^

+ === systemd

  

  Some configuration parameters are passed to daemon via command line

  options. This behaviour may override settings in postgresql.conf. For
@@ -255,8 +247,7 @@ 

  for more details.

  

  [[postgresql.conf]]

- postgresql.conf

- ^^^^^^^^^^^^^^^

+ === postgresql.conf

  

  If you want postgres to accept network connections, you should change

  
@@ -267,8 +258,7 @@ 

  `listen_addresses = '*'`

  

  [[pg_hba.conf]]

- pg_hba.conf

- ^^^^^^^^^^^

+ === pg_hba.conf

  

  Once your database is set up, you need to configure access to your

  database server. This may be done by editing file
@@ -320,8 +310,7 @@ 

  link:#link-pghba[pg_hba.conf file].

  

  [[optimisation]]

- Optimisation

- ~~~~~~~~~~~~

+ == Optimisation

  

  Default configuration of postgres is severely undertuned. It can handle

  simple application with not so often database access but if you require
@@ -330,8 +319,7 @@ 

  logging mechanism is configured not very intuitively.

  

  [[performance]]

- Performance

- ^^^^^^^^^^^

+ === Performance

  

  Number of clients which may be connected to PostgreSQL at the same time:

  
@@ -363,8 +351,7 @@ 

  link:#link-tuning[documentation about] tuning PostgreSQL.

  

  [[logging]]

- Logging

- ^^^^^^^

+ === Logging

  

  By default, logs are rotated every week and you don't find much

  information in there (one could miss log level, date, time, ...). Also
@@ -433,8 +420,7 @@ 

  `log_line_prefix = '%t [%p] '`

  

  [[final-recipe]]

- Final recipe

- ++++++++++++

+ ==== Final recipe

  

  `log_destination = 'stderr'` +

  `logging_collector = on` +
@@ -447,8 +433,7 @@ 

  `log_line_prefix = '%t %u@%r:%d [%p] '`

  

  [[reference]]

- Reference

- ~~~~~~~~~

+ == Reference

  

  link:PostgreSQL/README.rpm-dist[Full RPM packaging documentation]

  

@@ -0,0 +1,25 @@ 

+ [id='proc_installing-an-RPM-file']

+ = Installing an RPM File

+ 

+ This procedure shows you how to install an RPM file after you have downloaded the file to your desktop. An RPM file contains the required installation packages for a software.

+ 

+ ._Prerequisites_

+ 

+ * You must have administrative permission to install new RPM files on your system. Either root password or sudo access is required.

+ 

+ ._Procedure_

+ 

+ . Open a terminal.

+ . Change your working directory to the location of the RPM file. If you have downloaded the RPM file to the `Downloads` directory, enter:

+ +

+ [subs=quotes]

+ ----

+ $ cd ~/Downloads

+ ----

+ +

+ . Install the RPM file:

+ +

+ [subs=quotes]

+ ----

+ $ sudo rpm -i NAME_OF_RPM.rpm

+ ----

@@ -0,0 +1,27 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: setting-key-shortcut

+ [id='setting-key-shortcut_{context}']

+ = Setting a key shortcut to run an application in GNOME

+ 

+ If you frequently use a certain application, you can set a keyboard shortcut to quickly launch that application on GNOME.

+ 

+ This example shows how to set a key shortcut to launch the terminal.

+ 

+ To set a key shortcut to run an application:

+ 

+ . Navigate to menu:Settings[Keyboard] to open the *Keyboard Shortcuts* list.

+ . Click `+` at the bottom of the list to create a new shortcut.

+ . Enter the following details in the *Add Custom Shortcut* window:

+ * Add a `Name` for your shortcut, for example, `Terminal`.

+ * Enter the command that launches the application. For example, `gnome-terminal`.

+ . Click *Set Shortcut* to open the *Set Custom Shortcut* window.

+ . Type a keyboard shortcut, for example `Ctrl-Alt-T`.

+ . Click *Add*.

+ 

+ Your shortcut appears under *Custom Shortcuts* and is ready to use.

+ 

+ image:custom_shortcut.png[]

+ 

+ To edit or remove your shortcut, click the shortcut to open its details.

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,96 @@ 

+ = How to use QEMU

+ 

+ QEMU is a very flexible virtualization technology however it is quite slow and it is recommended that you understand and evaluate alternative solutions before picking this one.

+ Refer to https://fedoraproject.org/wiki/Getting_started_with_virtualization[Getting started with virtualization]

+ 

+ [[qemu]]

+ == QEMU

+ 

+ QEMU is a generic and open source processor emulator which achieves a good emulation speed by using dynamic translation.

+ 

+ QEMU has two operating modes:

+ 

+ * Full system emulation.

+ In this mode, QEMU emulates a full system (for example a PC), including a processor and various peripherials.

+ It can be used to launch different Operating Systems without rebooting the PC or to debug system code.

+ * User mode emulation (Linux host only). In this mode, QEMU can launch Linux processes compiled for one CPU on another CPU.

+ 

+ [[download]]

+ == Download

+ 

+ QEMU is available on Fedora repository. It can be installed by using https://fedoraproject.org/wiki/dnf[DNF]:

+ 

+ ....

+ $ su -c "dnf install qemu"

+ ....

+ 

+ 

+ [[qemu-commands-since-f]]

+ == QEMU commands since F?+

+ 

+ To discover the qemu commands that are installed perform the following:

+ 

+ ....

+ $ ls /usr/bin/qemu-*

+ ....

+ 

+ In the following examples where "qemu" is, substitute your command for executing qemu. E.g.

+ 

+ ....

+ qemu-system-i386

+ ....

+ 

+ or

+ 

+ ....

+ qemu-i386

+ ....

+ 

+ Of course, this does not apply to "qemu-img".

+ 

+ [[qemu-virtual-machine-installation]]

+ == QEMU virtual machine installation

+ 

+ Create the virtual image for the system:

+ 

+ ....

+ $ qemu-img create fedora.qcow 5G

+ ....

+ 

+ Of course you are not obliged to take 5GB.

+ 

+ Note: Even if you take 10GB this does NOT mean that the image does really HAVE the size of 10GB. It just means that your new system is limited up to 10GB - if the new system takes only 1,2 GB also the image will only be at 1,2GB.

+ 

+ Now let's install the OS. Put in the install CD and type into your konsole (all in one line without break):

+ 

+ ....

+ $ qemu -cdrom /dev/cdrom -hda fedora.qcow -boot d -net nic -net user -m 196 -localtime

+ ....

+ 

+ "-user -net" is important to have internet access within your new system.

+ "-m 196" is the Set virtual RAM size (megabytes), default is 128 MB, I chose 196.

+ 

+ The install may take some time. After the install, qemu will try to boot the new OS itself.

+ Maybe this may fail (was the case for me) - but don't worry.

+ If that happens: just close the qemu window and type the following command into your konsole to launch your new OS:

+ 

+ ....

+ $qemu fedora.qcow -boot c -net nic -net user -m 196 -localtime

+ ....

+ 

+ [[testing-iso-images]]

+ == Testing ISO Images

+ 

+ Type, in the proper directory

+ 

+ ....

+ $ qemu -m 512M -cdrom <isoname>.iso

+ ....

+ 

+ [[debugging]]

+ == Debugging

+ 

+ To get kernel output dumped to a file outside the virtual system, add e.g. "-serial file:/tmp/qemu-output.log" to the qemu command line.

+ When booting the virtual system, add "console=ttyS0" to the kernel boot parameters.

+ 

+ This output is particularly helpful if you are having trouble booting the system, in which case you may also wish to remove "rhgb" and "quiet" from the kernel boot parameters.

@@ -0,0 +1,74 @@ 

+ // This assembly is included in the following assemblies:

+ //

+ // <List assemblies here, each on a new line>

+ 

+ // Save the context of the assembly that is including this one.

+ // This is necessary for including assemblies in assemblies.

+ // See also the complementary step on the last line of this file.

+ :parent-context: {context}

+ // Base the file name and the ID on the assembly title. For example:

+ // * file name: my-assembly-a.adoc

+ // * ID: [id='my-assembly-a']

+ // * Title: = My assembly A

+ 

+ // The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.

+ [id='fedora-on-raspberry-pi']

+ // If the assembly is reused in other assemblies in a guide, include {context} in the ID: [id='a-collection-of-modules-{context}'].

+ = Fedora on Raspberry Pi

+ //If the assembly covers a task, start the title with a verb in the gerund form, such as Creating or Configuring.

+ :context: rpi

+ // The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.

+ 

+ The link:https://www.raspberrypi.org[Raspberry Pi] is a credit card-sized ARM based single board computer (SBC).

+ The Raspberry Pi Model B versions 2 and 3 are supported for Fedora 25 or newer, without any requirement of third party kernels or scripts to adjust offical images.

+ This documentation describes how to get started, and includes a Frequently Asked Questions (FAQ) section at the end of the document about what is supported, and what is not.

+ 

+ [id='raspberry-pi-prerequisites']

+ .Prerequisites

+ 

+ * Raspberry Pi Model B, version 2 or 3.

+ * A power supply (link:https://www.raspberrypi.org/help/faqs/#power[details on raspberrypi.org]).

+ ** Minimum 2 Amps for Raspberry Pi Model B, version 2.

+ ** Minimum 2.5 Amps for the Raspberry Pi Model B, version 3.

+ * HDMI-compatible Monitor or TV.

+ * A USB keyboard and USB mouse.

+ * SD card reader.

+ * A microSD Card (16 GB or larger).

+ * A computer running Microsoft Windows, Apple OS X, or Linux.

+ * A Fedora ARM image from: link:https://arm.fedoraproject.org/[].

+ 

+ The procedure for installing Fedora ARM on a microSD in preparation for using Fedora on a Raspberry Pi depends on your computers' operating system (Microsoft Windows, Apple OS X, or Linux).

+ 

+ * For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}>>.

+ * For users of other Linux distributions, see: <<installing-fedora-on-a-raspberry-pi-for-linux-users_{context}>>.

+ * For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}>>.

+ * For Apple OS X users, see: <<installing-fedora-on-a-raspberry-pi-for-apple-osx-users_{context}>>.

+ 

+ // The following include statements pull in the module files that comprise the assembly. Include any combination of concept, procedure, or reference modules required to cover the user story. You can also include other assemblies.

+ 

+ // [leveloffset=+1] ensures that when a module starts with a level-1 heading (= Heading), the heading will be interpreted as a level-2 heading (== Heading) in the assembly.

+ 

+ include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-for-linux-users.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-for-apple-osx-users.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_booting-fedora-on-a-raspberry-pi-for-the-first-time.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/ref_frequently-asked-questions_-installing-fedora-on-a-raspberry-pi.adoc[leveloffset=+1]

+ 

+ == Additional Resources

+ 

+ * The most up-to-date information can be found on the link:https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi?rd=Raspberry_Pi[Raspberry Pi page] of the Fedora Wiki.

+ * For Raspberry Pi hardware specifications and project ideas, see: link:https://www.raspberrypi.org/[The Raspberry Pi Foundation Website].

+ * For information on configuring Fedora, including installing programs and updates, see: link:https://docs.fedoraproject.org/f28/system-administrators-guide/[Fedora Docs: System Administrator’s Guide]

+ * For assistance or support, see:

+ ** link:https://ask.fedoraproject.org/[Ask Fedora]

+ ** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]

+ ** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]

+ 

+ // Restore the context to what it was before this assembly.

+ :context: {parent-context}

modules/ROOT/pages/repositories.adoc en-US/repositories.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,200 @@ 

+ [[chap-how-to-reset-a-root-password]]

+ = How to Reset the root Password

+ 

+ Setting up a root password is one of the steps when installing Fedora.

+ If you forget, or lose, the root password, there are two common methods to reset it:

+ 

+ * In Rescue Mode

+ 

+ * Using a Fedora Live Media (USB/DVD/CD)

+ 

+ 

+ [[sect-how-to-reset-the-password-from-emergency-or-single-user-mode]]

+ == How to reset the root password in Rescue Mode

+ 

+ [NOTE]

+ 

+ ====

+ 

+ Changing passwords as root does not prompt for the old password.

+ 

+ ====

+ 

+ While booting the system the link:++grub2.html++[GRUB2] menu will be displayed.

+ To boot the system into rescue mode using `bash` follow these steps:

+ 

+ . Use the arrow keys to select the boot entry you want to edit

+ 

+ . Press *e* to edit that entry

+ 

+ . Use the arrow keys to go to the line that starts with `linux`, `linux16`, or `linuxefi`

+ 

+ . Go the the end of that line, add a space then type `rw init=/bin/bash`.

+ If your disk is encrypted, you may need to add `plymouth.enable=0`

+ 

+ . Press *Ctrl-x* or *F10* to boot that entry

+ 

+ . Run the command:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ passwd

+ 

+ ----

+ +

+ It will prompt you to enter the new root password twice.

+ 

+ . Restore the SELinux context and permissions with:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ touch /.autorelabel

+ 

+ ----

+ 

+ +

+ 

+ [WARNING]

+ 

+ ====

+ 

+ If you do not restore the SELinux permissions, the boot process may fail.

+ You may have to do a hard-reboot and start back at step 1.

+ 

+ ====

+ 

+ . Reboot the machine with:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ /sbin/reboot -f

+ 

+ ----

+ 

+ The system may take a while to boot as SELinux will be relabeling its permissions on the filesystem.

+ If you see the Plymouth boot screen you can press the `ESC` key on your keyboard to view the SELinux progress.

+ Once it is complete, your system is ready and your root password has been successfully changed.

+ 

+ [[sect-reset-password-using-the-fedora-live-media]]

+ == How to reset the root password with a Fedora Live Media

+ 

+ [NOTE]

+ 

+ ====

+ 

+ To download and create a live USB of Fedora Workstation, follow the instructions on the link:++live-usb.html++[Fedora USB Live Media Quick Doc].

+ 

+ ====

+ 

+ . Boot the Live installation media and choose `Try Fedora`

+ 

+ . From the desktop, open a terminal and switch to root using `su` (it won't ask for a password)

+ 

+ . To view your hard drive device nodes, in the terminal type: `df -H`.

+ For this example we will use `/dev/sda1` for the `/boot` partition and `/dev/sda2` for the root `/` partition.

+ +

+ If you are using LVM partitions, type: `sudo lvscan` and note the `/dev` path of your root partition.

+ For this example we will use `/dev/fedora/root`.

+ 

+ . Create a directory for the mount point (use the `-p` option to create subdirectories):

+ +

+ [source,bash]

+ 

+ ----

+ 

+ mkdir -p /mnt/sysimage/boot

+ 

+ ----

+ 

+ . Mount the `/` (root) partition (be sure to use the actual device node or LVM path of your root `/` partition):

+ +

+ To mount root on a *standard partition* scheme enter:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ mount /dev/sda2 /mnt/sysimage 

+ 

+ ----

+ +

+ To mount root on an *LVM partition* scheme enter:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ mount /dev/fedora/root /mnt/sysimage

+ 

+ ----

+ 

+ . Continue the process by mounting `/boot`, `proc`, `/dev`, and `/run` with:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ mount /dev/sda1 /mnt/sysimage/boot

+ 

+ mount -t proc none /mnt/sysimage/proc

+ 

+ mount -o bind /dev /mnt/sysimage/dev

+ 

+ mount -o bind /run /mnt/sysimage/run

+ 

+ ----

+ 

+ . `chroot` to the mounted root partition with:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ chroot /mnt/sysimage /bin/bash

+ 

+ ----

+ 

+ . Change the root password:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ passwd

+ 

+ ----

+ 

+ . Exit out of chroot with:

+ +

+ [source,bash]

+ 

+ ----

+ 

+ exit

+ 

+ ----

+ +

+ and exit out of the terminal.

+ 

+ . Reboot your system and boot from the hard drive.

+ 

+ Congratulations, your root password has been successfully changed.

+ 

+ [[sect-additional-troubleshooting]]

+ == Additional Troubleshooting

+ 

+ . If you cannot enter rescue mode because you forgot the Firmware/BIOS password here are some options:

+ 

+ .. Refer to your computer's documentation for instructions on resetting the Firmware/BIOS password in CMOS memory.

+ 

+ .. Temporarily move the system hard disk to another machine, and follow the procedures above to reset the root password.

+ 

+ . If you have set a password for your boot loader, refer to link:++creating-and-using-a-live-installation-image.html++[Creating and Using a Live Installation Image].

+ 

+ . If you want to reset the boot loader password, refer to the instructions on how to link:++https://fedoraproject.org/wiki/Reset_Bootloader_Password++[Reset the Bootloader Password]. 

\ No newline at end of file

@@ -0,0 +1,28 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: securing-the-system-by-keeping-it-up-to-date

+ :experimental:

+ 

+ [id='securing-the-system-by-keeping-it-up-to-date']

+ = Securing the system by keeping it up-to-date

+ 

+ This section explains:

+ 

+ * Why it is important to update your system regularly (link:#why-it-is-important-keeping-your-system-up-to-date[Why it is important to keep your system up-to-date])

+ * How to apply updates manually by using GUI or CLI (link:#manual-updating-using-cli[Manual updating using CLI])

+ * How to enable automatic updates (link:#setting-automatic-updates[Setting automatic updates])

+ 

+ include::{partialsdir}/con_why-it-is-important-keeping-your-system-up-to-date.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_manual-updating-using-gui.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_manual-updating-using-cli.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_setting-automatic-updates.adoc[leveloffset=+1]

+ 

+ 

+ [discrete]

+ == Additional Resources

+ 

+ * The https://docs-old.fedoraproject.org/en-US/Fedora/26/html/System_Administrators_Guide/ch-DNF.html[DNF] chapter in the Fedora System Administrator's Guide

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,16 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: switching-desktop-environments

+ :imagesdir: ./images

+ 

+ [[switching-desktop-environments]]

+ = Switching desktop environments

+ 

+ Fedora's default desktop environment is GNOME 3 in the Workstation spin, but it is very easy to try any of the many other desktop environments that are available without affecting your current desktop environment.

+ 

+ include::{partialsdir}/proc_installing-additional-desktop-enviroments.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_switching-desktop-enviroments-using-gui.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_switching-desktop-enviroments-using-cli.adoc[leveloffset=+1]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,72 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: prod_troubleshooting_selinux

+ 

+ [id='prod_troubleshooting_selinux']

+ = Troubleshooting SELinux

+ 

+ This document covers the basics of troubleshooting SELinux.

+ 

+ SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. For example, an SELinux error generated by the Apache web server may appear as `comm="/usr/sbin/httpd"`.

+ 

+ Each error message includes information on the source context (`scontext`) of that part of your system performing an action, and the target context (`tcontext`), the target of the action. In many cases, the source is a binary and the target a file.

+ 

+ == Understanding Denials

+ When SELinux prevents any software from accessing a particular resource, for example, when *Firefox* is denied access to `/etc/shadow`, it generates a message and logs it in `/var/log/audit/audit.log` or `/var/log/messages` if *audit* service is disabled. If the log contains `avc: denied` that means it is an SELinux policy denial. Note that you would need administrator privileges (root access) on your system to be able to read this log file. An example denial would look like:

+ -----

+ type=AVC msg=audit(1214965667.121:635): avc:  denied  { unix_read unix_write } for  pid=15524 comm="npviewer.bin"

+ key=59918130 scontext=unconfined_u:unconfined_r:nsplugin_t:s0-s0:c0.c1023

+ tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s

+ -----

+ == Using the setroubleshoot utility

+ 

+ *setroubleshoot* is a utility that parses the messages from SELinux and provides comprehensive help on what it means and possible actions to take. It has both a graphical utility for your desktop and a server side component that can send email alerts. It is installed by default on Fedora. To install it on your system, use the *Software* tool in GUI or enter the following command:

+ -----

+ $ sudo dnf install setroubleshoot

+ -----

+ 

+ To start the program, run the following command:

+ -----

+ $ sealert

+ -----

+ 

+ You can find recent alerts in the browser that appears.

+ 

+ To troubleshoot an error, click the *troubleshoot* button in the SELinux Alert browser. The browser will return available options for resolving the error and commands to run to fix the problem.

+ 

+ [NOTE]

+ ====

+ Some troubleshooting events can be resolved by enabling a boolean switch policy. This will allow the activity to procede in the future, regardless of SELinux enforcing policy. It is not recommended to utilize booleans without fully understanding the issue. For more information on booleans, see the link:https://docs-old.fedoraproject.org/en-US/Fedora/25/html/SELinux_Users_and_Administrators_Guide/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html[Booleans] chapter in the SELinux User's and Administrator's Guide.

+ ====

+ 

+ 

+ ////

+ include::modules/con-troubleshooting-selinux-overview.adoc[leveloffset=+1]

+ 

+ include::modules/con-troubleshooting-selinux-access-is-denied.adoc[leveloffset=+2]

+ 

+ include::modules/con_troubleshooting_selinux_top_three_causes_of_problems.adoc[leveloffset=+1]

+ 

+ include::modules/con_troubleshooting_selinux_fixing_problems.adoc[leveloffset=+1]

+ 

+ include::modules/con_troubleshooting_selinux_searching_viewing_denials.adoc[leveloffset=+2]

+ 

+ include::modules/con_troubleshooting_selinux_disabling_permissive_domains.adoc[leveloffset=+2]

+ 

+ include::modules/con_troubleshooting_selinux_raw_audit_messages.adoc[leveloffset=+1]

+ 

+ include::modules/con_troubleshooting_selinux_sealert_messages.adoc[leveloffset=+2]

+ 

+ include::modules/con_troubleshooting_selinux_allowing_access_audit.adoc[leveloffset=+1]

+ 

+ include::modules/proc_troubleshooting_selinux_allowing_access_audit.adoc[leveloffset=+2]

+ ////

+ 

+ == Additional Resources

+ 

+  * link:https://docs-old.fedoraproject.org/en-US/Fedora/25/html/SELinux_Users_and_Administrators_Guide/chap-Security-Enhanced_Linux-Troubleshooting.html[Troubleshooting] in the SELinux User's and Administrator's Guide

+ 

+  * link:https://fedorapeople.org/~dwalsh/SELinux/Presentations/selinux_four_things.pdf[Four Key Causes of SELinux Errors]

+ 

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,183 @@ 

+ = Using UEFI with QEMU

+ 

+ '''

+ 

+ [IMPORTANT]

+ ======

+ 

+ This page was automatically converted from https://fedoraproject.org/wiki/Using_UEFI_with_QEMU

+ 

+ It is probably

+ 

+ * Badly formatted

+ * Missing graphics and tables that do not convert well from mediawiki

+ * Out-of-date

+ * In need of other love

+ 

+ 

+ Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

+ 

+ Once you've fixed this page, remove this notice, and update

+ [filename]`modules/ROOT/nav.adoc`.

+ 

+ Once the document is live, go to the original wiki page and replace its text

+ with the following macro:

+ 

+ ....

+ {{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}

+ ....

+ 

+ ======

+ 

+ '''

+ 

+ 

+ [[firmware-installation]]

+ Firmware installation

+ ---------------------

+ 

+ UEFI for x86 QEMU/KVM VMs is called OVMF (Open Virtual Machine

+ Firmware). It comes from EDK2 (EFI Development Kit), which is the UEFI

+ reference implementation.

+ 

+ [[installing-uefi-for-qemu-from-fedora-repos]]

+ Installing 'UEFI for QEMU' from Fedora repos

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ Since June 2016, OVMF is available in Fedora repositories. All you need

+ to have installed is `edk2-ovmf` RPM. Furthermore, it should be now a

+ dependency of the package, so you probably have it installed already.

+ This includes firmware for secureboot (`OVMF_CODE.secboot.fd`)

+ 

+ [[installing-uefi-for-qemu-nightly-builds]]

+ Installing 'UEFI for QEMU' nightly builds

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ Gerd Hoffmann, Red Hatter and QEMU developer, has a dnf repo on his

+ personal site that provides nightly builds of a whole bunch of QEMU/KVM

+ firmware, including EDK2/OVMF.

+ 

+ Here's how to pull down the nightly builds for x86:

+ 

+ ` sudo dnf install dnf-plugins-core` +

+ ` sudo dnf config-manager --add-repo `http://www.kraxel.org/repos/firmware.repo[`http://www.kraxel.org/repos/firmware.repo`] +

+ ` sudo dnf install edk2.git-ovmf-x64`

+ 

+ Note, these are nightly builds, and may occasionally be broken.

+ 

+ [[optionally-configure-libvirtd-to-advertise-uefi-support]]

+ Optionally Configure libvirtd to advertise UEFI support

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ Libvirt needs to know about UEFI->NVRAM config file mapping, so it can

+ advertise it to tools like virt-manager/virt-install. On Fedora 22 and

+ later, libvirt packages are configured to look for the nightly build

+ paths, so this will work out of the box.

+ 

+ However, if you want to use custom binaries, you will need to edit the

+ nvram variable in /etc/libvirt/qemu.conf and restart libvirtd.

+ 

+ [[creating-a-vm]]

+ Creating a VM

+ -------------

+ 

+ [[virt-manager]]

+ virt-manager

+ ~~~~~~~~~~~~

+ 

+ Create a new VM in virt-manager. When you get to the final page of the

+ 'New VM' wizard, do the following:

+ 

+ * Click 'Customize before install', then select 'Finish'

+ * On the 'Overview' screen, Change the 'Firmware' field to select the

+ 'UEFI x86_64' option.

+ * Click 'Begin Installation'

+ * The boot screen you'll see should use `linuxefi` commands to boot the

+ installer, and you should be able to run `efibootmgr` inside that

+ system, to verify that you're running an UEFI OS.

+ 

+ [[virt-install]]

+ virt-install

+ ~~~~~~~~~~~~

+ 

+ Add `--boot uefi` to your `virt-install` command. Example:

+ 

+ ` sudo virt-install --name f20-uefi \` +

+ `   --ram 2048 --disk size=20 \` +

+ `   --boot uefi \` +

+ `   --location `https://dl.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/os/[`https://dl.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/os/`]

+ 

+ [[testing-secureboot-in-a-vm]]

+ Testing Secureboot in a VM

+ --------------------------

+ 

+ These steps describe how to test Fedora Secureboot support inside a KVM

+ VM. The audience here is QA folks that want to test secureboot, and any

+ other curious parties. This requires configuring the VM to use UEFI, so

+ it builds upon the previous UEFI steps.

+ 

+ [[run-enrolldefaultkeys.efi]]

+ Run EnrollDefaultKeys.efi

+ ~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ (Formerly this article recommended the independent utility

+ "LockDown_ms.efi".)

+ 

+ Since OVMF doesn't ship with any SecureBoot keys installed, we need to

+ install some to mimic what an MS certified UEFI machine will ship with.

+ OVMF now ships with the binaries required to set up a default set of

+ keys. The easiest way is to use UefiShell.iso which is available at

+ `/usr/share/edk2/ovmf/UefiShell.iso`. Boot your VM with this as the

+ CD-ROM image and it should boot into the UEFI shell. At the prompt

+ 

+ * Shell> fs0:

+ * FS0:\> EnrollDefaultKeys.efi

+ * FS0:\> reset

+ * The VM will restart. Let it boot into Fedora as normal. Log in

+ * You should see the string 'Secure boot enabled' in dmesg. Secureboot

+ is now enabled for every subsequent boot.

+ 

+ [[testing-fedora-cddvd-secure-boot-in-a-vm]]

+ Testing Fedora CD/DVD Secure Boot in a VM

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ Once you have a secureboot configured VM as described above, it's easy

+ to use this to test ISO media secureboot support.

+ 

+ * Use virt-manager to attach the ISO media to your VM

+ * Use virt-manager to change the VM boot settings to boot off the CDROM

+ * Start the VM

+ * Switch to a terminal inside the VM, verify Secureboot is enabled by

+ checking dmesg

+ 

+ [[notes]]

+ Notes

+ -----

+ 

+ [[using-uefi-with-aarch64-vms]]

+ Using UEFI with AArch64 VMs

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ 

+ link:Architectures/ARM/AArch64[Fedora's AArch64 releases] will only run

+ on UEFI, so require UEFI inside the VM. However the steps are slightly

+ different. See this page for complete documentation:

+ https://fedoraproject.org/wiki/Architectures/AArch64/Install_with_QEMU

+ 

+ [[extra-links]]

+ Extra links

+ -----------

+ 

+ * QA:Testcase_Virtualization_UEFI[QA:Testcase Virtualization UEFI]

+ * http://www.linux-kvm.org/page/OVMF[KVM wiki OVMF page]

+ * https://wiki.ubuntu.com/SecurityTeam/SecureBoot[Ubuntu secureboot

+ page]

+ * http://en.opensuse.org/openSUSE:UEFI_Secure_boot_using_qemu-kvm[OpenSUSE

+ secureboot page]

+ * http://www.labbott.name/blog/2016/09/15/secure-ish-boot-with-qemu/[Using

+ SecureBoot with QEMU]

+ 

+ Category:Virtualization Category:QA

+ '''

+ 

+ See a typo, something missing or out of date, or anything else which can be

+ improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

@@ -0,0 +1,37 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: understanding-and-administering-systemd

+ :source-highlighter: prettify

+ 

+ [id='understanding-and-administering-systemd']

+ = Understanding and administering systemd

+ 

+ Learn the basic principles of systemd: how to configure it and use to administer the system.

+ 

+ include::{partialsdir}/con_understanding-systemd.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_starting-stopping-and-querying-systemd-services.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_modifying-existing-systemd-services.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_creating-new-systemd-services.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_converting-sysvinit-services.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/ref_common-service-parameters.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/ref_mapping-runlevel-to-targets.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/ref_mapping-service-commands.adoc[leveloffset=+1]

+ 

+ 

+ [discrete]

+ == Additional resources

+ 

+ * http://www.freedesktop.org/wiki/Software/systemd[Project homepage]

+ * http://0pointer.de/blog/projects/ - Lennart's blog has lots of information about systemd. Lennart is the primary systemd developer

+ * http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions

+ * http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks

+ * link:Features/systemd[ Features Fedora 15:systemd]

+ * http://fosdem.org/2011/interview/lennart-poettering.html[Interview with the developer]

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

modules/ROOT/pages/upgrading-fedora-online.adoc en-US/upgrading-fedora-online.adoc
file renamed
+24 -47
@@ -18,7 +18,7 @@ 

  Pull requests accepted at https://pagure.io/fedora-docs/quick-docs

  

  Once you've fixed this page, remove this notice, and update

- `_topic_map.yml`.

+ [filename]`modules/ROOT/nav.adoc`.

  

  Once the document is live, go to the original wiki page and replace its text

  with the following macro:
@@ -36,12 +36,10 @@ 

  using (without the DNF system upgrade plugin).

  

  [[upgrading-fedora-using-dnf-directly]]

- Upgrading Fedora using dnf directly

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ == Upgrading Fedora using dnf directly

  

  [[participate]]

- Participate

- ~~~~~~~~~~~

+ == Participate

  

  If you are upgrading using Dnf and it shows any general dependency

  issues, please file them in http://bugzilla.redhat.com[Bugzilla]. But
@@ -53,8 +51,7 @@ 

  link:SIGs/LiveUpgrade[ Live Upgrade Special Interest Group].

  

  [[upgrading-across-multiple-releases]]

- Upgrading across multiple releases

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ == Upgrading across multiple releases

  

  If you need to upgrade across several releases, it is generally

  recommended to go one release at a time: for example, rather than going
@@ -64,20 +61,17 @@ 

  see link:#eol[the end-of-life section].

  

  [[instructions-to-upgrade-using-dnf]]

- Instructions to upgrade using dnf

- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ == Instructions to upgrade using dnf

  

  [[backup-your-system]]

- 1. Backup your system

- ^^^^^^^^^^^^^^^^^^^^^

+ === 1. Backup your system

  

  Backup any personal data to an external hard drive or to another

  machine. If there is some unrecoverable error that requires a fresh

  install, you don't want to lose any data.

  

  [[read-about-common-problems]]

- 2. Read about common problems

- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

+ === 2. Read about common problems

  

  Further down in this page there is a list of common problems specific to

  dnf upgrades for specific versions. Some of them require attention
@@ -92,8 +86,7 @@ 

  link:Common_bugs[Common bugs].

  

  [[clean-stuff]]

- 3. Clean Stuff

- ^^^^^^^^^^^^^^

+ === 3. Clean Stuff

  

  Review and remove all .rpmsave and .rpmnew files before and after

  upgrading. (And if you have selinux enabled then remember to check
@@ -103,8 +96,7 @@ 

  non-standard packages.

  

  [[do-the-upgrade]]

- 4. Do the upgrade

- ^^^^^^^^^^^^^^^^^

+ === 4. Do the upgrade

  

  If you have 3rd party repositories configured, you may need to adjust

  them for the new Fedora version. If you switch from one Fedora release
@@ -121,8 +113,7 @@ 

  Log out of your graphical desktop and then

  

  [[fedora-upgrade]]

- fedora-upgrade

- ++++++++++++++

+ ==== fedora-upgrade

  

  A small script named fedora-upgrade is available which aims to automate

  the process outlined below. To run it, do the following
@@ -139,8 +130,7 @@ 

  Alternatively, follow the manual steps:

  

  [[go-to-a-text-console]]

- Go to a text console

- ++++++++++++++++++++

+ ==== Go to a text console

  

  ....

  ctrl + alt + F2
@@ -155,16 +145,14 @@ 

  ....

  

  [[fully-update-your-current-fedora-install]]

- Fully update your current Fedora install

- ++++++++++++++++++++++++++++++++++++++++

+ ==== Fully update your current Fedora install

  

  ....

  # dnf upgrade

  ....

  

  [[install-the-package-signing-key-for-the-release-you-are-upgrading-to]]

- Install the package signing key for the release you are upgrading to

- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+ ==== Install the package signing key for the release you are upgrading to

  

  If you are upgrading across two releases or fewer from Fedora 20 or

  later, this step should be unnecessary. If you are upgrading from an
@@ -195,8 +183,7 @@ 

  that happens, download the file with or and import the downloaded file.

  

  [[clean-the-cache]]

- Clean the cache

- +++++++++++++++

+ ==== Clean the cache

  

  Then remove all traces of the version you are leaving from the dnf cache

  in `/var/cache/dnf`.
@@ -206,8 +193,7 @@ 

  ....

  

  [[upgrade-all-packages]]

- Upgrade all packages

- ++++++++++++++++++++

+ ==== Upgrade all packages

  

  Run the upgrade command:

  
@@ -216,8 +202,7 @@ 

  ....

  

  [[make-sure-fedora-is-upgraded]]

- 5. Make sure Fedora is upgraded

- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

+ === 5. Make sure Fedora is upgraded

  

  Distro-sync will usually take care of upgrades for the third party

  repositories you have enabled as well. Confirm with after the upgrade
@@ -251,8 +236,7 @@ 

  ....

  

  [[preparing-for-reboot]]

- 6. Preparing for reboot

- ^^^^^^^^^^^^^^^^^^^^^^^

+ === 6. Preparing for reboot

  

  Before booting you should usually install the bootloader from your new

  grub by running
@@ -274,8 +258,7 @@ 

  ....

  

  [[cleanup-your-system]]

- 7. Cleanup your system

- ^^^^^^^^^^^^^^^^^^^^^^

+ === 7. Cleanup your system

  

  Again, cleanup your system as described in section 2. Also you might

  want to remove some cache files that are no longer used, for example
@@ -286,8 +269,7 @@ 

  * /var/lib/mock

  

  [[release-specific-notes]]

- Release specific notes

- ~~~~~~~~~~~~~~~~~~~~~~

+ == Release specific notes

  

  Note: the release-specific notes for link:End_of_life[End of life]

  releases are on the
@@ -295,16 +277,14 @@ 

  manager upgrade page].

  

  [[from-pre-release]]

- From pre-release

- ^^^^^^^^^^^^^^^^

+ === From pre-release

  

  If you are upgrading to a final release from an Alpha, Beta, or release

  candidate, please see link:Upgrading_from_pre-release_to_final[Upgrading

  from pre-release to final].

  

  [[to-rawhide]]

- To Rawhide

- ^^^^^^^^^^

+ === To Rawhide

  

  See the link:Releases/Rawhide[Rawhide] release page for more information

  on Rawhide.
@@ -322,20 +302,17 @@ 

  ....

  

  [[fedora-25]]

- Fedora 25

- ^^^^^^^^^

+ === Fedora 25

  

  No special instructions. Follow the above instructions.

  

  [[fedora-24]]

- Fedora 24

- ^^^^^^^^^

+ === Fedora 24

  

  No special instructions. Follow the above instructions.

  

  [[upgrading-from-legacy-end-of-life-eol-fedora-releases]]

- Upgrading from legacy end of life (EOL) Fedora releases

- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

+ === Upgrading from legacy end of life (EOL) Fedora releases

  

  Note that Fedora strongly recommends against ever running an end-of-life

  release on any production system, or any system connected to the public

@@ -0,0 +1,84 @@ 

+ [[ch-Upgrading]]

+ = Upgrading to a new release of Fedora

+ 

+ [IMPORTANT]

+ ====

+ 

+ . Be sure to *back-up your data* before upgrading your Fedora system in the event something breaks and leaves your system unusable.

+ . Read the link:++https://fedoraproject.org/wiki/Releases#Current_Supported_Releases++[Release

+ Notes] carefully before attempting an upgrade.

+ 

+ ====

+ 

+ 

+ [[sect-upgrading-to-the-next-fedora-workstation-release]]

+ == Upgrading to the next Fedora Workstation release

+ 

+ As of Fedora Workstation 23, when the next stable release is available a graphical notification will appear similar to the update notifications.

+ Clicking this, or running the _Software_ application and going to the _Updates_ pane, will display a simple graphical interface for upgrading the system.

+ It will download the upgrade files, then prompt for a reboot to install them, similar to a system update.

+ When the upgrade is complete, the system will automatically reboot into the new release.

+ 

+ image:Upgradef24f25-gs.png[Upgradef24f25-gs.png,title="Upgradef24f25-gs.png",width=640]

+ 

+ [[sect-upgrading-using-the-dnf-system-upgrade-plugin]]

+ == Upgrading using the DNF System Upgrade plugin

+ 

+ This method is used to upgrade Fedora Workstation from the command-line.

+ It is also used to troubleshoot issues with packages preventing the graphical method from upgrading.

+ 

+ For instructions on upgrading with the DNF system upgrade plugin, refer to the link:++dnf-system-upgrade.html++[DNF System Upgrade Quick Doc].

+ 

+ [[sect-upgrading-the-fedora-atomic-host-via-rpm-ostree]]

+ == Upgrading the Fedora Atomic Host via rpm-ostree

+ 

+ For instructions on upgrading Fedora Atomic Host installations between Fedora releases, refer to the link:++atomic-host-upgrade.html++[Atomic Host Upgrade Quick Doc].

+ 

+ [[sect-can-i-upgrade-between-fedora-releases-using-only-dnf]]

+ == Can I upgrade between Fedora releases using only DNF?

+ 

+ Upgrading between Fedora releases without the link:++dnf_system_upgrade.html++[DNF system upgrade plugin] is not tested by the Fedora QA team.

+ Any issues using this method are not considered blockers for a release but in practice works for many users.

+ 

+ [[sect-can-i-update-from-a-pre-release-alpha-beta-or-other-development-snapshot-to-the-final-release]]

+ == Can I update from a pre-release (Alpha, Beta, or other development snapshot) to the final release?

+ 

+ If you are using a pre-release of Fedora, and want to know more about upgrading to the final release, refer to the

+ link:++https://fedoraproject.org/wiki/Upgrading_from_pre-release_to_final++[Upgrading from pre-release to final] page.

+ This is technically not an 'upgrade' operation, but an update.

+ There are some special considerations involved in making sure you stay on the update track you intend to use, which are documented on that page.

+ 

+ [[sect-how-do-i-upgrade-to-rawhide-and-branched]]

+ == How do I upgrade to Rawhide and Branched?

+ 

+ link:++https://fedoraproject.org/wiki/Releases/Rawhide++[Rawhide] and link:++https://fedoraproject.org/wiki/Releases/Branched++[Branched] are the development releases of Fedora.

+ They are suitable for users developing or testing Fedora before public release.

+ They are *NOT SUITABLE* for regular day-to-day use unless you are a fairly experienced user, and certainly not suitable for mission-critical use.

+ You should read through those pages carefully before deciding to run Branched or Rawhide.

+ See the link:++fedora-life-cycle.html++[Fedora Life Cycle Quick Doc] for more information on how the whole Fedora cycle works from Rawhide, to Branched, to the milestone releases (Alpha and Beta), to a 'final' release.

+ 

+ Upgrading to a Branched release or to Rawhide can be done with the link:++dnf_system_upgrade.html++[DNF system upgrade plugin].

+ Carefully read this page as there are some special notes to ensure a successful upgrade.

+ 

+ [[sect-can-i-upgrade-using-the-fedora-installer-anaconda]]

+ == Can I upgrade using the Fedora installer (anaconda)?

+ 

+ Fedora releases up to Fedora 17 included upgrade functionality in the Fedora installer, anaconda.

+ This can be a better choice than a package manager upgrade for some End Of Life (EOL) upgrades.

+ If you are attempting to upgrade from Fedora 16 or older, it is highly recommended to upgrade to Fedora 16 and perform an installer upgrade from Fedora 16 to Fedora 17 before upgrading any further.

+ 

+ To upgrade using the installer, boot the system from a network install or DVD image for the target release, and run through the initial steps of the install process.

+ After you select storage devices the installer should offer you the option to upgrade the installed system.

+ 

+ [IMPORTANT]

+ ====

+ 

+ If your installation is located on a 'specialized' storage device, be sure to configure and select it.

+ 

+ ====

+ 

+ [[sect-upgrading-from-end-of-life-releases]]

+ == Can I upgrade from an End Of Life (EOL) release?

+ 

+ Fedora strongly discourages running an end-of-life release on any production system, or any system connected to the public internet.

+ For more information, see the link:++dnf_system_upgrade.html++[DNF System Upgrade Quick Doc].

@@ -0,0 +1,15 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: adobe-flash

+ 

+ = Using Adobe Flash

+ 

+ include::{partialsdir}/3rdparty-message.adoc[]

+ 

+ include::{partialsdir}/con_what_is_adobe_flash.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_checking_fedora_version.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_installing_adobe_flash.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,97 @@ 

+ [id='sec-Using-AIDE']

+ = Checking Integrity With *AIDE*

+ 

+ Advanced Intrusion Detection Environment (AIDE) is a utility that creates a database of files on the system, and then uses that database to ensure file integrity and detect system intrusions.

+ 

+ == Installing *AIDE*

+ 

+ . To install the _aide_ package:

+ +

+ ----

+ $ sudo dnf install aide

+ ----

+ . To generate an initial database:

+ +

+ ----

+ $ sudo aide --init

+ Start timestamp: 2018-07-11 12:35:47 +0200 (AIDE 0.16)

+ AIDE initialized database at /var/lib/aide/aide.db.new.gz

+ 

+ Number of entries:	150666

+ 

+ ---------------------------------------------------

+ The attributes of the (uncompressed) database(s):

+ ---------------------------------------------------

+ 

+ /var/lib/aide/aide.db.new.gz

+   MD5      : 0isjEPsCORFk7laoGGz8tQ==

+   SHA1     : j0aPLakWChM+TAuxfVIpy9nqBOE=

+   RMD160   : nYyyx0AGZj4e5rwcz77afasXFrw=

+   TIGER    : IBVo5A2A4En1kM6zDjD/MnlkN4QWeSOw

+   SHA256   : YveypaI9c5PJNvPSZf8YFfjCMWfGUA8q

+              vyqLpLJWY0E=

+   SHA512   : TiUYmHYflS3A+j17qw5mW78Fn2yXLpCF

+              1LE1/RhiqqtMn1MjkKDrr+3TE+/vWfa4

+              7253cDhNmC6hoFndkS67Xw==

+ 

+ 

+ End timestamp: 2018-07-11 12:37:35 +0200 (run time: 1m 48s)

+ ----

+ +

+ NOTE: In the default configuration, the *aide --init* command checks just a set of directories and files defined in the `/etc/aide.conf` file. To include additional directories or files in the AIDE database, and to change their watched parameters, edit `/etc/aide.conf` accordingly.

+ 

+ . To start using the database, remove the `.new` substring from the initial database file name:

+ +

+ ----

+ $ sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz

+ ----

+ 

+ . To change the location of the *AIDE* database, edit the `/etc/aide.conf` file and modify the `DBDIR` value. For additional security, store the database, configuration, and the `/usr/sbin/aide` binary file in a secure location such as a read-only media.

+ +

+ IMPORTANT: To avoid SELinux denials after the AIDE database location change, update your SELinux policy accordingly. See the link:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/[SELinux User's and Administrator's Guide] for more information.

+ 

+ == Performing Integrity Checks

+ 

+ To initiate a manual check:

+ ----

+ $ sudo aide --check

+ Start timestamp: 2018-07-11 12:41:20 +0200 (AIDE 0.16)

+ AIDE found differences between database and filesystem!!

+ 

+ Summary:

+   Total number of entries:	150667

+   Added entries:		1

+   Removed entries:		0

+   Changed entries:		2

+ 

+ ---------------------------------------------------

+ Added entries:

+ ---------------------------------------------------

+ 

+ f++++++++++++++++: /etc/cups/subscriptions.conf.O

+ ...

+ [output truncated]

+ ----

+ 

+ At a minimum, *AIDE* should be configured to run a weekly scan. At most, *AIDE* should be run daily. For example, to schedule a daily execution of AIDE at _04:05_ a.m. using the *cron* command, see the link:https://docs.fedoraproject.org/f27/system-administrators-guide/monitoring-and-automation/Automating_System_Tasks.html[Automating System Tasks] chapter in the System Administration Guide.

+ 

+ Add the following line to the `/etc/crontab` file:

+ ----

+  05 4 * * * root /usr/sbin/aide --check

+ ----

+ 

+ == Updating an *AIDE* Database

+ 

+ After verifying the changes of your system such as, package updates or configuration files adjustments, update your baseline *AIDE* database:

+ ----

+ $ sudo aide --update

+ ----

+ The *aide --update* command creates the `/var/lib/aide/aide.db.new.gz` database file. To start using it for integrity checks, remove the `.new` substring from the file name.

+ 

+ == Additional Resources

+ 

+ For additional information on *AIDE*, see the following documentation:

+ 

+  - link:https://static.open-scap.org/ssg-guides/ssg-sl7-guide-ospp-rhel7-server.html#xccdf_org.ssgproject.content_group_aide[Guide to the Secure Configuration of Red Hat Enterprise Linux 7 (OpenSCAP Security Guide): Verify Integrity with AIDE]

+ 

+  - link:http://aide.sourceforge.net/stable/manual.html[The AIDE manual]

@@ -0,0 +1,20 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: using-nested-virtiualization-in-kvm

+ = How to enable nested virtualization in KVM

+ 

+ Learn how to run a virtual machine within a virtual machine.

+ 

+ include::{partialsdir}/proc_enabling-nested-virtualization-in-kvm.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_configuring-nested-virtualization-in-virt-manager.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_testing-nested-virtualization.adoc[leveloffset=+1]

+ 

+ 

+ == Additional resources

+ 

+ * https://bugzilla.redhat.com/show_bug.cgi?id=1055002

+ * http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/

+ * https://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,23 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: using-shared-system-certificates

+ [[using-shared-system-certificates]]

+ = Using Shared System Certificates

+ 

+ The Shared System Certificates storage enables NSS, GnuTLS, OpenSSL, and Java to share a default source for retrieving system certificate anchors and black list information. By default, the trust store contains the Mozilla CA list, including positive and negative trust. The system allows updating of the core Mozilla CA list or choosing another certificate list.

+ 

+ include::{partialsdir}/con_using-the-system-wide-trust-store.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_adding-new-certificates.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_managing-trusted-system-certificates.adoc[leveloffset=+1]

+ 

+ 

+ [[shared-system-certificates-additional-resources]]

+ == Additional Resources

+ 

+ For more information, see the following man pages:

+ 

+ * `update-ca-trust(8)`

+ * `trust(1)`

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,11 @@ 

+ ifdef::context[:parent-context: {context}]

+ :context: viewing-logs

+ 

+ include::{partialsdir}/con_viewing-logs.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_log-files-command-line.adoc[leveloffset=+1]

+ 

+ include::{partialsdir}/proc_log-files-GUI.adoc[leveloffset=+1]

+ 

+ ifdef::parent-context[:context: {parent-context}]

+ ifndef::parent-context[:!context:]

@@ -0,0 +1,180 @@ 

+ = Wine

+ 

+ 

+ 

+ http://winehq.org/[Wine] is an open source implementation of the Windows

+ API on top of X and OpenGL.

+ 

+ Wine emulates the Windows runtime environment by translating Windows system calls

+ into POSIX-compliant system calls, recreating the directory structure of Windows systems,

+ and providing alternative implementations of Windows system libraries,

+ system services through https://wiki.winehq.org/Wineserver[wineserver]

+ and various other components such as Internet Explorer, the Windows Registry Editor, and msiexec.

+ 

+ == Packages

+ 

+ Fedora's Wine packages are split up to allow for smaller installations.

+ The `wine` meta package will bring with it the most important components

+ of Wine. Expert users may want to pick specific components from the list

+ below:

+ 

+ [cols=",",]

+ |=======================================================================

+ |*name* |''' summary '''

+ 

+ |_wine_ |Meta package

+ 

+ |_wine-alsa_ |ALSA sound support for wine

+ 

+ |_wine-arial-fonts_ |Arial fonts provided by wine-staging

+ 

+ |_wine-capi_ |ISDN support for wine

+ 

+ |_wine-cms_ |Color Management for wine

+ 

+ |_wine-common_ |Common wine files and scripts

+ 

+ |_wine-core_ |Wine core package

+ 

+ |_wine-courier-fonts_ |Wine Courier font family

+ 

+ |_wine-desktop_ |Desktop integration features

+ 

+ |_wine-devel_ |Wine development environment

+ 

+ |_wine-filesystem_ |Filesystem directories and basic configuration for

+ wine

+ 

+ |_wine-fixedsys-fonts_ |Wine Fixedsys font family

+ 

+ |_wine-fonts_ |Wine font meta package

+ 

+ |_wine-ldap_ |LDAP support for wine

+ 

+ |_wine-marlett-fonts_ |Wine Marlett font family

+ 

+ |_wine-ms-sans-serif-fonts_ |Wine MS Sans Serif font family

+ 

+ |_wine-openal_ |OpenAL sound support for wine

+ 

+ |_wine-opencl_ |OpenCL support for wine

+ 

+ |_wine-pulseaudio_ |PulseAudio support for wine

+ 

+ |_wine-small-fonts_ |Wine Small font family

+ 

+ |_wine-symbol-fonts_ |Wine Symbol font family

+ 

+ |_wine-systemd_ |systemd configuration for the wine binfmt handler

+ 

+ |_wine-system-fonts_ |Wine System font family

+ 

+ |_wine-sysvinit_ |SysV initscript for the wine binfmt handler

+ 

+ |_wine-tahoma-fonts_ |Wine Tahoma font family

+ 

+ |_wine-tahoma-fonts-system_ |Wine Tahoma font family system integration

+ 

+ |_wine-twain_ |Twain (image scanning) support for wine

+ 

+ |_wine-wingdings-fonts_ |Wine Wingdings font family

+ 

+ |_wine-wingdings-fonts-system_ |Wine Wingdings font family system

+ integration

+ |=======================================================================

+ 

+ Additional documentation is provided via the ''wine-docs '' package.

+ 

+ [[available-versions]]

+ == Available versions

+ 

+ Fedora applies fixes and features from the *wine-staging* project. EPEL

+ packages do not use wine-staging patches.

+ 

+ *Current versions of Wine in Fedora:*

+ 

+ [cols=",",]

+ |=================

+ |Fedora 28 |3.4

+ |Fedora 27 |3.4

+ |Fedora 26 |3.4

+ |EPEL 7 |3.0

+ |=================

+ 

+ Newer versions may be available in the corresponding `updates-testing`

+ repositories.

+ 

+ [[testing-versions]]

+ == Testing Versions

+ 

+ [cols=",",]

+ |=================

+ |Fedora 28 |3.5

+ |Fedora 27 |3.5

+ |Fedora 26 |3.5

+ |=================

+ 

+ [[bugs-and-problems]]

+ == Bugs and problems

+ 

+ Before reporting bugs against Wine please make sure your system is fully

+ up to date.

+ 

+ ....

+ dnf update

+ ....

+ 

+ Also check if a newer version is available in updates-testing.

+ 

+ ....

+ dnf --enablerepo=updates-testing update wine

+ ....

+ 

+ If you are using the proprietary graphics drivers please remove them

+ from your system and try again, as they are known to cause problems.

+ 

+ When debugging Wine, your goal is to determine if the issue is one of

+ _code functionality_ or _packaging in Fedora_.

+ 

+ Check the http://appdb.winehq.org[Wine Application Database] to see if

+ your application is supported, or if there are known issues that match

+ yours. Anything that falls into this category is a bug in upstream code

+ functionality.

+ 

+ The next step is to see if the problem persists with a clean ~/.wine

+ folder. To try this without losing your old configuration:

+ 

+ ....

+ mv ~/.wine ~/.wine-save

+ ....

+ 

+ Afterwards try to trigger the bug again. Your original wine folder can

+ be restored with:

+ 

+ ....

+ rm -fr ~/.wine; mv ~/.wine-save ~/.wine

+ ....

+ 

+ If your application still does not work but has been working in a

+ previous version of wine it is probably a regression. Consider filling a

+ bug in the upstream https://bugs.wine-staging.com/[Wine-staging bug

+ tracking system].

+ 

+ IMPORTANT: Do not file bugs in the Winehq.org bugzilla unless told to do so.

+ 

+ 

+ If you really think that your bug is Fedora-related, file a bug against

+ the Wine component in https://bugzilla.redhat.com[Fedora's bug tracking

+ system].

+ 

+ [[updates-testing]]

+ == Updates-Testing

+ 

+ If you use the version of wine in the updates-testing repository then

+ please log into https://bodhi.fedoraproject.org/updates/?packages=wine[bodhi] and

+ comment on the build, including any problems that may be in the

+ packaging, naming, or elsewhere. The build needs positive karma to be

+ pushed to the updates repository.

+ 

+ See a typo, something missing or out of date, or anything else which can be

+ improved? Edit this document at https://pagure.io/fedora-docs/quick-docs[Pagure].

file added
+18
@@ -0,0 +1,18 @@ 

+ #!/bin/sh

+ 

+ if [ "$(uname)" == "Darwin" ]; then

+     # Running on macOS.

+     # Let's assume that the user has the Docker CE installed

+     # which doesn't require a root password.

+     echo "The preview will be available at http://localhost:8080/"

+     docker run --rm -v $(pwd)/public:/usr/share/nginx/html:ro -p 8080:80 nginx

+ 

+ elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then

+     # Running on Linux.

+     # Let's assume that it's running the Docker deamon

+     # which requires root.

+     echo ""

+     echo "This build script is using Docker to run the build in an isolated environment. You might be asked for a root password in order to start it."

+     echo "The preview will be available at http://localhost:8080/"

+     sudo docker run --rm -v $(pwd)/public:/usr/share/nginx/html:ro -p 8080:80 nginx

+ fi

file added
+20
@@ -0,0 +1,20 @@ 

+ site: 

+   title: Local Preview

+   start_page: quick-docs::index

+ content:

+   sources:

+    - url: .

+      branches: HEAD

+ ui:

+   bundle:

+     url: https://asamalik.fedorapeople.org/ui-bundle.zip

+     snapshot: true

+   default_layout: with_menu

+ output: 

+   clean: true 

+   dir: ./public

+   destinations: 

+   - provider: archive 

+ runtime:

+   pull: true

+   cache_dir: ./cache

If you're doing this workaround you need to also set a new context for the module, otherwise there's no point since :parent-context: = :context: anyway...

The includes below look like a procedure that, for some inexplicable reason, has been split into a separate module for each step. That's not how modularity works.

Use leveloffsets on includes, not inside each file

"there should entry must be present" - I don't think that's quite right

so are we changing the mode or owner/group as described a few lines earlier?

1 new commit added

  • Fixing the content using comments in PR67
5 years ago

rebased onto b22f273

5 years ago

4 new commits added

  • Add the sudoers topic
  • Update the Raspberry Pi topic (tkelly)
  • Hiding the broken Fedora Release Life Cycle topic
  • Add 3 topics to nav.adoc, fix errors
5 years ago

Hi,

  • In commit 1399006 you added adding_user_to_sudoers_file.adoc to nav.adoc but the file doesn't seem to exist in the repo, did you forget to commit it?

Everything else looks good, including the fixes based on earlier comments.

1 new commit added

  • add adding_user_to_sudoers_file.adoc
5 years ago

Pull-Request has been merged by pbokoc

5 years ago
Metadata
Changes Summary 396
+3 -10
file changed
.gitignore
+31 -10
file changed
README.md
-11
file removed
_distro_map.yml
-0
file removed
_images/favicon.ico
-0
file removed
_images/favicon32x32.png
-61
file removed
_images/fedora.svg
-0
file removed
_images/redhat-logo.png
-0
file removed
_javascripts/.gitkeep
-6
file removed
_javascripts/bootstrap-offcanvas.js
-575
file removed
_stylesheets/asciibinder.css
-3
file removed
_templates/_css.html.erb
-31
file removed
_templates/_nav.html.erb
-184
file removed
_templates/page.html.erb
-157
file removed
_topic_map.yml
+16
file added
antora.yml
+16
file added
build.sh
-19
file removed
en-US/changing-selinux-states-and-modes.adoc
-16
file removed
en-US/configuring-ip-networking-with-nmcli.adoc
-6
file removed
en-US/configuring-x-window-system-using-the-xorg-conf-file.adoc
-13
file removed
en-US/creating-a-disk-partition-in-linux.adoc
-11
file removed
en-US/creating-and-using-a-live-installation-image.adoc
-53
file removed
en-US/creating-encrypted-block-devices.adoc
-12
file removed
en-US/creating-rpm-packages.adoc
-1
file removed
en-US/disabling-automatic-screenlock.adoc
-3
file removed
en-US/displaying_user_prompt_on_gnome_login_screen.adoc
-10
file removed
en-US/encrypting-drives-using-LUKS.adoc
-29
file removed
en-US/firewalld.adoc
-18
file removed
en-US/getting-started-with-selinux.adoc
-14
file removed
en-US/getting-started-with-virtualization.adoc
-11
file removed
en-US/installing-chromium-or-google-chrome-browsers.adoc
-7
file removed
en-US/installing-spotify.adoc
-24
file removed
en-US/modules/con_introduction-to-luks.adoc
-9
file removed
en-US/modules/proc_add-entry-to-etc-fstab.adoc
-25
file removed
en-US/modules/proc_add-mapping-information-to-etc-fstab.adoc
-18
file removed
en-US/modules/proc_create-filesystems-on-mapped-device.adoc
-45
file removed
en-US/modules/proc_create-mapping-to-allow-access-to-decrypted-contents.adoc
-50
file removed
en-US/modules/proc_format-device-as-dmcrypt-encrypted-device.adoc
-30
file removed
en-US/modules/proc_package-enabling-third-party.adoc
-73
file removed
en-US/modules/proc_restoring-bootloader-using-live-disk.adoc
-45
file removed
en-US/modules/proc_revoking-gpg-keys.adoc
-38
file removed
en-US/modules/proc_rpm_preparing_your_system.adoc
-68
file removed
en-US/modules/proc_setting-automatic-updates.adoc
-56
file removed
en-US/modules/proc_setting-default-entry-for-grub2.adoc
-33
file removed
en-US/modules/proc_setting-password-for-interactive-edit-mode.adoc
-64
file removed
en-US/modules/proc_starting-stopping-and-querying-systemd-services.adoc
-22
file removed
en-US/modules/proc_starting_firewalld.adoc
-29
file removed
en-US/modules/proc_stopping_firewalld.adoc
-40
file removed
en-US/modules/proc_switching-desktop-enviroments-using-cli.adoc
-32
file removed
en-US/modules/proc_switching-desktop-enviroments-using-gui.adoc
-20
file removed
en-US/modules/proc_testing-nested-virtualization.adoc
-60
file removed
en-US/modules/proc_troubleshooting-live-usb.adoc
-69
file removed
en-US/modules/proc_using-grub2-prompt.adoc
-18
file removed
en-US/modules/proc_using-old-graphics-modes.adoc
-25
file removed
en-US/modules/proc_using-same-password-for-root-as-user.adoc
-214
file removed
en-US/modules/ref_Configuring-networking-with-nmcli.adoc
-31
file removed
en-US/modules/ref_changing-selinux-modes-at-boot-time.adoc
-118
file removed
en-US/modules/ref_common-service-parameters.adoc
-37
file removed
en-US/modules/ref_help-mkpart.adoc
-58
file removed
en-US/modules/ref_jdk-tools.adoc
-103
file removed
en-US/modules/ref_managing-virtual-machines.adoc
-31
file removed
en-US/modules/ref_mapping-runlevel-to-targets.adoc
-42
file removed
en-US/modules/ref_mapping-service-commands.adoc
-37
file removed
en-US/modules/ref_other-virtualization-options.adoc
-45
file removed
en-US/modules/ref_virtio-win-rpm-contents.adoc
-125
file removed
en-US/openh264.adoc
-152
file removed
en-US/package-management.adoc
-143
file removed
en-US/packagekit-not-found.adoc
-32
file removed
en-US/performing-administration-tasks-using-sudo.adoc
-29
file removed
en-US/proc_installing-RPM.adoc
-23
file removed
en-US/proc_setting-key-shortcut.adoc
-96
file removed
en-US/qemu.adoc
-334
file removed
en-US/raspberry-pi.adoc
-200
file removed
en-US/reset-root-password.adoc
-24
file removed
en-US/securing-the-system-by-keeping-it-up-to-date.adoc
-12
file removed
en-US/switching-desktop-environments.adoc
-65
file removed
en-US/troubleshooting_selinux.adoc
-183
file removed
en-US/uefi-with-qemu.adoc
-33
file removed
en-US/understanding-and-administering-systemd.adoc
-84
file removed
en-US/upgrading.adoc
-12
file removed
en-US/using-adobe-flash.adoc
-97
file removed
en-US/using-aide.adoc
-16
file removed
en-US/using-nested-virtualization-in-kvm.adoc
-19
file removed
en-US/using-shared-system-certificates.adoc
-8
file removed
en-US/viewing-logs.adoc
-185
file removed
en-US/wine.adoc
-138
file removed
index-main.html
+0
file added
modules/ROOT/assets/images/20180825-how-to-file-a-bug-cc-list.png
+0
file added
modules/ROOT/assets/images/20180825-how-to-file-a-bug-gs-bugs.png
+0
file added
modules/ROOT/assets/images/20180825-how-to-file-a-bug-gs.png
+0
file added
modules/ROOT/assets/images/20180825-how-to-file-a-bug-new-bug-shortcut.png
+0
file added
modules/ROOT/assets/images/20180825-how-to-file-a-bug-new-bug.png
+0
file added
modules/ROOT/assets/images/20180825-how-to-file-a-bug-qa.png
+0 -0
file renamed
en-US/images/Bios_USB_boot.jpg
modules/ROOT/assets/images/Bios_USB_boot.jpg
+0 -0
file renamed
en-US/images/Boxes_new_machine.png
modules/ROOT/assets/images/Boxes_new_machine.png
+0 -0
file renamed
en-US/images/Customize_resources.png
modules/ROOT/assets/images/Customize_resources.png
+0 -0
file renamed
en-US/anaconda/images/DSC_3217.JPG
modules/ROOT/assets/images/DSC_3217.JPG
+0 -0
file renamed
en-US/images/Download_os.png
modules/ROOT/assets/images/Download_os.png
+0 -0
file renamed
en-US/images/Fedora_Live_USB_creator.png
modules/ROOT/assets/images/Fedora_Live_USB_creator.png
+0 -0
file renamed
en-US/images/FireWwall_GUI_startup.PNG
modules/ROOT/assets/images/FireWwall_GUI_startup.PNG
+0 -0
file renamed
en-US/images/Firewall-tui.PNG
modules/ROOT/assets/images/Firewall-tui.PNG
+0 -0
file renamed
en-US/images/Firewall_GUI_First_Time_Startup.PNG
modules/ROOT/assets/images/Firewall_GUI_First_Time_Startup.PNG
+0 -0
file renamed
en-US/images/Firewall_GUI_other_ports.PNG
modules/ROOT/assets/images/Firewall_GUI_other_ports.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_Custom_Rules.PNG
modules/ROOT/assets/images/Firewall_TUI_Custom_Rules.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_Custom_Rules_Adding.PNG
modules/ROOT/assets/images/Firewall_TUI_Custom_Rules_Adding.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_ICMP_Filter.PNG
modules/ROOT/assets/images/Firewall_TUI_ICMP_Filter.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_Port_Forwarding.PNG
modules/ROOT/assets/images/Firewall_TUI_Port_Forwarding.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_Port_Forwarding_Adding.PNG
modules/ROOT/assets/images/Firewall_TUI_Port_Forwarding_Adding.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_Trusted_services.PNG
modules/ROOT/assets/images/Firewall_TUI_Trusted_services.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_Warning.PNG
modules/ROOT/assets/images/Firewall_TUI_Warning.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_masquerading.PNG
modules/ROOT/assets/images/Firewall_TUI_masquerading.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_other_ports.PNG
modules/ROOT/assets/images/Firewall_TUI_other_ports.PNG
+0 -0
file renamed
en-US/images/Firewall_TUI_trusted_interfaces.PNG
modules/ROOT/assets/images/Firewall_TUI_trusted_interfaces.PNG
+0 -0
file renamed
en-US/images/Firewall_Wizard.PNG
modules/ROOT/assets/images/Firewall_Wizard.PNG
+0 -0
file renamed
en-US/images/Firewall_Wizard_2.PNG
modules/ROOT/assets/images/Firewall_Wizard_2.PNG
+0 -0
file renamed
en-US/images/Firewall_Wizard_3.PNG
modules/ROOT/assets/images/Firewall_Wizard_3.PNG
+0 -0
file renamed
en-US/images/Firewall_Wizard_4.PNG
modules/ROOT/assets/images/Firewall_Wizard_4.PNG
+0 -0
file renamed
en-US/images/Firewall_Wizard_5.PNG
modules/ROOT/assets/images/Firewall_Wizard_5.PNG
+0 -0
file renamed
en-US/images/First_menu_firewall_tui.PNG
modules/ROOT/assets/images/First_menu_firewall_tui.PNG
+0 -0
file renamed
en-US/images/Installation_review.png
modules/ROOT/assets/images/Installation_review.png
+0 -0
file renamed
en-US/images/No_configuration.PNG
modules/ROOT/assets/images/No_configuration.PNG
+0 -0
file renamed
en-US/images/Properties_USB_size.png
modules/ROOT/assets/images/Properties_USB_size.png
+0 -0
file renamed
en-US/images/Select_from_boxes_menu.png
modules/ROOT/assets/images/Select_from_boxes_menu.png
+0 -0
file renamed
en-US/images/Select_from_file.png
modules/ROOT/assets/images/Select_from_file.png
+0 -0
file renamed
en-US/images/Select_virtual_machine.png
modules/ROOT/assets/images/Select_virtual_machine.png
+0 -0
file renamed
en-US/images/Setup_machine.png
modules/ROOT/assets/images/Setup_machine.png
+0 -0
file renamed
en-US/images/Unetbootin_gtk3.png
modules/ROOT/assets/images/Unetbootin_gtk3.png
+0 -0
file renamed
en-US/images/Upgradef24f25-gs.png
modules/ROOT/assets/images/Upgradef24f25-gs.png
+0 -0
file renamed
en-US/images/custom_shortcut.png
modules/ROOT/assets/images/custom_shortcut.png
+0 -0
file renamed
en-US/images/gdm-pick-wayland.png
modules/ROOT/assets/images/gdm-pick-wayland.png
+0 -0
file renamed
en-US/images/mediawriter-icon.png
modules/ROOT/assets/images/mediawriter-icon.png
+0 -0
file renamed
en-US/images/packages_icon_search.png
modules/ROOT/assets/images/packages_icon_search.png
+0 -0
file renamed
en-US/images/packages_icon_software.png
modules/ROOT/assets/images/packages_icon_software.png
+0 -0
file renamed
en-US/images/qemu_gtk3.png
modules/ROOT/assets/images/qemu_gtk3.png
+0
file added
modules/ROOT/assets/images/selinux-intro-apache-mariadb.png
+0 -0
file renamed
en-US/images/shortcuts-add-empty.png
modules/ROOT/assets/images/shortcuts-add-empty.png
+0 -0
file renamed
en-US/images/shortcuts-add-enter.png
modules/ROOT/assets/images/shortcuts-add-enter.png
+0 -0
file renamed
en-US/images/shortcuts-add-filled.png
modules/ROOT/assets/images/shortcuts-add-filled.png
+0 -0
file renamed
en-US/images/shortcuts-add-shortcut.png
modules/ROOT/assets/images/shortcuts-add-shortcut.png
+0 -0
file renamed
en-US/images/shortcuts-added.png
modules/ROOT/assets/images/shortcuts-added.png
+0 -0
file renamed
en-US/images/shortcuts-disabled.png
modules/ROOT/assets/images/shortcuts-disabled.png
+0 -0
file renamed
en-US/images/shortcuts-edit.png
modules/ROOT/assets/images/shortcuts-edit.png
+0 -0
file renamed
en-US/images/shortcuts-enabling-entered.png
modules/ROOT/assets/images/shortcuts-enabling-entered.png
+0 -0
file renamed
en-US/images/shortcuts-enabling-entering.png
modules/ROOT/assets/images/shortcuts-enabling-entering.png
+0 -0
file renamed
en-US/images/shortcuts-keyboard-scroll.png
modules/ROOT/assets/images/shortcuts-keyboard-scroll.png
+0 -0
file renamed
en-US/images/shortcuts-list-disabled.png
modules/ROOT/assets/images/shortcuts-list-disabled.png
+0 -0
file renamed
en-US/images/shortcuts-settings-devices.png
modules/ROOT/assets/images/shortcuts-settings-devices.png
+0 -0
file renamed
en-US/images/software-updates.png
modules/ROOT/assets/images/software-updates.png
+0 -0
file renamed
en-US/images/switching-desktop-environments-login.png
modules/ROOT/assets/images/switching-desktop-environments-login.png
+0 -0
file renamed
en-US/images/switching-desktop-environments-switchdesk.png
modules/ROOT/assets/images/switching-desktop-environments-switchdesk.png
+0 -0
file renamed
en-US/images/system-config-kickstart.png
modules/ROOT/assets/images/system-config-kickstart.png
+75
file added
modules/ROOT/nav.adoc
+1 -1
file renamed
en-US/3rdparty-message.adoc
modules/ROOT/pages/_partials/3rdparty-message.adoc
+0 -0
file renamed
en-US/modules/TODO_virtio-win.adoc
modules/ROOT/pages/_partials/TODO_virtio-win.adoc
+0 -0
file renamed
en-US/attributes.adoc
modules/ROOT/pages/_partials/attributes.adoc
+0 -0
file renamed
en-US/modules/con_Getting-started-with-nmcli.adoc
modules/ROOT/pages/_partials/con_Getting-started-with-nmcli.adoc
+0 -0
file renamed
en-US/modules/con_Understanding-the-nmcli-options.adoc
modules/ROOT/pages/_partials/con_Understanding-the-nmcli-options.adoc
+0 -0
file renamed
en-US/modules/con_about-java.adoc
modules/ROOT/pages/_partials/con_about-java.adoc
+0 -0
file renamed
en-US/modules/con_benefits-of-selinux.adoc
modules/ROOT/pages/_partials/con_benefits-of-selinux.adoc
+1 -2
file renamed
en-US/modules/con_block-device-encryption.adoc
modules/ROOT/pages/_partials/con_block-device-encryption.adoc
+0 -0
file renamed
en-US/modules/con_controlling_ports_firewalld.adoc
modules/ROOT/pages/_partials/con_controlling_ports_firewalld.adoc
+0 -0
file renamed
en-US/modules/con_disk-partition-linux.adoc
modules/ROOT/pages/_partials/con_disk-partition-linux.adoc
+0 -0
file renamed
en-US/modules/con_firewalld.adoc
modules/ROOT/pages/_partials/con_firewalld.adoc
+24
file added
modules/ROOT/pages/_partials/con_introduction-to-luks.adoc
+1 -1
file renamed
en-US/modules/con_introduction-to-selinux.adoc
modules/ROOT/pages/_partials/con_introduction-to-selinux.adoc
+0 -0
file renamed
en-US/modules/con_logging-sudo-commands.adoc
modules/ROOT/pages/_partials/con_logging-sudo-commands.adoc
+0 -0
file renamed
en-US/modules/con_package-management-in-fedora.adoc
modules/ROOT/pages/_partials/con_package-management-in-fedora.adoc
+0 -0
file renamed
en-US/modules/con_permanent-changes-in-selinux-states-and-modes.adoc
modules/ROOT/pages/_partials/con_permanent-changes-in-selinux-states-and-modes.adoc
+0 -0
file renamed
en-US/modules/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc
modules/ROOT/pages/_partials/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc
+0 -0
file renamed
en-US/modules/con_rpm_packaging_overview.adoc
modules/ROOT/pages/_partials/con_rpm_packaging_overview.adoc
+6 -6
file renamed
en-US/modules/con_rpm_spec_file_overview.adoc
modules/ROOT/pages/_partials/con_rpm_spec_file_overview.adoc
+0 -0
file renamed
en-US/modules/con_runtime_and_permanent_firewalld.adoc
modules/ROOT/pages/_partials/con_runtime_and_permanent_firewalld.adoc
+0 -0
file renamed
en-US/modules/con_selinux-architecture.adoc
modules/ROOT/pages/_partials/con_selinux-architecture.adoc
+0 -0
file renamed
en-US/modules/con_selinux-examples.adoc
modules/ROOT/pages/_partials/con_selinux-examples.adoc
+0 -0
file renamed
en-US/modules/con_selinux-states-and-modes.adoc
modules/ROOT/pages/_partials/con_selinux-states-and-modes.adoc
+0 -0
file renamed
en-US/modules/con_sudo-timeout.adoc
modules/ROOT/pages/_partials/con_sudo-timeout.adoc
+0 -0
file renamed
en-US/modules/con_the-purpose-of-rpm-fusion.adoc
modules/ROOT/pages/_partials/con_the-purpose-of-rpm-fusion.adoc
+0 -0
file renamed
en-US/modules/con_understanding-systemd.adoc
modules/ROOT/pages/_partials/con_understanding-systemd.adoc
+0 -0
file renamed
en-US/modules/con_using-sudo-access-docker.adoc
modules/ROOT/pages/_partials/con_using-sudo-access-docker.adoc
+0 -0
file renamed
en-US/modules/con_using-sudo-assign-admin-privileges.adoc
modules/ROOT/pages/_partials/con_using-sudo-assign-admin-privileges.adoc
+0 -0
file renamed
en-US/modules/con_using-sudo-without-password.adoc
modules/ROOT/pages/_partials/con_using-sudo-without-password.adoc
+0 -0
file renamed
en-US/modules/con_using-the-system-wide-trust-store.adoc
modules/ROOT/pages/_partials/con_using-the-system-wide-trust-store.adoc
+0 -0
file renamed
en-US/modules/con_viewing-logs.adoc
modules/ROOT/pages/_partials/con_viewing-logs.adoc
+0 -0
file renamed
en-US/modules/con_what-is-sudo.adoc
modules/ROOT/pages/_partials/con_what-is-sudo.adoc
+0 -0
file renamed
en-US/modules/con_what_is_adobe_flash.adoc
modules/ROOT/pages/_partials/con_what_is_adobe_flash.adoc
+0 -0
file renamed
en-US/modules/con_why-it-is-important-keeping-your-system-up-to-date.adoc
modules/ROOT/pages/_partials/con_why-it-is-important-keeping-your-system-up-to-date.adoc
+0 -0
file renamed
en-US/modules/con_xorg-conf.adoc
modules/ROOT/pages/_partials/con_xorg-conf.adoc
+0 -0
file renamed
en-US/modules/concept_chromium-web-browser.adoc
modules/ROOT/pages/_partials/concept_chromium-web-browser.adoc
+0 -0
file renamed
en-US/modules/concept_fedora-virtio-drivers-vs-rhel.adoc
modules/ROOT/pages/_partials/concept_fedora-virtio-drivers-vs-rhel.adoc
+0 -0
file renamed
en-US/modules/concept_third-party-repositories.adoc
modules/ROOT/pages/_partials/concept_third-party-repositories.adoc
+0 -0
file renamed
en-US/modules/concept_virtio-win-repo-overview.adoc
modules/ROOT/pages/_partials/concept_virtio-win-repo-overview.adoc
+179
file added
modules/ROOT/pages/_partials/creating-encrypted-block-devices.adoc
+0 -0
file renamed
en-US/modules/proc_Brief-selection-of-nmcli-examples.adoc
modules/ROOT/pages/_partials/proc_Brief-selection-of-nmcli-examples.adoc
+0 -0
file renamed
en-US/modules/proc_adding-new-certificates.adoc
modules/ROOT/pages/_partials/proc_adding-new-certificates.adoc
+0 -0
file renamed
en-US/modules/proc_adding-new-fonts-as-superuser.adoc
modules/ROOT/pages/_partials/proc_adding-new-fonts-as-superuser.adoc
+0 -0
file renamed
en-US/modules/proc_adding-new-fonts-as-user.adoc
modules/ROOT/pages/_partials/proc_adding-new-fonts-as-user.adoc
+0 -0
file renamed
en-US/modules/proc_adding-other-operating-systems-grub2.adoc
modules/ROOT/pages/_partials/proc_adding-other-operating-systems-grub2.adoc
+0 -0
file renamed
en-US/modules/proc_adding-repositories.adoc
modules/ROOT/pages/_partials/proc_adding-repositories.adoc
+0 -0
file renamed
en-US/modules/proc_adding-shortcut-custom-app-gnome.adoc
modules/ROOT/pages/_partials/proc_adding-shortcut-custom-app-gnome.adoc
+0 -0
file renamed
en-US/modules/proc_backup-gpg-keys-cli.adoc
modules/ROOT/pages/_partials/proc_backup-gpg-keys-cli.adoc
+0 -0
file renamed
en-US/modules/proc_backup-gpg-keys-gnome.adoc
modules/ROOT/pages/_partials/proc_backup-gpg-keys-gnome.adoc
+0 -0
file renamed
en-US/modules/proc_backup-gpg-keys-kde.adoc
modules/ROOT/pages/_partials/proc_backup-gpg-keys-kde.adoc
+66
file added
modules/ROOT/pages/_partials/proc_booting-fedora-on-a-raspberry-pi-for-the-first-time.adoc
+0 -0
file renamed
en-US/modules/proc_booting-from-usb-sticks.adoc
modules/ROOT/pages/_partials/proc_booting-from-usb-sticks.adoc
+0 -0
file renamed
en-US/modules/proc_booting-with-configfile-on-different-partition.adoc
modules/ROOT/pages/_partials/proc_booting-with-configfile-on-different-partition.adoc
+0 -0
file renamed
en-US/modules/proc_changing-to-enforcing-mode.adoc
modules/ROOT/pages/_partials/proc_changing-to-enforcing-mode.adoc
+0 -0
file renamed
en-US/modules/proc_changing-to-permissive-mode.adoc
modules/ROOT/pages/_partials/proc_changing-to-permissive-mode.adoc
+0 -0
file renamed
en-US/modules/proc_changing_runtime_firewalld.adoc
modules/ROOT/pages/_partials/proc_changing_runtime_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_checking_fedora_version.adoc
modules/ROOT/pages/_partials/proc_checking_fedora_version.adoc
+0 -0
file renamed
en-US/modules/proc_checking_firewalld.adoc
modules/ROOT/pages/_partials/proc_checking_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_closing_ports_firewalld.adoc
modules/ROOT/pages/_partials/proc_closing_ports_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_compiling_your_application_from_source.adoc
modules/ROOT/pages/_partials/proc_compiling_your_application_from_source.adoc
+0 -0
file renamed
en-US/modules/proc_configuring-apache-httpd.adoc
modules/ROOT/pages/_partials/proc_configuring-apache-httpd.adoc
+0 -0
file renamed
en-US/modules/proc_configuring-nested-virtualization-in-virt-manager.adoc
modules/ROOT/pages/_partials/proc_configuring-nested-virtualization-in-virt-manager.adoc
+0 -0
file renamed
en-US/modules/proc_configuring-xorg-as-default-gnome-session.adoc
modules/ROOT/pages/_partials/proc_configuring-xorg-as-default-gnome-session.adoc
+0 -0
file renamed
en-US/modules/proc_configuring_firewalld.adoc
modules/ROOT/pages/_partials/proc_configuring_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_converting-sysvinit-services.adoc
modules/ROOT/pages/_partials/proc_converting-sysvinit-services.adoc
+0 -0
file renamed
en-US/modules/proc_copying-public-gpg-keys-manually.adoc
modules/ROOT/pages/_partials/proc_copying-public-gpg-keys-manually.adoc
+0 -0
file renamed
en-US/modules/proc_creating-a-disk-partition-in-linux.adoc
modules/ROOT/pages/_partials/proc_creating-a-disk-partition-in-linux.adoc
+0 -0
file renamed
en-US/modules/proc_creating-and-using-live-cd.adoc
modules/ROOT/pages/_partials/proc_creating-and-using-live-cd.adoc
+0 -0
file renamed
en-US/modules/proc_creating-and-using-live-usb.adoc
modules/ROOT/pages/_partials/proc_creating-and-using-live-usb.adoc
+0 -0
file renamed
en-US/modules/proc_creating-gpg-keys-cli.adoc
modules/ROOT/pages/_partials/proc_creating-gpg-keys-cli.adoc
+0 -0
file renamed
en-US/modules/proc_creating-gpg-keys-gnome.adoc
modules/ROOT/pages/_partials/proc_creating-gpg-keys-gnome.adoc
+0 -0
file renamed
en-US/modules/proc_creating-gpg-keys-kde.adoc
modules/ROOT/pages/_partials/proc_creating-gpg-keys-kde.adoc
+0 -0
file renamed
en-US/modules/proc_creating-new-systemd-services.adoc
modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc
+2 -2
file renamed
en-US/modules/proc_creating-virtual-machines.adoc
modules/ROOT/pages/_partials/proc_creating-virtual-machines.adoc
+0 -0
file renamed
en-US/modules/proc_creating_xorg_conf.adoc
modules/ROOT/pages/_partials/proc_creating_xorg_conf.adoc
+0 -0
file renamed
en-US/modules/proc_disabling-gnome-screenlock.adoc
modules/ROOT/pages/_partials/proc_disabling-gnome-screenlock.adoc
+0 -0
file renamed
en-US/modules/proc_disabling-repositories.adoc
modules/ROOT/pages/_partials/proc_disabling-repositories.adoc
+0 -0
file renamed
en-US/modules/proc_disabling-selinux.adoc
modules/ROOT/pages/_partials/proc_disabling-selinux.adoc
+0 -0
file renamed
en-US/modules/proc_disabling-shortcut-custom-app-gnome.adoc
modules/ROOT/pages/_partials/proc_disabling-shortcut-custom-app-gnome.adoc
+0 -0
file renamed
en-US/modules/proc_displaying_user_prompt_on_gnome_login_screen.adoc
modules/ROOT/pages/_partials/proc_displaying_user_prompt_on_gnome_login_screen.adoc
+0 -0
file renamed
en-US/modules/proc_downloading-fedora.adoc
modules/ROOT/pages/_partials/proc_downloading-fedora.adoc
+0 -0
file renamed
en-US/modules/proc_downloading-source-code.adoc
modules/ROOT/pages/_partials/proc_downloading-source-code.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-chromium-plugins.adoc
modules/ROOT/pages/_partials/proc_enabling-chromium-plugins.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-hardware-virtualization-support.adoc
modules/ROOT/pages/_partials/proc_enabling-hardware-virtualization-support.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-latest-virtio-win-repo.adoc
modules/ROOT/pages/_partials/proc_enabling-latest-virtio-win-repo.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-nested-virtualization-in-kvm.adoc
modules/ROOT/pages/_partials/proc_enabling-nested-virtualization-in-kvm.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-repositories.adoc
modules/ROOT/pages/_partials/proc_enabling-repositories.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-selinux.adoc
modules/ROOT/pages/_partials/proc_enabling-selinux.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-serial-console-grub.adoc
modules/ROOT/pages/_partials/proc_enabling-serial-console-grub.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-shortcut-custom-app-gnome.adoc
modules/ROOT/pages/_partials/proc_enabling-shortcut-custom-app-gnome.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-the-rpmfusion-repositories-using-command-line-utilities.adoc
modules/ROOT/pages/_partials/proc_enabling-the-rpmfusion-repositories-using-command-line-utilities.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-the-rpmfusion-repositories-using-graphical-applications.adoc
modules/ROOT/pages/_partials/proc_enabling-the-rpmfusion-repositories-using-graphical-applications.adoc
+0 -0
file renamed
en-US/modules/proc_enabling-third-party-repository.adoc
modules/ROOT/pages/_partials/proc_enabling-third-party-repository.adoc
+0 -0
file renamed
en-US/modules/proc_enabling_firewalld.adoc
modules/ROOT/pages/_partials/proc_enabling_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_exporting-gpg-keys-cli.adoc
modules/ROOT/pages/_partials/proc_exporting-gpg-keys-cli.adoc
+0 -0
file renamed
en-US/modules/proc_exporting-gpg-keys-gnome.adoc
modules/ROOT/pages/_partials/proc_exporting-gpg-keys-gnome.adoc
+0 -0
file renamed
en-US/modules/proc_exporting-gpg-keys-kde.adoc
modules/ROOT/pages/_partials/proc_exporting-gpg-keys-kde.adoc
+0 -0
file renamed
en-US/modules/proc_filing-virtio-win-bugs.adoc
modules/ROOT/pages/_partials/proc_filing-virtio-win-bugs.adoc
+8 -8
file renamed
en-US/modules/proc_install-predefined-systems.adoc
modules/ROOT/pages/_partials/proc_install-predefined-systems.adoc
+0 -0
file renamed
en-US/modules/proc_install_firewalld_gui.adoc
modules/ROOT/pages/_partials/proc_install_firewalld_gui.adoc
+0 -0
file renamed
en-US/modules/proc_installing-additional-desktop-enviroments.adoc
modules/ROOT/pages/_partials/proc_installing-additional-desktop-enviroments.adoc
+0 -0
file renamed
en-US/modules/proc_installing-chromium-web-browser.adoc
modules/ROOT/pages/_partials/proc_installing-chromium-web-browser.adoc
+59
file added
modules/ROOT/pages/_partials/proc_installing-fedora-on-a-raspberry-pi-for-apple-osx-users.adoc
+68
file added
modules/ROOT/pages/_partials/proc_installing-fedora-on-a-raspberry-pi-for-linux-users.adoc
+59
file added
modules/ROOT/pages/_partials/proc_installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users.adoc
+84
file added
modules/ROOT/pages/_partials/proc_installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer.adoc
+0 -0
file renamed
en-US/modules/proc_installing-fonts.adoc
modules/ROOT/pages/_partials/proc_installing-fonts.adoc
+0 -0
file renamed
en-US/modules/proc_installing-grub2-on-bios-system.adoc
modules/ROOT/pages/_partials/proc_installing-grub2-on-bios-system.adoc
+0 -0
file renamed
en-US/modules/proc_installing-grub2-on-efi-system.adoc
modules/ROOT/pages/_partials/proc_installing-grub2-on-efi-system.adoc
+0 -0
file renamed
en-US/modules/proc_installing-httpd.adoc
modules/ROOT/pages/_partials/proc_installing-httpd.adoc
+0 -0
file renamed
en-US/modules/proc_installing-multimedia-plug-ins-with-dnf.adoc
modules/ROOT/pages/_partials/proc_installing-multimedia-plug-ins-with-dnf.adoc
+0 -0
file renamed
en-US/modules/proc_installing-openjdk.adoc
modules/ROOT/pages/_partials/proc_installing-openjdk.adoc
+0 -0
file renamed
en-US/modules/proc_installing-oracle-java.adoc
modules/ROOT/pages/_partials/proc_installing-oracle-java.adoc
+12 -30
file renamed
en-US/modules/proc_installing-spotify-on-fedora.adoc
modules/ROOT/pages/_partials/proc_installing-spotify-on-fedora.adoc
+0 -0
file renamed
en-US/modules/proc_installing-virtio-win-repo.adoc
modules/ROOT/pages/_partials/proc_installing-virtio-win-repo.adoc
+0 -0
file renamed
en-US/modules/proc_installing-virtualization-software.adoc
modules/ROOT/pages/_partials/proc_installing-virtualization-software.adoc
+0 -0
file renamed
en-US/modules/proc_installing-webapps.adoc
modules/ROOT/pages/_partials/proc_installing-webapps.adoc
+0 -0
file renamed
en-US/modules/proc_installing_adobe_flash.adoc
modules/ROOT/pages/_partials/proc_installing_adobe_flash.adoc
+0 -0
file renamed
en-US/modules/proc_installing_firewalld.adoc
modules/ROOT/pages/_partials/proc_installing_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_installing_vlc.adoc
modules/ROOT/pages/_partials/proc_installing_vlc.adoc
+0 -0
file renamed
en-US/modules/proc_log-files-GUI.adoc
modules/ROOT/pages/_partials/proc_log-files-GUI.adoc
+0 -0
file renamed
en-US/modules/proc_log-files-command-line.adoc
modules/ROOT/pages/_partials/proc_log-files-command-line.adoc
+0 -0
file renamed
en-US/modules/proc_managing-trusted-system-certificates.adoc
modules/ROOT/pages/_partials/proc_managing-trusted-system-certificates.adoc
+0 -0
file renamed
en-US/modules/proc_manual-updating-using-cli.adoc
modules/ROOT/pages/_partials/proc_manual-updating-using-cli.adoc
+0 -0
file renamed
en-US/modules/proc_manual-updating-using-gui.adoc
modules/ROOT/pages/_partials/proc_manual-updating-using-gui.adoc
+0 -0
file renamed
en-US/modules/proc_modifying-existing-systemd-services.adoc
modules/ROOT/pages/_partials/proc_modifying-existing-systemd-services.adoc
+0 -0
file renamed
en-US/modules/proc_opening_ports_firewalld.adoc
modules/ROOT/pages/_partials/proc_opening_ports_firewalld.adoc
+0 -0
file renamed
en-US/modules/proc_package-browsing-installing-software.adoc
modules/ROOT/pages/_partials/proc_package-browsing-installing-software.adoc
+30
file added
modules/ROOT/pages/_partials/proc_package-enabling-third-party.adoc
+0 -0
file renamed
en-US/modules/proc_package-install-command-line.adoc
modules/ROOT/pages/_partials/proc_package-install-command-line.adoc
+0 -0
file renamed
en-US/modules/proc_package-searching-web-apps.adoc
modules/ROOT/pages/_partials/proc_package-searching-web-apps.adoc
+0 -0
file renamed
en-US/modules/proc_removing-shortcut-custom-app-gnome.adoc
modules/ROOT/pages/_partials/proc_removing-shortcut-custom-app-gnome.adoc
+73
file added
modules/ROOT/pages/_partials/proc_restoring-bootloader-using-live-disk.adoc
+45
file added
modules/ROOT/pages/_partials/proc_revoking-gpg-keys.adoc
+2 -2
file renamed
en-US/modules/proc_rpm_creating_an_rpm.adoc
modules/ROOT/pages/_partials/proc_rpm_creating_an_rpm.adoc
+38
file added
modules/ROOT/pages/_partials/proc_rpm_preparing_your_system.adoc
+0 -0
file renamed
en-US/modules/proc_run-docker-using-sudo.adoc
modules/ROOT/pages/_partials/proc_run-docker-using-sudo.adoc
+0 -0
file renamed
en-US/modules/proc_running_vlc.adoc
modules/ROOT/pages/_partials/proc_running_vlc.adoc
+0 -0
file renamed
en-US/modules/proc_securing-apache-httpd.adoc
modules/ROOT/pages/_partials/proc_securing-apache-httpd.adoc
+68
file added
modules/ROOT/pages/_partials/proc_setting-automatic-updates.adoc
+56
file added
modules/ROOT/pages/_partials/proc_setting-default-entry-for-grub2.adoc
+33
file added
modules/ROOT/pages/_partials/proc_setting-password-for-interactive-edit-mode.adoc
+0 -0
file renamed
en-US/modules/proc_setting-up-your-local-dev-and-compilation-environment.adoc
modules/ROOT/pages/_partials/proc_setting-up-your-local-dev-and-compilation-environment.adoc
+0 -0
file renamed
en-US/modules/proc_solving-absent-floppy.adoc
modules/ROOT/pages/_partials/proc_solving-absent-floppy.adoc
+64
file added
modules/ROOT/pages/_partials/proc_starting-stopping-and-querying-systemd-services.adoc
+22
file added
modules/ROOT/pages/_partials/proc_starting_firewalld.adoc
+29
file added
modules/ROOT/pages/_partials/proc_stopping_firewalld.adoc
+40
file added
modules/ROOT/pages/_partials/proc_switching-desktop-enviroments-using-cli.adoc
+32
file added
modules/ROOT/pages/_partials/proc_switching-desktop-enviroments-using-gui.adoc
+20
file added
modules/ROOT/pages/_partials/proc_testing-nested-virtualization.adoc
+60
file added
modules/ROOT/pages/_partials/proc_troubleshooting-live-usb.adoc
+69
file added
modules/ROOT/pages/_partials/proc_using-grub2-prompt.adoc
+18
file added
modules/ROOT/pages/_partials/proc_using-old-graphics-modes.adoc
+25
file added
modules/ROOT/pages/_partials/proc_using-same-password-for-root-as-user.adoc
+214
file added
modules/ROOT/pages/_partials/ref_Configuring-networking-with-nmcli.adoc
+31
file added
modules/ROOT/pages/_partials/ref_changing-selinux-modes-at-boot-time.adoc
+118
file added
modules/ROOT/pages/_partials/ref_common-service-parameters.adoc
+224
file added
modules/ROOT/pages/_partials/ref_frequently-asked-questions_-installing-fedora-on-a-raspberry-pi.adoc
+37
file added
modules/ROOT/pages/_partials/ref_help-mkpart.adoc
+58
file added
modules/ROOT/pages/_partials/ref_jdk-tools.adoc
+103
file added
modules/ROOT/pages/_partials/ref_managing-virtual-machines.adoc
+31
file added
modules/ROOT/pages/_partials/ref_mapping-runlevel-to-targets.adoc
+42
file added
modules/ROOT/pages/_partials/ref_mapping-service-commands.adoc
+37
file added
modules/ROOT/pages/_partials/ref_other-virtualization-options.adoc
+0 -0
file renamed
en-US/modules/ref_the-most-useful-dnf-commands.adoc
modules/ROOT/pages/_partials/ref_the-most-useful-dnf-commands.adoc
+45
file added
modules/ROOT/pages/_partials/ref_virtio-win-rpm-contents.adoc
+6 -2
file renamed
en-US/adding-new-fonts-fedora.adoc
modules/ROOT/pages/adding-new-fonts-fedora.adoc
+7 -3
file renamed
en-US/adding-or-removing-software-repositories-in-fedora.adoc
modules/ROOT/pages/adding-or-removing-software-repositories-in-fedora.adoc
+27
file added
modules/ROOT/pages/adding_user_to_sudoers_file.adoc
+0 -0
file renamed
en-US/anaconda/anaconda.adoc
modules/ROOT/pages/anaconda/anaconda.adoc
+0 -0
file renamed
en-US/anaconda/anaconda_distros.adoc
modules/ROOT/pages/anaconda/anaconda_distros.adoc
+0 -0
file renamed
en-US/anaconda/anaconda_logging.adoc
modules/ROOT/pages/anaconda/anaconda_logging.adoc
+0 -0
file renamed
en-US/anaconda/anaconda_product_image.adoc
modules/ROOT/pages/anaconda/anaconda_product_image.adoc
+0 -0
file renamed
en-US/anaconda/anaconda_updates.adoc
modules/ROOT/pages/anaconda/anaconda_updates.adoc
+15 -13
file renamed
en-US/assembly_installing-plugins-for-playing-movies-and-music.adoc
modules/ROOT/pages/assembly_installing-plugins-for-playing-movies-and-music.adoc
+1 -1
file renamed
en-US/autoupdates.adoc
modules/ROOT/pages/autoupdates.adoc
+15 -11
file renamed
en-US/bootloading-with-grub2.adoc
modules/ROOT/pages/bootloading-with-grub2.adoc
+2 -1
file renamed
en-US/bumblebee.adoc
modules/ROOT/pages/bumblebee.adoc
+21
file added
modules/ROOT/pages/changing-selinux-states-and-modes.adoc
+16
file added
modules/ROOT/pages/configuring-ip-networking-with-nmcli.adoc
+10
file added
modules/ROOT/pages/configuring-x-window-system-using-the-xorg-conf-file.adoc
+8 -2
file renamed
en-US/configuring-xorg-as-default-gnome-session.adoc
modules/ROOT/pages/configuring-xorg-as-default-gnome-session.adoc
+22 -17
file renamed
en-US/create-gpg-keys.adoc
modules/ROOT/pages/create-gpg-keys.adoc
+4 -4
file renamed
en-US/create-hello-world-rpm.adoc
modules/ROOT/pages/create-hello-world-rpm.adoc
+12
file added
modules/ROOT/pages/creating-a-disk-partition-in-linux.adoc
+16
file added
modules/ROOT/pages/creating-and-using-a-live-installation-image.adoc
+16
file added
modules/ROOT/pages/creating-rpm-packages.adoc
+10 -6
file renamed
en-US/creating-windows-virtual-machines-using-virtio-drivers.adoc
modules/ROOT/pages/creating-windows-virtual-machines-using-virtio-drivers.adoc
+1 -1
file renamed
en-US/debug-dracut-problems.adoc
modules/ROOT/pages/debug-dracut-problems.adoc
+1 -1
file renamed
en-US/debug-systemd-problems.adoc
modules/ROOT/pages/debug-systemd-problems.adoc
+1 -1
file renamed
en-US/debug-wayland-problems.adoc
modules/ROOT/pages/debug-wayland-problems.adoc
+5
file added
modules/ROOT/pages/disabling-automatic-screenlock.adoc
+7
file added
modules/ROOT/pages/displaying_user_prompt_on_gnome_login_screen.adoc
+0 -0
file renamed
en-US/dnf-system-upgrade.adoc
modules/ROOT/pages/dnf-system-upgrade.adoc
+23 -21
file renamed
en-US/dnf.adoc
modules/ROOT/pages/dnf.adoc
+14 -27
file renamed
en-US/edit-iptables-rules.adoc
modules/ROOT/pages/edit-iptables-rules.adoc
+7 -13
file renamed
en-US/enable-touchpad-click.adoc
modules/ROOT/pages/enable-touchpad-click.adoc
+20
file added
modules/ROOT/pages/encrypting-drives-using-LUKS.adoc
+5 -1
file renamed
en-US/fedora-and-red-hat-enterprise-linux.adoc
modules/ROOT/pages/fedora-and-red-hat-enterprise-linux.adoc
+4 -0
file renamed
en-US/fedora-life-cycle.adoc
modules/ROOT/pages/fedora-life-cycle.adoc
+9 -5
file renamed
en-US/finding-and-installing-linux-applications.adoc
modules/ROOT/pages/finding-and-installing-linux-applications.adoc
+33
file added
modules/ROOT/pages/firewalld.adoc
+8 -4
file renamed
en-US/getting-started-with-apache-http-server.adoc
modules/ROOT/pages/getting-started-with-apache-http-server.adoc
+19
file added
modules/ROOT/pages/getting-started-with-selinux.adoc
+18
file added
modules/ROOT/pages/getting-started-with-virtualization.adoc
+201
file added
modules/ROOT/pages/howto-file-a-bug.adoc
+7 -7
file renamed
en-US/index.adoc
modules/ROOT/pages/index.adoc
+9 -5
file renamed
en-US/installing-and-running-vlc.adoc
modules/ROOT/pages/installing-and-running-vlc.adoc
+15
file added
modules/ROOT/pages/installing-chromium-or-google-chrome-browsers.adoc
+8 -4
file renamed
en-US/installing-grub2.adoc
modules/ROOT/pages/installing-grub2.adoc
+8 -4
file renamed
en-US/installing-java.adoc
modules/ROOT/pages/installing-java.adoc
+8 -4
file renamed
en-US/installing-software-from-source.adoc
modules/ROOT/pages/installing-software-from-source.adoc
+13
file added
modules/ROOT/pages/installing-spotify.adoc
+6 -5
file renamed
en-US/installing-virtual-systems-with-gnome-boxes.adoc
modules/ROOT/pages/installing-virtual-systems-with-gnome-boxes.adoc
+12 -12
file renamed
en-US/kernel/build-custom-kernel.adoc
modules/ROOT/pages/kernel/build-custom-kernel.adoc
+0 -0
file renamed
en-US/kernel/overview.adoc
modules/ROOT/pages/kernel/overview.adoc
+0 -0
file renamed
en-US/kernel/troubleshooting.adoc
modules/ROOT/pages/kernel/troubleshooting.adoc
+8 -4
file renamed
en-US/managing-keyboard-shortcuts-for-running-app-in-gnome.adoc
modules/ROOT/pages/managing-keyboard-shortcuts-for-running-app-in-gnome.adoc
+1 -1
file renamed
en-US/mirroring.adoc
modules/ROOT/pages/mirroring.adoc
+125
file added
modules/ROOT/pages/openh264.adoc
+152
file added
modules/ROOT/pages/package-management.adoc
+137
file added
modules/ROOT/pages/packagekit-not-found.adoc
+36
file added
modules/ROOT/pages/performing-administration-tasks-using-sudo.adoc
+16 -31
file renamed
en-US/postgresql.adoc
modules/ROOT/pages/postgresql.adoc
+25
file added
modules/ROOT/pages/proc_installing-RPM.adoc
+27
file added
modules/ROOT/pages/proc_setting-key-shortcut.adoc
+96
file added
modules/ROOT/pages/qemu.adoc
+74
file added
modules/ROOT/pages/raspberry-pi.adoc
+0 -0
file renamed
en-US/repositories.adoc
modules/ROOT/pages/repositories.adoc
+200
file added
modules/ROOT/pages/reset-root-password.adoc
+28
file added
modules/ROOT/pages/securing-the-system-by-keeping-it-up-to-date.adoc
+16
file added
modules/ROOT/pages/switching-desktop-environments.adoc
+72
file added
modules/ROOT/pages/troubleshooting_selinux.adoc
+183
file added
modules/ROOT/pages/uefi-with-qemu.adoc
+37
file added
modules/ROOT/pages/understanding-and-administering-systemd.adoc
+24 -47
file renamed
en-US/upgrading-fedora-online.adoc
modules/ROOT/pages/upgrading-fedora-online.adoc
+84
file added
modules/ROOT/pages/upgrading.adoc
+15
file added
modules/ROOT/pages/using-adobe-flash.adoc
+97
file added
modules/ROOT/pages/using-aide.adoc
+20
file added
modules/ROOT/pages/using-nested-virtualization-in-kvm.adoc
+23
file added
modules/ROOT/pages/using-shared-system-certificates.adoc
+11
file added
modules/ROOT/pages/viewing-logs.adoc
+180
file added
modules/ROOT/pages/wine.adoc
+18
file added
preview.sh
+20
file added
site.yml