NSLU2-Linux
view · edit · print · history

Main.HowToGetInvolved History

Hide minor edits - Show changes to markup

January 29, 2007, at 05:09 PM by fcarolo -- removed broken wikilinks
Changed lines 2-3 from:

Monotone repository at monotone.nslu2-linux.org.

to:

Monotone repository at monotone.nslu2-linux.org.

Changed line 10 from:

built using OpenEmbedded in the Monotone repository, and Optware

to:

built using OpenEmbedded in the Monotone repository, and Optware

August 12, 2006, at 08:55 PM by hs -- Typo
Changed line 46 from:

PS: if you would like to support nslu2-linux, yo might consider a donation.

to:

PS: if you would like to support nslu2-linux, you might consider a donation.

June 22, 2006, at 08:31 PM by AdamBaker -- update to reflect CVS to SVN migration
Changed lines 4-5 from:

Optware packages (formerly known as Unslung packages) are developed and maintained in the CVS repository on sf.net/projects/nslu which is based on the OpenWrt build system which

to:

Optware packages (formerly known as Unslung packages) are developed and maintained in the SVN repository on svn.nslu2-linux.org which is based on the OpenWrt build system which

Changed line 12 from:

in the CVS repository. We are still hopeful that someone with

to:

in the SVN repository. We are still hopeful that someone with

Changed line 33 from:

contributing them to the CVS repository on sf.net and announce them on

to:

contributing them to the SVN repository and announce them on

May 28, 2006, at 11:36 PM by marceln -- Updated to unslung 6.x
Changed lines 39-40 from:

If you are a happy Unslung user, then now is the time to upgrade to Unslung 5.x.

to:

If you are a happy Unslung user, then now is the time to upgrade to Unslung 6.x.

May 28, 2006, at 09:45 PM by Werner Teeling -- followup: like it? donate -> question.
Changed lines 46-47 from:

PS: if you would like to support nslu2-linux, yo might consider a donation?.

to:

PS: if you would like to support nslu2-linux, yo might consider a donation. (Who updates the 'donations & sponsors' page?)

May 28, 2006, at 09:42 PM by Werner Teeling -- added: make donation, and q. about donationlist.
Added line 46:

PS: if you would like to support nslu2-linux, yo might consider a donation?.

April 18, 2006, at 03:13 AM by ironstorm -- test edit
Added line 45:
August 10, 2005, at 03:18 AM by rwhitby --
Changed lines 2-4 from:

Monotone repository at nslu2-linux.bkbits.net.

Unslung packages are developed and maintained in the CVS

to:

Monotone repository at monotone.nslu2-linux.org.

Optware packages (formerly known as Unslung packages) are developed and maintained in the CVS

Changed line 10 from:

built using OpenEmbedded in the Monotone repository, and Unslung

to:

built using OpenEmbedded in the Monotone repository, and Optware

Changed line 19 from:

The OpenSlug firmware (which is a complete kernel and ramdisk

to:

The OpenSlug firmware (which is a complete kernel and ramdisk

Changed line 32 from:

If you are an Unslung package developer, then please continue

to:

If you are an Optware package developer, then please continue

August 10, 2005, at 03:16 AM by rwhitby --
Changed lines 37-39 from:

then look at AddAPackageToUnslung to find out how to get started.

to:

then look at the Optware Development page to find out how to get started.

August 10, 2005, at 03:13 AM by rwhitby --
Changed lines 1-3 from:

The Unslung firmware uses the BitBake/OpenEmbedded build system kept in a BitKeeper repository at nslu2-linux.bkbits.net.

to:

The Unslung firmware uses the OpenEmbedded build system kept in a Monotone repository at nslu2-linux.bkbits.net.

Changed line 10 from:

built using BitBake/OpenEmbedded in the BitKeeper repository, and Unslung

to:

built using OpenEmbedded in the Monotone repository, and Unslung

Changed lines 13-14 from:

extensive BitBake/OpenEmbedded knowledge will step forward and work out how to get the BitBake/OpenEmbedded packages (which assume a different set of base

to:

extensive OpenEmbedded knowledge will step forward and work out how to get the OpenEmbedded packages (which assume a different set of base

Changed lines 21-22 from:

Linksys firmware) is also being built using the BitBake/OpenEmbedded build system in the BitKeeper repository. The OpenSlug firmware is immediately

to:

Linksys firmware) is also being built using the OpenEmbedded build system in the Monotone repository. The OpenSlug firmware is immediately

Changed line 29 from:

BitBake/OpenEmbedded experience, then visit the IRC channel and help out with

to:

OpenEmbedded experience, then visit the IRC channel and help out with

Changed line 37 from:

then look at http://www.nslu2-linux.org/wiki/Unslung/AddAPackageToUnslung

to:

then look at AddAPackageToUnslung

June 14, 2005, at 01:23 PM by rwhitby --
Changed lines 1-9 from:

The Unslung 3.x firmware uses the BitBake/OpenEmbedded build system kept in a BitKeeper repository at nslu2-linux.bkbits.net - this firmware is in beta testing and it can currently do everything that the Unslung 1.x and Unslung 2.x firmware could do (and a little bit more). The difference is that the Unslung 3.x firmware runs completely from a jffs2 filesystem in the internal flash memory of the NSLU2.

Unslung 3.x currently uses exactly the same packages as the Unslung 1.x and 2.x firmware does, and the packages are still developed and maintained in the CVS

to:

The Unslung firmware uses the BitBake/OpenEmbedded build system kept in a BitKeeper repository at nslu2-linux.bkbits.net.

Unslung packages are developed and maintained in the CVS

Changed lines 22-27 from:

system in the BitKeeper repository, but it is at a very early alpha stage. It is envisaged that the OpenSlug firmware will immediately be able to take advantage of the 1500 packages when it starts working (because it will use the set of base files that the OpenEmbedded packages expect to exist).

to:

system in the BitKeeper repository. The OpenSlug firmware is immediately able to take advantage of many of the 1500 OpenEmbedded packages.

Changed lines 40-41 from:

If you are a happy Unslung 1.x or 2.x user, then now is the time to upgrade to Unslung 3.x.

to:

If you are a happy Unslung user, then now is the time to upgrade to Unslung 5.x.

January 20, 2005, at 10:54 PM by tman --
Changed lines 1-53 from:

Describe HowToGetInvolved here.

to:

The Unslung 3.x firmware uses the BitBake/OpenEmbedded build system kept in a BitKeeper repository at nslu2-linux.bkbits.net - this firmware is in beta testing and it can currently do everything that the Unslung 1.x and Unslung 2.x firmware could do (and a little bit more). The difference is that the Unslung 3.x firmware runs completely from a jffs2 filesystem in the internal flash memory of the NSLU2.

Unslung 3.x currently uses exactly the same packages as the Unslung 1.x and 2.x firmware does, and the packages are still developed and maintained in the CVS repository on sf.net/projects/nslu which is based on the OpenWrt build system which is based on the buildroot system found on uClibc.org. There was a plan to try and take advantage of the 1500 packages available in OpenEmbedded and try and make them work with the Unslung firmware, but that has proved to be more difficult than first envisioned. So for the short and medium term, Unslung firmware will be built using BitBake/OpenEmbedded in the BitKeeper repository, and Unslung packages will continue to be built using the home-grown build system in the CVS repository. We are still hopeful that someone with extensive BitBake/OpenEmbedded knowledge will step forward and work out how to get the BitBake/OpenEmbedded packages (which assume a different set of base files from what exists in the Linksys ramdisk) to work with the Unslung firmware and root filesystem (which is, by definition, designed to use the Linksys root filesystem to retain the stock product functionality).

The OpenSlug firmware (which is a complete kernel and ramdisk replacement, treating the NSLU2 as hardware board and not re-using any Linksys firmware) is also being built using the BitBake/OpenEmbedded build system in the BitKeeper repository, but it is at a very early alpha stage. It is envisaged that the OpenSlug firmware will immediately be able to take advantage of the 1500 packages when it starts working (because it will use the set of base files that the OpenEmbedded packages expect to exist).

So, if you are a seasoned embedded Linux developer, then visit the IRC channel and help out with OpenSlug.

If you are an embedded Linux userspace developer with extensive BitBake/OpenEmbedded experience, then visit the IRC channel and help out with getting the OpenEmbedded packages to work with Unslung.

If you are an Unslung package developer, then please continue contributing them to the CVS repository on sf.net and announce them on the mailing list.

If you are an Unslung user, and want to become a package developer, then look at http://www.nslu2-linux.org/wiki/Unslung/AddAPackageToUnslung to find out how to get started.

If you are a happy Unslung 1.x or 2.x user, then now is the time to upgrade to Unslung 3.x.

If you are an unhappy Unslung user, then let us know why you are unhappy...

If you are none of the above, then it's time to buy yourself an NSLU2, load the Unslung firmware onto it, and join the fun :-)

view · edit · print · history · Last edited by fcarolo.
Based on work by hs, AdamBaker, marceln, Werner Teeling, ironstorm, and rwhitby.
Originally by tman.
Page last modified on January 29, 2007, at 05:09 PM