Difference between revisions of "Bering-uClibc 4.x"
Davidmbrooke (Talk | contribs) (Added content) |
|||
| Line 1: | Line 1: | ||
| − | + | ==Overview== | |
| + | [[Bering-uClibc]] is one of the branches of the [[LEAF]] (Linux Embedded Appliance Framework) project, delivering on [[LEAF]]'s ambition to provide a secure, feature-rich, customizable embedded Linux network appliance for use in a variety of network topologies. Although it can be used in other ways, its primary goal is as a Internet gateway, router, firewall and wireless access point. | ||
| + | |||
[[Bering-uClibc 4.x]] is basically [[Bering-uClibc 3.x]] brought up to date with the latest versions of the main software components. | [[Bering-uClibc 4.x]] is basically [[Bering-uClibc 3.x]] brought up to date with the latest versions of the main software components. | ||
In particular: | In particular: | ||
* The Linux Kernel is upgraded from 2.4.x to 2.6.x. | * The Linux Kernel is upgraded from 2.4.x to 2.6.x. | ||
* The Shorewall package is upgraded from 3.x to 4.x. | * The Shorewall package is upgraded from 3.x to 4.x. | ||
| + | * The uClibc library is upgraded from 0.9.28 to 0.9.30. | ||
These changes bring both advantages and disadvantages compared to [[Bering-uClibc 3.x]]. | These changes bring both advantages and disadvantages compared to [[Bering-uClibc 3.x]]. | ||
| − | The main disadvantage is that the distribution is much larger which means it no longer has any chance of being hosted on floppy disk media | + | The main disadvantage is that the distribution is much larger which means it no longer has any chance of being hosted on floppy disk media. |
| − | The | + | |
| + | ==Main Features== | ||
| + | The key characteristics of [[Bering-uClibc 4.x]] are: | ||
| + | * Based on a recent release of the Linux Kernel. | ||
| + | * Runs on industry standard devices with x86 processors. | ||
| + | * Designed to perform well on relatively low-specification hardware. In particular: | ||
| + | ** The system runs from an in-memory filesystem. Disk storage is only required for booting and for holding configuration settings. | ||
| + | ** The [http://www.uclibc.org/ uClibc] C library is used in place of the [http://www.gnu.org/software/libc/libc.html GNU C Library] since uClibc is much smaller in size. | ||
| + | ** Considerable use is made of [http://www.busybox.net/ BusyBox] utilities as replacements for larger applications. | ||
| + | * Focussed on providing excellent networking facilities. | ||
| + | |||
| + | |||
| + | ==Development History== | ||
| + | Work on [[Bering-uClibc 4.x]] started in April 2010, with [[User:Nitr0man|Nitr0man]] as the lead developer and contributions from [[User:Kapeka|Kapeka]] and [[User:Davidmbrooke|davidMbrooke]] among others. | ||
| + | The development was mostly completed by late October 2010, with multiple Alpha test systems "in production". | ||
| + | The first Beta test version is expected to be released before the end of 2010. | ||
Version Changelog | Version Changelog | ||
* [[Bering-uClibc 4.x - Changelog]] | * [[Bering-uClibc 4.x - Changelog]] | ||
| − | |||
| + | ==Further Documentation== | ||
For further information see: | For further information see: | ||
| − | * [[Bering-uClibc 4.x - User Guide]] | + | * [[Bering-uClibc 4.x - User Guide]] for Installers, Administrators and general Users. |
| − | * [[Bering-uClibc 4.x - Developer Guide]] | + | * [[Bering-uClibc 4.x - Developer Guide]] for Developers of new features or new application Packages. |
| + | |||
| + | [[Category:Bering-uClibc_4.x]] | ||
Revision as of 20:38, 8 November 2010
Overview
Bering-uClibc is one of the branches of the LEAF (Linux Embedded Appliance Framework) project, delivering on LEAF's ambition to provide a secure, feature-rich, customizable embedded Linux network appliance for use in a variety of network topologies. Although it can be used in other ways, its primary goal is as a Internet gateway, router, firewall and wireless access point.
Bering-uClibc 4.x is basically Bering-uClibc 3.x brought up to date with the latest versions of the main software components. In particular:
- The Linux Kernel is upgraded from 2.4.x to 2.6.x.
- The Shorewall package is upgraded from 3.x to 4.x.
- The uClibc library is upgraded from 0.9.28 to 0.9.30.
These changes bring both advantages and disadvantages compared to Bering-uClibc 3.x. The main disadvantage is that the distribution is much larger which means it no longer has any chance of being hosted on floppy disk media.
Main Features
The key characteristics of Bering-uClibc 4.x are:
- Based on a recent release of the Linux Kernel.
- Runs on industry standard devices with x86 processors.
- Designed to perform well on relatively low-specification hardware. In particular:
- The system runs from an in-memory filesystem. Disk storage is only required for booting and for holding configuration settings.
- The uClibc C library is used in place of the GNU C Library since uClibc is much smaller in size.
- Considerable use is made of BusyBox utilities as replacements for larger applications.
- Focussed on providing excellent networking facilities.
Development History
Work on Bering-uClibc 4.x started in April 2010, with Nitr0man as the lead developer and contributions from Kapeka and davidMbrooke among others. The development was mostly completed by late October 2010, with multiple Alpha test systems "in production". The first Beta test version is expected to be released before the end of 2010.
Version Changelog
Further Documentation
For further information see:
- Bering-uClibc 4.x - User Guide for Installers, Administrators and general Users.
- Bering-uClibc 4.x - Developer Guide for Developers of new features or new application Packages.
