Fedora in the Lab

 
 
By Jason Brooks  |  Posted 2010-06-16 Email Print this article Print
 
 
 
 
 
 
 


 

Fedora 13 in the Lab

I tested the x86-64 version of Fedora 13 on a Lenovo ThinkPad T60 and on virtual machines running under Fedora 13's implementation of the Linux KVM (Kernel-based Virtual Machine) virtualization host.

The x86 and x86-64 versions are available as DVD or CD images that comprise the entire distribution, as well as in Live CD and Live USB images that may be used to try out Fedora without modifying your hard drive. With the Live USB images, it's possible to save data from the live sessions on USB sticks, which makes them more convenient to use than the CD images.

Fedora 13 ships with a new, optional user management utility, called AccountsDialog, which will eventually replace Red Hat's system-config-users tool. The new tool puts a graphical face on some of the work that Red Hat has been doing to whittle away at the all-powerful superuser account in favor of more granularly parcelled permissions. For instance, where the existing utility runs as the root user from the get-go, the new tool launches without requiring administrator rights and asks for rights elevation as needed.

Red Hat has been moving in this direction over its past few releases, removing the requirement for administrative applications to run entirely with superuser rights, and tapping the PolicyKit framework to handle the permission-granting. What caught my eye in the new user tool is the option to configure users as Standard, Administrator or Supervised, with the unfamiliar-looking Supervised bucket as the default.

While the primary user account I'd created remained in the Supervised bucket, applications that supported the PolicyKit framework would ask for my system's root password when they required rights elevation. When I shifted my account to the Administrator class, the system asked instead for my account password. This change in permissions management sets the stage to give certain administrative rights to certain users, thereby allowing for finer-grained control over the system.

The move toward embracing PolicyKit within Fedora is still going on, and many tools still require root permissions. I used a command line utility, pkexec, to elevate my permissions to run some of these applications, but this tool does not work with graphical applications. For more information on the changes involving the user management tool and PolicyKit, see this mailing list thread: tinyurl.com/23d8xxq.

Elsewhere in the release, I was pleased to find that Red Hat's handy network management framework, cleverly known as NetworkManager, has picked up a command line interface to go along with the graphical tools to which it's been limited so far. The new utility, called cnetworkmanager, should be a welcome sight for those who work with headless Fedora servers and would like to use the same network configuration tool they've become accustomed to on GUI-based systems.

Another cool Fedora 13 feature that caught my eye was BFO, a Fedora take on the BKO (boot.kernel.org) project that enables administrators to boot a machine from a very small disc image and run or install Fedora from the network. I installed one of my test VMs using a svelte 626KB BFO image and found the process more streamlined than with previous Fedora network installation attempts. I recommend editing the boot command from the GRUB (Grand Unified Bootloader) screen to point to a nearby mirror of Fedora. I typically opt for the kernel.org mirror here in San Francisco.

I mentioned at the top of this review that my tests using Fedora 13 were nearly free of SELinux issues: The mandatory access control framework, which comes enabled on Fedora, typically gives me some trouble during tests. This time around, all was smooth until I hit Bug 566332 while connecting to my BlackBerry 8330 phone via Bluetooth. On the bright side, this snag gave me the opportunity to see Fedora's new SELinux trobuleshooter panel icon, which is modeled after an automobile's check engine light.

 


 
 
 
 
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