NSLU2-Linux
view · edit · print · history

SlugOS.UsingTheBinary History

Hide minor edits - Show changes to markup

February 07, 2010, at 08:16 PM by kyle -- add warning about wifi
Changed lines 101-103 from:
to:

NOTE: If you run this tool over wifi and it fails with the error "no NSLU2 machines found in upgrade mode" then try connecting to the network with a wire.

August 31, 2008, at 06:10 PM by thx1011 -- Added note about first boot time duration
Changed line 104 from:
  1. After a successful flash the NSLU2 will reboot. SlugOS uses the ready/status LED to indicate boot progress. The LED sequence is described in more detail in OpenSlugLEDsDuringBoot.
to:
  1. After a successful flash the NSLU2 will reboot. SlugOS uses the ready/status LED to indicate boot progress. The LED sequence is described in more detail in OpenSlugLEDsDuringBoot. (Note: The first boot will take some time, around five minutes.)
November 08, 2007, at 09:34 PM by Tobias Balle-Peresen -- Turn off lights when flashing newer slugs.
Changed lines 93-94 from:

NOTE: Slugs produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

to:

NOTE: Slugs produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. Carrying out the procedure in a darkened room makes it easier to tell when the light changes. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

October 17, 2007, at 01:22 AM by fcarolo -- updated links and formatting
Changed lines 14-15 from:

SlugOS will not work on anything else.

to:

SlugOS will not work on anything else.

Changed line 17 from:

devices is needed in order to install packages onto the device and make SlugOS `useful:

to:

devices is needed in order to install packages onto the device and make SlugOS useful:

October 17, 2007, at 01:20 AM by fcarolo -- updated links and formatting
Changed lines 4-5 from:

Aliases: DebianSlug, OpenSlug

to:

Aliases: OpenSlug and DebianSlug

Changed line 8 from:

The binary is intended to be loaded ('flashed') into the flash ROM of a LinkSys NSLU2. More experienced users might flash one of the following devices:

to:

The binary is intended to be loaded ('flashed') into the flash ROM of a supported device. The original target for SlugOS is the LinkSys NSLU2, but more experienced users might flash one of the following devices:

Changed lines 16-20 from:

NOTE: Flashing the ROM of an NSLU2 removes the LinkSys supported code. Data on any hard disk or flash disk is retained, unchanged, but programs on the disk will almost certainly not be usable after the change.

NOTE: Synology DS101: By 13 Jun 2006, Flash ROM isn't supported, so writing a permanent kernel and root fs is currently not possible. However, user may try to boot the DS101 with a new kernel by uploading it to the RedBoot over serial cable or from a tftp-server on every boot.

NOTE: Because the binary only contains a minimal set of programs necessary to boot SlugOS, one of the following devices is needed in order to install packages onto the device and make SlugOS useful:

to:

Because the binary flash image only contains a minimal set of programs necessary to boot SlugOS, one of the following devices is needed in order to install packages onto the device and make SlugOS `useful:

Changed lines 20-21 from:
  • NFS Export
to:
  • NFS Export from another Linux machine

NOTE: Flashing the ROM of an NSLU2 removes the original Linksys supported code. Data on any hard disk or flash disk is retained, unchanged, but programs on the disk from other distributions (such as UnSlung) will almost certainly not be usable after the change.

NOTE: Synology DS101: By 13 Jun 2006, Flash ROM isn't supported, so writing a permanent kernel and root fs is currently not possible. However, user may try to boot the DS101 with a new kernel by uploading it to the RedBoot over serial cable or from a tftp-server on every boot.

Changed lines 32-37 from:

SlugOS is built using the OpenEmbedded build system. This system currently includes over 1000 separate packages of which approximately 100 are known to build for SlugOS and are included in the SlugOS feeds. Many packages have not been tested!

The SlugOS operating system

SlugOS 3.10 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

to:

SlugOS is built using the OpenEmbedded build system. This system currently includes over 1000 separate packages of which approximately 100 are known to build for SlugOS and are included in the SlugOS feeds. Please note that many packages have not been fully tested, so if you encounter any problems, please report them to the custom firmware mailing list.

The SlugOS operating system

SlugOS 3.10 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

Changed lines 39-41 from:
  • Windows or Linux OS
    • OS-specific Flashing Software
    • Access to SSH -- SSH is the only way to make the initial connection to SlugOS.
to:
  • Windows, Linux or MacOS computer
    • OS-specific Flashing Software (details below)
    • An SSH client -- SSH is the only way to make the initial connection to SlugOS
Changed lines 45-48 from:

NOTE: If you do not have either a Windows or Linux machine it is still possible to flash the device, more details can be found on the page describing how to RecoverFromABadFlash.

to:
  • SlugOS Binary image
Changed lines 48-49 from:
  1. Install Sercomm's Win32 tool
to:
Changed lines 51-52 from:
  • Make sure your Windows Firewall is off
to:
  • If you are running Windows XP or Vista, make sure your Windows Firewall is off
  1. Install an SSH client, such as PuTTY.
Changed lines 55-60 from:
  1. Build UpSlug2 from source.
    • NOTE: Gentoo has a package for upslug2 in portage.
    • NOTE: Debian etch and sid have a package for upslug2.

NSLU2

to:
  1. Install UpSlug2 using a package for your distro, or build it from the sources. The UpSlug2 page has more information about available binary packages and setup instructions.
  2. Make sure your distribution has an SSH client, such as OpenSSH or Dropbear. Any Linux distro should have one of these.

Mac OS X

  1. Install UpSlug2 from source, as described in the UpSlug2 on Mac OS X page.
  2. Mac OS X already includes an ssh client from OpenSSH.

Preparing the NSLU2

Changed lines 72-73 from:

If you have not used the NSLU2 you may find it convenient to use the LinkSys setup software to initialise the above information and to verify that the machine is working correctly. LinkSys technical support will be unable to help you once you have flashed SlugOS.

to:

If you have not used the NSLU2 you may find it convenient to use the Linksys setup software to initialize the above information and to verify that the machine is working correctly. Linksys technical support will be unable to help you once you have flashed SlugOS.

Changed line 83 from:
  1. Download the SlugOS image from http://www.slug-firmware.net
to:
  1. Download the SlugOS image from http://www.slug-firmware.net
Changed lines 99-101 from:

NOTE: You can monitor the progress of the flash by watching your UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

to:

NOTE: You can monitor the progress of the flash by watching your UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

August 23, 2007, at 06:16 PM by fcarolo -- fixed false wikilinks
Changed line 10 from:
to:
  • GiantShoulder Loft
Changed lines 109-110 from:

After the initialization you can use ipkg to download and install software (Unslung and other OpenEmbedded OSes?)

to:

After the initialization you can use ipkg to download and install software.

August 22, 2007, at 08:50 PM by anonymous -- usplug->upslug2
Changed lines 83-84 from:
  1. Flash the NSLU2 by using UpSlug or the Win32 Sercomm Utility
to:
  1. Flash the NSLU2 by using UpSlug2 or the Win32 Sercomm Utility
Changed lines 89-93 from:

NOTE: Once the NSLU2 is in upgrade mode it will remain in this state until either the power is disconnected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode - the flash can be retried from UpSlug or the Sercomm utilty.

NOTE: You can monitor the progress of the flash by watching your UpSlug/UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

to:

NOTE: Once the NSLU2 is in upgrade mode it will remain in this state until either the power is disconnected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode - the flash can be retried from UpSlug2 or the Sercomm utilty.

NOTE: You can monitor the progress of the flash by watching your UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

March 25, 2007, at 08:18 AM by marXman -- Forgot colon, sorry.
Changed lines 85-86 from:

NOTE Slugs produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

to:

NOTE: Slugs produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

March 25, 2007, at 08:17 AM by marXman -- Minor edit to enhance readability
Changed lines 85-86 from:

NOTE NSLU2 units produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

to:

NOTE Slugs produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

March 25, 2007, at 08:15 AM by marXman -- Note about LED colors on newer models, this one really confused me
Added lines 85-86:

NOTE NSLU2 units produced October 2006 or later will not display a red status LED color, but instead a darker orange nuance, which may not be clearly distinguishable depending on the light conditions. The procedure to enter the upgrade mode is just the same as described above, but you have to eye the status LED more carefully to get the right moment for releasing the reset button.

February 02, 2007, at 04:43 PM by Mannkind -- Fixed formatting
Changed lines 89-91 from:

'NOTE:'' You can monitor the progress of the flash by watching your UpSlug/UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

to:

NOTE: You can monitor the progress of the flash by watching your UpSlug/UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

February 02, 2007, at 04:42 PM by Mannkind -- Removed duplicated info
February 02, 2007, at 04:42 PM by Mannkind -- Removed duplicated info
February 02, 2007, at 04:42 PM by Mannkind -- Removed duplicated info
Deleted line 74:

Download the image from http://www.slug-firmware.net/ then flash it by putting the NSLU2 into upgrade mode then using the uploading program.

February 01, 2007, at 03:36 AM by Mannkind --
Changed lines 84-85 from:
  1. Flash the NSLU2 by using UpSlug or the Win32 Sercomm Utility
to:
  1. Flash the NSLU2 by using UpSlug or the Win32 Sercomm Utility
February 01, 2007, at 03:34 AM by Mannkind --
Changed line 53 from:
  • NOTE: Gentoo has a package for upslug2 in portage.\\
to:
  • NOTE: Gentoo has a package for upslug2 in portage.
February 01, 2007, at 03:33 AM by Mannkind --
Changed line 52 from:
  1. Build UpSlug2 from source.\\
to:
  1. Build UpSlug2 from source.
February 01, 2007, at 03:33 AM by Mannkind --
Changed lines 53-55 from:

NOTE: Gentoo has a package for upslug2 in portage.
NOTE: Debian etch and sid have a package for upslug2.

to:
  • NOTE: Gentoo has a package for upslug2 in portage.
    ** NOTE: Debian etch and sid have a package for upslug2.
Deleted line 77:
  1. D
February 01, 2007, at 03:31 AM by Mannkind --
Changed lines 4-5 from:

Aliases:: DebianSlug, OpenSlug

to:

Aliases: DebianSlug, OpenSlug

February 01, 2007, at 03:31 AM by Mannkind --
Changed lines 2-11 from:

The current version of the SlugOS binary images is 3.10 (referred to as DebianSlug-3.10-beta or OpenSlug-3.10-beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

The binary is intended to be loaded ('flashed') into the flash ROM of a LinkSys NSLU2 (or, for experienced users, an Iomega NAS100d, GiantShoulder? Loft, D-Link DSMG600, or Synology DS101). It will not work on anything else. Flashing the ROM of an NSLU2 removes the LinkSys supported code. Data on any hard disk or flash disk is retained, unchanged, but programs on the disk will almost certainly not be usable after the change.

NOTE for DS101: By 13 Jun 2006, Flash ROM isn't supported, so writing a permanent kernel and root fs is currently not possible. However, user may try to boot the DS101 with a new kernel by uploading it to the RedBoot over serial cable or from a tftp-server on every boot.

It is necessary to have an external hard disk, flash disk, or NFS export available for use by SlugOS to install programs on to make SlugOS useful. The binary contains a minimal set of programs necessary to boot the system, even basic file server functionality requires the installation of separate packages. The nslu2-linux feeds for SlugOS contain a number of pre-built packages which may be installed after preparing the external disk for use.

NOTE: The procedure described here will work when "upgrading" from Unslung (my slug had ver 5.5) to SlugOS

to:

Current Version: 3.10
Aliases:: DebianSlug, OpenSlug

Introduction

The binary is intended to be loaded ('flashed') into the flash ROM of a LinkSys NSLU2. More experienced users might flash one of the following devices:

SlugOS will not work on anything else.

NOTE: Flashing the ROM of an NSLU2 removes the LinkSys supported code. Data on any hard disk or flash disk is retained, unchanged, but programs on the disk will almost certainly not be usable after the change.

NOTE: Synology DS101: By 13 Jun 2006, Flash ROM isn't supported, so writing a permanent kernel and root fs is currently not possible. However, user may try to boot the DS101 with a new kernel by uploading it to the RedBoot over serial cable or from a tftp-server on every boot.

NOTE: Because the binary only contains a minimal set of programs necessary to boot SlugOS, one of the following devices is needed in order to install packages onto the device and make SlugOS useful:

  • External Hard Disk
  • Flash Disk
  • NFS Export

NOTE: If you are upgrading from a previous version of SlugOS please refer to: UpgradingOpenSlugToANewRelease.

Changed lines 36-67 from:

Requirements to flash the image

You need an NSLU2 and either a Windows PC or a Linux or similar operating system. If you choose the latter you need root access on that machine or the ability to run a program with root access (e.g. using sudo).

The Windows or Linux(etc) machine is used to run the program to download the image to the NSLU2. The Linux(etc) program is a simple C program which is potentially portable to other operating systems, however this has not yet been done.

If you do not have either a Windows or Linux machine it is still possible to flash a new image if you can set up a TFTP server and are able to telnet into the RedBoot boot loader of the NSLU2. The latter can be difficult to do and this approach is not described further on this page. More details can be found in the page describing how to RecoverFromABadFlash.

Requirements to run SlugOS

To make effective use of the SlugOS binary image you need an ethernet network into which you can plug the NSLU2 and a separate computer which can run ssh. Linux(etc) clients include dropbear and openssh, Windows clients include PuTTY. ssh is the only way to make the initial connection to SlugOS.

Preparation

To flash the image you need:

  1. The program to upload the image to the NSLU2.
  2. An NSLU2.
  3. Optional setup of the NSLU2 networking.
  4. The flash image itself.

Windows PC

Install Sercomm's Win32 tool. This tool is able to locate the slug on the network even if its default IP address (192.168.1.77) is not on the correct subnet and the Linksys utility cannot locate it.
To avoid any problems make sure that you have your Windows Firewall off.

Linux(etc) machine

Build UpSlug2 from source.
NOTE: Gentoo has a package for upslug2 in portage.
NOTE: Debian etch and sid have a package for upslug2.

to:

Prerequisites

  • Windows or Linux OS
    • OS-specific Flashing Software
    • Access to SSH -- SSH is the only way to make the initial connection to SlugOS.
  • Ethernet Network
  • An NSLU2 (or compatible device)
  • SlugOS Binary

NOTE: If you do not have either a Windows or Linux machine it is still possible to flash the device, more details can be found on the page describing how to RecoverFromABadFlash.

Windows

  1. Install Sercomm's Win32 tool
    • This tool can locate the slug on the network even if it isn't on the same subnet, and even when the Linksys tool cannot locate the slug.
    • Make sure your Windows Firewall is off

Linux

  1. Build UpSlug2 from source.
    NOTE: Gentoo has a package for upslug2 in portage.
    NOTE: Debian etch and sid have a package for upslug2.
Changed lines 73-74 from:

Flashing the image

to:

Flashing the NSLU2

Changed lines 76-109 from:

To put the NSLU2 into upgrade mode:

  1. Disconnect any disks and/or devices from the USB ports.
  2. Power off the NSLU2
  3. Press and hold the reset button (accessible through the small hole on the back just above the power input).
  4. Press and release the power button to power on the NSLU2.
  5. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button.
  6. The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode.

If you decide not to flash the image the NSLU2 can be rebooted by disconnecting the power. If the ready/status LED does not turn green after step (4) it will remain red for several seconds then flash amber. This happens if you do not release the reset button in time - pull the power, reconnect it and repeat from step (2).

Once the NSLU2 is in upgrade mode it will remain in this state until either the power is disconnected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode - the flash can be retried from UpSlug or the Sercomm utilty.

You can monitor the progress of the flash by watching your UpSlug/UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

Using the result

After a successful flash the NSLU2 will reset and boot. SlugOS uses the ready/status LED to indicate boot progress. You should see the following sequence:

  1. Amber: control is within the RedBoot boot loader or the early stage of the Linux kernel boot.
  2. Red: the NSLU2 will beep when the LED turns red. This happens at the middle stage of the kernel boot when the LED driver is loaded.
  3. Flashing amber: initial user space boot.
  4. Alternate amber/green: final user space boot.
  5. Green: the system has booted and log in should be possible.

The LED sequence is described in more detail in OpenSlugLEDsDuringBoot.

The first time you log in (look here for the default root password) to SlugOS some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

If you want to serve the NSLU2's disks to a Windows network, probably one of the first things you want to do after initialising is to install and configure Samba. If you are not very familiar in that area consult GettingStartedWithSamba.

If you want to serve NFS from the slug see InstallNFS.

to:
  1. Download the SlugOS image from http://www.slug-firmware.net
  2. Put the NSLU2 into Upgrade Mode
    1. D
    2. Disconnect any disks and/or devices from the USB ports.
    3. Power off the NSLU2
    4. Press and hold the reset button (accessible through the small hole on the back just above the power input).
    5. Press and release the power button to power on the NSLU2.
    6. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button.
    7. The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green).
    8. Flash the NSLU2 by using UpSlug or the Win32 Sercomm Utility

NOTE: If you decide not to flash the image the NSLU2 can be rebooted by disconnecting the power. If the ready/status LED does not turn green after step (4) it will remain red for several seconds then flash amber. This happens if you do not release the reset button in time - pull the power, reconnect it and repeat from step (2).

NOTE: Once the NSLU2 is in upgrade mode it will remain in this state until either the power is disconnected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode - the flash can be retried from UpSlug or the Sercomm utilty.

'NOTE:'' You can monitor the progress of the flash by watching your UpSlug/UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

After Flashing / Initialization

  1. After a successful flash the NSLU2 will reboot. SlugOS uses the ready/status LED to indicate boot progress. The LED sequence is described in more detail in OpenSlugLEDsDuringBoot.
    • Amber: control is within the RedBoot boot loader or the early stage of the Linux kernel boot.
    • Red: the NSLU2 will beep when the LED turns red. This happens at the middle stage of the kernel boot when the LED driver is loaded.
    • Flashing amber: initial user space boot.
    • Alternate amber/green: final user space boot.
    • Green: the system has booted and log in should be possible.
  2. Once the ready/status LED is green, SSH into the NSLU2 as 'root'
  3. Follow the SlugOS initialization as described in InitialisingOpenSlug
  4. Install Packages and Enjoy!

After Initialization

After the initialization you can use ipkg to download and install software (Unslung and other OpenEmbedded OSes?)

NOTE: If you want to serve the NSLU2's disks to a Windows network, you'll want to install and configure Samba by following the instructions at GettingStartedWithSamba.

NOTE: If you want to serve NFS from the slug follow the instructions at InstallNFS.

January 27, 2007, at 09:29 AM by Shaunp -- Sercomm upgrade utility changed
Changed line 43 from:

Install Sercomm's Win32 tool. This tool is able to locate the slug on the network even if its default IP address (192.168.1.77) is not on the correct subnet and the Linksys utility cannot locate it.\\

to:

Install Sercomm's Win32 tool. This tool is able to locate the slug on the network even if its default IP address (192.168.1.77) is not on the correct subnet and the Linksys utility cannot locate it.\\

July 24, 2006, at 03:45 PM by hwdb -- added link because I had to look around for thedefault root passwd
Changed lines 101-102 from:

The first time you log in (look here for the default root password) to SlugOS some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

to:

The first time you log in (look here for the default root password) to SlugOS some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

July 24, 2006, at 03:42 PM by hwdb --
Changed lines 101-102 from:

The first time you log in to SlugOS some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

to:

The first time you log in (look here for the default root password) to SlugOS some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

June 22, 2006, at 04:11 AM by Peter Hartzler -- Note Debian etch and sid have upslug2.
Changed lines 49-50 from:

NOTE: Gentoo has a package for upslug2 in portage

to:

NOTE: Gentoo has a package for upslug2 in portage.
NOTE: Debian etch and sid have a package for upslug2.

June 14, 2006, at 02:32 PM by Alex Chan --
Added lines 6-7:

NOTE for DS101: By 13 Jun 2006, Flash ROM isn't supported, so writing a permanent kernel and root fs is currently not possible. However, user may try to boot the DS101 with a new kernel by uploading it to the RedBoot over serial cable or from a tftp-server on every boot.

June 11, 2006, at 04:37 AM by rwhitby --
Changed lines 2-3 from:

The current version of the SlugOS binary images is 3.10 (referred to as DebianSlug-3.10-beta or OpenSlug-3.10-Beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

to:

The current version of the SlugOS binary images is 3.10 (referred to as DebianSlug-3.10-beta or OpenSlug-3.10-beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

Changed lines 6-9 from:

It is necessary to have an external hard disk, flash disk, or NFS export available for use by OpenSlug to install programs on to make OpenSlug useful. The binary contains a minimal set of programs necessary to boot the system, even basic file server functionality requires the installation of separate packages. The nslu2-linux feed for OpenSlug contains a number of pre-built packages which may be installed after preparing the external disk for use.

NOTE: The procedure described here will work when "upgrading" from Unslung (my slug had ver 5.5) to Openslug

to:

It is necessary to have an external hard disk, flash disk, or NFS export available for use by SlugOS to install programs on to make SlugOS useful. The binary contains a minimal set of programs necessary to boot the system, even basic file server functionality requires the installation of separate packages. The nslu2-linux feeds for SlugOS contain a number of pre-built packages which may be installed after preparing the external disk for use.

NOTE: The procedure described here will work when "upgrading" from Unslung (my slug had ver 5.5) to SlugOS

Changed lines 12-17 from:

OpenSlug is built using the OpenEmbedded build system. This system currently includes over 1000 separate packages of which approximately 100 are known to build for OpenSlug and are included in the OpenSlug feed. Many packages have not been tested!

The OpenSlug operating system

OpenSlug 3.10 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

to:

SlugOS is built using the OpenEmbedded build system. This system currently includes over 1000 separate packages of which approximately 100 are known to build for SlugOS and are included in the SlugOS feeds. Many packages have not been tested!

The SlugOS operating system

SlugOS 3.10 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

Changed lines 26-29 from:

Requirements to run OpenSlug

To make effective use of the OpenSlug binary image you need an ethernet network into which you can plug the NSLU2 and a separate computer which can run ssh. Linux(etc) clients include dropbear and openssh, Windows clients include PuTTY. ssh is the only way to make the initial connection to OpenSlug.

to:

Requirements to run SlugOS

To make effective use of the SlugOS binary image you need an ethernet network into which you can plug the NSLU2 and a separate computer which can run ssh. Linux(etc) clients include dropbear and openssh, Windows clients include PuTTY. ssh is the only way to make the initial connection to SlugOS.

Changed line 46 from:

Build UpSlug from source. Alternative: build UpSlug2 from source.\\

to:

Build UpSlug2 from source.\\

Changed lines 51-52 from:

If your NSLU2 is already in use on a network the basic network settings will be retained (someone confirm this is still true with version 2.7? Yes it is true at least departing from Linksys R63 to Openslug 2.7Beta). The basic network settings are:

to:

If your NSLU2 is already in use on a network the basic network settings will be retained. The basic network settings are:

Changed lines 57-58 from:

If you have not used the NSLU2 you may find it convenient to use the LinkSys setup software to initialise the above information and to verify that the machine is working correctly. LinkSys technical support will be unable to help you once you have flashed OpenSlug.

to:

If you have not used the NSLU2 you may find it convenient to use the LinkSys setup software to initialise the above information and to verify that the machine is working correctly. LinkSys technical support will be unable to help you once you have flashed SlugOS.

Changed lines 88-89 from:

After a successful flash the NSLU2 will reset and boot. OpenSlug uses the ready/status LED to indicate boot progress. You should see the following sequence:

to:

After a successful flash the NSLU2 will reset and boot. SlugOS uses the ready/status LED to indicate boot progress. You should see the following sequence:

Changed lines 98-99 from:

The first time you log in to OpenSlug some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

to:

The first time you log in to SlugOS some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

June 10, 2006, at 06:37 AM by eFfeM -- 3.8 -> 3.10
Changed lines 2-3 from:

The current version of the SlugOS binary images is 3.8 (referred to as DebianSlug-3.8-beta or OpenSlug-3.8-Beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

to:

The current version of the SlugOS binary images is 3.10 (referred to as DebianSlug-3.10-beta or OpenSlug-3.10-Beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

Changed lines 16-17 from:

OpenSlug 3.8 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

to:

OpenSlug 3.10 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

June 06, 2006, at 09:59 AM by repvik --
Changed lines 1-3 from:

The SlugOS (DebianSlug, OpenSlug) Binary

The current version of the OpenSlug binary image is 3.8 (referred to as DebianSlug-3.8-beta or OpenSlug-3.8-Beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

to:

The SlugOS (DebianSlug, OpenSlug) Binary

The current version of the SlugOS binary images is 3.8 (referred to as DebianSlug-3.8-beta or OpenSlug-3.8-Beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

June 06, 2006, at 05:01 AM by rwhitby --
Added lines 1-102:

The SlugOS (DebianSlug, OpenSlug) Binary

The current version of the OpenSlug binary image is 3.8 (referred to as DebianSlug-3.8-beta or OpenSlug-3.8-Beta). If you are upgrading from a previous version of OpenSlug please follow the instructions in UpgradingOpenSlugToANewRelease.

The binary is intended to be loaded ('flashed') into the flash ROM of a LinkSys NSLU2 (or, for experienced users, an Iomega NAS100d, GiantShoulder? Loft, D-Link DSMG600, or Synology DS101). It will not work on anything else. Flashing the ROM of an NSLU2 removes the LinkSys supported code. Data on any hard disk or flash disk is retained, unchanged, but programs on the disk will almost certainly not be usable after the change.

It is necessary to have an external hard disk, flash disk, or NFS export available for use by OpenSlug to install programs on to make OpenSlug useful. The binary contains a minimal set of programs necessary to boot the system, even basic file server functionality requires the installation of separate packages. The nslu2-linux feed for OpenSlug contains a number of pre-built packages which may be installed after preparing the external disk for use.

NOTE: The procedure described here will work when "upgrading" from Unslung (my slug had ver 5.5) to Openslug

Available packages

OpenSlug is built using the OpenEmbedded build system. This system currently includes over 1000 separate packages of which approximately 100 are known to build for OpenSlug and are included in the OpenSlug feed. Many packages have not been tested!

The OpenSlug operating system

OpenSlug 3.8 is based on Linux 2.6.16. It is a 'regular' Linux operating system and should be familiar territory for anyone who has used any similar operating system. It is a full Linux operating system. You should either be confident that you can set up such an operating system or be prepared to spend some time learning. This wiki does not contain enough to teach you how to set up the operating system.

Requirements to flash the image

You need an NSLU2 and either a Windows PC or a Linux or similar operating system. If you choose the latter you need root access on that machine or the ability to run a program with root access (e.g. using sudo).

The Windows or Linux(etc) machine is used to run the program to download the image to the NSLU2. The Linux(etc) program is a simple C program which is potentially portable to other operating systems, however this has not yet been done.

If you do not have either a Windows or Linux machine it is still possible to flash a new image if you can set up a TFTP server and are able to telnet into the RedBoot boot loader of the NSLU2. The latter can be difficult to do and this approach is not described further on this page. More details can be found in the page describing how to RecoverFromABadFlash.

Requirements to run OpenSlug

To make effective use of the OpenSlug binary image you need an ethernet network into which you can plug the NSLU2 and a separate computer which can run ssh. Linux(etc) clients include dropbear and openssh, Windows clients include PuTTY. ssh is the only way to make the initial connection to OpenSlug.

Preparation

To flash the image you need:

  1. The program to upload the image to the NSLU2.
  2. An NSLU2.
  3. Optional setup of the NSLU2 networking.
  4. The flash image itself.

Windows PC

Install Sercomm's Win32 tool. This tool is able to locate the slug on the network even if its default IP address (192.168.1.77) is not on the correct subnet and the Linksys utility cannot locate it.
To avoid any problems make sure that you have your Windows Firewall off.

Linux(etc) machine

Build UpSlug from source. Alternative: build UpSlug2 from source.
NOTE: Gentoo has a package for upslug2 in portage

NSLU2

If your NSLU2 is already in use on a network the basic network settings will be retained (someone confirm this is still true with version 2.7? Yes it is true at least departing from Linksys R63 to Openslug 2.7Beta). The basic network settings are:

  1. The ethernet boot protocol - either a static IP address or DHCP.
  2. The hostname and (if specified) domain name.
  3. For a static IP address the address and the related servers. With DHCP this information is provided by the DHCP server.

If you have not used the NSLU2 you may find it convenient to use the LinkSys setup software to initialise the above information and to verify that the machine is working correctly. LinkSys technical support will be unable to help you once you have flashed OpenSlug.

If you flash a machine which has not been used before the network setup will be as follows:

  1. The network will be configured via DHCP if a DHCP server is present
  2. otherwise it will have a static IP address which will be 192.168.1.77

If you have a DHCP server running, for instance a router, you can determine the assigned IP address from its DHCP clients table.

Flashing the image

Download the image from http://www.slug-firmware.net/ then flash it by putting the NSLU2 into upgrade mode then using the uploading program.

To put the NSLU2 into upgrade mode:

  1. Disconnect any disks and/or devices from the USB ports.
  2. Power off the NSLU2
  3. Press and hold the reset button (accessible through the small hole on the back just above the power input).
  4. Press and release the power button to power on the NSLU2.
  5. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button.
  6. The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode.

If you decide not to flash the image the NSLU2 can be rebooted by disconnecting the power. If the ready/status LED does not turn green after step (4) it will remain red for several seconds then flash amber. This happens if you do not release the reset button in time - pull the power, reconnect it and repeat from step (2).

Once the NSLU2 is in upgrade mode it will remain in this state until either the power is disconnected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode - the flash can be retried from UpSlug or the Sercomm utilty.

You can monitor the progress of the flash by watching your UpSlug/UpSlug2 session. You can also keep an eye on the Ethernet led on the NSLU2 - any activity you see is the transmission of the binary.

Using the result

After a successful flash the NSLU2 will reset and boot. OpenSlug uses the ready/status LED to indicate boot progress. You should see the following sequence:

  1. Amber: control is within the RedBoot boot loader or the early stage of the Linux kernel boot.
  2. Red: the NSLU2 will beep when the LED turns red. This happens at the middle stage of the kernel boot when the LED driver is loaded.
  3. Flashing amber: initial user space boot.
  4. Alternate amber/green: final user space boot.
  5. Green: the system has booted and log in should be possible.

The LED sequence is described in more detail in OpenSlugLEDsDuringBoot.

The first time you log in to OpenSlug some amount of initialisation will be required. This is described in InitialisingOpenSlug. After the initialisation package download and use is the same as on Unslung (which uses the same package utility - ipkg) and on OpenEmbedded operating systems.

If you want to serve the NSLU2's disks to a Windows network, probably one of the first things you want to do after initialising is to install and configure Samba. If you are not very familiar in that area consult GettingStartedWithSamba.

If you want to serve NFS from the slug see InstallNFS.

view · edit · print · history · Last edited by kyle.
Based on work by thx1011, Tobias Balle-Peresen, fcarolo, anonymous, marXman, Mannkind, Shaunp, hwdb, Peter Hartzler, Alex Chan, rwhitby, eFfeM, and repvik.
Originally by rwhitby.
Page last modified on February 07, 2010, at 08:16 PM