There are no comments up to now.
| Beyond the Linux Distribution? |
|
|
|
| Monday, 26 May 2008 | |
|
After reading about Ian Murdock's plans for Componentized Linux, I got to thinking about the current state of Linux. If I've understood his intentions, it sounds like what he's trying to do is create some kind of distribution-independent central repository of Linux software, similar to the CPAN/Perl model. In the CPAN/Perl model, a user downloads the Perl runtime from a variety of sources, probably his or her specific Linux distribution. To get value out of it, however, the user connects to CPAN, the central repository of Perl modules, and chooses exactly what he/she wants, which is then downloaded and installed into the existing Perl core. So why couldn't the same principle be applied to Linux distributions? An example architecture would consist of a variety of core distributions, consisting of essential runtime software, like an installer, a kernel, and various packages that allow you to download further software. Behind the individual distributions, however, would be a central repository of Linux software (call it the Central Linux Package Repository, or CLPR). The user would be presented with a list of available packages, from which he or she would choose what to install (X, GNOME, Mozilla, Apache, etc.). The core would connect to CLPR and download the individual packages, configure them according to user specifications, and install them on the local system. The difference here is that there is only one central Linux software repository, not one for each separate distribution out there. To enhance the value of the Linux platform in general, software would be committed to the central repository, and thus would be available to users of each distribution immediately. It would conserve packaging effort and bandwidth, since the software wouldn't be duplicated 100 times for 100 distributions. The key here, of course, would be the use of standards like the FHS and LSB specifications. These projects would tie together all the various Linux distributions and make CLPR packages work appropriately for all distributions. Take Debian, for example. In this new Linux system, Debian would consist of a Core and an Installer. The Installer would set up the Core, the kernel, the network, and a CLPR package manager (based on apt, say). It would then present the user with an aptitude or tasksel-like tool that would allow him/her to choose which software it should install. It would connect to the CLPR, download the LSB-compliant software, and install it, producing an up-to-date, widely tested, standards-based solution for the user. Is this what Murdock is trying to do? If so, it sounds like an amazing idea.
» No Comments
» Post Comment
|
| < Prev | Next > |
|---|
Main Menu
| Home |
| About |
| Articles |
| News |
| Contact Us |
