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

Oracle/IBM/Red Hat/Fedora Leftovers

  • Fedora program update: 2020-48 – Fedora Community Blog

    Here’s your report of what has happened in Fedora this week. Elections voting is open through 3 December. Fedora 31 has reached end of life. EPEL 6 will reach end-of-life on Monday.

  • Oracle Linux 8: Oracle Ksplice made easy with free training

    This week’s training blog presents a set of free, short videos on using Oracle Ksplice on Oracle Linux 8. Oracle Ksplice allows you to install the latest kernel and key user-space security and bug fix updates while the system is running. You don’t need to coordinate with users to schedule system down time. You don’t need to stop running applications and you don’t need to reboot your systems to install kernel and user-space updates.

  • More for developers in the new Red Hat OpenShift 4.6 web console - Red Hat Developer

    Red Hat OpenShift 4.6 streamlines developer onboarding in the OpenShift web console, but that’s not all. This article details improvements and new features in the topology view and introduces OpenShift’s new, form-based approach to creating horizontal pod autoscalers and Helm charts. I also touch on application monitoring improvements and the latest updates for Red Hat OpenShift Pipelines, Red Hat OpenShift Serverless, and the Kiali Operator in OpenShift 4.6.

  • Log-On Wave for IBM Z Simplifies Administration and Operation of Virtualized Linux Infrastructures on IBM Z and LinuxONE

    Log-On Software (Log-On) an IBM Business Partner and developer of software solutions for IBM Z, has announced Log-On Wave for IBM Z, with general availability planned for January 2021. According to the company, Log-On Wave for IBM Z simplifies the administration and operation of virtual Linux servers running on IBM Z and IBM LinuxONE. The result is that IT organizations and service providers benefit from an intuitive graphical interface and intelligent functionality that improves productivity by simplifying administration, configuration and management and future-proofs operations by shielding complexity and enabling less experienced administrators to easily manage highly virtualized infrastructures.

  • Implementing storage: Compliance concerns for stateful financial services applications

    There’s little doubt that industry pressures have driven financial services firms to implement - and to continue to adopt - transformative solutions to maintain competitive advantages that help streamline operations and introduce new products. However, along with having to surmount technical issues, this industry presents special challenges regulatory and compliance concerns, in addition to technology considerations. Regulators play a major role in financial institutions, therefore, by necessity, banks create organizational models and processes to ensure that work is being delivered with the most minimal risk possible - and technology solutions must also adhere to this regulatory overlay.

  • Web interfaces for your syslog server - Blog - syslog-ng Community - syslog-ng Community

    This is the 2020 edition of my most read blog entry about syslog-ng web-based graphical user interfaces (web GUIs). Many things have changed in the past few years. In 2011, only a single logging as a service solution was available, while nowadays, I regularly run into others. Also, while some software disappeared, the number of logging-related GUIs is growing. This is why in this post, I will mostly focus on generic log management and open source instead of highly specialized software, like SIEMs.

  • Red Hat Quarkus Java stack moves to OpenShift

    Red Hat’s Quarkus framework for building Kubernetes-native Java applications is now included with the company’s OpenShift 4.6 open source container application platform, a step Red Hat describes as important in bringing Java into modern cloud-native application development. Previously supported in Red Hat Runtimes middleware, Quarkus now is natively integrated into OpenShift to provide for easier development, the company said. Developers can use familiar tools and do remote development on clusters via IDEs such as CodeReady Workspaces. Developers also can do serverless workload deployment and application storage management.

Torsten Franz: My first month at the Ubuntu Community Council

In the last few weeks I have been asked by many people what topics we have in the Community Council and what we are doing. After a month in the Council, I want to give a first insight into what happened in the early days and what has been on my mind. Of course, these are all subjective impressions and I am not speaking here from the perspective of the Community Council, but from my own perspective. In the beginning, of course, we had to deal with organisational issues. These include ensuring that everyone is included in the Community Council’s communication channels. There are two main channels that we use. On the one hand, we have a team channel on IRC on Freenode to exchange ideas. The channel has the advantage that you can ask the others small questions and have a relaxed chat. To reach everyone in the Council, we have set up the mailing list: community-council at lists.ubuntu.com No, I haven’t yet managed to read through all the documents and threads that deal with the Community Council or how to make the community more active again. But I have already read a lot in the first month on the Community Hub and on mailing lists to get different impressions. I can only encourage everyone to get involved with constructive ideas and help us to improve the community of Ubuntu. I haven’t worked on an international board since 2017 and had completely forgotten one topic that is more complex than national teams: the different timezones. But after a short time we managed to find a date where we all can basically do it and we had our public meeting of the council. This took place twice and the second time we all managed to attend. The minutes of the meetings are publicly available: 1st Meeting and 2nd Meeting. We have decided that we will hold the meeting twice a month. Read more Also: Design and Web team summary – 24th November 2020 | Ubuntu

GTK: At the Heart of GNOME

GTK is at the heart of the GNOME application and software development kit. GTK is used to create graphical user interfaces (GUIs) for desktop environments, applications, and window managers. Since the GTK 4 development process began in 2016, we have about 250 individual contributors, with more than 100 active this year. Thanks to the funding received by the GNOME Foundation in 2020, the GTK development team was able to run hackfests, including one we were lucky enough to have at FOSDEM. This funding also supported Emmanuele Bassi, Core GTK Developer at the GNOME Foundation, working on GTK full-time. For most of 2020, Emmanuele worked on implementing a new accessibility interface for GTK 4, to ensure that more people can use GNOME applications, including those with disabilities. We are building a diverse and sustainable free software computing ecosystem where everyone can be empowered by technology they trust. Since Emmanuele works directly for the Foundation he’s uniquely able to focus on the needs of the community, project, and users to support these goals. GTK is a project with a long history, and throughout that history, it has gone through multiple iterations. A new major release is on the horizon. After four years of development that included a complete overhaul of the internals of the toolkit, GTK 4 promises to be faster through hardware acceleration; more efficient, in terms of performance and power consumption; and more ergonomic, for both application developers, and end users. Over the past four years, the GTK team has continued work on the existing stable versions of GTK and put out multiple releases. Read more Also: GTK Planning More Improvements In 2021 From Better Accessibility To Animation Framework

Platform exclusivity, DRM, and independent authors: A cautionary tale

Imagine, for the sake of argument, that you wrote a book. You've worked on it for years, and you want to share it with the world. You want to reach as many people as possible, but it would be nice to be compensated for your hard work. How many weekends did you spend at home, polishing your manuscript instead of going out with friends? How many sleepless nights have you spent staring at a blank page, looking for inspiration? While researching the best way to publish, you hear horror stories about authors finding their books sold on counterfeit Web sites or distributed gratis without the author's consent. You read stories about authors feeling violated as their hard work is stolen in such a way. As you read about these activities, you also see mentions of companies that claim that they would protect your work against it. Should you publish your book through them, your book would only be available through their application. People could only access it through their store, and they wouldn't even be able to open the file on a device that isn't vetted by the company. The app is very popular, so most people use it anyway, and authors do not have to worry about a lack of interest. Only dealing with one store would also make things easier on your end. You won't have to manage different things. They'll even format your book for you. Sounds easy enough, so you take the deal. Weeks pass, and you make a few sales. It's by no mean a huge success, but you got a few positive reviews, mostly from family and friends. You keep mentioning your project to everyone you know, and find some limited interest. One day, a friend you hadn't talked to in a while asks about your book. They say that they don't like the app your book requires, and they don't want to buy it through the one store you signed an exclusivity deal with. They explain that Digital Restrictions Management (DRM) restricts their freedom to read the book on their device of choice, and won't even let them make backups of the file. They tell you how they once used a similar app, but were locked out of all the books they purchased after moving away from said application. After hearing your friend's story, you decide to give them a DRM-free copy of your book. After all, you wrote it so people would enjoy it first and foremost, and you want your friend to see the fruit of your labor. Read more