The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Release Notes/1.3-release"
(12 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{DISPLAYTITLE:Funtoo Linux 1.3 Release Notes}} | |||
== Upgrading == | |||
We recommend a ''clean install'' of Funtoo Linux 1.3 rather than an upgrade if possible. To upgrade existing Funtoo Linux 1.2 systems, please see [[Upgrade_Instructions/1.3-release|Funtoo Linux 1.3 upgrade instructions.]] | |||
== Important Changes == | == Important Changes == | ||
Line 14: | Line 18: | ||
=== Deprecation of multilib Support === | === Deprecation of multilib Support === | ||
'''Multilib support -- the ability for 64-bit versions of Funtoo Linux to run legacy 32-bit applications -- has been deprecated''', so that Funtoo Linux for 64-bit CPUs is now 64-bit only -- what we used to offer as a separate "pure64" build. This was done because 32-bit support was originally created as a stop-gap measure 15 years ago to allow for a seamless transition to 64-bit computing, and we believe the time has come to shed this ongoing maintenance burden and focus efforts that have historically been spent on 32-bit compatibility | '''Multilib support -- the ability for 64-bit versions of Funtoo Linux to run legacy 32-bit applications -- has been deprecated''', so that Funtoo Linux for 64-bit CPUs is now 64-bit only -- what we used to offer as a separate "pure64" build. This was done because 32-bit support was originally created as a stop-gap measure 15 years ago to allow for a seamless transition to 64-bit computing, and we believe the time has come to shed this ongoing maintenance burden and focus efforts that have historically been spent on 32-bit compatibility to other areas. | ||
We realize that this may create inconvenience for some users. There are some workarounds that will work for most situations. One is to create a 32-bit chroot environment for the odd 32-bit application that you may still need to run. | We realize that this may create inconvenience for some users. There are some workarounds that will work for most situations. One is to create a 32-bit chroot environment for the odd 32-bit application that you may still need to run. | ||
Line 44: | Line 48: | ||
Official Funtoo Linux AWS images are now available in the AWS Marketplace (and will be updated to 1.3 soon!) See: | Official Funtoo Linux AWS images are now available in the AWS Marketplace (and will be updated to 1.3 soon!) See: | ||
[[File:aws-select-funtoo.png|thumb|Funtoo Linux in the AWS Marketplace]] | |||
* [https://aws.amazon.com/marketplace/pp/B07KT3VN7Q?qid=1546835222297&sr=0-1&ref_=srh_res_product_title Funtoo Linux (optimized for t2 instances)] | * [https://aws.amazon.com/marketplace/pp/B07KT3VN7Q?qid=1546835222297&sr=0-1&ref_=srh_res_product_title Funtoo Linux (optimized for t2 instances)] | ||
* [https://aws.amazon.com/marketplace/pp/B07KXSY9CF?qid=1546835222297&sr=0-2&ref_=srh_res_product_title Funtoo Linux (optimized for AMD EPYC instances)] | * [https://aws.amazon.com/marketplace/pp/B07KXSY9CF?qid=1546835222297&sr=0-2&ref_=srh_res_product_title Funtoo Linux (optimized for AMD EPYC instances)] | ||
Instructions for deploying Funtoo Linux AWS images can be found on our [[Amazon EC2 Launch]] page. | |||
=== Kits system changes === | === Kits system changes === | ||
Line 54: | Line 60: | ||
* {{c|core-server-kit}}, for key LAMP applications typically used in a server environment. | * {{c|core-server-kit}}, for key LAMP applications typically used in a server environment. | ||
* {{c|core-ui-kit}}, for core UI frameworks. | * {{c|core-ui-kit}}, for core UI frameworks. | ||
* {{c|core-gl-kit}}, for OpenGL/Mesa and core X11 protocols | * {{c|core-gl-kit}}, for OpenGL/Mesa and core X11 protocols (Again, thanks goes to Chris Giorgi for these efforts!) | ||
=== Database Improvements === | === Database Improvements === | ||
Line 61: | Line 67: | ||
=== Desktop Improvements === | === Desktop Improvements === | ||
==== {{c|xorg-server}} ==== | |||
{{c|suid}} USE is now disabled by default in {{c|xorg-server}}, partially in response to [https://www.mail-archive.com/xorg-announce@lists.x.org/msg01138.html CVE-2018-14665] and to follow upstream X.org recommended best practice. You will likely need to enable {{c|suid}} for X to start correctly if you are ''not'' using a display manager like {{c|gdm}} or {{c|xdm}}, and instead starting X directly using {{c|xinit}} or {{c|startx}}. This can be done by adding the following line to {{f|/etc/portage/package.use}}, and re-emerging if necessary: | |||
{{file|name=/etc/portage/package.use|body= | |||
x11-base/xorg-server suid | |||
}} | |||
==== Kit Improvements ==== | |||
[[File:Shotcut.png|200px|thumb|Shotcut video editor]] | |||
The following improvements have been made to desktop kits: | The following improvements have been made to desktop kits: | ||
Line 69: | Line 87: | ||
* {{c|kde-kit}} now delivers an updated KDE Plasma 5 (5.4.13) experience that, like GNOME 3.30, uses elogind but not systemd. | * {{c|kde-kit}} now delivers an updated KDE Plasma 5 (5.4.13) experience that, like GNOME 3.30, uses elogind but not systemd. | ||
* {{c|xfce-kit}} now delivers a fully-tested XFCE 4.13. | * {{c|xfce-kit}} now delivers a fully-tested XFCE 4.13. | ||
* {{c|gfxcard-nvidia}} mix-in created for easy one-step setup of systems with NVIDIA cards for use with proprietary NVIDIA drivers. nvidia-drivers now has uvm is enabled by default | * {{c|gfxcard-nvidia}} mix-in created for easy one-step setup of systems with NVIDIA cards for use with proprietary NVIDIA drivers. nvidia-drivers now has uvm is enabled by default. | ||
* Video editing improvements: {{c|media-libs/mlt}}, {{c|media-video/shotcut}} new {{c|media-video/flowblade}} ebuild added. | * Video editing improvements: {{c|media-libs/mlt}}, {{c|media-video/shotcut}} new {{c|media-video/flowblade}} ebuild added. | ||
Line 92: | Line 110: | ||
* mail-client/thunderbird-60.4.0 (https://www.mozilla.org/en-US/security/advisories/mfsa2018-28/) | * mail-client/thunderbird-60.4.0 (https://www.mozilla.org/en-US/security/advisories/mfsa2018-28/) | ||
* www-client/firefox-64.0 (https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/) | * www-client/firefox-64.0 (https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/) | ||
[[Category:Release Notes]] | |||
[[Category:Official Documentation]] |
Latest revision as of 01:24, January 8, 2019
Upgrading
We recommend a clean install of Funtoo Linux 1.3 rather than an upgrade if possible. To upgrade existing Funtoo Linux 1.2 systems, please see Funtoo Linux 1.3 upgrade instructions.
Important Changes
There have been several important changes to the Funtoo Linux release process, builds and packages that we will cover below.
Kit Snapshots
The kits in meta-repo are based on a 13 November 2018 snapshot of Gentoo Linux. Unlike Funtoo Linux 1.2, all kits are frozen and 1.3 will serve as a "long term stable" (LTS) release of Funtoo Linux. This differs from the 1.2 release of Funtoo Linux where some kits were frozen, and others were not. We moved to a fully-snapshotted kit model to prevent unpredictable dependency breakage due to upstream changes that would apply to some kits but not others, which was an ongoing problem with the 1.2 release.
Funtoo Linux will continue to follow a "snapshot" true release process so that we can focus our efforts on developing new features for Funtoo. Our release goal is to provide (at the very minimum) 4 releases per year, and backport critical security fixes into our LTS release. Work on our next release will begin immediately and will be based on a snapshot of Gentoo Linux from early 2019.
Behind the scenes, there have been very significant improvements to our kits technology which will make it possible to accelerate our release cycle.
Deprecation of multilib Support
Multilib support -- the ability for 64-bit versions of Funtoo Linux to run legacy 32-bit applications -- has been deprecated, so that Funtoo Linux for 64-bit CPUs is now 64-bit only -- what we used to offer as a separate "pure64" build. This was done because 32-bit support was originally created as a stop-gap measure 15 years ago to allow for a seamless transition to 64-bit computing, and we believe the time has come to shed this ongoing maintenance burden and focus efforts that have historically been spent on 32-bit compatibility to other areas.
We realize that this may create inconvenience for some users. There are some workarounds that will work for most situations. One is to create a 32-bit chroot environment for the odd 32-bit application that you may still need to run.
We will be offering more advanced solutions in the future. For applications such as the popular Steam, we are developing a container-based solution with GPU passthrough -- essentially a "chroot on steroids" -- that will allow you to deploy Steam in a container. We welcome the challenge to deliver this solution to Funtoo users as the efforts we are spending on container GPU acceleration are more beneficial to the larger Funtoo community than continuing to maintain multilib. We are making good progress here (Thanks Pavol Cupka (palica)!) and expect to have robust support for legacy apps like Steam soon. We appreciate your patience while we work on getting this ready!
Move to LTS Kernel
Historically, we have bundled a prebuilt debian-sources kernel and initramfs in our stage3 tarballs to make it easier for users to install Funtoo. We are now pre-building debian-sources-lts 4.9.130-1. This is a 'long term stable' kernel which allows us to offer more compatibility with things like nvidia-drivers
and virtualbox
. It is also a production-ready kernel by default. We still provide official support for debian-sources
, which is available for installation via ebuild, and will install as a pre-built universal kernel+initramfs if you set the binary
USE flag.
Please note that if you are not using debian-sources
or debian-sources-lts
, we assume you're an expert user and can take full responsibility for building and running your kernel of choice. While we allow you to run any kernel with Funtoo Linux, the only ones we officially provide support for are debian-sources
and debian-sources-lts
. This is because these are the kernels that we use ourselves, and test in both production and desktop/workstation environments.
Funtoo Linux 1.3 Improvements
Besides the important changes detailed above, there are a host of other improvements in Funtoo Linux 1.3, detailed below:
Core System
gcc
updated to 7.4.1. Many thanks to Chris Giorgi (TemptorSent) for these udpates! This rewritten gcc ebuild also has major improvements such as crossdev support. (See FL-3787.)binutils
updated to 2.31.1glibc
updated to version 2.27.gcc-config
updated to version 2.0.ego-2.7.2
includes many bug fixes.boot-update
, Funtoo's official boot loader tool, has now been fully integrated into ego asego boot
.openrc
updated to version 0.40.2.perl
updated to version 5.26.lxd
updated to 3.6.
AWS (Amazon Web Services) Support
Official Funtoo Linux AWS images are now available in the AWS Marketplace (and will be updated to 1.3 soon!) See:
Instructions for deploying Funtoo Linux AWS images can be found on our Amazon EC2 Launch page.
Kits system changes
The following kits have been created:
core-server-kit
, for key LAMP applications typically used in a server environment.core-ui-kit
, for core UI frameworks.core-gl-kit
, for OpenGL/Mesa and core X11 protocols (Again, thanks goes to Chris Giorgi for these efforts!)
Database Improvements
Funtoo Linux now offers official Oracle mysql-community
8 ebuilds. The Oracle ebuilds provide a compelling alternative to mariadb
for production database deployments.
Desktop Improvements
xorg-server
suid
USE is now disabled by default in xorg-server
, partially in response to CVE-2018-14665 and to follow upstream X.org recommended best practice. You will likely need to enable suid
for X to start correctly if you are not using a display manager like gdm
or xdm
, and instead starting X directly using xinit
or startx
. This can be done by adding the following line to /etc/portage/package.use
, and re-emerging if necessary:
/etc/portage/package.use
x11-base/xorg-server suid
Kit Improvements
The following improvements have been made to desktop kits:
xorg-kit
is now fully forked from Gentoo, and is based around xorg-server 1.20.gnome-kit
is fully forked from Gentoo and now offers a reliable GNOME 3.30 experience without systemd. See GNOME First Steps for information on how to set up.- Wayland support has been integrated into Funtoo Linux and is available via the
wayland
mix-in, and is enabled for kde-plasma-5 by default (see below.) kde-kit
now delivers an updated KDE Plasma 5 (5.4.13) experience that, like GNOME 3.30, uses elogind but not systemd.xfce-kit
now delivers a fully-tested XFCE 4.13.gfxcard-nvidia
mix-in created for easy one-step setup of systems with NVIDIA cards for use with proprietary NVIDIA drivers. nvidia-drivers now has uvm is enabled by default.- Video editing improvements:
media-libs/mlt
,media-video/shotcut
newmedia-video/flowblade
ebuild added.
It is now possible to enable both gnome
and kde-plasma-5
profiles and have a system that runs both systemd-less GNOME and KDE Plasma. The KDE Plasma profile is currently based on the GNOME profile to ensure compatibility so KDE Plasma-only users will (for now) notice quite a bit of GNOME-related USE flags being enabled. This will be addressed in future releases.
Web Site Improvements
- New Funtoo Linux MediaWiki theme.
- New even more simplified Installation Guide with a tutorial-style page-by-page navigation style.
- Addition of the Funtoo CPU Database with real-time search capability.
- Totally redesigned FAQ section that allows users to submit their own FAQ questions.
- Upgrades made to bug tracker and forums.
Security fixes
There have been numerous security fixes in Funtoo Linux 1.3, with a few notable fixes mentioned below:
- net-dns/avahi-0.7-r4 (CVE-2017-6519) addresses a long-standing issue of avahi being remotely exploitable over an IPv6 network.
- dev-lang/go-1.10.7, dev-lang/go-1.11.4 (CVE-2018-16873, CVE-2018-16874, CVE-2018-16875)
- dev-libs/libxml2-2.9.8-r1 (CVE-2017-8872, CVE-2018-14404, CVE-2018-14567)
- app-arch/tar-1.30-r1 (CVE-2018-20482)
- mail-client/thunderbird-60.4.0 (https://www.mozilla.org/en-US/security/advisories/mfsa2018-28/)
- www-client/firefox-64.0 (https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/)