<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>aeolus (Posts about os)</title><link>https://yieldsfalsehood.com/aeolus/</link><description></description><atom:link href="https://yieldsfalsehood.com/aeolus/tags/os.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:elliot@yieldsfalsehood.com"&gt;elliot&lt;/a&gt; </copyright><lastBuildDate>Thu, 07 Aug 2025 12:04:22 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>zabbix &gt;= 7.4.1-2 may require manual intervention</title><link>https://yieldsfalsehood.com/aeolus/posts/zabbix-7-4-1-2-may-require-manual-intervention-9383f659/</link><dc:creator>Arch</dc:creator><description>&lt;p&gt;Starting with &lt;code&gt;7.4.1-2&lt;/code&gt;, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared &lt;code&gt;zabbix&lt;/code&gt; user account (as originally &lt;a href="https://www.zabbix.com/documentation/current/en/manual/installation/install#create-user-account"&gt;intended by upstream&lt;/a&gt; and done by other distributions):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;zabbix-server&lt;/li&gt;
&lt;li&gt;zabbix-proxy&lt;/li&gt;
&lt;li&gt;zabbix-agent &lt;em&gt;(also used by the &lt;code&gt;zabbix-agent2&lt;/code&gt; package)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;zabbix-web-service&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This shared &lt;code&gt;zabbix&lt;/code&gt; user account is provided by the newly introduced &lt;code&gt;zabbix-common&lt;/code&gt; &lt;em&gt;split&lt;/em&gt; package, which is now a dependency for all relevant &lt;code&gt;zabbix-*&lt;/code&gt; packages.&lt;/p&gt;
&lt;p&gt;The switch to the new user account is handled automatically for the corresponding main configuration files and &lt;code&gt;systemd&lt;/code&gt; service units.&lt;/p&gt;
&lt;p&gt;However, &lt;strong&gt;manual intervention may be required&lt;/strong&gt; if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;PSK&lt;/code&gt; files used for encrypted communication&lt;/li&gt;
&lt;li&gt;Custom scripts for metrics collections or report generations&lt;/li&gt;
&lt;li&gt;&lt;code&gt;sudoers&lt;/code&gt; rules for metrics requiring elevated privileges to be collected&lt;/li&gt;
&lt;li&gt;...&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Those should therefore be updated to refer to and / or be owned by the new &lt;code&gt;zabbix&lt;/code&gt; user account, otherwise some services or user parameters may fail to work properly, or not at all.&lt;/p&gt;
&lt;p&gt;Once migrated, you may &lt;a href="https://wiki.archlinux.org/title/Users_and_groups#Other_examples_of_user_management"&gt;remove the obsolete user accounts from your system&lt;/a&gt;.&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/zabbix-7-4-1-2-may-require-manual-intervention-9383f659/</guid><pubDate>Mon, 04 Aug 2025 14:58:22 GMT</pubDate></item><item><title>DebConf25 closes in Brest and DebConf26 announced</title><link>https://yieldsfalsehood.com/aeolus/posts/debconf25-closes-in-brest-and-debconf26-announced-dff7c912/</link><dc:creator>Debian</dc:creator><description>&lt;p&gt;On Saturday 19 July 2025, the annual
&lt;a href="https://debconf25.debconf.org/"&gt;Debian Developers and Contributors Conference&lt;/a&gt;
came to a close.&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/debconf25-closes-in-brest-and-debconf26-announced-dff7c912/</guid><pubDate>Sun, 03 Aug 2025 00:00:00 GMT</pubDate></item><item><title>Alpine 3.19.8, 3.20.7, 3.21.4 and 3.22.1 released</title><link>https://yieldsfalsehood.com/aeolus/posts/alpine-3-19-8-3-20-7-3-21-4-and-3-22-1-released-8584a84d/</link><dc:creator>Alpine</dc:creator><description>&lt;p&gt;Alpine 3.19.8, 3.20.7, 3.21.4 and 3.22.1 released&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/alpine-3-19-8-3-20-7-3-21-4-and-3-22-1-released-8584a84d/</guid><pubDate>Tue, 15 Jul 2025 00:00:00 GMT</pubDate></item><item><title>linux-firmware &gt;= 20250613.12fe085f-5 upgrade requires manual intervention</title><link>https://yieldsfalsehood.com/aeolus/posts/linux-firmware-20250613-12fe085f-5-upgrade-requires-manual-intervention-70a1942e/</link><dc:creator>Arch</dc:creator><description>&lt;p&gt;With &lt;code&gt;20250613.12fe085f-5&lt;/code&gt;, we split our firmware into several vendor-focused packages. &lt;code&gt;linux-firmware&lt;/code&gt; is now an empty package depending on our default set of firmware.&lt;/p&gt;
&lt;p&gt;Unfortunately, this coincided with upstream reorganizing the symlink layout of the NVIDIA firmware, resulting in a situation that Pacman cannot handle. When attempting to upgrade from &lt;code&gt;20250508.788aadc8-2&lt;/code&gt; or earlier, you will see the following errors:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;To progress with the system upgrade, first remove &lt;code&gt;linux-firmware&lt;/code&gt;, then reinstall it as part of the upgrade:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# pacman -Rdd linux-firmware
# pacman -Syu linux-firmware
&lt;/code&gt;&lt;/pre&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/linux-firmware-20250613-12fe085f-5-upgrade-requires-manual-intervention-70a1942e/</guid><pubDate>Sat, 21 Jun 2025 23:09:08 GMT</pubDate></item><item><title>Plasma 6.4.0 will need manual intervention if you are on X11</title><link>https://yieldsfalsehood.com/aeolus/posts/plasma-6-4-0-will-need-manual-intervention-if-you-are-on-x11-304456a6/</link><dc:creator>Arch</dc:creator><description>&lt;p&gt;On Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11.&lt;/p&gt;
&lt;p&gt;With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn't be ok to install plasma-x11-session and kwin-x11 for every
one using Plasma.&lt;/p&gt;
&lt;h3&gt;tldr: Install plasma-x11-session if you are still using x11&lt;/h3&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/plasma-6-4-0-will-need-manual-intervention-if-you-are-on-x11-304456a6/</guid><pubDate>Fri, 20 Jun 2025 07:08:17 GMT</pubDate></item><item><title>Transition to the new WoW64 wine and wine-staging</title><link>https://yieldsfalsehood.com/aeolus/posts/transition-to-the-new-wow64-wine-and-wine-staging-801921bf/</link><dc:creator>Arch</dc:creator><description>&lt;p&gt;We are transitioning the wine and wine-staging package to a pure &lt;a href="https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0#wow64"&gt;wow64&lt;/a&gt; build. This change removes the dependency on the multilib repository for wine and wine-staging.&lt;/p&gt;
&lt;p&gt;The main reason for this is to align with upstream Wine development, which simplifies packaging and the dependency chain.&lt;/p&gt;
&lt;p&gt;Potential Issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;OpenGL Performance: A known limitation of the new WoW64 mode is reduced performance for 32-bit applications that use OpenGL directly&lt;/li&gt;
&lt;li&gt;Breaking Changes: Existing 32-bit prefixes needs to be recreated&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you are facing issues with 32 bit prefixes, please recreate these and reinstall the application.&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/transition-to-the-new-wow64-wine-and-wine-staging-801921bf/</guid><pubDate>Mon, 16 Jun 2025 16:22:01 GMT</pubDate></item><item><title>Alpine 3.22.0 released</title><link>https://yieldsfalsehood.com/aeolus/posts/alpine-3-22-0-released-67ad8378/</link><dc:creator>Alpine</dc:creator><description>&lt;p&gt;Alpine 3.22.0 released&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/alpine-3-22-0-released-67ad8378/</guid><pubDate>Fri, 30 May 2025 00:00:00 GMT</pubDate></item><item><title>Updated Debian 12: 12.11 released</title><link>https://yieldsfalsehood.com/aeolus/posts/updated-debian-12-12-11-released-0f4b796e/</link><dc:creator>Debian</dc:creator><description>&lt;p&gt;The Debian project is pleased to announce the eleventh update of its
stable distribution Debian 12 (codename &lt;q&gt;bookworm&lt;/q&gt;).
This point release mainly adds corrections for security issues,
along with a few adjustments for serious problems. Security advisories
have already been published separately and are referenced where available.&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/updated-debian-12-12-11-released-0f4b796e/</guid><pubDate>Sat, 17 May 2025 00:00:00 GMT</pubDate></item><item><title>Valkey to replace Redis in the [extra] Repository</title><link>https://yieldsfalsehood.com/aeolus/posts/valkey-to-replace-redis-in-the-extra-repository-d0dd3c55/</link><dc:creator>Arch</dc:creator><description>&lt;p&gt;Valkey, a high-performance key/value datastore, will be replacing redis in the [extra] repository. This change is due to Redis modifying its license from BSD-3-Clause to RSALv2 and SSPLv1 on &lt;a href="https://github.com/redis/redis/commit/0b34396924eca4edc524469886dc5be6c77ec4ed"&gt;March 20th, 2024&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Arch Linux Package Maintainers intend to support the availability of the redis package for roughly 14 days from the day of this post, to enable a smooth transition to valkey. After the 14 day transition period has ended, the redis package will be moved to the AUR. Also, from this point forward, the redis package will not receive any additional updates and should be considered deprecated until it is removed.&lt;/p&gt;
&lt;p&gt;Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes.&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/valkey-to-replace-redis-in-the-extra-repository-d0dd3c55/</guid><pubDate>Thu, 17 Apr 2025 13:16:29 GMT</pubDate></item><item><title>Updated Debian 12: 12.10 released</title><link>https://yieldsfalsehood.com/aeolus/posts/updated-debian-12-12-10-released-3088fd5a/</link><dc:creator>Debian</dc:creator><description>&lt;p&gt;The Debian project is pleased to announce the tenth update of its
stable distribution Debian 12 (codename &lt;q&gt;bookworm&lt;/q&gt;).
This point release mainly adds corrections for security issues,
along with a few adjustments for serious problems. Security advisories
have already been published separately and are referenced where available.&lt;/p&gt;</description><category>os</category><guid>https://yieldsfalsehood.com/aeolus/posts/updated-debian-12-12-10-released-3088fd5a/</guid><pubDate>Sat, 15 Mar 2025 00:00:00 GMT</pubDate></item></channel></rss>