OpenSlug-2.3-beta release notes
Any users of OpenSlug-1.12-beta should upgrade as soon as possible to OpenSlug-2.3-beta using UpSlug.
Users of OpenSlug-2.0-beta should upgrade to 2.3-beta to get access to the new package feed - the OpenSlug-2.0-beta package feed will no longer be updated regularly (if at all.)
Sections in this page:
All changes are with respect to OpenSlug-2.0-beta. A major change corresponds to a change in the version number of the downloaded (remote) source. A minor change indicates that a package still uses the same source but has had a minor revision (including, possibly, addition of a patch) in the build.
(1) Release Email
The NSLU2-Linux development team is pleased to announce the source release of OpenSlug 2.3-beta. This source release can be found at the release page:
Information about the OpenSlug software and this release can be found at the OpenSlug home page. This page gives essential information for first time users of OpenSlug.
The full release notes for this software can be found in the OpenSlug-2.3-beta release notes.
Note that the OpenSlug software is intended for use by people who have previously installed and administered one or more Linux systems. If you are a first-time user of custom firmware for the NSLU2, then we recommend that you start with the Unslung firmware, and then make a decision whether to move to the OpenSlug firmware only after you are familiar with installing and running custom firmware on the NSLU2.
Due to licensing of the Intel IXP400 loadable kernel module, the binary releases are being prepared by a trusted third party, will be released separately on a different site from www.nslu2-linux.org, and will require you to agree to a click-through end-user license to be able to download the binary firmware image. As a result binary releases are made a few days after source releases.
Note that there is no charge for this click-through license, and (as far as we can tell - we are not lawyers, and you should make your own judgement before accepting the license) the only thing that the license prevents you from doing is to redistribute the Intel IXP400 loadable kernel module in a way which might subject the Intel IXP400 software to any other license obligations (this is a condition of use of the Intel IXP400 software which runs the built-in ethernet interface of the NSLU2).
Since the Intel source is compiled into a loadable kernel module (for OpenSlug, - the kernel module is just copied from the Linksys firmware for Unslung), then aggregating that loadable kernel module with the rest of the firmware does not subject the Intel software to any other license obligations and therefore complies with the Intel license.
However the nslu2-linux developent team cannot accept that license on your behalf, and therefore any individual who downloads the binary image must accept the Intel license on their own behalf before that individual can be given access to the binary image that our trusted third party will release.
Information about the binary release is sent to the NSLU2 mailing lists on http://groups.yahoo.com. If you are not familiar with building software from source you should use the binary release.
(2) Known bugs
The following bug reported in versions of OpenSlug to 2.3-beta was not fixed in 2.3-beta:
The following feature requests were not implemented in OpenSlug-2.3-beta and have been deferred for a future release (see the bug report for the current status):
The bugs currently known to exist in OpenSlug-2.3-beta may be found using the OpenSlug-2.3-beta bug query.
(3) Fixed bugs
The following bugs present in OpenSlug-2.0-beta have been fixed in OpenSlug-2.3-beta:
The remaining bugs reported in 1.12 and 2.0 have been fixed. The full list of bugs in OpenSlug (including fixed ones) can be found at the OpenSlug bug query.
(4) Major package changes
The following packages have undergone a major revision change. This means that a different revision of the package source code is being used. For further information consult the home page of the package.
(6) Package additions
These packages have been added to the build (there are many other packages which can be built from the source tree.)
(5) Package removals
The packages have been removed from the build (they may still be available in the source tree.)
(7) Minor package changes
The following packages have minor revisions. These changes can be seen in the source