Goals for SlugOS5:

1) EABI (both BE and LE)

Use a Snapshot of the Angstrom toolchain to assure Devs of a non-moving toolchain.

2) opkg (replacement for ipkg, but without gpg signing due to size)

opkg is already implemented in Angstrom so is already available.

In addition to those goals, we plan to explore the following areas:

3) Busybox improvements - we will be adding many more of the busybox versions of standard Linux commands, and enabling many more options and features for the busybox versions -- this will permit us to replace some of the full versions of utilities in the base flash, freeing up space for other features.

4) /dev improvements - managing USB storage devices (where the same device can end up as /dev/sda on one boot, and as /dev/sdb on the next boot, for example), is problematic. The current solution using udev needs to be improved so that we can more gracefully handle some of the interesting situations SlugOS users have come up with in the past!

need to write persistent naming rules to handle this

5) Recovery features - something similar to the Unslung "bootdisk" concept will be added; allowing the use of external devices to diagnose or communicate with a SlugOS system. While lower on the list, it would also be nice to have netconsole support built-in, as it is on Unslung.

6) Kernel - this sort of goes without saying, but we will be upgrading to whatever kernel is stable at the time of the release.

7) Boot infrastructure - SlugOS users have spoken, we need to do a better job in this release to make booting from NFS work "out-of-the-box". If the /dev improvements work out, it would be desirable to have the low-level support to permit one to "turnup" to a RAID device -- this may or may not be practical. The networking utilities on the core image will also be expanded.

Perhaps different images with NFS or RAID as emphasis?

(original source for this wiki page came from http://tech.groups.yahoo.com/group/nslu2-developers/message/1891)