Software selection. As shown here, the left pane is where you select your choice of desktop environment (Desktop Environment), and the right pane (Add-ons) is where you select specific software or software categories to install. And this is where I think the developers got too cute, too detailed than is necessary.

For example, Firefox by itself is an add-on.
Anaconda Add-on Firefox

But there is a separate add-on category called Graphical Internet. Last time I checked, Firefox is a graphical Internet application and in a running system, you will find it under the Internet menu category.
Anaconda Add-on Internet

There is separate add-on category called Office/Productivity.
Anaconda Add-on Office

But LXDE (Lightweight X11 Desktop Environment) has its own add-on office category. I did not know that LXDE has its own office productivity suite or is this LibreOffice with the look and feel of LXDE?
Anaconda Add-on Office

Related Post:  Fedora 20 GNOME 3 and KDE preview

Same thing with Xfce. And there are many more examples where this granularity in package selection just does not make too much sense.
Anaconda Add-on Office

Disk or storage configuration is where the new Anaconda will take some getting used to. It is not as intuitive as it should be. In the current Anaconda, this aspect is very straightforward to configure, but this new interface does not appear to be so.
Anaconda Disk Setup

This is the manual partitioning interface. I find the current one much simpler and better.
Anaconda Disk Setup

Related Post:  How to install Fedora 21 Workstation Cinnamon on a Btrfs filesystem

Creating a mount point. At this stage, there is no pre-defined mount points to choose from, but this is still a pre-release version. Could change when stable rolls out.
Anaconda Set Mount Point

This is the partition-level view of the manual partitioning window. I am still getting used to it.
Anaconda Set Mount Point

Four Device Types are defined.

And there are three options in the Technology dropdown menu. Not much to say here since I am still getting used to it. But stay tuned, more to come. My overall assessment, though, is this: yes, some parts look good, but the disk partitioning aspect could be better.


Share on facebook
Share on twitter
Share on pinterest
Share on linkedin

Hola! Did you notice that no longer runs network ads?  Yep, no more ads from the usual suspects that track you across the Internet.  But since  I still need to pay to keep the site running, feel free to make a small donation by PayPal.

Subscribe for updates. Trust me, no spam!

Mailchimp Signup Form

Sponsored links

1. Attend Algorithm Conference, a top AI and ML event for 2020.
2. Reasons to use control panel for your server.
3. DHgate Computers Electronics, Cell Phones & more.

26 Responses

  1. The previous Anaconda is going to be around for a while. Because of new hardware, forcing uefi booting, a new Anaconda is required.
    The weakness with the old one was the difficulty of allocating partitions across different disks.
    For example, /boot on one drive, /home on a second /opt on a third and everything else (/ /etc /usr etc) on a fourth.

    I was hoping that anaconda would be ready for Fedora 18, but it will be late. Still, it will be more “first time user” friendly.

  2. I have been using anaconda for the past 6 years, and this new version is a major improvement. I long ago suggested that a GUI interface that incorporates a Gparted presentation of disks and partitions, would go a long way to eliminating installation errors, where there are multiple partitions on a single drive.

    I would like to address some of the English text. It could be improved, and I offered via Fedora user group to do it, but I have not ever had any feedback. How do I go about getting myself involved in rephrasing some of the text?

    There is one default button missing, from what I saw of the print-screens, and that is “Use default Settings”. There may be a resequencing of some panels, but that is to be expected. It is a great step forward. Bravo to the developer(s).

    1. But the current presentation of disks and disk partitions in Anaconda is as good as it gets. It’s very easy to explain to anybody, even to a noob. Why did they have to change that aspect if it’s not broken?

  3. As far as I am concerned, as long as the actual distro works then who CARES how the install GUI looks? I come from a MS background, and although MS managed to make their installations all “pretty” and enticing for the eyes, the actual “insides” of the OS just plain sucked! I’d rather a screwy, not-too-familiar, installation interface that “leads” to software and technology that WORKS, than to have something look good for the hour – half hour it takes to install and then have to deal with an OS that is useless! SO lighten up maybe?….there’s worse things to deal with when installing software..(incompatible HW……faulty files etc….

  4. yeah, the software selection does look overcomplicated. Though usually I install the “add-ons” after and not during the OS installation, since I install software packages on an as needed basis.

      1. You’ve got to be kidding! Have you tried setting up a dual-boot system, or creating partitions manually. How does it stack up wrt the current stable version?

        1. the software selection on the pre-alpha that was “too detailed” was probably just to test the interface on much simpler tasks (such as seeing if it actually installs a single software package) before testing more complicated ones such as the entire set of administrator tools in one add-on, and was obviously not the final since the add-on selection on the alpha version is better laid out than the one on the pre-alpha version. I’m currently testing dual-booting now, but I don’t expect it to work flawlessly since this is the alpha version, the installer has already crashed several times, which is not surprising from an alpha release. Anaconda will probably work flawlessly on the final release.

    1. Ubuntu is not the only distribution that has a following. Installation was and is a major weakness in attracting new converts from Windows to Linux. Anaconda goes much much better than before to address this barrier for new users.

  5. What I see in the interface so are good points and bad ones, but I’m afraid I have to distance myself from the posts of Christopher Thomas and Finid. Their posts address only futilities as far as GUI design goes, and should be put near the bottom of the priority list.

    Why so? Well, first lets remind ourselves what the objective of a GUI is. It’s not (as some people seem to think) to provide eye candy. Eye candy is a waste of time (unless you can use it to sell something).

    The objective of a GUI is to allow an end-user to use a piece of software safely, effectively, conveniently and reliably with (almost) zero knowledge of how it works (and no intention of reading a manual either).

    To do this, a GUI must take people by the hand, and steer them through the available choices. It should also allow people access to all relevant options in such a way that the can find what they need. A GUI for installation must also be able to cleanly back out of choices until final confirmation is given. Don’t underestimate this please, this seemingly modest requirement takes a *lot* of effort and polish to achieve. Much more so than hacking a piece of code to read a few config files.

    In fact, this level of functionality is far more than most Open Source Software ever delivers. Simply because OSS tends to be written by programmers for other programmers (or hobbyists who like to tinker).

    When a GUI does allow safe, effective, and reliable use of a piece of software, the functional design of that GUI is done.

    What remains is some design polish, which (and I agree with Christopher here) should not be entrusted to a programmer because they’re not very competent at it. But looking at the above screens, the GUI seems to totally basic in design, but usable and fit for purpose.

    If the developers have any energy left after building this, investing it in a solid and informative help function would be *far* more useful than providing an Aero-look to the windows.

    Remember that this GUI is going to be used (and probably no more than once) by people who want to install Linux without understanding how it works, and who’d otherwise be installing MS Windows. Hand-holding, completeness, clarity, and reliability are paramount. Eye-candy is not.

    1. Intuitive is the word that describes what you are attempting to describe in the first four paragraphs of your comments. By that measure, the disk partitioning part, which is about the most important aspect of an installation program, is a fail of the medium variety. And that is the part that I am complaining about.

      It’s not about eye candy, but about being simple, point-and-click-easy-to-use, without consulting a manual. Take a look at the redesigned PC-BSD installer, which offers even more advanced features than Anaconda. It is a major interface redesign, but it managed to achieve a level of intuitiveness lacking in the new Anaconda.

      And contrary to your point, installers tend to be used a lot more than once by the same person. If you have been around Linux for some time, you know that we tend to install and reinstall again and again. But I guess by the time you use it twice or more, you will have gotten used to it, in spite of its design shortcomings.

      1. I visited the link, and did not find the disk selection and setup very compelling. Anaconda is really better.

  6. Designing the partitioning tool is really difficult and they’ve been through at least six different designs I can remember, all with good points and bad points. So just saying it ‘could be better’ doesn’t really help much 🙂 It might be useful if you could say more specifically what you find problematic about the current design.

  7. can SOMEBODY please let a designer work on this before it goes live…

    UGLY UGLY UGLY…..does nobody understand how to align elements so it doesn’t look like you just threw it together using a bunch of programmers..

    we need to stop using programmers as designers, they are useless at it, I’m a programmer and I realise that and it’s why I don’t design my work, I only program it.

      1. Oh God. If that thing has been created by a “designer”, then there’s very little hope. There’s no point in telling a self-appointed designer such basic things as “mind the spacing” or “select proper font sizes”. If she’s deluded enough to believe she’s a designer, how can we expect her to listen to design 101 issues?

          1. Do you realize that for a true designer, spacing and font sizes are second nature? Not even in an early alpha state would something put up by a real designer look that awful.

          2. ..Did it occur to you a rendering bug can affect the entire layout? You can comparing a pre-release which does not reflect the final version.
            And yes, I am aware of spacing and typography but the skeletal structure needs to function first.

        1. As the designer in question, I greatly encourage you to try out the new version of the installer available in Fedora 18 Beta. As Luya pointed out (and as would have been obvious to you if you looked at the mockups you were pointed to and compared them to the running Alpha screens), the Alpha release was very much focused on core functionality and not design polish.

          Myself and several other Fedora designers spent the several weeks before the beta release working with the GTK+ and glade files for Anaconda, fixing the alignment, padding, and font size issues as best we could. GTK+ is not a very forgiving platform for designers.

          Anyway, I hope you’ll find the surface design issues in beta to be an improvement (we have more to go before final.) I also hope you’ll agree that we prioritized functionality over pretty over the course of our release timeline.


          1. Since the beta was released, I’ve installed Fedora 18 beta more than 4 times, both on real hardware and in a virtual environment.

            Beyond the obvious design issues, the disk partitioning aspect is a major headache. On one installation attempt on a system with an existing Linux distro on it, I spent about 15 minutes spinning between manual and automatic partitioning modes, until I gave up on that installation. I needed to find a documentation on how to dual-boot Fedora 18 beta and another OS. And I am not a noob on this matter.

            Why should I need to read a documentation just to know how to install Fedora 18 alongside another distro on the same HDD? That is evidence of a major design failure. That was never the case with the old Anaconda, where the choices and what to do are as clear as daylight. Why can’t this one be the same.

            Why are buttons scattered all over the place? There is a Done button on the top left at some steps, while on others, a Continue button is on the bottom right. Consistency.

            I think you guys tried to be too cute with something that needed to be very simple.

          2. I kinda like the new Anaconda because it’s less clicking since you don’t need to go through all the steps, and you don’t have to click back a bunch of times to get to a previous step, but like finid pointed out, the buttons shouldn’t be scattered like that, which was one of the few problems I had, mine was on a new Virtual Disk inside VirtualBox so I didn’t run into the problem with installing on a system with an existing distro, but I have no problem with having to read documentation since I do that a lot with Arch, but it might not be so good with someone who’s new to Gnu/Linux

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the latest

On social media
Via my newsletter
Mailchimp Signup Form

Partner links

1. Attend Algorithm Conference, a top AI and ML event for 2021.
2. Reasons to use control panel for your server.
3. DHgate Computers Electronics, Cell Phones & more.
Hacking, pentesting distributions

Linux Distributions for Hacking

Experts use these Linux distributions for hacking, digital forensics, and pentesting.


The authors of these books are confirmed to speak during

Algorithm Conference

T-minus AI

Author was the first chairperson of AI for the U.S. Air Force.

The case for killer robots

Author is the Director of the Center for Natural and Artificial Intelligence.

Why greatness cannot be planned

Author works on AI safety as a Senior Research Scientist at Uber AI Labs.

Anastasia Marchenkova

An invitation from Anastasia Marchenkova

Hya, after stints as a quantum researcher at Georgia Tech Quantum Optics & Quantum Telecom Lab, and the University of Maryland Joint Quantum Institute, I’m now working on superconducting qubit quantum processors at Bleximo. I’ll be speaking during Algorithm Conference in Austin, Texas, July 16 – 18, 2020. Meet me there and let’s chat about progress and hype in quantum computing.