Language Selection

English French German Italian Portuguese Spanish

Further thoughts on Mandriva...

Filed under
MDV

Some good (and a little not-so-good) comments on the previous Mandriva post. I wanted to point out just a few things...

A few folks made some assumptions about my choice of distros, or experiences with Mandriva. I've used Mandriva, though I admit it's been a few years. I used Mandrake before it for quite a while. It never really caught my fancy, sorry. That doesn't mean Mandriva isn't the bee's knees for a lot of other people, but it never really grabbed me as spectacular.

I often say that distributions are like underwear: No one can tell you what will make your butt comfortable. Some people dig on boxers, other people wear briefs, and some folks go commando. There's no a right or wrong, but just what works for you. Unfortunately, Mandriva skivvies just haven't caught on with enough people willing to part with cash to make it a working business. It happens.

Back in the day, long before there was an Ubuntu, there was Stormix -- a nifty and easy to use (at the time) distro based on Debian. (Sound familiar?) They didn't catch on, the company failed -- and Linux as a whole survived. Sad for the company and its users, but life went on and I don't know too many people still pining away for Stormix.

rest here




All Mandriva needs is new

All Mandriva needs is new management and a good marketing department.

re: All Mandriva needs

How does even a great marketing department sell something that sounds like Nair® for gay men?

Open source projects need to get past the 5 nerds playing D&D naming scheme if they ever want to be taken serious in the real world.

Comment viewing options

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

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more