Language Selection

English French German Italian Portuguese Spanish

Mandriva’s future (2)

Filed under
MDV

As is summarized by a mailing list post, Mandriva as being a distribution developed by a company and paid employees, is now an empty box. There is no more head in charge of the future direction of the distribution, who can take the necessary decisions for new releases. It looks like no more paid employees are working on GNOME and KDE packaging, and most people working on the installer and Mandriva’s configuration tools are gone. Looking at the SVN commit history it seems like the members of the security team are almost the only paid employees still working on the distribution. One can safely say that Mandriva is now de facto already a community developed distribution.

In the meantime, the CEO has reacted on a bug report. He says that Mandriva will concentrate on the server market in Europe and on the desktop market in countries like Brazil. Because European developers would have refused to be part of that future direction, they have been fired, according to the CEO. Of course this does not make any sense. There no reason why developers in Europe could not be working on the desktop if the target market for the desktop is mostly Brazil. The real reason why people are being fired, is of course that there is simply no more money to pay them anymore. Furthermore, I am pretty sure that Mandriva can never be a real competitor for distributions like Red Hat Enterprise Linux and Novell’s Suse Linux Enterprise Server, which are much more popular in large companies.

full post




More in Tux Machines

NHS open-source Spine 2 platform to go live next week

Last year, the NHS said open source would be a key feature of the new approach to healthcare IT. It hopes embracing open source will both cut the upfront costs of implementing new IT systems and take advantage of using the best brains from different areas of healthcare to develop collaborative solutions. Meyer said the Spine switchover team has “picked up the gauntlet around open-source software”. The HSCIC and BJSS have collaborated to build the core services of Spine 2, such as electronic prescriptions and care records, “in a series of iterative developments”. Read more

What the Linux Foundation Does for Linux

Jim Zemlin, the executive director of the Linux Foundation, talks about Linux a lot. During his keynote at the LinuxCon USA event here, Zemlin noted that it's often difficult for him to come up with new material for talking about the state of Linux at this point. Every year at LinuxCon, Zemlin delivers his State of Linux address, but this time he took a different approach. Zemlin detailed what he actually does and how the Linux Foundation works to advance the state of Linux. Fundamentally it's all about enabling the open source collaboration model for software development. "We are seeing a shift now where the majority of code in any product or service is going to be open source," Zemlin said. Zemlin added that open source is the new Pareto Principle for software development, where 80 percent of software code is open source. The nature of collaborative development itself has changed in recent years. For years the software collaboration was achieved mostly through standards organizations. Read more

Arch-based Linux distro KaOS 2014.08 is here with KDE 4.14.0

The Linux desktop community has reached a sad state. Ubuntu 14.04 was a disappointing release and Fedora is taking way too long between releases. Hell, OpenSUSE is an overall disaster. It is hard to recommend any Linux-based operating system beyond Mint. Even the popular KDE plasma environment and its associated programs are in a transition phase, moving from 4.x to 5.x. As exciting as KDE 5 may be, it is still not ready for prime-time; it is recommended to stay with 4 for now. Read more

diff -u: What's New in Kernel Development

One problem with Linux has been its implementation of system calls. As Andy Lutomirski pointed out recently, it's very messy. Even identifying which system calls were implemented for which architectures, he said, was very difficult, as was identifying the mapping between a call's name and its number, and mapping between call argument registers and system call arguments. Some user programs like strace and glibc needed to know this sort of information, but their way of gathering it together—although well accomplished—was very messy too. Read more