NSLU2-Linux
view · edit · print · history

FAQ.HomePage History

Hide minor edits - Show changes to markup

February 08, 2009, at 11:11 AM by maisondouf -- ls command output format error
Added line 88:
October 18, 2008, at 08:08 PM by Ghostface -- replaced usb stick with usb flash drive
Changed line 87 from:
to:
October 18, 2008, at 07:58 PM by Ghostface -- Add a new problem+solution to the troubleshooting section
Added line 87:
August 18, 2008, at 04:27 AM by stanley_p_miller -- added ipkg xsystem error section
Added line 86:
February 04, 2008, at 11:12 PM by rednuht -- link to - checking networking for first time usage
Added line 53:
January 07, 2008, at 06:28 PM by bcrowell --
Added line 25:
January 05, 2008, at 04:02 PM by SyNko -- ive added the endianness explanation in order to clearify the Be and Le distro type
Changed lines 30-31 from:
to:
January 02, 2008, at 02:48 AM by bcrowell -- ForgetsUserPasswords
Added line 82:
December 04, 2007, at 08:09 PM by Dmitri -- Added FAQ about stock firmware
Added line 81:
July 09, 2007, at 01:55 AM by vivekv -- adding information on sluginfo.cgi
Added line 80:
May 28, 2007, at 02:33 PM by johnmc --
Added line 10:
November 23, 2006, at 03:19 AM by M0les -- Added simple MAC address label-reading explanation
Changed lines 46-47 from:
to:
November 06, 2006, at 03:48 PM by natch -- added question about constantly blinking access light on thumbdrive.
Added line 60:
October 16, 2006, at 04:19 AM by AM --
Changed line 76 from:
to:
October 15, 2006, at 06:16 PM by AM --
October 15, 2006, at 05:34 PM by AM --
Changed lines 75-76 from:
to:
August 22, 2006, at 06:46 PM by garbled -- add formatting
Changed lines 74-75 from:
to:
June 30, 2006, at 01:35 AM by PatrickSchneider -- Added table of comparision for the different NSLU2-firmwares
Added line 10:
June 23, 2006, at 12:43 PM by pepesz76 --
Changed lines 38-39 from:
to:
June 23, 2006, at 12:42 PM by pepesz76 --
Changed lines 38-39 from:
to:
June 22, 2006, at 11:10 PM by pepesz76 --
Changed lines 37-38 from:
to:
June 13, 2006, at 10:44 PM by Zak --
Changed lines 5-6 from:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the wiki as "payment" for having your question answered.

to:

If the answer to your question asked on the mailing list contains new information, it should make its way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the wiki as "payment" for having your question answered.

May 01, 2006, at 10:50 AM by Liviu Ionescu -- OpenSlugBuildFailsDueToSymlinks added
Changed lines 36-37 from:
to:
January 08, 2006, at 07:30 AM by tman --
Changed line 9 from:
to:
January 08, 2006, at 07:30 AM by tman -- Renamed page
Changed line 9 from:
to:
January 05, 2006, at 04:58 PM by tman --
Changed lines 34-37 from:

almost same kind of mipsel cpu.So I want to play !]]

to:
January 03, 2006, at 04:30 PM by roberto_silva_pt -- How to mount Unslung SMB (Samba 3.0.14a) disk in Mac OS X
Changed lines 71-72 from:
to:
November 22, 2005, at 03:34 AM by AndreaFanfani -- Added a brief FAQ about the compilation of single package.
Changed lines 36-37 from:
to:
November 18, 2005, at 08:38 AM by nnhoan -- optware wl500g build mini howto
Changed lines 34-85 from:
  • [[Optware_wl500g howto|wl500g from Assus uses BCM947xx? ;I have netgear wgt634u using bcm5365

almost same kind of mipsel cpu.So I want to play ! A toolchain: http://downloads.openwrt.org/docs/buildroot-documentation.html $cvs -d:pserver:anonymous@openwrt.org:/openwrt co openwrt once the compilation succeeded, copy /openwrt/staging_dir_mipsel to /opt/brcm/hndtools-mipsel-uclibc In the bin/ mipsel-linux-uclibc-gcc is referred to ,while in the master Makefile mipsel-uclibc-gcc is used ;so either make the necessary symlinks in the bin/ or modify in the master Makefile to reflect this. B wl500g_optware:

 put the nslu2_master_Makefile in Mywl500g/ directory.To build the optware :

$make setup-optware (it in fact cvs check out "cvsroot/nslu co -d optware unslung" ) $make optware-wl500g will normally build all the wl500g packages described in the Makefile. C needed Hacks: I describe just two as examples to follow;you need more to get the full blown packages compiled ! Once "adduser" successfully built,it just stops at "adns " with the following error: -- make[3]: Entering directory `/home/wangji/hslug/optware/wl500g/builds/adns/src' /opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc -g -O2 -Wall -Wmissing-prototypes -Wwrite-strings -Wstrict-prototypes -Wcast-qual -Wpointer-arith -c -o parse.o parse.c parse.c:118: error: conflicting types for 'adns__parse_domain' internal.h:579: error: previous declaration of 'adns__parse_domain' was here -- 2 ways to solve :

 a dirty_solution: 
   just replace in optware/wl500g/builds/adns/src/parse.c line 117 :
       adns_queryflags  by  parsedomain_flags 
  redo '$make optware-wl500g' to resume the build
 b pseudogood_solution :
    create 2 trees adns-1.1/  and adns-1.1-patch/ from adns-1.1.tar.gz
    modify parse.c as in a)  then create the patch with
    diff -Naur adns-1.1 adns-1.1-patch > optware/sources/adns/adns-1.1.patch
  modify optware/make/adns.mk to reflect this ;2 lines are concerned
  line 41 : ADNS_PATCHES=$(ADNS_SOURCE_DIR)/adns-1.1.patch
  line 96 :  cat $(ADNS_PATCHES) | patch -d $(BUILD_DIR)/$(ADNS_DIR) -p1

again,redo make optware-wl500g to resume;you will be stopped at "bash" with error: -- make[3]: Entering directory `/home/wangji/hslug/optware/wl500g/builds/bash/lib/malloc' /opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc -I. -I../.. -I../.. -I../../include -I../../lib -DHAVE_CONFIG_H -DSHELL -g -O2 -DRCHECK -Dbotch=programming_error -O2 -pipe -I/home/wangji/hslug/optware/wl500g/staging/opt/include -c malloc.c malloc.c:239: warning: integer constant is too large for "unsigned long" type malloc.c: In function `internal_free': malloc.c:904: error: label at end of compound statement make[3]: *** [malloc.o] Error 1 -- dirty solution "label at end of compound statement":

 add a "return;"  to line 904 of optware/wl500g/builds/bash/lib/malloc/malloc.c

resume with make optware-wl500g ! D poor Noobs might not know : you better install in your host machine both automake1.4 and 1.9 : it helps a lot :-)]]

to:

almost same kind of mipsel cpu.So I want to play !]]

November 18, 2005, at 07:45 AM by nnhoan -- optware_wl500g howto
Changed lines 34-85 from:
to:
  • [[Optware_wl500g howto|wl500g from Assus uses BCM947xx? ;I have netgear wgt634u using bcm5365

almost same kind of mipsel cpu.So I want to play ! A toolchain: http://downloads.openwrt.org/docs/buildroot-documentation.html $cvs -d:pserver:anonymous@openwrt.org:/openwrt co openwrt once the compilation succeeded, copy /openwrt/staging_dir_mipsel to /opt/brcm/hndtools-mipsel-uclibc In the bin/ mipsel-linux-uclibc-gcc is referred to ,while in the master Makefile mipsel-uclibc-gcc is used ;so either make the necessary symlinks in the bin/ or modify in the master Makefile to reflect this. B wl500g_optware:

 put the nslu2_master_Makefile in Mywl500g/ directory.To build the optware :

$make setup-optware (it in fact cvs check out "cvsroot/nslu co -d optware unslung" ) $make optware-wl500g will normally build all the wl500g packages described in the Makefile. C needed Hacks: I describe just two as examples to follow;you need more to get the full blown packages compiled ! Once "adduser" successfully built,it just stops at "adns " with the following error: -- make[3]: Entering directory `/home/wangji/hslug/optware/wl500g/builds/adns/src' /opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc -g -O2 -Wall -Wmissing-prototypes -Wwrite-strings -Wstrict-prototypes -Wcast-qual -Wpointer-arith -c -o parse.o parse.c parse.c:118: error: conflicting types for 'adns__parse_domain' internal.h:579: error: previous declaration of 'adns__parse_domain' was here -- 2 ways to solve :

 a dirty_solution: 
   just replace in optware/wl500g/builds/adns/src/parse.c line 117 :
       adns_queryflags  by  parsedomain_flags 
  redo '$make optware-wl500g' to resume the build
 b pseudogood_solution :
    create 2 trees adns-1.1/  and adns-1.1-patch/ from adns-1.1.tar.gz
    modify parse.c as in a)  then create the patch with
    diff -Naur adns-1.1 adns-1.1-patch > optware/sources/adns/adns-1.1.patch
  modify optware/make/adns.mk to reflect this ;2 lines are concerned
  line 41 : ADNS_PATCHES=$(ADNS_SOURCE_DIR)/adns-1.1.patch
  line 96 :  cat $(ADNS_PATCHES) | patch -d $(BUILD_DIR)/$(ADNS_DIR) -p1

again,redo make optware-wl500g to resume;you will be stopped at "bash" with error: -- make[3]: Entering directory `/home/wangji/hslug/optware/wl500g/builds/bash/lib/malloc' /opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc -I. -I../.. -I../.. -I../../include -I../../lib -DHAVE_CONFIG_H -DSHELL -g -O2 -DRCHECK -Dbotch=programming_error -O2 -pipe -I/home/wangji/hslug/optware/wl500g/staging/opt/include -c malloc.c malloc.c:239: warning: integer constant is too large for "unsigned long" type malloc.c: In function `internal_free': malloc.c:904: error: label at end of compound statement make[3]: *** [malloc.o] Error 1 -- dirty solution "label at end of compound statement":

 add a "return;"  to line 904 of optware/wl500g/builds/bash/lib/malloc/malloc.c

resume with make optware-wl500g ! D poor Noobs might not know : you better install in your host machine both automake1.4 and 1.9 : it helps a lot :-)]]

November 14, 2005, at 03:07 AM by kc --
Changed line 14 from:
to:
November 14, 2005, at 03:05 AM by kc --
Added line 14:
November 03, 2005, at 02:48 PM by Cheef-Daniel --
Added line 65:
October 25, 2005, at 07:19 AM by RandomVisitor -- wiki isn\'t a proper noun
Changed lines 5-6 from:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the Wiki as "payment" for having your question answered.

to:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the wiki as "payment" for having your question answered.

September 26, 2005, at 09:04 AM by hilikus --
Changed lines 65-66 from:
to:
September 16, 2005, at 10:30 PM by Newb -- simple question
Added line 9:
September 01, 2005, at 06:23 PM by grahame_falvey -- Link to USB Hub FAQ
Changed lines 38-39 from:
to:
August 28, 2005, at 10:07 PM by effem -- added DiskNotRecognized entry
Changed lines 62-63 from:
to:
August 22, 2005, at 04:43 PM by tman --
Changed lines 7-56 from:

Contents

Which firmware should I use first?
I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?
How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI, IDE, USB, etc...), using Microsoft Windows??
When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory"
What is the root password on an unmodified NSLU2 with stock Linksys firmware (version xx)
How do I completely backup my NSLU2??
When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware)
When I modify /etc/passwd, I still can't telnet into my box
Can I use the built-in thttpd for my web-server?
My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?
Can I setup the NSLU2 to use NTFS partitions?
Can I use RAID?
Which SSH daemon should I use?
Can I boot the NSLU2 with a USB device as the root filesystem?
Can I use a USB hub so that I can add more than two external hard drives?
I need to build more kernel modules, where are the kernel sources for the NSLU2?
What is the ixp1 interface, and can it be used for anything useful?
Can I write and compile code directly on the NSLU2?
Why does my NSLU2 beep every eight hours?
When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information"
ipkg update doesn't work?
How do I spin down my USB hard disks?
After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore
What is the difference between a "soft-float" and "hard-float" compiler?
Are there any differences between the NSLU2 and the NSLU2UK?
When I first apply power to the NSLU2, it is off. How do I fix that?
Why are you still using R29 firmware? R63 is out.
The NSLU drops connections all the time, even the web interface times out.
Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected
How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible?
How can I recover a bad conf parition when the web interface says my HD is "not formatted"?
How can I restore Samba on NSLU2 if it is no longer working?
Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?
Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all files in the root file system are very old?
What can I do if sda2 (/share/hdd/conf) is getting full and I cant install ipkg packages anymore?
What's the default password for Openslug?
Why do pages on this wiki not format correctly?
I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?
How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.
Why do Bad Things happen after installing Unslung 4.20 beta?
How can I get a working ipkg sub-system after upgrading it with the bad one which had been made available in the feed in May 2005?
Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-Beta or Linksys 2.3R29?
How to check your disk for errors (and repair them)
Why does my NSLU2 suddenly take so long (4 minutes or more) to reboot
How can I determine my installed Unslung version?
What is the Unslung version telling me?
How to correct that the Ready/Status LED won´t turn green and allow communication after upgrading with Unslung 5.5-Beta
How to determine that rootfs really exist on USB disk after unslinging\\

to:

Contents

Hardware

Troubleshooting

Wiki

August 22, 2005, at 04:27 PM by tman --
Changed lines 5-6 from:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the Wiki as "payment" for having your question answered.

to:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the Wiki as "payment" for having your question answered.

Changed lines 9-564 from:

1. Which firmware should I use first?
2. I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?
3. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI, IDE, USB, etc...), using Microsoft Windows?
4. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory"
5. What is the root password on an unmodified NSLU2 with stock Linksys firmware (version xx)
6. How do I completely backup my NSLU2?
7. When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware), I cannot do XXX.
8. When I modify /etc/passwd, I still can't telnet into my box
9. Can I use the built-in thttpd for my web-server?
10. My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?
11. Can I setup the NSLU2 to use NTFS partitions?
12. Can I use RAID?
13. Which SSH daemon should I use ?
14. Can I boot the NSLU2 with a USB device as the root filesystem?
15. Can I use a USB hub so that I can add more than two external hard drives?
16. I need to build more kernel modules, where are the kernel sources for the NSLU2?
17. What is the ixp1 interface, and can it be used for anything useful?
18. Can I write and compile code directly on the NSLU2?
19. Why does my NSLU2 beep every eight hours?
20. When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information"
21. ipkg update doesn't work?
22. How do I spin down my USB hard disks?
23. After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore
24. What is the difference between a "soft-float" and "hard-float" compiler?
25. Are there any differences between the NSLU2 and the NSLU2UK?
26. When I first apply power to the NSLU2, it is off. How do I fix that?
27. Why are you still using R25 firmware? R29 is out.
28. The NSLU drops connections all the time, even the web interface times out.
29. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected
30. How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible
31. How do I install Apache?
32. How can I recover a bad conf parition when the web interface says my HD is "not formatted"?
33. How can I restore samba on NSLU2 if it is no longer working?
34. Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?
35. Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all the files in the root file system are very old?
36. What can I do if sda2 (/share/hdd/conf) is getting full and i cant install ipkg packages anymore?
37. What's the default password for Openslug?
38. Why do pages on this wiki not format correctly?
39. I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?
40. How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.
41. Why do Bad Things happen after installing Unslung 4.20 beta?
42. How can I get a working ipkg sub-system after upgrading it with the bad one which had been made available in the feed in May 2005?
43. Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-beta or Linksys 2.3R29?
44. How to check your disk for errors (and repair them)
45. Why does my NSLU2 suddenly take so long (4 minutes or more) to reboot
46. How can I determine my installed uNSLUng version?
47. What is the uNSLUng version telling me?
48. How to correct that the Ready/Status LED won´t turn green and allow communication after upgrading with BETA 5.5
49. How to determine that rootfs really exist on usbdisk after unslinging
50. Setting up cross gdb for nslu2
51. (Obsolete)Where is ftpd or other (standard linux) utilities?

1. Which firmware should I use first?

Unslung 5.5-beta - see HowToGetInvolved? for details.

2. I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?

OK, here's the deal. If you flash the Unslung firmware with NO disks attached (as you should), and THEN enable telnet through the web interface (STILL with NO disks attached, as explained in the README) and then telnet to the IP address of the NSLU2 (STILL with NO disks attached, and telneting to Linux, NOT to RedBoot), you will be able to log in as "root" with the password "uNSLUng" (as long as there are STILL NO disks attached). BUT, as soon as you plug a disk in, the password will CHANGE to whatever password is stored (in MULTIPLE places) on the disk. And this other password (which you probably don't know, and neither do we) may even PERSIST after you unplug the disk (as it may have been automatically copied into the root filesystem which is now in the internal flash in Unslung 3.x). So you either need to change that root password (using the ChangePasswordsFromTheCommandLine instructions because simply editing the /etc/passwd file is NOT enough to make it stick, see also FAQ nr 7) AND follow the instructions in DiversionScripts to permanently enable telnet, OR install and configure the dropbear or openssh package.

3. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI, IDE, USB, etc...), using Microsoft Windows?

You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest, Paragon Partition Manager is fairly quick), and with most utilities, all the files written will be owned by root. Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.

4. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

If you are running with a USB flash or hard disk with unmodified firmware, this is the result of the Linksys upgrade application thinking that the NSLU2 has run out of memory (it hasn't really - it's just being temporarily used for buffers and caching, and is still available for any programs that need it, but the Linksys upgrade application is not smart enough to know that). Turning off the NSLU2, removing ALL drives, rebooting without any disks connected and then going straight into the Admin webpage for the firmware upgrade should get rid of the error.
Received the "Not enough Memory" message while updating a brand new untouched NSLU2 with the latest Linksys firmware (NSLU2_V23R29.bin) from the Linksys support site. NSLU2 had no disks attached at the time. Followed the above advice and flash completed OK.

5. What is the root password on an unmodified NSLU2 with stock Linksys firmware (version xx).

The short answer is that we don't know, and we don't want to know.
There are concerns that releasing this information allows people to gain access to any internet visible NSLU2. However, by default the NSLU2 resides on a unroutable subnet (192.168.1.77) which would mean that any attack would have to originate from inside your network. If this was the case then securing your NSLU2 is the least of your problems. Allowing unrestricted access from the internet is also a bad idea. Both possible avenues for abuse result from implicit actions by the user/owner to allow access.
The default administrative access via the web interface is user:admin password:admin

6. How do I completely backup my NSLU2?

There are several parts to this answer. First get root access as noted above for the stock Linksys or other places for Unslung or Openslug. Next you will need to backup all the partitions from the flash and the hard driver/flash stick. A recommendation is to backup the flash onto the hard drive/flash stick first, then when one backs up the hard drive/flash stick (HD/FS) you'll have both.
At the root prompt, type "dmesg" to get a printout of the console of the kernel messages during boot. Search in there for something like the following:
Searching for RedBoot partition table in IXP4XX-Flash0 at offset 0x7e0000
6 RedBoot partitions found on MTD device IXP4XX-Flash0
Creating 6 MTD partitions on "IXP4XX-Flash0":
0x00000000-0x00040000 : "RedBoot" ....
This lets you know there are 6 partitions in the flash. N.B. BE VERY CAREFUL with the following commands. A mistyped or bad command can literally erase or hose up you're entire system. USE AT YOUR OWN RISK. First, MAKE SURE your current working directory is on the HD/FS. Then for each of the partitions do some similar to the following:
dd if=/dev/mtdblock0 of=redboot.bin
dd if=/dev/mtdblock1 of=sysconf.bin
dd if=/dev/mtdblock2 of=kernel.bin
Continue this all the way through mtdblock5 or how many partitions one has. Note: Since we started at 0, the mtdblock number will be 1 less than the total number.
Note: the block number start with 0. This provides you with a binary copy of the contents of the individual paritions in flash. Next, you will need to properly shutdown and power off the NSLU2 to backup the contents of the HD/FS. This is most easily performed on another system. I'd recommend getting a copy of ubuntu or knoppix and running from the livecd if you don't have access to Linux/Unix system.
On that Linux/Unix system, one needs to plug in the NSLU2 hard drive/flash stick, I'd suggest mounting the partitions read only, and tar up the partitions and save off a copy of the MBR (master boot record -- this contains the partition table on the disk itself). With this data, an indentical type disk could be restored. Other disks could be restored which are larger also. When done shutdown properly and reattach the HD/FS to the NSLU2.
Finally, as long as Redboot isn't toasted, you can reload and restore the flash partitions. If Redboot is toasted, then you'd need to do hw modifications to get JTAG access to restore Redboot or another boot loader to the flash and then be able to restore everything.

7. When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware), I cannot do XXX.

If you attach a regular USB hard disk to the NSLU2, you must first format the drive. This creates 3 partitions (two ext3 filesystems and swap). With flash drives, the NSLU2 won't normally let you do this. However, the NSLU2 still recognizes the drive and mounts it as a single VFAT (Windows-based) filesystem. This causes a number of problems and most of the fancy functionality of the NSLU2 is not available (like adding users, controling shares, creating backup jobs, etc). However, the box will still function as a simple Samba server with one directory shared. If this works for you, great. Otherwise, you may want to look into one of the custom firmware options to get more out of your box.

8. When I modify /etc/passwd, I still can't telnet into my box.

The NSLU2 keeps multiple copies of /etc/passwd. You may also need to change the copies in /usr/local and /share/*/conf/.
 
     1: /share/hdd/conf/usr/local/passwd
        /share/hdd/conf/passwd
        /share/flash/conf/passwd
        /share/flash/conf/usr/local/passwd
     2: /share/hdd/conf/etc/passwd -> /share/hdd/conf/passwd
        /share/flash/conf/etc/passwd -> /share/hdd/conf/passwd
     3: /usr/local/etc/passwd
 
Marked with 1 are the locations you should check and edit.
Marked with 2 are links only.

9. Can I use the built-in thttpd for my web-server?

Yes, see the HowTo section.

10. My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?

Fedora Core 2 uses NFS protocol version 3 by default. You need to pass the nfsvers option to the mount command in order to force the NFS client to use an older protocol version: mount -t nfs -o nfsvers=2 <nslu2 ip>:/share/hdd /mnt

11. Can I setup the NSLU2 to use NTFS partitions?

Currently, no.
There are two NTFS drivers for Linux in existance:
  • Captive - http://www.jankratochvil.net/project/captive/
This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow.
  • Linux NTFS project - http://linux-ntfs.sourceforge.net/status.html
This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users. The new, rewritten version of the NTFS driver is included in the Linux 2.6.9 kernel, so once the OpenSlug project succeeds in getting the 2.6 kernel running on the NSLU2, it will be possible to see if this driver works.
update: Recent (April 2005+) builds of OpenSlug come with the NTFS kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled in - so the mount is read-only.

12. Can I use RAID?

Yes. But currently only with the Unslung-able firmware. How to enable RAID support in Unslung-able. OpenSlug is capable of RAID support but nobody has tried it yet.

13. Which SSH daemon should I use ?

dropbear is more lightweight. The downside is that dropbear does not support that many features and is slower. OpenSSH does support the full set of features and is a bit quicker in the key handling. One set of tests found OpenSSH on the NSLU2 to be 8x faster than dropbear at scp transfers - 800kB/s vs 100kB/s (using "scp -c blowfish" as this should be the least CPU-intensive cypher).

14. Can I boot the NSLU2 with a USB device as the root filesystem?

Yes, using the Unslung firmware (version 2.12-beta or later), with either a 1Gb or larger external hard disk plugged into either port, or a 256MB or larger flash disk plugged into the Disk1 port.

15. Can I use a USB hub so that I can add more than two external hard drives?

Not with the stock Linksys firmware. Nor can it be done with Unslung firmware. OpenSlug firmware (which is in early alpha testing, and is only available if you build it from source code and have a serial port added to your slug) will be able to when it is released. Note that you can add other devices using a hub, just not more than two external mass storage devices.

16. I need to build more kernel modules, where are the kernel sources for the NSLU2?

  • Use the OpenEmbedded environment to create your kernel and configure modules there
  • Get the kernel sources from ...

17. What is the ixp1 interface, and can it be used for anything useful?

The IXP420 has two network interfaces built in, ixp0 and ixp1. ixp0 is wired to the ethernet socket on the back through the RealTek PHY chip. ixp1 however is not connected to anything at all and the lines aren't brought out anywhere on the PCB. This means that it is not possible to use ixp1 at all.

18. Can I write and compile code directly on the NSLU2?

Yes! See NativeNSLU2Toolchain to set up a development environment on your Unslung NSLU2, and see BuildGNUMakeOnYourNSLU2Box, MakeGNUGawkOnYourNSLU2Box, and MakeThttpdOnYourNSLU2Box for examples of doing this.

19. Why does my NSLU2 beep every eight hours?

peecock41 figured out what it means when the NSLU2 beeps every 8 hours.

20. When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information".

Something probably got fudged up in the internal system configuration. Re-flashing won't fix the problem; you will need to reset the system configuration.

21. ipkg update doesn't work

Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
These errors can be cause by two things. 1) DNS is unreachable and 2) you have an http proxy.
Simple solution: It is easy to miss a DNS setting. Revert network and slug to default settings. If you overlooked a DNS setting previously reverting to defaults may eliminate the problem.
Default settings should be as follows.
Router IP - 192.168.1.1 <http://192.168.1.1>
Subnet 255.255.255.0 <http://255.255.255.0>
Slug IP: 192.168.1.77 <http://192.168.1.77>
Subnet 255.255.255.0 <http://255.255.255.0>
Default port 80
If these settings do not make a difference consider the following file edits.
DNS is unreachable.
Solution: Make sure your netmasks and gateway information are set properly. If they are and you're running an own dhcp server on your LAN, see that there's a line like option domain-name-servers dns.ip.address.here, 2nd.ip.address.here; in your /etc/dhcpd.conf file.

Solution: If you have a windows box, bring up a command line and type "ipconfig /all." Note the gateway and DNS server numbers. Go to the Linksys slug setup page ("Administration," then "LAN") and make sure you have entered the proper network mask, gateway (usually the same IP as your router) AND DNS servers.

You have an http proxy.
Solution: You need to configure ipkg to go through the proxy. This is done through the file /etc/ipkg.conf, but the standard unSlung installation doesn't have a sample file.
For a simple proxy, a single line option http_proxy http://proxy.ip.address.here:proxy_port will do the job (mine needs option http_proxy http://192.168.255.1:3128).
For a proxy that needs username, password etc. you'll need more - look at the ipkg documentation at http://handhelds.org/moin/moin.cgi/Ipkg and the sample file http://openwrt.org/ipkg/ipkg.conf.

22. How do I spin down my USB hard disks?

You can download the Power Booster utility at http://www.hitachigst.com/downloads/pbinstall.exe for 2.5" IBM/Hitachi TravelStar disks. The Power Booster utility will enable the auto spin down feature of the disk. For 3.5" IBM/Hitachi drives (and maybe others), you can download the Feature Tool at http://www.hitachigst.com/hdd/support/download.htm. Otherwise temporarily install the IDE disk in your ordinary Linux box, read the disk technical documentation and use hdparm to adjust the settings by hand. The trick is to enable APM within the drive itself, so Linux doesn't have to care about it at all. You can't use hdparm to alter the APM settings from the NSLU2 as the USB->IDE adapters are emulated as SCSI host adapters in the Linux kernel which is incompatible with the necessary hdparm options.
Either way, you'll have to open your 2.5" USB enclosure and install the disk drive temporarily to a desktop computer using a 2.5" to 3.5" IDE adapter. After that, you can do the APM adjustment in Windows or Linux.
For Maxtor OneTouch drives see the Maxtor OneTouch HOWTO.
I just bought a Seagate Baracuda 3.5" drive and installed it in a third party enclosure. Upon contacting their tech support in Europe they stated that:
  • Seagate does not support other power management than managed by the running OS
  • Seagate does not support drives to be installed in third party enclosures
  • Seagate disks do not have a function to retain the power management settings
So I guess my advice would be not to buy the Seagate disks

23. After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore

The original Linksys backup binary has problems with symbolic links, the backup can be made working again using rsync.

24. What is the difference between a "soft-float" and "hard-float" compiler?

"float" refers to a floating point unit (FPU) in a CPU to do floating point math calculations. Some CPUs don't have a built in FPU but a lot of software requires the use of one. To achieve this on a platform without a FPU you can use an emulator. There are two types of emulation, one where the kernel will trap all the opcodes related to the FPU and then perform the calculations itself or one where you put the emulator into the application binary itself and it does it all internally.
The FPU emulators are architecture specific and the kernel based one for the ARM architecture is NWFPE (NetWinder Floating Point Emulator) which was written by NetWinder? for their series of ARM based devices.
The user space emulation system is more efficient than the kernel space one due to not requiring the need to trap illegal instruction errors and then performing the requested calculation. Each time you issue a FP opcode, there will be a context switch which is expensive in terms of time and speed. Building the necessary code into the application binary itself however means it just calculates it directly without the need for the traps. The disadvantage however is that the FP code is built into each application and any non compliant applications won't be supported.
It is possible to use a kernel with NWFPE built in for all non softfloat binaries and have softfloat for everything else.
Example: Now you should understand better the following string when you compile codes for nslu2:
"armv5b-softfloat-linux/gcc-3.3.4-glibc-2.2.5/bin/armv5b-softfloat-linux-gcc"
See this URL for futher details: http://linux-7110.sourceforge.net/howtos/netbook_new/x936.htm

25. Are there any differences between the NSLU2 and the NSLU2UK?

In the UK we get the NSLU2UK shipped instead of the NSLU2. The difference is that it comes with a UK PSU.

26. When I first apply power to the NSLU2, it is off. How do I fix that?

See the HowTo Recipes for hardware hacking.

27. Why are you still using R25 firmware? R29 is out.

Unslung 5.x uses R29. The GPL sources for the R29 firmware has been published at the Linksys GPL Code Center. More details about R29 are at LinksysR29. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.

28. The NSLU drops connections all the time, even the web interface times out.

Try disabling UPnP support on the NSLU2 and possibly on the router as well. A user reports that their NSLU2 was basically unusable until they switched off UPnP support through the web admin interface. Since disabling UPnP support in the NSLU2, there have not been any problems. There may be issues with certain D-Link routers (in this case a D-Link 624) and UPnP support as well so it is recommended that you disable UPnP support in the router. Please leave a note in the wiki if disabling UPnP support helps.
I had to disable UPnP to get my NSLU2 to work properly. I have a D-Link DI-524 router.
Disabling UPnP helped for me. I have a D-Link DI-624 router.

29. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected.

This generally occurs when a USB hub is utilized. In it's current state the NSLU2 Unslung kernel only supports two drives, one on each port. Several USB devices may appear to the NSLU2 as multiple drivers and this confuses the Unslung kernel. A common example is having a printer with a flash card slot plugged into a USB hub along with a hard disk. In this case, there is a high chance that the web interface will incorrectly report the drive as "Not Formatted" because it is looking at the flash card slot in the printer instead of the expected hard disk. DO NOT WORRY. Your drive and it's data is intact and to fix this you just need to disconnect the conflicting devices (in this case the printer) and restart the NSLU2.

30. How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible.

Upgrading OpenSSH when you're logged in via OpenSSH is unfortunately not a good thing to do. Fortunately there is a solution: enable telnet on the NSLU2 via http://192.168.1.77/Management/telnet.cgi (Note: This has been removed as of R29), then telnet into the NSLU2 and type 'ipkg install openssh' which will reinstall/upgrade OpenSSH.

31. How do I install Apache?

1. ipkg install unslung-feeds
2. ipkg update
3. ipkg install php-apache (This will install PHP, Apache and all the other needed apps too)
4. Restart your NSLU2 or restart the Apache server by typing this line:

/opt/etc/init.d/S80apache restart
Now you're done.
Note that the default Apache installation uses port 8000, so to view your test installation:
http://(NSLU2 location):8000
If you try to install Apache without doing the "unslung-feeds" step, chances are you will get an error like

ERROR: Cannot satisfy the following dependencies for apache: openldap openldap

32. How can I recover a bad conf parition when the web interface says my HD is "not formatted" ?

If you have erased your conf parition but you have a made a backup of the files (by a simple tar czf /share/hdd/conf/*), when you restore the files, the HD won't be recognized anymore...
The solution is to recreate the two hidden files that you haven't saved...
If your conf parition isn't mounted yet, mount it (mount /dev/sda2 /share/hdd/conf)
The commands are:
  
        touch /share/hdd/conf/.dongle
        chmod 0666 /share/hdd/conf/.dongle
        touch /share/hdd/conf/.htpasswd
        chmod 0644 /share/hdd/conf/.htpasswd
  
Now you must fill the .htpasswd file by a password generated by the htpasswd provided by apache... search htpasswd on google for more informations...

33. How can I restore samba on NSLU2 if it is no longer working?

1. Turn NSLU2-HDD off
2. Flash NSLU2 with original Linksys R25 firmware using telnet into RedBoot & use a TFTP server or use the SerComm upgrade protocol (see HowTo's)
3. Reset sysconf (see HowTo's)
4. Flash unslung-version of choice (e.g. 3.18) via webpage of NSLU2
5. Telnet into NSLU2 after enabling telnet and login with standard password
6. Turn HDD on
7. Unsling again with "/sbin/unsling"
8. Reboot
Now samba should work again, your data on the HDD should be unchanged.

34. Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?

When the slug first boots up, the data partition is readonly until the disk quota system has scanned it and computed the disk usage of all the users. Depending on how much data there is on your data partition, this may take several seconds, or several minutes. Note that this is the default behaviour of Unslung; it will happen even if you have not done anything to configure the quota system.
This issue frequently bites people who have linked /opt to a directory in the data partition in order to get more space for packages. If you do that, you must either disable quotas (see below) or live with the fact that /opt might not always be writable.
If you have no interest in quotas, you might want to disable them by creating a DiversionScript. Placing this content in /unslung/rc.quota should do the trick:
#!/bin/sh
return 0

35. Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all the files in the root file system are very old?

This is the intended behaviour on a slug with a flash file system root. When the flash file system is created the dates on all the files it contains are set to 0, this corresponds to the last instant in 1969. This means that you can instantly see if a file has been changed.

36. What can I do if sda2 (/share/hdd/conf) is getting full and i cant install ipkg packages anymore?

Best option is to move the /opt directory to the data partition (sda1):
mv /share/hdd/conf/opt /share/hdd/data/opt
rm /opt; ln -s /share/hdd/data/opt /opt
That's it. Thanks to perlguru for the info!

37. What's the default password for Openslug?

opeNSLUg
If you have made some change to delete the root password from the build (so that it is empty on first boot) then it will become:
OpenSlug
in builds after April 3, 2005. (sysconfsetup zaps it on first boot if it is not set.)

38. Why do pages on this wiki not format correctly?

Some pages do not format to fit the width of the window. This is because they contain unsplittable lines which set the minimum width of the text much greater than the width of the window.
These lines appear to be caused by @@typewriter@@ formatting directives. Apparently the wiki code will not split such a line. To avoid this don't set @@ formatting for more than a few words. Simply stop and restart with a pair of @@ directives to give the wiki a chance to line-break.

39. I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?

This problem occurs when copying "large" files (1MB and up, at least on my setup). Small files do not seem to be a problem.
You probably have the slug hooked up to a 10Mbps network. Hook it up to a 100Mbps network and you are back in business. This has to do with the ethernet connection on the slug losing packets when connected to a 10Mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.

40. How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.

The slug has two USB ports marked as:
Disk 1
Disk 2/Flash
The Linksys documentation specifically says: do not plug a USB flash memory key into the "Disk 1" port. You are instructed by Linksys to plug it into the "Disk 2/Flash" port. The Unslung doco however indicates you should format the hard disk (your USB flash memory key) before you do the firmware upgrade and validate its functionality. You plug the USB flash memory key into the "Disk 1" port as recommended and find you can't format it with the Linksys firmware. Now what?
It has to be formatted later using the Unslung firmware. Follow all the Unslung steps as documented and at this step format the USB flash memory key. It should be plugged into the "Disk 1" port and will now be succesfully formatted:
"4) Identify which drive you wish you "unsling", and plug it in. Wait a minute or two while the disk is mounted.
If the disk has not been previously formatted on the NSLU2, then now is the time to do that. Make sure that the drive is recognized in the web interface."
The web interface is a bit vague about whether it has performed a successful format, so give it a minute or so, switch to the Home page and then return to the "Administration-->Disk" page to refresh it. It should now show "Disk 1 Status as "Formatted" and "Disk 2 Status as "Not Installed".
Notes:
1) The USB flash memory key must be 256MB or bigger.
2) Once you are up and running the ports are mapped to these two directories:
Disk 1 ---> /share/hdd/.. (your USB flash memory key)
Disk 2/Flash ---> /share/flash/.. (nothing attached)
This is confusing as you are now using a USB flash memory key for the hard disk -> ie /share/hdd/..
but /share/flash/.. is unused.
3) This FAQ refers to 3.x Unslung software
4) Background info credited to Rod Whitby:
Linksys treats 10GB or larger as disks (ext3) and less than 10GB as flash (VFAT). They only allow flash on disk2. The Unslung firmware treats 1GB or larger as disk (ext3), and less than 1GB as flash (VFAT), unless the flash is on disk1, in which case it is treated as a very small ext3 disk.
256MB is the minimum (due to the way that the Linksys software partitions it). Whether or not you need larger depends on how many packages you are going to load.

41. Why do Bad Things happen after installing Unslung 4.20 beta?

What happened for me was that I was getting inconsistent behaviour after installing Unslung 4.20 beta, which now I am fairly sure was simply that the unslinging had worked, but I had failed to put the device out of maintenance mode after doing the upgrade to 4.20. This meant that everything I tried was filling up device memory, with confusing results (not always recognizing the disk after reboot, some packages install, others do not, etc). The key point was that after unslinging and rebooting I was still seeing this from df:
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 6528 5292 1236 81% /
...
Whereas when it works I see this:
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 192117464 8068452 182097196 4% /
...
with a 160 GB disk, with some data already copied onto it.
(I had previously failed to setup a 1 GB USB flash disk as the primary disk, but now suspect that the problem was the same in both cases).
Eventually the slug refused to boot at all, but the RedBoot rescue method using HTTP worked fine for me, and from that point everything worked properly - presumably because this method of re-flashing does not leave the device in maintenance mode.
Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

42. How can I get a working ipkg sub-system after upgrading it with the bad one which had been made available in the feed during May 2005?

Between Tue May 17 16:27:00 2005 UTC and Thu May 19 22:51:19 2005 UTC (maybe a bit more due to lag time for cleaning the feeds), a bad ipkg package (named 'ipkg_0.99.148-number_armeb.ipk' where number can be from 1 to 4) had been made available in the unslung optware feeds.
A step by step procedure to restore the original ipkg sub-system has been published in the wiki HowTo.
See RestoreWorkingIpkgFromJffs2
The current version works and does not need to be changed. If upgraded ipkg before or after those dates then there is no need to change anything.

43. Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-beta or Linksys 2.3R29?

There exists a bug in Linksys V2.3R29 software (which Unslung 5.5 is based on) that causes Disk 2/Flash to show the following on the web page:
Disk 2/Flash: Ready, 0MB (0% Free)
Using df from a telnet session will show the correct disk usage. We do not have the code for this part of the firmware so it will have to be fixed by Linksys.

44. How to check your disk for errors (and repair them)

  • Boot the slug without disk.
  • Connect the disk.
  • Through telnet unmount all drives.
umount /dev/sda1
  • The web interface still would not allow me to scan. The log said:
"Warning: Out of disk space, scandisk cannot proceed."
  • However if you telnet to the device you can issue the command
/sbin/fsck.ext3 -f /dev/sda1
  • This will check the disk for you (assuming your drive is on /dev/sda1).
If you want to you can add the -y flag to the command. This will answer all questions with yes automatically (which is generally the best choice anyway).
WARNING: be sure to reboot your slug after doing this (to avoid that you accidently fill up the flash filesystem)

This is a test method to run Scandisk from the Web interface * Boot the Slug without a disk * Enable Telnet http://192.168.1.77/Management/telnet.cgi * Telnet using admin/admin * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface * The drive activity light will illuminate while Scandisk proceeds. * When finished, Disk 1 Status will display Scandisk completed. * Disk Log will report that scandisk failed, contradicting the Web interface. * Scandisk appears to work, whereas the Disk Log appears to be in error * More on this later...

45. Why does my NSLU2 suddenly take so long (4 minutes or more) to reboot

The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manually scan the disk – Using the instructions from FAQ Question #44

46. How can I determine my installed uNSLUng version?

cat /.unslung

47. What is the uNSLUng version telling me?

The first number is the Linksys version it is based on, the second is the actual uNSLUng version.

48. How to correct the problem with Ready/Status LED where it won´t turn green and allow communication after upgrading with BETA 5.5
Boot NSLU2 without HD attached.
Telnet in with root/uNSLUng.
rm /.sd#1root <- # being a if you were unslung to disk 1 and b if you were unslung to disk 2 (disk 1 means /dev/sda1, storage media on port 1, disk 2 means /dev/sdb1, storage media on port 2).
Reboot NSLU2 - again without HD attached.
Telnet in with root/uNSLUng.
Plug in the usb disk.
Re-format via web interface, if needed. If not formatting, then just /sbin/unsling disk#. If formatted, wait until formatting is completed, then /sbin/unsling disk# in telnet session.
Reboot with drive attached.
This should get you back to a booting NSLU2 with rootfs on hd

49. How to determine that rootfs really exist on usbdisk after unslinging

Filesystem1k-blocksUsedAvailableUse%Mounted on
rootfs96569564585695129920%/
/dev/sda165285320120881%/initrd
/dev/sda196569564585695129920%/
/dev/sda196569564585695129920%/share/hdd/data
/dev/sda212395541421185333%/share/hdd/conf

This is taken (with the command df) from a freshly unslung nslu2 with 10GB USB disk. If the size of rootfs (9512992) and / on /dev/sda1 (which is my usbdisk on port 1) reflects the size of your disk's data partition (/share/hdd/data), then you are good.

50. setting up cross_gdb for NSLU2

1 a starter gdb tutorial for student:

 http://www.cs.cmu.edu/~gilpin/tutorial/

2 get gdbserver from ipkg-unbuild [openslug pkgs]gdb-6.3*ipk,put into nslu2/usr/bin

3 On host_knoppix compile from src gdb-6.3*tar.gz with

 configure --target=armeb-linux --host=i686-linux
make install will create later " armeb-linux-gdb " binary ,which is our cross_gdb

4 install 'lesstif' then 'ddd' to get " datadisplay debugger GUI "

5 To start crosscompile test.cpp from 1 ,just using openslug_tool

 (openslug)/tmp/cross/bin/armeb-linux-g++ -WALL -ggdb test.cpp -o test_nslu
put test_nslu to ~user_nslu/

6 nslu_side start from ssh_console (kind of telnet)

 gdbserver knoppix_IP:5000 test_nslu 

7 knoppix_side

   ddd --debugger /usr/local/bin/armeb-linux-gdb 
once in gdb connect to gdbserver nslu_IP using
(gdb)target remote nslu1_IP:5000

8 have fun

51. (Obsolete) Where is ftpd or other (standard linux) utilities?

The NSLU2 comes with a stripped down root filesystem. If what you need is in the original SnapGear sources, you can build it yourself easily. See HowTo Recipes for instructions. Or, you can download a binary image of a fairly complete root filesystem build from the NSLU2-Linux yahoo group (see romfs.tar.gz at http://groups.yahoo.com/group/nslu2-linux/files/ ). Then, simply install the utilities that you require.
to:

Which firmware should I use first?
I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?
How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI, IDE, USB, etc...), using Microsoft Windows??
When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory"
What is the root password on an unmodified NSLU2 with stock Linksys firmware (version xx)
How do I completely backup my NSLU2??
When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware)
When I modify /etc/passwd, I still can't telnet into my box
Can I use the built-in thttpd for my web-server?
My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?
Can I setup the NSLU2 to use NTFS partitions?
Can I use RAID?
Which SSH daemon should I use?
Can I boot the NSLU2 with a USB device as the root filesystem?
Can I use a USB hub so that I can add more than two external hard drives?
I need to build more kernel modules, where are the kernel sources for the NSLU2?
What is the ixp1 interface, and can it be used for anything useful?
Can I write and compile code directly on the NSLU2?
Why does my NSLU2 beep every eight hours?
When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information"
ipkg update doesn't work?
How do I spin down my USB hard disks?
After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore
What is the difference between a "soft-float" and "hard-float" compiler?
Are there any differences between the NSLU2 and the NSLU2UK?
When I first apply power to the NSLU2, it is off. How do I fix that?
Why are you still using R29 firmware? R63 is out.
The NSLU drops connections all the time, even the web interface times out.
Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected
How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible?
How can I recover a bad conf parition when the web interface says my HD is "not formatted"?
How can I restore Samba on NSLU2 if it is no longer working?
Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?
Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all files in the root file system are very old?
What can I do if sda2 (/share/hdd/conf) is getting full and I cant install ipkg packages anymore?
What's the default password for Openslug?
Why do pages on this wiki not format correctly?
I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?
How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.
Why do Bad Things happen after installing Unslung 4.20 beta?
How can I get a working ipkg sub-system after upgrading it with the bad one which had been made available in the feed in May 2005?
Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-Beta or Linksys 2.3R29?
How to check your disk for errors (and repair them)
Why does my NSLU2 suddenly take so long (4 minutes or more) to reboot
How can I determine my installed Unslung version?
What is the Unslung version telling me?
How to correct that the Ready/Status LED won´t turn green and allow communication after upgrading with Unslung 5.5-Beta
How to determine that rootfs really exist on USB disk after unslinging\\

August 22, 2005, at 03:04 PM by tman --
Changed lines 500-501 from:

48. How to correct that the Ready/Status LED won´t turn green and allow communication after upgrading with BETA 5.5

to:

48. How to correct the problem with Ready/Status LED where it won´t turn green and allow communication after upgrading with BETA 5.5

Changed lines 504-505 from:

rm /.sd#1root <- # being a if you were unslung to disk 1 and b if you were unslung to disk 2 (disk 1 means /dev/sda1, storage media on port 1, disk 2 means /dev/sdb1, storage media on port 2).\\

to:

rm /.sd#1root <- # being a if you were unslung to disk 1 and b if you were unslung to disk 2 (disk 1 means /dev/sda1, storage media on port 1, disk 2 means /dev/sdb1, storage media on port 2).\\

Changed lines 508-509 from:

Re-format via web interface, if needed. If not formatting, then just /sbin/unsling disk#. If formatted, wait until formatting is

to:

Re-format via web interface, if needed. If not formatting, then just /sbin/unsling disk#. If formatted, wait until formatting is

Changed lines 522-523 from:

This is taken (with the command df)from a freshly unslung nslu2 with 10Gb usbdisk. If the size of rootfs (9512992) and / on /dev/sda1 (which is my usbdisk on port 1)reflects the size of your disk's data

to:

This is taken (with the command df) from a freshly unslung nslu2 with 10GB USB disk. If the size of rootfs (9512992) and / on /dev/sda1 (which is my usbdisk on port 1) reflects the size of your disk's data

Changed lines 526-528 from:

50. setting up cross_gdb for nslu2

to:

50. setting up cross_gdb for NSLU2

Changed lines 529-530 from:
     http://www.cs.cmu.edu/~gilpin/tutorial/
to:
 http://www.cs.cmu.edu/~gilpin/tutorial/
Changed lines 536-539 from:
     configure --target=armeb-linux --host=i686-linux

  make install will create later " armeb-linux-gdb " binary ,which is our cross_gdb
to:
 configure --target=armeb-linux --host=i686-linux
make install will create later " armeb-linux-gdb " binary ,which is our cross_gdb
Changed lines 544-546 from:
  (openslug)/tmp/cross/bin/armeb-linux-g++ -WALL -ggdb test.cpp -o test_nslu

 put test_nslu to ~user_nslu/
to:
 (openslug)/tmp/cross/bin/armeb-linux-g++ -WALL -ggdb test.cpp -o test_nslu
put test_nslu to ~user_nslu/
Changed lines 550-551 from:
   gdbserver knoppix_IP:5000 test_nslu 
to:
 gdbserver knoppix_IP:5000 test_nslu 
Changed lines 556-557 from:
 once in gdb connect to gdbserver nslu_IP using
to:
once in gdb connect to gdbserver nslu_IP using
August 22, 2005, at 02:16 AM by Bill Wallace --
Changed lines 215-216 from:

Solution: If you have a windows box, bring up a command line and type "ipcongig /all." Note the gateway and DNS server numbers. Go to the Linksys slug setup page ("Administration," then "LAN") and make sure you have entered the proper networks mask, gateway (usually the same IP as your router) AND DNS servers.

to:

Solution: If you have a windows box, bring up a command line and type "ipconfig /all." Note the gateway and DNS server numbers. Go to the Linksys slug setup page ("Administration," then "LAN") and make sure you have entered the proper network mask, gateway (usually the same IP as your router) AND DNS servers.

August 22, 2005, at 02:14 AM by Bill Wallace --
Added lines 215-216:

Solution: If you have a windows box, bring up a command line and type "ipcongig /all." Note the gateway and DNS server numbers. Go to the Linksys slug setup page ("Administration," then "LAN") and make sure you have entered the proper networks mask, gateway (usually the same IP as your router) AND DNS servers.

August 10, 2005, at 08:09 PM by sharth -- is '''not''' compiled it -> is '''not''' compiled in
Changed lines 155-156 from:
update: Recent (April 2005+) builds of OpenSlug come with the NTFS kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled it - so the mount is read-only.
to:
update: Recent (April 2005+) builds of OpenSlug come with the NTFS kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled in - so the mount is read-only.
August 09, 2005, at 12:35 PM by tman --
Added lines 61-62:


August 09, 2005, at 03:04 AM by rwhitby --
Changed lines 14-17 from:
to:
Changed lines 59-60 from:
to:
Changed lines 87-88 from:

5a. How do I completely backup my NSLU2?

to:

6. How do I completely backup my NSLU2?

Changed lines 110-111 from:

6. When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware), I cannot do XXX.

to:

7. When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware), I cannot do XXX.

Changed lines 114-115 from:

7. When I modify /etc/passwd, I still can't telnet into my box.

to:

8. When I modify /etc/passwd, I still can't telnet into my box.

Deleted lines 130-133:

8. Where is ftpd or other (standard linux) utilities?

The NSLU2 comes with a stripped down root filesystem. If what you need is in the original SnapGear sources, you can build it yourself easily. See HowTo Recipes for instructions. Or, you can download a binary image of a fairly complete root filesystem build from the NSLU2-Linux yahoo group (see romfs.tar.gz at http://groups.yahoo.com/group/nslu2-linux/files/ ). Then, simply install the utilities that you require.
Added lines 559-562:

51. (Obsolete) Where is ftpd or other (standard linux) utilities?

The NSLU2 comes with a stripped down root filesystem. If what you need is in the original SnapGear sources, you can build it yourself easily. See HowTo Recipes for instructions. Or, you can download a binary image of a fairly complete root filesystem build from the NSLU2-Linux yahoo group (see romfs.tar.gz at http://groups.yahoo.com/group/nslu2-linux/files/ ). Then, simply install the utilities that you require.
August 09, 2005, at 02:57 AM by rwhitby --
Changed lines 5-6 from:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). You can assist in this process - if your question is answered to your satisfaction, then the onus is on you to update the Wiki as "payment" for having your question answered.

to:

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Information or HowTo areas). It is *your* duty to assist in this process - if your question is answered to your satisfaction, then the onus is on *you* to update the Wiki as "payment" for having your question answered.

August 08, 2005, at 12:52 PM by rwhitby --
Changed lines 3-4 from:

If you have a question, then ask it on the mailing list (of course, you would ask Google, and also search this site and on the mailing list archives before actually posting a question, lest you look silly by asking something that can be easily found in the archives).

to:

If you have a question, then ask it on the mailing list (of course, you would ask Google, and also search this site and on the mailing list archives before actually posting a question, lest you look silly by asking something that can be easily found in the archives).

August 08, 2005, at 06:56 AM by nnhoan -- setting up cross gdb for nslu2
Changed lines 59-60 from:
to:
August 07, 2005, at 12:31 PM by nnhoan -- setting up cross gdb for nslu2
Changed lines 528-530 from:

'''50. setting up cross_gdb for nslu2

to:

50. setting up cross_gdb for nslu2

August 07, 2005, at 12:26 PM by nnhoan -- cross_gdb for nslu2
Added lines 527-562:

'''50. setting up cross_gdb for nslu2

1 a starter gdb tutorial for student:

     http://www.cs.cmu.edu/~gilpin/tutorial/

2 get gdbserver from ipkg-unbuild [openslug pkgs]gdb-6.3*ipk,put into nslu2/usr/bin

3 On host_knoppix compile from src gdb-6.3*tar.gz with

     configure --target=armeb-linux --host=i686-linux

  make install will create later " armeb-linux-gdb " binary ,which is our cross_gdb

4 install 'lesstif' then 'ddd' to get " datadisplay debugger GUI "

5 To start crosscompile test.cpp from 1 ,just using openslug_tool

  (openslug)/tmp/cross/bin/armeb-linux-g++ -WALL -ggdb test.cpp -o test_nslu

 put test_nslu to ~user_nslu/

6 nslu_side start from ssh_console (kind of telnet)

   gdbserver knoppix_IP:5000 test_nslu 

7 knoppix_side

   ddd --debugger /usr/local/bin/armeb-linux-gdb 

 once in gdb connect to gdbserver nslu_IP using

   (gdb)target remote nslu1_IP:5000

8 have fun

August 02, 2005, at 03:12 PM by caplink811 -- correted hd parameters
Changed lines 504-505 from:

rm /.sda#root <- # being 1 if you were unslung to disk 1 and 2 if you were unslung to disk 2.\\

to:

rm /.sd#1root <- # being a if you were unslung to disk 1 and b if you were unslung to disk 2 (disk 1 means /dev/sda1, storage media on port 1, disk 2 means /dev/sdb1, storage media on port 2).\\

August 01, 2005, at 10:38 PM by Mattias --
Changed line 57 from:
to:
Changed lines 500-501 from:

48. How to correct that the Ready/Status LED won´t turn green and allow communication

to:

48. How to correct that the Ready/Status LED won´t turn green and allow communication after upgrading with BETA 5.5

August 01, 2005, at 10:36 PM by Mattias --
Added line 501:
August 01, 2005, at 10:36 PM by Mattias --
Changed line 500 from:

48. How to correct that the Ready/Status LED won´t turn green and allow communication

to:

48. How to correct that the Ready/Status LED won´t turn green and allow communication\\

August 01, 2005, at 10:35 PM by Mattias --
Changed line 501 from:
Boot NSLU2 without HD attached.\\
to:

Boot NSLU2 without HD attached.\\

August 01, 2005, at 10:34 PM by Mattias --
Changed lines 501-502 from:
Boot NSLU2 without HD attached.

Telnet in with root/uNSLUng.

to:
Boot NSLU2 without HD attached.
Telnet in with root/uNSLUng.\\
Changed lines 504-507 from:

were unslung to disk 2. Reboot NSLU2 - again without HD attached. Telnet in with root/uNSLUng. Hotplug the hard drive.

to:

were unslung to disk 2.
Reboot NSLU2 - again without HD attached.
Telnet in with root/uNSLUng.
Plug in the usb disk.\\

Changed lines 510-512 from:

completed, then /sbin/unsling disk# in telnet session. Reboot with drive attached.

to:

completed, then /sbin/unsling disk# in telnet session.
Reboot with drive attached.

August 01, 2005, at 10:31 PM by Mattias --
Changed line 516 from:
||Filesystem||1k-blocks||Used||Available||Use%||Mounted on||
to:
Filesystem1k-blocksUsedAvailableUse%Mounted on
August 01, 2005, at 10:30 PM by Mattias --
Changed lines 516-522 from:
Filesystem 1k-blocks Used Available Use% Mounted on

rootfs 9656956 45856 9512992 0% / /dev/sda1 6528 5320 1208 81% /initrd /dev/sda1 9656956 45856 9512992 0% / /dev/sda1 9656956 45856 9512992 0% /share/hdd/data /dev/sda2 123955 4142 118533 3% /share/hdd/conf

to:
||Filesystem||1k-blocks||Used||Available||Use%||Mounted on||
rootfs96569564585695129920%/
/dev/sda165285320120881%/initrd
/dev/sda196569564585695129920%/
/dev/sda196569564585695129920%/share/hdd/data
/dev/sda212395541421185333%/share/hdd/conf
August 01, 2005, at 10:21 PM by Mattias --
Changed line 514 from:

How to determine that rootfs really exist on usbdisk after unslinging

to:

49. How to determine that rootfs really exist on usbdisk after unslinging

August 01, 2005, at 10:20 PM by Mattias --
Added line 513:
August 01, 2005, at 10:19 PM by Mattias --
Changed line 513 from:

faq49?How to determine that rootfs really exist on usbdisk after unslinging

to:

How to determine that rootfs really exist on usbdisk after unslinging

August 01, 2005, at 10:19 PM by Mattias --
Changed lines 512-523 from:

This should get you back to a booting NSLU2 with rootfs on hd

to:

This should get you back to a booting NSLU2 with rootfs on hd faq49?How to determine that rootfs really exist on usbdisk after unslinging

Filesystem 1k-blocks Used Available Use% Mounted on

rootfs 9656956 45856 9512992 0% / /dev/sda1 6528 5320 1208 81% /initrd /dev/sda1 9656956 45856 9512992 0% / /dev/sda1 9656956 45856 9512992 0% /share/hdd/data /dev/sda2 123955 4142 118533 3% /share/hdd/conf

This is taken (with the command df)from a freshly unslung nslu2 with 10Gb usbdisk. If the size of rootfs (9512992) and / on /dev/sda1 (which is my usbdisk on port 1)reflects the size of your disk's data partition (/share/hdd/data), then you are good.

August 01, 2005, at 10:11 PM by Mattias --
Added lines 498-512:

48. How to correct that the Ready/Status LED won´t turn green and allow communication

Boot NSLU2 without HD attached.

Telnet in with root/uNSLUng. rm /.sda#root <- # being 1 if you were unslung to disk 1 and 2 if you were unslung to disk 2. Reboot NSLU2 - again without HD attached. Telnet in with root/uNSLUng. Hotplug the hard drive. Re-format via web interface, if needed. If not formatting, then just /sbin/unsling disk#. If formatted, wait until formatting is completed, then /sbin/unsling disk# in telnet session. Reboot with drive attached.

This should get you back to a booting NSLU2 with rootfs on hd

July 31, 2005, at 04:14 PM by e7a -- how to determine and read version number
Changed lines 55-57 from:
to:
Added lines 490-497:

46. How can I determine my installed uNSLUng version?

cat /.unslung

47. What is the uNSLUng version telling me?

The first number is the Linksys version it is based on, the second is the actual uNSLUng version.
July 30, 2005, at 08:46 AM by rwhitby --
Changed line 52 from:
to:
Changed lines 449-450 from:

43. Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-beta?

to:

43. Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-beta or Linksys 2.3R29?

July 28, 2005, at 04:18 PM by JakobEriksson -- Update on running NTFS.sys
Changed lines 148-149 from:
This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. Short answer is still no.
to:
This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow.
July 24, 2005, at 04:15 PM by C751 -- Q36: use absolute path when creating new symlink
Changed lines 355-356 from:
rm /opt; ln -s /share/hdd/data/opt opt
to:
rm /opt; ln -s /share/hdd/data/opt /opt
July 22, 2005, at 04:10 PM by tom -- at least when using 5.5-beta
Changed line 476 from:

* Enable Telnet http://192.168.1.77/management/telnet.cgi

to:

* Enable Telnet http://192.168.1.77/Management/telnet.cgi

Changed line 487 from:
The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manually scan the disk – Using the instructions from FAQ Question #44
to:
The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manually scan the disk – Using the instructions from FAQ Question #44
July 21, 2005, at 05:15 AM by DougLourey --
Changed lines 474-484 from:

[- This is a test method to run Scandisk from the Web interface on

 * Boot the Slug without a disk
 * Enable Telnet http://192.168.1.77/management/telnet.cgi
 * Telnet using admin/admin
 * Connect the disk.  When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface
 * The drive activity light will illuminate while Scandisk proceeds.
 * When finished, Disk 1 Status will display Scandisk completed.
 * Disk Log will report that scandisk failed, contradicting the Web interface.
 * Scandisk appears to work, whereas the Disk Log appears to be in error
 * More on this later... -]
to:

This is a test method to run Scandisk from the Web interface * Boot the Slug without a disk * Enable Telnet http://192.168.1.77/management/telnet.cgi * Telnet using admin/admin * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface * The drive activity light will illuminate while Scandisk proceeds. * When finished, Disk 1 Status will display Scandisk completed. * Disk Log will report that scandisk failed, contradicting the Web interface. * Scandisk appears to work, whereas the Disk Log appears to be in error * More on this later...

July 21, 2005, at 05:13 AM by DougLourey --
Changed lines 482-484 from:
 * "Scandisk appears to work, whereas the Disk Log appears to be in error"
 * "More on this later..." -]
to:
 * Scandisk appears to work, whereas the Disk Log appears to be in error
 * More on this later... -]
July 21, 2005, at 05:08 AM by DougLourey --
Changed lines 474-484 from:

_> This is a test method to run Scandisk from the Web interface on _> * Boot the Slug without a disk _> * Enable Telnet http://192.168.1.77/management/telnet.cgi _> * Telnet using admin/admin _> * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface _> * The drive activity light will illuminate while Scandisk proceeds. _> * When finished, Disk 1 Status will display Scandisk completed. _> * Disk Log will report that scandisk failed, contradicting the Web interface. _> * "Scandisk appears to work, whereas the Disk Log appears to be in error" _> * "More on this later..."

to:

[- This is a test method to run Scandisk from the Web interface on

 * Boot the Slug without a disk
 * Enable Telnet http://192.168.1.77/management/telnet.cgi
 * Telnet using admin/admin
 * Connect the disk.  When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface
 * The drive activity light will illuminate while Scandisk proceeds.
 * When finished, Disk 1 Status will display Scandisk completed.
 * Disk Log will report that scandisk failed, contradicting the Web interface.
 * "Scandisk appears to work, whereas the Disk Log appears to be in error"
 * "More on this later..." -]
July 21, 2005, at 05:06 AM by DougLourey --
Changed lines 474-484 from:

.> This is a test method to run Scandisk from the Web interface on <. .> * Boot the Slug without a disk <. .> * Enable Telnet http://192.168.1.77/management/telnet.cgi <. .> * Telnet using admin/admin <. .> * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface <. .> * The drive activity light will illuminate while Scandisk proceeds. <. .> * When finished, Disk 1 Status will display Scandisk completed. <. .> * Disk Log will report that scandisk failed, contradicting the Web interface. <. .> * "Scandisk appears to work, whereas the Disk Log appears to be in error" <. .> * "More on this later..." <.

to:

_> This is a test method to run Scandisk from the Web interface on _> * Boot the Slug without a disk _> * Enable Telnet http://192.168.1.77/management/telnet.cgi _> * Telnet using admin/admin _> * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface _> * The drive activity light will illuminate while Scandisk proceeds. _> * When finished, Disk 1 Status will display Scandisk completed. _> * Disk Log will report that scandisk failed, contradicting the Web interface. _> * "Scandisk appears to work, whereas the Disk Log appears to be in error" _> * "More on this later..."

July 21, 2005, at 05:05 AM by DougLourey --
Changed lines 474-484 from:

.> This is a test method to run Scandisk from the Web interface on .> * Boot the Slug without a disk .> * Enable Telnet http://192.168.1.77/management/telnet.cgi .> * Telnet using admin/admin .> * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface .> * The drive activity light will illuminate while Scandisk proceeds. .> * When finished, Disk 1 Status will display Scandisk completed. .> * Disk Log will report that scandisk failed, contradicting the Web interface. .> * "Scandisk appears to work, whereas the Disk Log appears to be in error" .> * "More on this later..."

to:

.> This is a test method to run Scandisk from the Web interface on <. .> * Boot the Slug without a disk <. .> * Enable Telnet http://192.168.1.77/management/telnet.cgi <. .> * Telnet using admin/admin <. .> * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface <. .> * The drive activity light will illuminate while Scandisk proceeds. <. .> * When finished, Disk 1 Status will display Scandisk completed. <. .> * Disk Log will report that scandisk failed, contradicting the Web interface. <. .> * "Scandisk appears to work, whereas the Disk Log appears to be in error" <. .> * "More on this later..." <.

July 21, 2005, at 05:03 AM by DougLourey --
Changed lines 474-484 from:
to:

.> This is a test method to run Scandisk from the Web interface on .> * Boot the Slug without a disk .> * Enable Telnet http://192.168.1.77/management/telnet.cgi .> * Telnet using admin/admin .> * Connect the disk. When the drive is recognized, press ""Start/Stop Disk 1"" in the Web interface .> * The drive activity light will illuminate while Scandisk proceeds. .> * When finished, Disk 1 Status will display Scandisk completed. .> * Disk Log will report that scandisk failed, contradicting the Web interface. .> * "Scandisk appears to work, whereas the Disk Log appears to be in error" .> * "More on this later..."

July 17, 2005, at 08:32 PM by Michael Edholm -- Added command for unmounting drive in #44
Added line 463:
umount /dev/sda1
July 17, 2005, at 01:02 PM by tman --
Changed lines 476-477 from:

The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manually scan the disk – Using the instructions from FAQ Question# 44

to:
The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manually scan the disk – Using the instructions from FAQ Question #44
July 17, 2005, at 12:46 PM by Glenn Gerrard --
Changed lines 476-477 from:

The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manual scan the disk – Using the instructions from FAQ Question# 44

to:

The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manually scan the disk – Using the instructions from FAQ Question# 44

July 16, 2005, at 07:58 PM by Glenn Gerrard -- Why does my NSLU2 suddenly take so long (4 minutes or more) to reboot
Changed lines 54-55 from:
to:
Added lines 472-477:

45. Why does my NSLU2 suddenly take so long (4 minutes or more) to reboot

The OS keeps a record of how many reboots since the last fsck.ext3 of the disk. When the NSLU2 reboots from hard disk with the uNSLUng firmware it checks the state of the external disk. If you have passed the maximum number of reboots the system will do a “quick” check that takes about 4 minutes – This behaviour will continue until you manual scan the disk – Using the instructions from FAQ Question# 44

June 29, 2005, at 04:26 PM by Frans Meulenbroeks -- added a few newlines around item 44
Added line 455:
Added line 457:
Changed line 469 from:
WARNING: be sure to reboot your slug after doing this (to avoid that you accidently fill up the flash filesystem)
to:
WARNING: be sure to reboot your slug after doing this (to avoid that you accidently fill up the flash filesystem)
June 29, 2005, at 06:28 AM by Frans Meulenbroeks -- FAQ 44: layout changes, added warning
Changed lines 456-459 from:
Boot the slug without disk.
Connect the disk.
Through telnet unmount all drives.
The web interface still would not allow me to scan. The log said:
to:
  • Boot the slug without disk.
  • Connect the disk.
  • Through telnet unmount all drives.
  • The web interface still would not allow me to scan. The log said:
Changed lines 461-464 from:
However if you telnet to the device you can issue the command
/sbin/fsck.ext3 -f /dev/sda1
This will check the disk for you (assuming your drive is on /dev/sda1).
If you want to you can add the -y flag to the command. This will answer all questions with yes automatically (which is generally the best choice anyway).
to:
  • However if you telnet to the device you can issue the command
/sbin/fsck.ext3 -f /dev/sda1
  • This will check the disk for you (assuming your drive is on /dev/sda1).
If you want to you can add the -y flag to the command. This will answer all questions with yes automatically (which is generally the best choice anyway).
WARNING: be sure to reboot your slug after doing this (to avoid that you accidently fill up the flash filesystem)
June 28, 2005, at 07:42 PM by Frans Meulenbroeks -- added entry 44: How to check your disk for errors (and repair them)
Changed lines 53-54 from:
to:
Added lines 454-464:

44. How to check your disk for errors (and repair them)

Boot the slug without disk.
Connect the disk.
Through telnet unmount all drives.
The web interface still would not allow me to scan. The log said:
"Warning: Out of disk space, scandisk cannot proceed."
However if you telnet to the device you can issue the command
/sbin/fsck.ext3 -f /dev/sda1
This will check the disk for you (assuming your drive is on /dev/sda1).
If you want to you can add the -y flag to the command. This will answer all questions with yes automatically (which is generally the best choice anyway).
June 22, 2005, at 04:46 PM by tman --
Changed lines 192-193 from:
Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
to:
Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
Changed lines 199-202 from:
Router IP - 192.168.1.1 <http://192.168.1.1>
Subnet 255.255.255.0 <http://255.255.255.0>
Slug IP: 192.168.1.77 <http://192.168.1.77>
Subnet 255.255.255.0 <http://255.255.255.0>
to:
Router IP - 192.168.1.1 <http://192.168.1.1>
Subnet 255.255.255.0 <http://255.255.255.0>
Slug IP: 192.168.1.77 <http://192.168.1.77>
Subnet 255.255.255.0 <http://255.255.255.0>
June 21, 2005, at 01:58 AM by tman --
Added line 381:
Changed lines 385-388 from:
The Linksys documentation specifically says: do not plug a USB flash memory key into the "Disk 1" port. You are instructed by Linksys to plug it into the "Disk 2/Flash" port. The Unslung doco however indicates you should format the hard disk (your USB flash memory key) before you do the firmware upgrade and validate its functionality. You plug the USB flash memory key into the "Disk 1" port as recommended and find you can't format it with the Linksys firmware. Now what?
It has to be formatted later using the Unslung firmware. Follow all the Unslung steps as documented and at this step format the USB flash memory key. It should be plugged into the "Disk 1" port and will now be succesfully formatted:
to:
The Linksys documentation specifically says: do not plug a USB flash memory key into the "Disk 1" port. You are instructed by Linksys to plug it into the "Disk 2/Flash" port. The Unslung doco however indicates you should format the hard disk (your USB flash memory key) before you do the firmware upgrade and validate its functionality. You plug the USB flash memory key into the "Disk 1" port as recommended and find you can't format it with the Linksys firmware. Now what?
It has to be formatted later using the Unslung firmware. Follow all the Unslung steps as documented and at this step format the USB flash memory key. It should be plugged into the "Disk 1" port and will now be succesfully formatted:
Added line 396:
Changed lines 401-403 from:
  • Disk 1 ---> /share/hdd/.. (your USB flash memory key)
  • Disk 2/Flash ---> /share/flash/.. (nothing attached)
to:
Disk 1 ---> /share/hdd/.. (your USB flash memory key)
Disk 2/Flash ---> /share/flash/.. (nothing attached)
Changed lines 411-414 from:
  • Linksys treats 10GB or larger as disks (ext3) and less than 10GB as flash (VFAT). They only allow flash on disk2. The Unslung firmware treats 1GB or larger as disk (ext3), and less than 1GB as flash (VFAT), unless the flash is on disk1, in which case it is treated as a very small ext3 disk.
  • 256MB is the minimum (due to the way that the Linksys software partitions it). Whether or not you need larger depends on how many packages you are going to load.
to:
Linksys treats 10GB or larger as disks (ext3) and less than 10GB as flash (VFAT). They only allow flash on disk2. The Unslung firmware treats 1GB or larger as disk (ext3), and less than 1GB as flash (VFAT), unless the flash is on disk1, in which case it is treated as a very small ext3 disk.
256MB is the minimum (due to the way that the Linksys software partitions it). Whether or not you need larger depends on how many packages you are going to load.
Changed lines 417-436 from:

What happened for me was that I was getting inconsistent behaviour after installing Unslung 4.20 beta, which now I am fairly sure was simply that the unslinging had worked, but I had failed to put the device out of maintenance mode after doing the upgrade to 4.20. This meant that everything I tried was filling up device memory, with confusing results (not always recognizing the disk after reboot, some packages install, others do not, etc). The key point was that after unslinging and rebooting I was still seeing this from df:

Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 6528 5292 1236 81% /
...

Whereas when it works I see this:

Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 192117464 8068452 182097196 4% /
...

with a 160 GB disk, with some data already copied onto it.

(I had previously failed to setup a 1 GB USB flash disk as the primary disk, but now suspect that the problem was the same in both cases).

Eventually the slug refused to boot at all, but the RedBoot rescue method using HTTP worked fine for me, and from that point everything worked properly - presumably because this method of re-flashing does not leave the device in maintenance mode.

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

to:
What happened for me was that I was getting inconsistent behaviour after installing Unslung 4.20 beta, which now I am fairly sure was simply that the unslinging had worked, but I had failed to put the device out of maintenance mode after doing the upgrade to 4.20. This meant that everything I tried was filling up device memory, with confusing results (not always recognizing the disk after reboot, some packages install, others do not, etc). The key point was that after unslinging and rebooting I was still seeing this from df:
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 6528 5292 1236 81% /
...
Whereas when it works I see this:
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 192117464 8068452 182097196 4% /
...
with a 160 GB disk, with some data already copied onto it.
(I had previously failed to setup a 1 GB USB flash disk as the primary disk, but now suspect that the problem was the same in both cases).
Eventually the slug refused to boot at all, but the RedBoot rescue method using HTTP worked fine for me, and from that point everything worked properly - presumably because this method of re-flashing does not leave the device in maintenance mode.
Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.
Changed lines 439-441 from:

Between Tue May 17 16:27:00 2005 UTC and Thu May 19 22:51:19 2005 UTC (maybe a bit more due to lag time for cleaning the feeds), a bad ipkg package (named 'ipkg_0.99.148-number_armeb.ipk' where number can be from 1 to 4) had been made available in the unslung optware feeds.

A step by step procedure to restore the original ipkg sub-system has been published in the wiki HowTo.\\

to:
Between Tue May 17 16:27:00 2005 UTC and Thu May 19 22:51:19 2005 UTC (maybe a bit more due to lag time for cleaning the feeds), a bad ipkg package (named 'ipkg_0.99.148-number_armeb.ipk' where number can be from 1 to 4) had been made available in the unslung optware feeds.
A step by step procedure to restore the original ipkg sub-system has been published in the wiki HowTo.\\
Changed lines 444-445 from:

The current version works and does not need to be changed. If upgraded ipkg before or after those dates then there is no need to change anything.

to:
The current version works and does not need to be changed. If upgraded ipkg before or after those dates then there is no need to change anything.
Changed lines 448-450 from:

There exists a bug in Linksys V2.3R29 software (which Unslung 5.5 is based on) that causes Disk 2/Flash to show the following on the web page:

  Disk 2/Flash:         Ready, 0MB (0% Free)

Using df from a telnet session will show the correct disk usage. We do not have the code for this part of the firmware so it will have to be fixed by Linksys.\\

to:
There exists a bug in Linksys V2.3R29 software (which Unslung 5.5 is based on) that causes Disk 2/Flash to show the following on the web page:
Disk 2/Flash: Ready, 0MB (0% Free)
Using df from a telnet session will show the correct disk usage. We do not have the code for this part of the firmware so it will have to be fixed by Linksys.\\
June 20, 2005, at 11:32 PM by gsherwood -- Added FAQ 43.
Changed lines 52-53 from:
to:
Added lines 443-448:

43. Why does my Disk2/Flash show 0MB Free after installing Unslung 5.5-beta?

There exists a bug in Linksys V2.3R29 software (which Unslung 5.5 is based on) that causes Disk 2/Flash to show the following on the web page:

  Disk 2/Flash:         Ready, 0MB (0% Free)

Using df from a telnet session will show the correct disk usage. We do not have the code for this part of the firmware so it will have to be fixed by Linksys.\\

June 19, 2005, at 09:55 PM by tman -- Changed R29 references.
Changed lines 51-52 from:
to:
Changed lines 56-57 from:
Probably Unslung 3.18-beta - see HowToGetInvolved? for details. Note that the Unslung firmware is based on Linksys 2.3R25 firmware currently. We will switch over to 2.3R29 soon.
to:
Unslung 5.5-beta - see HowToGetInvolved? for details.
Deleted line 204:
Changed lines 264-265 from:
The GPL sources for the R29 firmware has been published at the Linksys GPL Code Center. We will move over to R29 soon. More details about R29 are at LinksysR29. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
to:
Unslung 5.x uses R29. The GPL sources for the R29 firmware has been published at the Linksys GPL Code Center. More details about R29 are at LinksysR29. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
Changed lines 271-272 from:
Disabling UPnP helped for me. I have a DLINK DI-624 router.
to:
Disabling UPnP helped for me. I have a D-Link DI-624 router.
June 19, 2005, at 09:52 PM by tman --
Changed lines 3-4 from:

If you have a question, then ask it on the mailing list (of course, you would ask Google, and also search this site and on the mailing list archives before actually posting a question, lest you look silly by asking something that can be easily found in the archives).

to:

If you have a question, then ask it on the mailing list (of course, you would ask Google, and also search this site and on the mailing list archives before actually posting a question, lest you look silly by asking something that can be easily found in the archives).

Changed lines 434-437 from:

42. How can I get a working ipkg sub-system after upgrading it with the bad one which have been made available in the feed during may 2005?

Between Tue May 17 16:27:00 2005 UTC and Thu May 19 22:51:19 2005 UTC (maybe a bit more due to lag time for cleaning the feeds), a bad ipkg package (named 'ipkg_0.99.148-number_armeb.ipk' where number can be from 1 to 4) has been made available in the uslung optware feeds.

to:

42. How can I get a working ipkg sub-system after upgrading it with the bad one which had been made available in the feed during May 2005?

Between Tue May 17 16:27:00 2005 UTC and Thu May 19 22:51:19 2005 UTC (maybe a bit more due to lag time for cleaning the feeds), a bad ipkg package (named 'ipkg_0.99.148-number_armeb.ipk' where number can be from 1 to 4) had been made available in the unslung optware feeds.

Added lines 440-441:

The current version works and does not need to be changed. If upgraded ipkg before or after those dates then there is no need to change anything.

June 19, 2005, at 09:50 PM by tman --
Changed line 169 from:
  • Use the OpenEmbedded environment to create your kernel and configure modules there
to:
  • Use the OpenEmbedded environment to create your kernel and configure modules there
Changed lines 178-179 from:
Yes! See NativeNSLU2Toolchain to set up a development environment on your Unslung NSLU2, and see BuildGNUMakeOnYourNSLU2Box, MakeGNUGawkOnYourNSLU2Box, and MakeThttpdOnYourNSLU2Box for examples of doing this.
to:
Yes! See NativeNSLU2Toolchain to set up a development environment on your Unslung NSLU2, and see BuildGNUMakeOnYourNSLU2Box, MakeGNUGawkOnYourNSLU2Box, and MakeThttpdOnYourNSLU2Box for examples of doing this.
Changed lines 182-183 from:
peecock41 figured out what it means when the NSLU2 beeps every 8 hours.
to:
peecock41 figured out what it means when the NSLU2 beeps every 8 hours.
Changed lines 190-191 from:
Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
to:
Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
Deleted line 217:
Changed lines 224-225 from:
For Maxtor OneTouch drives see the Maxtor OneTouch HOWTO.
to:
For Maxtor OneTouch drives see the Maxtor OneTouch HOWTO.
Changed lines 236-237 from:
See http://www.nslu2-linux.org/wiki/HowTo/FixTheDriveBackupForUnslungFirmware
to:
Changed line 270 from:
I had to disable UPnP to get my NSLU2 to work properly. I have a DLINK DI-524 router.
to:
I had to disable UPnP to get my NSLU2 to work properly. I have a D-Link DI-524 router.
Changed lines 337-338 from:
If you have no interest in quotas, you might want to disable them by creating a DiversionScript. Placing this content in /unslung/rc.quota should do the trick:
to:
If you have no interest in quotas, you might want to disable them by creating a DiversionScript. Placing this content in /unslung/rc.quota should do the trick:
Changed lines 387-392 from:
"4) Identify which drive you wish you "unsling", and plug it in. Wait a minute or two while the disk is mounted.
- If the disk has not been previously formatted on the NSLU2, then now is
the time to do that. Make sure that the drive is recognized in the
web interface."
to:
"4) Identify which drive you wish you "unsling", and plug it in. Wait a minute or two while the disk is mounted.
If the disk has not been previously formatted on the NSLU2, then now is the time to do that. Make sure that the drive is recognized in the web interface."
Changed lines 432-433 from:

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

to:

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

Changed line 439 from:

See RestoreWorkingIpkgFromJffs2

to:
June 09, 2005, at 04:32 AM by Craig -- Added default DNS settings step to FAQ 21
Changed lines 192-193 from:
Reason: DNS is unreachable.
to:
These errors can be cause by two things. 1) DNS is unreachable and 2) you have an http proxy.
Simple solution: It is easy to miss a DNS setting. Revert network and slug to default settings. If you overlooked a DNS setting previously reverting to defaults may eliminate the problem.
Default settings should be as follows.
Router IP - 192.168.1.1 <http://192.168.1.1>
Subnet 255.255.255.0 <http://255.255.255.0>
Slug IP: 192.168.1.77 <http://192.168.1.77>
Subnet 255.255.255.0 <http://255.255.255.0>
Default port 80
If these settings do not make a difference consider the following file edits.
DNS is unreachable.
Changed lines 210-211 from:
Reason2: You have an http proxy.
to:
You have an http proxy.
Added line 218:
June 08, 2005, at 03:15 PM by jf --
Added line 51:
Changed lines 420-427 from:

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

to:

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

42. How can I get a working ipkg sub-system after upgrading it with the bad one which have been made available in the feed during may 2005?

Between Tue May 17 16:27:00 2005 UTC and Thu May 19 22:51:19 2005 UTC (maybe a bit more due to lag time for cleaning the feeds), a bad ipkg package (named 'ipkg_0.99.148-number_armeb.ipk' where number can be from 1 to 4) has been made available in the uslung optware feeds.

A step by step procedure to restore the original ipkg sub-system has been published in the wiki HowTo.
See RestoreWorkingIpkgFromJffs2

June 05, 2005, at 01:37 PM by g2 -- Add 5a Completely backup
Added line 14:
Added lines 78-100:

5a. How do I completely backup my NSLU2?

There are several parts to this answer. First get root access as noted above for the stock Linksys or other places for Unslung or Openslug. Next you will need to backup all the partitions from the flash and the hard driver/flash stick. A recommendation is to backup the flash onto the hard drive/flash stick first, then when one backs up the hard drive/flash stick (HD/FS) you'll have both.
At the root prompt, type "dmesg" to get a printout of the console of the kernel messages during boot. Search in there for something like the following:
Searching for RedBoot partition table in IXP4XX-Flash0 at offset 0x7e0000
6 RedBoot partitions found on MTD device IXP4XX-Flash0
Creating 6 MTD partitions on "IXP4XX-Flash0":
0x00000000-0x00040000 : "RedBoot" ....
This lets you know there are 6 partitions in the flash. N.B. BE VERY CAREFUL with the following commands. A mistyped or bad command can literally erase or hose up you're entire system. USE AT YOUR OWN RISK. First, MAKE SURE your current working directory is on the HD/FS. Then for each of the partitions do some similar to the following:
dd if=/dev/mtdblock0 of=redboot.bin
dd if=/dev/mtdblock1 of=sysconf.bin
dd if=/dev/mtdblock2 of=kernel.bin
Continue this all the way through mtdblock5 or how many partitions one has. Note: Since we started at 0, the mtdblock number will be 1 less than the total number.
Note: the block number start with 0. This provides you with a binary copy of the contents of the individual paritions in flash. Next, you will need to properly shutdown and power off the NSLU2 to backup the contents of the HD/FS. This is most easily performed on another system. I'd recommend getting a copy of ubuntu or knoppix and running from the livecd if you don't have access to Linux/Unix system.
On that Linux/Unix system, one needs to plug in the NSLU2 hard drive/flash stick, I'd suggest mounting the partitions read only, and tar up the partitions and save off a copy of the MBR (master boot record -- this contains the partition table on the disk itself). With this data, an indentical type disk could be restored. Other disks could be restored which are larger also. When done shutdown properly and reattach the HD/FS to the NSLU2.
Finally, as long as Redboot isn't toasted, you can reload and restore the flash partitions. If Redboot is toasted, then you'd need to do hw modifications to get JTAG access to restore Redboot or another boot loader to the flash and then be able to restore everything.
June 04, 2005, at 09:19 PM by ov2k -- Update Hitachi Feature Tool link (for new version)
Changed lines 181-182 from:
You can download the Power Booster utility at http://www.hitachigst.com/downloads/pbinstall.exe for 2.5" IBM/Hitachi TravelStar disks. The Power Booster utility will enable the auto spin down feature of the disk. For 3.5" IBM/Hitachi drives (and maybe others), you can download the Feature Tool at http://www.hitachigst.com/downloads/featuretool_v195.exe. Otherwise temporarily install the IDE disk in your ordinary Linux box, read the disk technical documentation and use hdparm to adjust the settings by hand. The trick is to enable APM within the drive itself, so Linux doesn't have to care about it at all. You can't use hdparm to alter the APM settings from the NSLU2 as the USB->IDE adapters are emulated as SCSI host adapters in the Linux kernel which is incompatible with the necessary hdparm options.
to:
You can download the Power Booster utility at http://www.hitachigst.com/downloads/pbinstall.exe for 2.5" IBM/Hitachi TravelStar disks. The Power Booster utility will enable the auto spin down feature of the disk. For 3.5" IBM/Hitachi drives (and maybe others), you can download the Feature Tool at http://www.hitachigst.com/hdd/support/download.htm. Otherwise temporarily install the IDE disk in your ordinary Linux box, read the disk technical documentation and use hdparm to adjust the settings by hand. The trick is to enable APM within the drive itself, so Linux doesn't have to care about it at all. You can't use hdparm to alter the APM settings from the NSLU2 as the USB->IDE adapters are emulated as SCSI host adapters in the Linux kernel which is incompatible with the necessary hdparm options.
June 04, 2005, at 03:15 PM by Joe User --
Changed line 395 from:

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual)

to:

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual) If you see the above behavior from df, check to make sure your drive is set to always-on/manual.

June 04, 2005, at 03:13 PM by Joe User -- Added note about auto power-on drives
Changed lines 393-395 from:

Eventually the slug refused to boot at all, but the RedBoot rescue method using HTTP worked fine for me, and from that point everything worked properly - presumably because this method of re-flashing does not leave the device in maintenance mode.

to:

Eventually the slug refused to boot at all, but the RedBoot rescue method using HTTP worked fine for me, and from that point everything worked properly - presumably because this method of re-flashing does not leave the device in maintenance mode.

Addition: Some drives are not detected if they are set to automatic power on at boot time. (For example the Buffalo DriveStation can be set to Manual or Auto. To work with 4.20 it must be set to Manual)

June 01, 2005, at 03:51 PM by jp30 -- remove misleading nsswitch.conf advice from the apache answer
Changed line 250 from:
4. Create a file called /etc/nsswitch.conf which contains this line:\\
to:
4. Restart your NSLU2 or restart the Apache server by typing this line:\\
Deleted lines 251-254:

hosts: files dns

5. Restart your NSLU2 or restart the Apache server by typing this line:
\\
May 26, 2005, at 07:49 AM by Stefan Hauser --
Changed line 144 from:
  • Use the OpenEmbedded environment to create your kernel and configure modules there
to:
  • Use the OpenEmbedded environment to create your kernel and configure modules there
May 23, 2005, at 12:11 PM by rfolwell -- Why do Bad Things happen after installing Unslung 4.20 beta?
Added line 49:
Added lines 378-397:

41. Why do Bad Things happen after installing Unslung 4.20 beta?

What happened for me was that I was getting inconsistent behaviour after installing Unslung 4.20 beta, which now I am fairly sure was simply that the unslinging had worked, but I had failed to put the device out of maintenance mode after doing the upgrade to 4.20. This meant that everything I tried was filling up device memory, with confusing results (not always recognizing the disk after reboot, some packages install, others do not, etc). The key point was that after unslinging and rebooting I was still seeing this from df:

Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 6528 5292 1236 81% /
...

Whereas when it works I see this:

Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 192117464 8068452 182097196 4% /
...

with a 160 GB disk, with some data already copied onto it.

(I had previously failed to setup a 1 GB USB flash disk as the primary disk, but now suspect that the problem was the same in both cases).

Eventually the slug refused to boot at all, but the RedBoot rescue method using HTTP worked fine for me, and from that point everything worked properly - presumably because this method of re-flashing does not leave the device in maintenance mode.

May 15, 2005, at 04:20 PM by tman --
Changed line 11 from:
to:
Changed lines 58-59 from:

3. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI,IDE,USB,ETC..), using Microsoft Windows?

to:

3. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI, IDE, USB, etc...), using Microsoft Windows?

Changed lines 339-340 from:
You probably have the slug hooked up to a 10Mbps network. Hook it up to a 100Mbps network and you are back in business. This has to do with the ethernet connection on the slug loosing packets when connected to a 10Mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
to:
You probably have the slug hooked up to a 10Mbps network. Hook it up to a 100Mbps network and you are back in business. This has to do with the ethernet connection on the slug losing packets when connected to a 10Mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
Changed lines 360-361 from:
1) The USB flash memory key must be 256 GB or bigger.
to:
1) The USB flash memory key must be 256MB or bigger.
Changed lines 370-371 from:
3) This FAQ refers to 3.x unslung software
to:
3) This FAQ refers to 3.x Unslung software
Changed lines 374-375 from:
  • Linksys treats 10Gb or larger as disks (ext3) and less than 10Gb as flash (vfat). They only allow flash on disk2. The Unslung firmware treats 1Gb or larger as disk (ext3), and less than 1Gb as flash (vfat), unless the flash is on disk1, in which case it is treated as a very small ext3 disk.
to:
  • Linksys treats 10GB or larger as disks (ext3) and less than 10GB as flash (VFAT). They only allow flash on disk2. The Unslung firmware treats 1GB or larger as disk (ext3), and less than 1GB as flash (VFAT), unless the flash is on disk1, in which case it is treated as a very small ext3 disk.
Deleted lines 376-377:
May 15, 2005, at 08:45 AM by JP --
Changed lines 48-49 from:

40. [[#faq40|How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.

to:
May 15, 2005, at 08:39 AM by JP --
Changed lines 48-49 from:
to:

40. [[#faq40|How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.

Added lines 340-378:

40. How can I use the slug with just a USB flash memory key - I don't want to attach a hard disk.

The slug has two USB ports marked as:
Disk 1
Disk 2/Flash
The Linksys documentation specifically says: do not plug a USB flash memory key into the "Disk 1" port. You are instructed by Linksys to plug it into the "Disk 2/Flash" port. The Unslung doco however indicates you should format the hard disk (your USB flash memory key) before you do the firmware upgrade and validate its functionality. You plug the USB flash memory key into the "Disk 1" port as recommended and find you can't format it with the Linksys firmware. Now what?
It has to be formatted later using the Unslung firmware. Follow all the Unslung steps as documented and at this step format the USB flash memory key. It should be plugged into the "Disk 1" port and will now be succesfully formatted:
"4) Identify which drive you wish you "unsling", and plug it in. Wait a minute or two while the disk is mounted.
- If the disk has not been previously formatted on the NSLU2, then now is
the time to do that. Make sure that the drive is recognized in the
web interface."
The web interface is a bit vague about whether it has performed a successful format, so give it a minute or so, switch to the Home page and then return to the "Administration-->Disk" page to refresh it. It should now show "Disk 1 Status as "Formatted" and "Disk 2 Status as "Not Installed".
Notes:
1) The USB flash memory key must be 256 GB or bigger.
2) Once you are up and running the ports are mapped to these two directories:
  • Disk 1 ---> /share/hdd/.. (your USB flash memory key)
  • Disk 2/Flash ---> /share/flash/.. (nothing attached)
This is confusing as you are now using a USB flash memory key for the hard disk -> ie /share/hdd/..
but /share/flash/.. is unused.
3) This FAQ refers to 3.x unslung software
4) Background info credited to Rod Whitby:
  • Linksys treats 10Gb or larger as disks (ext3) and less than 10Gb as flash (vfat). They only allow flash on disk2. The Unslung firmware treats 1Gb or larger as disk (ext3), and less than 1Gb as flash (vfat), unless the flash is on disk1, in which case it is treated as a very small ext3 disk.
  • 256MB is the minimum (due to the way that the Linksys software partitions it). Whether or not you need larger depends on how many packages you are going to load.
May 15, 2005, at 07:18 AM by JP --
Changed lines 13-14 from:
to:
Changed lines 68-69 from:

5. What is the root password on an unmodified NSLU2 with stock firmware (version xx).

to:

5. What is the root password on an unmodified NSLU2 with stock Linksys firmware (version xx).

Changed lines 76-77 from:

6. When I boot the NSLU2 with a USB flash drive (with the stock firmware), I cannot do XXX.

to:

6. When I boot the NSLU2 with a USB flash drive (with the stock Linksys firmware), I cannot do XXX.

May 13, 2005, at 11:26 AM by roel --
Changed lines 56-57 from:
OK, here's the deal. If you flash the Unslung firmware with NO disks attached (as you should), and THEN enable telnet through the web interface (STILL with NO disks attached, as explained in the README) and then telnet to the IP address of the NSLU2 (STILL with NO disks attached, and telneting to Linux, NOT to RedBoot), you will be able to log in as "root" with the password "uNSLUng" (as long as there are STILL NO disks attached). BUT, as soon as you plug a disk in, the password will CHANGE to whatever password is stored (in MULTIPLE places) on the disk. And this other password (which you probably don't know, and neither do we) may even PERSIST after you unplug the disk (as it may have been automatically copied into the root filesystem which is now in the internal flash in Unslung 3.x). So you either need to change that root password (using the ChangePasswordsFromTheCommandLine instructions because simply editing the /etc/passwd file is NOT enough to make it stick) AND follow the instructions in DiversionScripts to permanently enable telnet, OR install and configure the dropbear or openssh package.
to:
OK, here's the deal. If you flash the Unslung firmware with NO disks attached (as you should), and THEN enable telnet through the web interface (STILL with NO disks attached, as explained in the README) and then telnet to the IP address of the NSLU2 (STILL with NO disks attached, and telneting to Linux, NOT to RedBoot), you will be able to log in as "root" with the password "uNSLUng" (as long as there are STILL NO disks attached). BUT, as soon as you plug a disk in, the password will CHANGE to whatever password is stored (in MULTIPLE places) on the disk. And this other password (which you probably don't know, and neither do we) may even PERSIST after you unplug the disk (as it may have been automatically copied into the root filesystem which is now in the internal flash in Unslung 3.x). So you either need to change that root password (using the ChangePasswordsFromTheCommandLine instructions because simply editing the /etc/passwd file is NOT enough to make it stick, see also FAQ nr 7) AND follow the instructions in DiversionScripts to permanently enable telnet, OR install and configure the dropbear or openssh package.
May 05, 2005, at 06:07 PM by tman --
Changed lines 184-185 from:
For Maxtor OneTouch drives see the Maxtor OneTouch HOWTO.
to:
For Maxtor OneTouch drives see the Maxtor OneTouch HOWTO.
May 05, 2005, at 12:43 PM by tman -- Added TOC
Changed lines 7-8 from:

0. Which firmware should I use first?

to:

Contents

1. Which firmware should I use first?
2. I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?
3. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI,IDE,USB,ETC..), using Microsoft Windows?
4. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory"
5. What is the root password on an unmodified NSLU2 with stock firmware (version xx)
6. When I boot the NSLU2 with a USB flash drive (with the stock firmware), I cannot do XXX.
7. When I modify /etc/passwd, I still can't telnet into my box
8. Where is ftpd or other (standard linux) utilities?
9. Can I use the built-in thttpd for my web-server?
10. My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?
11. Can I setup the NSLU2 to use NTFS partitions?
12. Can I use RAID?
13. Which SSH daemon should I use ?
14. Can I boot the NSLU2 with a USB device as the root filesystem?
15. Can I use a USB hub so that I can add more than two external hard drives?
16. I need to build more kernel modules, where are the kernel sources for the NSLU2?
17. What is the ixp1 interface, and can it be used for anything useful?
18. Can I write and compile code directly on the NSLU2?
19. Why does my NSLU2 beep every eight hours?
20. When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information"
21. ipkg update doesn't work?
22. How do I spin down my USB hard disks?
23. After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore
24. What is the difference between a "soft-float" and "hard-float" compiler?
25. Are there any differences between the NSLU2 and the NSLU2UK?
26. When I first apply power to the NSLU2, it is off. How do I fix that?
27. Why are you still using R25 firmware? R29 is out.
28. The NSLU drops connections all the time, even the web interface times out.
29. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected
30. How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible
31. How do I install Apache?
32. How can I recover a bad conf parition when the web interface says my HD is "not formatted"?
33. How can I restore samba on NSLU2 if it is no longer working?
34. Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?
35. Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all the files in the root file system are very old?
36. What can I do if sda2 (/share/hdd/conf) is getting full and i cant install ipkg packages anymore?
37. What's the default password for Openslug?
38. Why do pages on this wiki not format correctly?
39. I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?

1. Which firmware should I use first?

Changed lines 54-55 from:

1. I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?

to:

2. I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?

Changed lines 58-59 from:

2. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI,IDE,USB,ETC..), using Microsoft Windows?

to:

3. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI,IDE,USB,ETC..), using Microsoft Windows?

Changed lines 62-63 from:

3. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

to:

4. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

Changed lines 68-69 from:

4. What is the root password on an unmodified NSLU2 with stock firmware (version xx).

to:

5. What is the root password on an unmodified NSLU2 with stock firmware (version xx).

Changed lines 76-77 from:

5. When I boot the NSLU2 with a USB flash drive (with the stock firmware), I cannot do XXX.

to:

6. When I boot the NSLU2 with a USB flash drive (with the stock firmware), I cannot do XXX.

Changed lines 80-81 from:

6. When I modify /etc/passwd, I still can't telnet into my box.

to:

7. When I modify /etc/passwd, I still can't telnet into my box.

Changed lines 97-98 from:

7. Where is ftpd or other (standard linux) utilities?

to:

8. Where is ftpd or other (standard linux) utilities?

Changed lines 101-102 from:

8. Can I use the built-in thttpd for my web-server?

to:

9. Can I use the built-in thttpd for my web-server?

Changed lines 105-106 from:

9. My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?

to:

10. My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?

Changed lines 109-110 from:

10. Q: Can I setup the NSLU2 to use NTFS partitions?

to:

11. Can I setup the NSLU2 to use NTFS partitions?

Changed lines 125-126 from:

11. Can I use RAID?

to:

12. Can I use RAID?

Changed lines 129-130 from:

12. Which SSH daemon should I use ?

to:

13. Which SSH daemon should I use ?

Changed lines 133-134 from:

13. Can I boot the NSLU2 with a USB device as the root filesystem?

to:

14. Can I boot the NSLU2 with a USB device as the root filesystem?

Changed lines 137-138 from:

14. Can I use a USB hub so that I can add more than two external hard drives?

to:

15. Can I use a USB hub so that I can add more than two external hard drives?

Changed lines 141-142 from:

15. I need to build more kernel modules, where are the kernel sources for the NSLU2?

to:

16. I need to build more kernel modules, where are the kernel sources for the NSLU2?

Changed lines 146-147 from:

16. What is the ixp1 interface, and can it be used for anything useful?

to:

17. What is the ixp1 interface, and can it be used for anything useful?

Changed lines 150-151 from:

17. Can I write and compile code directly on the NSLU2?

to:

18. Can I write and compile code directly on the NSLU2?

Changed lines 154-155 from:

18. Why does my NSLU2 beep every eight hours?

to:

19. Why does my NSLU2 beep every eight hours?

Changed lines 158-159 from:

19. When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information".

to:

20. When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information".

Changed lines 162-163 from:

20. ipkg update doesn't work

to:

21. ipkg update doesn't work

Changed lines 178-180 from:

21. How do I spin down my USB hard disks?

to:

22. How do I spin down my USB hard disks?

Changed lines 192-193 from:

22. After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore

to:

23. After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore

Changed lines 198-199 from:

23. What is the difference between a "soft-float" and "hard-float" compiler?

to:

24. What is the difference between a "soft-float" and "hard-float" compiler?

Changed lines 214-215 from:

24. Are there any differences between the NSLU2 and the NSLU2UK?

to:

25. Are there any differences between the NSLU2 and the NSLU2UK?

Changed lines 218-219 from:

25. When I first apply power to the NSLU2, it is off. How do I fix that?

to:

26. When I first apply power to the NSLU2, it is off. How do I fix that?

Changed lines 222-223 from:

26. Why are you still using R25 firmware? R29 is out.

to:

27. Why are you still using R25 firmware? R29 is out.

Changed lines 226-227 from:

27. The NSLU drops connections all the time, even the web interface times out.

to:

28. The NSLU drops connections all the time, even the web interface times out.

Changed lines 233-234 from:

28. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected.

to:

29. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected.

Changed lines 237-238 from:

29. How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible.

to:

30. How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible.

Changed lines 241-242 from:

30. How do I install Apache?

to:

31. How do I install Apache?

Changed lines 267-268 from:

31. How can I recover a bad conf parition when the web interface says my HD is "not formatted" ?

to:

32. How can I recover a bad conf parition when the web interface says my HD is "not formatted" ?

Changed lines 282-284 from:

32. How can I restore samba on NSLU2 if it is no longer working?

to:

33. How can I restore samba on NSLU2 if it is no longer working?

Changed lines 295-296 from:

33. Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?

to:

34. Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?

Changed lines 306-307 from:

34. Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all the files in the root file system are very old?

to:

35. Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all the files in the root file system are very old?

Changed lines 310-311 from:

35. What can I do if sda2 (/share/hdd/conf) is getting full and i cant install ipkg packages anymore?

to:

36. What can I do if sda2 (/share/hdd/conf) is getting full and i cant install ipkg packages anymore?

Changed lines 319-320 from:

36. What's the default password for Openslug?

to:

37. What's the default password for Openslug?

Changed lines 329-330 from:

37. Why do pages on this wiki not format correctly?

to:

38. Why do pages on this wiki not format correctly?

Changed lines 335-336 from:

38. I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?

to:

39. I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?

Changed line 339 from:
You probably have the slug hooked up to a 10Mbps network. Hook it up to a 100Mbps network and you are back in business. This has to do with the ethernet connection on the slug loosing packets when connected to a 10Mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
to:
You probably have the slug hooked up to a 10Mbps network. Hook it up to a 100Mbps network and you are back in business. This has to do with the ethernet connection on the slug loosing packets when connected to a 10Mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
May 01, 2005, at 03:59 AM by Mats Ekelund -- Disabling UPNP solved dropped connections
Changed lines 189-190 from:
to:
Disabling UPnP helped for me. I have a DLINK DI-624 router.
April 28, 2005, at 03:43 AM by JP -- Add para to section 3
Added lines 23-24:
Received the "Not enough Memory" message while updating a brand new untouched NSLU2 with the latest Linksys firmware (NSLU2_V23R29.bin) from the Linksys support site. NSLU2 had no disks attached at the time. Followed the above advice and flash completed OK.
April 27, 2005, at 12:09 PM by tman --
Changed lines 293-295 from:
This problem occurs when copying "large" files (1mb and up, at least on my setup). Small files do not seem to be a problem.
You probably have the slug hooked up to a 10mbps network. Hook it up to a 100mbps network and you are back in business. This has to do with the ethernet connection on the slug loosing packets when connected to a 10mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
to:
This problem occurs when copying "large" files (1MB and up, at least on my setup). Small files do not seem to be a problem.
You probably have the slug hooked up to a 10Mbps network. Hook it up to a 100Mbps network and you are back in business. This has to do with the ethernet connection on the slug loosing packets when connected to a 10Mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
April 27, 2005, at 07:25 AM by Arno Jansen --
Added lines 290-295:

38. I keep getting "Cannot copy file: path too deep" errors when copying files onto the slug! What's wrong?

This problem occurs when copying "large" files (1mb and up, at least on my setup). Small files do not seem to be a problem.
You probably have the slug hooked up to a 10mbps network. Hook it up to a 100mbps network and you are back in business. This has to do with the ethernet connection on the slug loosing packets when connected to a 10mbps network. Search google with "path too deep" to find out more information, and this thread thread in particular.
April 22, 2005, at 06:46 PM by tman -- Corrected #0 as we have the source for R29 now.
Changed lines 9-10 from:
Probably Unslung 3.18-beta - see HowToGetInvolved? for details. Note that the Unslung firmware is based on Linksys 2.3R25 firmware. We are not able to update the Unslung firmware to 2.3R29 until Linksys releases the kernel source code changes from R25 to R29. So you have to choose either Unslung or R29 - you cannot have both until Linksys releases the source code for R29.
to:
Probably Unslung 3.18-beta - see HowToGetInvolved? for details. Note that the Unslung firmware is based on Linksys 2.3R25 firmware currently. We will switch over to 2.3R29 soon.
April 22, 2005, at 06:39 PM by tman -- Added link to LinksysR29 to #26
Changed lines 180-181 from:
The sources for the R29 kernel has been published. We will move over to R29 soon. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
to:
The GPL sources for the R29 firmware has been published at the Linksys GPL Code Center. We will move over to R29 soon. More details about R29 are at LinksysR29. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
April 22, 2005, at 05:02 PM by tman -- Updated #26 R29 entry.
Changed lines 180-181 from:
The sources for the R25 kernel are available, those for R29 are not yet. We hope they will be published by Linksys soon. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
to:
The sources for the R29 kernel has been published. We will move over to R29 soon. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
Changed lines 238-239 from:

32. How can I restore samba on nslu2 if it is no longer working?

to:

32. How can I restore samba on NSLU2 if it is no longer working?

Changed line 241 from:
2. Flash NSLU2 with original linksys R25 firmware using telnet into RedBoot and tftp-server or sercomm (see HowTo's)
to:
2. Flash NSLU2 with original Linksys R25 firmware using telnet into RedBoot & use a TFTP server or use the SerComm upgrade protocol (see HowTo's)
April 21, 2005, at 04:11 PM by jbowler -- Noted current OpenSlug support for NTFS
Added lines 78-79:
update: Recent (April 2005+) builds of OpenSlug come with the NTFS kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled it - so the mount is read-only.
April 20, 2005, at 01:43 PM by barrym --
Changed lines 202-207 from:
4. Create a file called /etc/nsswitch.conf which contains this: hosts: files dns
Now you're done.
If you try to install Apache without doing the "unslung-feeds" step, chances are you will get an error like "ERROR: Cannot satisfy the following dependencies for apache: openldap openldap"
to:
4. Create a file called /etc/nsswitch.conf which contains this line:

hosts: files dns
5. Restart your NSLU2 or restart the Apache server by typing this line:

/opt/etc/init.d/S80apache restart
Now you're done.
Note that the default Apache installation uses port 8000, so to view your test installation:
http://(NSLU2 location):8000
If you try to install Apache without doing the "unslung-feeds" step, chances are you will get an error like

ERROR: Cannot satisfy the following dependencies for apache: openldap openldap
April 18, 2005, at 04:59 AM by jbowler --
Changed lines 221-223 from:

Now you must fill the .htpasswd file by a password generated by the htpasswd provided by apache... search htpasswd on google for more informations...

to:
Now you must fill the .htpasswd file by a password generated by the htpasswd provided by apache... search htpasswd on google for more informations...
Changed lines 235-236 from:

Now samba should work again, your data on the HDD should be unchanged.

to:
Now samba should work again, your data on the HDD should be unchanged.
Changed lines 239-244 from:

When the slug first boots up, the data partition is readonly until the disk quota system has scanned it and computed the disk usage of all the users. Depending on how much data there is on your data partition, this may take several seconds, or several minutes. Note that this is the default behaviour of Unslung; it will happen even if you have not done anything to configure the quota system.

This issue frequently bites people who have linked /opt to a directory in the data partition in order to get more space for packages. If you do that, you must either disable quotas (see below) or live with the fact that /opt might not always be writable.

If you have no interest in quotas, you might want to disable them by creating a DiversionScript. Placing this content in /unslung/rc.quota should do the trick:

to:
When the slug first boots up, the data partition is readonly until the disk quota system has scanned it and computed the disk usage of all the users. Depending on how much data there is on your data partition, this may take several seconds, or several minutes. Note that this is the default behaviour of Unslung; it will happen even if you have not done anything to configure the quota system.
This issue frequently bites people who have linked /opt to a directory in the data partition in order to get more space for packages. If you do that, you must either disable quotas (see below) or live with the fact that /opt might not always be writable.
If you have no interest in quotas, you might want to disable them by creating a DiversionScript. Placing this content in /unslung/rc.quota should do the trick:
Changed lines 250-251 from:

This is the intended behaviour on a slug with a flash file system root. When the flash file system is created the dates on all the files it contains are set to 0, this corresponds to the last instant in 1969. This means that you can instantly see if a file has been changed.

to:
This is the intended behaviour on a slug with a flash file system root. When the flash file system is created the dates on all the files it contains are set to 0, this corresponds to the last instant in 1969. This means that you can instantly see if a file has been changed.
Changed lines 254-255 from:

Best option is to move the /opt directory to the data partition (sda1):

to:
Best option is to move the /opt directory to the data partition (sda1):
Changed lines 259-260 from:

That's it. Thanks to perlguru for the info!

to:
That's it. Thanks to perlguru for the info!
Changed lines 263-270 from:

opeNSLUg

If you have made some change to delete the root password from the build (so that it is empty on first boot) then it will become:

OpenSlug

in builds after April 3, 2005. (sysconfsetup zaps it on first boot if it is not set.)

to:
opeNSLUg
If you have made some change to delete the root password from the build (so that it is empty on first boot) then it will become:
OpenSlug
in builds after April 3, 2005. (sysconfsetup zaps it on first boot if it is not set.)
Changed lines 273-275 from:

Some pages do not format to fit the width of the window. This is because they contain unsplittable lines which set the minimum width of the text much greater than the width of the window.

These lines appear to be caused by @@typewriter@@ formatting directives. Apparently the wiki code will not split such a line. To avoid this don't set @@ formatting for more than a few words. Simply stop and restart with a pair of @@ directives to give the wiki a chance to line-break.

to:
Some pages do not format to fit the width of the window. This is because they contain unsplittable lines which set the minimum width of the text much greater than the width of the window.
These lines appear to be caused by @@typewriter@@ formatting directives. Apparently the wiki code will not split such a line. To avoid this don't set @@ formatting for more than a few words. Simply stop and restart with a pair of @@ directives to give the wiki a chance to line-break.
April 18, 2005, at 04:57 AM by jbowler --
Changed lines 261-262 from:

36. What's the default password for Openslug ?

to:

36. What's the default password for Openslug?

Changed lines 269-275 from:

in builds after April 3, 2005. (sysconfsetup zaps it on first boot if it is not set.)

to:

in builds after April 3, 2005. (sysconfsetup zaps it on first boot if it is not set.)

37. Why do pages on this wiki not format correctly?

Some pages do not format to fit the width of the window. This is because they contain unsplittable lines which set the minimum width of the text much greater than the width of the window.

These lines appear to be caused by @@typewriter@@ formatting directives. Apparently the wiki code will not split such a line. To avoid this don't set @@ formatting for more than a few words. Simply stop and restart with a pair of @@ directives to give the wiki a chance to line-break.

April 18, 2005, at 04:53 AM by jbowler --
Changed lines 117-118 from:
Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
to:
Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
Changed lines 121-122 from:
Solution: Make sure your netmasks and gateway information are set properly. If they are and you're running an own dhcp server on your LAN, see that there's a line like option domain-name-servers dns.ip.address.here, 2nd.ip.address.here; in your /etc/dhcpd.conf file.
to:
Solution: Make sure your netmasks and gateway information are set properly. If they are and you're running an own dhcp server on your LAN, see that there's a line like option domain-name-servers dns.ip.address.here, 2nd.ip.address.here; in your /etc/dhcpd.conf file.
Changed lines 127-128 from:
For a simple proxy, a single line option http_proxy http://proxy.ip.address.here:proxy_port will do the job (mine needs option http_proxy http://192.168.255.1:3128).
to:
For a simple proxy, a single line option http_proxy http://proxy.ip.address.here:proxy_port will do the job (mine needs option http_proxy http://192.168.255.1:3128).
April 15, 2005, at 08:59 PM by jp30 --
Changed lines 200-201 from:
3. ipkg install php (This will install Apache and all the other needed apps too)
to:
3. ipkg install php-apache (This will install PHP, Apache and all the other needed apps too)
April 15, 2005, at 05:09 PM by 216.113.168.141 --
Changed lines 13-14 from:
OK, here's the deal. If you flash the Unslung firmware with *NO* disks attached (as you should), and *THEN* enable telnet through the web interface (*STILL* with *NO* disks attached, as explained in the README) and then telnet to the IP address of the NSLU2 (*STILL* with *NO* disks attached, and telneting to Linux, *NOT* to RedBoot), you will be able to log in as "root" with the password "uNSLUng" (as long as there are *STILL* *NO* disks attached). *BUT*, as soon as you plug a disk in, the password will *CHANGE* to whatever password is stored (in *MULTIPLE* places) on the disk. And this other password (which you probably don't know, and neither do we) may even *PERSIST* after you unplug the disk (as it may have been automatically copied into the root filesystem which is now in the internal flash in Unslung 3.x). So you either need to change that root password (using the ChangePasswordsFromTheCommandLine instructions because simply editing the /etc/passwd file is *NOT* enough to make it stick) *AND* follow the instructions in DiversionScripts to permanently enable telnet, *OR* install and configure the dropbear or openssh package.
to:
OK, here's the deal. If you flash the Unslung firmware with NO disks attached (as you should), and THEN enable telnet through the web interface (STILL with NO disks attached, as explained in the README) and then telnet to the IP address of the NSLU2 (STILL with NO disks attached, and telneting to Linux, NOT to RedBoot), you will be able to log in as "root" with the password "uNSLUng" (as long as there are STILL NO disks attached). BUT, as soon as you plug a disk in, the password will CHANGE to whatever password is stored (in MULTIPLE places) on the disk. And this other password (which you probably don't know, and neither do we) may even PERSIST after you unplug the disk (as it may have been automatically copied into the root filesystem which is now in the internal flash in Unslung 3.x). So you either need to change that root password (using the ChangePasswordsFromTheCommandLine instructions because simply editing the /etc/passwd file is NOT enough to make it stick) AND follow the instructions in DiversionScripts to permanently enable telnet, OR install and configure the dropbear or openssh package.
Changed lines 33-34 from:
If you attach a regular USB hard disk to the NSLU2, you must first format the drive. This creates 3 partitions (two ext3 filesystems and swap). With flash drives, the NSLU2 won't normally let you do this. However, the NSLU2 still recognizes the drive and mounts it as a single VFAT (Windows-based) filesystem. This causes a number of problems and most of the fancy functionality of the NSLU2 is not available (like adding users, controling shares, creating backup jobs, etc). However, the box will still function as a simple Samba server with one directory shared. If this works for you, great. Otherwise, you may want to look into one of the custom firmware options to get more out of your box.
to:
If you attach a regular USB hard disk to the NSLU2, you must first format the drive. This creates 3 partitions (two ext3 filesystems and swap). With flash drives, the NSLU2 won't normally let you do this. However, the NSLU2 still recognizes the drive and mounts it as a single VFAT (Windows-based) filesystem. This causes a number of problems and most of the fancy functionality of the NSLU2 is not available (like adding users, controling shares, creating backup jobs, etc). However, the box will still function as a simple Samba server with one directory shared. If this works for you, great. Otherwise, you may want to look into one of the custom firmware options to get more out of your box.
Changed lines 78-79 from:

11. Can I use RAID?

to:

11. Can I use RAID?

Changed lines 245-247 from:
#!/bin/sh
return 0
to:
#!/bin/sh
return 0
Changed lines 256-258 from:
mv /share/hdd/conf/opt /share/hdd/data/opt
rm /opt; ln -s /share/hdd/data/opt opt
to:
mv /share/hdd/conf/opt /share/hdd/data/opt
rm /opt; ln -s /share/hdd/data/opt opt
Changed lines 263-264 from:

opeNSLUg

to:

opeNSLUg

Changed lines 267-268 from:

OpenSlug

to:

OpenSlug

April 15, 2005, at 04:57 PM by 216.113.168.141 --
Changed lines 39-46 from:

1: /share/hdd/conf/usr/local/passwd

   /share/hdd/conf/passwd
   /share/flash/conf/passwd
   /share/flash/conf/usr/local/passwd

2: /share/hdd/conf/etc/passwd -> /share/hdd/conf/passwd

   /share/flash/conf/etc/passwd -> /share/hdd/conf/passwd

3: /usr/local/etc/passwd =]

to:
     1: /share/hdd/conf/usr/local/passwd
        /share/hdd/conf/passwd
        /share/flash/conf/passwd
        /share/flash/conf/usr/local/passwd
     2: /share/hdd/conf/etc/passwd -> /share/hdd/conf/passwd
        /share/flash/conf/etc/passwd -> /share/hdd/conf/passwd
     3: /usr/local/etc/passwd
 =]
Changed lines 214-218 from:
touch /share/hdd/conf/.dongle
chmod 0666 /share/hdd/conf/.dongle
touch /share/hdd/conf/.htpasswd
chmod 0644 /share/hdd/conf/.htpasswd
to:
  
        touch /share/hdd/conf/.dongle
        chmod 0666 /share/hdd/conf/.dongle
        touch /share/hdd/conf/.htpasswd
        chmod 0644 /share/hdd/conf/.htpasswd
  
Changed line 227 from:
2. Flash NSLU2 with original linksys R25 firmware using telnet into Redboot and tftp-server or sercomm (see HowTo's)
to:
2. Flash NSLU2 with original linksys R25 firmware using telnet into RedBoot and tftp-server or sercomm (see HowTo's)
Changed lines 235-236 from:

Now samba should work again, your data on the hdd should be unchanged.

to:

Now samba should work again, your data on the HDD should be unchanged.

April 15, 2005, at 04:46 PM by 216.113.168.141 --
Changed lines 222-232 from:

32. How can I restore samba on nslu2 if it isnt working no more ?

turn nslu2-hdd off
flash nslu2 with original linksys r25 firmware using telnet into redboot and tftp-server or sercomm (see how to's)
reset sysconf (see how to's)
flash unslung-version of choice (e.g. 3.18) via webpage of nslu2
telnet into nslu2 after enabling telnet and login with standard password
turn hdd on
unsling again with "/sbin/unsling"
reboot
to:

32. How can I restore samba on nslu2 if it is no longer working?

1. Turn NSLU2-HDD off
2. Flash NSLU2 with original linksys R25 firmware using telnet into Redboot and tftp-server or sercomm (see HowTo's)
3. Reset sysconf (see HowTo's)
4. Flash unslung-version of choice (e.g. 3.18) via webpage of NSLU2
5. Telnet into NSLU2 after enabling telnet and login with standard password
6. Turn HDD on
7. Unsling again with "/sbin/unsling"
8. Reboot
April 04, 2005, at 12:41 PM by barrym --
Added lines 206-207:
If you try to install Apache without doing the "unslung-feeds" step, chances are you will get an error like "ERROR: Cannot satisfy the following dependencies for apache: openldap openldap"
April 03, 2005, at 11:43 AM by jbowler --
Added lines 260-265:

If you have made some change to delete the root password from the build (so that it is empty on first boot) then it will become:

OpenSlug

in builds after April 3, 2005. (sysconfsetup zaps it on first boot if it is not set.)

March 27, 2005, at 10:20 PM by ccsmart --
Changed line 257 from:

'''36. What's the defaut password for Openslug ?

to:

36. What's the default password for Openslug ?

March 27, 2005, at 10:19 PM by ccsmart --
Changed lines 255-259 from:

That's it. Thanks to perlguru for the info!

to:

That's it. Thanks to perlguru for the info!

'''36. What's the defaut password for Openslug ?

opeNSLUg

March 23, 2005, at 10:03 PM by rwhitby --
Changed line 178 from:
The sources for the R25 kernel are available, those for R29 are not yet. We hope they will be published by Linksys soon.
to:
The sources for the R25 kernel are available, those for R29 are not yet. We hope they will be published by Linksys soon. Note that Linksys have removed telnet from R29, but Unslung will reinstate it.
March 16, 2005, at 07:52 AM by sebster --
Changed line 248 from:

35. What can I do if sda2 (/share/hdd/conf is getting full and i cant install ipkg packages anymore?

to:

35. What can I do if sda2 (/share/hdd/conf) is getting full and i cant install ipkg packages anymore?

Changed line 250 from:

Best option is to move the /opt dir to the data partition (sda1):

to:

Best option is to move the /opt directory to the data partition (sda1):

Changed line 255 from:

thats it. Thanks to perlguru for the info!

to:

That's it. Thanks to perlguru for the info!

March 15, 2005, at 02:23 PM by K Carter Sr --
Changed line 17 from:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest, Paragon Partition Manager is pretty swift), and with most utilities, all the files written will be owned by root. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
to:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest, Paragon Partition Manager is fairly quick), and with most utilities, all the files written will be owned by root. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
March 15, 2005, at 02:22 PM by K Carter Sr --
Changed line 17 from:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest), and with most utilities, all the files written will be owned by root. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
to:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest, Paragon Partition Manager is pretty swift), and with most utilities, all the files written will be owned by root. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
March 15, 2005, at 02:17 PM by K Carter Sr --
Changed line 15 from:

2. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC, using Microsoft Windows?

to:

2. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC (SCSI,IDE,USB,ETC..), using Microsoft Windows?

March 15, 2005, at 02:13 PM by K Carter Sr --
Changed line 17 from:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest), and with most utilities, all the files written will be owned by root. Full details of this, and the caveats of the various partitioning software packages will be placed in the howto section soon. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
to:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest), and with most utilities, all the files written will be owned by root. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
March 14, 2005, at 09:55 AM by wipmac --
Changed lines 252-253 from:

mv /share/hdd/conf/opt /share/hdd/data/opt rm /opt; ln -s /share/hdd/data/opt opt

to:
mv /share/hdd/conf/opt /share/hdd/data/opt
rm /opt; ln -s /share/hdd/data/opt opt
March 14, 2005, at 09:55 AM by wipmac --
Changed lines 246-255 from:

This is the intended behaviour on a slug with a flash file system root. When the flash file system is created the dates on all the files it contains are set to 0, this corresponds to the last instant in 1969. This means that you can instantly see if a file has been changed.

to:

This is the intended behaviour on a slug with a flash file system root. When the flash file system is created the dates on all the files it contains are set to 0, this corresponds to the last instant in 1969. This means that you can instantly see if a file has been changed.

35. What can I do if sda2 (/share/hdd/conf is getting full and i cant install ipkg packages anymore?

Best option is to move the /opt dir to the data partition (sda1):

mv /share/hdd/conf/opt /share/hdd/data/opt rm /opt; ln -s /share/hdd/data/opt opt

thats it. Thanks to perlguru for the info!

March 14, 2005, at 01:16 AM by jbowleracmorg --
Added lines 243-246:

34. Why are all the dates of the system files set to the end of 1969? / Is the clock on my slug set incorrectly, all the files in the root file system are very old?

This is the intended behaviour on a slug with a flash file system root. When the flash file system is created the dates on all the files it contains are set to 0, this corresponds to the last instant in 1969. This means that you can instantly see if a file has been changed.

March 13, 2005, at 10:09 PM by jp30 --
Changed line 235 from:

When the slug first boots up, the data partition is readonly until the disk quota system has scanned it and computed the disk usage of all the users. Depending on how much data there is on your data partition, this may take several second, or several minutes. Note that this is the default behaviour of Unslung; it will happen even if you have not done anything to configure the quota system.

to:

When the slug first boots up, the data partition is readonly until the disk quota system has scanned it and computed the disk usage of all the users. Depending on how much data there is on your data partition, this may take several seconds, or several minutes. Note that this is the default behaviour of Unslung; it will happen even if you have not done anything to configure the quota system.

March 13, 2005, at 10:08 PM by jp30 --
Added lines 232-242:

33. Why is my data partition readonly all of a sudden? / Why are my startup scripts unable to write to the data partition?

When the slug first boots up, the data partition is readonly until the disk quota system has scanned it and computed the disk usage of all the users. Depending on how much data there is on your data partition, this may take several second, or several minutes. Note that this is the default behaviour of Unslung; it will happen even if you have not done anything to configure the quota system.

This issue frequently bites people who have linked /opt to a directory in the data partition in order to get more space for packages. If you do that, you must either disable quotas (see below) or live with the fact that /opt might not always be writable.

If you have no interest in quotas, you might want to disable them by creating a Unslung.DiversionScripts DiversionScript?. Placing this content in /unslung/rc.quota should do the trick:

#!/bin/sh
return 0
March 11, 2005, at 09:22 PM by wipmac --
Changed line 225 from:
flash unlsung-version of choice
to:
flash unslung-version of choice (e.g. 3.18) via webpage of nslu2
March 11, 2005, at 09:21 PM by wipmac --
Added lines 218-231:

32. How can I restore samba on nslu2 if it isnt working no more ?

turn nslu2-hdd off
flash nslu2 with original linksys r25 firmware using telnet into redboot and tftp-server or sercomm (see how to's)
reset sysconf (see how to's)
flash unlsung-version of choice
telnet into nslu2 after enabling telnet and login with standard password
turn hdd on
unsling again with "/sbin/unsling"
reboot

Now samba should work again, your data on the hdd should be unchanged.

March 10, 2005, at 02:30 PM by ChristianLescuyer --
Changed lines 140-141 from:
I just bought a Seagate Baracuda 3,5' drive and installed it in a third party enclosure. Upon contacting their tech support in Europe they stated that:
  • Seagate does not support other pwoer management than managed by the running OS
to:
I just bought a Seagate Baracuda 3.5" drive and installed it in a third party enclosure. Upon contacting their tech support in Europe they stated that:
  • Seagate does not support other power management than managed by the running OS
Changed lines 143-144 from:
  • The seagate disks do not have a function to retain the power management settings
So i guess my advice would be not to buy the seagate disks
to:
  • Seagate disks do not have a function to retain the power management settings
So I guess my advice would be not to buy the Seagate disks
March 10, 2005, at 02:05 AM by laurens --
Added lines 140-145:
I just bought a Seagate Baracuda 3,5' drive and installed it in a third party enclosure. Upon contacting their tech support in Europe they stated that:
  • Seagate does not support other pwoer management than managed by the running OS
  • Seagate does not support drives to be installed in third party enclosures
  • The seagate disks do not have a function to retain the power management settings
So i guess my advice would be not to buy the seagate disks
March 06, 2005, at 08:57 AM by Adrian Godwin --
Added lines 123-131:
Reason2: You have an http proxy.
Solution: You need to configure ipkg to go through the proxy. This is done through the file /etc/ipkg.conf, but the standard unSlung installation doesn't have a sample file.
For a simple proxy, a single line option http_proxy http://proxy.ip.address.here:proxy_port will do the job (mine needs option http_proxy http://192.168.255.1:3128).
For a proxy that needs username, password etc. you'll need more - look at the ipkg documentation at http://handhelds.org/moin/moin.cgi/Ipkg and the sample file http://openwrt.org/ipkg/ipkg.conf.
March 06, 2005, at 04:36 AM by yahpn --
Added lines 169-170:
I had to disable UPnP to get my NSLU2 to work properly. I have a DLINK DI-524 router.
March 03, 2005, at 04:09 PM by mathieu_xwave --
Added lines 188-200:

31. How can I recover a bad conf parition when the web interface says my HD is "not formatted" ?

If you have erased your conf parition but you have a made a backup of the files (by a simple tar czf /share/hdd/conf/*), when you restore the files, the HD won't be recognized anymore...
The solution is to recreate the two hidden files that you haven't saved...
If your conf parition isn't mounted yet, mount it (mount /dev/sda2 /share/hdd/conf)
The commands are:
touch /share/hdd/conf/.dongle
chmod 0666 /share/hdd/conf/.dongle
touch /share/hdd/conf/.htpasswd
chmod 0644 /share/hdd/conf/.htpasswd

Now you must fill the .htpasswd file by a password generated by the htpasswd provided by apache... search htpasswd on google for more informations...

February 28, 2005, at 12:44 AM by ka6sox --
Changed line 167 from:
Try disabling UPnP support on the NSLU2 and possibly on the router as well. A user reports that their NSLU2 was basically unusable until they switched off UPnP support through the web admin interface. Since disabling UPnP support in the NSLU2, there have not been any problems. There may be issues with certain D-Link routers (in this case a D-Link 624) and UPnP support as well so it is recommended that you disable UPnP support in the router. Please leave a note in the wiki if disabling UPnP support helps.
to:
Try disabling UPnP support on the NSLU2 and possibly on the router as well. A user reports that their NSLU2 was basically unusable until they switched off UPnP support through the web admin interface. Since disabling UPnP support in the NSLU2, there have not been any problems. There may be issues with certain D-Link routers (in this case a D-Link 624) and UPnP support as well so it is recommended that you disable UPnP support in the router. Please leave a note in the wiki if disabling UPnP support helps.
February 28, 2005, at 12:39 AM by ka6sox --
Changed line 17 from:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic? is one of the slowest), and with most utilities, all the files written will be owned by root. Full details of this, and the caveats of the various partitioning software packages will be placed in the howto section soon. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
to:
You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic is one of the slowest), and with most utilities, all the files written will be owned by root. Full details of this, and the caveats of the various partitioning software packages will be placed in the howto section soon. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.
February 24, 2005, at 01:51 PM by tman --
Changed line 161 from:

26. Why are you still using R25 kernel ? there is a R29 out

to:

26. Why are you still using R25 firmware? R29 is out.

Changed line 163 from:
The sources for the R25 kernel are available, those for R29 not yet. We hope they will be published by Linksys soon.
to:
The sources for the R25 kernel are available, those for R29 are not yet. We hope they will be published by Linksys soon.
Changed line 167 from:
My NSLU2 was basically unusable until I switched off UPNP support through the web admin interface. Since then it is rock solid. I am connected to a DLink? 624, seems especially DLink? people have that problem. It's recommended that Dlink 624 folks also turn off UPNP at the router as well, i.e., not just on the NSLU2.
to:
Try disabling UPnP support on the NSLU2 and possibly on the router as well. A user reports that their NSLU2 was basically unusable until they switched off UPnP support through the web admin interface. Since disabling UPnP support in the NSLU2, there have not been any problems. There may be issues with certain D-Link routers (in this case a D-Link 624) and UPnP support as well so it is recommended that you disable UPnP support in the router. Please leave a note in the wiki if disabling UPnP support helps.
Changed line 169 from:

28. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than I would have expected.

to:

28. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than expected.

Changed line 171 from:
This generally occurs when a USB hub is utilized. In it's current state the NSLU2 kernel only supports two drives. Several USB devices may appear to the NSLU2 as an additional drive and this confuses the kernel. A common setup where the problem would be observed is with a printer (with flash card slot) and a drive plugged into USB HUB and with the HUB plugged into NSLU2. In this case there is a good possiblity that NSLU2 web interface incorrectly reports the drive as "Not Formatted" because it is looking at the drive of the printer instead of the drive you would have expected. DO NOT WORRY. Your drive is intact and to correct this operation disconnect conflicting device and reboot NSLU2.
to:
This generally occurs when a USB hub is utilized. In it's current state the NSLU2 Unslung kernel only supports two drives, one on each port. Several USB devices may appear to the NSLU2 as multiple drivers and this confuses the Unslung kernel. A common example is having a printer with a flash card slot plugged into a USB hub along with a hard disk. In this case, there is a high chance that the web interface will incorrectly report the drive as "Not Formatted" because it is looking at the flash card slot in the printer instead of the expected hard disk. DO NOT WORRY. Your drive and it's data is intact and to fix this you just need to disconnect the conflicting devices (in this case the printer) and restart the NSLU2.
Changed line 173 from:

29. What can i do, if i use openssh to connect to the nslu2 (e.g. putty) and then i try to upgrade openssh on the nslu2, because when doing that, the ssh-connection will be droppen and no login possible any more?

to:

29. How can I upgrade OpenSSH if I'm connected to the NSLU2 via SSH? If I try to upgrade whilst connected via SSH, the connection is dropped and then no further login is possible.

Changed line 175 from:
"upgrading openssh when you're logged in through openssh is unfortunately not a good thing to do ...." (rwhitby) but fortunately theres a solution: enable telnet on the nslu2 via http://192.168.1.77/Management/telnet.cgi, then telnet into the nslu2. type 'ipkg install openssh' which will reinstall openssh. then try your ssh client (e.g. putty) with old settings and it should be fine again
to:
Upgrading OpenSSH when you're logged in via OpenSSH is unfortunately not a good thing to do. Fortunately there is a solution: enable telnet on the NSLU2 via http://192.168.1.77/Management/telnet.cgi (Note: This has been removed as of R29), then telnet into the NSLU2 and type 'ipkg install openssh' which will reinstall/upgrade OpenSSH.
Changed line 177 from:

30. How to install apache?

to:

30. How do I install Apache?

Changed lines 179-180 from:
1. ipkg install unslung-feeds, 2. ipkg update, 3. ipkg install php (this will install apache and all the other needed apps too), 4. create a file called /etc/nsswitch.conf which contains this: hosts: files dns

Now you're done.

to:
1. ipkg install unslung-feeds
2. ipkg update
3. ipkg install php (This will install Apache and all the other needed apps too)
4. Create a file called /etc/nsswitch.conf which contains this: hosts: files dns
Now you're done.
February 24, 2005, at 12:51 PM by wipmac --
Changed lines 175-180 from:
"upgrading openssh when you're logged in through openssh is unfortunately not a good thing to do ...." (rwhitby) but fortunately theres a solution: enable telnet on the nslu2 via http://192.168.1.77/Management/telnet.cgi, then telnet into the nslu2. type 'ipkg install openssh' which will reinstall openssh. then try your ssh client (e.g. putty) with old settings and it should be fine again
to:
"upgrading openssh when you're logged in through openssh is unfortunately not a good thing to do ...." (rwhitby) but fortunately theres a solution: enable telnet on the nslu2 via http://192.168.1.77/Management/telnet.cgi, then telnet into the nslu2. type 'ipkg install openssh' which will reinstall openssh. then try your ssh client (e.g. putty) with old settings and it should be fine again

30. How to install apache?

1. ipkg install unslung-feeds, 2. ipkg update, 3. ipkg install php (this will install apache and all the other needed apps too), 4. create a file called /etc/nsswitch.conf which contains this: hosts: files dns

Now you're done.

February 24, 2005, at 11:09 AM by wipmac --
Changed lines 175-176 from:
"upgrading openssh when you're logged in through openssh is unfortunately not a good thing to do ...." (rwhitby)

but fortunately theres a solution: enable telnet on the nslu2 via http://192.168.1.77/Management/telnet.cgi, then telnet into the nslu2. type 'ipkg install openssh' which will reinstall openssh. then try your ssh client (e.g. putty) with old settings and it should be fine again

to:
"upgrading openssh when you're logged in through openssh is unfortunately not a good thing to do ...." (rwhitby) but fortunately theres a solution: enable telnet on the nslu2 via http://192.168.1.77/Management/telnet.cgi, then telnet into the nslu2. type 'ipkg install openssh' which will reinstall openssh. then try your ssh client (e.g. putty) with old settings and it should be fine again
February 24, 2005, at 11:08 AM by wipmac --
Added lines 173-176:

29. What can i do, if i use openssh to connect to the nslu2 (e.g. putty) and then i try to upgrade openssh on the nslu2, because when doing that, the ssh-connection will be droppen and no login possible any more?

"upgrading openssh when you're logged in through openssh is unfortunately not a good thing to do ...." (rwhitby)

but fortunately theres a solution: enable telnet on the nslu2 via http://192.168.1.77/Management/telnet.cgi, then telnet into the nslu2. type 'ipkg install openssh' which will reinstall openssh. then try your ssh client (e.g. putty) with old settings and it should be fine again

February 22, 2005, at 02:17 AM by unix_fan --
Changed line 167 from:
My NSLU2 was basically unusable until I switched off UPNP support through the web admin interface. Since then it is rock solid. I am connected to a DLink? 624, seems especially DLink? people have that problem.
to:
My NSLU2 was basically unusable until I switched off UPNP support through the web admin interface. Since then it is rock solid. I am connected to a DLink? 624, seems especially DLink? people have that problem. It's recommended that Dlink 624 folks also turn off UPNP at the router as well, i.e., not just on the NSLU2.
February 05, 2005, at 12:02 AM by Keith Garry Boyce --
Added lines 169-172:

28. Why does the system report that a previously formatted drive is not formatted or that the drive is a different size than I would have expected.

This generally occurs when a USB hub is utilized. In it's current state the NSLU2 kernel only supports two drives. Several USB devices may appear to the NSLU2 as an additional drive and this confuses the kernel. A common setup where the problem would be observed is with a printer (with flash card slot) and a drive plugged into USB HUB and with the HUB plugged into NSLU2. In this case there is a good possiblity that NSLU2 web interface incorrectly reports the drive as "Not Formatted" because it is looking at the drive of the printer instead of the drive you would have expected. DO NOT WORRY. Your drive is intact and to correct this operation disconnect conflicting device and reboot NSLU2.
February 03, 2005, at 01:07 PM by rwhitby --
Changed line 9 from:
Probably Unslung 3.17-beta - see HowToGetInvolved? for details. Note that the Unslung firmware is based on Linksys 2.3R25 firmware. We are not able to update the Unslung firmware to 2.3R29 until Linksys releases the kernel source code changes from R25 to R29. So you have to choose either Unslung or R29 - you cannot have both until Linksys releases the source code for R29.
to:
Probably Unslung 3.18-beta - see HowToGetInvolved? for details. Note that the Unslung firmware is based on Linksys 2.3R25 firmware. We are not able to update the Unslung firmware to 2.3R29 until Linksys releases the kernel source code changes from R25 to R29. So you have to choose either Unslung or R29 - you cannot have both until Linksys releases the source code for R29.
February 02, 2005, at 05:40 AM by rwhitby --
Changed line 163 from:
The sources for the R25 kernel are available, those for R29 not yet. We expect them to arrive soon
to:
The sources for the R25 kernel are available, those for R29 not yet. We hope they will be published by Linksys soon.
February 01, 2005, at 02:41 PM by Oli --
Added lines 165-168:

27. The NSLU drops connections all the time, even the web interface times out.

My NSLU2 was basically unusable until I switched off UPNP support through the web admin interface. Since then it is rock solid. I am connected to a DLink? 624, seems especially DLink? people have that problem.
January 29, 2005, at 11:15 PM by rwhitby --
Changed line 9 from:
Probably Unslung 3.17-beta - see HowToGetInvolved? for details.
to:
Probably Unslung 3.17-beta - see HowToGetInvolved? for details. Note that the Unslung firmware is based on Linksys 2.3R25 firmware. We are not able to update the Unslung firmware to 2.3R29 until Linksys releases the kernel source code changes from R25 to R29. So you have to choose either Unslung or R29 - you cannot have both until Linksys releases the source code for R29.
January 26, 2005, at 10:13 AM by rwhitby --
Changed line 92 from:
Not with the stock Linksys firmware. Nor can it be done with Unslung firmware. OpenSlug firmware (which is in early alpha testing, and is only available if you build it from source code and have a serial port added to your slug) will be able to when it is released.
to:
Not with the stock Linksys firmware. Nor can it be done with Unslung firmware. OpenSlug firmware (which is in early alpha testing, and is only available if you build it from source code and have a serial port added to your slug) will be able to when it is released. Note that you can add other devices using a hub, just not more than two external mass storage devices.
January 23, 2005, at 12:06 AM by djoek --
Added lines 161-164:

26. Why are you still using R25 kernel ? there is a R29 out

The sources for the R25 kernel are available, those for R29 not yet. We expect them to arrive soon
January 20, 2005, at 10:53 PM by tman --
Changed lines 1-160 from:

Describe {{FAQ}} here.

to:

This is a collection of, you guessed it, frequently asked questions.

If you have a question, then ask it on the http://groups.yahoo.com/group/nslu2-linux mailing list (of course, you would ask Google, and also search this site and on the mailing list archives before actually posting a question, lest you look silly by asking something that can be easily found in the archives).

If the answer to your question asked on the mailing list contains new information, it should make it's way here (or to the Info.HomePage Information? or HowTo.HomePage HowTo? areas). You can assist in this process - if your question is answered to your satisfaction, then the onus is on you to update the Wiki as "payment" for having your question answered.

0. Which firmware should I use first?

Probably Unslung 3.17-beta - see HowToGetInvolved? for details.

1. I can't telnet to my newly Unslung NSLU2. Why not? I thought that Unslung enabled telnet, and that the root password was set to uNSLUng?

OK, here's the deal. If you flash the Unslung firmware with *NO* disks attached (as you should), and *THEN* enable telnet through the web interface (*STILL* with *NO* disks attached, as explained in the README) and then telnet to the IP address of the NSLU2 (*STILL* with *NO* disks attached, and telneting to Linux, *NOT* to RedBoot), you will be able to log in as "root" with the password "uNSLUng" (as long as there are *STILL* *NO* disks attached). *BUT*, as soon as you plug a disk in, the password will *CHANGE* to whatever password is stored (in *MULTIPLE* places) on the disk. And this other password (which you probably don't know, and neither do we) may even *PERSIST* after you unplug the disk (as it may have been automatically copied into the root filesystem which is now in the internal flash in Unslung 3.x). So you either need to change that root password (using the ChangePasswordsFromTheCommandLine instructions because simply editing the /etc/passwd file is *NOT* enough to make it stick) *AND* follow the instructions in DiversionScripts to permanently enable telnet, *OR* install and configure the dropbear or openssh package.

2. How can I access a NSLU2 ext2/ext3 formatted drive locally connected to a PC, using Microsoft Windows?

You can use several Windows partitioning programs that support ext2/ext3 formatted drives and perform file operations like reading, writing, and error checking. Note: There are significant differences in writing speeds amongst the various partitioning utilities (PartitionMagic? is one of the slowest), and with most utilities, all the files written will be owned by root. Full details of this, and the caveats of the various partitioning software packages will be placed in the howto section soon. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Explore2fs works quite well and is free (GPL), but does not write reliably, error check, or have in-place (non-export edit) editing of text files, like the Windows partitioning programs do.

3. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

If you are running with a USB flash or hard disk with unmodified firmware, this is the result of the Linksys upgrade application thinking that the NSLU2 has run out of memory (it hasn't really - it's just being temporarily used for buffers and caching, and is still available for any programs that need it, but the Linksys upgrade application is not smart enough to know that). Turning off the NSLU2, removing ALL drives, rebooting without any disks connected and then going straight into the Admin webpage for the firmware upgrade should get rid of the error.

4. What is the root password on an unmodified NSLU2 with stock firmware (version xx).

The short answer is that we don't know, and we don't want to know.
There are concerns that releasing this information allows people to gain access to any internet visible NSLU2. However, by default the NSLU2 resides on a unroutable subnet (192.168.1.77) which would mean that any attack would have to originate from inside your network. If this was the case then securing your NSLU2 is the least of your problems. Allowing unrestricted access from the internet is also a bad idea. Both possible avenues for abuse result from implicit actions by the user/owner to allow access.
The default administrative access via the web interface is user:admin password:admin

5. When I boot the NSLU2 with a USB flash drive (with the stock firmware), I cannot do XXX.

If you attach a regular USB hard disk to the NSLU2, you must first format the drive. This creates 3 partitions (two ext3 filesystems and swap). With flash drives, the NSLU2 won't normally let you do this. However, the NSLU2 still recognizes the drive and mounts it as a single VFAT (Windows-based) filesystem. This causes a number of problems and most of the fancy functionality of the NSLU2 is not available (like adding users, controling shares, creating backup jobs, etc). However, the box will still function as a simple Samba server with one directory shared. If this works for you, great. Otherwise, you may want to look into one of the custom firmware options to get more out of your box.

6. When I modify /etc/passwd, I still can't telnet into my box.

The NSLU2 keeps multiple copies of /etc/passwd. You may also need to change the copies in /usr/local and /share/*/conf/.
 
1: /share/hdd/conf/usr/local/passwd
   /share/hdd/conf/passwd
   /share/flash/conf/passwd
   /share/flash/conf/usr/local/passwd
2: /share/hdd/conf/etc/passwd -> /share/hdd/conf/passwd
   /share/flash/conf/etc/passwd -> /share/hdd/conf/passwd
3: /usr/local/etc/passwd

Marked with 1 are the locations you should check and edit.
Marked with 2 are links only.

7. Where is ftpd or other (standard linux) utilities?

The NSLU2 comes with a stripped down root filesystem. If what you need is in the original SnapGear sources, you can build it yourself easily. See HomePage HowTo? Recipes for instructions. Or, you can download a binary image of a fairly complete root filesystem build from the NSLU2-Linux yahoo group (see romfs.tar.gz at http://groups.yahoo.com/group/nslu2-linux/files/ ). Then, simply install the utilities that you require.

8. Can I use the built-in thttpd for my web-server?

Yes, see the HomePage HowTo? section.

9. My computer runs Fedora Core 2 and I'm getting "server is down" when I try to mount the NSLU2. What's going on?

Fedora Core 2 uses NFS protocol version 3 by default. You need to pass the nfsvers option to the mount command in order to force the NFS client to use an older protocol version: mount -t nfs -o nfsvers=2 <nslu2 ip>:/share/hdd /mnt

10. Q: Can I setup the NSLU2 to use NTFS partitions?

Currently, no.
There are two NTFS drivers for Linux in existance:
  • Captive - http://www.jankratochvil.net/project/captive/
This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like http://fabrice.bellard.free.fr/qemu/ QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. Short answer is still no.
  • Linux NTFS project - http://linux-ntfs.sourceforge.net/status.html
This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users. The new, rewritten version of the NTFS driver is included in the Linux 2.6.9 kernel, so once the OpenSlug project succeeds in getting the 2.6 kernel running on the NSLU2, it will be possible to see if this driver works.

11. Can I use RAID?

Yes. But currently only with the Unslung-able firmware. HowTo.EnableRAIDSupport How to enable RAID support in Unslung-able?. OpenSlug is capable of RAID support but nobody has tried it yet.

12. Which SSH daemon should I use ?

dropbear is more lightweight. The downside is that dropbear does not support that many features and is slower. OpenSSH does support the full set of features and is a bit quicker in the key handling. One set of tests found OpenSSH on the NSLU2 to be 8x faster than dropbear at scp transfers - 800kB/s vs 100kB/s (using "scp -c blowfish" as this should be the least CPU-intensive cypher).

13. Can I boot the NSLU2 with a USB device as the root filesystem?

Yes, using the Unslung firmware (version 2.12-beta or later), with either a 1Gb or larger external hard disk plugged into either port, or a 256MB or larger flash disk plugged into the Disk1 port.

14. Can I use a USB hub so that I can add more than two external hard drives?

Not with the stock Linksys firmware. Nor can it be done with Unslung firmware. OpenSlug firmware (which is in early alpha testing, and is only available if you build it from source code and have a serial port added to your slug) will be able to when it is released.

15. I need to build more kernel modules, where are the kernel sources for the NSLU2?

  • Use the OpenEmbedded environment to create your kernel and configure modules there
  • Get the kernel sources from ...

16. What is the ixp1 interface, and can it be used for anything useful?

The IXP420 has two network interfaces built in, ixp0 and ixp1. ixp0 is wired to the ethernet socket on the back through the RealTek PHY chip. ixp1 however is not connected to anything at all and the lines aren't brought out anywhere on the PCB. This means that it is not possible to use ixp1 at all.

17. Can I write and compile code directly on the NSLU2?

18. Why does my NSLU2 beep every eight hours?

peecock41 figured out what it means when the Info.WhyTheNSLU2BeepsEveryEightHours NSLU2 beeps every 8 hours?.

19. When I try to change the settings of my NSLU2 via the web interface, I get an error message that says "Error: Fail to get system information".

Something probably got fudged up in the internal system configuration. Re-flashing won't fix the problem; you will need to HowTo.ResetSysConf reset the system configuration?.

20. ipkg update doesn't work

Symptoms: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-x3a5K1 http://ipkg.nslu2-linux An error ocurred, return value: 1.
Reason: DNS is unreachable.
Solution: Make sure your netmasks and gateway information are set properly. If they are and you're running an own dhcp server on your LAN, see that there's a line like option domain-name-servers dns.ip.address.here, 2nd.ip.address.here; in your /etc/dhcpd.conf file.

21. How do I spin down my USB hard disks?

You can download the Power Booster utility at http://www.hitachigst.com/downloads/pbinstall.exe for 2.5" IBM/Hitachi TravelStar disks. The Power Booster utility will enable the auto spin down feature of the disk. For 3.5" IBM/Hitachi drives (and maybe others), you can download the Feature Tool at http://www.hitachigst.com/downloads/featuretool_v195.exe. Otherwise temporarily install the IDE disk in your ordinary Linux box, read the disk technical documentation and use hdparm to adjust the settings by hand. The trick is to enable APM within the drive itself, so Linux doesn't have to care about it at all. You can't use hdparm to alter the APM settings from the NSLU2 as the USB->IDE adapters are emulated as SCSI host adapters in the Linux kernel which is incompatible with the necessary hdparm options.
Either way, you'll have to open your 2.5" USB enclosure and install the disk drive temporarily to a desktop computer using a 2.5" to 3.5" IDE adapter. After that, you can do the APM adjustment in Windows or Linux.

22. After installing the Unslung firmware, the disk 1 to disk 2 backup doesn't work anymore

The original Linksys backup binary has problems with symbolic links, the backup can be made working again using rsync.
See http://www.nslu2-linux.org/wiki/HowTo/FixTheDriveBackupForUnslungFirmware

23. What is the difference between a "soft-float" and "hard-float" compiler?

"float" refers to a floating point unit (FPU) in a CPU to do floating point math calculations. Some CPUs don't have a built in FPU but a lot of software requires the use of one. To achieve this on a platform without a FPU you can use an emulator. There are two types of emulation, one where the kernel will trap all the opcodes related to the FPU and then perform the calculations itself or one where you put the emulator into the application binary itself and it does it all internally.
The FPU emulators are architecture specific and the kernel based one for the ARM architecture is NWFPE (NetWinder Floating Point Emulator) which was written by NetWinder? for their series of ARM based devices.
The user space emulation system is more efficient than the kernel space one due to not requiring the need to trap illegal instruction errors and then performing the requested calculation. Each time you issue a FP opcode, there will be a context switch which is expensive in terms of time and speed. Building the necessary code into the application binary itself however means it just calculates it directly without the need for the traps. The disadvantage however is that the FP code is built into each application and any non compliant applications won't be supported.
It is possible to use a kernel with NWFPE built in for all non softfloat binaries and have softfloat for everything else.
Example: Now you should understand better the following string when you compile codes for nslu2:
"armv5b-softfloat-linux/gcc-3.3.4-glibc-2.2.5/bin/armv5b-softfloat-linux-gcc"
See this URL for futher details: http://linux-7110.sourceforge.net/howtos/netbook_new/x936.htm

24. Are there any differences between the NSLU2 and the NSLU2UK?

In the UK we get the NSLU2UK shipped instead of the NSLU2. The difference is that it comes with a UK PSU.

25. When I first apply power to the NSLU2, it is off. How do I fix that?

See the HowTo.HomePage HowTo? Recipes for hardware hacking.