Become a fan of Slashdot on Facebook


Forgot your password?
Businesses Mandriva Linux

Mandriva Juggles Multiple Codebases 44

jfruh writes "In the wake of its decision to cede control of its Linux distro to its community, Mandriva is trying a tricky balancing act: offering Linux products based on two different code bases. Desktop and OEM offerings will be based on the Mandriva distro, while server products will be based on the traditional Mageia codebase." Update: As babai101 points out the codebases were reversed in the original post.
This discussion has been archived. No new comments can be posted.

Mandriva Juggles Multiple Codebases

Comments Filter:
  • OP got it wrong! (Score:5, Informative)

    by babai101 ( 1964448 ) on Monday July 09, 2012 @02:05PM (#40594377)
    From TFA "According to CEO Jean-Manual Croset and Director of Community Charles Schulz, the Mandriva server products will be based on the Mageia distribution of Linux, while desktop and OEM products will be based on the historical Mandriva Linux distro." Desktop and OEM offerings to be based upon Mandriva not on Mageia and server to be based on Mageia not Mandriva.
    • But shouldn't it have been the other way around? Mandriva use their own in-house code for their servers (like Red Hat does), and use the community fork (like Fedora) for the desktop/OEM versions? After all, servers are what they can actually sell, whereas desktops are usually given away. So it would make more sense that their employees work on the servers, wouldn't it?
      • In fact, the whole point is that in house is a simplification. mandriva SA is controlled by 2 heads, one from JM Crozet, a switzerland business man, and the other by leonid Reiman, a russian "businessman", whose record on the web should explain why no one would say no to him. So basically, what is the reason of a complex strategy is the result of a compromise :
        - desktop is mainly targetted at russian school and the rosa distribution. Rosa pay people who pushed the incompatibility with Mageia for innovation

  • by colinrichardday ( 768814 ) <> on Monday July 09, 2012 @02:05PM (#40594383)

    Yeah, no problems keeping those straight.

  • Redhat/Fedora (Score:4, Insightful)

    by gmuslera ( 3436 ) on Monday July 09, 2012 @02:27PM (#40594583) Homepage Journal
    They hadnt a lot of problems juggling between those codebases neither. Not sure if Fedora is to Redhat Enterprise like Mageia to Mandriva, or is a totally different beast, but it could work as precedent.
    • by nxtw ( 866177 )

      Each major RHEL release starts with a fork from a Fedora release.
      RHEL6 is apparently based on Fedora 12/13 []

      • Wasn't Fedora actually a fork from RHEL? At what point did the 2 get interchanged in terms of roles?
        • Fedora is basically the experimental version of RedHat - Red Hat uses Fedora to test the integration of bleeding edge (Desktop) technology which then will eventually end up in RHEL.

          In my (3-4 years old) experience this results in every Fedora version upgrade breaking something new.

          I think the original Fedora codebase (when they migrated from being a set of extra repositories to being a full-blown distro) was taken from the (discontinued) Red Hat Linux, with some caveats (see above rgd stability) Fedora has

    • by Yaa 101 ( 664725 )

      Mageia is a fork of the rock solid Mandriva 2010 codebase, Mandriva crashed with their experimental 2011 codebase and threw out the main builders of the product, these builders united in september 2010 to start Mageia.

      They used the Mandriva 2010 to build the servers that make the distribution (puppet based) and made the Mageia 1 distro with the servers in june 2011.
      At this moment Mageia 2 is out there but it is not as stable, the product is in the middle of changing from startup scripts to systemd and has d

      • Why don't they use Mageia for servers and PCLinux, which is another Mandriva fork, for desktops?
        • by Yaa 101 ( 664725 )

          PCLinux is an old fork, probably it is too far from the codebase of Mandriva.

          Texstar (PCLinux' maintainer) used to be a packager for Mandriva years ago, he rpm'd a lot of applications in those days, and the packages were of exceptional quality.

  • by Picass0 ( 147474 ) on Monday July 09, 2012 @02:35PM (#40594679) Homepage Journal

    This is exciting to see. Giving the community greater influence over the future development of the distro has put this on my list to watch. I've used Ubuntu and Fedora (laptop and desktop) for years, but I used Mandrake years back and would be open minded to doing so again.

    • by dmomo ( 256005 )

      I also enjoyed Mandrake for quite a stretch. At some point, they started littering the install process, and then the desktop with ads. I respect the need for a revenue model, but I feel the experience was too intrusive. There were plenty of alternatives, so I jumped ship.

    • But wouldn't using Mandrake re-invoke copyright battles w/ Hearst corporation, who had already won a case against them in 2004 over the use of that name? As it is, Mandrake Corporation was already in trouble due to the use of the magicians's bowler hat and wand as its logo, and to top that, the use of a Linux tool named Lothar, who in the strip was Mandrake's friend and principle body-building aide. The merger w/ Connectiva and the resulting name change resolved that issue. The last thing the company nee

  • Whats the difference between desktop and server other than what marketing has tried to create?

    Imagine having to support two versions of mysql, one on the KDE desktops and one on the backend server. Lovely.

    • About $5000... ba da bum bum...

  • Having used Mandriva (and Mandrake before it) ever since Redhat split its distributions I tried the 2011 version... It was a complete pig's ear of a release, especially if you want to integrate it into a shared network or use it for real work. The worst part (other than systemd and its intrinsic brokenness) is the default "Start" menu replacement. (Oh, and the WiFi is completely broken, the wired networking half so.)

    Mandriva 2010.x was stable and worked very well and this is the basis for Mageia.

    If there we
  • The Mandrake Team created a dependency tool (urpmi) at a time when only debian did, and poor redhat users had to download dependencies by hand.
    The Mandriva Team improved on the -drake family of tools, and came up with a centralized configuration panel : the MCC ; SuSE was doing the same ahead of 6 months, and poor debian users had to dpkg-reconfigure each packages by hand.

    In all that time, it was still the same people doing the good job (Pixel, warly, fpons, and so on).

    Now that they have all left (fired or

Information is the inverse of entropy.