[This page is still under construction]
Note: Unslung 6.10-beta is not considered an upgrade to Unslung 6.8-beta. There are no significant
changes that would justify an upgrade, and there is no specific support for upgrading from Unslung
6.8-beta to Unslung 6.10-beta. Upgrade information from 5.5-beta to 6.8-beta applies to upgrading
from 5.5-beta to 6.10-beta as well.
Changes from Unslung 6.8-beta to Unslung 6.10-beta
Bugfixes and Minor Changes:
| Fix | Comments |
| NLS Codepages | Codepage 850 is now built-in, diversion script for added codepages no longer necessary |
| Samba Codepages | Moved to a separate package for ease of maintenance |
| Slingbox Support | Minor syntax corrections to Linksys scripts |
| Security | Disable ourtelnetrescueuser account entirely |
| Documentation | Replace firmware upgrade web page |
| Format Fix | Change mkfs.ext3 to work around odd Linksys GUI bug |
| Space Recovery | remove duplicate date binaries |
| Root Account | Created home directory for root |
| Cleanup /var | Selected cleanup of /var at boot |
| Boot Delay | Disk wait time in early bootup increased for large disks |
| Completion | Tab-completion turned on for built-in shell |
| Utilities | "more", "dos2unix", "unix2dos" utilities added |
Internal Features:
| Feature | Comments |
| Boot-time Diagnostics | Special feature enables netconsole and nc to direct console and startup script output to the network for diagnosing bootup and startup failures, in the absense of a serial console. |
| Bootdisk | Special feature automatically executes scripts on FAT-formatted devices at boot-time in order to provide diagnostics, recovery, or automation |
| Slingbox fdisk | Addition of a fully-functional "fdisk" utility to the firmware |
Packages removed:
| Package | Reason for removal |
| cpio | Moved into slingbox (to save flash space) |
| findutils | Moved into slingbox (to save flash space) |
| busybox 0.60 (Linksys) | Superceded by Slingbox |
| resling, slingover | Obsolete |
Packages added:
| Package | Reason for addition |
| kernel-module-netconsole | boot-time diagnostic feature |
| rc.bootdisk | boot-time execution feature |
| update-rc.d | |
Packages changed:
| Package | Unslung 6.8-beta version | Unslung 6.10-beta version | Comments |
| ipkg | 0.99.154-r2 | 0.99.163-r6 | |
| libc6 | 2.2.5-r5 | 2.2.5-r13 | |
| libgcc | 3.4.4-r3 | 3.4.4-r7 | |
| slingbox | 1.00-r8 | 1.3.1-r2 | |
| kernel | 2.4.22.l2.3r63-r10 | 2.4.22.l2.3r63-r21 | |
| libipkg | 0.99.154-r2 | 0.99.163-r6 | |
| nslu2-linksys-libs | 2.3r63-r2 | 2.3r63-r3 | |
| unslung-rootfs | 2.3r63-r11 | 2.3r63-r22 | |
| update-modules | 1.0-r4 | 1.0-r6 | |
Should you upgrade from Unslung 6.8-beta to 6.10-beta?
The answer is "probably not, unless you're having specific problems with
Unslung 6.8-beta".
Anyone installing Unslung from scratch should always use the latest
version (in this case, Unslung 6.10-beta). Anyone running Unslung
5.5-beta (or an earlier version) is encouraged to upgrade, since we
don't support that version any more.
If you already have Unslung 6.8-beta installed, unslung to an external
hard disk, and running happily, then there is no real reason for you to
go through the hassle of upgrading the firmware on the internal flash.
As noted above, the changes between Unslung 6.8-beta and Unslung 6.10-beta are
mostly about improving the installation and recovery experience.
There are no new normal-run-time user-visible features.
The kernel has not changed, so there is no new hardware support. If a
device didn't work on Unslung 6.8-beta, then it still won't work on
Unslung 6.10-beta (and it's very likely that it will *never* work on the
Unslung firmware, since the kernel is effectively frozen).
The Linksys binaries have not changed, and there are no changes to the
web interface (except the removal of the non-working web upgrade page).
There are no performance improvements. The same optware packages will
run on either 6.8-beta to 6.10-beta, and will run with exactly the same
features and performance. Optware will continue to support 6.8-beta and
6.10-beta equally well into the future.
However, if you have not been able to get Unslung 6.8-beta to be able to
boot from an external hard disk, then you might want to give 6.10-beta a
try, as we have increased the disk wait time in early bootup to support
large disks that take longer to initialize. In fact, if you haven't
been able to get 6.8-beta to work, then we recommend trying again with
6.10-beta and then reporting the failure on the mailing list.