Language Selection

English French German Italian Portuguese Spanish

Mandriva Linux 2006.1-0.3

Filed under
MDV
Reviews
-s

With all the changes in Mandrivaland this year, it was nice that one thing remained the same, Mandriva's tradition of releasing a Christmas Cooker Snapshot. We had heard rumors of a release for club members, so Tuxmachines is particularly thrilled Mandriva released something for the general public too. Glancing through the changelog we see a lot of bug fixes and software updates. Should you upgrade? This is what we found when we booted up our sparking new 2006.1-0.3 install.

For those new to Linuxville, Mandriva Linux is one of the oldest Linux distributions around. It was first released in 1998 as Mandrake Linux and featured the KDE desktop environment. It was based highly on Redhat Linux, which at the time only offered the Gnome desktop. Mandrake improved upon Redhat, and soon added their own "drak"tools to their distro. In the following years, they became one of the most popular distros available. They recently acquired Conectiva and Lycoris Linux and changed their name to Mandriva. Even though there is still a version available for free (in both senses of the word), they highly encourage users to join their MandrivaClub, to help support the company and development, and to receive added benefits such as first to receive releases, proprietary drivers, wonderful support, updates and extra applications. Mandriva Linux 2006 was released in September 2005 and a free version was made public in October. This month brings today's focus, Mandriva Linux 2006.1-0.3 (Beta), December Cooker snapshot. This is usually the first stop on the long road to the next release.

Years ago, when I installed each Mandrake as they released new versions, the Christmas Cooker Snapshot, as we called it then, was a welcome mid-cycle release. I always did a fresh install and was usually quite pleased. That was in the day of Mandrake's philosophy of "bleeding edge technology" and many times brought the latest and greatest of all our favorite apps. Later on after I began running and updating cooker on a daily basis, many times the new release introduced bugs not apparent on the daily upgraded system. For example, some changed configs, broken symlinks, or lost libraries didn't show up on the daily upgraded system, but were more apparent on a fresh install. So, should the average guy upgrade/install this December Cooker Snapshot?

The snapshot is available in your choice of 3 ~700mb isos for either the i586 or x86_64 archs or in a one i586 Live CD. I went with the 3 isos for i586 and did a hard drive install after unpacking the isos and burning the boot.img to cdr.

The installer is the same great Mandriva installer we've all probably memorized by now. It's appearance is retained from 2006. As per usual, it walks the user through the configuration, install, and post-configuration with simple easy-to-follow steps. 996 packages installed in about 5 minutes, although two failed. I was doing a hard drive install from unpacked isos, yet it still had problems with the vim-common and xorg-server packages. I wasn't concerned about the vim-common, but I was a bit worried about xorg. After the package installation one reaches the Summary screen. This, as you might recall, is where one actually reconfigures their system if needed. Areas include System, hardware, network, boot, and start-up services. Here I encountered my other worrisome install bug. The start-up services dialog was blank. There were no services listed at all. I hoped it was a bug in the configuration and not actually in the filesystem. I mounted that partition and saw that the rcX.d directories contained the appropriate symlinks to the services in /etc/init.d, and this was confirmed with the start up of my new Mandriva Cooker system. However, the problem with xorg might be a showstopper for some folks as x was not complete. It had trouble finding some of its need modules and could not start.

I set up a cooker mirror in urpmi and installed xorg-X11-server (and vim-common while I was at it). This fixed that little problem and the X server was able to start after that. So, if this happens to you and you wish a quick fix, type:

urpmi.addmedia uninett ftp://ftp.uninett.no/pub/Linux/MandrivaLinux/devel/cooker/i586/media/main

and then:

urpmi.addmedia contrib ftp://ftp.uninett.no/pub/Linux/MandrivaLinux/devel/cooker/i586/media/contrib

(Pick a mirror close to you for best results, this is just an example). Once that is done, just type:

urpmi --media uninett,contrib xorg-X11-server

They have updated Xorg to the newly released 6.9.0, KDE 3.5, Gnome 2.12, and gimp 2.3.5; as well as apache 2.2.0 and MySQL 5.0.x. Here is a full rpmlist of applications available on the cds. Once you set up your urpmi mirrors, you'll have access to the full range of software, including OpenOffice.org 1.5 or 2.0.


I was glad to see the new release of xorg included, however, all was not perfect. Using the "nv" drivers only allowed one of my connected monitors to function = my 2nd monitor (monitor1 or crt-1). When using the nvidia drivers I could use twinview as I prefer, and with vesa I would get a "cloned" setup (my second choice). So, although the 6800 chipset lockup is now fixed in the "nv" drivers, it's still has some problems. Further test showed this was not a Mandriva problem (if it's even considered a problem), but yet still another bug with xorg.

The greatest update to be included in the cooker snapshot is KDE 3.5. It was wonderfully stable here during operation and even included options for my dual monitor setup (when used). The only problem encountered was a kicker/panel crash upon "logout." Again, I've read about this before and it is a kde problem, not a Mandriva bug.

    

Also updated is gnome to 2.12. I had problems with gnome here. It would start, but it complained about the settings deamon and as such I would not be able to set an user configurations. Another aspect of this was whatever default settings (background, icons, etc) Mandriva may have chosen did not show up either. I've seen various distros have problems in some manner or other with several gnome versions lately. This must be a picky bunch of packages to compile.

    

Gnucash bombed out as well. While testing the various applications available, most performed excellently except for Gnucash. It would not start up. Instead I'd see a flash of splash screen and then it was gone. All others did fine.

Kaffine complained about win32codecs & dvdcss being missing, but other than that, it functioned as designed. Xine did okay with avis and mpegs as well. The music cd players did very well too.

    

I noticed a new bookmark toolbar shortcut to Skype telephony service. This must be in preparation for their integration of Skype technology. Although my search was probably hindered by my lack of knowledge in this area, I wasn't able to find any indication that was included in our test package today.


Another problem or two was encountered with the file search tools. The gnome-search died upon execution and kat couldn't index due to not being able to start the Kat deamon. The old stand-by search functioned well tho.


So, all in all, it's a cooker snapshot. There are bugs here and there, some not Mandriva's fault per se, but none that were really show stoppers. If you'd like a cooker partition in addition to your regular stable install, this release is still a good way to get started. Or perhaps, if you don't mind a few little bugs here and there, then this release can get you on the cutting edge with it's xorg 6.9 and kde 3.5.

If you would like to run cooker and perform periodic updates, this can be accomplished with:

urpmi --media uninett,contrib --auto-select

More screenshots posted in the gallery. All Tuxmachines' Mandriva coverage here.

Known issues so far:

  • rpmdrake segfaults on x86_64, mcc does not launch (seems
    related to pango or something). urpmi works correctly though.

  • "live installation" isn't perfect (empty root password, keeps guest
    user), the live CD won't halt, and it doesn't contain the copy wizard
    to create live systems on USB keys.

Changelog since 2006:

  • DrakX 1.1093 / drakxtools-10.4.7mdk
  • Stage 1
    • support jfs and xfs
  • Network
    • load all ethernet modules in all installation modes (fixes the problem of firewire not being loaded in automatic mode)
    • update zones file for shorewall 3.0
    • use new DBus typing facilities
    • don't screw up eagle-usb devices if the firmware is already loaded
    • fix wireless network list using iwlist (`` returns a defined empty string if the command fails)
    • handle zd1201 as well
    • don't let interfaces with unknown drivers be configured
    • fix rt2400/rt2500 devices detection (workaround for their missing "device" link in sysfs)
    • use disconnected icon if no route, even if wifi is associated
    • handle new ueagle-atm driver
    • use /lib/firmware as default firmware directory
  • Printer
    • fixed setting up printers with pre-made Foomatic PPD in /usr/share/cups/model (bug #19524).
    • HPLIP support
      • Gutenprint support
      • support for several other new drivers
      • Printer communication error handling
      • Main window of printerdrake comes up faster
      • Many bug fixes and detail improvements
  • Filesystem
    • add user_xattr (useful for beagle, cf bugzilla #15068)
    • simplify text for option "users" (was not accurate and much too verbose) (see also bugzilla #19848)
    • add button "Label" (in expert for now) to set the "volume label" (and so get LABEL= in fstab and lilo.conf)
    • when calling dmraid, replace -ccs and -ccr with -s -c -c and -r -c -c(the former doesn't work anymore with dmraid 1.0.0 RC9) cf #19654
    • log is mixed with valid data (bugzilla #19654)
    • use vol_id to find device type
  • Live
    • add some useful devices for live systems build
    • don't run Xnest if an auto_install file is used
      * install all hardware related packages when building a live system
  • Bootloader
    • fix getting raid-extra-boot (bugzilla #19965)
      * Rescue
    • fix restoring many primary partitions
      * partimage, fix (same behaviour as before, but option save_home_directory really mean what it says)
    • acpi=ht is bad on some boxes (=> sata_sis not working)
  • Sound
    • install aoss too when installing ALSA
      * Upgrade
    • fix upgrading conectivaoffice pkg (bugzilla #18948)
  • X config
    • properly handle switch between nvidia & nvidia_legacy
    • simplify (and make it more robust)
    • make it more easier to understand
    • ensure we don't load both "/usr/X11R6/lib/modules/extensions/libglx.so" and "/usr/X11R6/lib/modules/extensions/nvidia/libglx.so"
    • handle nvidia_legacy
    • don't create files (and thus don't run ldconfig when not needed)
    • don't modify /etc/ld.so.conf.d/{nvidia,ati}.conf if file does not exist (otherwise at package install time, one gets a .rpmnew)
  • Packages
    • install powernowd on x86_64 (since they've the cool&quiet technology) and athcool on athlon32
  • kernel 2.6.12-13mdk
    • Updated pl2303 usb-serial driver to support X75 and SX1 Siemens mobiles
    • selected fixes from 2.6.13 and beyond:
      • add r300 drm support
      • fix x86_64 idle=poll
      • fix races in libata core
      • properly fix the radeon IRQ handling code
      • properly fix the errata #122 workaround on x86_64 + add it to i386
      • merge new upstream ioctl32 compat code, thus supporting i915 as well
  • KDE 3.5
  • Gnome 2.12
  • OpenOffice 2.0
  • Xorg 6.9
  • amarok 1.3.7
  • apache 2.2.0
  • bind 9.3.2
  • bittorrent 4.3.3
  • epiphany 1.8.4
  • evolution 2.4.2.1
  • gimp 2.3.5
  • kaffeine 0.7.1
  • MySQL 5.0.17
  • postgresql 8.1.1

More in Tux Machines

today's leftovers

  • Bring your ideas to the world with kubectl plugins

    kubectl is the most critical tool to interact with Kubernetes and has to address multiple user personas, each with their own needs and opinions. One way to make kubectl do what you need is to build new functionality into kubectl. Challenges with building commands into kubectl However, that’s easier said than done. Being such an important cornerstone of Kubernetes, any meaningful change to kubectl needs to undergo a Kubernetes Enhancement Proposal (KEP) where the intended change is discussed beforehand. When it comes to implementation, you’ll find that kubectl is an ingenious and complex piece of engineering. It might take a long time to get used to the processes and style of the codebase to get done what you want to achieve. Next comes the review process which may go through several rounds until it meets all the requirements of the Kubernetes maintainers – after all, they need to take over ownership of this feature and maintain it from the day it’s merged. When everything goes well, you can finally rejoice. Your code will be shipped with the next Kubernetes release. Well, that could mean you need to wait another 3 months to ship your idea in kubectl if you are unlucky. So this was the happy path where everything goes well. But there are good reasons why your new functionality may never make it into kubectl. For one, kubectl has a particular look and feel and violating that style will not be acceptable by the maintainers. For example, an interactive command that produces output with colors would be inconsistent with the rest of kubectl. Also, when it comes to tools or commands useful only to a minuscule proportion of users, the maintainers may simply reject your proposal as kubectl needs to address common needs. But this doesn’t mean you can’t ship your ideas to kubectl users.

  • Phoronix Test Suite 9.4 Released With More Features For Open-Source, Cross-Platform Automated Benchmarking

    Phoronix Test Suite 9.4-Vestby is now available as one of our largest updates in recent years for our open-source, cross-platform automated benchmarking framework. Almost wanting to rebrand it as Phoronix Test Suite 10, sticking to conventional versioning the Phoronix Test Suite 9.4 release brings numerous result viewer improvements, a lot of polishing to the PDF result exporting, various Microsoft Windows support improvements, new statistics capabilities, some useful new sub-commands, and much more as the latest quarterly feature release.

  • Linux 5.6 Tests On AMD EPYC 7742 vs. Intel Xeon 8280 2P With 100+ Benchmarks

    The latest benchmarks for your viewing pleasure are looking at the dual Intel Xeon Platinum 8280 performance up against the dual AMD EPYC 7742 CPUs while using the in-development Linux 5.6 kernel as the first time trying out these highest-end server processors on this new kernel debuting as stable in about one month's time.

  • PyIDM – An Open Source Alternative to IDM (Internet Download Manager)

    pyIDM is a free, open-source alternative to IDM (Internet Download Manager), used to download general files and videos from youtube as well as other streaming websites. It is developed using Python (requires Python 3.6+) and relies only on open source tools and libraries such as pycurl, youtube_dl, FFmpeg, and pysimplegui. It features multiple-connections, a speed engine (and it offers high download speeds based on libcurl); resume uncompleted downloads, support for fragmented video streams, support for encrypted/non-encrypted HLS (HTTP Live Streaming) media streams. Besides, it also supports scheduling downloads, re-using an existing connection to a remote server, and HTTP proxy support. And it allows users to control options such as selecting a theme (there are 140 themes available), set proxy, selecting segment size, speed limit, maximum concurrent downloads and maximum connections per download.

  • DRM Plugin crashes after openSUSE Tumbleweed update

    A few days ago openSUSE users started complaining about DRM Plugin crashes in Firefox after running a Tumbleweed update. Netflix requires the DRM plugin in Firefox to be able to play encrypted videos. The plugin would crash due to a bug in Firefox 73. While this bug affected not just openSUSE users, but everyone using Firefox 73, it became apparent to TW users as v73 landed in the Tumbleweed repo.

  • How Melissa Di Donato Is Going To Reinvent SUSE

    SUSE is one of the oldest open source companies and the first to market Linux for the enterprise. Even though it has undergone several acquisitions and a merger, it remains a strong player in the business. It has maintained its integrity and core values around open source. It continues to rely on its tried-and-tested Linux business and European markets, and generally shies away from making big moves taking big risks. Until now. SUSE appointed Melissa Di Donato as its first female CEO. She is making some serious changes to the company, from building a diverse and inclusive culture to betting on emerging technologies and taking risks. Soon after taking the helm last year, Di Donato spent the first few months traveling around the globe to meet SUSE teams and customers and get a better sense of the perception of the market about the company. Just like Red Hat CEO Jim Whitehurst, Di Donato didn’t come to the company from an open source background. She had spent the last 25 years of her career as a SUSE customer, so she did have an outsider’s perspective of the company. “I am not interested in what SUSE was when I joined. I am more interested in what we want to become,” she said.

  • Experimental feature: snap refresh awareness and update inhibition

    We’d like to follow up on last week’s article about parallel installs for classic snaps with another bleeding-edge topic. Today, we will discuss snap refreshes. By design, snaps come with automatic updates, and by default, the update (refresh) frequency check is four times a day. Whenever new application versions are published, they soon become available and propagate to all end-user systems. Normally, the process is transparent and seamless, but there could be exceptions. For instance, if you have an app open and running, an update could be disruptive in the middle of your work. Some developers have asked for an option to inhibit refreshes of snaps while they are running, and this is now a new, experimental feature that you can enable and test on your system. [...] The app refresh capability offers snaps users another level of control in the overall user experience. Automatic updates are geared toward security, but users can defer updates for up to 60 days, and now, they also have the ability to gracefully update applications with minimal disruption to their normal usage patterns and workflows. We very much welcome your feedback and suggestions, especially with new and upcoming features. The refresh awareness option is a good example of where the developer feedback has been valuable and useful in making the snap ecosystem even friendlier and more robust. If you have any ideas on this topic – or any other, please join our forum for a discussion.

  • How Domotz streamlined provisioning of IoT devices

    Learn how Ubuntu Core and snaps gives Domotz a competitive advantage As the number of IoT devices scale, the challenges of provisioning and keeping them up to date in the field increases. Domotz, who manufacture an all-in-one, network monitoring and management device for enterprise IoT networks, found themselves with this challenge that was further compounded by their rapid software release cadence. One of the most crucial and difficult aspects for Domotz to solve was the delivery of automatic updates to the tens of thousands of devices deployed. Domotz turned to snaps and Ubuntu Core to meet their exacting requirements. I absolutely believe that Ubuntu Core and snaps give us a competitive advantage. We are the only company in the IoT network management space that can guarantee a secure, always-up-to-date device for our customers’ on-premises deployments.

  • A birthday gift: 2GB Raspberry Pi 4 now only $35

    TL;DR: it’s our eighth birthday, and falling RAM prices have allowed us to cut the price of the 2GB Raspberry Pi 4 to $35. You can buy one here.

  • The RedMonk Programming Language Rankings: January 2020 [Ed: Redmonk uses to assess programming languages use only projects that Microsoft (a Redmonk client) controls. Some 'research', eh?]
  • Announcing Rust 1.41.1

    The Rust team has published a new point release of Rust, 1.41.1. Rust is a programming language that is empowering everyone to build reliable and efficient software. If you have a previous version of Rust installed via rustup, getting Rust 1.41.1 is as easy as: rustup update stable If you don't have it already, you can get rustup from the appropriate page on our website.

  • This Week in Rust 327
  • Zip Files: History, Explanation and Implementation

    I have been curious about data compression and the Zip file format in particular for a long time. At some point I decided to address that by learning how it works and writing my own Zip program. The implementation turned into an exciting programming exercise; there is great pleasure to be had from creating a well oiled machine that takes data apart, jumbles its bits into a more efficient representation, and puts it all back together again. Hopefully it is interesting to read about too.

    This article explains how the Zip file format and its compression scheme work in great detail: LZ77 compression, Huffman coding, Deflate and all. It tells some of the history, and provides a reasonably efficient example implementation written from scratch in C. The source code is available in hwzip-1.0.zip.

    I am very grateful to Ange Albertini, Gynvael Coldwind, Fabian Giesen, Jonas Skeppstedt (web), Primiano Tucci, and Nico Weber who provided valuable feedback on draft versions of this material.

Netrunner Linux Still Goes Its Own Way at 'Twenty'

The Netrunner distro used to be a bleeding-edge choice among KDE options. With little that's new and must-have, this release takes the edge off the bleeding. I wasn't nudged away from my preferred competing KDE distro -- the new Feren OS Plasma edition. While Netrunner 20.01 provides a fairly solid integration of classic KDE desktop performance, this release is a departure, in that it is not a step or two ahead of most other KDE-integrated Linux OSes. I Netrunner attracts two types of typical users. One fancies a more friendly desktop environment. The second wants the freedom to tweak more extensively than other desktop environments allow. Hardware requirements include a minimum CPU of 1.6 GHz Intel Atom N270 or greater and at least 1 GB of RAM with at least 10 GB hard drive space. Also, the computer should have Intel GMA 945 graphics card support with 128+ MB of video memory. Netrunner is a unique distro with its own spin on the K Plasma desktop environment. Seasoned Linux users who like to fiddle and tweak an OS into their own platform will love how this distro integrates the KDE Plasma desktop. Newcomers can be quite content using the out-of-the-box settings. Read more

Wind River launches dev site with TensorFlow for Linux and a free VxWorks download

A new “Wind River Labs” developer site hosts projects including TensorFlow for Wind River Linux, the first free VxWorks SDK, and VxWorks BSPs for the Raspberry Pi and UP Squared. One would think that when Wind River decided to launch a public-facing developer site, it would showcase the Yocto Project based Wind River Linux, which is available in a GPL-licensed release on GitHub in addition to the standard commercial version and new continuous integration version. Yet when Wind River announced its new Wind River Labs site this week, its proprietary VxWorks was the star of the show — but with a twist. There’s a new free VxWorks SDK for evaluating the RTOS for non-commercial purposes, as well as open source VxWorks BSPs for the Raspberry Pi and UP Squared boards. Read more

Security, Proprietary Software and Openwashing

  • Linux 4.4.215 / 4.9.215 / 4.14.172 / 5.5.7 Kernels Bringing Intel KVM Security Fix

    A few days back we reported on a security vulnerability within Intel's KVM virtualization code for the Linux kernel. That vulnerability stems from unfinished kernel code and was fixed for Linux 5.6 Git and is now being back-ported to the 4.4 / 4.9 / 4.14 / 5.5 supported kernels. Back on Monday when the CVE-2020-2732 patches first came to light, little was publicly known about the issue but that it stemmed from incomplete code in the vmx_check_intercept functionality in not checking all possible intercepts and in turn could end up emulating instructions that should be disabled by the hypervisor.

  • Let's Encrypt Has Issued a Billion Certificates

    We issued our billionth certificate on February 27, 2020. We’re going to use this big round number as an opportunity to reflect on what has changed for us, and for the Internet, leading up to this event. In particular, we want to talk about what has happened since the last time we talked about a big round number of certificates - one hundred million. One thing that’s different now is that the Web is much more encrypted than it was. In June of 2017 approximately 58% of page loads used HTTPS globally, 64% in the United States. Today 81% of page loads use HTTPS globally, and we’re at 91% in the United States! This is an incredible achievement. That’s a lot more privacy and security for everybody. Another thing that’s different is that our organization has grown a bit, but not by much! In June of 2017 we were serving approximately 46M websites, and we did so with 11 full time staff and an annual budget of $2.61M. Today we serve nearly 192M websites with 13 full time staff and an annual budget of approximately $3.35M. This means we’re serving more than 4x the websites with only two additional staff and a 28% increase in budget. The additional staff and budget did more than just improve our ability to scale though - we’ve made improvements across the board to provide even more secure and reliable service. Nothing drives adoption like ease of use, and the foundation for ease of use in the certificate space is our ACME protocol. ACME allows for extensive automation, which means computers can do most of the work. It was also standardized as RFC 8555 in 2019, which allows the Web community to confidently build an even richer ecosystem of software around it. Today, thanks to our incredible community, there is an ACME client for just about every deployment environment. Certbot is one of our favorites, and they’ve been working hard to make it even easier for people to use.

  • The “Cloud Snooper” malware that sneaks into your Linux servers [Ed: Sophos citing itself, hyping up the threat is installing malicious software on one's own server]

    SophosLabs has just published a detailed report about a malware attack dubbed Cloud Snooper. The reason for the name is not so much that the attack is cloud-specific (the technique could be used against pretty much any server, wherever it’s hosted), but that it’s a sneaky way for cybercrooks to open up your server to the cloud, in ways you very definitely don’t want, “from the inside out”. The Cloud Snooper report covers a whole raft of related malware samples that our researchers found deployed in combination.

  • OpenSMTPD Email Server Vulnerability Threatens Many Linux and BSD Systems [Ed: It is this package, not the operating systems (GNU/Linux rarely uses this)]

    A critical vulnerability has been discovered in the OpenBSD email server OpenSMTPD. Exploiting the flaw could allow remote code execution attacks. The seriousness of the vulnerability poses a threat to the integrity of OpenBSD and Linux systems.

  • A billion Wi-Fi devices suffer from a newly discovered security fla

    More than a billion internet-connected devices—including Apple's iPhone and Amazon's Echo—are affected by a security vulnerability that could allow [attackers] to spy on traffic sent over Wi-Fi.

  • New ‘Haken’ Malware Found On Eight Apps In Google Play Store

    Eight apps – mostly camera utilities and children’s games – were discovered spreading a new malware strain that steals data and signs victims up for expensive premium services.

  •                            
  • What does it take to commit to 100% open source?
                                 
                                   

    While experts in the database market in particular agree that open source is becoming the norm, the question remains, just how open is this sector’s open-source software? Can software providers realistically succeed with a company that’s 100% open source? Furthermore, would a proprietary infrastructure software provider with a freemium tier be able to achieve the same benefits as those committing to open source?

                                   

    The short answer is, yes — a proprietary infrastructure software company with a freemium tier could theoretically achieve the same benefits as companies going fully open source. However, it’s important to recognize that it would take a freemium model company a significantly longer period of time for its software to mature to the same level as that of an open-source company. Also, the loss of collaborative development and slower feedback loops would likely lead to a higher probability of the software never achieving market traction and ultimately fading away into oblivion.

  • Mirantis: Balancing Open Source With Guardrails

    Mirantis, an open infrastructure company that rose to popularity with its OpenStack offering, is now moving into the Kubernetes space very aggressively. Last year, the company acquired the Docker Enterprise business from Docker. This week, it announced that they were hiring the Kubernetes experts from the Finnish company Kontena and established a Mirantis office in Finland, expanding the company’s footprint in Europe. Mirantis already has a significant presence in Europe due to large customers such as Bosch and Volkswagen.