Home ›

Mandrake 7.2: Odyssey to Mediocrity

Issue 83

From Issue #83
March 2001

Mar 01, 2001  By Stephanie Black
 in
Stephanie takes a look at Mandrake 7.2.
Conclusion

It's anyone's guess whether runtime problems are due to libraries, or to unflagged dependencies, even the “optimized” Mandrake kernel 2.2.17. (This is an issue I'll discuss another time, but suffice it to say that an increasing number of Linux distributions have souped-up kernels and are inadvertently making an argument for standardization in the process.) For whatever reason, or combination of reasons, a good many of the applications included with Mandrake are not able to run or don't run as smoothly as they do under other distributions.

Mandrake is the kind of distribution one wants to like very much. It's cheery, and the good folks at Mandrakesoft have been so generous with packages, one wants to be able to say, “Well done!” The best one can, honestly, get away with is to admit that it's good in some parts. Most frequently, those parts have to do with ideas, rather than the implementation thereof.

Good/Bad

Stephanie Black is a writer—of words and code. When not writing, she runs a Linux consultancy, Coastal Den Computing, in Vancouver, BC, Canada. In her off-hours, she's usually playing fetch with her cats, or collaborating/colluding with her partner, a fabric artist and business manager.

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Just in case someone reads this article...

Anonymous's picture
Submitted by Anonymous on Fri, 12/07/2001 - 03:00.

Go and read this one too:

http://mandrakeforum.com/article.php?sid=615&lang=en

It's really amasing how such an obviously wrong and biased review ever made it to Linux Journal.

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions