A look at Progeny Debian Beta [LWN.net]

July 28, 2004

This article was contributed by Joe 'Zonker' Brockmeier.

The Progeny Debian 2.0 Developer Edition beta has been out for a little while now, long enough for this writer to whip it onto a laptop and take it for a spin.

There's a lot to like in the latest release. Though it's not quite bug free, it is looking much more polished, and good enough for day to day usage if one doesn't mind a few rough edges. For example, the installer set the mouse pointer to "/dev/input/mice" rather than "/dev/psaux" -- which caused X to come to an abrupt halt until this was corrected. Sound was not detected or correctly configured, though my wireless network card was automatically recognized.

Users are given the choice of desktop, workstation, server or custom installation. While the installer worked flawlessly, it seemed to take quite a long while to copy over packages. This isn't a major issue, but one hopes that the installation will be optimized by a final release for users who have to perform multiple installs. In all, the install closely resembles a Fedora Core install, so users who have some experience with Anaconda will feel right at home.

By default, this release installs the 2.6.6 Linux kernel. A 2.4 kernel is available as a component -- though some components are non-functional in the beta, so it's not entirely clear whether the 2.4 kernel component can be installed.

Speaking of components, it would be negligent not to mention that this release is "a showcase of Progeny's Componentized Linux technology," and not just any Linux distribution. (Interested users can find the entire list of available components here.) From the end user's perspective, it's nice to be able to install a single package rather than picking a slew of packages that are necessary to run a program. Even with apt's wonderful dependency system, it is often necessary to install several packages to arrive at one functional program.

Unfortunately, the beta's "sources.list" is strictly for loading packages off of CD-ROM. Users who have become used to using apt to install packages anywhere they happen to have a network connection will not be pleased with needing to cart CDs with them. It's not immediately obvious how to add Progeny's componentized package lists to the "sources.list," which has confused a number of the beta testers. Of course, packages from Debian testing seem to work quite well in absence of a Progeny network package source.

In all, the release shows a lot of promise. While it's not quite yet ready for prime time, the Progeny folks have made a lot of progress since the alpha release back in April.

(Log in to post comments)

A look at Progeny Debian Beta

Posted Jul 30, 2004 20:27 UTC (Fri) by brouhaha (subscriber, #1698) [Link]

Even with apt's wonderful dependency system, it is often necessary to install several packages to arrive at one functional program.

Doesn't that just mean that some dependency information is missing from one of the Debian packages? Surely that's easily fixed if it's brought to the package maintainer's attention?

I still do not understand how this "componentized" stuff works, and I really don't want to take the time to experiment with it unless I have some minimal understanding of the concept first. How exactly is a component different than a package, or a group of packages with dependencies? If evolution and gnucash both needed some library to work, is that library packaged with both components, or do you need to install the library component? In the former case, it seems likely to cause problems rather than solve them, and in the latter case I don't see how it is different than packages.

The web site seems to explain what the benefits are, but not how they are achieved. When it was first announced amid great fanfare, I got the distinct impression that it was just a marketing breakthrough of calling packages by a new name. I'd like to think that my first impression was wrong and that there is actually something of substance to the concept, and it would help a lot if there was an actual explanation of what it really means.

A look at Progeny Debian Beta

Posted Aug 11, 2004 20:16 UTC (Wed) by sethml (subscriber, #8471) [Link]

Doesn't that just mean that some dependency information is missing from one of the Debian packages?

I suspect that the issue referred to in the article involves optional components of programs. For example, 'apt-get install gimp' will install a functional copy of gimp, but not a full-featured version. To install gimp completely, you need something like 'apt-get install gimp gimp-data-extras gimp-help-en gimp-manual gimp-python gimp-svg gimp-perl'. Whether you think this is a good thing or not probably depends on whether you're trying to save disk space or not.