FEED Validator

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 25, column 0: Use of unknown namespace: com-wordpress:feed-additions:1 (11 occurrences) [help]

  <site xmlns="com-wordpress:feed-additions:1">58617187</site>	<item>
  

• line 649, column 0: style attribute contains potentially dangerous content: max-height (9 occurrences) [help]

  										<content:encoded><![CDATA[
  

• line 871, column 0: content:encoded should not contain decoding attribute (7 occurrences) [help]

• line 985, column 0: content:encoded should not contain fetchpriority attribute [help]

• line 985, column 0: content:encoded should not contain sizes attribute (6 occurrences) [help]

• line 1291, column 0: content:encoded should not contain data-id attribute (4 occurrences) [help]

  <figure class="wp-block-gallery has-nested-images columns-default is-cropped ...
  

• line 1295, column 0: content:encoded should not contain loading attribute (3 occurrences) [help]

Source: https://fedoramagazine.org/feed/

1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
4. xmlns:dc="http://purl.org/dc/elements/1.1/"
5. xmlns:atom="http://www.w3.org/2005/Atom"
6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
9. xmlns:georss="http://www.georss.org/georss"
10. xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
11. >
12.  
13. <channel>
14. <title>Fedora Magazine</title>
15. <atom:link href="https://fedoramagazine.org/feed/" rel="self" type="application/rss+xml" />
16. <link>https://fedoramagazine.org/</link>
17. <description>Guides, information, and news about the Fedora operating system for users, developers, system administrators, and community members.</description>
18. <lastBuildDate>Fri, 17 May 2024 14:22:36 +0000</lastBuildDate>
19. <language>en-US</language>
20. <sy:updatePeriod>
21. hourly </sy:updatePeriod>
22. <sy:updateFrequency>
23. 1 </sy:updateFrequency>
24. <generator>https://wordpress.org/?v=6.5.3</generator>
25. <site xmlns="com-wordpress:feed-additions:1">58617187</site> <item>
26. <title>Registration Open: Fedora 40 Release Party on May 24-25</title>
27. <link>https://fedoramagazine.org/registration-open-fedora-40-release-party-on-may-24-25/</link>
28. <comments>https://fedoramagazine.org/registration-open-fedora-40-release-party-on-may-24-25/#comments</comments>
30. <dc:creator><![CDATA[Joseph Gayoso]]></dc:creator>
31. <pubDate>Fri, 17 May 2024 08:00:00 +0000</pubDate>
32. <category><![CDATA[Fedora Project community]]></category>
33. <guid isPermaLink="false">https://fedoramagazine.org/?p=40442</guid>
34.  
35. <description><![CDATA[Join us next weekend on Friday and Saturday, May 24-25 to celebrate the release of Fedora Linux 40! We&#8217;re going to be hearing from community members inside and outside of the Fedora Project on what is new in Fedora 40, what we can look forward to next, and how we come together as a community. [&#8230;]]]></description>
36. <content:encoded><![CDATA[
37. <p>Join us next weekend on Friday and Saturday, <strong>May 24-25</strong> to celebrate the release of Fedora Linux 40! We&#8217;re going to be hearing from community members inside and outside of the Fedora Project on what is new in Fedora 40, what we can look forward to next, and how we come together as a community. </p>
38.  
39.  
40.  
41. <span id="more-40442"></span>
42.  
43.  
44.  
45. <h2 class="wp-block-heading">Register Here</h2>
46.  
47.  
48.  
49. <p><a href="https://pretix.eu/fedora/f40-party/">Register to attend the Fedora 40 Release Party here!</a></p>
50.  
51.  
52.  
53. <h2 class="wp-block-heading">What topics will be discussed? </h2>
54.  
55.  
56.  
57. <ul>
58. <li>We&#8217;ll learn about upgrades like KDE Plasma 6 and Fedora Asahi Remix 40</li>
59.  
60.  
61.  
62. <li>Community updates like from the Fedora DEI Team and Mentored Project Initiative</li>
63.  
64.  
65.  
66. <li>Infrastructure changes like with Kiwi for Fedora Cloud and the Git Forge investigation</li>
67.  
68.  
69.  
70. <li>Updates from our downstream friends at <a href="https://universal-blue.org/">Universal Blue</a> and <a href="https://ultramarine-linux.org/">Ultramarine</a></li>
71.  
72.  
73.  
74. <li>And more! <a href="https://fedoraproject.org/wiki/Fedora_Linux_40_Release_Party_Schedule#Schedule">Here&#8217;s the schedule of topics and speakers</a></li>
75. </ul>
76.  
77.  
78.  
79. <p>Join us!</p>
80.  
81.  
82.  
83. <hr class="wp-block-separator has-alpha-channel-opacity"/>
84.  
85.  
86.  
87. <h2 class="wp-block-heading">What is a release party?</h2>
88.  
89.  
90.  
91. <p>Fedora Release Parties are virtual, user-focused conferences where the community comes together to talk about what’s new in the latest release of Fedora and where we’re going for future releases. Topics we’ve covered include the process of working through implementing a change and roadmaps for what different teams want to do next in Fedora. Sometimes there are updates from Fedora-associated groups who have something to share, like Amazon or Lenovo. We also have breaks for socials where we can talk to each other in video calls (you don’t have to share video or speak if you don’t want to). If you have an interest in a behind-the-scenes look at your favorite distro, come learn and hang out with the contributors who make it!</p>
92.  
93.  
94.  
95. <h2 class="wp-block-heading">Where will it happen?</h2>
96.  
97.  
98.  
99. <p>In previous years we used <em>Hopin</em> to run virtual conferences, but the Fedora 40 Release Party will be the first that we do in Matrix! We’ve wanted to do this since the <a href="https://creativefreedomsummit.com/" target="_blank" rel="noreferrer noopener">Creative Freedom Summit</a> showed how it could be done a couple of years ago. This is a step that allows us to lean more on open source for outreach.</p>
100.  
101.  
102.  
103. <p>However, we also want to be open in another way, and that’s with livestreaming. We will be streaming the talks on our <a href="https://www.youtube.com/@fedora" target="_blank" rel="noreferrer noopener">Fedora Project YouTube channel</a>. That way anyone can watch and the streams will be immediately available afterwards!</p>
104.  
105.  
106.  
107. <p><a href="https://pretix.eu/fedora/f40-party/">Please register for the release party!</a> Once you do and provide your Matrix ID, the organizers will invite you to the Matrix channel and we&#8217;ll be on our way to a great celebration.</p>
108.  
109.  
110.  
111. <p>We hope to see you there!</p>
112.  
113.  
114.  
115. <h2 class="wp-block-heading">Learn more</h2>
116.  
117.  
118.  
119. <p>Check out the <a target="_blank" rel="noreferrer noopener" href="https://www.youtube.com/playlist?list=PL0x39xti0_64gKjGkGi8mId0X1ppl7lMH">Fedora 39 Release Party</a> to get an idea of the kinds of topics we cover.</p>
120.  
121.  
122.  
123. <p>Get hyped on social media with hashtag #FedoraReleaseParty!</p>
124. ]]></content:encoded>
126. <wfw:commentRss>https://fedoramagazine.org/registration-open-fedora-40-release-party-on-may-24-25/feed/</wfw:commentRss>
127. <slash:comments>3</slash:comments>
130. <post-id xmlns="com-wordpress:feed-additions:1">40442</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/05/F40_Release_Party_Register-300x127.jpg" length="7388" type="image/jpg" /> </item>
131. <item>
132. <title>An alternative way of saving toolboxes</title>
133. <link>https://fedoramagazine.org/alternative-way-of-saving-toolboxes-for-later-use/</link>
134. <comments>https://fedoramagazine.org/alternative-way-of-saving-toolboxes-for-later-use/#comments</comments>
136. <dc:creator><![CDATA[Liviu Vasut]]></dc:creator>
137. <pubDate>Mon, 13 May 2024 08:00:00 +0000</pubDate>
138. <category><![CDATA[FAQs and Guides]]></category>
139. <category><![CDATA[Fedora Project community]]></category>
140. <category><![CDATA[For Developers]]></category>
141. <category><![CDATA[For System Administrators]]></category>
142. <category><![CDATA[Using Software]]></category>
143. <category><![CDATA[backup]]></category>
144. <category><![CDATA[copy]]></category>
145. <category><![CDATA[restore]]></category>
146. <category><![CDATA[toolbox]]></category>
147. <guid isPermaLink="false">https://fedoramagazine.org/?p=40358</guid>
148.  
149. <description><![CDATA[A previous article in the Fedora Magazine describes how toolboxes can be saved in a container image repository and restored on the same or a different machine. The method described there works well for complex scenarios where setting up the toolbox takes considerable time or effort. But most of the time, toolboxes are simpler than [&#8230;]]]></description>
150. <content:encoded><![CDATA[
151. <p>A <a href="https://fedoramagazine.org/backup-and-restore-toolboxes-with-podman/" target="_blank" rel="noreferrer noopener">previous article</a> in the Fedora Magazine describes how toolboxes can be saved in a container image repository and restored on the same or a different machine. The method described there works well for complex scenarios where setting up the toolbox takes considerable time or effort. But most of the time, toolboxes are simpler than that, and saving them as container images is… well, wasteful. Let’s see how we can store and use our toolboxes in a cheaper way.</p>
152.  
153.  
154.  
155. <span id="more-40358"></span>
156.  
157.  
158.  
159. <h2 class="wp-block-heading">Problem statement</h2>
160.  
161.  
162.  
163. <ol>
164. <li>Define toolboxes in simple text files so that they are easy to transfer or version in a GIT repository.</li>
165.  
166.  
167.  
168. <li>Have the ability to describe a toolbox in a declarative way.</li>
169.  
170.  
171.  
172. <li>Have everything set up automatically so that the toolbox is ready to use upon initial entry.</li>
173.  
174.  
175.  
176. <li>The system should support customizations or extensions to accommodate any corner cases that were not foreseeable from the start.</li>
177. </ol>
178.  
179.  
180.  
181. <h2 class="wp-block-heading">Proposed solution</h2>
182.  
183.  
184.  
185. <p>Toolboxes are just instances of a container image. However, they have access to the home directory and use the same configuration as the host shell. On the other hand, each toolbox has a special file, visible only inside the toolbox, that keeps the name of the toolbox. This is  <em>/run/.containerenv</em>. Combining these two facts presents a possible route to the desired state: simply keep whatever initialization or configuration steps as simple <em>rc</em> files and use a convention to source them only for a specific toolbox. Consider, step by step, how this can be accomplished (using <em>bash</em> as an example because it’s the default shell in Fedora.  Other shells should support the same mechanisms).</p>
186.  
187.  
188.  
189. <p>For the system to work, two things are needed:</p>
190.  
191.  
192.  
193. <ul>
194. <li>A few toolbox definitions.</li>
195.  
196.  
197.  
198. <li>Something to take those definitions and turn them into toolboxes.</li>
199. </ul>
200.  
201.  
202.  
203. <h2 class="wp-block-heading">Storing toolbox Definitions</h2>
204.  
205.  
206.  
207. <p>The first point is easy. Put the files anywhere. For example, they can reside in<em>~/.bashrc.d/toolboxes</em>. (This path is used throughout the rest of the discussion.) Each <em>rc</em> file is named after the toolbox it configures. For example, <em>~/.bashrc.d/toolboxes/taskwarrior.rc</em> for a toolbox named <em>taskwarrior</em>  to be used for tasks and time tracking. The contents of this file is described later in this article.</p>
208.  
209.  
210.  
211. <h2 class="wp-block-heading">Converting Definitions into toolboxes</h2>
212.  
213.  
214.  
215. <p>For the second point, to keep things nice and tidy, place the orchestration logic in a separate file in the <em>~/.bashrc.d</em> directory. For example, call it <em>toolbox.rc</em>. It should have the following content:</p>
216.  
217.  
218.  
219. <pre class="wp-block-preformatted">function expose(){<br /> [ -f "$1" ] || echo -e "#!/bin/sh\nexec /usr/bin/flatpak-spawn --host $(basename $1) \"\$@\"" | sudo tee "$1" 1&gt;/dev/null &amp;&amp; sudo chmod +x "$1"<br />}<br /><br />function install_dependencies(){<br /> [ -f /.first_run ] || sudo dnf -y install $@<br />}<br /><br />if [ -f "/run/.toolboxenv" ]<br />then<br /> TOOLBOX_NAME=$( grep -oP "(?&lt;=name=\")[^\";]+" /run/.containerenv )<br /> if [ -f "$HOME/.bashrc.d/toolboxes/${TOOLBOX_NAME}.rc" ]<br /> then<br /> . "$HOME/.bashrc.d/toolboxes/${TOOLBOX_NAME}.rc"<br /> fi<br /> <br /> if ! [ -f /.first_run ] ; then<br /> [[ $(type -t setup) == function ]] &amp;&amp; setup<br /> sudo touch /.first_run<br /> fi<br />fi</pre>
220.  
221.  
222.  
223. <p>With the orchestration logic set up, some toolboxes are needed to orchestrate. Continuing with the <em>taskwarrior</em> toolbox example, a definition is added. Create a file called <em>~/.bashrc.d/toolboxes/taskwarrior.rc</em> and add the following line in it:</p>
224.  
225.  
226.  
227. <pre class="wp-block-preformatted">install_dependencies task timew</pre>
228.  
229.  
230.  
231. <p>This practically says that in this toolbox these two packages are to be installed: <em>task</em> and <em>timew</em>.</p>
232.  
233.  
234.  
235. <h2 class="wp-block-heading">Creating toolboxes</h2>
236.  
237.  
238.  
239. <p>Now, create and enter the toolbox:</p>
240.  
241.  
242.  
243. <pre class="wp-block-preformatted"><strong>$ toolbox create taskwarrior<br />$ toolbox enter taskwarrior</strong></pre>
244.  
245.  
246.  
247. <p>When the newly created toolbox is entered, <em>dnf</em> runs automatically to install the declared dependencies. Exit the toolbox and enter it again and you will get the prompt directly because all the packages are already installed.</p>
248.  
249.  
250.  
251. <p>It is now possible to stop the container and recreate the toolbox and everything will be installed back automatically.</p>
252.  
253.  
254.  
255. <pre class="wp-block-preformatted"><strong>$ podman stop timewarrior<br />$ toolbox rm timewarrior<br />$ toolbox create taskwarrior<br />$ toolbox enter taskwarrior</strong></pre>
256.  
257.  
258.  
259. <h2 class="wp-block-heading">Getting More Complicated</h2>
260.  
261.  
262.  
263. <p>Now complicate things a bit. What if some random commands need to run to set up the toolbox? This is done using a special function, called <em>setup()</em>, which is called from <em>toolbox.rc</em>, as shown above. As an example, here is the setup for a toolbox for working with AWS resources. It is named <em>awscli</em> and the associated configuration file is <em>~/.bashrc.d/toolboxes/awscli.rc</em>:</p>
264.  
265.  
266.  
267. <pre class="wp-block-preformatted">setup() {<br /> curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"<br /> unzip awscliv2.zip<br /> sudo ./aws/install<br />}</pre>
268.  
269.  
270.  
271. <p>Another use case to cover is exposing host commands inside the toolbox. Consider a toolbox for file management that opens pdf files in a browser previously installed as a flatpak on the host. Employ the <em>expose()</em> function, also defined in <em>toolbox.rc</em>, to give access to flatpak inside the toolbox. Below is the <em>vifm.rc</em> file used to create the <em>vifm</em> toolbox:</p>
272.  
273.  
274.  
275. <pre class="wp-block-preformatted">install_dependencies vifm fuse-zip curlftpfs shared-mime-info ImageMagick poppler-utils<br />expose /usr/bin/flatpak</pre>
276.  
277.  
278.  
279. <p>With that, from inside the toolbox, start the browser using:</p>
280.  
281.  
282.  
283. <pre class="wp-block-preformatted"><strong>$ flatpak run com.vivaldi.Vivaldi</strong></pre>
284.  
285.  
286.  
287. <h2 class="wp-block-heading">Extending the toolbox</h2>
288.  
289.  
290.  
291. <p>The last point in the problem statement (wish list) was extensibility. What is shown thus far is just a basis that already works pretty well. However, one can see how this system is adaptable and can evolve to meet other requirements. For example, new functions can be defined, both as implementations in <em>toolbox.rc</em> or as hooks to be called if defined inside the toolbox configuration file. Also, the existing functionality can be mixed and matched depending on current needs. The last example, for instance, demonstrates a combination of dependencies and host command access. Do not forget that the toolbox configurations defined in <em>~/.bashrc.d/toolboxes</em> are ultimately just shell files and you can add everything that the shell supports: aliases, custom functions, environment variables, etc.</p>
292.  
293.  
294.  
295. <h2 class="wp-block-heading">Troubleshooting</h2>
296.  
297.  
298.  
299. <p><strong>Problem</strong>: nothing is happening when I enter a new toolbox.</p>
300.  
301.  
302.  
303. <p>The <em>~/.bashrc</em> might not be set up to source files from <em>~/.bashrc.d</em>. Check that the following block exists in <em>~/.bashrc</em>:</p>
304.  
305.  
306.  
307. <pre class="wp-block-preformatted"># User specific aliases and functions<br />if [ -d ~/.bashrc.d ]; then<br />    for rc in ~/.bashrc.d/*; do<br />        if [ -f "$rc" ]; then<br />            . "$rc"<br />        fi<br />    done    <br />fi      <br />unset rc</pre>
308.  
309.  
310.  
311. <p><strong>Problem</strong>: when I enter a toolbox I get a <em>command not found</em> error.</p>
312.  
313.  
314.  
315. <p>The order in which files are sourced might not be correct. Try renaming <em>~/.bashrc.d/toolbox.rc</em> to <em>~/.bashrc.d/00-toolbox.rc</em>, then delete and recreate the toolbox.</p>
316. ]]></content:encoded>
318. <wfw:commentRss>https://fedoramagazine.org/alternative-way-of-saving-toolboxes-for-later-use/feed/</wfw:commentRss>
319. <slash:comments>4</slash:comments>
322. <post-id xmlns="com-wordpress:feed-additions:1">40358</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/05/toolbox-backup-code-1-300x127.jpg" length="10344" type="image/jpg" /> </item>
323. <item>
324. <title>Unlocking the power of Fedora CoreOS</title>
325. <link>https://fedoramagazine.org/unlocking-the-power-of-fedora-coreos/</link>
326. <comments>https://fedoramagazine.org/unlocking-the-power-of-fedora-coreos/#comments</comments>
328. <dc:creator><![CDATA[Aishat Ijiyode]]></dc:creator>
329. <pubDate>Fri, 10 May 2024 08:00:00 +0000</pubDate>
330. <category><![CDATA[Fedora Project community]]></category>
331. <category><![CDATA[FCOS]]></category>
332. <category><![CDATA[Fedora]]></category>
333. <category><![CDATA[Fedora CoreOS]]></category>
334. <guid isPermaLink="false">https://fedoramagazine.org/?p=40065</guid>
335.  
336. <description><![CDATA[Fedora CoreOS is an automatically updating, immutable operating system built on the trusted Fedora Linux distribution. It allows containerized workloads to run securely and at scale. It combines the benefits of containerization with the reliability and security of an immutable infrastructure. In this article, we&#8217;ll explore the unique capabilities of Fedora CoreOS and its use [&#8230;]]]></description>
337. <content:encoded><![CDATA[
338. <p>Fedora CoreOS is an automatically updating, immutable operating system built on the trusted Fedora Linux distribution. It allows containerized workloads to run securely and at scale. It combines the benefits of containerization with the reliability and security of an immutable infrastructure. In this article, we&#8217;ll explore the unique capabilities of Fedora CoreOS and its use cases.</p>
339.  
340.  
341.  
342. <span id="more-40065"></span>
343.  
344.  
345.  
346. <h2 class="wp-block-heading">The Essence of Immutability in Fedora CoreOS</h2>
347.  
348.  
349.  
350. <p>One of the core principles of Fedora CoreOS is immutability. In traditional operating systems, individual packages are updated. In Fedora CoreOS, updates are applied atomically as a complete replacement of the entire OS. This approach ensures consistency and reliability across deployments. It also eliminates potential drift or configuration issues caused by incremental updates.</p>
351.  
352.  
353.  
354. <h2 class="wp-block-heading">Automated Deployments with Ignition and Butane</h2>
355.  
356.  
357.  
358. <p>Fedora CoreOS leverages <a href="https://github.com/coreos/ignition" target="_blank" rel="noreferrer noopener">Ignition configuration files</a> for automated provisioning and configuration of instances during the initial boot process. However, instead of manually creating these JSON-formatted Ignition files, you can write the configurations in a simpler, human-readable, YAML based format called <a href="https://github.com/coreos/butane" target="_blank" rel="noreferrer noopener">Butane config</a>. Butane files are then converted into the corresponding Ignition files using the <a href="https://fedoramagazine.org/getting-started-with-fedora-coreos/" target="_blank" rel="noreferrer noopener">Butane tool</a>.</p>
359.  
360.  
361.  
362. <p>By automating the provisioning process with Ignition configs generated from Butane specifications, you can consistently deploy and configure Fedora CoreOS instances across different environments. These configuration files ensure repeatable and reliable deployments. The instances apply the configuration defined in the Ignition config on the first boot.</p>
363.  
364.  
365.  
366. <p>This automation capability is particularly valuable for infrastructure components use cases that require high availability and minimal downtime. These may include systems such as load balancers, firewalls, and other critical systems.</p>
367.  
368.  
369.  
370. <h2 class="wp-block-heading">Container orchestration and Kubernetes cluster setup</h2>
371.  
372.  
373.  
374. <p>Fedora CoreOS is optimized for running containerized workloads and seamlessly integrates with container orchestration platforms like Kubernetes. It comes pre-installed with both Podman and Moby-engine (Docker) for all your container needs.</p>
375.  
376.  
377.  
378. <p>Fedora CoreOS is also at the core of <a href="https://www.okd.io/" target="_blank" rel="noreferrer noopener">OKD</a>, the community distribution of Kubernetes. It is built from the same projects as Red Hat OpenShift. Additionally, you can customize Fedora CoreOS for specific workloads or environments. This makes it particularly useful for setting up dedicated Kubernetes clusters for different applications or environments.</p>
379.  
380.  
381.  
382. <p>One notable example is <a href="https://typhoon.psdn.io/" target="_blank" rel="noreferrer noopener">Typhoon</a>. A free and open-source project that provides declarative Kubernetes infrastructure management and integrates with Fedora CoreOS. With Typhoon, you can define your desired Kubernetes cluster configuration using human-readable language. And it will provision and configure additional cluster components, including Fedora CoreOS machines serving as worker nodes. This integration enables efficient and flexible Kubernetes deployments tailored to your needs. It ensures consistent and repeatable configurations across diverse environments like bare metal, cloud providers, and local networks.</p>
383.  
384.  
385.  
386. <h2 class="wp-block-heading">Customization and workload optimization</h2>
387.  
388.  
389.  
390. <p>While Fedora CoreOS is immutable, it is still customizable for specific workloads or environments. This  capability enables you to optimize Fedora CoreOS instances for particular applications or use cases by adding necessary packages, configurations, or services.</p>
391.  
392.  
393.  
394. <p>By tailoring Fedora CoreOS to your workloads, you can strike a balance between the benefits of an immutable operating system and the flexibility to meet your requirements. This approach ensures that your applications run in a consistent and optimized environment while still leveraging the security and reliability advantages of CoreOS.</p>
395.  
396.  
397.  
398. <h2 class="wp-block-heading">Automatic Updates and Resilience</h2>
399.  
400.  
401.  
402. <p>Fedora CoreOS follows a structured release cycle. Update releases typically occur every two weeks after undergoing extensive testing and validation through multiple update streams, such as &#8220;testing&#8221; and &#8220;next&#8221;. This automatic update mechanism ensures that Fedora CoreOS instances stay up-to-date with the latest stable releases. This mechanism also minimizes security risks and provides access to new features and enhancements.</p>
403.  
404.  
405.  
406. <p>You can opt to run instances on these testing streams to automatically evaluate upcoming releases before deploying to production. This way, you can identify and mitigate potential issues or incompatibilities. If an update introduces problems or vulnerabilities, the ability to roll back to a previous version further enhances the resilience of Fedora CoreOS-based infrastructure.</p>
407.  
408.  
409.  
410. <h2 class="wp-block-heading">Hybrid cloud and General-Purpose Server Capabilities</h2>
411.  
412.  
413.  
414. <p>While Fedora CoreOS is optimized for running containerized workloads and Kubernetes clusters, it is also designed to be operable as a standalone, general-purpose server operating system. This versatility makes it a compelling choice for a wide range of server workloads, beyond just containerized applications or Kubernetes clusters. It can provide benefits such as improved security, reliability, and reduced maintenance overhead, even for traditional server applications.</p>
415.  
416.  
417.  
418. <h2 class="wp-block-heading">Exploration and learning on Fedora CoreOS</h2>
419.  
420.  
421.  
422. <p>As an open-source project, Fedora CoreOS serves as a valuable resource for exploration and learning about immutable operating systems, containerization, and modern infrastructure practices. The <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/" target="_blank" rel="noreferrer noopener">Fedora CoreOS rich documentation</a> includes articles like &#8220;<a href="https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/" target="_blank" rel="noreferrer noopener">Getting Started with Fedora CoreOS</a>&#8221; and a host of other useful information about Fedora CoreOS. The <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/faq/" target="_blank" rel="noreferrer noopener">Fedora CoreOS FAQ</a> provides a solid starting point for understanding and experimenting with Fedora CoreOS. If you are new to Fedora CoreOS, <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-setup/" target="_blank" rel="noreferrer noopener">the tutorial section</a> is a great place to start. For further information about ignition files and how they are made from butane files, check out <a href="https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/">this section of the Fedora CoreOS documentation</a>.</p>
423.  
424.  
425.  
426. <p>Additionally, the open-source nature of Fedora CoreOS fosters community collaboration and contribution, enabling knowledge sharing and collective advancement of the project. This inclusive ecosystem encourages users to explore, learn, and contribute to its development, further enhancing its capabilities and adoption.</p>
427.  
428.  
429.  
430. <h2 class="wp-block-heading">In conclusion</h2>
431.  
432.  
433.  
434. <p>Fedora CoreOS offers a powerful combination of immutability, automatic updates, container optimization, and customization capabilities. All of this makes it a versatile choice for modern infrastructure and application deployment scenarios. Fedora CoreOS provides a robust foundation to meet diverse needs. Whether you&#8217;re deploying containerized applications, setting up Kubernetes clusters, exploring edge computing or IoT, or building secure and resilient infrastructure.</p>
435.  
436.  
437.  
438. <p>By embracing the principles of immutable infrastructure, automated deployments, and containerization, you can unlock the full potential of Fedora CoreOS and drive innovation in your organization&#8217;s infrastructure and application delivery pipelines.</p>
439. ]]></content:encoded>
441. <wfw:commentRss>https://fedoramagazine.org/unlocking-the-power-of-fedora-coreos/feed/</wfw:commentRss>
442. <slash:comments>6</slash:comments>
445. <post-id xmlns="com-wordpress:feed-additions:1">40065</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/04/COREOS-1-300x127.png" length="9497" type="image/jpg" /> </item>
446. <item>
447. <title>Fedora Asahi Remix 40 is now available</title>
448. <link>https://fedoramagazine.org/fedora-asahi-remix-40-is-now-available/</link>
449. <comments>https://fedoramagazine.org/fedora-asahi-remix-40-is-now-available/#comments</comments>
451. <dc:creator><![CDATA[Davide Cavalca]]></dc:creator>
452. <pubDate>Wed, 08 May 2024 08:00:00 +0000</pubDate>
453. <category><![CDATA[New in Fedora]]></category>
454. <category><![CDATA[Asahi]]></category>
455. <category><![CDATA[Releases]]></category>
456. <guid isPermaLink="false">https://fedoramagazine.org/?p=40373</guid>
457.  
458. <description><![CDATA[We are happy to announce the general availability of Fedora Asahi Remix 40. This release brings the newly released Fedora Linux 40 to Apple Silicon Macs. Fedora Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. It was unveiled at Flock 2023 and first released later in [&#8230;]]]></description>
459. <content:encoded><![CDATA[
460. <p>We are happy to announce the general availability of Fedora Asahi Remix 40. This release brings the <a href="https://fedoramagazine.org/announcing-fedora-linux-40/" target="_blank" rel="noreferrer noopener">newly released</a> Fedora Linux 40 to Apple Silicon Macs.</p>
461.  
462.  
463.  
464. <span id="more-40373"></span>
465.  
466.  
467.  
468. <p><a href="https://fedora-asahi-remix.org/" target="_blank" rel="noreferrer noopener">Fedora Asahi Remix</a> is developed in close collaboration with the <a href="https://fedoraproject.org/wiki/SIGs/Asahi" target="_blank" rel="noreferrer noopener">Fedora Asahi SIG</a> and the <a href="https://asahilinux.org/" target="_blank" rel="noreferrer noopener">Asahi Linux</a> project. It was <a href="https://fedoramagazine.org/coming-soon-fedora-for-apple-silicon-macs/" target="_blank" rel="noreferrer noopener">unveiled</a> at Flock 2023 and first <a href="https://fedoramagazine.org/introducing-fedora-asahi-remix-39/" target="_blank" rel="noreferrer noopener">released</a> later in December with Fedora Asahi Remix 39.</p>
469.  
470.  
471.  
472. <p>In addition to all the <a href="https://fedoramagazine.org/whats-new-fedora-workstation-40/" target="_blank" rel="noreferrer noopener">exciting improvements</a> brought by Fedora Linux 40, Fedora Asahi Remix brings <a href="https://rosenzweig.io/blog/conformant-gl46-on-the-m1.html" target="_blank" rel="noreferrer noopener">conformant OpenGL 4.6</a> support to Apple Silicon. It also continues to provide extensive <a href="https://asahilinux.org/fedora/#device-support" target="_blank" rel="noreferrer noopener">device support</a>, including high quality audio out of the box.</p>
473.  
474.  
475.  
476. <p>Fedora Asahi Remix offers <a href="https://kde.org/announcements/megarelease/6/" target="_blank" rel="noreferrer noopener">KDE Plasma 6</a> as our flagship desktop experience. It also features a custom Calamares-based initial setup wizard. A GNOME variant is also available, featuring GNOME 46, with both desktop variants matching what Fedora Linux offers. Fedora Asahi Remix also provides a Fedora Server variant for server workloads and other types of headless deployments. Finally, we offer a Minimal image for users that wish to build their own experience from the ground up.</p>
477.  
478.  
479.  
480. <p>You can install Fedora Asahi Remix today by following our <a href="https://docs.fedoraproject.org/en-US/fedora-asahi-remix/installation/" target="_blank" rel="noreferrer noopener">installation guide</a>. Existing systems, running Fedora Asahi Remix 39, can be updated following the usual Fedora <a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/" target="_blank" rel="noreferrer noopener">upgrade process</a>. </p>
481.  
482.  
483.  
484. <p>Please report any Remix-specific issues in our <a href="https://pagure.io/fedora-asahi/remix-bugs/issues" target="_blank" rel="noreferrer noopener">tracker</a>, or reach out in our <a href="https://discussion.fedoraproject.org/c/neighbors/asahi/92" target="_blank" rel="noreferrer noopener">Discourse forum</a> or our <a href="https://matrix.to/#/#asahi:fedoraproject.org" target="_blank" rel="noreferrer noopener">Matrix room</a> for user support.</p>
485. ]]></content:encoded>
487. <wfw:commentRss>https://fedoramagazine.org/fedora-asahi-remix-40-is-now-available/feed/</wfw:commentRss>
488. <slash:comments>8</slash:comments>
491. <post-id xmlns="com-wordpress:feed-additions:1">40373</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/05/Fedora_Asahi_remix_40_available-300x127.jpg" length="8166" type="image/jpg" /> </item>
492. <item>
493. <title>Get Involved with Fedora Bootable Containers</title>
494. <link>https://fedoramagazine.org/get-involved-with-fedora-bootable-containers/</link>
495. <comments>https://fedoramagazine.org/get-involved-with-fedora-bootable-containers/#comments</comments>
497. <dc:creator><![CDATA[jasonbrooks]]></dc:creator>
498. <pubDate>Tue, 07 May 2024 08:00:00 +0000</pubDate>
499. <category><![CDATA[Fedora Project community]]></category>
500. <guid isPermaLink="false">https://fedoramagazine.org/?p=40343</guid>
501.  
502. <description><![CDATA[For quite a while now, we&#8217;ve had image-based Fedora Linux variants—starting with Fedora Atomic Host and Atomic Desktop. The original variants evolved into Fedora CoreOS, Fedora IoT, a whole family of Fedora Atomic Desktops, and the awesome Universal Blue project. Bootable containers make it much simpler to create and collaborate on image-based Fedora systems. Here&#8217;s [&#8230;]]]></description>
503. <content:encoded><![CDATA[
504. <p>For quite a while now, we&#8217;ve had image-based Fedora Linux variants—starting with <a href="https://fedoraproject.org/wiki/Atomic_WG" target="_blank" rel="noreferrer noopener">Fedora Atomic Host and Atomic Desktop</a>. The original variants evolved into <a href="https://fedoraproject.org/coreos/" target="_blank" rel="noreferrer noopener">Fedora CoreOS</a>, <a href="https://fedoraproject.org/iot/" target="_blank" rel="noreferrer noopener">Fedora IoT</a>, a whole family of <a href="https://fedoraproject.org/atomic-desktops/" target="_blank" rel="noreferrer noopener">Fedora Atomic Desktops</a>, and the awesome <a href="https://universal-blue.org/" target="_blank" rel="noreferrer noopener">Universal Blue</a> project. Bootable containers make it much simpler to create and collaborate on image-based Fedora systems. Here&#8217;s how you can get involved.</p>
505.  
506.  
507.  
508. <span id="more-40343"></span>
509.  
510.  
511.  
512. <p>If you&#8217;ve used one of these image-based Fedora systems, you know how easy they are to update, upgrade, or, if things aren&#8217;t working quite right, to roll back. However, creating your own custom image-based Fedora system has always been a bit tricky, requiring special tools, processes and infrastructure.</p>
513.  
514.  
515.  
516. <p>Over <a href="https://fedoraproject.org/wiki/Changes/OstreeNativeContainer" target="_blank" rel="noreferrer noopener">the past couple of years</a>, the tools and methods available for building image-based systems in Fedora have evolved. They now natively support OCI/Docker containers as a transport and delivery mechanism for operating system content.&nbsp;</p>
517.  
518.  
519.  
520. <p>With these changes, and the introduction of <a href="https://containers.github.io/bootc/" target="_blank" rel="noreferrer noopener">bootc</a>, we now have the tools to build image-based systems using ordinary Containerfiles and regular OCI-container build tools. We also have the infrastructure to define, build, deploy and manage Linux systems.&nbsp;</p>
521.  
522.  
523.  
524. <p>For instance, the Fedora IoT WG <a href="https://fedoraproject.org/wiki/Changes/Fedora_IoT_Bootable_Container" target="_blank" rel="noreferrer noopener">has plans to deliver</a> two bootc containers for Fedora IoT users. There is a cut down minimal version for users to use as a base to build their own vision of Fedora IoT. There is also a second image to deliver the traditional Fedora IoT user experience.</p>
525.  
526.  
527.  
528. <h2 class="wp-block-heading">Taking the Initiative</h2>
529.  
530.  
531.  
532. <p>We have a great opportunity to enhance collaboration among image-based Fedora variants, and to empower other projects and individual users to create their own Fedora-based derivatives by working together on <a href="https://containers.github.io/bootable/" target="_blank" rel="noreferrer noopener">bootable container technologies</a>.&nbsp;</p>
533.  
534.  
535.  
536. <p>That&#8217;s why I&#8217;m excited to announce that we&#8217;ve proposed a new <a href="https://docs.fedoraproject.org/en-US/project/initiatives/" target="_blank" rel="noreferrer noopener">Fedora Community Initiative</a> to seize this opportunity. This initiative aims to bring together the Fedora working groups that build and promote image-based Fedora variants.</p>
537.  
538.  
539.  
540. <p>The contributors working on the <a href="https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-492-new-initiative-fedora-bootc/116062" target="_blank" rel="noreferrer noopener">proposed initiative</a> will:</p>
541.  
542.  
543.  
544. <ul>
545. <li>Identify opportunities to share base images</li>
546.  
547.  
548.  
549. <li>Identify and work through Fedora Infra issues</li>
550.  
551.  
552.  
553. <li>Document use of bootable container tools and processes</li>
554.  
555.  
556.  
557. <li>Promote the use of Fedora bootable containers with blog and mailing list posts, social media, and coordination with Fedora Marketing Team</li>
558.  
559.  
560.  
561. <li>Reach out to projects outside of Fedora proper that might want to collaborate</li>
562. </ul>
563.  
564.  
565.  
566. <p>Check out the initiative wiki page for more information. You can learn who to reach out to if you&#8217;d like to get involved in the effort, in the context of one of the Fedora variants. You can also join the discussion on Fedora&#8217;s matrix instance in the <a href="https://matrix.to/#/#bootc:fedoraproject.org" target="_blank" rel="noreferrer noopener">fedora-bootc</a> room, or on Fedora discussion by following or posting with the <a href="https://discussion.fedoraproject.org/tag/bootc-initiative" target="_blank" rel="noreferrer noopener">bootc-initiative tag</a>. Finally, check out this <a href="https://docs.fedoraproject.org/en-US/bootc/" target="_blank" rel="noreferrer noopener">doc page</a> to kick the tires on Fedora bootc for yourself.</p>
567. ]]></content:encoded>
569. <wfw:commentRss>https://fedoramagazine.org/get-involved-with-fedora-bootable-containers/feed/</wfw:commentRss>
570. <slash:comments>16</slash:comments>
573. <post-id xmlns="com-wordpress:feed-additions:1">40343</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/05/Bootable_containers-300x127.jpg" length="12252" type="image/jpg" /> </item>
574. <item>
575. <title>Save the Date: Fedora 40 Release Party on May 24-25</title>
576. <link>https://fedoramagazine.org/save-the-date-fedora-40-release-party-on-may-24-25/</link>
577. <comments>https://fedoramagazine.org/save-the-date-fedora-40-release-party-on-may-24-25/#comments</comments>
579. <dc:creator><![CDATA[Joseph Gayoso]]></dc:creator>
580. <pubDate>Mon, 06 May 2024 08:00:00 +0000</pubDate>
581. <category><![CDATA[Fedora Project community]]></category>
582. <guid isPermaLink="false">https://fedoramagazine.org/?p=40338</guid>
583.  
584. <description><![CDATA[After the hard work of pushing out the Fedora Linux 40 release, we now look at celebrating with a release party! The Fedora 40 Release Party will take place on May 24-25, Friday and Saturday. What is a release party? Fedora Release Parties are virtual, user-focused conferences where the community comes together to talk about [&#8230;]]]></description>
585. <content:encoded><![CDATA[
586. <p>After the hard work of pushing out the Fedora Linux 40 release, we now look at celebrating with a release party! The Fedora 40 Release Party will take place on <strong>May 24-25</strong>, Friday and Saturday.</p>
587.  
588.  
589.  
590. <span id="more-40338"></span>
591.  
592.  
593.  
594. <h2 class="wp-block-heading">What is a release party?</h2>
595.  
596.  
597.  
598. <p>Fedora Release Parties are virtual, user-focused conferences where the community comes together to talk about what&#8217;s new in the latest release of Fedora and where we&#8217;re going for future releases. Topics we&#8217;ve covered include the process of working through implementing a change and roadmaps for what different teams want to do next in Fedora. Sometimes there are updates from Fedora-associated groups who have something to share, like Amazon or Lenovo. We also have breaks for socials where we can talk to each other in video calls (you don&#8217;t have to share video or speak if you don&#8217;t want to). If you have an interest in a behind-the-scenes look at your favorite distro, come learn and hang out with the contributors who make it!</p>
599.  
600.  
601.  
602. <h2 class="wp-block-heading">Where will it happen?</h2>
603.  
604.  
605.  
606. <p>In previous years we used <em>Hopin</em> to run virtual conferences, but the Fedora 40 Release Party will be the first that we do in Matrix! We&#8217;ve wanted to do this since the <a href="https://creativefreedomsummit.com/" target="_blank" rel="noreferrer noopener">Creative Freedom Summit</a> showed how it could be done a couple of years ago. This is a step that allows us to lean more on open source for outreach.</p>
607.  
608.  
609.  
610. <p>However, we also want to be open in another way, and that&#8217;s with livestreaming. We will be streaming the talks on our <a href="https://www.youtube.com/@fedora" target="_blank" rel="noreferrer noopener">Fedora Project YouTube channel</a>. That way anyone can watch and the streams will be immediately available afterwards!</p>
611.  
612.  
613.  
614. <p>Details for registering will come soon, but for now please save the date for <strong>May 24-25</strong>!</p>
615.  
616.  
617.  
618. <p>We hope to see you there!</p>
619.  
620.  
621.  
622. <h2 class="wp-block-heading">Learn more</h2>
623.  
624.  
625.  
626. <p>Check out the <a target="_blank" rel="noreferrer noopener" href="https://www.youtube.com/playlist?list=PL0x39xti0_64gKjGkGi8mId0X1ppl7lMH">Fedora 39 Release Party</a> to get an idea of the kinds of topics we cover.</p>
627.  
628.  
629.  
630. <p>Get hyped on social media with hashtag #FedoraReleaseParty!</p>
631. ]]></content:encoded>
633. <wfw:commentRss>https://fedoramagazine.org/save-the-date-fedora-40-release-party-on-may-24-25/feed/</wfw:commentRss>
634. <slash:comments>2</slash:comments>
637. <post-id xmlns="com-wordpress:feed-additions:1">40338</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/05/F40_Release-Party-300x127.jpg" length="6496" type="image/jpg" /> </item>
638. <item>
639. <title>What’s new for Fedora Atomic Desktops in Fedora 40</title>
640. <link>https://fedoramagazine.org/whats-new-for-fedora-atomic-desktops-in-fedora-40/</link>
641. <comments>https://fedoramagazine.org/whats-new-for-fedora-atomic-desktops-in-fedora-40/#comments</comments>
643. <dc:creator><![CDATA[Timothée Ravier]]></dc:creator>
644. <pubDate>Mon, 29 Apr 2024 08:00:00 +0000</pubDate>
645. <category><![CDATA[Fedora Project community]]></category>
646. <guid isPermaLink="false">https://fedoramagazine.org/?p=40306</guid>
647.  
648. <description><![CDATA[Fedora 40 has been released! 🎉 So let’s see what comes in this new release for the Fedora Atomic Desktops variants (Silverblue, Kinoite, Sway Atomic and Budgie Atomic). Introducing Fedora Atomic Desktops As you might have guessed from the title, we are now called Fedora Atomic Desktops! See the&#160;Introducing Fedora Atomic Desktops&#160;Fedora Magazine article for [&#8230;]]]></description>
649. <content:encoded><![CDATA[
650. <p><a href="https://fedoramagazine.org/announcing-fedora-linux-40/" target="_blank" rel="noreferrer noopener">Fedora 40 has been released!</a> <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f389.png" alt="🎉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> So let’s see what comes in this new release for the Fedora Atomic Desktops variants (Silverblue, Kinoite, Sway Atomic and Budgie Atomic).</p>
651.  
652.  
653.  
654. <span id="more-40306"></span>
655.  
656.  
657.  
658. <h2 class="wp-block-heading">Introducing Fedora Atomic Desktops<a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#introducing-fedora-atomic-desktops"></a><br /><a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#introducing-fedora-atomic-desktops"></a></h2>
659.  
660.  
661.  
662. <p>As you might have guessed from the title, we are now called Fedora Atomic Desktops! See the&nbsp;<a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">Introducing Fedora Atomic Desktops</a>&nbsp;Fedora Magazine article for all the details.</p>
663.  
664.  
665.  
666. <p>The summary is that the Fedora Atomic Desktops are made up of four atomic spins:</p>
667.  
668.  
669.  
670. <ul>
671. <li>Fedora Silverblue</li>
672.  
673.  
674.  
675. <li>Fedora Kinoite</li>
676.  
677.  
678.  
679. <li>Fedora Sway Atomic (was Fedora Sericea)</li>
680.  
681.  
682.  
683. <li>Fedora Budgie Atomic (was Fedora Onyx)</li>
684. </ul>
685.  
686.  
687.  
688. <p>And we have a&nbsp;<a href="https://fedoraproject.org/atomic-desktops/" target="_blank" rel="noreferrer noopener">landing page on fedoraproject.org</a>.</p>
689.  
690.  
691.  
692. <h2 class="wp-block-heading">Status update on bootloader updates (bootupd integration)<a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#status-update-on-bootloader-updates-bootupd-integration"></a><br /><a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#status-update-on-bootloader-updates-bootupd-integration"></a></h2>
693.  
694.  
695.  
696. <p>Unfortunately, we could not land <a href="https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd" target="_blank" rel="noreferrer noopener">bootupd</a> support in this release due to an issue found late in Anaconda’s handling of bootupd installations which relied on incomplete functionality in bootupd.</p>
697.  
698.  
699.  
700. <p>We will attempt to add bootupd again after the release, via an update.</p>
701.  
702.  
703.  
704. <p>If you encounter Secure Boot errors or need to update your bootloader in the meantime, you can try the instructions from&nbsp;<a href="https://github.com/fedora-silverblue/issue-tracker/issues/543#issuecomment-2048350047" target="_blank" rel="noreferrer noopener">fedora-silverblue#543</a>. Make sure to have a Live USB ready in case you encounter an issue. Please make backups beforehand.</p>
705.  
706.  
707.  
708. <p>We are hoping to land improvements to bootupd that should simplify this process.</p>
709.  
710.  
711.  
712. <p>See:&nbsp;<a href="https://gitlab.com/fedora/ostree/sig/-/issues/1" target="_blank" rel="noreferrer noopener">atomic-desktops-sig#1</a>.</p>
713.  
714.  
715.  
716. <h2 class="wp-block-heading">What’s new in Silverblue<a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#whats-new-in-silverblue"></a><br /><a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#whats-new-in-silverblue"></a></h2>
717.  
718.  
719.  
720. <h3 class="wp-block-heading">Latest GNOME release<a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#latest-gnome-release"></a><br /><a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#latest-gnome-release"></a></h3>
721.  
722.  
723.  
724. <p>Fedora Silverblue comes with the latest&nbsp;<a href="https://release.gnome.org/46/" target="_blank" rel="noreferrer noopener">GNOME 46 release</a>.</p>
725.  
726.  
727.  
728. <p>For more details about the changes that comes with GNOME 46, see&nbsp;<a href="https://fedoramagazine.org/whats-new-fedora-workstation-40/" target="_blank" rel="noreferrer noopener">What’s new in Fedora Workstation 40</a>&nbsp;on the Fedora Magazine and&nbsp;<a href="https://blogs.gnome.org/uraeus/2024/03/28/fedora-workstation-40-what-are-we-working-on/" target="_blank" rel="noreferrer noopener">Fedora Workstation 40 – what are we working on</a>&nbsp;from Christian F.K. Schaller.</p>
729.  
730.  
731.  
732. <h3 class="wp-block-heading" id="no-longer-overlay-langpacks-by-default">No longer overlay language packages (langpack) by default<a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#no-longer-overlay-langpacks-by-default"></a></h3>
733.  
734.  
735.  
736. <p>GNOME Software will no longer overlay the langpack packages for your locale on the first update. This should make updates much faster as they won’t need to overlay packages anymore (unless you explicitly decide to overlay some packages).</p>
737.  
738.  
739.  
740. <p>If you are updating from a previous release, you will have to remove this overlayed package manually. For example:</p>
741.  
742.  
743.  
744. <p>1. Find the overlayed package using rpm-ostree status:</p>
745.  
746.  
747.  
748. <pre class="wp-block-preformatted">$ rpm-ostree status<br />State: idle<br />Deployments:<br />● fedora:fedora/40/x86_64/silverblue<br />                  Version: 40.20240410.1 (2024-04-10T03:43:23Z)<br />                   Commit: 2428fdbec13787633b3bcd79d4f002ab48582bae8c6a473ca357a1ad43573a94<br />             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C<br />          LayeredPackages: langpacks-fr<br /><br />  fedora:fedora/40/x86_64/silverblue<br />                  Version: 40.20240402.0 (2024-04-02T00:39:43Z)<br />                   Commit: 634c8097165e6aab2baeaca6ae6d1ea2a7f11fba9f4955297bcf0fc2507047be<br />             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C<br />          LayeredPackages: langpacks-fr</pre>
749.  
750.  
751.  
752. <p>2. Remove the overlayed package and reboot:</p>
753.  
754.  
755.  
756. <pre class="wp-block-preformatted">$ rpm-ostree uninstall langpacks-fr<br />...</pre>
757.  
758.  
759.  
760. <p>Note that this will remove the dictionaries for the corresponding language from your system and thus for applications included in the image.</p>
761.  
762.  
763.  
764. <p>For Flatpaks, the dictionaries are downloaded according to the languages set in the Flatpak config. If you have set your preferred languages in GNOME Settings, this configuration should have been set already. For example:</p>
765.  
766.  
767.  
768. <pre class="wp-block-preformatted"># Get the current config<br />$ flatpak config --list<br />languages: en;fr;de (default: en)<br />extra-languages: *unset*<br /><br /># Set the languages to use<br />$ flatpak config --set languages "en;fr"</pre>
769.  
770.  
771.  
772. <p>See the <a href="https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-config" target="_blank" rel="noreferrer noopener">flatpak-config</a> documentation for more details.</p>
773.  
774.  
775.  
776. <p>Also note that with this change the translated man pages for system commands will also be removed. To get the man pages back, you can install them in a container using toolbox for example:</p>
777.  
778.  
779.  
780. <pre class="wp-block-preformatted">$ toolbox create<br />$ toolbox enter<br />$ sudo dnf install man-pages-fr</pre>
781.  
782.  
783.  
784. <p>See:&nbsp;<a href="https://gitlab.com/fedora/ostree/sig/-/issues/14" target="_blank" rel="noreferrer noopener">atomic-desktops-sig#14</a>.</p>
785.  
786.  
787.  
788. <h2 class="wp-block-heading">What’s new in Kinoite<a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#whats-new-in-kinoite"></a><br /><a href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#whats-new-in-kinoite"></a></h2>
789.  
790.  
791.  
792. <h3 class="wp-block-heading">KDE Plasma 6<a class="header-link" title="Permalink" style="position: relative;left: 0.5em;font-size: 0.8em" href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#kde-plasma-6"></a><a class="header-link" title="Permalink" style="position: relative;left: 0.5em;font-size: 0.8em" href="https://tim.siosm.fr/blog/wip/fedora-atomic-desktops-40.html#kde-plasma-6"></a></h3>
793.  
794.  
795.  
796. <p>Fedora Kinoite ships with&nbsp;<a href="https://kde.org/announcements/megarelease/6/" target="_blank" rel="noreferrer noopener">Plasma 6, Frameworks 6 and Gear 24.02</a>&nbsp;(<a href="https://fedoraproject.org/wiki/Changes/KDE_Plasma_6">Fedora Change</a>). See also&nbsp;<a href="https://fedoramagazine.org/whats-new-in-fedora-kde-40/" target="_blank" rel="noreferrer noopener">What’s New in Fedora KDE 40?</a>&nbsp;on the Fedora Magazine.</p>
797.  
798.  
799.  
800. <h3 class="wp-block-heading" id="wayland-only">Wayland only</h3>
801.  
802.  
803.  
804. <p>Fedora Kinoite is now Wayland only. Legacy X11 applications will run using XWayland. See&nbsp;<a href="https://fedoraproject.org/wiki/KDE/X11_Unsupported" target="_blank" rel="noreferrer noopener">Fedora 40: X11 is now unsupported</a>.</p>
805.  
806.  
807.  
808. <p>If you have an NVIDIA GPU and encounter issues, I recommend looking at Universal Blue images (see below), waiting for an upcoming NVIDIA driver update that will hopefully improve Wayland support or trying out the updated Nouveau / NVK stack for supported cards.</p>
809.  
810.  
811.  
812. <h3 class="wp-block-heading" id="kde-apps-as-fedora-flatpaks">KDE Apps as Fedora Flatpaks</h3>
813.  
814.  
815.  
816. <p>A subset of KDE Apps are now installed by default as Fedora Flatpaks by Ananconda for new installations. The Flatpaks are&nbsp;<a href="https://gitlab.com/fedora/ostree/sig/-/issues/8" target="_blank" rel="noreferrer noopener">not installed on updates</a>&nbsp;but you can install them from the Fedora Flatpak remote or from Flathub.</p>
817.  
818.  
819.  
820. <h3 class="wp-block-heading" id="kde-flatpak-on-flathub">KDE Flatpaks on Flathub</h3>
821.  
822.  
823.  
824. <p>Most KDE Apps are directly published and maintained on Flathub by the KDE community and we have mostly completed the transition to the Qt 6.6 and KDE Framework 6 Runtime.</p>
825.  
826.  
827.  
828. <p>You can track the progress for the remaining apps in&nbsp;<a href="https://invent.kde.org/teams/flathub/issues/-/issues/26" target="_blank" rel="noreferrer noopener">kde/teams/flathub#26</a>.</p>
829.  
830.  
831.  
832. <h2 class="wp-block-heading" id="whats-new-in-sway-atomic">What’s new in Sway Atomic</h2>
833.  
834.  
835.  
836. <p>Fedora Sway Atmoic comes with the latest&nbsp;<a href="https://github.com/swaywm/sway/releases/tag/1.9" target="_blank" rel="noreferrer noopener">1.9 Sway release</a>.</p>
837.  
838.  
839.  
840. <h2 class="wp-block-heading" id="whats-new-in-budgie-atomic">What’s new in Budgie Atomic</h2>
841.  
842.  
843.  
844. <p>Fedora Budgie Atomic ships with the latest release of the&nbsp;<a href="https://buddiesofbudgie.org/blog/budgie-10-9-released" target="_blank" rel="noreferrer noopener">Budgie Desktop 10.9</a>&nbsp;“release series”. Budgie 10.9 features some initial porting work to&nbsp;<kbd>libxfce4windowing</kbd>&nbsp;as it progresses towards its move to Wayland and redesigns its Bluetooth applet with new direct (dis-)connect functionality.</p>
845.  
846.  
847.  
848. <p>Additionally, Fedora Budgie Atomic ships with the latest Budgie Control Center and takes into use budgie-session. As Buddies of Budgie officially supports Fedora, Budgie Desktop has also received numerous backported bug fixes to provide Fedora users an even better experience.</p>
849.  
850.  
851.  
852. <p>You can learn more about the latest happenings in Budgie on the&nbsp;<a href="https://buddiesofbudgie.org/blog" target="_blank" rel="noreferrer noopener">Buddies of Budgie blog</a>.</p>
853.  
854.  
855.  
856. <h2 class="wp-block-heading" id="whats-next">What’s next</h2>
857.  
858.  
859.  
860. <p>Unfortunately, this section will be short this time, as there has not been much progress on our future plans&nbsp;<a href="https://tim.siosm.fr/blog/2023/11/22/fedora-atomic-desktops-39/#whats-next" target="_blank" rel="noreferrer noopener">since the last time</a>.</p>
861.  
862.  
863.  
864. <p>We will provide an updated article when more information becomes available.</p>
865.  
866.  
867.  
868. <h3 class="wp-block-heading" id="teaser-for-improved-update-support-in-discover-for-kinoite">Teaser for improved update support in Discover for Kinoite</h3>
869.  
870.  
871.  
872. <figure class="wp-block-image size-large"><a href="https://tim.siosm.fr/assets/images/kinoite-discover-update-size.png"><img decoding="async" src="https://tim.siosm.fr/assets/images/kinoite-discover-update-size.png" alt=""/></a></figure>
873.  
874.  
875.  
876. <h2 class="wp-block-heading" id="universal-blue-bluefin-bazzite-and-aurora">Universal Blue, Bluefin, Bazzite and Aurora</h2>
877.  
878.  
879.  
880. <p>Our friends in the Universal Blue, Bluefin and Bazzite projects also released updates for their images.</p>
881.  
882.  
883.  
884. <p>Universal Blue is now considered&nbsp;<a href="https://universal-blue.discourse.group/t/universal-blue-is-now-generally-available/1233" target="_blank" rel="noreferrer noopener">Generally Available</a>&nbsp;alongside&nbsp;<a href="https://universal-blue.discourse.group/t/bluefin-is-now-generally-available/1234" target="_blank" rel="noreferrer noopener">Bluefin</a>.</p>
885.  
886.  
887.  
888. <p>For all your gaming needs,&nbsp;<a href="https://universal-blue.discourse.group/t/announcing-bazzite-3-0/1218" target="_blank" rel="noreferrer noopener">Bazzite reached version 3.0</a>, rebasing on our fresh Fedora 40 images.</p>
889.  
890.  
891.  
892. <p>They are also introducing&nbsp;<a href="https://getaurora.dev/" target="_blank" rel="noreferrer noopener">Aurora</a>, a KDE Plasma and Kinoite based alternative to Bluefin. See the&nbsp;<a href="https://universal-blue.discourse.group/t/introduction-to-aurora/1235" target="_blank" rel="noreferrer noopener">Introduction to Aurora</a>&nbsp;post for all the details.</p>
893.  
894.  
895.  
896. <h2 class="wp-block-heading" id="where-to-reach-us">Where to reach us</h2>
897.  
898.  
899.  
900. <p>We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users.</p>
901.  
902.  
903.  
904. <ul>
905. <li>Atomic Desktops SIG:&nbsp;<a href="https://fedoraproject.org/wiki/SIGs/AtomicDesktops" target="_blank" rel="noreferrer noopener">Wiki page</a>, <a href="https://gitlab.com/fedora/ostree/sig/-/issues" target="_blank" rel="noreferrer noopener">Issue tracker</a>,&nbsp;<a href="https://matrix.to/#/#atomic-desktops:fedoraproject.org" target="_blank" rel="noreferrer noopener">#atomic-desktops:fedoraproject.org</a></li>
906.  
907.  
908.  
909. <li>Silverblue:&nbsp;<a href="https://docs.fedoraproject.org/en-US/workstation-working-group/" target="_blank" rel="noreferrer noopener">Workstation Working Group</a>,&nbsp;<a href="https://matrix.to/#/#silverblue:fedoraproject.org" target="_blank" rel="noreferrer noopener">#silverblue:fedoraproject.org</a></li>
910.  
911.  
912.  
913. <li>Kinoite:&nbsp;<a href="https://fedoraproject.org/wiki/SIGs/KDE" target="_blank" rel="noreferrer noopener">KDE SIG</a>,&nbsp;<a href="https://matrix.to/#/#kinoite:fedoraproject.org" target="_blank" rel="noreferrer noopener">#kinoite:fedoraproject.org</a></li>
914.  
915.  
916.  
917. <li>Sway Atomic:&nbsp;<a href="https://fedoraproject.org/wiki/SIGs/Sway" target="_blank" rel="noreferrer noopener">Sway SIG</a>,&nbsp;<a href="https://matrix.to/#/#sway:fedoraproject.org" target="_blank" rel="noreferrer noopener">#sway:fedoraproject.org</a></li>
918.  
919.  
920.  
921. <li>Budgie Atomic:&nbsp;<a href="https://fedoraproject.org/wiki/SIGs/Budgie" target="_blank" rel="noreferrer noopener">Budgie SIG</a>,&nbsp;<a href="https://matrix.to/#/#budgie:fedoraproject.org" target="_blank" rel="noreferrer noopener">#budgie:fedoraproject.org</a></li>
922. </ul>
923. ]]></content:encoded>
925. <wfw:commentRss>https://fedoramagazine.org/whats-new-for-fedora-atomic-desktops-in-fedora-40/feed/</wfw:commentRss>
926. <slash:comments>5</slash:comments>
929. <post-id xmlns="com-wordpress:feed-additions:1">40306</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/04/whats_new_Atomic_Fedora_40-300x127.jpg" length="9367" type="image/jpg" /> </item>
930. <item>
931. <title>How to rebase to Fedora Linux 40 on Silverblue</title>
932. <link>https://fedoramagazine.org/how-to-rebase-to-fedora-linux-40-on-silverblue/</link>
933. <comments>https://fedoramagazine.org/how-to-rebase-to-fedora-linux-40-on-silverblue/#comments</comments>
935. <dc:creator><![CDATA[Michal Konečný]]></dc:creator>
936. <pubDate>Wed, 24 Apr 2024 08:00:00 +0000</pubDate>
937. <category><![CDATA[New in Fedora]]></category>
938. <category><![CDATA[Using Software]]></category>
939. <category><![CDATA[fedora 40]]></category>
940. <category><![CDATA[OStree]]></category>
941. <category><![CDATA[rebase]]></category>
942. <guid isPermaLink="false">https://fedoramagazine.org/?p=40186</guid>
943.  
944. <description><![CDATA[Fedora Silverblue is&#160;an operating system for your desktop built&#160;on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers&#160;numerous advantages&#160;such as being able to roll back in case of any problems. If you want to update or rebase to Fedora Linux 40 on your Fedora Silverblue system, this article tells you how. [&#8230;]]]></description>
945. <content:encoded><![CDATA[
946. <p>Fedora Silverblue is&nbsp;<a href="https://docs.fedoraproject.org/en-US/fedora-silverblue/" target="_blank" rel="noreferrer noopener">an operating system for your desktop built&nbsp;on Fedora Linux</a>. It’s excellent for daily use, development, and container-based workflows. It offers&nbsp;<a href="https://fedoramagazine.org/give-fedora-silverblue-a-test-drive/" target="_blank" rel="noreferrer noopener">numerous advantages</a>&nbsp;such as being able to roll back in case of any problems. If you want to update or rebase to Fedora Linux 40 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.</p>
947.  
948.  
949.  
950. <span id="more-40186"></span>
951.  
952.  
953.  
954. <h2 class="wp-block-heading">Update your existing system</h2>
955.  
956.  
957.  
958. <p>Prior to actually doing the rebase to Fedora Linux 40, you should apply any pending updates. Enter the following in the terminal:</p>
959.  
960.  
961.  
962. <pre class="wp-block-preformatted">$ rpm-ostree update</pre>
963.  
964.  
965.  
966. <p>or install updates through GNOME Software and reboot.</p>
967.  
968.  
969.  
970. <h2 class="wp-block-heading">Note</h2>
971.  
972.  
973.  
974. <p>rpm-ostree is the underlying atomic technology that all the <a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">Fedora Atomic Desktops</a> use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.</p>
975.  
976.  
977.  
978. <h2 class="wp-block-heading">Rebasing using GNOME Software</h2>
979.  
980.  
981.  
982. <p>GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.</p>
983.  
984.  
985.  
986. <figure class="wp-block-image size-full is-style-default"><a href="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46.png"><img fetchpriority="high" decoding="async" width="1199" height="803" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46.png" alt="GNOME_Software_download_screenshot" class="wp-image-40187" srcset="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46.png 1199w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46-300x201.png 300w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46-1024x686.png 1024w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46-768x514.png 768w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46-816x546.png 816w" sizes="(max-width: 1199px) 100vw, 1199px" /></a></figure>
987.  
988.  
989.  
990. <p>First thing to do is download the new image, so select the&nbsp;<em>Download</em>&nbsp;button. This will take some time. When it is done you will see that the update is ready to install.</p>
991.  
992.  
993.  
994. <figure class="wp-block-image size-full"><a href="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17.png"><img decoding="async" width="1199" height="803" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17.png" alt="GNOME_Software_update_screenshot" class="wp-image-40188" srcset="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17.png 1199w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17-300x201.png 300w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17-1024x686.png 1024w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17-768x514.png 768w, https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17-816x546.png 816w" sizes="(max-width: 1199px) 100vw, 1199px" /></a></figure>
995.  
996.  
997.  
998. <p>Select the&nbsp;<em>Restart &amp; Upgrade</em>&nbsp;button. This step will take only a few moments and the computer will  restart when the update is completed. After the restart you will end up in a new and shiny release of Fedora Linux 40. Easy, isn’t it?</p>
999.  
1000.  
1001.  
1002. <h2 class="wp-block-heading">Rebasing using terminal</h2>
1003.  
1004.  
1005.  
1006. <p>If you prefer to do everything in a terminal, then this part of the guide is for you.</p>
1007.  
1008.  
1009.  
1010. <p>Rebasing to Fedora Linux 40 using the terminal is easy. First, check if the 40 branch is available:</p>
1011.  
1012.  
1013.  
1014. <pre class="wp-block-preformatted">$ ostree remote refs fedora</pre>
1015.  
1016.  
1017.  
1018. <p>You should see the following in the output:</p>
1019.  
1020.  
1021.  
1022. <pre class="wp-block-preformatted">fedora:fedora/40/x86_64/silverblue</pre>
1023.  
1024.  
1025.  
1026. <p>If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:</p>
1027.  
1028.  
1029.  
1030. <pre class="wp-block-preformatted"># 0 is entry position in rpm-ostree status
1031. $ sudo ostree admin pin 0</pre>
1032.  
1033.  
1034.  
1035. <p>To remove the pinned deployment use the following command:</p>
1036.  
1037.  
1038.  
1039. <pre class="wp-block-preformatted"># 2 is entry position in rpm-ostree status
1040. $ sudo ostree admin pin --unpin 2</pre>
1041.  
1042.  
1043.  
1044. <p>Next, rebase your system to the Fedora Linux 40 branch.</p>
1045.  
1046.  
1047.  
1048. <pre class="wp-block-preformatted">$ rpm-ostree rebase fedora:fedora/40/x86_64/silverblue</pre>
1049.  
1050.  
1051.  
1052. <p>Finally, the last thing to do is restart your computer and boot to Fedora Linux 40.</p>
1053.  
1054.  
1055.  
1056. <h2 class="wp-block-heading">How to roll back</h2>
1057.  
1058.  
1059.  
1060. <p>If anything bad happens (for instance, if you can’t boot to Fedora Linux 40 at all) it’s easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 40 and your system will start in that previous version rather than Fedora Linux 40. If you don’t see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:</p>
1061.  
1062.  
1063.  
1064. <pre class="wp-block-preformatted">$ rpm-ostree rollback</pre>
1065.  
1066.  
1067.  
1068. <p>That’s it. Now you know how to rebase Fedora Silverblue to Fedora Linux 40 and roll back. So why not do it today?</p>
1069.  
1070.  
1071.  
1072. <h2 class="wp-block-heading">FAQ</h2>
1073.  
1074.  
1075.  
1076. <p>Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.</p>
1077.  
1078.  
1079.  
1080. <p><strong>Question: Can I skip versions during rebase of Fedora? For example from Fedora 38 Silverblue to Fedora 40 Silverblue?</strong></p>
1081.  
1082.  
1083.  
1084. <p>Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (38-&gt;39 for example) to avoid unnecessary errors.</p>
1085.  
1086.  
1087.  
1088. <p><strong>Question: I have <a href="https://rpmfusion.org/" target="_blank" rel="noreferrer noopener">rpm-fusion</a> layered and I get errors during rebase. How should I do the rebase?</strong></p>
1089.  
1090.  
1091.  
1092. <p>Answer: If you have <a href="https://rpmfusion.org/" target="_blank" rel="noreferrer noopener">rpm-fusion</a> layered on your Silverblue installation, you should do the following before rebase:</p>
1093.  
1094.  
1095.  
1096. <pre class="wp-block-preformatted">$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release</pre>
1097.  
1098.  
1099.  
1100. <p>After doing this you can follow the guide in this blog post.</p>
1101.  
1102.  
1103.  
1104. <p><strong>Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),&#8230;?</strong></p>
1105.  
1106.  
1107.  
1108. <p>Yes, you can follow the&nbsp;<em>Rebasing using the terminal</em>&nbsp;part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use <kbd>fedora:fedora/40/x86_64/kinoite</kbd></p>
1109.  
1110.  
1111.  
1112. <p></p>
1113. ]]></content:encoded>
1115. <wfw:commentRss>https://fedoramagazine.org/how-to-rebase-to-fedora-linux-40-on-silverblue/feed/</wfw:commentRss>
1116. <slash:comments>10</slash:comments>
1119. <post-id xmlns="com-wordpress:feed-additions:1">40186</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2021/04/silverblue-rebase-300x127.jpg" length="6958" type="image/jpg" /> </item>
1120. <item>
1121. <title>OMG! We’re at forty! (Announcing the release of Fedora Linux 40)</title>
1122. <link>https://fedoramagazine.org/announcing-fedora-linux-40/</link>
1123. <comments>https://fedoramagazine.org/announcing-fedora-linux-40/#comments</comments>
1125. <dc:creator><![CDATA[Matthew Miller]]></dc:creator>
1126. <pubDate>Tue, 23 Apr 2024 14:00:00 +0000</pubDate>
1127. <category><![CDATA[Fedora Project community]]></category>
1128. <guid isPermaLink="false">https://fedoramagazine.org/?p=40232</guid>
1129.  
1130. <description><![CDATA[Oh, wow. This feels like a big number! I’m proud to announce the 40th release of Fedora Linux, a community-built and community-maintained operating system that belongs to all of us. I’m also happy to note that we’re back on track with an on-time release. Thank you to all Fedora contributors who made that possible, and [&#8230;]]]></description>
1131. <content:encoded><![CDATA[
1132. <p>Oh, wow. This feels like a big number! I’m proud to announce the 40th release of Fedora Linux, a community-built and community-maintained operating system that belongs to <em>all</em> of us. I’m also happy to note that we’re back on track with an on-time release. Thank you to all Fedora contributors who made that possible, and who have, yet again, made this our best one ever.</p>
1133.  
1134.  
1135.  
1136. <span id="more-40232"></span>
1137.  
1138.  
1139.  
1140. <p>This is also a <em>personally</em> exciting number for me, because this marks the <em>20th</em> release for which I’ve served as Fedora Project Leader. We’ve gone through a lot in this last decade, and I’m incredibly happy to see our community thrive and grow. In addition to many long-familiar names and faces, it’s exciting to see a new generation with new energy and ideas. In some cases, this is <em>literally </em>a new generation, as many of you have grown up with Fedora. But at whatever age, I&#8217;m proud we&#8217;ve built such a welcoming and friendly community, and that we continue to work at improving our inclusiveness, diversity, and accessibility.</p>
1141.  
1142.  
1143.  
1144. <p>But anyway! Enough of that. Time to see what we&#8217;ve got for you in Fedora Linux 40! If you have a system already, <a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/" target="_blank" rel="noreferrer noopener">Upgrading Fedora to a New Release</a> is easy. If you’re new, or just curious, head to <a href="https://fedoraproject.org" target="_blank" rel="noreferrer noopener">Get Fedora</a> for installation options.</p>
1145.  
1146.  
1147.  
1148. <h2 class="wp-block-heading">Desktop news</h2>
1149.  
1150.  
1151.  
1152. <p>Fedora Workstation Edition features the GNOME desktop environment, now updated to version 46. Check out <a href="https://fedoramagazine.org/whats-new-fedora-workstation-40" target="_blank" rel="noreferrer noopener">What&#8217;s New in Fedora Workstation 40?</a> for the highlights!</p>
1153.  
1154.  
1155.  
1156. <p>The KDE Spin now includes KDE Plasma 6, and runs with Wayland out of the box. Read more about that and other KDE Spin updates at <a href="https://fedoramagazine.org/whats-new-in-fedora-kde-40">What&#8217;s New in Fedora KDE 40?</a></p>
1157.  
1158.  
1159.  
1160. <p>We’re also officially reviving the “Fedora Atomic Desktop” brand for all of our variants which use ostree or image-based provisioning. Our technology isn’t really “immutable”, so this provides a better grouping. Read more about this at <a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">Introducing Fedora Atomic Desktops</a> — but in short, Fedora Silverblue and Fedora Kinoite will remain, while the other desktop&nbsp; variants will become Fedora Sway Atomic and Fedora Budgie Atomic.</p>
1161.  
1162.  
1163.  
1164. <h2 class="wp-block-heading">Tools for AI development</h2>
1165.  
1166.  
1167.  
1168. <p>Fedora Linux 40 ships with our first-ever PyTorch package. PyTorch is a popular framework for deep learning, and it can be difficult to reliably install with the right versions of drivers and libraries and so on. The current package only supports running on the CPU, without GPU or NPU acceleration, but this is just the first step. Our aim is to produce a complete stack with PyTorch and other popular tools ready to use on a wide variety of hardware out-of-the-box.</p>
1169.  
1170.  
1171.  
1172. <p>We’re also shipping with ROCm 6 — open-source software that provides acceleration support for AMD graphics cards. We plan to have that enabled for PyTorch in a future release.</p>
1173.  
1174.  
1175.  
1176. <h2 class="wp-block-heading">Updates all around!</h2>
1177.  
1178.  
1179.  
1180. <p>As usual, we’ve rebuilt everything in the distribution using updated compilers and libraries (and, of course, those updated tools are ready for developers to use). These updates bring bugfixes, security improvements, and performance gains.</p>
1181.  
1182.  
1183.  
1184. <p>And, of course, hundreds of Fedora packagers and testers have worked to integrate the latest versions of open source software from thousands of upstream projects. Those projects, in turn, are made by an uncountable number of developers and contributors working on marketing, design, documentation, code, quality, translations, communications, events, governance, infrastructure, security, and so much more. Thank you again to everyone who makes Fedora amazing, and to everyone whose work has built this whole universe of free and open source software.</p>
1185.  
1186.  
1187.  
1188. <h2 class="wp-block-heading">Speaking of updates&#8230;</h2>
1189.  
1190.  
1191.  
1192. <p>There are several important release-day bugfix and security updates available today as well. If you upgrade from an earlier Fedora Linux release, you&#8217;ll get them as part of that. For new installations, please make sure to check for and apply updates as soon as possible.</p>
1193.  
1194.  
1195.  
1196. <h2 class="wp-block-heading">In the unlikely event of a problem…</h2>
1197.  
1198.  
1199.  
1200. <p>If you run into a problem, visit our<a href="https://ask.fedoraproject.org/" target="_blank" rel="noreferrer noopener"> Ask Fedora</a> user support forum. This includes a category for<a href="https://discussion.fedoraproject.org/tags/c/ask/common-issues/82/none/f40" target="_blank" rel="noreferrer noopener"> common issues</a>.&nbsp;</p>
1201.  
1202.  
1203.  
1204. <h2 class="wp-block-heading">Or if you just want to say “hello”…</h2>
1205.  
1206.  
1207.  
1208. <p>Drop by our<a href="https://discussion.fedoraproject.org/c/fun/8" target="_blank" rel="noreferrer noopener"> “virtual watercooler” on Fedora Discussion</a> and join a conversation, share something interesting, and introduce yourself.</p>
1209.  
1210.  
1211.  
1212. <p>Also, remember that our annual contributor conference, <a href="https://flocktofedora.org/" target="_blank" rel="noreferrer noopener">Flock To Fedora</a>, is coming up! It’ll be in Rochester, New York this August. The <a href="https://communityblog.fedoraproject.org/flock-2024-cfp-until-april-21st/" target="_blank" rel="noreferrer noopener">call for session proposals</a> is still open, if you have something you’d like to share or work on. If you’re already a Fedora contributor, or are interested in being one, or think you might be, we’d love to see you there!</p>
1213. ]]></content:encoded>
1215. <wfw:commentRss>https://fedoramagazine.org/announcing-fedora-linux-40/feed/</wfw:commentRss>
1216. <slash:comments>78</slash:comments>
1219. <post-id xmlns="com-wordpress:feed-additions:1">40232</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Linux_40_release-300x127.jpg" length="4886" type="image/jpg" /> </item>
1220. <item>
1221. <title>Slimbook Fedora 2: New Ultrabooks for Fedora Linux 40</title>
1222. <link>https://fedoramagazine.org/slimbook-fedora-2-new-ultrabooks-for-fedora-linux-40/</link>
1223. <comments>https://fedoramagazine.org/slimbook-fedora-2-new-ultrabooks-for-fedora-linux-40/#comments</comments>
1225. <dc:creator><![CDATA[Joseph Gayoso]]></dc:creator>
1226. <pubDate>Tue, 23 Apr 2024 13:58:00 +0000</pubDate>
1227. <category><![CDATA[New in Fedora]]></category>
1228. <category><![CDATA[Slimbook]]></category>
1229. <guid isPermaLink="false">https://fedoramagazine.org/?p=40175</guid>
1230.  
1231. <description><![CDATA[Check out the new Fedora Slimbook 2 Ultrabook with Fedora Linux 40 installed! Fourteen inch and sixteen inch versions are available.]]></description>
1232. <content:encoded><![CDATA[
1233. <p>The response from the Fedora community to the Fedora Slimbook 16” and 14” has been great! More and more people are noticing the quality of these laptops. We’ve even had a demo unit at events like <strong>FOSDEM</strong> and <strong>SCaLE</strong> for community members to play with.</p>
1234.  
1235.  
1236.  
1237. <p>To build on that excitement, Slimbook and the Fedora Project are announcing <a href="https://fedora.slimbook.com/" target="_blank" rel="noreferrer noopener"><strong>Slimbook Fedora 2</strong></a>!</p>
1238.  
1239.  
1240.  
1241. <span id="more-40175"></span>
1242.  
1243.  
1244.  
1245. <h2 class="wp-block-heading">Slimbook Fedora 2</h2>
1246.  
1247.  
1248.  
1249. <p>The Slimbook Fedora 2 comes in the 14” and 16” models and brings with it fantastic new options.</p>
1250.  
1251.  
1252.  
1253. <ul>
1254. <li>Silver is popular, but how about a <strong>smooth black Magnesium chassis</strong>?</li>
1255.  
1256.  
1257.  
1258. <li>For those who need it, you now have the option of a <strong>US ANSI keyboard layout</strong> so you can work without skipping a beat!</li>
1259.  
1260.  
1261.  
1262. <li>CPU is being upgraded to <strong>Intel’s 13th Gen i7</strong> processor</li>
1263.  
1264.  
1265.  
1266. <li>Take your work to the next level with the <strong>Nvidia RTX 4000 series</strong> graphics card in the 16” model</li>
1267. </ul>
1268.  
1269.  
1270.  
1271. <p>Of course we can’t forget that the Slimbook Fedora 2 will also come with the Fedora logo engraved on the lid, as well as on the super key. <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
1272.  
1273.  
1274.  
1275. <p>This hardware update comes with a software upgrade courtesy of Fedora&#8217;s latest release, <strong>Fedora Workstation 40</strong>. Featuring<strong> GNOME 46</strong> and numerous other enhancements, Slimbook Fedora 2 continues to be a great travel companion. Fedora Linux 40 also comes with the latest <strong>Nouveau</strong> drivers to give you a much better out of the box experience with the Nvidia graphics card in the 16” model.</p>
1276.  
1277.  
1278.  
1279. <p>Slimbook is dedicated to supporting open source initiatives. As part of that, 3% of the proceeds from each Slimbook Fedora unit sold will continue to be donated to the <strong>GNOME Foundation</strong>.</p>
1280.  
1281.  
1282.  
1283. <p>Besides that there is also the Fedora contributor discount which gives you an additional €100 off! If you’re a contributor to the Fedora Project you can find more info on how to get this discount from<a href="https://communityblog.fedoraproject.org/fedora-slimbook-contributor-discount/"> this Community Blog post</a>.</p>
1284.  
1285.  
1286.  
1287. <p>Additionally, Slimbook offers a €150 discount for everyone on last year&#8217;s model. You can purchase the previous model with a discount through this link: <a href="https://fedora.slimbook.com" target="_blank" rel="noreferrer noopener">https://fedora.slimbook.com</a>.</p>
1288.  
1289.  
1290.  
1291. <figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex">
1292. <figure class="wp-block-image size-large"><img decoding="async" width="1024" height="768" data-id="40176" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-1024x768.jpg" alt="" class="wp-image-40176" srcset="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-1024x768.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-300x225.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-768x576.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-1536x1152.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-816x612.jpg 816w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back.jpg 2000w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
1293.  
1294.  
1295.  
1296. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="819" data-id="40177" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front-1024x819.jpg" alt="" class="wp-image-40177" srcset="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front-1024x819.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front-300x240.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front-768x614.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front-816x653.jpg 816w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front.jpg 1500w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
1297.  
1298.  
1299.  
1300. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="819" data-id="40178" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-1024x819.jpg" alt="" class="wp-image-40178" srcset="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-1024x819.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-300x240.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-768x614.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-1536x1229.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-2048x1638.jpg 2048w, https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-816x653.jpg 816w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
1301.  
1302.  
1303.  
1304. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="682" data-id="40179" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-1024x682.png" alt="" class="wp-image-40179" srcset="https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-1024x682.png 1024w, https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-300x200.png 300w, https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-768x512.png 768w, https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-1536x1024.png 1536w, https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-816x544.png 816w, https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black.png 2000w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
1305. </figure>
1306.  
1307.  
1308.  
1309. <p>More details below:</p>
1310.  
1311.  
1312.  
1313. <h4 class="wp-block-heading">Slimbook Fedora 2, 16” Model</h4>
1314.  
1315.  
1316.  
1317. <ul>
1318. <li>Intel® Core<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" alt="™" class="wp-smiley" style="height: 1em; max-height: 1em;" /> i7-13700H Processor</li>
1319.  
1320.  
1321.  
1322. <li>NVIDIA GeForce RTX<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" alt="™" class="wp-smiley" style="height: 1em; max-height: 1em;" /> 4060 GPU</li>
1323.  
1324.  
1325.  
1326. <li>Sleek Color Options: Silver and Black (magnesium chassis)</li>
1327.  
1328.  
1329.  
1330. <li>16-inch 16:10, 100% sRGB, 90Hz Display (2560 x 1600 Resolution)</li>
1331.  
1332.  
1333.  
1334. <li>Versatile Keyboard Options: ISO and ANSI (Available in almost any language)</li>
1335.  
1336.  
1337.  
1338. <li>Up to 64 GB SO-DIMM DDR5 RAM (removable)</li>
1339.  
1340.  
1341.  
1342. <li>Up to 8 TB M.2 SSD NVMe Gen 4.0 (removable)</li>
1343.  
1344.  
1345.  
1346. <li>Thunderbolt 4 &amp; USB-C 3.2 Gen2 10Gbps</li>
1347.  
1348.  
1349.  
1350. <li>82 Wh Battery</li>
1351.  
1352.  
1353.  
1354. <li>Lightweight Design: 1.6 kg (3.5 lbs)<br /></li>
1355. </ul>
1356.  
1357.  
1358.  
1359. <h4 class="wp-block-heading">Slimbook Fedora 2, 14” Model</h4>
1360.  
1361.  
1362.  
1363. <ul>
1364. <li>Intel® Core<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" alt="™" class="wp-smiley" style="height: 1em; max-height: 1em;" /> i7-13700H Processor</li>
1365.  
1366.  
1367.  
1368. <li>Sleek Color Options: Silver and Black</li>
1369.  
1370.  
1371.  
1372. <li>14-inch 16:10, 100% sRGB, 90Hz Display (2880 x 1800 Resolution)</li>
1373.  
1374.  
1375.  
1376. <li>Versatile Keyboard Options: ISO and ANSI</li>
1377.  
1378.  
1379.  
1380. <li>Up to 64 GB SO-DIMM DDR5 RAM (removable)</li>
1381.  
1382.  
1383.  
1384. <li>Up to 8 TB M.2 SSD NVMe Gen 4.0 (removable)</li>
1385.  
1386.  
1387.  
1388. <li>Thunderbolt 4 &amp; USB-C 3.2 Gen2 10Gbps</li>
1389.  
1390.  
1391.  
1392. <li>99 Wh Battery</li>
1393.  
1394.  
1395.  
1396. <li>Lightweight Design: 1.3 kg (2.8 lbs)</li>
1397. </ul>
1398.  
1399.  
1400.  
1401. <p>Check out both new Slimbook Fedora 2 models at <a href="https://fedora.slimbook.com/">https://fedora.slim</a><a href="https://fedora.slimbook.com/" target="_blank" rel="noreferrer noopener">b</a><a href="https://fedora.slimbook.com/">ook.com/</a>!&nbsp;</p>
1402.  
1403.  
1404.  
1405. <p><strong>Additional Resources</strong></p>
1406.  
1407.  
1408.  
1409. <ul>
1410. <li>Learn more about<a href="https://fedora.slimbook.es/" target="_blank" rel="noreferrer noopener"> Slimbook Fedora</a></li>
1411.  
1412.  
1413.  
1414. <li>Follow Slimbook on<a href="https://linuxrocks.online/@slimbook" target="_blank" rel="noreferrer noopener"> Mastodon</a></li>
1415.  
1416.  
1417.  
1418. <li>Follow Slimbook on<a href="https://x.com/slimbook" target="_blank" rel="noreferrer noopener"> Twitter</a></li>
1419.  
1420.  
1421.  
1422. <li>Follow Slimbook on<a href="https://www.instagram.com/slimbook/" target="_blank" rel="noreferrer noopener"> Instagram</a></li>
1423.  
1424.  
1425.  
1426. <li>Follow Slimbook on<a href="https://www.facebook.com/slimbook.es" target="_blank" rel="noreferrer noopener"> Facebook</a></li>
1427.  
1428.  
1429.  
1430. <li>Follow Slimbook on<a href="https://www.youtube.com/@slimbook-laptops" target="_blank" rel="noreferrer noopener"> YouTube</a></li>
1431.  
1432.  
1433.  
1434. <li>Learn more about the<a href="https://fedoraproject.org/" target="_blank" rel="noreferrer noopener"> Fedora Project</a></li>
1435.  
1436.  
1437.  
1438. <li>Follow the Fedora Project on<a href="https://fosstodon.org/@fedora" target="_blank" rel="noreferrer noopener"> Mastodon</a></li>
1439.  
1440.  
1441.  
1442. <li>Follow the Fedora Project on<a href="https://twitter.com/fedora?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor" target="_blank" rel="noreferrer noopener"> Twitter</a></li>
1443.  
1444.  
1445.  
1446. <li>Follow the Fedora Project on<a href="https://www.instagram.com/thefedoraproject/" target="_blank" rel="noreferrer noopener"> Instagram</a></li>
1447.  
1448.  
1449.  
1450. <li>Follow the Fedora Project on<a href="https://www.facebook.com/fedoraproject.org/" target="_blank" rel="noreferrer noopener"> Facebook</a></li>
1451.  
1452.  
1453.  
1454. <li>Follow the Fedora Project on <a href="https://www.linkedin.com/company/fedora-project" target="_blank" rel="noreferrer noopener">LinkedIn</a></li>
1455.  
1456.  
1457.  
1458. <li>Subscribe to the Fedora Project on<a href="https://www.youtube.com/@fedora" target="_blank" rel="noreferrer noopener"> YouTube</a></li>
1459. </ul>
1460. ]]></content:encoded>
1462. <wfw:commentRss>https://fedoramagazine.org/slimbook-fedora-2-new-ultrabooks-for-fedora-linux-40/feed/</wfw:commentRss>
1463. <slash:comments>28</slash:comments>
1466. <post-id xmlns="com-wordpress:feed-additions:1">40175</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2024/04/wife-banner-final-300x127.jpg" length="11253" type="image/jpg" /> </item>
1467. </channel>
1468. </rss>
1469.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

1. Download the "valid RSS" banner.

2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

3. Add this HTML to your page (change the image src attribute if necessary):

   <a href="http://www.feedvalidator.org/check.cgi?url=https%3A//fedoramagazine.org/feed/"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//fedoramagazine.org/feed/

Home · About · News · Docs · Terms