Language Selection

English French German Italian Portuguese Spanish

What if Linux Distros were Women?

Filed under
Humor

I've used quite a few linux distros in my time. Recently it occurred to me what they would look like if they were beautiful, attractive women. I think perhaps I've spent too much time on the computer, eh? Anyway, I've made a list. Tell me what you think!

If Linux Distros were women:

Redhat:
Redhat would be a gorgous, expensive hooker. She'd do whatever you wanted, and do it well. You'll be left satisfied, but you'll have no idea how she did it. If you needed help with her, there are many paid phone numbers you can call to chat about her.

Fedora Core:
Fedora Core would be just as good as Redhat, but wouldn't cost you a dime.

CentOS:
CentOS would look just like Fedora Core, except... Except it would look just like Fedora Core.

Suse:
Suse would be a moderately attractive hooker. She wouldn't be quite as good as Redhat, but there are still lots of fun paid phone numbers for you to call.

OpenSuse:
OpenSuse would be every bit as good as Suse, but wouldn't cost you a penny.

Debian Sarge:
Debian Sarge would be a 50 year old lady. She'd cook, clean, and iron better than any other the other linux distros, would have no moodswings whatsoever, and would have a life expectancy of 157 years. There'd be plenty of people willing to help you maintain her, and they'd all be fairly knowledgable.

Debian Etch:
Debian Etch would be exactly like Debian Sarge, except that she'd be the spritely young age of 40.

Read More Here.

Now we just need pictures.

'Nuff said. Smile

(And what's wrong with 40-year-olds anyway?!)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Red Hat News

  • An Open Source Load Balancer for OpenShift
    A highly-available deployment of OpenShift needs at least two load balancers: One to load balance the control plane (the master API endpoints) and one for the data plane (the application routers). In most on-premise deployments, we use appliance-based load balancers (such as F5 or Netscaler).
  • Red Hat Beefs Up Platform as a Service Suite
    Red Hat has begun shipping Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service (iPaaS) offering, Fuse Online. With Fuse 7, the vendor says expanding its integration capabilities natively to Red Hat OpenShift Container Platform, an enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • Red Hat ‘Fuses’ Low Code Development and Data Integration
    Red Hat, a provider of open source solutions, has announced Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service offering, Fuse Online. With Fuse 7, Red Hat is expanding its integration capabilities natively to Red Hat OpenShift Container Platform, a comprehensive enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • The GPL cooperation commitment and Red Hat projects
    As of today, all new Red Hat-initiated open source projects that opt to use GPLv2 or LGPLv2.1 will be expected to supplement the license with the cure commitment language of GPLv3. The cure language will live in a file in the project source tree and will function as an additional permission extended to users from the start. This is the latest development in an ongoing initiative within the open source community to promote predictability and stability in enforcement of GPL-family licenses. The “automatic termination” provision in GPLv2 and LGPLv2.x is often interpreted as terminating the license upon noncompliance without a grace period or other opportunity to correct the error in compliance. When the Free Software Foundation released GPLv2 in 1991, it held nearly all GPL-licensed copyrights, in part a consequence of the copyright assignment policy then in place for GNU project contributions. Long after the Linux kernel and many other non-GNU projects began to adopt the GPL and LGPL, the FSF was still the only copyright holder regularly engaged in license enforcement. Under those conditions, the automatic termination feature of GPLv2 section 4 may have seemed an appropriate means of encouraging license compliance.
  • Monness Believes Red Hat (NYSE: RHT) Still Has Room to Grow
  • Comparing Red Hat (RHT) & Autoweb (AUTO)
  • As Red Hat (RHT) Share Value Rose, Calamos Advisors Upped Its Position by $300,831; Chilton Capital Management Increases Stake in Equinix (EQIX)
  • Blair William & Co. IL Buys 23,279 Shares of Red Hat Inc (RHT)

Total War: WARHAMMER

Red Hat changes its open-source licensing rules

From outside programming circles, software licensing may not seem important. In open-source, though, licensing is all important. So, when leading Linux company Red Hat announces that -- from here on out -- all new Red Hat-initiated open-source projects that use the GNU General Public License(GPLv2) or GNU Lesser General Public License (LGPL)v2.1 licenses will be expected to supplement the license with GPL version 3 (GPLv3)'s cure commitment language, it's a big deal. Read more

Android Leftovers