Language Selection

English French German Italian Portuguese Spanish

Late 2008 Fav Distro

*BSD
2% (26 votes)
Fedora
4% (73 votes)
Debian
6% (105 votes)
Slackware
3% (57 votes)
Gentoo
3% (43 votes)
Mandriva
6% (99 votes)
PCLOS
10% (162 votes)
SimplyMepis
8% (134 votes)
openSUSE
19% (314 votes)
*Ubuntu
27% (444 votes)
Other
11% (183 votes)
Total votes: 1640

Should they be grouped?

I know it makes the list longer, but shouldn't Ubuntu and BSD not be grouped to give a more accurate view? Ubuntu may be the top slot but I think it would be valid enough to see if Kubuntu beats out openSUSE or if Xubuntu is more popular than Kubuntu.

I can understand not wanting to get too granular because the list will be way too big if you start adding Ubuntu Studio, Ubuntu CE, etc.

Also, shouldn't the title be a little more specific? I don't see CentOS / Red Hat so I assume these are selected more on the desktop usage than server.

~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Linux means Freedom,
the problem is most users don't know what it is,
or how to use it.

Arch Linux

One more vote for Arch Linux. The distro-hop-stopper Wink

Sidux all the way for me!

Sidux is super stable, got Compiz working too!

If I could, I would nominate several

I like to categorize my software. Let's face it, the core kernel and the primary utilities are rock solid, and the major applications are pretty solid, too, so it is usually packaging that differentiates the systems. Once they are installed and configured, they are more similar than different.

With that said, the MEPIS community has, not one, but two really outstanding desktop systems, SimplyMEPIS and AntiX, and they both are of consistent high quality, whether under development and lacking a few things, or in final form. Because of this, I gave MEPIS my vote.

I am a big Debian fan in general. I am not a particularly big fan of the Debian installer, but you really do not have to install Debian very often. I feel that it is the Debian software that makes so many of the distributions on this list great to begin with, including the leader in the poll, Ubuntu. However, if I were to nominate another distribution, it would be the sidux distribution, which leverages and tames the cutting edge software in the Debian project from the Sid repositories.

Still, because this is mostly about desktop favorites, I am sticking with MEPIS. I am really proud of the entire community there, and I really encourage people to take a fresh look at SimplyMEPIS and perhaps at the AntiX that you may not have seen or tried before. They are both worthy of attention and use, and that is why I have come back to write here a second time in this thread.

Brian Masinick

I also voted for other

Arch is my distro, followed by gentoo and slack. *BSD is solid but the performance is a little questionable.

wish I had two votes

I gave my vote for *BSD . I love my Anti-x and Mepis installs - they work perfect right off the bat , are fast , and rock solid . Even with a few annoyances setting up PC-BSD and compiling Gnome from ports, it gives me much better audio than any Linux distro I've tried ( especially with Steam games ). Both PC-BSD and Mepis have excellent , multiple software options and great stability . It's a shame to choose one over the other .

Mepis has regained #1 status...

SimplyMEPIS is once again the best Linux desktop distro, and especially
for 'newbies'. [I was gonna add, in my opinion. But, now that I think
of it, it is also the opinion of most everyone who tries it!]

As a real 'distro-junkie', I've tried alot of them...most all the ones
that publish a LiveCD. Mepis's LiveCD is just one thing that sets it
apart...since they pre-install 'ndiswrapper' and about a dozen Win-drivers,
not to mention all the latest NATIVE wifi drivers, it has the BEST chance
of getting online out-of-the-box via wifi of any distro...bar none! [On a few of the
more troublesome ones, it may need a tweak or a prod while under the LiveCD,
so if yours doesn't work, post a quick note in MepisLovers forum, and
the talented crew of users will talk you thru it.]

Some find it hard to believe that this distro is the work of a single
individual (well the kernel and kitting...the repository, artwork, etc,
comes from the whole team of MepisLovers). Version 8 is in late-beta
stage (RC1 as I speak). Take it for a spin and see for yourself.

[My 2nd fav is 'sidux'...like many of the other MepisLovers. Oh, if you
have a 'resource-challenged' older machine, try the lighter-weight
brother of Mepis, called antiX.]

Cheers...

Dave

MEPIS for me

I am a big Debian-based distro fan. I really love three distros: sidux, antiX, and SimplyMEPIS. Because MEPIS is listed and because antiX is part of the MEPIS family, that gives MEPIS two votes from me. Since I only have one vote, I pick MEPIS rather than Debian (a great choice too), or other, which would obscure my interests.

MEPIS it is with two (unofficial) votes.

Brian Masinick
masinick .AT yahoo .DOT com

Arch Linux

I also voted other. Arch Linux is miles ahead of the distros on this list in my opinion.

Other Distro . . .

Guess I should have cast my vote for Debian (Sid). Sidux is my favorite distro at the turn of the new year.

More in Tux Machines

Red Hat: Kubernetes, 'Cloud', and GlusterFS 4.1.0 Release

  • Kubernetes StatefulSet In Action
    Recently, I stumbled upon a StackOverflow question around StatefulSets which made me wonder how well understood they are at large. So I decided to put together a simple stateful app that can be used to experiment with a StatefulSet. In this blog post we will have a closer look at this app and see it in action. If you’re not familiar with StatefulSets, now is a good time for a refresher, consulting the official docs concerning their usage and guarantees they provide.
  • The road to cloud-native applications
    As many organizations do not have the luxury of completely rebuilding their technology foundation or immediately adopting new practices and mindsets, they can embrace gradual yet fundamental shifts in culture, processes, and technology to help support greater velocity and agility. With software increasingly key to how users engage with businesses and how businesses can innovate to stay competitive, organizations should adapt to the new demands of the Digital Economy, such as speeding up application development and delivery. The cloud-native approach describes a way of modernizing existing applications and building new applications based on cloud principles, using services and adopting processes optimized for the agility and automation of cloud computing.
  • GlusterFS 4.1 Released With Performance Monitoring Improvements
    GlusterFS. the network-attached storage file-system focused on cloud computing and more that is developed by Red Hat, is up to version 4.1 as its newest release.
  • Announcing GlusterFS release 4.1.0 (Long Term Maintenance)
    The Gluster community is pleased to announce the release of 4.1, our latest long term supported release.
  • Release notes for Gluster 4.1.0
    This is a major release that includes a range of features enhancing management, performance, monitoring, and providing newer functionality like thin arbiters, cloud archival, time consistency. It also contains several bug fixes.

Games: XENONAUTS 2, Make Sail and More

Programming: Zapcc C++, PHP and Python

  • Some Compiler Performance Benchmarks With The Zapcc Caching Compiler
    Here are some quick benchmarks I ran this week of the newly open-sourced Zapcc C++ caching compiler based upon LLVM/Clang and compared to the upstream Clang performance, GCC, and Ccache with the speed on the original compilation of the benchmark code and then again on a subsequent compilation.
  • PHP 7.3.0 alpha 1 Released
    PHP team is glad to announce the release of the first PHP 7.3.0 version, PHP 7.3.0 Alpha 1. This starts the PHP 7.3 release cycle, the rough outline of which is specified in the PHP Wiki.
  • PHP 7.3 Alpha 2 Released With Many Bug Fixes
    Just shy of two weeks since PHP 7.3 went into alpha, the second alpha release of this upcoming annual feature release to the PHP programming language is now available. PHP 7.3 has been working on several new functions, WebP support within the image create from string function, improved PHP garbage collection, and a variety of other features and improvements. While PHP 7.3 is still open for new features, PHP 7.3 Alpha 2 comes with just bug fixes. Bug fixes for alpha two range from core fixes to various bugs in its ZIP, EXIF, Date, and CLI code, among other areas. The fixes are outlined here.
  • Python virtual environments
    In a short session at the 2018 Python Language Summit, Steve Dower brought up the shortcomings of Python virtual environments, which are meant to create isolated installations of the language and its modules. He said his presentation was "co-written with Twitter" and, indeed, most of his slides were of tweets. At the end, he also slipped in an announcement of his plans for hosting a core development sprint in September.
  • A Python static typing update
    One of the larger features added to Python over the last few releases is support for static typing in the language. Static type-checking and tools to support it show up frequently as topics at the Python Language Summit (PLS) and this year was no exception. Mypy developers Jukka Lehtosalo and Ivan Levkivskyi gave an update on static typing at PLS 2018. Lehtosalo started things off by talking about stub files, which contain type information for libraries and other modules. If you are going to type-check code that uses outside modules, from the standard library or a third-party library, the tool needs to understand the types used in the public interfaces of the library. The type-checking that can be done is limited if there are no stubs for the libraries used.
  • Linux distributions and Python 2
    Python 2.7 will reach its end of life in less than two years—at least for the core development team. Linux distributions need to figure out how to handle the transition given that many of their users are still using that version of the language—and may still be well beyond the end-of-life date. Petr Viktorin and Matthias Klose led a session at the 2018 Python Language Summit to discuss distributions' approaches to deprecating Python 2. Viktorin works for Red Hat and focused on the Fedora distribution. He wants to help figure out how to help the Python downstreams so that Python 2 can be fully discontinued. There are two different ways to do that; either make sure that everyone switches to Python 3 or simply deprecate Python 2 and "wash our hands" of the problem. He would prefer the first alternative. He will be working on this transition for Red Hat as part of his day job and would like to do it in the community as well; that will minimize the need to maintain Python 2 going forward.

Kernel Coverage at LWN (Outside Paywall Now)

  • XArray and the mainline
    The XArray data structure was the topic of the final filesystem track session at the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM). XArray is a new API for the kernel's radix-tree data structure; the session was led by Matthew Wilcox, who created XArray. When asked by Dave Chinner if the session was intended to be a live review of the patches, Wilcox admitted with a grin that it might be "the only way to get a review on this damn patch set". In fact, the session was about the status of the patch set and its progress toward the mainline. Andrew Morton has taken the first eight cleanup patches, Wilcox said, which is great because there was a lot of churn there. The next set has a lot of churn as well, mostly due to renaming. The 15 patches after that actually implement XArray and apply it to the page cache. Those could be buggy, but they pass the radix-tree tests so, if they are, more tests are needed, he said.
  • Filesystem test suites
    While the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM) filesystem track session was advertised as being a filesystem test suite "bakeoff", it actually focused on how to make the existing test suites more accessible. Kent Overstreet said that he has learned over the years that various filesystem developers have their own scripts for testing using QEMU and other tools. He and Ted Ts'o put the session together to try to share some of that information (and code) more widely. Most of the scripts and other code has not been polished or turned into a project, Overstreet continued. Bringing new people up to speed on the tests and how they are run takes time, but developers want to know how to run the tests before they send code to the maintainer.
  • Messiness in removing directories
    In the filesystem track at the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM), Al Viro discussed some problems he has recently spotted in the implementation of rmdir(). He covered some of the history of that implementation and how things got to where they are now. He also described areas that needed to be checked because the problem may be present in different places in multiple filesystems. The fundamental problem is a race condition where operations can end up being performed on directories that have already been removed, which can lead to some rather "unpleasant" outcomes, Viro said. One warning, however: it was a difficult session to follow, with lots of gory details from deep inside the VFS, so it is quite possible that I have some (many?) of the details wrong here. Since LSFMM there has been no real discussion of the problem and its solution on the mailing lists that I have found.
  • Handling I/O errors in the kernel
    The kernel's handling of I/O errors was the topic of a discussion led by Matthew Wilcox at the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM) in a combined storage and filesystem track session. At the start, he asked: "how is our error handling and what do we plan to do about it?" That led to a discussion between the developers present on the kinds of errors that can occur and on ways to handle them. Jeff Layton said that one basic problem occurs when there is an error during writeback; an application can read the block where the error occurred and get the old data without any kind of error. If the error was transient, data is lost. And if it is a permanent error, different filesystems handle it differently, which he thinks is a problem. Dave Chinner said that in order to have consistent behavior across filesystems, there needs to be a definition of what that behavior should be. There is a need to distinguish between transient and permanent failures and to create a taxonomy of how to deal with each type.
  • 4.18 Merge window, part 1
    As of this writing, 7,515 non-merge changesets have been pulled into the mainline repository for the 4.18 merge window. Things are clearly off to a strong start. The changes pulled this time around include more than the usual number of interesting new features; read on for the details.
  • Year-2038 work in 4.18
    We now have less than 20 years to wait until the time_t value used on 32-bit systems will overflow and create time-related mayhem across the planet. The grand plan for solving this problem was posted over three years ago now; progress since then has seemed slow. But quite a bit of work has happened deep inside the kernel and, in 4.18, some of the first work that will be visible to user space has been merged. The year-2038 problem is not yet solved, but things are moving in that direction. If 32-bit systems are to be able to handle times after January 2038, they will need to switch to a 64-bit version of the time_t type; the kernel will obviously need to support applications using that new type. Doing so in a way that doesn't break existing applications is going to require some careful work, though. In particular, the kernel must be able to successfully run a system where applications have been rebuilt to use a 64-bit time_t, but ancient binaries stuck on 32-bit time_t still exist; both applications should continue to work (though the old code may fail to handle times correctly). The first step is to recognize that most architectures already have support for applications running in both 64-bit and 32-bit modes in the form of the compatibility code used to run 32-bit applications on 64-bit systems. At some point, all systems will be 64-bit systems when it comes to time handling, so it makes sense to use the compatibility calls for older applications even on 32-bit systems. To that end, with 4.18, work has been done to allow both 32-bit and 64-bit versions of the time-related system calls to be built on all architectures. The CONFIG_64BIT_TIME configuration symbol controls the building of the 64-bit versions on 32-bit systems, while CONFIG_COMPAT_32BIT_TIME controls the 32-bit versions.