The CRUX Project Presented by Per Liden, Johannes Winkelmann, Matt Housh, Jay Dolan CRUX is a lightweight, i686-optimized Linux distribution targeted at experienced Linux users. The primary focus of this distribution is keep it simple, which is reflected in a straightforward tar.gz-based package system, BSD-style initscripts, and a relatively small collection of trimmed packages. The secondary focus is utilization of new Linux features and recent tools and libraries. CRUX also has a ports system which makes it easy to install and upgrade applications.

Why Another Distribution? ● Choice was limited at the time ● A learning experience for team members ● An “untainted” linux environment ● Most recent, yet stable, technologies ● No frills, simple by design

How did CRUX start? ● Created by Per Liden in May 2000 – “CRUX” was short, catchy, and available – Solo effort for first year ● CLC Project founded in 2001 – Coordinate user contributions – Birthplace for many features and tools

Ports and Packages ● A CRUX port is a directory containing several files which specify the build process for a particular software package. ● A CRUX package is the result of a port build process; that is, compiled binaries and accompanying files. ● A package is roughly equivalent to an.rpm or.deb file.

Ports – Distributing CRUX ports ● A client tool to download CRUX ports from a server ● Supports an arbitrary number of collections and transports – CVS – HTTP – Subversion – Rsync ● Creates a hierarchy of ports, similar to FreeBSD.

Pkgutils – A package manager ● A set of utilities to create, install, query, and remove CRUX packages. – Pkgmk – Create a package using Pkgfile – Pkgadd – Install a package to the system – Pkginfo – Query an installed package – Pkgrm – Remove an installed package ● These are implemented in Bash/C++ and provide the core of CRUX.

Prt-get ● Provides an additional layer atop Pkgutils: – Port (software) dependencies – Search and query functionality – Automated system updates – Filesystem abstraction ● Prt-get provides these features without upsetting the Ports and Pkgutils systems. It is optional. ● Prt-get still leaves the user in the “drivers seat”

HttpUp – Ports from the masses ● Provides ports distribution over HTTP which allows users to easily share their ports ● Seamless integration with Ports utility ● Requires only web space to host ports (not CVS, SVN, or other) ● Allows users behind firewalls to use Ports system

Status of Ports system ● CRUX provides “core” and “opt” ports collections from central SVN server – Approximately 600 ports ● There are over 60 HttpUp collections provided by CRUX users worldwide – Approximately 3400 ports ● In total there are over 4000 ports available

Accommodating Contributions ● HttpUp works well, but by itself results in fragmentation of Ports system – Each collection requires explicit subscription – Lack of collaboration among contributors ● A ports database provides a consolidated list of user collections – Searchable user interface – Gathers limited statistics

Accomodating Contributions... ● A “merged collection” allows ports distribution from one source ● Explicit subscription to each collection is no longer required, but still possible ● Addressing duplication, selection, and security become more feasible ● Ability to mirror and archive user and merged collections as an added bonus

CRUXCon 2005 ● Consolidation of CRUX and CLC projects to a common server ● Establishing a “Core” group to distribute the workload ● Restructuring and improving the Ports system ● Future plans and project direction – Release schedule – New features

Thank you! ● Questions? ●