/etc/rant - SUSE Rocks, Fedora Locks

Welcome to the 20th century of usability, Fedora Core 5. Too bad this is the 21st.

I hope you'll forgive me if I can't make good on the name of this column 100% of the time this month, because I will be including a few raves in this rant. I'll start with SUSE 10.0. I have been working on a SUSE 10.0 review for what seems like forever. The way things have been going, SUSE 11.0 probably will ship by the time I'm done.

If you read my rant from last month, you'll know I've upgraded to a dual-core AMD64 machine. I had to reinstall SUSE 10.0 on this new machine to continue my work on the review. I was tempted to call Novell and ask for the AMD64 version of SUSE 10.0, but I went ahead and installed SUSE from the DVD that came in the box they sent. Much to my surprise and delight, it installed an AMD64 version of SUSE. It was only after it installed the 64-bit version that I examined the box carefully. Sure enough, in fine print (at least it's fine print to my 53-year-old eyes), it says that the box includes multiple versions of SUSE, including the AMD64 version.

It gets better. SUSE includes Sun Java 1.5, and the 64-bit version of Firefox can actually use it. I had to kludge a 32-bit version of Firefox on Kubuntu in order to get Java working as a plugin.

I don't want to spend much more time waxing rhapsodic over SUSE, lest I include too much rave in this rant. But although there are a few things I don't like about SUSE 10.0, I would have no trouble recommending it to virtually anyone. I confess, I have never liked SUSE in the past. This version has changed my opinion entirely.

As of a few days before this writing, the final version of Fedora Core 5 became available. I downloaded and installed the AMD64 version. It won't boot. Why? Because Fedora Core configures the GRUB bootloader to boot the partition labeled /. As it happens, I have about three partitions with that same label. I boot the Kanotix live CD, edit the GRUB configuration and /etc/fstab to point to the actual partition, and now Fedora boots.

What is it with the Fedora people that they feel compelled to use disk labels instead of partition device names? I realize that this won't be a problem for the average user who uses only Fedora and no other distribution of Linux. But then again, the average user isn't likely to move Fedora to another partition or change the order of drives either, so the advantages of using disk labels will be lost on them. If the Fedora folks are bent on using disk labels, they could at least label the root partition something unique and identifying, like FC564ROOT for the AMD64 version and FC532ROOT for the i386 version.

I'll save you the rant on how disappointed I was with the 64-bit version as a desktop and tell you I decided to go with Fedora Core 5 i386 instead.

This time I edit the GRUB and /etc/fstab files after the installation finishes so it will boot the first time. As has been the case for years of using Red Hat distributions, it gets hung up on starting Sendmail about half the time. Surely I can't be the only person who has experienced this? Why does this problem still exist? Why does Fedora even install Sendmail? There have been superior alternatives for years.

Kudos to Fedora for finally including a software package manager that lets you install packages other than the ones they want you to use. It would be nicer if it was even remotely intuitive, but then the Fedora folks are GNOME lovers, so making it intuitive would violate the GNOME specification. It would be even nicer if the software updater didn't run so slow that I always assume it is simply frozen and kill it. I always fall back to yum update, but even the command-line version of Yum doesn't run, it crawls. Slowly.

The good news about Fedora Core 5 is that it not only includes SELinux (NSA Security Enhanced Linux), but it is preconfigured and enabled by default. It also makes it easy to configure SELinux policies. I love this. If SELinux is important to you, Fedora may be your bag.

But here's my big beef aside from the bonehead disk label problem and other nuisances. Why are the Fedora folks so anal about licenses? There's no Sun Java in Fedora. There's no Flash plugin. I can almost excuse the maintainers for leaving these things out, but Fedora makes no effort at all to make it a no-brainer to add them. How many of you out there really don't want your browser to be able to support Java or Flash? Aren't you going to add these things anyway? So why not make it easy? Ubuntu/Kubuntu makes it easy, and these distros are based on Debian, the most license-anal distro on the planet.

Bottom line—if you're already a Fedora fan, you'll want Core 5. If you use anything else, now's not the time to switch.

Nicholas Petreley is Editor in Chief of Linux Journal and a former programmer, teacher, analyst and consultant who has been working with and writing about Linux for more than ten years.

______________________

Comments

Comment viewing options

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

commercial vs free distro

Tejas Kokje's picture

You are comparing a freely downloadable distro (Fedora) with a commercial paid version of distro from Novell. I don't think you are comparing apples to apples.

Download free SUSE from opensuse.org and compare it with Fedora.

Tejas Kokje

Rant about Autopackage

Anonymous's picture

Hey, could you take a look at Autopackage and rant about it in a future column? I donno about you guys, but making it easy for people to install software off the web sounds like a bad idea to me.

java license

mattdm's picture

Nicholas, have you actually read the Java license?

It clearly requires several things which make it impossible to include in Fedora -- even if Fedora accepted non-Free/OSS licenses.

For one thing, redistribution is only allowed with "Your programs", and only "for the sole purpose of running your Programs" -- you can't distribute it as a convenient operating system component. (It's pretty clear about that -- your programs must "add significant and primary functionality to the Software" -- you can't just include a "hello world" to get around this.)

Furthermore, "you do not distribute additional software intended to replace any component(s) of the Software" apparently means that gcj has to be patched out of gcc, which would be unfortunate given how strong that's gotten.

And then there's the indemnification clause...

use of labels on disk partitions

Gerald Werner's picture

Disks are cheep, so I usually install multiple partitions and OSes on a computer. When it comes to labels for the partitions, I make sure each has a unique label (they do not have to match the mount points). So for the first OS, I use "/1" and "/boot1", and for the second OS, "/2" and "/boot2". After I backup an OS from one partition to another, all I need to do is edit the numbers in the master grub.conf file and the copied /etc/fstab file. It is a lot easier than remembering partition numbers. Life is great having a bootable backup of the OS.

- Jerry

Webinar
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Webinar
Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix