When my colleague Ken Starks wrote on FOSS Force the other day about his gripe with Linux Mint’s handling of updates, I was a little amused because I had just dealt with this issue during the recent Bash crisis. I run Mint Maya with Xfce and I expected to find the Bash fix in Synaptic, but it wasn’t there. When I eventually found the update manager, I actually quite liked the set up. Having system updates easily available seemed to make sense and I liked the design. Like many things in tech, it turns out that the design was a little accidental, the result of a conflict necessitating the removal of the system update functions from Synaptic. But it works. I kind of like it.
It also seems to fit with one of the underlying philosophies of the distro. Mint is famous for being a desktop that anybody can use. Updates on the dash is a concept which a new-to-Linux Windows’ user can understand, maybe even without having to go to the forums for help — and a piece of cake for experienced free software users. In my case, the only problem I had is that I misunderstood the severity numbering scheme, figuring one to be most severe instead of the least, but I easily managed to patch and update my system.
I was impressed — which is why I was amused by Ken’s consternation.
Christine Hall has been a journalist since 1971. In 2001, she began writing a weekly consumer computer column and started covering Linux and FOSS in 2002 after making the switch to GNU/Linux. Follow her on Twitter: @BrideOfLinux
A biennial tradition in the San Francisco Bay Area, MeetBSD 2014 uses a mixed unConference format featuring both scheduled talks and community-driven events such as birds-of-a-feather meetings, lightning talks, and speed geeking sessions. MeetBSD can be traced back to a local workshop for BSD developers and users, hosted annually in Poland since 2004. Since then, MeetBSD’s popularity has spread, and it’s now widely recognized as its own conference with participants from all over the world.
Here’s what I want to know. Is replacing a well known application in Linux with a crippled version acceptable when it’s done in the name of stability? I’ll go ahead and place myself in front of you for scorn and castigation by admitting that I’ve been a member of the Slashdot community since 2002. Everyone has a sig line, right? Mine was thoroughly honed to be as concise a possible:
What took me by surprise was an invitation to be the closing keynote speaker. “Surprised” isn’t nearly adequate. For almost a week afterward, I checked my inbox several times a day, waiting for the apologetic message that they had sent the email to the wrong person.
Nope. I’m an advocate of free “as in speech” software — which includes the freedom to choose. If there’s a FOSS solution for something I need or want to do, I’ll take that every time, and encourage my friends to do so as well. However, if there’s something I need or want to do with no FOSS solution available, I might use a proprietary solution, depending on the depth of my need or want and on how draconian the terms of the proprietary EULA.
