diff options
Diffstat (limited to 'nixos/doc/manual/release-notes/rl-2009.xml')
| -rw-r--r-- | nixos/doc/manual/release-notes/rl-2009.xml | 86 |
1 files changed, 44 insertions, 42 deletions
diff --git a/nixos/doc/manual/release-notes/rl-2009.xml b/nixos/doc/manual/release-notes/rl-2009.xml index 8135bb562c84..d9ff51ae3df0 100644 --- a/nixos/doc/manual/release-notes/rl-2009.xml +++ b/nixos/doc/manual/release-notes/rl-2009.xml @@ -66,6 +66,12 @@ </listitem> <listitem> <para> + Python 3.5 has reached its upstream EOL at the end of September 2020: it + has been removed from the list of available packages. + </para> + </listitem> + <listitem> + <para> Two new options, <link linkend="opt-services.openssh.authorizedKeysCommand">authorizedKeysCommand</link> and <link linkend="opt-services.openssh.authorizedKeysCommandUser">authorizedKeysCommandUser</link>, have been added to the <literal>openssh</literal> module. If you have <literal>AuthorizedKeysCommand</literal> @@ -226,29 +232,7 @@ GRANT ALL PRIVILEGES ON *.* TO 'mysql'@'localhost' WITH GRANT OPTION; <filename>testing-python.nix</filename> respectively. </para> </listitem> - <listitem> - <para> - The Mediatomb service declares new options. It also adapts existing - options to make the configuration generation lazy. The existing option - <literal>customCfg</literal> (defaults to false), when enabled, stops - the service configuration generation completely. It then expects the - users to provide their own correct configuration at the right location - (whereas the configuration was generated and not used at all before). - The new option <literal>transcodingOption</literal> (defaults to no) - allows a generated configuration. It makes the mediatomb service pulls - the necessary runtime dependencies in the nix store (whereas it was - generated with hardcoded values before). The new option - <literal>mediaDirectories</literal> allows the users to declare autoscan - media directories from their nixos configuration: - <programlisting> - services.mediatomb.mediaDirectories = [ - { path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; } - { path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; } - ]; - </programlisting> - </para> - </listitem> - </itemizedlist> + </itemizedlist> </section> <section xmlns="http://docbook.org/ns/docbook" @@ -605,8 +589,8 @@ systemd.services.nginx.serviceConfig.ReadWritePaths = [ "/var/www" ]; <listitem> <para> In addition to the hostname, the fully qualified domain name (FQDN), - which consists of <literal>${cfg.hostName}</literal> and - <literal>${cfg.domain}</literal> is now added to + which consists of <literal>${networking.hostName}</literal> and + <literal>${networking.domain}</literal> is now added to <literal>/etc/hosts</literal>, to allow local FQDN resolution, as used by the <literal>hostname --fqdn</literal> command and other applications that try to determine the FQDN. These new entries take precedence over entries @@ -626,6 +610,10 @@ systemd.services.nginx.serviceConfig.ReadWritePaths = [ "/var/www" ]; or digit, and have as interior characters only letters, digits, and hyphen. The maximum length is 63 characters. Additionally it is recommended to only use lower-case characters. + If (e.g. for legacy reasons) a FQDN is required as the Linux kernel network node hostname + (<literal>uname --nodename</literal>) the option + <literal>boot.kernel.sysctl."kernel.hostname"</literal> + can be used as a workaround (but be aware of the 64 character limit). </para> </listitem> <listitem> @@ -863,6 +851,13 @@ CREATE ROLE postgres LOGIN SUPERUSER; </listitem> <listitem> <para> + The <literal>hardware.nvidia.optimus_prime.enable</literal> service has been renamed to + <literal>hardware.nvidia.prime.sync.enable</literal> and has many new enhancements. + Related nvidia prime settings may have also changed. + </para> + </listitem> + <listitem> + <para> The package <package>nextcloud17</package> has been removed and <package>nextcloud18</package> was marked as insecure since both of them will <link xlink:href="https://docs.nextcloud.com/server/19/admin_manual/release_schedule.html"> will be EOL (end of life) within the lifetime of 20.09</link>. @@ -887,21 +882,11 @@ CREATE ROLE postgres LOGIN SUPERUSER; </para> </listitem> <listitem> - <para> - The mediatomb service is now using the new and maintained <literal>gerbera</literal> - <literal>gerbera</literal> fork instead of the unmaintained - <literal>mediatomb</literal> package. If you want to keep the old - behavior, you must declare it with: - <programlisting> - services.mediatomb.package = pkgs.mediatomb; - </programlisting> - One new option <literal>openFirewall</literal> has been introduced which - defaults to false. If you relied on the service declaration to add the - firewall rules itself before, you should now declare it with: - <programlisting> - services.mediatomb.openFirewall = true; - </programlisting> - </para> + <para> + The GNOME desktop manager no longer default installs <package>gnome3.epiphany</package>. + It was chosen to do this as it has a usability breaking issue (see issue <link xlink:href="https://github.com/NixOS/nixpkgs/issues/98819">#98819</link>) + that makes it unsuitable to be a default app. + </para> </listitem> </itemizedlist> </section> @@ -1132,8 +1117,10 @@ services.transmission.settings.rpc-bind-address = "0.0.0.0"; </listitem> <listitem> <para> - The <literal>fontconfig</literal> module stopped generating fontconfig 2.10.x config and cache. - Fontconfig 2.10.x was removed from Nixpkgs - it hasn't been used in any nixpkgs package anymore. + The <literal>fontconfig</literal> module stopped generating config and cache files for fontconfig 2.10.x, the <filename>/etc/fonts/fonts.conf</filename> now belongs to the latest fontconfig, just like on other Linux distributions, and we will <link xlink:href="https://github.com/NixOS/nixpkgs/pull/95358">no longer</link> be versioning the config directories. + </para> + <para> + Fontconfig 2.10.x was removed from Nixpkgs since it hasn’t been used in any Nixpkgs package for years now. </para> </listitem> <listitem> @@ -1223,5 +1210,20 @@ services.transmission.settings.rpc-bind-address = "0.0.0.0"; </para> </listitem> </itemizedlist> + <itemizedlist> + <listitem> + <para> + For AMD GPUs, Vulkan can now be used by adding <literal>amdvlk</literal> + to <literal>hardware.opengl.extraPackages</literal>. + </para> + </listitem> + <listitem> + <para> + Similarly, still for AMD GPUs, the ROCm OpenCL stack can now be used by adding + <literal>rocm-opencl-icd</literal> to + <literal>hardware.opengl.extraPackages</literal>. + </para> + </listitem> + </itemizedlist> </section> </section> |