I have run across a few people who are perplexed by
firewalld and I must admit that I was for a while until I did some reading and experimentation. What is
firewalld? It is basically a replacement for the ancient
iptables service on RHEL and Fedora systems. So many of us were just used to manually editing
/etc/sysconfig/iptables and then coping that file from system to system as desired, that the switch to
firewalld was a bit scary. I mean, who wants to learn something new, right?
Another thing that is scary about
firewalld is the complexity of the rules it shows when you do something like:
While the configuration, tools and output has dramatically changed... really
firewalld makes things easier and more manageable. Really. One of the problems with Linux across distros is that there really hasn't been a standardized way to handle the host-based firewall. Each distro seems to have their own way of doing it... and popular packages like Shorewall have been around for years. I think
firewalld tries for a happy medium somewhere between simple and complex and a standard that distros can choose to adopt.
Anyway, here are some basics (as root or via sudo) but if you want more be sure and check out the documentation:
Main documentation: www.firewalld.org/documentation/
Fedora Documentation: fedoraproject.org/wiki/FirewallD
RHEL Documentation: access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Using_Firewalls.html
firewall-cmd --list-all(shows human readable firewall settings)
firewall-cmd --add-service=sshd --permanent(opens up port 22 which is sshd and saves to config)
firewall-cmd --add-service=http --permanent(opens up port 80 which is http and saves to config)
firewall-cmd --add-service=https --permanent(opens up port 443 which is https and saves to config)
firewall-cmd --remove-service=https --permanent(closes port 443 and saves to config)
If you want don't want your changes saved just leave off --permanent.
Want to open arbitrary ports for some service (like voxelands-server for example)? That is easy too:
firewall-cmd --add-port=30000/tcp --permanent
Want UDP? Ok:
firewall-cmd --add-port=30000/udp --permanent
After your changes it doesn't hurt to verify again with:
Want to manage firewalld via a config management system? There is a formula for SaltStack here and supposedly Ansible also supports firewalld.
Want to edit a file instead of running
firewall-cmd? That's possible too.
firewalld stores everything somewhere under /etc/firewalld/. In particular the changes listed above would get written to
/etc/firewalld/zones/public.xml. Yeah, it's an "xml" file but make a change or two via firewall-cmd and see what it adds or removes from it and you'll see that it is very easy to monkey-see-monkey-do for those that want to edit the file directly. After updating or replacing any of firewalld's configuration files you want to make firewalld aware of the change with:
systemctl reload firewalld
If you are brave enough to manually edit the config just be aware that you are responsible for your typos.
I've only touched the tip of the iceburg for the most common stuff. Need more info? Yeah, there is a ton of documentation including a couple of man pages.
I've been following the development of Fedora 21 since a little before the alpha release. Getting my MontanaLinux remix to build was actually quite easy and the fact that rpmfusion has a rawhide repo means all of the multimedia codecs / applications were good to go as well. I've done few dozen installs as KVM virtual machines and thought it was time to try physical hardware.
First I installed it on my Acer netbook that is 32-bit only and about 5 years old now. The battery in it is shot and smartd has been telling me for over a year that the hard drive has been getting more and more bad sectors... which is a fairly good indicator that the hard drive is going bad. Doing the install from a LiveUSB it took a while because the installer was finding some of the bad spots on the drive. For whatever reason during the install the progress bar immediately said 100% and I knew that was wrong... so I kept switching over to a text console to periodically do a df -h to see how much had been written to the hard drive. Oddly whenever I'd switch over to the text console, the green illuminated power button would go amber and the screen would go blank... which to me meant it was suspending to RAM or something. At that point I'd have to hit a few keys on the keyboard and it would wake back up. For whatever reason it did this at least a dozen times during the install. I really wasn't expecting a good install given the flaws in my hardware and how they were manifesting themselves during the install process... but being patient paid off... and it actually was successful... and seems be working just fine post-install.
Installing it on my Optiplex 9010 desktop at work was also more complicated than I was expecting. For whatever reason (maybe a BIOS setting?) I could NOT get my machine too display the bootloader menu from a LiveUSB although other Dell models at work seemed to work fine. So I burned a DVD with the burner in the Optiplex 9010. Oddly the same drive that wrote the DVD seems unable to read it about 19 out of 20 tries. That meant that I couldn't get it to boot from the DVD either. I finally decided to try something different... and I got an external / USB optical drive and plugged it into the USB port and I was able to get it to successfully read the DVD and the bootloader to appear. With a functioning bootloader I was able to boot the DVD and the live system worked great... and the installer went flawlessly.
Fedora 21 pre-beta actually seems quite stable. As you may recall I have all of the desktop environments installed as part of my remix so I can check them all out... but I primarily use KDE. On both of my machines I have /home as a separate partition so my personal data is retained across installs. I also backup /etc and /root to /home/backups/ so any of my previous configurations (stuff like ssh keys) can be retrieved and used if desired.
I picked lightdm as the default login manager. In the past I've mainly used kdm but KDE is in the process of transitioning to sddm which seems a bit buggy still.
One of the main features in Fedora 21 I'm wanting to play with actually is provided by the rpmfusion repos... ffmpeg 2.3.3. I'm wanting to do some testing with the newer ffmpeg that does a reasonable job at webm encoding with vp9 and opus. I'd also like to try out GNOME 3 under the Wayland display server... which is supposedly working fairly well in Fedora 21... but I haven't tried it yet.
One weird glitch I ran into was with the Google-provided google-chrome-stable package. I'm not much of a Google Chrome user but I do occasionally use it for (legacy) sites that require Adobe Flash. I use Firefox the vast majority of the time... but I've decided to no longer install the Adobe provided flash-plugin package (at version 11.x). As you probably know Google has taken over maintenance of newer Flash versions (currently 15.x) on Linux and include it as part of Google Chrome. As a result, whenever there is a Flash update from Adobe, there is a Google Chrome update that soon follows. Anyway, very early in the Fedora 21 development cycle (pre-alpha), the Google Chrome package refused to install because Fedora 21 had a much newer version of some library (I don't recall which one) and it wanted the older version. A few Google Chrome package updates later... and it is happy with regards to dependencies... but installing it with rpm... it gets stuck on the post-install and just sits there. I had to ^c rpm (which you generally don't want to do) because it wasn't going to finish... and just to be safe I did an rpm --rebuilddb and everything seems fine. The google-chrome-stable package verifies just fine (rpm -V google-chrome-stable) and the package works as expected.
Overall everything I've tried works fine. I like to get started with new Fedora releases as early as possible in the development cycle so I can help report any bugs I find (in Fedora provided packages) and be up-to-speed with all of the new features on release day so I can deploy to other machines immediately. I've been doing it that way for several releases now. I do really appreciate all of the work the Fedora developers put into each release.
I ran across this on Monday night. Anyone else watch Major Crimes? Enjoy!
I just accidentally discovered a feature I didn't even know existed. What feature? I'll call it the Firefox Resolution Tester feature although I'm sure that is NOT the real name of it. I don't know how long it has been a feature of Firefox... maybe for a long time... but like I said... I just found it in Firefox 30. How do you access it? Hit
CONTROL-SHIFT-m. That's it.
I accidentally discovered it when I wasn't paying attention to which application window I was using had the focus. I thought it was konsole (KDE GUI terminal).
CONTROL-SHIFT-m in konsole toggles the menu on and off. In Firefox it takes the current web page you are viewing and puts a black border around that has a control menu at the top left of that black border. The control menu allows you to pick from several pre-defined resolutions or even add additional presets if desired. Picking a different resolution resizes the view of the page (and increases the black border around it accordingly) to the desired resolution. It also has a screenshot feature (saves to your default download directory and auto-names images something like "Screen Shot 2014-06-01 at 07.42.29.png"). You can also rotate the resolution to simulate a mobile device. It has a "Simulate Touch Event" button but I'm not sure what that does. Anyone?
At work they recently licensed a commercial web content management system that primarily targets larger educational institutions -- OmniUpdate Campus. The web developers (which I am not one) at work have created a nice responsive theme that everyone can use for their departmental websites and it works great. Don't have a responsive site handy? You can try this temporary testing one I made in OmniUpdate. That's just a shell but it'll show you responsiveness.
Anyway, I kind of got off track. Yeah, Firefox. Try
CONTROL-SHIFT-m and enjoy. Can anyone tell me what version of Firefox first included this feature?
MontanaLinux: Please tell me about yourself... as much as you feel comfortable with... as open or as closed as you want to be... family, education, work, hobbies, religion, volunteering, diet, music tv / movies, etc.
Máirín Duffy: Let's see if I can cover all of those in one sentence. I'm a married vegetarian Roman Catholic mom and RPI alumna living in Boston who is happily employed at Red Hat as an interaction designer and occasionally teaches kids how to use FLOSS creative software, and additionally am a big fan of Zooey Deschanel (so I like New Girl and She & Him.)
ML: What software-based graphics tools have you worked with in the past and what currently are your favorite applications?
MD: My first digital painting program was the Smurfs Paint 'n Play for the Coleco ADAM. When we finally got a PC with a VGA card, I used Deluxe Paint II and the Disney Animation Studio painting programs. I used Photoshop and Gimp when I was in high school and was introduced to the Macromedia tools in college. My tools of choice in college were Macromedia Fireworks for almost everything, and Adobe Illustrator, Macromedia Director, and Macromedia Flash for everything else. I followed sodipodi and I switched over 100% to FLOSS tools around Inkscape 0.39.
At this point I've been using a fully FLOSS creative work flow for around 7 years — starting with Inkscape and Gimp on Fedora and branching out to Scribus, MyPaint, Krita, Blender, Darktable, etc. as new applications became available. Inkscape is by far my favorite graphics tool and I use it for almost everything.
ML: Are there any hardware accessories that you like to use in your daily creative work? ...and if so, please tell me about them.
MD: I have a Lenovo x220T which is a laptop with a swivel-screen that has a built-in Wacom tablet and stylus. I use it often when I need to do illustration work; it's good for sketching, too.
ML: I believe you have done some FOSS training sessions at a few educational institutions. Please tell me about those experiences and do you hope to do more of those in the future?
MD: I've done a lot of sessions, but the two longest ones were probably the Inkscape class I did at a middle school near Red Hat's Boston-area office (10 weeks) and a Gimp and Inkscape class I did with the Girl Scouts in Boston (8 weeks.) (You can read more about each respectively at http://opensource.com/education/10/4/introducing-open-source-middle-school and http://blog.linuxgrrl.com/category/girl-scouts-class/)
It is a lot of work to put together classes like that, but working with kids is really fun. The thing about these classes is that the kids get to keep the software. For example, I found out that a student I taught in one of the classes still uses Inkscape at home and entered an art contest with a design she made in it well after the class was over. You know, when I was a similar age to those kids, I was a student in an outreach program at the school that later became my alma mater (RPI.) We were taught character animation in Macromedia Director. Not only could I not go home after the class was over to practice and build on my skills because I didn't have the software — it was quite expensive back then — but by the time I entered college Macromedia Director was basically sunset as a product in favor of Flash. Is there anything today that can even open up *.dcr files from Director? My Director projects are probably bitrotted forever, and I'm not that old.
I think us folks in the FLOSS world take it for granted that there are these amazing and free tools using open standards right at our fingertips and the more we can share and teach them to others, I truly believe the world will be a better place.
ML: What FOSS / Linux conferences have you participated in? Have you given any presentations and if so, on what topics?
MD: I have; probably too many to list them all at this point. I was just at Grace Hopper a couple of weeks ago and participated in the Open Source Day Systers Mailman 3 Hackfest (got a few commits in to Mailman 3 too!) Last year, I gave a talk at the Red Hat Summit OpenSource.com panel about FLOSS creative software. I keynoted at Software Freedom Day Boston a couple years ago or so about attracting more designers to FLOSS. I gave a talk at the Linux Plumbers' Conference a couple years ago about storage technologies and UX (related to some of the Anaconda design work I did.) I wrote a paper about designing for free software as part of an open source workspace at the ACM CHI conference in 2010 (http://blog.linuxgrrl.com/2010/04/06/contributing-to-free-open-source-software-as-a-designer/.) I've also given talks at the Libre Graphics Meeting, SXSW, GUADEC, FUDCon, LibrePlanet, FOSS.in, LinuxCon, and probably others I'm not recalling at the moment.
ML: Do you consider yourself a technology lover? If so, do you have any visions of the future you'd like to share?
MD: I learned how to read by playing text-parser adventure games on an old 8088 machine; I grew up with a love of technology and auspicious thoughts for a future with even better technology. Unfortunately, I'm a bit more cautious about technology now - particularly tablets and phones. I'm a new parent, and I worry about the ubiquity of these devices and how they may affect childrens' development. It's also sad to go to pretty much every public place and see heads bent down staring at screens rather than healthy social interaction (I'm as guilty as anybody.) What about the divide between people who can afford these devices and a ubiquitous internet connection and those who can't? There's bad that comes with the good that technology brings, and I think a lot more careful thought and action needs to be put into mitigating that bad.
ML: What hardware have you purchased for yourself? Do you have a laptop, smartphone and/or a tablet? If so, what?
MD: I have an x220T tablet, a Samsung Galaxy S4, and a Nook HD. I've never purchased a piece of Apple hardware in my life, although I was - oddly enough - given a gumstick iPod Shuffle once when I signed a lease on an apartment. It bricked after a few months.
ML: Do you use any non-FOSS software? If so, what and why?
MD: The only non-FLOSS desktop software I use is my income tax software. I have it installed on a hard drive with a Windows install on it that came with my husband's personal laptop before we swapped an SSD into it. I use that once a year, because I'd rather do my own taxes and the laws change too frequently for any potential FLOSS solution to be workable.
I do have more non-FLOSS apps on my phone than I'd like to admit, and I use more non-FLOSS web apps than I'd prefer (although many are FLOSS.) I used to not even use Flickr or Twitter because they aren't open source - as I get older, I think I'm getting more soft in tolerating that. One piece of proprietary software I'm particularly proud of avoiding, though, is Gmail.
About your work with Red Hat
ML: How long have you worked for Red Hat and what positions have you held there?
MD: I've worked for Red Hat close to 9 years, if you don't count my summer internship before I started full-time. I've been an interaction designer the entire time, but I have worked on different teams over the years.
ML: What projects have you worked on within Red Hat?
MD: I've worked on a lot of projects over the 9 year period so it would be boring to list them all out. The two main products/projects I've worked on are Red Hat Network / Red Hat Network Satellite and Fedora. As of late I've been spending a lot of time on Hyperkitty, the mail archiver web UI for Mailman 3.
About your work with the Fedora Project
ML: How did you first get involved with the Fedora Project?
MD: I used Red Hat Linux when I was a high school student but was converted to Debian in college. I migrated to Fedora and got involved with the Fedora Project when I did a summer internship with Red Hat's desktop team in the summer of 2004.
ML: What things have you worked on in Fedora?
MD: A lot of things! I've been the community design team lead for several years at this point, which has involved a lot of wrangling to get the artwork ready for each release on time, although honestly gnokii (Sirko Kemter) does a lot of this work now - he makes sure things are ready and prepares a lot of the release artwork. Most recently on the Fedora design team I've done a lot of artwork for the Fedora Badges system (badges.fedoraproject.org) I redesigned the fedoraproject.org website with a team of Fedora design team members in 2009-2010 although it is due for some updates these days, I think. I've done a lot of UX work for a lot of different components that are in Fedora, including virt-manager and anaconda, the installer. I've also done UX work for some of the infrastructure applications that help run Fedora, including the Fedora Packages app (http://apps.fedoraproject.org/packages). I've served on the Fedora board too, but not a full term.
ML: What do you think Fedora's strengths and weaknesses are both as a FOSS development project and as a general purpose Linux distribution?
MD: By development project, I'm assuming you mean a FLOSS project community and not necessarily a development platform (but please correct me if I'm wrong.) As a community I think Fedora has a major strength in that it attracts many smart and passionate folks. The corresponding weakness (which is shared by other FLOSS projects) is that demographically it's not a particularly diverse set of folks. We are actively working on that though; for example, Fedora has participated in the FLOSS Outreach Program for Women in the past couple of rounds or so.
Another strength of Fedora is that as a community, Fedora is particularly concerned about openness and transparency with respect to project discussion but also privacy when it comes to personal information — so much so that, for example, when we proposed a Fedora badge for folks voting in a vote to choose wallpapers, we had to make the badge an opt-in badge rather than automatic because concern was voiced about individuals' privacy with respect to whether or not they voted. Folks aren't just interested in software freedom; they are interested in other social justice issues (like privacy) as well. A weakness to counter that is that in a community of passionate people, the discussions can get pretty heated — particularly on the mailing lists. This is also not unique to the Fedora Project. We are hoping to help tame the flames with affordances provided by Hyperkitty, when it's ready.
As a general-purpose Linux distribution, I think Fedora's strengths are that you have highly-skilled, full-time software developers alongside community developers putting out software in Fedora first. The corresponding weakness is that because there's new technology in Fedora first — for example, systemd or GNOME 3 — when you use Fedora you have to learn the new things sooner than other distros' users since you're getting it first. That can take time; there might not be as much documentation and as many how-to blogs available yet to learn because the tech is so new.
ML: What things would you change about Fedora if you had a magic wand?
MD: If I had a magic wand, Hyperkitty would be ready and deployed across all of the Fedora mailing lists and we'd be having much more productive and efficient conversations!
About your Anaconda design work
ML: Anaconda is the installer that Fedora uses on the install and live media. Why did Fedora need to redesign Anaconda?
MD: Will Woods covered this much better than I could in a two-part blog series that starts here:
Adam Williamson and I wrote this too to go along with the initial release of the new UI:
The redesign was initiated by the development team. The design wasn't conjured up first and then pushed on to them. They made a decision that a redesign had to be done, and they sought out UX help for the UI part of it. That is how I became involved in the project. A lot of underlying problems with Anaconda were addressed - quite well - by the development team but haven't gotten as much attention as the UI because the UI is simply more visible. (The two links above give specific examples.)
ML: Is the Anaconda redesign completed or is it an ongoing process?
MD: The major chunks of it are completed, but improvements are an ongoing process. We've done several usability test rounds (with the help of two interns, Stephanie Manuel and Filip Kosik), including a couple where we performed tests at DevConf.cz in Brno, Czech Republic and in Red Hat's Boston-area office. You can see the test documents from those tests here: https://fedoraproject.org/wiki/Anaconda/UX_Redesign#Usability and a summary of the analysis from the test results from Brno https://www.redhat.com/archives/anaconda-devel-list/2013-April/msg00018.html and Boston https://www.redhat.com/archives/anaconda-devel-list/2013-April/msg00011.html. We combed through all of the test videos and reports and incorporated some user feedback we'd gotten on the redesign as well and came up with an exhaustive list of issues to address, many of which have already been addressed: http://fedoraproject.org/wiki/Anaconda/UX_Redesign/Usability_Test_Suggestions
The Anaconda developers, as they encounter usability-related UI bugs, will often consult with me or other UX folks to hash out a solution and then fix the bugs.
So the redesign isn't stagnant; as bugs filter in they are addressed on top of our active work to identify issues and address them through QA and usability testing.
ML: What has been the most challenging part of the redesign?
MD: The most challenging part of the redesign (which my vent^W talk at the Linux Plumbers' Conference a couple of years ago actually focused on) was any interaction involving storage technologies. I actually converted that talk into a blog, so if you want to go more in depth on this you can take a look at that: http://blog.linuxgrrl.com/2013/01/04/storage-from-a-ux-designers-perspective/ Storage technology is all over the place and I think it's a bit of a miracle it is as standardized as it is. There are so many tough situations you can get into when you get storage wrong. (An example from Anaconda: http://blog.linuxgrrl.com/2013/03/04/refreshing-storage/)
ML: I must admit that when I first encountered the partitioning screens starting with Fedora 18, I was not fond of them. For various reasons, I do a lot of Fedora installs and eventually it grew on me... but I still hear quite a bit of complaining. How much and what feedback have you gotten from the community?
MD: The main feedback we get about most of the new Anaconda screens is either complaining about the position of the 'done' buttons in the upper left (folks want it in the lower right) and the text of the 'done' button (it's previously been 'back,' and we got complaints then because it doesn't always mean back, so we changed it to 'done.')
I think these complaints are symptoms of the hub and spoke model we've chosen to go with. For most of the screens, hub and spoke works great. Where it falls apart is the storage-related screens, because the storage 'spoke' is actually a little mini linear wizard in itself. I'm not convinced that hub and spoke generally was the wrong model to go with, but we've been making small tweaks here and there to the storage area so that it'll make more sense based on the usability test results and feedback we've gotten.
I also think some of these issues are symptoms of a design goal we had — make it possible for less-experienced users who just want a working system without much fuss to get one. In the design, I think I tried a bit too hard to prevent those users from being exposed to more complicated bits like custom partitioning. I mean, where I was coming from was reasonable: if you know how to create a RAID 4 array and you can actually recite the difference between all of the RAID levels, you're probably smart enough to poke around and find what you want. If 'RAID' makes you think of bug spray in all-caps, you back away slowly from the computer if you encounter any form of custom partitioning. Again, though, I think I made some bad calls there and those are shaking out in the usability test results and user feedback.
Actually last week I talked to Chris about instead of only having custom partitioning accessible from the 'Done' button on the first storage screen, to also have a button to just go to it since many people want to go there and aren't sure how when they get to the first storage screen. (It really is not intuitive to hit 'Done' to get to custom partitioning.) I'm hoping to mock up the fix this week. (I know this does seem a bit late to get to it, but to be fair I was on maternity leave for much of the Fedora 19 development cycle.)
ML: What complaints have you encountered and how valid do you think they are?
MD: That's a particularly broad question so I'll answer it broadly with respect to the user feedback we've gotten. Generally, I was pleasantly surprised by the feedback we got on the UI part of the redesign. Any time you embark on a major redesign — especially if the thing you're redesigning has been pretty much the same for a 10-year long period — you're going to get backlash. The things folks had the most trouble with were the parts of the redesign I knew were weak (particularly storage.) The parts of the design I thought worked well, for the most part, didn't receive a lot of complaints. I was seriously expecting hate mail, but I didn't receive any. I actually received a few well-reasoned and productive critiques that then went straight into the 'Usability Test Suggestions' wiki bucket list of items to address. The most common off-the-cuff feedback I hear is along the lines of, "I didn't like it at first, but now that I've had time to get used to it, it works fine for me."
I think a big reason for the less-severe-than-expected and surprisingly-helpful-feedback was how open we were with the redesign and rewrite process — I worked pretty hard to blog our major design decisions and process and the Anaconda team are very open in IRC and on the anaconda mailing lists. If someone was really bothered by it and did a search, my guess is they'd find all of that documentation and be able to see where we were coming from with some of the decisions and that may have moderated their feedback a bit.
I will also be the first person to say that there's no way that the design work I put together for the Anaconda team was perfect. Have you ever taken a drawing or painting class? If you start in with the eyes, and try to render them perfectly, then move out to the nose and the mouth and the head and the body — rendering each as accurately as you can, one-by-one — you are going to find yourself with a disproportionate and likely poorly-composed work with many smaller nicely-rendered bits. Nobody, not even the great Renaissance masters, sit down to an easel and draw a perfectly lifelike rendering of what's in front of them starting with the very first stroke. You have to start with broad strokes first, lay down the foundation for your composition, do one pass for gesture, do another pass to pick out the positions of the major body parts, another pass to hit the major shadows, do another pass... so on and so forth, until you get down to precisely-rendered, life-like details. You don't start with those details. The design we started with for Anaconda is a few passes in, but we're working with the feedback we get to make additional passes and refinements.
ML: I've hear some people advocating for the use of a separate tool for the complex task of partitioning... perhaps gparted... but that wouldn't work would it? If I understand correctly, the Fedora installer has requirements for more advanced partitioning / filesystem features that gparted does not offer... things like Linux software RAID, LVM, and various combinations of those. Is using an external tool even a viable option?
MD: Using a separate tool for partitioning would be a good idea in that, at least for the full / non-live installer, you're in a limited environment to get your work done. Partitioning is scary work, even if you really know what you're doing. Anaconda itself is a limited environment — you don't have a web browser to look up help and it's constrained in ways a full desktop is not. Anaconda handles these things because it has to, but I personally think it would be ideal if Anaconda handled installation and a lot of the complicated storage bits were handled by another tool that specialized in storage. As you point out, though, the tools that exist now don't meet the same requirements that Anaconda does, so Anaconda continues to handle storage configuration like partitioning. Anaconda is now modular, though, so the storage-handling code is now actually broken out into a separate library called blivet. Maybe at some point an external tool could be written that uses that library.
ML: Are there any upcoming changes in Anaconda in Fedora 20 that you'd like to mention?
MD: If I can get that mockup I mentioned earlier done and the team has enough time to implement it, maybe there will be a button to go to directly to custom partitioning. If not Fedora 20, hopefully Fedora 21.
ML: Is there anything I neglected to ask about that you'd like to mention?
MD: Yes, "How do you like working at Red Hat?" To which I would answer, "It is the best job in the world." Thank you for the interview, I enjoyed it and I hope it helps your readers understand a bit more about the Anaconda UI redesign.
ML: Thank you for taking the time to answer my questions.
As you may know, Fedora totally redid their Anaconda installer starting with Fedora 18. There are many reasons for it and I'll not go into that here but one perception out there in Internet land is that the partitioning section of the newer Anaconda installer is a pain to use. I must admit that when I first started using it (installing Fedora 18 alpha and beta releases), I really did not like the changes. This dislike persisted for some time until I finally got used to it. Then time passed. Fedora 19 development started, ran its course, and then Fedora 19 was released. It offered some Anaconda refinements. Now Fedora 20 is approaching its beta release and there are yet more Anaconda refinements.
Since I build my own personal remix of Fedora with the stuff I want pre-installed, I do a lot of installs... to test stuff out. I've definitely gotten used to the newer Anaconda now and I actually like the partitioner. The last time I installed Fedora 17 (to test my last remix build, it has since gone EOL) I actually felt weird using the older Anaconda. I actually prefer the newer one now.
Few people do as many installs as me... and some are still stuck in the "not liking the newer Anaconda" stage. Their main gripe seems to be that the partitioner is very confusing and somewhat broken. I disagree with them and I've been doing some troubleshooting with a couple of problem installs users were having. Turns out their problems had less to do with Anaconda and more to do with having terrible pre-existing partition layouts on their hard drives. I though it might be useful to examine two cases where I have the actual fdisk listings of their partition tables. I'll not mention the names of the users who provided them to spare them some negative attention.
Example one - Let's just jump right in. Here's an image that shows a really poor pre-existing partition table:
Here is a somewhat incomplete
fdisk -l listing for it.
Device Boot Start End Blocks Id System /dev/sda1 63 80324 40131 de Dell Utility /dev/sda2 81920 20561919 10240000 7 HPFS/NTFS/exFAT /dev/sda3 * 37459968 204937215 83738624 7 HPFS/NTFS/exFAT /dev/sda4 307337216 312578047 2620416 f W95 Ext'd (LBA) /dev/sda5 307339264 312578047 2619392 dd Unknown
That almost looks reasonable until one examines the details closely. There is a gap between the end of sda2 and the start of sda3. There is a gap between the end of sda3 and sda4. sda4 (the extended partition) is very small and as a result sda5 (a logical inside of the extended) is very small. What we have here is a bunch of free space but no way to get to it. One can NOT make any additional primary partitions. One can NOT make any additional logical partitions... and to the best of my knowledge... one can NOT make any more extended partitions. All of that free space (> 50GB) is in a virtual no-man's land.
How did this poor partition layout manifest itself in the Anaconda installer? The partitioner said there was plenty of space to install Fedora but whenever you went to actually create partitions / mount points it would give an error about there not being enough room to create said partition. Basically Anaconda was confused by the layout but really didn't have a way to communicate that the layout was unworkable. The end user is left with the impression that Anaconda is horribly broken when it was really a badly mangled pre-existing partition table that was to blame.
Example two - Here's another example of a really poor pre-existing partition layout as witnessed by the complete
fdisk -l output.
Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0008cbe0 Device Boot Start End Blocks Id System /dev/sda1 476313598 625137344 74411873+ 5 Extended /dev/sda2 16065 157765631 78874783+ 83 Linux /dev/sda3 160312635 476295119 157991242+ 83 Linux /dev/sda5 602389368 625137344 11373988+ 82 Linux swap / Solaris /dev/sda6 * 476313600 528878053 26282227 83 Linux /dev/sda7 528891993 602389304 36748656 83 Linux
I wish I had a screenshot of what that looks like inside of gparted but I don't. Just look at the start and end sectors for each partition. sda1 starts somewhere in the middle of the drive. sda2 is near the front. sda5 is after sda7. I don't think there is freespace and if an install is to be done, the user needs to reuse one or more existing partitions.
What did Anaconda do with this? The user reported that the install progress bar just hung at a very low single-digit number. The user just ended up having to power cycle after waiting entirely too long for it to finish when it wouldn't. After rebooting the install seemed to be functional but what exactly happened to make the installer get stuck is unknown. Anaconda gave no indication that there was an issue and did its best to work but obviously got confused.
How did these partition tables get mangled? - For both partition tables, I don't think any sane partitioning program would allow a user to create those partitions on purpose so you really have to ask... how did they get that way? To the best of my knowledge, both users engage in the practice of distro hopping. Distro hopping is where one is interested in using or playing with a different Linux distribution with some regularity. One of those users might be the host of a popular Linux-related podcast who reviews one or more different Linux distros every week... or not. :) But seriously, those partition tables can only be the result of multiple Linux installers, using different methods, strong-arming their way. An odd partition operation to make this distro install... and another one later... and maybe more down the line... and you get a mangled layout. Or at least that is the best explanation I've been able to come up with.
How should Anaconda respond to pre-existing unusable or sub-optimal partition layouts? - It would be nice if Anaconda could play the part of partition therapist and recognize when a user has a really bad partition table that is virtually impossible to work with... and just inform the user in a kind but clear way that they need to fix that before Fedora will install. Historically Anaconda seems to just get confused and error out... thinking that it could do something with it but failing. Can this be fixed? I'm not sure but I hope so. I certainly don't expect Anaconda to figure out methods of fixing the bad partition layouts but they do exist and a small portion of users are going to run into trouble. Luckily I've yet to see a situation where Anaconda makes the situation worse by breaking existing OS installs.
But wait, there's more - It turns out that both users had additional partition related problems.
User one has a Dell laptop that offers a special featured named DirectMedia. Go ahead. Take a little time to read that wikipedia link especially the Design Controversy portion of it. It turns out that the existence of that odd extended / locigal partition combination might just have been the result of MediaDirect... and even if they had been able to install Linux, at some point later when Windows was booted again, MediaDirect would have probably regenerated the problematic sda4/sda5 combination probably breaking any Linux install that was done. Now that takes "Made for Microsoft Windows" to a new and more scary level doesn't it? :(
User two once used dd to backup the contents of one partition to another and as a result had two partitions with the same UUID. As you will recall, one of the U's in UUID stands for unique but in this case it wasn't. Just what confusion might that lead to? They reported on a few occasions that most boots of their computer things were normal but other boots the contents of their home directory would totally change... only to change again next boot. After they figured out that they had two partitions with the same UUID it started to make more sense.
Conclusion - The point is that where there is smoke there is sometimes fire and no Linux distro installer can be a complete fire extinguisher in all situations. Some users have bad partition layouts and it would be a good idea to take that into account. Oh, how about a recommendation... boot your machine with some live media that includes gparted and get your partitions in ship-shape before installing. gparted is more battle tested for partitioning, resizing, etc than any distro's installer. Lastly, the newer Anaconada isn't so bad so get over it! :)
This came out a couple of months ago but I just noticed it.
There have been a number of negative articles about the updated installer in Fedora 18. That negativity has found its way into the Linux podcast arena... but it seems to me that the vast majority of people spreading the word about it... haven't even seen it.
Korora is a Linux distribution that is a remix of Fedora and they recently had a new release based on Fedora 18. One cool thing they produced and included with their live media is an installation video (approximately 19 minutes in length)... so I thought I'd share their video so that perhaps some who haven't actually seen the new Fedora installer can have a look and see that it is actually quite good. Enjoy.
Direct video link: Korora-18-Install-Video.webm (66.2MB)
Thomas Cameron from Red Hat talks about Spacewalk although he slides refer to Red Hat Satellite which is the downstream project:
I keep up with Fedora releases. Fedora 19 was due for an "Alpha" release last Tuesday but they had to delay. As most everyone already knows, delays in Fedora are to be expected. Anyway, I thought I'd check out their Alpha test builds. They actually seem to be working quite well. I did several installs from the "Desktop" media which is GNOME 3.8.x-based. The installs I did were inside of KVM-based virtual machines. Then I added on all of the other desktop environments and tried them out. Even in this early stage, it seems to be quite usable and stable. I obviously did NOT run into any of the "blocker" bugs that were the cause of the Alpha release delay. I think most of those were EFI related.
Remixing from Alpha
I thought I'd try doing a MontanaLinux remix from the development repositories. For those not familiar with MontanaLinux, it is basically the vast majority of desktop environments and desktop managers and a lot of desktop software rolled into a 2+ GB live .iso. It includes packages from rpmfusion (codecs, gnome-mplayer, vlc, etc), Google (google-chrome-stable and google-talkplugin) and Adobe (flash-plugin).
So from my Fedora 19 pre-alpha VM, I installed the various kickstart packages, extracted out the KDE related kickstart (.ks) files, and then melded them into a single file, added the packages I wanted to the %packages section, and then did a tiny bit of customization in the %post and %post --nochroot sections of the kickstart. With a MontanaLinux-F19.ks file done, I proceeded with the build.
It built. I discovered (with help from nirik in #fedora-devel on freenode) that Fedora no longer looks at /etc/sysconfig/desktop for the default desktop environment and display manager. That is done with systemd's systemctl.
The Bug Fairy Always Visits
There are a few glitches here and there but that is to be expected. lightdm was messing me up... so I had to add an exclude in the %packages section. I'm still in the process of refining the kickstart but it seems to work well enough.
For some reason, when I boot the .iso in a KVM VM on a Fedora 18 host I can't use the combination of SPICE/QXL. If I change it to VNC/any, SPICE/VGA, or SPICE/VMVGA it works fine.
I made sure to add in the GNOME 3.8.x Classic extensions so the GNOME Classic mode shows up in the display manager Session options.
I've only been working on this for a few hours so I'm sure I've got a bit of learning left to do. Fedora has since released a number of Fedora 19 updates and I haven't tried those yet. More later.
Update: April 22 - There was an additional flood of updates over the weekend. I guess the current build from Fedora went gold for the Alpha release and they had stockpiled some updates until after. I put in a few more hours on my configs and got the 32 and 64-bit versions built. They are working well and the SPICE/QXL combination now works fine. Updates included KDE 4.10.2 and MATE 1.60 among others.
If anyone wants to try it out, feel free to email me (firstname.lastname@example.org) and I'll reply with a URL.
Update: April 24 - Fedora DID release Fedora 19 Alpha yesterday. I've done yet another rebuild and created a screencast video (no audio) showing the Live DVD iso booting inside of a KVM Virtual Machine connected to with the SPICE remoting protocol. I didn't do any fancy editing of the video so there are long boring parts where you stare at a blank screen as it boots or loads. In the 25 minute video I boot, do an install, reboot and then do a quick survey of all the desktop environments, some apps as well as how I like to personalize KDE. The pre-release Fedora 19 base has a debug kernel and I'm sure the installer is doing a lot of extra logging... so the installer and the boot is a lot slower than the final product will be but that is to be expected. Everything seems to be working nicely except for Cinnamon.
Anyone who would like to watch it can do so with the link below. Right-click to download or play in your webm compatible browser. It is about 66MB in size... which is about 3 times the size of my first hard drive back in 1986. :)