Language Selection

English French German Italian Portuguese Spanish

Mandriva Linux 2011TP (Tech Preview) - Quick Look

Filed under
Reviews

After laying-off a significant portion of its employees, is Mandriva going to remain a viable distribution? While many distros, including Mandriva, are furiously working on their Spring 2011 releases, Mandriva announced a two-week slip from their previously announced release dates. As a compensation, Mandriva gathered up its packages from its 2011 development repositories (called "Cooker"), and released a pre-alpha 2011 TP (Technology Preview) iso. The coming Alpha version is due to be released February 14 with Alpha2 slated to be released February 28. So, here's a quick report on the Technology Preview release, and how things are shaping up.

Many of Mandriva's recently laid off employees went on to form a fork of Mandriva called "Mageia". According to Susan Linton (Owner, operator and exalted grand pubah of Tuxmachines.org), Mageia Alpha1 is also due to be released mid February. It will be interesting to compare the two Alpha1 releases.

But, back to the Mandriva TP release. I downloaded the x86-64 bit TP ISO version yesterday (Feb 7), burned it, and proceeded to install it on "newton", my Acer Aspire 6930 Laptop (3 GB Ram, Nvidia 9600M GS video card, 7200 RPM hard disk (an upgrade after initial purchase), Intel wireless, and 1366x768 display).

The install went smoothly, except when rebooting--Mandriva TP did not pick-up my Windows 7 Partition in the boot window. The Win7 partition is still there--in fact, I can access the Win 7 files from Linux, so no worries (I rarely need to use Win 7).

Mandriva has updated its RPM system from RPM 4.6 to RPM 5. Because of the differing RPM versions, those wanting to update their older 2010 Mandriva installs to Cooker should be forwarned, there are extra steps to be taken. If you're one of these people, check-out the procedure here.

My first step, after installation was to update the TP release to the current state of Cooker (as of Feb 7). Then I installed the newest and latest KDE 6.0 stuff.

Like many distros lately, the open source Nouveau driver for nvidia video is installed by default. In fact, there is no proprietary Nvidia driver in Mandriva's cooker repositories. So, I went to Nvidia's web site, downloaded their proprietary driver, and compiled it for the TP kernel (Linux 2.6.37). Much to my surprise, this worked well. When the Nouveau driver performance becomes congruent to Nvidia's proprietary driver, I will switch to the Nouveau driver. Actually, the Nouveau driver performed fairly well, and is getting closer in quality to Nvidia's driver. I was surprised at how well the KDE desktop effects worked under the Nouveau driver.

Again, to my surprise, as Mandriva's 2011 Alpha 1 release approaches, I find it to be remarkably stable, fluid, and capable from the KDE side. The only issues I've encountered are from the flaky Firefox beta (4.0 beta10) browser, which is why I'm blogging this to Tuxmachines from the Rekonq browser.

In fact, I'm going to keep this (very) early version of Mandriva 2011 installed on my laptop, and update the packages daily.

UPDATE: An update of D-Bus BORKED this system yesterday. Lost my sound. Other issues. Looks like I'll wait for the 2011 Alpha1 release.

More in Tux Machines

today's howtos

Security Leftovers

  • Java and Python FTP attacks can punch holes through firewalls
    The Java and Python runtimes fail to properly validate FTP URLs, which can potentially allow attackers to punch holes through firewalls to access local networks. On Saturday, security researcher Alexander Klink disclosed an interesting attack where exploiting an XXE (XML External Entity) vulnerability in a Java application can be used to send emails.
  • Microsoft: no plans to patch known bugs before March [Ed: Microsoft is keeping open 'back doors' that are publicly known about, not just secret ones]
    Microsoft has no plans to issue updates for two vulnerabilities, one a zero-day and the other being one publicised by Google, before the scheduled date for its next round of updates rolls around in March. The company did not issue any updates in February, even though it had been scheduled to switch to a new system from this month onwards. It gave no reason for this, apart from saying: "This month, we discovered a last minute issue that could impact some customers and was not resolved in time for our planned updates today. "After considering all options, we made the decision to delay this month’s updates. We apologise for any inconvenience caused by this change to the existing plan." The Google-disclosed bug was made public last week, and is said to be a flaw in the Windows graphic device interface library that can be exploited both locally and remotely to read the contents of a user's memory.
  • Microsoft issues critical security patches, but leaves zero-day flaws at risk
    Microsoft has patched "critical" security vulnerabilities in its browsers, but has left at least two zero-day flaws with public exploit code. The software giant released numerous patches late on Tuesday to fix flaws in Adobe Flash for customers using Internet Explorer on Windows 8.1 and later, as well as Edge for Windows 10.

Red Hat News

  • Why upstream contributions matter when developing open source NFV solutions.
    When software is developed using open source methods, an upstream repository of the code is accessible to all members of the project. Members contribute to the code, test it, write documentation and can create a solution from that code to use or distribute under license. If an organization follows the main stream or branch of the upstream code their solution will receive all the changes and updates created in the upstream repository. Those changes simply “flow down” to the member’s solution. However, if a member organization forks the code — if they create a solution that strays from the main stream — their solution no longer receives updates, fixes and changes from the upstream repository. This organization is now solely responsible for maintaining their solution without the benefit of the upstream community, much like the baby salmon that took a tributary and then have to fend for themselves rather than remain in the main stream and receive the benefit and guidance of the other salmon making their way to the ocean.
  • HPE and Red Hat Join Forces to Give Customers Greater Choice for NFV Deployments
    Hewlett Packard Enterprise ( NYSE : HPE ) and Red Hat, Inc. ( NYSE : RHT ) announced today they are working together to accelerate the deployment of network functions virtualization (NFV) solutions based on fully open, production-ready, standards-based infrastructures. HPE plans to offer ready-to-use, pre-integrated HPE NFV System solutions and HPE Validated Configurations incorporating Red Hat OpenStack Platform and Red Hat Ceph Storage for communications service providers (CSPs).
  • Red Hat Joins the OpenPower Foundation
    As part of our commitment to delivering open technologies across many computing architectures, Red Hat has joined the OpenPOWER Foundation, an open development community based on the POWER microprocessor architecture, at the Platinum level. While we already do build and support open technologies for the POWER architecture, the OpenPOWER Foundation is committed to an open, community-driven technology-creation process – something that we feel is critical to the continued growth of open collaboration around POWER.
  • Buy, Sell or Hold? Analysts Approach: HCA Holdings, Inc. (HCA), Red Hat, Inc. (RHT)?

Linux and FOSS Events