Home Business IT Open Source Mandriva may be forced to shut down

One scheme proposed a capital increase of €4 million reserved for two main shareholders, Town Area and LinLux, and reduction of capital of €6.3 million carried by the two.


In the event of either of these shareholders not being agreeable, the capital increase of €4 million was to be reserved only for shareholders who had subscribed to the capital increase and the reduction of capital of 6.3 million would have to be supported by the two main shareholders.

If the company shuts shop, the distribution, which is developed mainly by Rosa Labs and the Brazilian company, Conectiva, which was acquired by Mandriva six years ago, may continue to be released.

But for users there is a fallback - in September 2010, some developers forked the Mandriva distribution, with the new distro being known as Mageia.

Mandriva began life in the late 90s as Mandrake Linux. With Red Hat Linux as its base but the KDE desktop environment instead of GNOME, it was at times known as "Red Hat with KDE"

A change of name was effected in 2005 after it lost a case filed by Hearst Corporation which had the rights to the name Mandrake. From MandrakeSoft it became Mandriva, coinciding with the acquisition of Conectiva, another GNU/Linux company based in Brazil.

Mandriva (then known as Mandrake) filed for bankruptcy in 2003 and emerged from that state the next year. In 2008, the company was badly affected by the global financial crisis and had to jettison all its external contributors.

FREE - SYDNEY & MELBOURNE BUSINESS INTELLIGENCE EVENTS

The Holy Grail of the Business Intelligence (BI) industry – pervasive deployments and widespread end-user adoption – has remained an illusive dream for years. Until now!

REGISTER & SECURE YOU PLACE / BRING A FRIEND

Melbourne - venue Captain Melville’s CBD 2:30 – 6:00pm, Tuesday 28th April

Sydney - venue Redoak CBD 2:30 – 6:00pm, Thursday 30th April

DON'T MISS OUT - MELBOURNE REGISTER NOW!

DON'T MISS OUT - SYDNEY REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect