Bering-uClibc 7.x - User Guide - Introduction
|Bering-uClibc 7.x - User Guide||Next|
The following important terms are used consistently throughout this User Guide. It is essential that the differences between them are understood.
Packages are files with a .lrp extension and are the main building blocks of a Bering-uClibc 7.x installation.
The functionality of Bering-uClibc 7.x can be tailored by adding and removing Packages from the default set.
In general, each Package implements one "application" or "service" - for example the
mhttpd.lrp package implements a mini HTTP server daemon.
If you are familiar with other Linux distributions then think of Packages as being equivalent to Red Hat .rpm files or Debian .deb files.
Sometimes, Packages are dependent on other Packages. Dependencies are listed in the "Requires" section of the Package help text.
Package dependencies will be resolved during installation, if the required Package(s) are available on the boot media.
The "core" of the Linux kernel only includes support for a very basic set of services and hardware devices. Any features outside this core must be added in the form of dynamically loadable kernel Modules. For example, the core kernel does not include support for the e100 Ethernet device driver. When running Bering-uClibc 7.x on a system with a network interface card which requires this driver the Module must be loaded in order for the network interface card to be used.
Kernel Modules are present in all Linux distributions, so documentation and instructions for other distributions can often be useful for Bering-uClibc 7.x. While Module loading has been automated to a significant extent, though there is still a need to understand the mechanics of Module loading more than with other Linux distributions which have the luxury of more disk and memory resources.
The starting point for any Bering-uClibc 7.x installation is one of the downloadable disk Images.
These contain all of the available Packages and Modules, and a default configuration which loads a small set of Packages suitable as a starting point for most users. This default configuration can also be thought of as a quick setup for the impatient user, meaning you can immediately use the box as a cable_modem firewall, the rules in
/etc/shorewall/rules are correctly preset for that.
Different disk Image files are available, tailored for different types of hardware. Later sections of this User Guide explain how to choose the most appropriate Image for your requirements.