Language Selection

English French German Italian Portuguese Spanish

Early 2007 Fav Distro

*ubuntu
26% (1436 votes)
openSUSE
15% (812 votes)
PCLOS
25% (1396 votes)
Mandriva
7% (403 votes)
Gentoo
5% (277 votes)
Slackware
4% (196 votes)
Debian
6% (331 votes)
Fedora/RH
4% (228 votes)
*BSD
1% (80 votes)
Other
6% (340 votes)
Total votes: 5499

Sceptical of the lot so far

I've tried 7 or 8. PCLOS is in front and there's daylight after the runner-up.

I think another poster hit the nail on the head. The major problem is that programmers and developers have too much say when we need leadership that says "Why not?" instead of why not. The trouble with "software for humanity" is that the leader says "Why not?" and the developers/programmers don't seem to know how.

I'm currently downloading KateOS which impresses me with the amount of information it makes available about package content and the fact that it has an update-OS tool. Lunar Linux also provides an impressive amount of information.

Debian Etch

Etch is my favorite. It is stable and very fast. Booting on my amd64 machine, from GRUB to the KDE login menu, takes 20 seconds. Installation is simple and easy now. And because it's Debian, there are more than 15,000 software packages in the Debian repositories. Those of us in the Linux, free software community enjoy many fine distributions and IMHO, Etch is one of the very best.

re: Debian Etch

I'm seriously considering switching my server over to Debian.

re: Etch

srlinuxx wrote:
I'm seriously considering switching my server over to Debian.

I agree with vonskippy's comment--CentOS or Debian on the server. I've pretty much settled on PCLOS on the Desktop, but I will be taking a long look at both Debian and CentOS this coming Summer when I have the time. I'm leaning toward Debian, but since CentOS is based on RHL, it's got to be solid as a server--after all, server land is Red Hat's Bread & Butter. Also, Red Hat's extensive documentation is a factor.

There are many who claim to use Gentoo effectively in server roles, but I think they are mainly full time tech industry folk. For those who maintain servers in their spare time, CentOS and Debian have to be easier work with.

Experimenting with one of the BSD flavors has always been a vague and distant ambition of mine, but I've never quite found the time or inclination to actually pursue it.

For me, anything with the letters SUSE in it is beyond consideration.

re: Debian

Rock stable, great net install, and you gotta love APT.

But the never ending release date mess, the dunc-tank debacle, developer bickering (and whining about how Ubuntu is stealing their thunder), the whole Ice Weasle hoo-ha, and the fact that support is available only from it's shall we say "wacky" community (i.e. no corp. sponsor), makes Debian hard to love, and certainly does a good job at scaring the suits (i.e. people who make the money decisions) away from warming up to it.

re: Debian

Quote:

Rock stable, great net install, and you gotta love APT.

I'm really wanting a binary distro I think. I'm getting a bit burnt out with all the gentoo hassles on the server. I can deal with wonky portage problems on the desktop, but I don't need broken stuff on the server.

I setup Debian last year when I was trying out some off-site hosts, and it seemed fairly simple and straight forward. I guess that's why I was leaning towards it.

A *bsd would require lots of new learning. Big Grin

re: Debian

CentOS and Debian would be on my short list for a good LAMP server distro. Both have good track records of security and stability. Both have a sufficient choice of server type packages (although CentOS is more like Sarge then Etch when it comes to package versions).

Since I'm guessing you don't have to worry about the politics of your choice, it pretty much boils down to your preference of APT vs YUM and rc.d vs service.

Source distro's seemed to make a lot more sense back in the days of mediocre hardware, but now you can (cheaply) just throw more clock cycles at it to overcome most binary vs custom compiled speed advantages.

Even for a quick study, I think the "time to learn/master/be comfortable" cost for *bsd would be higher then the payoff (especially for something as basic as a LAMP server).

I'm not sure where I'm going yet

I was a very happy Kanotix user until its lead developer, Kano, suddenly decided that basing a distro on Debian Unstable wasn't worth the effort. (Someone also said he wasn't able to support himself doing it like he wanted to.)

Within days, Kanotix's co-developer, SLH, and many of the other former Kanotix devs announced a new distro named Sidux, also based on Debian Unstable (Sid).

This was good because it allowed an easy upgrade path from Kanotix.

On the other hand, I don't particularly like a couple of Sidux's founders, and at this point it feels more like joining a religion than using an operating system.

I really like Debian's package management system, and the more you use it, the more you understand how it works. I'm not terribly interested in using a Debian derivative like *buntu, so I may just end up installing stock Debian Testing.

Distro hopping and evaluation

You've got to try different distros at times--even if it only reaffirms your current choice. But, installing and configuring trial distros can eat up enormous amounts of time. It's why I got involved here at Tuxmachines to start with--I needed to know what distros were worth trying. Of course, Tuxmachines has become a good Linux/OSS news/discussion site as well.

When you hit that sweet spot with a distro, and get your box(es) highly tuned with it, you then encounter those periods with maximum productivity (and entertainment). But software and hardware progress (except for the glaring exception of Vista), and things change. New wants and needs surface. And, sometimes, you try a different distro just for the adventure.

Eye candy is important. Good fonts, backgrounds, images and visual effects make the machine easier and more pleasurable to use, and result in better productivity. People have asked me, "How can you use Windows at work all day, and then, when you get home, the first thing you do is get on your computers at home?" The simple fact is that I use Linux exclusively at home, and I get a genuine sense of pleasure when I sit down to use my Linux machines. They look better, function better, and contribute toward my getting more work done.

Red Hat and Fedora works best for me.

My distro of choice has always been Redhat/Fedora. I use RHEL/CentOS/Fedora on almost all my server projects (mainly cluster farms doing molecular topography rendering). I never saw the advantage of distro-hopping, thinking it's better to dig in and master one, then hop around and be mediocre at many.

Until recently, never really worried about desktop linux - always used (gasp!) windows. As a business, the price of licensing is not even a blip on the spreadsheet when compared to interoperability between vendors and clients, application availability, and user learning curve costs. Now with Vista (what a major piece of suck that OS is) we're looking down the road to what our long term options are.

Unfortunately, Fedora has a lot of weak spots when it comes to the desktop. I tried PCLinuxOS, but they're pretty serious about being a desktop only distro, and since we do dev work on our desktops, they had way to much desktop-only inertia to overcome. I tried OpenSUSE, but wow, that was soooooo different from how RedHat/Fedora works, and I just couldn't learn to love YAST. Ubuntu always just rubbed me the wrong way with their "you're too stupid to trust with root" mentality.

So I'm either stuck with FC6, while waiting for FC7 to be released (end of April), or..... I might be learning to love Linux Mint. Like PCLinuxOS, it's a boutique distro with some very nice eye candy, multimedia ready out of the box, and a nice menu and control panel (wireless wth wpa-psk is even pretty painless to get working). Unlike PCLinuxOS it's fully capable of doing dev work on, or even running server apps using the vast library of Ubuntu applications and support. It still has that major sucky "no root" thing going on, but it's easy enough to setup a real root account so it's a minor whine.

So although I've always been a die hard RedHat/Fedora fan, and never into Distro hopping, I think I'll be taking FC6 off my laptop and replacing it with Linux Mint v2.2beta014. I haven't gone completely mental (at least not today) as I have no plans to dumping RHEL/CentOS from out server farms in favor of Debian/Ubuntu/Minty/Whatever.

My choice's Mandriva...

I've tried so many distros that i cannot even remember them Smile But every time i returned to my first love, Mandriva. I don't know why... Maybe it's because i've been using this distro since version 7.3, because i find it the easiest to use, because the Mandriva Linux community from Romania is really active and can provide answer to many questions, because i'm used to rpm/urpmi package management... Mandriva has lost the first place it had some years ago, and it seems like it is in great financial trouble, but it still is my choice. And will allways be, i guess. I'm waiting for PCLinuxOS 2007 final to see if it can change my opinion... But it's unlikely.

re: My choice's Mandriva...

Yeah, they're a sentimental favorite here too. They were the ones who rescued me from the evil empire, at version 7.2. I had a coupla near misses with 7.0 and 7.1, but 7.2 did it. I was hooked. I stuck with them until switching to Gentoo in Nov of 2003. I've been using that as my main desktop ever since. Portage used to work like clockwork, but it's becoming more and more buggy the last year or so. I'm not thinking of switching or anything, but the honeymoon is definitely over. Big Grin

I've been enjoying the testing releases of PCLOS 2007 on my laptop since they've been available. I ran openSUSE on it for a while, but never could get the fonts to purty up. Fonts look so gorgeous in PCLOS.

Tried many, ended up with Slackware

Prior to Slackware, I tried many distros but could not find any that did it all (at least for my wants). All I really need is desktop system that runs Kino (new baby = much raw dv), MPlayer and plugin for video, samba for printer and file sharing, and most any basic home applications. I also run a development server with php/mysql that I turn on when needed.

Tried PcLos once and thought I finally found the one, but after some use it seemed somewhat bloated. Tried MiniMe, but on building my system, I found that got somewhat buggy -- my guess it didn't handle dependencies correctly.

Then despite a frustrating experience with Slack in my early Linux days, I thought I'd give it another try. Turned out great. A bit time-consuming in the initial configuration that included compiling a 2.6 kernel. Ever since I got my system built, it's run like a dream -- never buggy, always fast and just as rock solid as its reputation. Basically a machine that I don't have to screw around until the next release, and if that release doesn't have any "gotta haves", I probably won't even worry about that.

As long as it's Linux

I prefer to consider this the fun part on the distro war ... a conflict that will eventually put Linux where Microsoft is.

As for my personal preference, I got happily stuck with PCLinuxOS after years of trying out (and still is) most of the Linux distros that are released. And now that PCLinuxOS 2007 Final is just around the bend, I hope it can give Ubuntu a run for its money.

Registered Linux User No. 401868

My favorite distribution for 2007

I used to use SuSE, Mandriva and Ubuntu in 2004/2005 but in 2006, I discovered ArchLinux. I'm still using it now in 2007 and I haven't looked back. My only regret is that I didn't discover this excellent distribution earlier. Smile

There's no real contest in my book

I've just installed Vector 5.8 and I have good memories of Zenwalk but PCLOS still wins. Now that I've dropped the nVidia driver, everything is looking good and proportional again. It's nice to be back.

More in Tux Machines

XFS / EXT4 / Btrfs / F2FS / NILFS2 Performance On Linux 5.8

Given the reignited discussions this week over Btrfs file-system performance stemming from a proposal to switch Fedora on the desktop to using Btrfs, here are some fresh benchmarks of not only Btrfs but alongside XFS, EXT4, F2FS, and for kicks NILFS2 was also tossed into the mix for these mainline file-system tests off the in-development Linux 5.8 kernel. With the yet-to-be-approved proposal specifically to use Btrfs for desktop installations, for this testing a single NVMe solid-state drive was used for testing in jiving with conventional desktop use-cases rather than any elaborate RAID setups, etc. Each of the tested file-systems were carried out with the default mount options in an out-of-the-box manner. Read more

Proprietary Software Leftovers

  • Ransomware Gangs Don’t Need PR Help

    Overall, I’ve tried to use each story to call attention to key failures that frequently give rise to ransomware infections, and to offer information about how other companies can avoid a similar fate.

    But simply parroting what professional extortionists have posted on their blog about victims of cybercrime smacks of providing aid and comfort to an enemy that needs and deserves neither.

  • Ransomware gangs are doing their homework before encrypting corporate data

    In the last three months, the criminal hackers behind the Maze ransomware have attacked two big IT service providers, one of which is a Fortune 500 company. Other ransomware gangs have hit big corporate targets, and in so doing are first locking computer systems and then publicly shaming companies that don’t pay up by dumping their data.

    For corporations that do pay the ransom, the pain sometimes isn’t over. There is no guarantee that the decryption key handed over by the attacker works, said Wendi Whitmore, global lead at IBM Security X-Force.

  • Zoom Will Offer End-To-End Encryption To All Its Users [Ed: But no. You cannot trust proprietary software to do what it claims to do.]

    The pandemic has moved more activities online--and specifically onto Zoom--than ever before. For an enterprise tool like Zoom, that means new users that the company never expected and did not design for, and all the unanticipated security and privacy problems that come with that sudden growth. Zoom's decision to offer end-to-end encryption more widely is especially important because the people who cannot afford enterprise subscriptions are often the ones who need strong security and privacy protections the most. For example, many activists rely on Zoom as an organizing tool, including the Black-led movement against police violence. To use Zoom's end-to-end encryption, free users will have to provide additional information, like a phone number, to authenticate. As Zoom notes, this is a common method for mitigating abuse, but phone numbers were never designed to be persistent all-purpose individual identifiers, and using them as such creates new risks for users. In different contexts, Signal, Facebook, and Twitter have all encountered disclosure and abuse problems with user phone numbers. At the very least, the phone numbers that users give Zoom should be used only for authentication, and only by Zoom. Zoom should not use these phone numbers for any other purpose, and should never require users to reveal them to other parties.

  • Desklab Portable USB-C Monitor

    I bought a mini-DisplayPort to HDMI adapter and for my first test ran it from my laptop, it was seen as a 1920*1080 DisplayPort monitor. The adaptor is specified as supporting 4K so I don’t know why I didn’t get 4K to work, my laptop has done 4K with other monitors. The next thing I plan to get is a VGA to HDMI converter so I can use this on servers, it can be a real pain getting a monitor and power cable to a rack mounted server and this portable monitor can be powered by one of the USB ports in the server. A quick search indicates that such devices start at about $12US. The Desklab monitor has no markings to indicate what resolution it supports, no part number, and no serial number. The only documentation I could find about how to recognise the difference between the FullHD and 4K versions is that the FullHD version supposedly draws 2A and the 4K version draws 4A. I connected my USB Ammeter and it reported that between 0.6 and 1.0A were drawn. If they meant to say 2W and 4W instead of 2A and 4A (I’ve seen worse errors in manuals) then the current drawn would indicate the 4K version. Otherwise the stated current requirements don’t come close to matching what I’ve measured.

Raspberry Pi 4's Vulkan Driver and More

  • Alejandro Piñeiro: v3dv status update 2020-07-01

    Input attachment is one of the main sub-features for Vulkan multipass, and we’ve gained support since the announcement. On Vulkan the support for multipass is more tightly supported by the API. Renderpasses can have multiple subpasses. These can have dependencies between each other, and each subpass define a subset of “attachments”. One attachment that is easy to understand is the color attachment: This is where a given subpass writes a given color. Another, input attachment, is an attachment that was updated in a previous subpass (for example, it was the color attachment on such previous subpass), and you get as a input on following subpasses. From the shader POV, you interact with it as a texture, with some restrictions. One important restriction is that you can only read the input attachment at the current pixel location. The main reason for this restriction is because on tile-based GPUs (like rpi4) all primitives are batched on tiles and fragment processing is rendered one tile at a time. In general, if you can live with those restrictions, Vulkan multipass and input attachment will provide better performance than traditional multipass solutions. If you are interested in reading more details on this, you can check out ARM’s very nice presentation “Vulkan Multipass mobile deferred done right”, or Sascha Willems’ post “Vulkan input attachments and sub passes”. The latter also includes information about how to use them and code snippets of one of his demos. For reference, this is how the input attachment demos looks on the rpi4...

  • Raspberry Pi 4's Vulkan Driver Is Now More Usable - Supporting More Features

    The "V3DV" Vulkan driver being developed by Igalia under contract with the Raspberry Pi Foundation has offered a status update on this official driver for the Raspberry Pi 4. The V3DV effort is the modern, official Vulkan driver for the Raspberry Pi 4 and not to be confused with the third-party Vulkan driver for pre-RPi4 hardware or the former Raspberry Pi 4 Vulkan effort. This is the new driver being developed and what ultimately will be the official driver option moving forward.

  • Code Jetpac’s rocket building action | Wireframe #40

Free/Libre/Open Source Software Leftovers

  • Copyright enforcement with Dr. Miriam Ballhausen

    We invited Dr. Miriam Ballhausen to talk with us about copyright enforcement. She is a German lawyer with the focus on software, data protection, copyright law and specifically Free Software copyright. This is the sixth regular episode of the Software Freedom Podcast for which we invite experts from our community. In this sixth episode of the Software Freedom Podcast we talk about Free Software copyright enforcement with our guest Dr. Miriam Ballhausen. Dr. Miriam Ballhausen is a German laywer and is specialised in Free Software copyright questions. Together we cover the basics about Free Software licensing and discuss, how Free Software copyright can be enforced, what are the steps to enforce it and why it is often enforced in Germany. We also explore how the REUSE project could help with being in compliance with Free Software licenses.

  • IBM Has Open Sourced Its Edge Device Platform and Wishes AWS and Microsoft Got On Board

    IBM's Open Horizon is meant to make it easier to manage thousands of IoT devices as edge computing nodes.

  • Open-source contact tracing, part 1

    The main goal of COVID-19 tracing applications is to notify users if they have been recently in contact with an infected person, so that they can isolate themselves or seek out testing. The creation of the applications is usually supported by governments, with the development performed by health authorities and research institutions. The Wikipedia page for COVID-19 apps lists (as of early June 2020) at least 38 countries with such applications in use or under development, and at least eight framework initiatives. The applications trace the people that the user has had contact with for a significant period (for example, 15 minutes) with close physical proximity (a distance around one meter). The complete tracing system usually consists of an application for mobile phones and the server software. For the distance measurement and detecting the presence of other users, GPS and Bluetooth are the technical solutions used in practice. GPS only appears in a small number of projects because it does not have enough precision, especially inside buildings. It also does not work in enclosed spaces like underground parking and subways. Most countries have chosen to develop a distance measurement using Bluetooth, generally the Bluetooth Low Energy (BLE) variant, which uses less energy than the classical version. This is important as the distance measurement is done by mobile phones, and so Bluetooth will need to be active most of the time. The Bluetooth protocol was not designed for these kinds of tasks, though, so research has been done on ways to measure distance accurately. A report [PDF] from the Pan-European Privacy-Preserving Proximity Tracing project shows that it is possible to measure distance using BLE signal strength, specifically received signal strength indication (RSSI). In a contact-tracing system using Bluetooth, the distance measurement is made by the two phones communicating using a specific message format. Since the formats differ between applications, communication is only guaranteed to work if both phones are using the same application.

  • More alternatives to Google Analytics

    Last week, we introduced the privacy concerns with using Google Analytics (GA) and presented two lightweight open-source options: GoatCounter and Plausible. Those tools are useful for site owners who need relatively basic metrics. In this second article, we present several heavier-weight GA replacements for those who need more detailed analytics. We also look at some tools that produce analytics data based on web-server-access logs, GoAccess, in particular.

  • GNU Taler news: Exchange independent security audit report published

    We received a grant from NLnet foundation to pay for an external security audit of the GNU Taler exchange cryptography, code and documentation. CodeBlau now concluded their audit. You can find the final report here. We have compiled a preliminary response detailing what changes we have already made and which changes we are still planning to make in the future. We thank CodeBlau for their work, and NLnet and the European Commission's Horizion 2020 NGI initiative for funding this work.