From 1bcf91feccbc0ee37da0aa2b09254e2b772e795b Mon Sep 17 00:00:00 2001 From: Alexander Grothe Date: Sun, 7 Jan 2018 19:00:27 +0100 Subject: [PATCH] Fix case of boolean variable --- Manual.html | 824 +++++++++++++------------- Manual.org | 6 +- install-yavdr.sh | 2 +- roles/collect-facts/defaults/main.yml | 2 +- roles/yavdr-xorg/defaults/main.yml | 2 +- 5 files changed, 418 insertions(+), 418 deletions(-) diff --git a/Manual.html b/Manual.html index 854011d..051b3b2 100644 --- a/Manual.html +++ b/Manual.html @@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - + Ansible Playbooks for yaVDR 0.7 @@ -240,233 +240,233 @@ for the JavaScript code in this tag.

Inhaltsverzeichnis

-
-

1 User Stories

+
+

1 User Stories

-
-

1.1 yavdr-full

+
+

1.1 yavdr-full

A User wants to install yaVDR without customization and relies on full automation. @@ -499,22 +499,22 @@ Several roles are used to tie everything together:

-
-

1.1.1 Using vdr, pulseaudio and xorg together

+
+

1.1.1 Using vdr, pulseaudio and xorg together

-
-

2 Introduction

+
+

2 Introduction

One of the major problems we faced with customized Ubuntu ISO files as installation media for prior yaVDR versions has been the limited hardware support and the time consuming process to create and update them. An interesting alternative to this approach is to enable the user to choose the installation medium himself so point releases, kernel versions and additional drivers can be chosen deliberately. After the basic setup is complete (and a working internet connection is available), a fully customizable install script completes the yaVDR installation.

-
-

3 Installing and configuring yaVDR with Ansible

+
+

3 Installing and configuring yaVDR with Ansible

This is an experimental feature which allows to set up a yaVDR installation based on a normal Ubuntu Server 16.04.x installation using Ansible. @@ -546,8 +546,8 @@ We use a callback to generate tags for all roles autmatically:

-
-

3.1 Install script for local usage

+
+

3.1 Install script for local usage

if (( $EUID != 0 )); then
@@ -564,18 +564,18 @@ apt-get update
 apt-get -y install --no-install-recommends ansible
 
 # TODO: run ansible on local host
-ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=true"
+ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=True"
-
-

4 Playbooks

+
+

4 Playbooks

-
-

4.1 yavdr07.yml

+
+

4.1 yavdr07.yml

The yavdr07.yml playbook sets up a fully-featured yaVDR installation: @@ -624,8 +624,8 @@ The yavdr07.yml playbook sets up a fully-featured yaVDR installatio

-
-

4.2 yavdr07-headless.yml

+
+

4.2 yavdr07-headless.yml

For a headless server installation yavdr07-headless.yml is a good choice @@ -658,8 +658,8 @@ For a headless server installation yavdr07-headless.yml is a good c

-
-

5 Hosts

+
+

5 Hosts

This playbook can either be used to run the installation on the localhost or any other PC in the network that can be accessed via ssh. Simply add the host names or IP addresses to the hosts file in the respective section: @@ -673,12 +673,12 @@ This playbook can either be used to run the installation on the localhost or any

-
-

6 Group Variables

+
+

6 Group Variables

-
-

6.1 default text for templates used by ansible

+
+

6.1 default text for templates used by ansible

---
@@ -690,8 +690,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.2 PPAs

+
+

6.2 PPAs

branch: experimental
@@ -706,8 +706,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.3 VDR user, directories, special configuration and plugins

+
+

6.3 VDR user, directories, special configuration and plugins

# properties of the user vdr and vdr-related options
@@ -733,8 +733,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.4 Media directories

+
+

6.4 Media directories

# dictionary of directories for (shared) files. Automatically exported via NFS and Samba if those roles are enabled
@@ -749,8 +749,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.5 NFS

+
+

6.5 NFS

nfs:
@@ -759,8 +759,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.6 Samba

+
+

6.6 Samba

samba:
@@ -770,8 +770,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.7 Additional packages

+
+

6.7 Additional packages

# additional packages you want to install
@@ -787,8 +787,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.8 System pre-configuration

+
+

6.8 System pre-configuration

frontend: vdr
@@ -803,20 +803,20 @@ This playbook can either be used to run the installation on the localhost or any
-
-

7 Roles

+
+

7 Roles

-
-

7.1 install-dependencies

+
+

7.1 install-dependencies

-
-

7.1.1 tasks

+
+

7.1.1 tasks

    -
  1. main.yml
    +
  2. main.yml
    ---
@@ -836,19 +836,19 @@ This playbook can either be used to run the installation on the localhost or any
    -
    -

    7.2 nvidia-387 drivers

    +
    +

    7.2 nvidia-387 drivers

    install nvidia-387 from ppa:graphics-drivers/ppa

    -
    -

    7.2.1 tasks

    +
    +

    7.2.1 tasks

      -
    1. main.yml
      +
    2. main.yml
      ---
@@ -878,15 +878,15 @@ install nvidia-387 from ppa:graphics-drivers/ppa
    -
    -

    7.3 yavdr-common

    +
    +

    7.3 yavdr-common

    This role is used to set up a basic yaVDR installation. It creates the directories, installs the vdr and other useful packages.

    -
    -

    7.3.1 default variables

    +
    +

    7.3.1 default variables

    This section is for reference only, please use the files in global_vars for customizations. @@ -899,7 +899,7 @@ This section is for reference only, please use the files in global_vars

      -
    1. Repositories
      +
    2. Repositories

      You can set a list of package repositories which provide the necessary packages. Feel free to use own PPAs if you need special customization to the VDR and it’s plugins. @@ -916,7 +916,7 @@ You can set a list of package repositories which provide the necessary packages.

    3. -
  3. Drivers
    +
  4. Drivers

    Automatically installed drivers can be very useful, but if you know you need a certain driver, you can simply set it’s value to true. If you don’t want a driver to be installed, set it’s value to false. @@ -929,7 +929,7 @@ Automatically installed drivers can be very useful, but if you know you need a c

-
  • Additional Packages
    +
  • Additional Packages

    Add additional packages you would like to have on your installation to this list @@ -943,7 +943,7 @@ Add additional packages you would like to have on your installation to this list

    • -
  • VDR
    +
  • VDR

    This section allows you to set the recording directory, the user and group that runs the vdr and it’s home directory. @@ -976,15 +976,15 @@ This section allows you to set the recording directory, the user and group that

    • -
    -

    7.3.2 tasks

    +
    +

    7.3.2 tasks

    yavdr-common executes the following tasks:

      -
    1. main.yml
      +
    2. main.yml
      ---
@@ -1000,7 +1000,7 @@ yavdr-common executes the following tasks:
        -
      1. Disable default installation of recommended packages
        +
      2. Disable default installation of recommended packages

        This task prevents apt to automatically install all recommended dependencies for packages: @@ -1017,7 +1017,7 @@ This task prevents apt to automatically install all recommended dependencies for

    -
  • Set up package repositories
    +
  • Set up package repositories
    - name: add PPAs
@@ -1037,7 +1037,7 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • Use bash instead of dash
    +
  • Use bash instead of dash
    - name: use bash instead of dash
@@ -1049,10 +1049,10 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • create user vdr
    • -
  • Disable release-upgrade notifications
    +
  • create user vdr
    • +
  • Disable release-upgrade notifications
      -
    1. SOMEDAY move from lineinfile to template
      +
    2. SOMEDAY move from lineinfile to template
      - name: disable release-upgrade notifications
@@ -1074,7 +1074,7 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • Install essential packages
    +
  • Install essential packages
    - name: apt | install basic packages
@@ -1106,7 +1106,7 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • Install additional packages (user defined)
    +
  • Install additional packages (user defined)
    - name: apt | install extra packages
@@ -1120,13 +1120,13 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • create directories
    • +
  • create directories
    • -
    -

    7.3.3 templates

    +
    +

    7.3.3 templates

    {{ ansible_managed_file | comment('c') }}
@@ -1138,25 +1138,25 @@ APT::Install-Suggests "0";
    -
    -

    7.4 collect facts about the system with custom modules

    +
    +

    7.4 collect facts about the system with custom modules

    -
    -

    7.4.1 variables

    +
    +

    7.4.1 variables

    -
    first_run: false
+
    first_run: False
    -
    -

    7.4.2 tasks

    +
    +

    7.4.2 tasks

      -
    1. main.yml
      +
    2. main.yml
      - name: get information about usb and pci hardware and loaded kernel modules
@@ -1196,16 +1196,16 @@ APT::Install-Suggests "0";
    -
    -

    7.5 vdr

    +
    +

    7.5 vdr

    -
    -

    7.5.1 tasks

    +
    +

    7.5.1 tasks

      -
    1. install the basic vdr packages
      +
    2. install the basic vdr packages
      ---
@@ -1224,7 +1224,7 @@ APT::Install-Suggests "0";
      3. -
    3. Add svdrp/svdrp-disc to /etc/services
      +
    4. Add svdrp/svdrp-disc to /etc/services
      - name: add svdrp and svdrp-disc to /etc/services
@@ -1239,7 +1239,7 @@ APT::Install-Suggests "0";
      5. -
    5. Set up the recording directory for the vdr user
      +
    6. Set up the recording directory for the vdr user
      - name: create vdr recdir
@@ -1274,7 +1274,7 @@ APT::Install-Suggests "0";
      7. -
    7. Install additional vdr plugins
      +
    8. Install additional vdr plugins

      The additional plugins to install can be set in the variable {{vdr_plugins}} in the group variables @@ -1292,7 +1292,7 @@ The additional plugins to install can be set in the variable {{vdr_plugins

    -
  • copy vdr configuration files (if they don’t exist yet)
    +
  • copy vdr configuration files (if they don’t exist yet)
    - name: ensure vdr is stopped
@@ -1325,15 +1325,15 @@ The additional plugins to install can be set in the variable {{vdr_plugins
    -
    -

    7.5.2 templates

    +
    +

    7.5.2 templates

    -
    -

    7.5.3 files

    +
    +

    7.5.3 files

      -
    1. remote.conf
      +
    2. remote.conf
      LIRC.Up KEY_UP
@@ -1468,7 +1468,7 @@ XKeySym.Next       XF86AudioNext
      3. -
    3. keymacros.conf
      +
    4. keymacros.conf
      # Remote control key macros for VDR
@@ -1494,12 +1494,12 @@ User0     @osdteletext
    -
    -

    7.6 STARTED yavdr-network

    +
    +

    7.6 STARTED yavdr-network

    -
    -

    7.6.1 default variables

    +
    +

    7.6.1 default variables

    install_avahi: true
@@ -1507,8 +1507,8 @@ User0     @osdteletext
    -
    -

    7.6.2 tasks

    +
    +

    7.6.2 tasks

    ---
@@ -1578,15 +1578,15 @@ User0     @osdteletext
    -
    -

    7.7 nfs-server

    +
    +

    7.7 nfs-server

    -
    -

    7.7.1 TODO avahi-services für NFS beim Stoppen des nfs-kernel-servers depublizieren, beim Start wieder announcen

    +
    +

    7.7.1 TODO avahi-services für NFS beim Stoppen des nfs-kernel-servers depublizieren, beim Start wieder announcen

    -
    -

    7.7.2 tasks

    +
    +

    7.7.2 tasks

    ---
@@ -1615,12 +1615,12 @@ User0     @osdteletext
    -
    -

    7.7.3 templates

    +
    +

    7.7.3 templates

      -
    1. /etc/exports
      +
    2. /etc/exports
      /srv *(rw,fsid=0,sync,no_subtree_check,all_squash,anongid={{ vdr.gid }},anonuid={{ vdr.uid }})
@@ -1631,7 +1631,7 @@ User0     @osdteletext
      3. -
    3. avahi services
      +
    4. avahi services
      <?xml version="1.0" standalone='no'?>
@@ -1652,12 +1652,12 @@ User0     @osdteletext
    -
    -

    7.8 STARTED yavdr-remote

    +
    +

    7.8 STARTED yavdr-remote

    -
    -

    7.8.1 default variables

    +
    +

    7.8.1 default variables

    lircd0_socket: /var/run/lirc/lircd0
@@ -1665,8 +1665,8 @@ User0     @osdteletext
    -
    -

    7.8.2 tasks

    +
    +

    7.8.2 tasks

    ---
@@ -1730,12 +1730,12 @@ User0     @osdteletext
    -
    -

    7.8.3 templates

    +
    +

    7.8.3 templates

      -
    1. Systemd Drop-in to start vdr with lirc support
      +
    2. Systemd Drop-in to start vdr with lirc support
      {% if frontend != 'kodi' %}
@@ -1746,7 +1746,7 @@ User0     @osdteletext
      3. -
    3. Systemd Drop-in to start lircd2uinput with lircd
      +
    4. Systemd Drop-in to start lircd2uinput with lircd
      [Service]
@@ -1756,7 +1756,7 @@ User0     @osdteletext
      5. -
    5. create /etc/rc_maps.cfg
      +
    6. create /etc/rc_maps.cfg
      #
@@ -1947,17 +1947,17 @@ ati_remote    rc-medion-x10-digitainer   /lib/udev/rc_keymaps/rc-medion-x10-digi
    -
    -

    7.8.4 files

    +
    +

    7.8.4 files

    -
    -

    7.9 pulseaudio

    +
    +

    7.9 pulseaudio

    -
    -

    7.9.1 tasks

    +
    +

    7.9.1 tasks

    ---
@@ -1980,8 +1980,8 @@ ati_remote    rc-medion-x10-digitainer   /lib/udev/rc_keymaps/rc-medion-x10-digi
    -
    -

    7.9.2 templates

    +
    +

    7.9.2 templates

    # Use PulseAudio by default
@@ -2003,12 +2003,12 @@ ati_remote    rc-medion-x10-digitainer   /lib/udev/rc_keymaps/rc-medion-x10-digi
    -
    -

    7.10 yavdr-xorg

    +
    +

    7.10 yavdr-xorg

    -
    -

    7.10.1 About the GUI session

    +
    +

    7.10.1 About the GUI session

    The X-Server is started by using the two systemd units xlogin@.service and x@.service provided by the package xlogin. The former is enabled (and started) for the vdr user - which results (using the default settings for the user vdr with the uid 666) in the activation of xlogin@vdr.service when reaching the graphical.target. @@ -2037,21 +2037,21 @@ In order to achive a clean shutdown of the session, x@t7.service is

    -
    -

    7.10.2 default variables

    +
    +

    7.10.2 default variables

    -
    first_run: false
+
    first_run: False
    -
    -

    7.10.3 tasks

    +
    +

    7.10.3 tasks

      -
    1. main.yml
      +
    2. main.yml
      ---
@@ -2066,7 +2066,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
      3. -
    3. setup-xorg.yml
      +
    4. setup-xorg.yml
      ---
@@ -2170,7 +2170,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
      5. -
    5. detect-xorg.yml
      +
    6. detect-xorg.yml
      ---
@@ -2292,7 +2292,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
      7. -
    7. desktop-session.yml
      +
    8. desktop-session.yml
      ---
@@ -2411,14 +2411,14 @@ In order to achive a clean shutdown of the session, x@t7.service is
    -
    -

    7.10.4 templates

    +
    +

    7.10.4 templates

      -
    1. xorg
      +
    2. xorg
        -
      1. x-verbose@.service
        +
      2. x-verbose@.service
        # file: roles/yavdr-xorg/templates/systemd/system/x-verbose@.service.j2
@@ -2434,7 +2434,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        3. -
      3. Drop-in snippet for x@.service
        +
      4. Drop-in snippet for x@.service
        [Unit]
@@ -2455,7 +2455,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        5. -
      5. Drop-in snippet for vdr.service
        +
      6. Drop-in snippet for vdr.service
        {{ ansible_managed_file | comment }}
@@ -2467,7 +2467,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        7. -
      7. .xinitrc
        +
      8. .xinitrc
        #!/bin/bash
@@ -2477,7 +2477,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        9. -
      9. xorg.conf
        +
      10. xorg.conf
        Section "Device"
@@ -2806,7 +2806,7 @@ EndSection
        11. -
      11. .Xresources
        +
      12. .Xresources
        xterm*background: Black
@@ -2831,7 +2831,7 @@ XTerm.vt100.font: 7x13
      3. -
    3. vdr
      +
    4. vdr
      [Service]
@@ -2847,9 +2847,9 @@ XTerm.vt100.font: 7x13
      5. -
    5. Systemd User Session
      +
    6. Systemd User Session
        -
      1. yavdr-desktop.target
        +
      2. yavdr-desktop.target
        [Unit]
@@ -2863,7 +2863,7 @@ XTerm.vt100.font: 7x13
        3. -
      3. detect-second-display
        +
      4. detect-second-display
        [Unit]
@@ -2879,7 +2879,7 @@ XTerm.vt100.font: 7x13
        5. -
      5. openbox-second.service
        +
      6. openbox-second.service
        [Unit]
@@ -2901,7 +2901,7 @@ XTerm.vt100.font: 7x13
        7. -
      7. osd2web.service
        +
      8. osd2web.service
        [Unit]
@@ -2922,7 +2922,7 @@ XTerm.vt100.font: 7x13
        9. -
      9. tmux.service
        +
      10. tmux.service
        [Unit]
@@ -2941,7 +2941,7 @@ XTerm.vt100.font: 7x13
        11. -
      11. wm-exit.service
        +
      12. wm-exit.service
        [Unit]
@@ -2961,7 +2961,7 @@ XTerm.vt100.font: 7x13
      7. -
    7. irexec
      +
    8. irexec

      irexec.service starts irexec for the user session @@ -2991,9 +2991,9 @@ end

    • -
  • openbox
    +
  • openbox
      -
    1. autostart
      +
    2. autostart
      # forward environment variables to an environment file and the systemd user session
@@ -3029,7 +3029,7 @@ systemctl --user isolate yavdr-desktop.target
      3. -
    3. rc.xml
      +
    4. rc.xml
      <?xml version="1.0" encoding="UTF-8"?>
@@ -3849,12 +3849,12 @@ systemctl --user isolate yavdr-desktop.target
      -
      -

      7.11 samba-install

      +
      +

      7.11 samba-install

      -
      -

      7.11.1 tasks

      +
      +

      7.11.1 tasks

      ---
@@ -3876,12 +3876,12 @@ systemctl --user isolate yavdr-desktop.target
      -
      -

      7.12 samba-config

      +
      +

      7.12 samba-config

      -
      -

      7.12.1 tasks

      +
      +

      7.12.1 tasks

      ---
@@ -3906,14 +3906,14 @@ systemctl --user isolate yavdr-desktop.target
      -
      -

      7.12.2 templates

      +
      +

      7.12.2 templates

        -
      1. smb.conf
        +
      2. smb.conf
          -
        1. global settings
          +
        2. global settings
          {{ ansible_managed_file | comment }}
@@ -3999,7 +3999,7 @@ systemctl --user isolate yavdr-desktop.target
          3. -
        3. media directories
          +
        4. media directories
          {% for name, path in media_dirs.iteritems() %}
@@ -4021,7 +4021,7 @@ systemctl --user isolate yavdr-desktop.target
          5. -
        5. include custom samba exports
          +
        6. include custom samba exports
          include = /etc/samba/smb.conf.custom
@@ -4034,15 +4034,15 @@ systemctl --user isolate yavdr-desktop.target
      -
      -

      7.13 STARTED autoinstall-drivers

      +
      +

      7.13 STARTED autoinstall-drivers

      It would be nice to be able to detect if it is suitable to install those drivers:

      -
      -

      7.13.1 TODO sundtek for Sundtek devices (local or network connection)

      +
      +

      7.13.1 TODO sundtek for Sundtek devices (local or network connection)

      Vendor-IDs: @@ -4053,14 +4053,14 @@ Vendor-IDs:

      -
      -

      7.13.2 TODO dddvb-dkms if only newer DD cards are detected

      +
      +

      7.13.2 TODO dddvb-dkms if only newer DD cards are detected

      -
      -

      7.13.3 TODO media-build-experimental (up to kernel 4.8) for „old“ cards like TT S2-6400 FF

      +
      +

      7.13.3 TODO media-build-experimental (up to kernel 4.8) for „old“ cards like TT S2-6400 FF

      -
      -

      7.13.4 TODO newly merged DD drivers

      +
      +

      7.13.4 TODO newly merged DD drivers

      from http://www.vdr-portal.de/board18-vdr-hardware/board102-dvb-karten/120817-treiber-der-cine-ctv6-ddbridge-ci-in-den-kernel-integrieren/ @@ -4069,15 +4069,15 @@ from -

      7.14 autoinstall-ubuntu-drivers

      +
      +

      7.14 autoinstall-ubuntu-drivers

      The tool ubuntu-drivers is used to install the matching driver version for nvidia graphics cards, virtualbox guest additions and Intel and AMD microcode updates.

      -
      -

      7.14.1 tasks

      +
      +

      7.14.1 tasks

      ---
@@ -4101,8 +4101,8 @@ The tool ubuntu-drivers is used to install the matching driver version for nvidi
      -
      -

      7.15 autoinstall-virtualbox-guest

      +
      +

      7.15 autoinstall-virtualbox-guest

      This role installs the guest additions for virtualbox guests on Ubuntu 16.04 @@ -4133,12 +4133,12 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04

      -
      -

      7.16 autoinstall-atric-usb

      +
      +

      7.16 autoinstall-atric-usb

      -
      -

      7.16.1 dependencies

      +
      +

      7.16.1 dependencies

      ---
@@ -4149,8 +4149,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
      -
      -

      7.16.2 tasks

      +
      +

      7.16.2 tasks

      ---
@@ -4193,8 +4193,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
      -
      -

      7.16.3 templates

      +
      +

      7.16.3 templates

      {{ ansible_managed_file | comment }}
@@ -4223,15 +4223,15 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
      -
      -

      7.17 autoinstall-satip

      +
      +

      7.17 autoinstall-satip

      If a Sat>IP Server responds to a discovery request, the package vdr-plugin-satip is installed.

      -
      -

      7.17.1 tasks

      +
      +

      7.17.1 tasks

      ---
@@ -4256,12 +4256,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.18 autoinstall-targavfd

      +
      +

      7.18 autoinstall-targavfd

      -
      -

      7.18.1 tasks

      +
      +

      7.18.1 tasks

      ---
@@ -4277,12 +4277,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.19 autoinstall-imonlcd

      +
      +

      7.19 autoinstall-imonlcd

      -
      -

      7.19.1 tasks

      +
      +

      7.19.1 tasks

      ---
@@ -4298,12 +4298,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.20 autoinstall-libcecdaemon

      +
      +

      7.20 autoinstall-libcecdaemon

      -
      -

      7.20.1 tasks

      +
      +

      7.20.1 tasks

      ---
@@ -4319,12 +4319,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.21 autoinstall-pvr350

      +
      +

      7.21 autoinstall-pvr350

      -
      -

      7.21.1 tasks

      +
      +

      7.21.1 tasks

      ---
@@ -4340,8 +4340,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.22 autoinstall-hauppauge-pvr

      +
      +

      7.22 autoinstall-hauppauge-pvr

      ---
@@ -4356,12 +4356,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.23 autoinstall-dvbsky-firmware

      +
      +

      7.23 autoinstall-dvbsky-firmware

      -
      -

      7.23.1 defaults

      +
      +

      7.23.1 defaults

      ---
@@ -4371,8 +4371,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.23.2 tasks

      +
      +

      7.23.2 tasks

      ---
@@ -4422,15 +4422,15 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
      -
      -

      7.24 TODO autoinstall-dvbhddevice

      +
      +

      7.24 TODO autoinstall-dvbhddevice

      Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware sollte in yavdr-firmware stecken

      -
      -

      7.24.1 tasks

      +
      +

      7.24.1 tasks

      ---
@@ -4447,12 +4447,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
      -
      -

      7.25 autoinstall-dvbsddevice

      +
      +

      7.25 autoinstall-dvbsddevice

      -
      -

      7.25.1 tasks

      +
      +

      7.25.1 tasks

      ---
@@ -4470,12 +4470,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
      -
      -

      7.26 autoinstall-hardware-irmp

      +
      +

      7.26 autoinstall-hardware-irmp

      -
      -

      7.26.1 tasks

      +
      +

      7.26.1 tasks

      ---
@@ -4491,24 +4491,24 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
      1. TODO add other device ids if necessary
        2. +
      2. TODO add other device ids if necessary
      -
      -

      7.27 kodi

      +
      +

      7.27 kodi

      -
      -

      7.27.1 tasks

      +
      +

      7.27.1 tasks

        -
      1. Install KODI
        +
      2. Install KODI
          -
        • main.yml
          -
          +
        • main.yml
          +
          - import_tasks: install-kodi.yml tags=install,update,kodi:install
 - import_tasks: configure-kodi.yml tags=install,update,kodi:configure
@@ -4516,7 +4516,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
          • -
        • install-kodi.yml
          +
        • install-kodi.yml
          ---
@@ -4534,7 +4534,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
          • -
        • configure-kodi.yml
          +
        • configure-kodi.yml
          - name: create kodi.service for the user session
@@ -4583,12 +4583,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
      -
      -

      7.27.2 templates

      +
      +

      7.27.2 templates

        -
      1. kodi.service
        +
      2. kodi.service

        This systemd unit for the user session starts (and stops) kodi. @@ -4613,15 +4613,15 @@ This systemd unit for the user session starts (and stops) kodi.

      -
      -

      7.27.3 files

      +
      +

      7.27.3 files

      Those configuration files provide a preconfiguration for kodi which overrides the system wide configuration

        -
      1. Lircmap.xml
        +
      2. Lircmap.xml

        This file allows to map keys sent by remotes via eventlircd (which uses the name devinput) to kodi key names. @@ -4691,14 +4691,14 @@ This file allows to map keys sent by remotes via eventlircd (which uses the name

      5. -
    5. keymaps
      +
    6. keymaps

      This file maps the keys defined in Lircmap.xml to actions within kodi.

        -
      1. remote.xml
        +
      2. remote.xml
        <!-- This file contains the mapping of keys (gamepad, remote, and keyboard) to actions within XBMC -->
@@ -5249,17 +5249,17 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
    • -
    -

    7.28 dvd

    +
    +

    7.28 dvd

    -
    -

    7.28.1 tasks

    +
    +

    7.28.1 tasks

      -
    • install libdvd-pkg, allow programs to eject optical media
      -
      +
    • install libdvd-pkg, allow programs to eject optical media
      +
      ---
 # file: roles/dvd/tasks/main.yml
@@ -5299,8 +5299,8 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
    -
    -

    7.29 template-test

    +
    +

    7.29 template-test

    ---
@@ -5541,12 +5541,12 @@ EndSection
    -
    -

    7.30 wakeup

    +
    +

    7.30 wakeup

    -
    -

    7.30.1 defaults

    +
    +

    7.30.1 defaults

    ---
@@ -5556,8 +5556,8 @@ EndSection
    -
    -

    7.30.2 tasks

    +
    +

    7.30.2 tasks

    ---
@@ -5578,8 +5578,8 @@ EndSection
    -
    -

    7.30.3 templates

    +
    +

    7.30.3 templates

    {{ ansible_managed_file | comment }}
@@ -5605,12 +5605,12 @@ ACPI_START_AHEAD=5
    -
    -

    7.31 grub-config

    +
    +

    7.31 grub-config

    -
    -

    7.31.1 default variables

    +
    +

    7.31.1 default variables

    system:
@@ -5622,8 +5622,8 @@ ACPI_START_AHEAD=5
    -
    -

    7.31.2 tasks

    +
    +

    7.31.2 tasks

    ---
@@ -5648,8 +5648,8 @@ ACPI_START_AHEAD=5
    -
    -

    7.31.3 templates

    +
    +

    7.31.3 templates

    #!/bin/sh
@@ -5672,8 +5672,8 @@ menuentry "PowerOff" {
    -
    -

    7.31.4 handlers

    +
    +

    7.31.4 handlers

    ---
@@ -5691,15 +5691,15 @@ menuentry "PowerOff" {
    -
    -

    8 Modules

    +
    +

    8 Modules

    This section contains custom modules for the yaVDR Playbooks. They are used to collect facts about the system and configure applications and daemons.

    -
    -

    8.1 hardware_facts.py

    +
    +

    8.1 hardware_facts.py

    # This Module collects the vendor- and device ids for USB- and PCI(e)-devices and currently loaded kernel modules.
@@ -5876,8 +5876,8 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
    -
    -

    8.2 satip_facts.py

    +
    +

    8.2 satip_facts.py

    DOCUMENTATION = '''
@@ -6001,8 +6001,8 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
    -
    -

    8.3 xrandr_facts.py

    +
    +

    8.3 xrandr_facts.py

    • [ ] support multiple screens (-d :0.0 .. :0.n)
      • @@ -6284,8 +6284,8 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
    -
    -

    9 Handlers

    +
    +

    9 Handlers

    - name: Reconfigure unattended upgrades with dpkg
@@ -6358,7 +6358,7 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c

    Autor: Alexander Grothe <seahawk1986@gmx.de>

    -

    Created: 2018-01-07 So 18:44

    +

    Created: 2018-01-07 So 19:00

    Validate

    diff --git a/Manual.org b/Manual.org index 656f58d..65ed528 100644 --- a/Manual.org +++ b/Manual.org @@ -154,7 +154,7 @@ apt-get update apt-get -y install --no-install-recommends ansible # TODO: run ansible on local host -ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=true" +ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=True" #+END_SRC * Playbooks ** yavdr07.yml @@ -574,7 +574,7 @@ APT::Install-Suggests "0"; *** variables #+BEGIN_SRC yaml :tangle roles/collect-facts/defaults/main.yml :mkdirp yes -first_run: false +first_run: False #+END_SRC *** tasks ***** main.yml @@ -1685,7 +1685,7 @@ b'\xde\xad\xbe\xef' #+END_SRC *** default variables #+BEGIN_SRC yaml :tangle roles/yavdr-xorg/defaults/main.yml :mkdirp yes :padline no -first_run: false +first_run: False #+END_SRC *** tasks diff --git a/install-yavdr.sh b/install-yavdr.sh index 1944991..25e68f8 100755 --- a/install-yavdr.sh +++ b/install-yavdr.sh @@ -13,4 +13,4 @@ apt-get update apt-get -y install --no-install-recommends ansible # TODO: run ansible on local host -ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=true" +ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=True" diff --git a/roles/collect-facts/defaults/main.yml b/roles/collect-facts/defaults/main.yml index cb1a64e..fffb828 100644 --- a/roles/collect-facts/defaults/main.yml +++ b/roles/collect-facts/defaults/main.yml @@ -1 +1 @@ -first_run: false +first_run: False diff --git a/roles/yavdr-xorg/defaults/main.yml b/roles/yavdr-xorg/defaults/main.yml index cb1a64e..fffb828 100644 --- a/roles/yavdr-xorg/defaults/main.yml +++ b/roles/yavdr-xorg/defaults/main.yml @@ -1 +1 @@ -first_run: false +first_run: False