NSLU2-Linux
view · edit · print · history

Puppy.EndUserPuppyInstall History

Hide minor edits - Show changes to markup

December 05, 2005, at 11:48 PM by John -- .
Changed line 50 from:
  1. Run /sbin/unsling in the telnet session which you have kept open.
to:
  1. Run /sbin/unsling disk1 in the telnet session which you have kept open.
August 27, 2005, at 07:28 PM by odvdveer --
Changed lines 10-12 from:
  1. Some from of a net connection.
  2. "unslung-able 2.x" firmware package or the "unslung 3.17-beta".
to:
  1. Some form of a net connection.
  2. "unslung 5.5beta" firmware package".
Changed lines 15-19 from:
  • Get unslung-able 2.x firmware from peteru. Email him and politely request it from him. The email address for Peter is "toppy at urbanec dot net".
Or get the unslung 3.17-beta firmware from sourceforge. This one worked for me with a 256MB flash key
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to TelnetIntoRedBoot, this is crucial should a mistake be made and you make the NSLU2 temporarily unbootable as I did. Once you can get to a RedBoot prompt you can type upgrade and then using the SerComm Upgrade Utility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
to:
  • Get the unslung 5.5-beta firmware from sourceforge.
  • Ensure you have read the readme that comes with the unslung firmware and ensure you have tested your ability to TelnetIntoRedBoot, this is crucial should a mistake be made and you make the NSLU2 temporarily unbootable as I did. Once you can get to a RedBoot prompt you can type upgrade and then using the SerComm Upgrade Utility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
Changed line 41 from:
  1. Upload the new unslungable 2.x firmware via the web interface install page. The update process can take a few minutes so be patient!
to:
  1. Upload the new unslung 5.5beta firmware via the web interface install page. The update process can take a few minutes so be patient!
Changed lines 85-86 from:

This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download the packages and install sucessfully.

to:

This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download the packages and install sucessfully. You might like to check if you have the gateway set on the NSLU2, this is often the cause of not being able to get the NSLU2 connected to the internet.

June 01, 2005, at 11:18 PM by tman -- Removing the term "brick" since it ISN'T accurate & typo fixes
Changed line 6 from:
  1. You have a USB disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1GB). You can also use a 256MB or larger flash key (you must plug it into the Disk1 port if you are using a flash key as the unslung disk).
to:
  1. You have a USB disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1GB). You can also use a 256MB or larger flash key (you must plug it into the Disk1 USB port on the back of the NSLU2 if you are using a flash key as the unslung disk).
Changed lines 94-95 from:

Once you have installed the above packages, you should reboot your slug with the USB disk attached and powered on. Since we have installed the openssh package, you no longer need to enable telnet. Instead, you can use your ssh client to connect to the slug and login as root with the default password uNSLUng (you can always follow generic unslung instructions for changing passwords, if you wish)

to:

Once you have installed the above packages, you should reboot your slug with the USB disk attached and powered on. Since we have installed the openssh package, you no longer need to enable telnet. Instead, you can use your SSH client to connect to the slug and login as root with the default password uNSLUng (you can always follow generic unslung instructions for changing passwords, if you wish)

June 01, 2005, at 11:17 PM by tman -- Removing the term"brick" since it ISN'T accurate & typos fixes
Changed lines 5-6 from:
  1. That you havn't done anything else to the NSLU2 apart from maybe turn it on and used it as linksys expected ;)
  2. You have a usb disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1 Gb). You can also use a 256MB or larger flash key (you must plug it into the Disk1 port if you are using a flash key as the unslung disk).
to:
  1. That you havn't done anything else to the NSLU2 apart from maybe turn it on and used it as Linksys expected ;)
  2. You have a USB disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1GB). You can also use a 256MB or larger flash key (you must plug it into the Disk1 port if you are using a flash key as the unslung disk).
Changed lines 16-21 from:
Or get the unslung 3.17-beta firmware from sourceforge. This one worked for me with a 256mb flash key
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the SerComm Upgrade Utility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
  • Get the nslu2 on the local network. It is generally better to attach it to a home network that has a net connection as it will be much easier to download and install the packages later.
to:
Or get the unslung 3.17-beta firmware from sourceforge. This one worked for me with a 256MB flash key
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to TelnetIntoRedBoot, this is crucial should a mistake be made and you make the NSLU2 temporarily unbootable as I did. Once you can get to a RedBoot prompt you can type upgrade and then using the SerComm Upgrade Utility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
  • Get the NSLU2 on the local network. It is generally better to attach it to a home network that has a net connection as it will be much easier to download and install the packages later.
Changed lines 25-29 from:
  • Use the Linksys cd setup to set ip address of the nslu2.
  • Set the nslu IP address to IP 192.168.1.77, subnet 255.255.255.0, gateway 192.168.1.100
  • Set my pc ip address to IP: 192.168.1.100, subnet : 255.255.255.0, gateway : 192.168.1.77
  • Connect to the web interface of the slug. Default url address is http://192.168.1.77/
to:
  • Use the Linksys CD setup utility to set the IP address of the NSLU2.
  • Set the NSLU2 IP address to IP 192.168.1.77, subnet 255.255.255.0, gateway 192.168.1.100
  • Set my PC IP address to IP: 192.168.1.100, subnet : 255.255.255.0, gateway : 192.168.1.77
  • Connect to the web interface of the slug. The default address assuming you set it to 192.168.1.77 is http://192.168.1.77/
Changed line 31 from:
  • Connect a usb 2.0 disk to the slug.
to:
  • Connect a USB 2.0 disk to the slug.
Changed line 43 from:

(if you get a message that you don't have enough memory and you are running windows you can use the SerComm Upgrade Utility

to:

(if you get a message that you don't have enough memory and you are running Windows you can use the SerComm Upgrade Utility

Changed lines 57-59 from:

Your now running an unslung on your nslu2. Now onto getting some extra software (and most importantly puppy) installed.

to:

You're now running an unslung on your nslu2. Now onto getting some extra software (and most importantly puppy) installed.

Changed lines 77-78 from:
This package will start the SSH (secure shell) daemon when the nslu2 starts each time. You can get a free ssh client here
to:
This package will start the SSH (secure shell) daemon when the NSLU2 starts each time. You can get a free SSH client here
Changed lines 81-82 from:

The package below is optional.

to:

The package below is optional:

Changed line 85 from:

If you've tried the above and get an error its normally because your nslu2 can't grab the packages direct from the net.

to:

If you've tried the above and get an error its normally because your NSLU2 can't grab the packages direct from the net.

Changed lines 96-98 from:

Now you can run your puppy commands ... AFTER you've connected your Topfield to the nslu2.

to:

Now you can run your puppy commands... AFTER you've connected your Topfield to the NSLU2.

Changed line 112 from:

You will need to have a big disk connected to the NSLU2 if you want to transfer files.

to:

You will need to have a big disk connected to the NSLU2 if you want to transfer files.

January 12, 2005, at 02:54 AM by Koops --
Changed lines 85-88 from:

The second method is a manual install involving manual downloads to another machine and copying over the files.

to:

If you've tried the above and get an error its normally because your nslu2 can't grab the packages direct from the net. This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download the packages and install sucessfully.

The manual install involving downloading to another machine and copying over the files.

January 12, 2005, at 02:50 AM by Koops --
Added lines 85-86:

The second method is a manual install involving manual downloads to another machine and copying over the files. These instructions are found on the ManualPuppyInstall page.

Changed lines 88-143 from:

NSLU2 that is indirectly connected to the net.

If you've tried the above and get an error its normally because your nslu2 can't grab the packages direct from the net. This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download the packages and install sucessfully.

Manually get packages

On a machine that has net access. ie. your normal net connected home machine.

goto the http://ipkg.nslu2-linux.org/ipkg/ Ipkg Package site and get the following.

 openssl_0.9.7d-1_armeb.ipk 
 zlib_1.2.1-1_armeb.ipk 
 openssh_3.8p1-1_armeb.ipk
 puppy_1.2-1_armeb.ipk
 bash_2.05b-1_armeb.ipk

FTP Transfer to nlsu2.

Now from the nslu2 ftp to my local pc that i've downloaded the packages to. ie. ftp 192.168.1.100 (pc). You'll need to have some type of ftp package installed to serve the files. I was running the free alex small ftp package from my windows machine.

  • add properly formatted example of ftp transfer*

Or you can transfer the files directly from a windows pc.

First:

  In the webinterface, on the administration -system page, check the server name and workgroup of your slug. Change the workgroup to the same workgroup as your PC, and the server name to ie Slug.

Then:

  Open a windows explorer window
  Go to network environment - complete network - microsoft windows network - work group - server name (ie Slug) - DISK1?
  Copy the ipk files to DISK1?

Finally:

  Telnet to the slug
  type: cd /share/hdd/data/public
  type: ls, and you should see the transfered files

You can now continue with the manual install of the packages

Manual install of packages.

Now cut and paste each of in the following commands to install each of the packages.

 ipkg install openssl_0.9.7d-1_armeb.ipk
 ipkg install zlib_1.2.1-1_armeb.ipk
 ipkg install openssh_3.8p1-1_armeb.ipk     <- This command will take a while as it generates the keys.
 ipkg install puppy_1.2-1_armeb.ipk
 ipkg install bash_2.05b-1_armeb.ipk

If you'd like to run some perl scripts you can optionally install perl.

 ipkg install perl_5.6.1-1_armeb.ipk

Now you are finished!

to:

That's it now you are finished!

January 07, 2005, at 12:39 PM by odvdveer --
Added lines 111-127:

Or you can transfer the files directly from a windows pc.

First:

  In the webinterface, on the administration -system page, check the server name and workgroup of your slug. Change the workgroup to the same workgroup as your PC, and the server name to ie Slug.

Then:

  Open a windows explorer window
  Go to network environment - complete network - microsoft windows network - work group - server name (ie Slug) - DISK1?
  Copy the ipk files to DISK1?

Finally:

  Telnet to the slug
  type: cd /share/hdd/data/public
  type: ls, and you should see the transfered files

You can now continue with the manual install of the packages

January 07, 2005, at 12:17 PM by odvdveer --
Changed line 11 from:
  1. "unslung-able 2.x" firmware package or the "unslung 3.16-beta".
to:
  1. "unslung-able 2.x" firmware package or the "unslung 3.17-beta".
January 07, 2005, at 12:16 PM by odvdveer --
Changed line 16 from:
Or get the http://sourceforge.net/projects/nslu unslung 3.16-beta firmware from sourceforge. This one worked for me with a 256mb flash key
to:
Or get the http://sourceforge.net/projects/nslu unslung 3.17-beta firmware from sourceforge. This one worked for me with a 256mb flash key
January 06, 2005, at 11:26 AM by camthecameraman --
Changed line 18 from:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utilityyou can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
to:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
January 06, 2005, at 11:25 AM by camthecameraman --
Changed line 18 from:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utilityutility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
to:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utilityyou can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
January 06, 2005, at 11:25 AM by camthecameraman --
Changed line 18 from:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utilityutility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
to:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utilityutility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
January 06, 2005, at 11:24 AM by camthecameraman --
Added lines 18-19:
  • Ensure you have read the readme that comes with the unslung-able firmware and ensure you have tested your ability to http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot, this is crucial should a mistake be made a nd you "brick" your unit as I did. Once you can get to a Redboot prompt you can type upgrade and then using the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utilityutility you can take your firmware back to the linksys original or re flash with an uNSLUng package. Ensure at the very least you are familiar with this process
December 29, 2004, at 03:08 PM by odvdveer --
Changed line 16 from:
Or get the http://sourceforge.net/projects/nslu unslung 3.16-beta firmware from sourceforge. This one worked for me with a 256mb usb-key
to:
Or get the http://sourceforge.net/projects/nslu unslung 3.16-beta firmware from sourceforge. This one worked for me with a 256mb flash key
December 29, 2004, at 02:12 PM by Olga D van de Veer --
Changed line 11 from:
  1. "unslung-able 2.x" firmware package.
to:
  1. "unslung-able 2.x" firmware package or the "unslung 3.16-beta".
Changed lines 15-16 from:
  • Get unslung-able 2.x firmware from peteru. Email him and politely request it from him. The email address for Peter is "toppy at urbanec dot net".
to:
  • Get unslung-able 2.x firmware from peteru. Email him and politely request it from him. The email address for Peter is "toppy at urbanec dot net".
Or get the http://sourceforge.net/projects/nslu unslung 3.16-beta firmware from sourceforge. This one worked for me with a 256mb usb-key
Added line 41:

(if you get a message that you don't have enough memory and you are running windows you can use the http://www.sercomm.com/web/download.nsf/cd9678c311095856482566a5000aac9e/7f17bf7344cfc12f482566aa00389845/$FILE/Upgrade_207_XP.exe SerComm Upgrade Utility

December 27, 2004, at 01:40 PM by peteru --
Added lines 130-131:

See PuppyUsage for some examples of how to use puppy.

December 24, 2004, at 11:23 AM by rwhitby --
Changed lines 23-24 from:
  • Set the nslu IP address to IP 192.168.0.77, subnet 255.255.255.0, gateway 192.168.0.100
  • Set my pc ip address to IP: 192.168.0.100, subnet : 255.255.255.0, gateway : 192.168.0.77
to:
  • Set the nslu IP address to IP 192.168.1.77, subnet 255.255.255.0, gateway 192.168.1.100
  • Set my pc ip address to IP: 192.168.1.100, subnet : 255.255.255.0, gateway : 192.168.1.77
Changed line 26 from:
  • Connect to the web interface of the slug. Default url address is http://192.168.0.77/
to:
  • Connect to the web interface of the slug. Default url address is http://192.168.1.77/
Changed lines 41-42 from:
  1. Enable telnet access via the telnet.cgi script. http://192.168.0.77/Management/telnet.cgi
  2. Telnet to the slug. From a Windows machine you can type "telnet 192.168.0.77"
to:
  1. Enable telnet access via the telnet.cgi script. http://192.168.1.77/Management/telnet.cgi
  2. Telnet to the slug. From a Windows machine you can type "telnet 192.168.1.77"
Changed lines 50-51 from:
  1. After a reboot, you will need to re-enable telnet access again using http://192.168.0.77/Management/telnet.cgi
  2. Telnet back into the slug. From a Windows machine you can type "telnet 192.168.0.77"
to:
  1. After a reboot, you will need to re-enable telnet access again using http://192.168.1.77/Management/telnet.cgi
  2. Telnet back into the slug. From a Windows machine you can type "telnet 192.168.1.77"
Changed line 102 from:

ie. ftp 192.168.0.100 (pc). You'll need to have some type of ftp package installed to serve the files.

to:

ie. ftp 192.168.1.100 (pc). You'll need to have some type of ftp package installed to serve the files.

Added lines 138-139:

You will need to have a big disk connected to the NSLU2 if you want to transfer files.

December 24, 2004, at 11:20 AM by rwhitby --
Changed line 47 from:
  1. Run /sbin/unslung in the telnet session which you have kept open.
to:
  1. Run /sbin/unsling in the telnet session which you have kept open.
December 22, 2004, at 02:48 AM by peteru --
Changed line 1 from:

Puppy End User install instructions.

to:

Puppy End User install instructions.

Changed lines 3-7 from:

Assumptions :

	a.That you've just purchased a Linksys NSLU2 and want to run puppy on it to connect to your Toppy.
	b.That you havn't done anything else to the NSLU2 apart from maybe turn it on and used it as linksys expected ;)
	c.You have a usb disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1 Gb).  You can also use a 256MB or larger flash key (you must plug it into the Disk1 port if you are using a flash key as the unslung disk).
	d.That you're not that familiar with linux but have some general computer proficiency.
to:

Assumptions:

  1. That you've just purchased a Linksys NSLU2 and want to run puppy on it to connect to your Toppy.
  2. That you havn't done anything else to the NSLU2 apart from maybe turn it on and used it as linksys expected ;)
  3. You have a usb disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1 Gb). You can also use a 256MB or larger flash key (you must plug it into the Disk1 port if you are using a flash key as the unslung disk).
  4. That you're not that familiar with Linux but have some general computer proficiency.
Changed lines 9-11 from:

Requirements : Some from of a net connection, "unslung-able 2.x" firmware package.

to:

Requirements:

  1. Some from of a net connection.
  2. "unslung-able 2.x" firmware package.
Changed line 13 from:

Pre install.

to:

Pre install.

Changed lines 15-16 from:

1.Get unslung-able 2.x firmware from peteru. Email him and politely request it from him. You can email Peter's via "toppy at urbanec dot net".

to:
  • Get unslung-able 2.x firmware from peteru. Email him and politely request it from him. The email address for Peter is "toppy at urbanec dot net".
Changed line 17 from:

2.Get the nslu2 on the local network. It is generally better to attach it home network that has a net connection as it will be much easier to download and install the packages later.

to:
  • Get the nslu2 on the local network. It is generally better to attach it to a home network that has a net connection as it will be much easier to download and install the packages later.
Changed lines 19-20 from:

However it is still possible to do it without a direct net connection. I was using a crossover cable to do install puppy.

to:
However it is still possible to do it without a direct net connection. I was using a crossover cable to install puppy.
Changed lines 22-43 from:
	1.Use the Linksys cd setup to set ip address of the nslu2.
	2.Set the nslu IP address to IP 192.168.0.77, subnet 255.255.255.0, gateway 192.168.0.100
	3.Set my pc ip address to IP: 192.168.0.100, subnet : 255.255.255.0, gateway : 192.168.0.77

3.Connect to the web interface of the slug. Default url address is http://192.168.1.77/

  • Make sure that your DNS server is set in the web interface.
  • Connect a usb 2.0 disk to the slug.
  • Format the disk under the admin tools/disk page.
  • Test that you can sucessfully use the disk. Copy a file over the network to it.
  • This ensures that we have a known good disk before installing unslung packages on it.

New firmware install.

  1. Remove any disks (including flash keys) connected to the slug.
  2. Upload the new unslungable 2.x firmware via the web interface install page. The update process can take a few minutes so be patient!
  3. Enable telnet access via the telnet.cgi script. http://192.168.1.77/Management/telnet.cgi
  4. Telnet to the machine. From a windows machine you can type "telnet 192.168.0.77"
  5. At the username prompt type "root" and at the password prompt type "uNSLUng".
  6. Plug the disk back into the slug. Wait for a minute or so while the slug recognises it.
  7. Check and see if your disk is formated via the web interface. If not format it :)
  8. Run /sbin/unslung in the telnet session which you have kept open.
to:
  • Use the Linksys cd setup to set ip address of the nslu2.
  • Set the nslu IP address to IP 192.168.0.77, subnet 255.255.255.0, gateway 192.168.0.100
  • Set my pc ip address to IP: 192.168.0.100, subnet : 255.255.255.0, gateway : 192.168.0.77
  • Connect to the web interface of the slug. Default url address is http://192.168.0.77/
    • Make sure that your DNS server is set in the web interface.
    • Connect a usb 2.0 disk to the slug.
    • Format the disk under the admin tools/disk page.
    • Test that you can sucessfully use the disk. Copy a file over the network to it.
    • This ensures that we have a known good disk before installing unslung packages on it.

New firmware install.

  1. Shutdown the slug.
  2. Remove any disks (including flash keys) connected to the slug.
  3. Power on the slug and wait for the beep.
  4. Upload the new unslungable 2.x firmware via the web interface install page. The update process can take a few minutes so be patient!
  5. The slug will reboot at the end of the upgrade.
  6. Enable telnet access via the telnet.cgi script. http://192.168.0.77/Management/telnet.cgi
  7. Telnet to the slug. From a Windows machine you can type "telnet 192.168.0.77"
  8. At the username prompt type "root" and at the password prompt type "uNSLUng".
  9. Plug the disk back into the slug.
  10. Wait for a minute or so while the slug recognises it.
  11. Check and see if your disk is formated via the web interface. If not format it :)
  12. Run /sbin/unslung in the telnet session which you have kept open.
  13. When the process is finished, you should reboot the slug.
  14. This time around you should have your USB disk connected during the boot process.
  15. After a reboot, you will need to re-enable telnet access again using http://192.168.0.77/Management/telnet.cgi
  16. Telnet back into the slug. From a Windows machine you can type "telnet 192.168.0.77"
Changed lines 53-54 from:

Your now running an unslung on your nslu2. Now onto getting some extra software (and most importantly puppy) installed.

to:

Your now running an unslung on your nslu2. Now onto getting some extra software (and most importantly puppy) installed.

Changed line 56 from:

Updating and install extra software packages.

to:

Updating and install extra software packages.

Changed line 60 from:

NSLU2 that is directly connected to the net.

to:

NSLU2 that is directly connected to the net.

Changed line 66 from:

ipkg update

to:
 ipkg update
Changed lines 70-71 from:

ipkg install openssl

to:
 ipkg install openssl
 ipkg install openssh
Changed line 73 from:

ipkg install openssh

to:
This package will start the SSH (secure shell) daemon when the nslu2 starts each time. You can get a free ssh client http://www.chiark.greenend.org.uk/~sgtatham/putty/ here
Changed lines 75-78 from:

This package will start the SSH (secure shell) daemon when the nslu2 starts each time. You can get a free ssh client http://www.chiark.greenend.org.uk/~sgtatham/putty/ here

ipkg install puppy

to:
 ipkg install puppy
Changed line 79 from:

ipkg install bash

to:
 ipkg install bash 
Changed line 82 from:

NSLU2 that is indirectly connected to the net.

to:

NSLU2 that is indirectly connected to the net.

Changed lines 84-85 from:

2. If you've tried the above and get an error its normally because your nslu2 can't grab the packages direct from the net. This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download them and install sucessfully.

to:

If you've tried the above and get an error its normally because your nslu2 can't grab the packages direct from the net. This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download the packages and install sucessfully.

Changed line 87 from:
Manually get packages
to:

Manually get packages

Changed lines 93-99 from:

openssl_0.9.7d-1_armeb.ipk

zlib_1.2.1-1_armeb.ipk

openssh_3.8p1-1_armeb.ipk

puppy_1.2-1_armeb.ipk

to:
 openssl_0.9.7d-1_armeb.ipk 
 zlib_1.2.1-1_armeb.ipk 
 openssh_3.8p1-1_armeb.ipk
 puppy_1.2-1_armeb.ipk
 bash_2.05b-1_armeb.ipk
Changed lines 99-101 from:

bash_2.05b-1_armeb.ipk

FTP Transfer to nlsu2.
to:

FTP Transfer to nlsu2.

Changed line 107 from:
Manual install of packages.
to:

Manual install of packages.

Changed lines 111-115 from:

ipkg install openssl_0.9.7d-1_armeb.ipk ipkg install zlib_1.2.1-1_armeb.ipk ipkg install openssh_3.8p1-1_armeb.ipk <- This command will take a while as it generates the keys. ipkg install puppy_1.2-1_armeb.ipk ipkg install bash_2.05b-1_armeb.ipk

to:
 ipkg install openssl_0.9.7d-1_armeb.ipk
 ipkg install zlib_1.2.1-1_armeb.ipk
 ipkg install openssh_3.8p1-1_armeb.ipk     <- This command will take a while as it generates the keys.
 ipkg install puppy_1.2-1_armeb.ipk
 ipkg install bash_2.05b-1_armeb.ipk

If you'd like to run some perl scripts you can optionally install perl.

 ipkg install perl_5.6.1-1_armeb.ipk
Changed line 120 from:

If you'd like to run some perl scripts you can optionally install perl. (ipkg install perl_5.6.1-1_armeb.ipk)

to:

Now you are finished!

Changed lines 122-123 from:

Now your finished!

to:

Connecting to the slug

Once you have installed the above packages, you should reboot your slug with the USB disk attached and powered on. Since we have installed the openssh package, you no longer need to enable telnet. Instead, you can use your ssh client to connect to the slug and login as root with the default password uNSLUng (you can always follow generic unslung instructions for changing passwords, if you wish)

Changed line 125 from:

Now you can run your puppy commands ... AFTER you've connected your topfield to the nslu2.

to:

Now you can run your puppy commands ... AFTER you've connected your Topfield to the nslu2.

Changed lines 131-133 from:

Type "puppy" and press "Enter" and it will show you all the options that it can take.

In general you'll be interested in using the "-c" flag which sends commands to the Topfield5000PVRT?.

to:

Type puppy and press "Enter" and it will show you all the options that it can take.

Changed line 133 from:

A simple test would be to type "puppy -c dir".

to:

In general you'll be interested in using the "-c" flag which sends commands to the Topfield TF5000PVRt.

Changed line 135 from:

This should list the contents of the topfield disk.

to:

A simple test would be to type puppy -c dir to list the contents of the Topfield disk.

Changed line 137 from:

The other commands are : "size, dir, get, put, rename, delete, reboot, cancel".

to:

The other commands are : "size, dir, get, put, rename, delete, reboot, cancel".

December 22, 2004, at 02:06 AM by rwhitby --
Added lines 61-62:

This will update the list of available packages and the following commands will download and install them from the net.

Deleted line 75:

This will update the list of available packages then downloads and installs them from the net.

December 22, 2004, at 02:04 AM by rwhitby --
Changed lines 6-7 from:
	c.You have a 256MB or larger usb disk that you can format and not have to worry about the contents of.
	d.That your not that familiar with linux but have some general computer proficiency.
to:
	c.You have a usb disk that you can format and not have to worry about the contents of (it doesn't have to be that big, but it must be larger than 1 Gb).  You can also use a 256MB or larger flash key (you must plug it into the Disk1 port if you are using a flash key as the unslung disk).
	d.That you're not that familiar with linux but have some general computer proficiency.
Changed line 28 from:
  • Connect a usb 2.0 disk to the Disk1 port on the slug (it must be connected to the Disk1 port, or it won't work correctly).
to:
  • Connect a usb 2.0 disk to the slug.
Changed line 36 from:
  1. Remove any disks (including USB disks) connected to the slug.
to:
  1. Remove any disks (including flash keys) connected to the slug.
Changed line 41 from:
  1. Plug the disk back into the Disk1 port. Wait for a minute or so while the slug recognises it.
to:
  1. Plug the disk back into the slug. Wait for a minute or so while the slug recognises it.
December 22, 2004, at 02:01 AM by rwhitby --
Changed lines 27-31 from:

Make sure that your DNS server is set in the web interface. Connect a usb 2.0 disk to the Disk1 port on the slug (it must be connected to the Disk1 port, or it won't work correctly). Format the disk under the admin tools/disk page. Test that you can sucessfully use the disk. Copy a file over the network to it. This ensures that we have a known good disk before installing unslung packages on it.

to:
  • Make sure that your DNS server is set in the web interface.
  • Connect a usb 2.0 disk to the Disk1 port on the slug (it must be connected to the Disk1 port, or it won't work correctly).
  • Format the disk under the admin tools/disk page.
  • Test that you can sucessfully use the disk. Copy a file over the network to it.
  • This ensures that we have a known good disk before installing unslung packages on it.
December 22, 2004, at 02:01 AM by rwhitby --
Added line 27:

Make sure that your DNS server is set in the web interface.

December 22, 2004, at 02:00 AM by rwhitby --
Changed lines 6-7 from:
	c.You have a usb disk that you can format and not have to worry about the contents of. 
	(doesn't have to be a huge disk btw!)
to:
	c.You have a 256MB or larger usb disk that you can format and not have to worry about the contents of.
Changed lines 27-28 from:

Connect a usb 2.0 disk to the slug. Format the disk under the admin tools/disk page.

to:

Connect a usb 2.0 disk to the Disk1 port on the slug (it must be connected to the Disk1 port, or it won't work correctly). Format the disk under the admin tools/disk page.

Added line 35:
  1. Remove any disks (including USB disks) connected to the slug.
Deleted line 36:
  1. Check and see if your disk is formated via the web interface. If not format it :)
Changed lines 40-42 from:
  1. run /sbin/unslung
to:
  1. Plug the disk back into the Disk1 port. Wait for a minute or so while the slug recognises it.
  2. Check and see if your disk is formated via the web interface. If not format it :)
  3. Run /sbin/unslung in the telnet session which you have kept open.
December 21, 2004, at 04:55 AM by Koops --
Changed line 23 from:
	1.Use linksys cd setup to set ip address of the nslu2.
to:
	1.Use the Linksys cd setup to set ip address of the nslu2.
Changed line 27 from:

3.Connect to the web interface of the slug. http://192.168.0.77/

to:

3.Connect to the web interface of the slug. Default url address is http://192.168.1.77/

Changed lines 35-40 from:

1.Upload the new unslungable 2.x firmware via the web interface install page. 2.Enable telnet access via the telnet.cgi script. http://192.168.0.77/Management/telnet.cgi 3.Telnet to the machine. From a windows machine you can type "telnet 192.168.0.77" 4.At the username prompt type "root" and at the password prompt type "uNSLUng". 5.Check and see if your disk is formated via the web interface. If not format it :) 6.run /sbin/unslung

to:
  1. Upload the new unslungable 2.x firmware via the web interface install page. The update process can take a few minutes so be patient!
  2. Check and see if your disk is formated via the web interface. If not format it :)
  3. Enable telnet access via the telnet.cgi script. http://192.168.1.77/Management/telnet.cgi
  4. Telnet to the machine. From a windows machine you can type "telnet 192.168.0.77"
  5. At the username prompt type "root" and at the password prompt type "uNSLUng".
  6. run /sbin/unslung
Added line 118:
Added line 125:
Added line 127:
December 21, 2004, at 04:50 AM by Koops --
Changed line 17 from:

2.Get the nslu2 on the local network.

to:

2.Get the nslu2 on the local network. It is generally better to attach it home network that has a net connection as it will be much easier to download and install the packages later.

Changed lines 19-20 from:

I was using a crossover cable so some of the following may not apply.

to:

However it is still possible to do it without a direct net connection. I was using a crossover cable to do install puppy.

Changed lines 22-23 from:
	1.Use linksys cd setup to set ip address of the slug.
to:
Below are the extra tasks I had to do to use a cross over cable instead of a real network connection.
	1.Use linksys cd setup to set ip address of the nslu2.
Changed line 46 from:

Updating packages.

to:

Updating and install extra software packages.

December 21, 2004, at 04:45 AM by Koops --
Changed line 17 from:

2. Get the nslug on the local network.

to:

2.Get the nslu2 on the local network.

Changed lines 22-24 from:
	Set the nslu IP address to IP 192.168.0.77, subnet 255.255.255.0, gateway 192.168.0.100

	2.Set my pc ip address to IP: 192.168.0.100, subnet : 255.255.255.0, gateway : 192.168.0.77
to:
	2.Set the nslu IP address to IP 192.168.0.77, subnet 255.255.255.0, gateway 192.168.0.100
	3.Set my pc ip address to IP: 192.168.0.100, subnet : 255.255.255.0, gateway : 192.168.0.77
December 21, 2004, at 04:44 AM by Koops --
Added line 62:

You can get a free ssh client http://www.chiark.greenend.org.uk/~sgtatham/putty/ here

Changed line 81 from:

goto the http://ipkg.nslu2-linux.org/ipkg/ site and get the following packages.

to:

goto the http://ipkg.nslu2-linux.org/ipkg/ Ipkg Package site and get the following.

December 21, 2004, at 04:24 AM by Koops --
Added lines 61-62:

This package will start the SSH (secure shell) daemon when the nslu2 starts each time.

Changed lines 65-67 from:

ipkg install bash

to:

The package below is optional.

ipkg install bash

Changed lines 125-127 from:

The other commands are : "size, dir, get, put, rename, delete, reboot, cancel".

Own notes: You'll need to enable telnet each time via the gui interface. I'm trying to find out how this is enabled permanently upon startup.

to:

The other commands are : "size, dir, get, put, rename, delete, reboot, cancel".

December 21, 2004, at 04:16 AM by Koops --
Changed line 1 from:

The Puppy End User install instructions for getting unslung and puppy working on your nslu2.

to:

Puppy End User install instructions.

Changed lines 12-14 from:

Pre install.

to:

Pre install.

Changed lines 32-33 from:

New firmware install.

to:

New firmware install.

Changed line 41 from:

Your now running an unslung nslu2!

to:

Your now running an unslung on your nslu2.

Changed line 45 from:

Updating packages.

to:

Updating packages.

Added lines 49-50:

NSLU2 that is directly connected to the net.

Added line 56:
Added line 58:
Added line 60:
Added line 62:
Added lines 67-68:

NSLU2 that is indirectly connected to the net.

Changed line 70 from:

This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download them and install

to:

This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download them and install sucessfully.

Changed line 72 from:

sucessfully.

to:
Manually get packages
Deleted line 76:

openssl_0.9.7d-1_armeb.ipk, zlib_1.2.1-1_armeb.ipk, openssh_3.8p1-1_armeb.ipk ,puppy_1.2-1_armeb.ipk,bash_2.05b-1_armeb.ipk , optionally

Changed lines 78-84 from:

(perl_5.6.1-1_armeb.ipk) from the how-to page.

to:

openssl_0.9.7d-1_armeb.ipk

zlib_1.2.1-1_armeb.ipk

openssh_3.8p1-1_armeb.ipk

puppy_1.2-1_armeb.ipk

Added lines 86-88:

bash_2.05b-1_armeb.ipk

FTP Transfer to nlsu2.
Added line 94:
  • add properly formatted example of ftp transfer*
Changed lines 96-132 from:

Below is an example ftp transfer of a file from my pc to the nslu2.

  1. ftp 192.168.0.100

Connected to 192.168.0.100. 220 aac41689 FTP version 0.7 ready at Tue Dec 21 12:01:54 2004 Name (192.168.0.100:root): anonymous 331 Enter PASS command Password: 230 Logged in Remote system type is Windows95/NT. ftp> ls 200 Port command okay 150 Opening data connection for list "C:\DOCUME~1\LKHOO~1.AUN\LOCALS~1\Temp\FLS1? 0E.tmp" drwx------ 1 ftp users 0 Dec 21 11:42 . drwx------ 1 ftp users 0 Dec 21 11:42 .. -rwx------ 1 ftp users 298160 Dec 21 11:43 bash_2.05b-1_armeb.ipk -rwx------ 1 ftp users 542927 Dec 21 11:43 openssh_3.8p1-1_armeb.ipk -rwx------ 1 ftp users 899521 Dec 21 11:43 openssl_0.9.7d-1_armeb.ipk -rwx------ 1 ftp users 10338 Dec 21 11:42 puppy_1.2-1_armeb.ipk -rwx------ 1 ftp users 55098 Dec 21 12:00 zlib_1.2.1-1_armeb.ipk WARNING! 7 bare linefeeds received in ASCII mode File may not have transferred correctly. 226 Transfer complete ftp> hash Hash mark printing on (1024 bytes/hash mark). ftp> bin 200 Type I OK ftp> get zlib_1.2.1-1_armeb.ipk local: zlib_1.2.1-1_armeb.ipk remote: zlib_1.2.1-1_armeb.ipk 200 Port command okay 150 Opening data connection for retr "/zlib_1.2.1-1_armeb.ipk"

226 Transfer complete 55098 bytes received in 0.0205 secs (2.6e+03 Kbytes/sec) ftp> bye 221 Goodbye!

to:
Manual install of packages.
Changed line 112 from:

ie. puppy -c dir

to:

Basic puppy usage.

Added lines 114-118:

Using puppy is from the command line. There are several different parameters you can pass to it. Type "puppy" and press "Enter" and it will show you all the options that it can take.

In general you'll be interested in using the "-c" flag which sends commands to the Topfield5000PVRT?. A simple test would be to type "puppy -c dir".

Changed lines 123-125 from:

Notes: You'll need to enable telnet each time via the gui interface. I'm trying to find out how this is enabled permanently upon

startup.

to:

Own notes: You'll need to enable telnet each time via the gui interface. I'm trying to find out how this is enabled permanently upon startup.

December 21, 2004, at 03:53 AM by Koops --
Changed lines 1-142 from:

Describe EndUserPuppyInstall here.

to:

The Puppy End User install instructions for getting unslung and puppy working on your nslu2.

Assumptions :

	a.That you've just purchased a Linksys NSLU2 and want to run puppy on it to connect to your Toppy.
	b.That you havn't done anything else to the NSLU2 apart from maybe turn it on and used it as linksys expected ;)
	c.You have a usb disk that you can format and not have to worry about the contents of. 
	(doesn't have to be a huge disk btw!)
	d.That your not that familiar with linux but have some general computer proficiency.

Requirements : Some from of a net connection, "unslung-able 2.x" firmware package.

Pre install.

1.Get unslung-able 2.x firmware from peteru. Email him and politely request it from him. You can email Peter's via "toppy at urbanec dot net".

2. Get the nslug on the local network.

I was using a crossover cable so some of the following may not apply.

	1.Use linksys cd setup to set ip address of the slug.
	Set the nslu IP address to IP 192.168.0.77, subnet 255.255.255.0, gateway 192.168.0.100

	2.Set my pc ip address to IP: 192.168.0.100, subnet : 255.255.255.0, gateway : 192.168.0.77

3.Connect to the web interface of the slug. http://192.168.0.77/ Connect a usb 2.0 disk to the slug. Format the disk under the admin tools/disk page. Test that you can sucessfully use the disk. Copy a file over the network to it. This ensures that we have a known good disk before installing unslung packages on it.

New firmware install.

1.Upload the new unslungable 2.x firmware via the web interface install page. 2.Enable telnet access via the telnet.cgi script. http://192.168.0.77/Management/telnet.cgi 3.Telnet to the machine. From a windows machine you can type "telnet 192.168.0.77" 4.At the username prompt type "root" and at the password prompt type "uNSLUng". 5.Check and see if your disk is formated via the web interface. If not format it :) 6.run /sbin/unslung

Your now running an unslung nslu2! Now onto getting some extra software (and most importantly puppy) installed.

Updating packages.

Now there are two ways to install packages onto the newly unslung nslu2.

1. Direct from the net if your nslu2 has access to the internet.

Simply Type :

ipkg update ipkg install openssl ipkg install openssh ipkg install puppy ipkg install bash

This will update the list of available packages then downloads and installs them from the net.

2. If you've tried the above and get an error its normally because your nslu2 can't grab the packages direct from the net. This situation will occur if you only have proxy access to the net. Don't fret however as you can manually download them and install

sucessfully.

On a machine that has net access. ie. your normal net connected home machine.

goto the http://ipkg.nslu2-linux.org/ipkg/ site and get the following packages. openssl_0.9.7d-1_armeb.ipk, zlib_1.2.1-1_armeb.ipk, openssh_3.8p1-1_armeb.ipk ,puppy_1.2-1_armeb.ipk,bash_2.05b-1_armeb.ipk , optionally

(perl_5.6.1-1_armeb.ipk) from the how-to page.

Now from the nslu2 ftp to my local pc that i've downloaded the packages to. ie. ftp 192.168.0.100 (pc). You'll need to have some type of ftp package installed to serve the files. I was running the free alex small ftp package from my windows machine.

Below is an example ftp transfer of a file from my pc to the nslu2.

  1. ftp 192.168.0.100

Connected to 192.168.0.100. 220 aac41689 FTP version 0.7 ready at Tue Dec 21 12:01:54 2004 Name (192.168.0.100:root): anonymous 331 Enter PASS command Password: 230 Logged in Remote system type is Windows95/NT. ftp> ls 200 Port command okay 150 Opening data connection for list "C:\DOCUME~1\LKHOO~1.AUN\LOCALS~1\Temp\FLS1? 0E.tmp" drwx------ 1 ftp users 0 Dec 21 11:42 . drwx------ 1 ftp users 0 Dec 21 11:42 .. -rwx------ 1 ftp users 298160 Dec 21 11:43 bash_2.05b-1_armeb.ipk -rwx------ 1 ftp users 542927 Dec 21 11:43 openssh_3.8p1-1_armeb.ipk -rwx------ 1 ftp users 899521 Dec 21 11:43 openssl_0.9.7d-1_armeb.ipk -rwx------ 1 ftp users 10338 Dec 21 11:42 puppy_1.2-1_armeb.ipk -rwx------ 1 ftp users 55098 Dec 21 12:00 zlib_1.2.1-1_armeb.ipk WARNING! 7 bare linefeeds received in ASCII mode File may not have transferred correctly. 226 Transfer complete ftp> hash Hash mark printing on (1024 bytes/hash mark). ftp> bin 200 Type I OK ftp> get zlib_1.2.1-1_armeb.ipk local: zlib_1.2.1-1_armeb.ipk remote: zlib_1.2.1-1_armeb.ipk 200 Port command okay 150 Opening data connection for retr "/zlib_1.2.1-1_armeb.ipk"

226 Transfer complete 55098 bytes received in 0.0205 secs (2.6e+03 Kbytes/sec) ftp> bye 221 Goodbye!

Now cut and paste each of in the following commands to install each of the packages.

ipkg install openssl_0.9.7d-1_armeb.ipk ipkg install zlib_1.2.1-1_armeb.ipk ipkg install openssh_3.8p1-1_armeb.ipk <- This command will take a while as it generates the keys. ipkg install puppy_1.2-1_armeb.ipk ipkg install bash_2.05b-1_armeb.ipk

If you'd like to run some perl scripts you can optionally install perl. (ipkg install perl_5.6.1-1_armeb.ipk)

Now your finished!

Now you can run your puppy commands ... AFTER you've connected your topfield to the nslu2.

ie. puppy -c dir

This should list the contents of the topfield disk.

The other commands are : "size, dir, get, put, rename, delete, reboot, cancel".

Notes: You'll need to enable telnet each time via the gui interface. I'm trying to find out how this is enabled permanently upon

startup.

view · edit · print · history · Last edited by John.
Based on work by odvdveer, tman, Koops, camthecameraman, Olga D van de Veer, peteru, and rwhitby.
Originally by Koops.
Page last modified on December 05, 2005, at 11:48 PM