Language Selection

English French German Italian Portuguese Spanish

Mandriva 2006 Final Look

Filed under
MDV
Reviews
-s

As you know Mandriva 2006.0 was released to club members on October 6, and then it was released to the general public yesterday, October 13. It is available at the time of this writing only as an ftp install. No word at this time of when isos will be made public but if you can download an iso, then you can do an ftp install. In fact, I prefer ftp installs in a way because you only have to download the packages you actually need. In addition, when you define a mirror for your ftp install, the information is usually stored for later and continued use through urpmi. In addition one doesn't need to waste more cdrs to have to dispose of later. Ftp is the way to go.

As we followed Mandriva through the 2006.0 development cycle we found many new features and vast improvements in other areas. Today we summarize the operating system that Mandriva 2006 has become.

Installation

So, pick a mirror and navigate to the official/2006.0/your_arch/install/images directory and download the boot.iso or network.img. The boot.iso is a 12.5mb iso to be burnt onto a cdrom while the network.img is a 1.4mb image to be dd'd onto a floppy disk. Both are used to boot your machine and start the install. If you prefer to use the floppy disk method, you may wish to read the readme as you may need additional disks such as for uncommon device drivers or the like. Note your mirror path to the arch directory. Upon boot of the boot.iso you are presented with a menu asking what type of install you'd like to do and in this case choose ftp install. After configuration of your internet connection, you can either use one of their predefined categories of mirror types or choose define your own. I'd suggest you have a mirror backup written down in case the mandrake predefined mirrors don't work out. I usually choose list your own and fill in the information. Then the install goes as usual. Pick your language, type of install, where to install if necessary, partition work if necessary. Then you choose your package groups or individual packages if desired and wait. If it's a network install, this will take more time than you might be accustomed to. After the packages are installed you are given the opportunity to set up users and passwords, configure your hardware and system, and setup a boot loader. Then you can boot into your shiny new Mandriva 2006 desktop.

Features:

  • KDE 3.4.2

  • Gnome 2.10.2
  • Kernel 2.6.12.11
  • Xorg 6.9 (cvs20050915)
  • Kat 0.6.3-19
  • Firefox 1.0.6
  • Gaim 1.5.0
  • OpenOffice.org 1.1.5
  • Nvu 1.0
  • Gcc 4.0.1
  • Evolution 2.2.3
  • Xine 1.1.0
  • Gimp 2.2.8
  • Interactive firewall
  • Full integration of Skype
  • Integration of Conectiva's and Lycoris's technologies
  • Official support for the Intel Centrino mobile technology
  • Full RPMlist as tested

The first and most noticably striking improvement is Mandriva's new blue penguin theme. A wonderfully tasteful choice after the 2005 Monster Tux. I'm not sure if it was ruined by the use of the new Disco Duck start up wav or not. j/k The new theme runs throughout Mandriva 2006 sporting pretty graphics, interesting sounds and colorful icons everywhere. Mandriva has become absolutely beautiful.

        

        

New this release is the Kat Desktop Search tool, which was covered fairly well in my Beta 2 report or my RC1 report. Kat is a desktop search engine that can index a directory or your whole system for comprehensive searching. Results can be as extensive as you define. A wonderful tool written by a really nice guy.

    

Also new in 2006 is the Smart package manager. Smart is different from other package managers in that it can use different types of packages, other than what the system specifically uses. It has configurations available for urpmi repository, rpm directory, apt-get repos, apt-rpm repos, Slackware repos, deb directories. This topic too was covered in more detail in my RC1 report. I'm not sure of the fate of Smart in Mandriva as I heard the developer has since moved on. Have no fear, for Mandriva's original package manager is still intact and performing to near perfection either by commandline or graphical interface.

        

And of course, Mandriva wouldn't be Mandriva without their famous Mandriva Control Center. From this one application one finds modules to configure their entire system, from network connection to firewall rules, from software installation/uninstalls to distribution upgrades, and from booting/startup options to hardware configuration. It is their flagship application where you can do all these thing and so much more.

        

Conclusion

All in all, as I've followed the development of Mandriva 2006, one thing has become clear. Mandriva is ever improving and it is reflected in this new more polished stable operating system. Featured here is only a taste. Throughout the entire development cycle I experienced very few applications crashes and never a major X server crash or system lock up. The compromises between bleeding-edge and stable applications has paid off tremendously for Mandriva. I've found the upgrade process perfected to a dream and the installer remains one of the key features that drives Mandriva's popularity. In this release not only is the look and feel improved, they have introduced new technologies and features for the novice and experienced alike. Mandriva provides enterprise level software and support as well as a free-for-download version and support in the form of mailing lists and forums. There are also unsponsored newsgroups, forums, and irc channels. To me, Mandriva is a world class system that can meet any user's needs, as it comes with just about any application in existence and many server applications as well.

Mandriva, the people's Linux.

All Tuxmachine's Mandriva coverage can be found HERE.

Mandriva's own Press Release is chocked full of further information.

Changelog since RC2:

  • Fixes
    • mozilla-firefox-1.0.6-15mdk: Security update, synched with FF 1.0.7
    • cvs-1.11.19-6mdk: security fix for cvsbug
    • desktop-common-data-2006-2mdk: Fix desktop-directory script
    • kat-0.6.3-19mdk
      • use html2text -nobs
      • fix search on multiple words (Laurent)
      • default wait time to 20 seconds
      • fix clearing of result windows (Laurent)
      • fix exclude dirs (Laurent)
      • more debug filtering
      • fix fulltext_eml
    • gnome-panel-2.10.2-10mdk: fix for UTF8 encoded url in .desktop file
    • libgnomeui2-2.10.1-10mdk: read UTF-8 encoded url in .desktop file correctly
    • kdebase-3.4.2-55mdk: various cosmetic fixes
  • DrakX 1.1092 / drakxtools-10.3-0.64mdk
    • Bootloader: cleanup sanitize_ver(), makes label longer but cleaner
    • Drakfont (interactive_mode) fix layout (license_msg) merge 2 similar strings
    • Keyboard: added "fo" keyboard, synchronized XKB keyboard names with what is in latest xorg
    • Network:
      • set hostname only after packages have been installed, or else graphical urpmi may fail
      • fix dvb crash during install
      • show IFW button even if not connected (#18708)
      • don't try to connect auto-magically ethernet interfaces during configuration in install, restart ethernet interface for pppoe connections, add some reminders, fix indentation.
      • use mandriva.com for connection tests
      • fix crash (ugtk2 dialog helpers aren't imported)
      • force menu refresh when interface status is modified (#18636)
      • pppoe_modem device doesn't exist, automatically configure DSL connection on installation from DSL
      • net_applet: fix crash when only one interface is configured
      • (is_ifplugd_blacklisted) do not blacklist anymore b44 since it now support reporting link status according to Arnaud Monnet de Lorbeau
      • restart hsf/hcfpci services when needed support madwifi drivers
      • increase timeout after a wireless network is selected don't vivify hash ref
      • allow to up/down any network interface (backport of my 2005 patch for PSA)
      • better handling of ASCII WEP keys (partial fix for #18558)
      • don't try to update shorewall configuration if it's disabled drakconnect: update interfaces list in shorewall drakconnect: write wireless settings in wireless.d/ as well
      • read shorewall net interface from configuration file first
      • lower signal level given by wpa_supplicant fix hidden ssid always recognized as current when using iwlist fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
      • net_applet: refresh wireless networks every minute only fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
      • fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
      • don't resize state icons show refresh icon if network isn't connected show ESSID if already configured for hidden ssid move signal strength icon on the left don't automatically refresh networks list use Managed mode if AP isn't Ad-Hoc drakconnect: write wireless settings in wireless.d/ as well fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
    • Packages:
      • don't warn lisa (which is installed by default)
      • more x86_64 mirrors (works, tested as lftp $url -e exit)
    • Hardware
      • ugly hack: wait for usb-storage devices to appear (bugzilla #13395)
      • display cards that offer additional parallel port in the system class rather than in the "unknown" section (custom_id) try harder to have a sane name: before fallbacking to the class name (eg: "Printer"), try to use the vendor name (eg for printers)
    • comment/dis-comment the content of ld.so.conf.d/{nvidia,ati}.conf instead of symlinking to a hidden file (implies the new ati/nvidia packages have config(noreplace) for those files) instead of symlinking, comment the content of the ld.so.conf.d/*.conf don't load glx with fbdev (since glx is used for various things nowadays, dixit fredl)
    • Printer:
      • Do not auto-install "sane-frontends" for MF devices.
      • On USB printer hot-plugging sometimes parallel printers are also shown in the window popping up to ask whether the printer should be set up. Even sometimes parallel printers which are not connected or turned on any more were shown. Fixed.
      • Adapted file names to check for to the changes on the HPIJ 0.91-8mdkpackages.
    • filesystem:
      • increase /usr max size
      • fix typo during install, don't use half working dmraids (#18386)
    • Drakbackup: Remove unclear text (not needed, #18619)
    • Upgrade
      • we do want doPartitionDisks and formatPartitions to be done early on upgrade, so that selectKeyboard is done when the partitions are mounted
      • call set_all_default() (to fix fstab on upgrade) before install packages so that {useSupermount} is correctly set (maybe we could also move the set_all_default on install there) since choosing keyboard is done after mounting partition to upgrade,
      • ensure we have gnome-volume-manager when we have gnome or kde (to handle cdrom auto mounting)


More in Tux Machines

SUSE and Red Hat Leftovers

  • Skuba on SUSE CaaS Platform 4

    With SUSE CaaS Platform 4 we heard our customers feedback and decided to change what the lifecycle of the platform looks like. Previous versions of SUSE CaaS Platform included an administrator node that despite being useful for managing the whole platform, was another component to take care of, and an extra machine to take into account when deploying the platform. This administrator node used Salt to set up and maintain the Kubernetes cluster among the different nodes comprising your cluster. During this time, your feedback has been that a little more flexibility on the deployment was appreciated, so you could experiment with slightly different setups, even if they were for proof of concepts while you were fleshing out the details of production clusters.

  • Kubernetes Rolling Update Strategy in our production infra

    Kubernetes rolling update strategy means suppose we are running pod (containers) in our live infra and we want to update new changes into our running pod like build update, confrontational changes etc. While deployment new pod with new changes suppose our containers got stuck or failed due to any reason. So, we have to redeploy old pod with old changes again to avoid downtime of our application. This complete process is called rolling update strategy in Kubernetes. Kubernetes rolling update strategy Before moving to next we should aware about new pod deployment strategy of Kubernetes means how many new pods it will deploy at a time without taking downtime. Because high availability of our website is our first priority. So, while deploying new pod Kubernetes will deploy 25% or you can say one fourth of the total pod. Suppose we are running four pods first it will terminate 25% of total pod means one pod. Then it will launch 25% new pod and so on.

  • Tackle OpenStack networking woes with SUSE OpenStack Cloud Crowbar

    By far, the most difficult aspect of successfully deploying OpenStack is getting the networking right, a challenge that has caused many a well-intentioned IT team to throw up its hands and toss in the towel. Fortunately, SUSE OpenStack Cloud removes much of that pain by automating most of the network deployment and dramatically simplifying custom network set-ups.

  • Grow your virtualization environments without breaking the bank

    An IT director at a large financial services company shares the benefits and cost reductions they’ve experienced by switching to Red Hat Virtualization. In just three years, it’s paved the way for an efficient, stable and cost-effective virtualization environment.

  • How to Handle OpenShift Worker Nodes Resources in Overcommitted State

    One of the benefits in adopting a system like OpenShift is facilitating burstable and scalable workload. Horizontal application scaling involves adding or removing instances of an application to match demand. When OpenShift schedules a Pod, it’s important that the nodes have enough resources to actually run it. If a user schedules a large application (in the form of Pod) on a node with limited resources , it is possible for the node to run out of memory or CPU resources and for things to stop working! It’s also possible for applications to take up more resources than they should. This could be caused by a team spinning up more replicas than they need to artificially decrease latency or simply because of a configuration change that causes a program to go out of control and try to use 100% of the available CPU resources. Regardless of whether the issue is caused by a bad developer, bad code, or bad luck, what’s important is how a cluster administrator can manage and maintain control of the resources. In this blog, let’s take a look at how you can solve these problems using best practices.

  • How the new Quarkus extension for Visual Studio Code improves the development experience

    Earlier this year, we were introduced to Quarkus, the next-generation, container-first framework for Java applications. As expected, such new frameworks and technologies make way for new developer tools focused on making the development experience even better. The recent Quarkus extension for Visual Studio Code release aims to do just that, by bringing features specific to Quarkus project development within VS Code. The new VS Code extension is dependent on a couple of Java extensions for VS Code, so it is recommended that you have the Java Extension Pack installed. This article outlines what the Quarkus extension for VS Code has to offer: convenient features for an already convenient Java framework.

Security: New Updates and "Optimizing KVM Virtualization Performance Stemming From Spectre"

  • Security updates for Monday

    Security updates have been issued by Debian (expat, php-pecl-http, and php7.0), Fedora (ImageMagick, jackson-annotations, jackson-bom, jackson-core, jackson-databind, and rubygem-rmagick), Mageia (chromium-browser-stable, ibus, kernel, samba, and thunderbird), openSUSE (chromium), Oracle (dovecot and kernel), Red Hat (dbus, kernel, kernel-alt, and kpatch-patch), Scientific Linux (dovecot and kernel), and SUSE (expat, ibus, kernel, kernel-source-rt, nmap, openssl, and webkit2gtk3).

  • Red Hat Working On Optimizing KVM Virtualization Performance Stemming From Spectre

    Red Hat's Andrea Arcangeli sent out an interesting patch series on Friday to micro-optimize the Kernel-based Virtual Machine (KVM) to enhance the VMEXIT performance in wake of Spectre mitigations. The "KVM monolithic" patch series ends up linking the KVM common code both into kvm-intel and kvm-amd so that the common "kvm" kernel module can be dropped. This occupies more disk space but should yield better run-time performance particularly for systems mitigated against Spectre Variant Two.

  • 10 Best Anonymous Browser Apps for Android to Stay Incognito

    Android isn’t the most secure platform out there, but with the 10 best apps for anonymous browsing, you can greatly enhance your privacy online. Today we’ll define what anonymous browsing actually entails, run through 10 essential Android apps, and present the 2 best Android VPNs for the ultimate mobile cybersecurity.

Kernel: AMD Navi 10 Firmware and Linux 5.4 Additions

  • AMD Navi 10 Firmware Finally Lands In The Linux-Firmware Tree

    While AMD has provided open-source Radeon RX 5700 series (Navi 10) support since launch and that code since worked into the various mainline code-bases from the Linux kernel to Mesa, one kink in their support has been their binary microcode images not being available from the reference linux-firmware.git location as needed to initialize the hardware. That Navi 10 firmware/microcode issue has finally been rectified with the images landing this morning. Up until now any Radeon RX 5700 series Linux customers or distribution/third-party driver packagers have had to pull these binary bits from this Navi10 directory on the personal site of AMDGPU lead maintainer Alex Deucher. Via his site is where he normally stages these binary microcode files until landing in linux-firmware.git as the de facto location for all Linux drivers' firmware files.

  • Linux 5.4 Brings Support For Wacom's MobileStudio Pro 13, Logitech Lightspeed Receivers

    Jiri Kosina on Sunday sent out the HID subsystem updates for the in-development Linux 5.4 kernel. The HID pull once again features support for several new devices particularly on the Logitech side.

  • Wireless USB + UWB Demotion Goes Ahead For Linux 5.4

    Back in August I noted that Wireless USB and Ultra Wideband would be deprecated within the Linux kernel and that is indeed happening for Linux 5.4. The Wireless USB (WUSB) and Ultra Wideband (UWB) subsystems within the Linux kernel were already orphaned for years with having no maintainer while now they are officially deprecated and demoted to the kernel's staging area. If no one steps up soon to maintain the code, it will be dropped in forthcoming kernel releases.

Videos from LibreOffice Conference 2019: OpenDocument Format

LibreOffice can open documents in many formats, including Microsoft Office files (.docx, .xlxs, .pptx). But it’s native file format is the fully open and standardised OpenDocument Format (ODF). At the recent LibreOffice Conference 2019 in Spain, community members gave presentations about news and updates for ODF. So, here are the first videos from the presentations (use headphones for best audio quality). Read more