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

GNU: The GNU C Library 2.28 and Guix on Android

  • Glibc 2.28 Upstream Will Build/Run Cleanly On GNU Hurd
    While Linux distributions are still migrating to Glibc 2.27, in the two months since the release changes have continued building up for what will eventually become the GNU C Library 2.28. The Glibc 2.28 work queued thus far isn't nearly as exciting as all the performance optimizations and more introduced with Glibc 2.27, but it's a start. Most notable at this point for Glibc 2.28 is that it will now build and run cleanly on GNU/Hurd without requiring any out-of-tree patches. There has been a ton of Hurd-related commits to Glibc over the past month.
  • Guix on Android!
    Last year I thought to myself: since my phone is just a computer running an operating system called Android (or Replicant!), and that Android is based on a Linux kernel, it's just another foreign distribution I could install GNU Guix on, right? It turned out it was absolutely the case. Today I was reminded on IRC of my attempt last year at installing GNU Guix on my phone. Hence this blog post. I'll try to give you all the knowledge and commands required to install it on your own Android device.
  • GNU Guix Wrangled To Run On Android
    The GNU Guix transactional package manager can be made to run on Android smartphones/tablets, but not without lots of hoops to jump through first.

Node.js 10.9 and npm milestone

  • Open Source Node.js Hits v10, with Better Security, Performance, More
    Speaking of which, the brand-new Node.js 10.0 is expected to soon support npm version 6 (currently Node.js ships with npm 5.7.x). The company npm Inc., which maintains the npm software package management application, today announced that major update, called npm@6. The npm company said its JavaScript software installer tool includes new security features for developers working with open source code.
  • Announcing npm@6
    In coordination with today’s announcement of Node.js v10, we’re excited to announce npm@6. This major update to npm includes powerful new security features for every developer who works with open source code. Read on to understand why this matters.

Openwashing: Sony, Scality and Ericsson

Voyage/Open Autonomous Safety (OAS) Now on GitHub

  • Voyage open-sources autonomous driving safety practices
    Dubbed Open Autonomous Safety, the initiative aims to help autonomous driving startups implement better safety-testing practices. Companies looking to access the documents, safety procedures and test code can do so via a GitHub repository.
  • Open-Sourcing Our Approach to Autonomous Safety
    Without a driver to help identify and mitigate failures, autonomous vehicle systems need incredibly robust safety requirements and an equally comprehensive and well-defined process for analyzing risks and assessing capabilities. Voyage models its safety approach after the ISO 26262 standard for automotive safety, taking the best practices from the automotive industry and applying them to autonomous technology. The automotive industry continues to reach for new levels of safety in manufacturing vehicles, and we are inspired by that approach.
  • Startup Voyage Wants to Open Source Self-Driving Car Safety
    Under what the company calls its Open Autonomous Safety initiative, Voyage is publishing information on its safety procedures, materials, and test code in a series of releases. The goal is to create an open-source library of safety procedures that multiple companies can use as a standard, a Voyage blog post said.
  • This startup’s CEO wants to open-source self-driving car safety testing
    The initial release, which Voyage calls Open Autonomous Safety (OAS), will take the form of a GitHub repository containing documents and code. The functional safety requirements are Voyage's interpretation of the ISO 26262 standard for automotive safety, updated for autonomous vehicles. "This is our internal driving test for any particular software build," says Cameron. "It lets us evaluate our designs and look for the different ways they can fail in the real world."