Sick Gaming
Fedora - What’s coming in Fedora 29 Anaconda? - Printable Version

+- Sick Gaming (https://www.sickgaming.net)
+-- Forum: Computers (https://www.sickgaming.net/forum-86.html)
+--- Forum: Linux, FreeBSD, and Unix types (https://www.sickgaming.net/forum-88.html)
+--- Thread: Fedora - What’s coming in Fedora 29 Anaconda? (/thread-85404.html)



Fedora - What’s coming in Fedora 29 Anaconda? - xSicKxBot - 06-27-2018

What’s coming in Fedora 29 Anaconda?

<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/whats-coming-in-fedora-29-anaconda.png" width="1024" height="768" title="" alt="" /></div><div><p>Last week, the Fedora Magazine <a href="https://fedoramagazine.org/whats-new-in-the-anaconda-installer-for-fedora-28/">covered the new features and improvements in the Fedora 28 Installer</a>. The Fedora installer team is already hard at work adding new features for Fedora 29. This article covers some of these improvements.</p>
<h3>Progress hub</h3>
<p>The progress hub is mostly empty (on Fedora Workstation) after <a href="https://fedoramagazine.org/whats-new-in-the-anaconda-installer-for-fedora-28/">moving the user creation step to GNOME Initial Setup</a>.</p>
<p><img class="size-full wp-image-21639" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/whats-coming-in-fedora-29-anaconda.png" alt="&quot;&lt;yoastmark" /></p>
<p>Discussions are on going with the Fedora Workstation working group  about re-working the progress hub. Hit the comments with suggestions on how you think this could be improved.</p>
<h3>More Anaconda on DBus</h3>
<p>Fedora 28 was the start of the ultimate goal of modularizing Anaconda. The main idea is to split the code into several modules that will communicate over DBus. Ultimately, this will enable a UI-less installation process.</p>
<p>The goal in Fedora 29 is to move all the storage-related code to the <a href="https://rhinstaller.wordpress.com/2017/12/08/storage-module/">storage module</a>.   Additionally, plans are in place to extend some of the other modules and introduce installation tasks, so you can monitor the installation steps.</p>
<h3>Supporting <i>Fedora Modularity</i></h3>
<p><a href="https://docs.pagure.org/modularity/">Fedora Modularity</a> was introduced in Fedora 28 for the Server variant. This effort is still expanding, adding more modules, features and bug fixes. The Anaconda team is  working on module installation support for Anaconda.</p>
<p>First of all, the new kickstart command, called “module”, is used to enable modules. Additionally, support for installing modules via the <strong>%packages</strong> section in kickstart.</p>
<p>There are already patches for <strong>Anaconda</strong>, <strong>DNF</strong>, <strong>Pykickstart</strong> and <strong>libdnf</strong> that make module installation from kickstart possible.</p>
<h3>Reducing Initial Setup dependencies even more</h3>
<p>Fedora 28 reduced Initial Setup dependencies from Anaconda and the compose tools greatly. Next on the list is to do the same with Blivet.</p>
<p>Currently, the <strong><i>python-blivet</i></strong> package has hard dependencies on many storage handling tools. The current plan is to introduce a <i>blivet-minimal</i> package to just provide the bare minimum of Blivet functionality, such as architecture detection and device-tree based storage modeling. The current <i>python-blivet</i> package will maintain its current dependencies. Consequently, Initial Setup won’t drag in unnecessary dependencies, making packaging more flexible.</p>
<h3>LUKS2 as default</h3>
<p>LUKS2 is the new generation of the Linux storage encryption workhorse, bringing various improvements and new features. Work has started adding support for creating LUKS2-based encrypted storage volumes during installation.</p>
</div>