A User wants to install yaVDR without customization and relies on full automation. @@ -528,24 +528,24 @@ Several roles are used to tie everything together:
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 by 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.
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. @@ -580,8 +580,8 @@ We use a callback to generate tags for all roles autmatically:
set -e @@ -605,12 +605,12 @@ ansible-playbook yavdr07.yml -b -i 'localhost_inventory
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: @@ -716,12 +716,12 @@ This playbook can either be used to run the installation on the localhost or any
---
@@ -739,8 +739,8 @@ This playbook can either be used to run the installation on the localhost or any
# properties of the user vdr and vdr-related options @@ -766,8 +766,8 @@ This playbook can either be used to run the installation on the localhost or any
# dictionary of directories for (shared) files. Automatically exported via NFS and Samba if those roles are enabled @@ -782,8 +782,8 @@ This playbook can either be used to run the installation on the localhost or any
nfs:
@@ -792,8 +792,8 @@ This playbook can either be used to run the installation on the localhost or any
samba:
@@ -803,8 +803,8 @@ This playbook can either be used to run the installation on the localhost or any
# additional packages you want to install @@ -820,8 +820,8 @@ This playbook can either be used to run the installation on the localhost or any
frontend: vdr
@@ -836,20 +836,20 @@ This playbook can either be used to run the installation on the localhost or any
---
@@ -870,19 +870,19 @@ This playbook can either be used to run the installation on the localhost or any
install nvidia-396 from ppa:graphics-drivers/ppa
---
@@ -912,15 +912,15 @@ install nvidia-396 from ppa:graphics-drivers/ppa
This role is used to set up a basic yaVDR installation. It creates the directories, installs the vdr and other useful packages.
This section is for reference only, please use the files in global_vars for customizations.
@@ -933,7 +933,7 @@ This section is for reference only, please use the files in global_vars
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. @@ -963,7 +963,7 @@ Automatically installed drivers can be very useful, but if you know you need a c
Add additional packages you would like to have on your installation to this list @@ -977,7 +977,7 @@ Add additional packages you would like to have on your installation to this list
This section allows you to set the recording directory, the user and group that runs the vdr and it’s home directory. @@ -1010,15 +1010,15 @@ This section allows you to set the recording directory, the user and group that
yavdr-common executes the following tasks:
---
@@ -1035,7 +1035,7 @@ yavdr-common executes the following tasks:
This task prevents apt to automatically install all recommended dependencies for packages: @@ -1052,7 +1052,7 @@ This task prevents apt to automatically install all recommended dependencies for
- name: add PPAs
@@ -1072,7 +1072,7 @@ This task prevents apt to automatically install all recommended dependencies for
- name: use bash instead of dash
@@ -1084,15 +1084,15 @@ This task prevents apt to automatically install all recommended dependencies for
- name: disable release-upgrade notifications
@@ -1114,7 +1114,7 @@ This task prevents apt to automatically install all recommended dependencies for
-- name: apt | install basic packages
@@ -1146,7 +1146,7 @@ This task prevents apt to automatically install all recommended dependencies for
- name: apt | install extra packages
@@ -1160,11 +1160,11 @@ This task prevents apt to automatically install all recommended dependencies for
{{ ansible_managed | comment('c') }} @@ -1184,7 +1184,7 @@ APT::Install-Suggests "0";
first_run: False
@@ -1212,12 +1212,12 @@ Allow the vdr user to restart vdr.service and reboot the system
- name: get information about usb and pci hardware and loaded kernel modules
@@ -1266,16 +1266,16 @@ Allow the vdr user to restart vdr.service and reboot the system
---
@@ -1294,7 +1294,7 @@ Allow the vdr user to restart vdr.service and reboot the system
- name: add svdrp and svdrp-disc to /etc/services
@@ -1309,7 +1309,7 @@ Allow the vdr user to restart vdr.service and reboot the system
- name: create vdr recdir
@@ -1344,7 +1344,7 @@ Allow the vdr user to restart vdr.service and reboot the system
The additional plugins to install can be set in the variable {{vdr_plugins}} in the group variables
@@ -1362,7 +1362,7 @@ The additional plugins to install can be set in the variable {{vdr_plugins
- name: ensure vdr is stopped
@@ -1393,7 +1393,7 @@ The additional plugins to install can be set in the variable {{vdr_plugins
- name: create directory for vdr.service systemd drop-in files
@@ -1414,8 +1414,8 @@ The additional plugins to install can be set in the variable {{vdr_plugins
LIRC.Up KEY_UP @@ -1567,7 +1567,7 @@ XKeySym.Next XF86AudioNext
# Remote control key macros for VDR @@ -1593,12 +1593,12 @@ User0 @osdteletext
---
@@ -1677,17 +1677,17 @@ User0 @osdteletext
/srv *(rw,fsid=0,sync,no_subtree_check,all_squash,anongid={{ vdr.gid }},anonuid={{ vdr.uid }})
@@ -1732,7 +1732,7 @@ User0 @osdteletext
<?xml version="1.0" standalone='no'?> @@ -1754,15 +1754,15 @@ User0 @osdteletext
The role yavdr-remote sets up the foundation for using eventlircd, lircd2uinput and the pre-configuration for remote receivers which can be detected by udev.
lircd0_socket: /var/run/lirc/lircd0
@@ -1770,8 +1770,8 @@ The role yavdr-remote sets up the foundation for using eventlircd,
---
@@ -1844,12 +1844,12 @@ The role yavdr-remote sets up the foundation for using eventlircd,
{% if frontend != 'kodi' %}
@@ -1860,7 +1860,7 @@ The role yavdr-remote sets up the foundation for using eventlircd,
[Service]
@@ -1870,7 +1870,7 @@ The role yavdr-remote sets up the foundation for using eventlircd,
{{ ansible_managed | comment }}
@@ -2062,19 +2062,19 @@ ati_remote rc-medion-x10-digitainer /lib/udev/rc_keymaps/rc-medion-x10-digi
---
@@ -2097,8 +2097,8 @@ ati_remote rc-medion-x10-digitainer /lib/udev/rc_keymaps/rc-medion-x10-digi
# Use PulseAudio by default @@ -2121,12 +2121,12 @@ ati_remote rc-medion-x10-digitainer /lib/udev/rc_keymaps/rc-medion-x10-digi
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. To simplify starting and stopping the X-server and the desktop session a yavdr-xorg.service is provided by the package yavdr-xorg, which depends on the two units mentioned before.
@@ -2155,8 +2155,8 @@ In order to achive a clean shutdown of the session, x@t7.service is
first_run: False
@@ -2179,12 +2179,12 @@ In order to achive a clean shutdown of the session, x@t7.service is
---
@@ -2197,7 +2197,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
---
@@ -2318,7 +2318,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
---
@@ -2478,7 +2478,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
KMS drivers (like for intel (i915) and amd (radeon)) require additional configuration beneath a customized xorg.conf - for a „static“ output configuration (which works if the TV or AV receiver is not turned on) we need to force loading the display(s) EDID early during the boot process.
@@ -2525,12 +2525,12 @@ Please note that rescanning the connected displays works only after removing the
{% set output_flag = 'D' if ("HDMI" in xorg.primary.connector or "DVI" in xorg.primary.connector or "DP" in xorg.primary.connector) else 'e' %} @@ -2540,11 +2540,11 @@ Please note that rescanning the connected displays works only after removing the
# file: roles/yavdr-xorg/templates/systemd/system/x-verbose@.service.j2 @@ -2560,7 +2560,7 @@ Please note that rescanning the connected displays works only after removing the
[Unit]
@@ -2586,7 +2586,7 @@ Please note that rescanning the connected displays works only after removing the
{{ ansible_managed | comment }}
@@ -2598,7 +2598,7 @@ Please note that rescanning the connected displays works only after removing the
{{ ansible_managed | comment }}
@@ -2612,7 +2612,7 @@ EndSection
Section "Device"
@@ -2938,7 +2938,7 @@ EndSection
-Set environment variables for system locale and user session on startup @@ -2954,12 +2954,12 @@ Set environment variables for system locale and user session on startup
#!/bin/bash @@ -2985,16 +2985,16 @@ manual_add_modules i915 radeon
---
@@ -3161,16 +3161,16 @@ manual_add_modules i915 radeon
xterm*background: Black @@ -3193,7 +3193,7 @@ XTerm.vt100.font: 7x13
#!/bin/bash @@ -3205,11 +3205,11 @@ XTerm.vt100.font: 7x13 -
# forward environment variables to an environment file and the systemd user session @@ -3245,7 +3245,7 @@ systemctl --user isolate yavdr-desktop.target
<?xml version="1.0" encoding="UTF-8"?> @@ -4071,7 +4071,7 @@ systemctl --user isolate yavdr-desktop.target
<?xml version="1.0" encoding="UTF-8"?> @@ -4900,11 +4900,11 @@ systemctl --user isolate yavdr-desktop.target -
[Unit] @@ -4917,7 +4917,7 @@ systemctl --user isolate yavdr-desktop.target
#!/bin/bash @@ -4946,7 +4946,7 @@ systemctl --user isolate yavdr-desktop.target
This script exchanges the primary and secondary screen. It needs access to the systemd user session. @@ -4965,7 +4965,7 @@ frontend-dbus-send start
[Unit]
@@ -4987,7 +4987,7 @@ frontend-dbus-send start
[Unit]
@@ -5010,7 +5010,7 @@ frontend-dbus-send start
[Unit]
@@ -5029,7 +5029,7 @@ frontend-dbus-send start
[Unit]
@@ -5048,7 +5048,7 @@ frontend-dbus-send start
-irexec.service starts irexec for the user session @@ -5082,12 +5082,12 @@ end
{{ ansible_managed | comment }}
@@ -5234,7 +5234,7 @@ end
{% for name, path in media_dirs.iteritems() %}
@@ -5256,7 +5256,7 @@ end
include = /etc/samba/smb.conf.custom @@ -5269,15 +5269,15 @@ end
It would be nice to be able to detect if it is suitable to install those drivers:
Vendor-IDs: @@ -5288,7 +5288,7 @@ Vendor-IDs:
https://github.com/s-moch/linux-saa716x - kann man den relevanten Teil als dkms-Paket bauen? @@ -5308,15 +5308,15 @@ Vendor-IDs:
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.
---
@@ -5339,8 +5339,8 @@ The tool ubuntu-drivers is used to install the matching driver version for nvidi
---
@@ -5408,8 +5408,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
---
@@ -5451,8 +5451,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
{{ ansible_managed | comment }}
@@ -5481,12 +5481,12 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
---
@@ -5497,8 +5497,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
---
@@ -5540,8 +5540,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
{{ ansible_managed | comment }}
@@ -5569,15 +5569,15 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
If a Sat>IP Server responds to a discovery request, the package vdr-plugin-satip is installed.
---
@@ -5602,12 +5602,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5623,12 +5623,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5644,12 +5644,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5665,12 +5665,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5686,8 +5686,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5702,12 +5702,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5718,8 +5718,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5760,12 +5760,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5776,8 +5776,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5787,8 +5787,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
---
@@ -5838,15 +5838,15 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware sollte in yavdr-firmware stecken
---
@@ -5857,8 +5857,8 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
---
@@ -5875,12 +5875,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
---
@@ -5891,8 +5891,8 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
---
@@ -5910,12 +5910,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
---
@@ -5926,8 +5926,8 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
---
@@ -5943,21 +5943,21 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
- import_tasks: install-kodi.yml tags=install,update,kodi:install - import_tasks: configure-kodi.yml tags=install,update,kodi:configure @@ -5965,7 +5965,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
---
@@ -5997,7 +5997,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
- name: create kodi.service for the user session
@@ -6046,12 +6046,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
This systemd unit for the user session starts (and stops) kodi. @@ -6076,15 +6076,15 @@ This systemd unit for the user session starts (and stops) kodi.
Those configuration files provide a preconfiguration for kodi which overrides the system wide configuration
This file maps the keys defined in Lircmap.xml to actions within kodi.
<?xml version="1.0" encoding="UTF-8"?> @@ -6714,17 +6714,17 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
--- # file: roles/dvd/tasks/main.yml @@ -6765,17 +6765,17 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
---
@@ -6824,12 +6824,12 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.