Under the Hood with Fedora 10

By Jason Brooks  |  Posted 2008-12-10 Print this article Print


I tested the x86 version of Fedora 10 on a Lenovo ThinkPad T60 and on virtual machines running under Linux's KVM (Kernel Virtual Machine) facility and under Sun Microsystems' VirtualBox 2.0 desktop virtualization application. I also tested the x86-64 version of Fedora 10 on a generic dual-core Advanced Micro Devices Athlon64 that we'd assembled in the lab.

The only hardware issue I experienced during these tests was with Fedora 10's autodetection of the monitor for our x86-64 machine. Rather than start up its graphical interface, Fedora 10 presented me with a blinking cursor in the upper left corner of my display. I got back on track by switching to a different virtual terminal, installing the system-config-display tool from Fedora's online software repositories and using the tool to chef up my own display configuration.

For one of my VM installations, I started out with a Fedora 9 installation that I then upgraded to Version 10. I was pleased to see that Fedora offers a utility, called "preupgrade," for conducting in-place upgrades between Fedora versions.

Also regarding installation, it's worth noting that Fedora does the best job of any Linux distribution I've tested of making it easy to install the distribution with hard drive encryption. Canonical's Ubuntu 8.10 does not support encrypted configurations from its standard installer disk, and Novell's OpenSUSE lacks any support for root and swap partition encryption.

Along similar lines, new in Fedora 10 is an encryption-by-default setting for the persistent home partition on the distribution's live USB installations.

Fedora 10 has continued to progress in its PackageKit software installation and update system, which forms a graphical front end to the distribution's Yum and RPM back-end software management tools. The best thing about PackageKit, at this point, is its integration with the PolicyKit permissions management framework that ships with Fedora 10.  For instance, it's possible to create a configuration in which certain limited-rights users are allowed to apply software updates signed with preapproved digital keys without entering an administrative password.

Red Hat has been steadily building out a complete open-source virtualization stack for the past several years, first based on Xen, and now centered most directly around KVM. In Fedora 10, Red Hat's virt-manager hypervisor management and VM creation utility has picked up a handful of enhancements relating to creation of new virtual machines on remote hosts running Xen or KVM.

Another relatively small yet worthwhile Fedora 10 enhancement that I noticed is the addition of the "/usr/local/sbin," "/usr/sbin" and "/sbin" locations to the default PATH established for normal users. A handful of command-line tools that can be useful to non-root users, such as the ifconfig command that provides network information, live in these "sbin" locations, and the PATH change enables users simply to type "ifconfig" (as opposed to "/sbin/ifconfig") to run this command.

eWEEK Labs Executive Editor Jason Brooks can be reached at jbrooks@eweek.com.

As Editor in Chief of eWEEK Labs, Jason Brooks manages the Labs team and is responsible for eWEEK's print edition. Brooks joined eWEEK in 1999, and has covered wireless networking, office productivity suites, mobile devices, Windows, virtualization, and desktops and notebooks. JasonÔÇÖs coverage is currently focused on Linux and Unix operating systems, open-source software and licensing, cloud computing and Software as a Service. Follow Jason on Twitter at jasonbrooks, or reach him by email at jbrooks@eweek.com.

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel