Price: $69 US (plus $20 for shipping)
Reviewer: Choong Ng
Linux Mandrake 8.0 is the latest release from MandrakeSoft. Released on-line on April 19, 2001, Mandrake 8.0 adds kernel 2.4.3, XFree86 4.0.3, KDE 2.1.1, GCC 2.96 and miscellaneous other upgrades to 7.2 (the previous release). Mandrake is advertised primarily as a workstation and desktop-oriented distribution, so I will be evaluating it with these applications in mind. Supremely important in a desktop distribution are ease of setup, ease of configuration, ease of operation, quality of the software bundle and ease of installing new software; I will focus primarily on these criteria. My test machine for this review is a PIII 560 with 384MB of RAM, a 6GB hard disk and a Matrox G400.
Mandrake 8.0 comes on two (download edition) or four (retail version) CD-ROMs; the first two of which will be necessary for most installations. As with nearly all modern distributions, loading the first CD and rebooting is all that is necessary to start the installation. Mandrake 8.0's graphical installer closely resembles the installer used in the 7.x releases and is really about as user-friendly as an OS installer should be. Once the installer loads, it prompts the user for information such as how the computer will be used and what broad categories of packages to install. Many of the decisions that users new to computers or new to Linux (e.g., converting from Windows, more about this below) won't necessarily know how to answer, such as sizing and placement of partitions, are handled by the installer's defaults. As with the 7.x releases, you can go back to any previous part of the install by clicking on the button next to the appropriate step on the left side of the screen. Even X configuration—the area where I most often run into trouble—went without a hitch. This appears to be at least in part due to the move to XFree86 4.0.3, a significant improvement despite lacking solid support for certain graphics chipsets (notably several by Chips and Technologies common in older notebooks). One option to pay special attention to is the option to log on a user at boot automatically. Once you have answered all of the configuration questions, the installer will install and configure the requested packages, meanwhile displaying annoying “hints” à la the Windows 98 installer. The install took a little less than 15 minutes from the first reboot (to start from the installation CD) to a KDE user desktop.
If you get the retail version of Mandrake 8.0 (this is discussed later), the startup process is completely graphical. The boot-loader menu is a text list with an abstract design in the background, and the Linux startup process with its status icons resembles a Mac OS boot more than anything else. While most Linux Journal readers likely will disable this feature in favor of actually seeing what's going on during the boot process, I can see it being highly beneficial to users who wouldn't know UNIX from eunuchs and think bash is a verb. When the desktop finally loads (startup could take a minute or two on slower hardware) the user is presented with a very Windows-esque interface. Good or bad, that's what it is (see the next section). At first examination this represents a fairly well set up desktop, with icons for documentation, connection to the Internet, etc., right on the desktop and the most useful applications and utilities already in the KDE menu.
Mandrake 8.0 is definitely a step forward in terms of desktop usability. Between the KDE 2 desktop and the pre-installed productivity applications, MandrakeSoft has managed to put together a very usable desktop environment suitable for many users' needs. The default install by no means caters to the advanced user or the server market; unlike the 7.x series of releases, Mandrake 8.0 doesn't include any alternative window managers nor does it install (by default) many popular services such as SSH and NFS. This is clearly a very desktop-oriented distro. While Mandrake doesn't really add much to the functionality of user applications—KDE 2 and bundled applications take care of most of that—it does bring a marked improvement to system configuration. The graphical configuration utilities included (Mandrake Control Center, User Manager, etc.) are a distinct improvement over the utilities included with most other distros including previous releases of Mandrake. Where users once had to guess at cryptic names not obvious without documentation, now there are obvious names and easy-to-operate utilities like Mandrake Control Center to ease the process. This is definitely a step forward.
That said, there are still significant problems. First and foremost for desktop users is the presence of GNOME and other non-KDE applications in a (by default) KDE environment. While this isn't a problem on its own, the fact that the GTK toolkit produces a significantly different look and a new set of widgets makes for a less consistent interface. For new users this shouldn't present much of a problem (you can just train them on both) nor should it present much of a problem for many Windows users (many Windows applications have bizarre nonstandard interfaces), but it may be an issue if you are a migrating Mac OS user who is used to software written by highly interface-conscious developers sporting carefully designed interfaces and consistent UI elements throughout. This too can be worked through, nonetheless it is something to be planned for if migrating users from one of these platforms.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide