NSLU2-Linux
view · edit · print · history

OpenSlug.InitialisingOpenSlug History

Hide minor edits - Show changes to markup

February 04, 2008, at 07:24 PM by fcarolo -- updated turnup instructions
Changed lines 43-44 from:

If you wish to set up the password and network yourself the message displayed on log in can be eliminated by removing /etc/motd. turnup init will do this when it is run. Network setup is concentrated in /etc/network/interfaces, but there is a hand-crafted script for udhcpc which ensures that the network is set up with the default (LinkSys?) static address 192.168.1.77 if DHCP fails.

to:

If you wish to set up the password and network yourself the message displayed on log in can be eliminated by removing /etc/motd. turnup init will do this when it is run. Network setup is concentrated in /etc/network/interfaces, but there is a hand-crafted script for udhcpc which ensures that the network is set up with the default (Linksys) static address 192.168.1.77 if DHCP fails.

February 04, 2008, at 07:19 PM by fcarolo -- up
Added line 17:
  1. Format the new root partition using mke2fs -j <DEVICE> to create an ext3 filesystem on it.
February 04, 2008, at 07:15 PM by fcarolo -- updated turnup instructions
Changed lines 10-11 from:

`Note: OpenSlug 3.10 and later versions will correctly detect the MAC address, so the following observations are no longer true. Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the Linksys identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original Linksys MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary. Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

to:

Note: OpenSlug 3.10 and later versions will correctly detect the MAC address, so the following observations are no longer true. Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the Linksys identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original Linksys MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary. Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

February 04, 2008, at 07:15 PM by fcarolo -- updated turnup instructions
Changed line 16 from:
  1. If you created a swap partition, prepare it with mkswap <SWAP PARTITION> and start using it with swapon -a.
to:
  1. If you created a swap partition, prepare it with mkswap <SWAP PARTITION> and start using it with swapon <SWAP PARTITION>.
February 04, 2008, at 07:12 PM by fcarolo -- updated turnup instructions
Changed lines 10-11 from:

`Note: OpenSlug 3.10 and later versions will correctly detect the MAC address, so the following observations are no longer true. Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the LinkSys? identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original LinkSys? MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary. Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

to:

`Note: OpenSlug 3.10 and later versions will correctly detect the MAC address, so the following observations are no longer true. Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the Linksys identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original Linksys MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary. Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

February 04, 2008, at 07:12 PM by fcarolo -- updated turnup instructions
Changed lines 3-4 from:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

to:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

Changed line 7 from:

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network. If you have a DHCP server on your network you may use dhcp as the boot protocol, not static (which is the default). Static has the advantage that you are always very sure about the IP address

to:

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network. If you have a DHCP server on your network you may use dhcp as the boot protocol, not static (which is the default). Static has the advantage that you are always very sure about the IP address

Changed lines 10-24 from:

Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the LinkSys? identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original LinkSys? MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary.

Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

Further initialisation is optional - it depends very much on what you want to do with OpenSlug. turnup help gives some help. Some of the steps you can follow are:

Note: To reboot the NSLU2 use the "shutdown -r now" command not the power button. This advice may be out of date - version 2.7 does a graceful shutdown in response to the power button, but "shutdown -r now" is definitely safe.

  1. (If necessary) Use fdisk (OpenSlug.InitialisingDisks)to create a partition on your destination disk. (consider making a swap partition as well) REBOOT the slug.
  2. Run turnup init
  3. Do extra network configuration
  4. If not already done, plug in a disk or flash card in USB1? and wait for the device to settle (you can see if the device is detected with the dmesg command)
  5. If necessary (see below) install packages to allow the NSLU2 to function correctly in your network.
  6. Format a hard disk (example: mkfs.ext3 <DEVICE>) (initialize swap on a different device with mkswap <DEVICE>)
  7. Run turnup disk -i <DEVICE> -t ext3 to create a root filesystem on the disk. (Or turnup memstick -i <DEVICE> -t ext3)
to:

`Note: OpenSlug 3.10 and later versions will correctly detect the MAC address, so the following observations are no longer true. Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the LinkSys? identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original LinkSys? MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary. Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

Further initialisation is optional - it depends very much on what you want to do with OpenSlug. turnup help gives some help. Some of the steps you can follow are:

  1. Run turnup init to set the new root password and confirm network setup. After that, do a turnup preserve to save your new configuration.
  2. You will need an external hard disk or flash card for OpenSlug. Plug in your disk, check that it was recognized looking at the kernel messages with dmesg and use fdisk to create a partition on your destination disk. Consider making a swap partition as well. See InitialisingDisks if you are not familiar with fdisk on a Linux machine. After creating your new partitions you must reboot the slug before trying to initialize the new partitions. Use shutdown -r now to reboot and remember to login using the new root password you set with turnup init.
  3. If you created a swap partition, prepare it with mkswap <SWAP PARTITION> and start using it with swapon -a.
  4. Run turnup disk -i <DEVICE> -t ext3 to create a root filesystem on the external disk. (Or turnup memstick -i <DEVICE> -t ext3 if you are using a flash disk.)
Changed lines 21-22 from:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1.

to:

Please note that <DEVICE> should be /dev/sda1 (first partition from the disk connected to USB port 1) or /dev/sdb1 (first partition from the disk connected to USB port 2). The <SWAP PARTITION> will probably be /dev/sda2 or /dev/sdb2.

January 11, 2007, at 04:40 PM by TheAnarcat -- document you need to plug in the disks!
Added line 21:
  1. If not already done, plug in a disk or flash card in USB1? and wait for the device to settle (you can see if the device is detected with the dmesg command)
December 23, 2006, at 08:51 PM by Jelle Alten -- added note about no disk leds in openslug 3.10 beta
Added lines 32-33:

Note: in OpenSlug 3.10 beta the disk leds do not turn on or flash when there is a disk attached. No lights. Just the power and ethernet leds work.

October 10, 2006, at 04:39 AM by Glen Harris -- Clarified broadcast ping
Changed lines 5-6 from:

Note: You might have to ping 192.168.1.255 to determine the device's new IP address. Alternatively, check your DHCP server's client table. Installation over stock firmware will use DHCP if available, otherwise defaulting to 192.168.1.77

to:

Note: If not using Windows, you can ping -b 192.168.1.255 to determine the device's new IP address. Alternatively, check your DHCP server's client table. Installation over stock firmware will use DHCP if available, otherwise defaulting to 192.168.1.77

May 18, 2006, at 02:38 PM by alfs -- pinpointing mac address change
Added lines 12-13:

Note: The MAC address change is performed each reboot from /etc/network/interfaces, which explains why upgrade mode still use the original MAC address.

May 05, 2006, at 09:45 PM by DM -- Removed my previous edits. My permissions problem wasn\'t solved with no_all_squash, it just made it so it used the slug itself as /. Sorry.
Changed lines 50-51 from:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you want to allow non-root users you'll need to use the rw,no_root_squash,no_all_squash options instead, otherwise users get a permission denied error from their shell when they attempt to login. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
to:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
May 05, 2006, at 09:28 PM by DM -- Made a mistake in previous update, no_root_squash is still needed.
Changed lines 50-51 from:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you want to allow non-root users you'll need to use the rw,no_all_squash options instead, otherwise users get a permission denied error from their shell when they attempt to login. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
to:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you want to allow non-root users you'll need to use the rw,no_root_squash,no_all_squash options instead, otherwise users get a permission denied error from their shell when they attempt to login. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
May 05, 2006, at 08:51 PM by DM -- Added a note about using \"no_all_squash\" for nfs shares, otherwise non-root users cannot log in.
Changed lines 50-51 from:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
to:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you want to allow non-root users you'll need to use the rw,no_all_squash options instead, otherwise users get a permission denied error from their shell when they attempt to login. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
April 19, 2006, at 12:28 PM by Kris Boyle -- Added information on MAC address change after flashing
Added lines 10-11:

Note: The MAC address of the Slug may change after flashing. If you are using the above DHCP reservation technique you will have to determine the new MAC address in order to make the reservation work again after flashing. It seems that the first three octets of the MAC address (the Organizationally Unique Identifier - OUI) change from the LinkSys? identifier to something new (reserved by the OpenSlug team???). If you do use reservations, make sure that you also have leases available so that the re-flashed Slug will get a new IP from your DHCP server. You should then be able to either check your DHCP server lease file or ping your gateway to determine the new Slug IP address. You will then need to update the MAC address in your DHCP reservation to get the Slug back to the IP address you want it on. Note that if you put the Slug into upgrade mode again it seems to revert to the original LinkSys? MAC address. If you are using reservations and think that you may be reflashing your Slug frequently using upgrade mode, it may be prudent to assign each MAC address to a unique IP address in your DHCP configuration file. The above behaviour was observed in flashing the OpenSlug-2.7-beta binary.

February 04, 2006, at 05:52 PM by endecotp -- Note what Samba is
Changed lines 60-61 from:

Probably one of the first things you want to do after initialising is install and configure Samba. If you are not very familiar in that area consult GettingStartedWithSamba.

to:

If you want to use your NSLU2 as a fileserver for Windows machines, probably one of the first things you want to do after initialising is to install and configure Samba. If you are not very familiar in that area consult GettingStartedWithSamba.

January 26, 2006, at 09:55 PM by frankvh -- Comment that vi is provided.
Added lines 30-31:

Note that the basic OpenSlug install includes the vi editor.

January 14, 2006, at 12:58 PM by JNC -- Forget
Changed lines 3-4 from:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg. [JNC : 2006, Jan.14th : Openslug 2.7 beta : the password was root].

to:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

January 14, 2006, at 10:23 AM by JNC -- Password issue
Changed lines 3-4 from:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

to:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg. [JNC : 2006, Jan.14th : Openslug 2.7 beta : the password was root].

December 17, 2005, at 02:00 PM by thx1011 -- Added link for info for Init Disks
Changed line 14 from:
  1. (If necessary) Use fdisk to create a partition on your destination disk. (consider making a swap partition as well) REBOOT the slug.
to:
  1. (If necessary) Use fdisk (OpenSlug.InitialisingDisks)to create a partition on your destination disk. (consider making a swap partition as well) REBOOT the slug.
October 23, 2005, at 09:02 AM by Terry Gray -- Must remount before you can delete from flash FS
Added lines 62-63:

If you reboot the system when the flash is full or close to full the NSLU2 will not be able to boot at all and you will have to reflash the image using UpSlug.

Changed lines 66-77 from:

If you reboot the system when the flash is full or close to full the NSLU2 will not be able to boot at all and you will have to reflash the image using UpSlug.

to:

NOTE: (teg update) If you want to delete anything from the internal flash filesystem, you must "remount" it as "read/write" using the following command:

 'mount -t jffs2 -o remount,rw /dev/mtdblock4 /initrd'

Then you can:

 'rm /initrd/boot/zImage*'

Remounting "RW" is also necessary if you accidentally run ""ipkg"" without an external root filesystem, and want to remove the files ipkg created, e.g. the big ones in ""/initrd/usr/lib/ipkg/""

October 21, 2005, at 09:09 AM by JimmyFergus --
Changed line 18 from:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>) (initialize swap on a differend device with mkswap <DEVICE>)
to:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>) (initialize swap on a different device with mkswap <DEVICE>)
October 21, 2005, at 09:07 AM by JimmyFergus --
Changed lines 46-47 from:
  • turnup nfs instead of turnup disk will allow you to use an NFS partition (see turnup help). It just works (but you need to know how to set up the NFS partition export correctly, using the no_root_squash option.) If you got any problems with a nfs root you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
to:
  • turnup nfs instead of turnup disk will allow you to run the machine without a disk, using an NFS export on another machine (see turnup help). It just works, but you need to know how to set up the NFS export correctly, using the rw,no_root_squash options. If you have any problems you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
October 21, 2005, at 09:04 AM by JimmyFergus --
Changed line 18 from:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>) (initialize swap with mkswap <DEVICE>)
to:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>) (initialize swap on a differend device with mkswap <DEVICE>)
Deleted lines 24-29:

-- Also Note that the above devices listed in #5 need to be diffrent. IE the swap cannot be the same disk as the one you just formatted.

-Roger --

Changed lines 46-47 from:
  • turnup nfs will allow you to use an NFS partition (see turnup help). It just works (but you need to know how to set up the NFS partition export correctly.) If you got any problems with a nfs root (turnup nfs ...) you can add a 'exec 2>>/boot.log >&2' to /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
to:
  • turnup nfs instead of turnup disk will allow you to use an NFS partition (see turnup help). It just works (but you need to know how to set up the NFS partition export correctly, using the no_root_squash option.) If you got any problems with a nfs root you can insert the line 'exec 2>>/boot.log >&2' into /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
October 21, 2005, at 08:58 AM by JimmyFergus --
Changed lines 3-6 from:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

Note: You might have to ping 192.168.1.255 to determine the device's new IP address. Mine changed from 192.168.1.77 to 192.168.1.107 after the installation over top of the stock firmware.

to:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

Note: You might have to ping 192.168.1.255 to determine the device's new IP address. Alternatively, check your DHCP server's client table. Installation over stock firmware will use DHCP if available, otherwise defaulting to 192.168.1.77

Changed lines 10-13 from:

Further initialisation is optional - it depends very much on what you want to do with OpenSlug. Some of the steps you can follow are:

Note: To reboot the NSLU2 use the "shutdown -r now" command not the power button.

to:

Further initialisation is optional - it depends very much on what you want to do with OpenSlug. turnup help gives some help. Some of the steps you can follow are:

Note: To reboot the NSLU2 use the "shutdown -r now" command not the power button. This advice may be out of date - version 2.7 does a graceful shutdown in response to the power button, but "shutdown -r now" is definitely safe.

Changed lines 52-53 from:
  • turnup nfs will allow you to use an NFS partition. It just works (but you need to know how to set up the NFS partition export correctly.) If you got any problems with a nfs root (turnup nfs ...) you can add a 'exec 2>>/boot.log >&2' to /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
to:
  • turnup nfs will allow you to use an NFS partition (see turnup help). It just works (but you need to know how to set up the NFS partition export correctly.) If you got any problems with a nfs root (turnup nfs ...) you can add a 'exec 2>>/boot.log >&2' to /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
October 10, 2005, at 02:40 AM by Roger Neumann -- Added comment about the drive to be booted into and swap need to be diffrent.
Added lines 25-30:

-- Also Note that the above devices listed in #5 need to be diffrent. IE the swap cannot be the same disk as the one you just formatted.

-Roger --

October 09, 2005, at 06:03 AM by jbowler -- Clarified removal of zImage*
Changed lines 62-63 from:

Once initialisation is complete you should remove /initrd/boot/zImage*. This removes the kernel image which releases about 800kbytes in the root flash partition. This provides some extra space to ensure that the system will be able to reboot. Actually this is only an issue if your root filesystem is very small (e.g. because it is on a memory stick)

to:

Once initialisation is complete you should remove /boot/zImage* from the flash file system. This removes the kernel image which releases about 800kbytes in the flash partition. This provides some extra space to ensure that the system will be able to reboot. Actually this is only an issue if your root filesystem is very small (e.g. because it is on a memory stick)

October 04, 2005, at 11:50 PM by AdyJoy -- Corrected -r option to shutdown
Changed lines 12-13 from:

Note: To reboot the NSLU2 use the "shutdown -h now" command not the power button.

to:

Note: To reboot the NSLU2 use the "shutdown -r now" command not the power button.

September 25, 2005, at 10:18 PM by bakotaco -- added swap partition information
Changed line 14 from:
  1. (If necessary) Use fdisk to create a partition on your destination disk. REBOOT the slug.
to:
  1. (If necessary) Use fdisk to create a partition on your destination disk. (consider making a swap partition as well) REBOOT the slug.
Changed line 18 from:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>)
to:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>) (initialize swap with mkswap <DEVICE>)
September 24, 2005, at 09:04 PM by JR -- Added a NOTE about possibly changed IP address
Added lines 5-6:

Note: You might have to ping 192.168.1.255 to determine the device's new IP address. Mine changed from 192.168.1.77 to 192.168.1.107 after the installation over top of the stock firmware.

September 21, 2005, at 10:26 PM by stanley_p_miller_qaz -- note on reboot method
Added lines 10-11:

Note: To reboot the NSLU2 use the "shutdown -h now" command not the power button.

September 05, 2005, at 11:47 AM by effem -- corrected path to zImage* so it points to the flash copy not the disk copy
Changed lines 58-59 from:

Once initialisation is complete you should remove /boot/zImage*. This removes the kernel image which releases about 800kbytes in the root flash partition. This provides some extra space to ensure that the system will be able to reboot. Actually this is only an issue if your root filesystem is very small (e.g. because it is on a memory stick)

to:

Once initialisation is complete you should remove /initrd/boot/zImage*. This removes the kernel image which releases about 800kbytes in the root flash partition. This provides some extra space to ensure that the system will be able to reboot. Actually this is only an issue if your root filesystem is very small (e.g. because it is on a memory stick)

September 05, 2005, at 11:46 AM by effem -- added ref to gettingstartedwithsamba
Added lines 54-55:

Probably one of the first things you want to do after initialising is install and configure Samba. If you are not very familiar in that area consult GettingStartedWithSamba.

September 04, 2005, at 10:49 AM by effem --
Changed lines 22-26 from:

There is no need that the partition is /dev/sda1. E.g. I used /dev/sda5

Most of these steps are standard administration operations. Those which use turnup, however, are NSLU2 specific. turnup exists to capture NSLU2 specific aspects of system setup in one place. It's a shell script, you can load it into an editor and see what it does. It even contains comments. Further details on using turnup are on the OpenSlug.OpenSlugTurnUp page.

to:

There is no need that the partition is /dev/sda1. However the current version only supports minor numbers up to and including 4. E.g. using /dev/sda5 does not work in 2.5beta. This will probably be fixed in a later release.

Most of these steps are standard administration operations. Those which use turnup, however, are NSLU2 specific. turnup exists to capture NSLU2 specific aspects of system setup in one place. It's a shell script, you can load it into an editor and see what it does. It even contains comments. Further details on using turnup are on the OpenSlug.OpenSlugTurnUp page.

September 04, 2005, at 02:49 AM by repvik --
Changed lines 14-15 from:
  1. Format a hard disk.
  2. mke2fs -j <DEVICE>
to:
  1. Format a hard disk (example: mkfs.ext3 <DEVICE>)
September 03, 2005, at 01:50 PM by effem -- added some more info; please proofread and correct as I am not a native english speaker
Changed lines 5-6 from:

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network. If you have a DHCP server on your network you should use dhcp as the boot protocol, not static (which is the default).

to:

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network. If you have a DHCP server on your network you may use dhcp as the boot protocol, not static (which is the default). Static has the advantage that you are always very sure about the IP address (which might be handy if things are not working). DHCP is convenient if your slug moves from network to network or if your network is big. With some DHCP servers you can make a reservation and make sure that a specific MAC address always gets the same IP address. DHCP servers in simple routers sometimes do not support this feature.

Changed lines 14-15 from:
  1. Format a hard disk. mke2fs -j <DEVICE>
to:
  1. Format a hard disk.
  2. mke2fs -j <DEVICE>
Changed lines 22-25 from:
to:

Of course you can also use an existing disk. E.g. if you used your disk before with unslung you could create an additional root partition (probably after resizing the existing partition first). That way you can skip the formatting step (5). There is no need that the partition is /dev/sda1. E.g. I used /dev/sda5

Changed lines 58-59 from:

Once initialisation is complete you should remove /boot/zImage*. This removes the kernel image which releases about 800kbytes in the root flash partition. This provides some extra space to ensure that the system will be able to reboot.

to:

Once initialisation is complete you should remove /boot/zImage*. This removes the kernel image which releases about 800kbytes in the root flash partition. This provides some extra space to ensure that the system will be able to reboot. Actually this is only an issue if your root filesystem is very small (e.g. because it is on a memory stick)

September 03, 2005, at 01:28 PM by effem -- added that for ssh the name is not needed; the ip address is also ok.
Changed lines 3-4 from:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. The initial password is opeNSLUg.

to:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. Of course you can also use the IP address. The initial password is opeNSLUg.

August 17, 2005, at 04:03 PM by blaster8 -- Formatting tweaks
Changed lines 1-2 from:

Using OpenSlug

to:

Using OpenSlug

Changed line 9 from:
  1. (If necessary) Use fdisk to create a partition on your destination disk. REBOOT the slug.
to:
  1. (If necessary) Use fdisk to create a partition on your destination disk. REBOOT the slug.
Changed line 14 from:
  1. Run turnup disk -i <DEVICE> -t ext3 to create a root filesystem on the disk. (Or turnup memstick -i <DEVICE> -t ext3)
to:
  1. Run turnup disk -i <DEVICE> -t ext3 to create a root filesystem on the disk. (Or turnup memstick -i <DEVICE> -t ext3)
Changed lines 18-20 from:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1.

to:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1.

August 17, 2005, at 03:57 PM by blaster8 -- Added note about using -t ext3 with turnup, so the ext3 fs is mounted as such
Changed line 14 from:
  1. Run turnup disk -i <DEVICE> to create a root filesystem on the disk. (Or turnup memstick -i <DEVICE>)
to:
  1. Run turnup disk -i <DEVICE> -t ext3 to create a root filesystem on the disk. (Or turnup memstick -i <DEVICE> -t ext3)
August 16, 2005, at 09:15 AM by Dan Scott -- Added link to OpenSlug.OpenSlugTurnUp
Changed lines 21-22 from:

Most of these steps are standard administration operations. Those which use turnup, however, are NSLU2 specific. turnup exists to capture NSLU2 specific aspects of system setup in one place. It's a shell script, you can load it into an editor and see what it does. It even contains comments.

to:

Most of these steps are standard administration operations. Those which use turnup, however, are NSLU2 specific. turnup exists to capture NSLU2 specific aspects of system setup in one place. It's a shell script, you can load it into an editor and see what it does. It even contains comments. Further details on using turnup are on the OpenSlug.OpenSlugTurnUp page.

July 23, 2005, at 09:17 PM by hanjo --
Changed lines 20-22 from:

If you got any problems with a nfs root (turnup nfs ...) you can add a 'exec 2>>/boot.log >&2' to /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.

to:
Changed lines 37-38 from:

The root file system doesn't have to be on a disk. turnup nfs will allow you to use an NFS partition. It just works (but you need to know how to set up the NFS partition export correctly.) turnup memstick is very similar to disk but it retains the RAM file systems to avoid putting frequently changing files on a USB flash device.

to:

The root file system doesn't have to be on a disk.

  • turnup nfs will allow you to use an NFS partition. It just works (but you need to know how to set up the NFS partition export correctly.) If you got any problems with a nfs root (turnup nfs ...) you can add a 'exec 2>>/boot.log >&2' to /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.
  • turnup memstick is very similar to disk but it retains the RAM file systems to avoid putting frequently changing files on a USB flash device.
July 23, 2005, at 09:05 PM by Anonymous -- reworked the last comment
Changed lines 20-21 from:

A 'turnup nfs' won't work without a proper netmask. It will hang while booting with the status led being solid amber.

to:

If you got any problems with a nfs root (turnup nfs ...) you can add a 'exec 2>>/boot.log >&2' to /boot/nfs and check /boot.log the next time it comes up. If it shows something like SIOCSIFNETMASK: Invalid argument, you probably have wrong subnetmask which results in broadcast failures and thus a nonworking nfs-root. With such a misconfiguration the nslu2 might hang while booting and showing a solid amber led.

July 23, 2005, at 09:02 PM by Anonymous -- A note that nfs rpc depends heavily on the netmask and broadcasts
Added lines 20-21:

A 'turnup nfs' won't work without a proper netmask. It will hang while booting with the status led being solid amber.

July 10, 2005, at 12:27 PM by KGP --
Changed line 9 from:
  1. (If necessary) Use fdisk to create a partition on your destination disk. REBOOT the slug...
to:
  1. (If necessary) Use fdisk to create a partition on your destination disk. REBOOT the slug.
Changed line 14 from:
  1. Run turnup disk -i <DEVICE> to create a root filesystem on the disk.
to:
  1. Run turnup disk -i <DEVICE> to create a root filesystem on the disk. (Or turnup memstick -i <DEVICE>)
July 10, 2005, at 12:26 PM by KGP --
Added line 9:
  1. (If necessary) Use fdisk to create a partition on your destination disk. REBOOT the slug...
Changed lines 18-21 from:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1 .

Don't forget to make a partition on this disk using fdisk. Do NOT use mke2fs on a DEVICE where you have some data.

to:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1.

July 05, 2005, at 08:12 PM by KGP --
Changed lines 17-19 from:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1 Don't forget to make a partition on this disk using fdisk.

to:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1 .

Don't forget to make a partition on this disk using fdisk. Do NOT use mke2fs on a DEVICE where you have some data.

July 05, 2005, at 08:11 PM by KGP --
Added lines 17-19:

Please note that <DEVICE> is /dev/sda1 or /dev/sdb1 Don't forget to make a partition on this disk using fdisk.

July 02, 2005, at 01:37 AM by henningsprangde --
Changed lines 12-13 from:
  1. Format a hard disk.
  2. Run turnup disk.
to:
  1. Format a hard disk. mke2fs -j <DEVICE>
  2. Run turnup disk -i <DEVICE> to create a root filesystem on the disk.
June 23, 2005, at 02:44 AM by jbowler --
Changed lines 3-8 from:

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network.

If you wish to set up the password and network yourself the message displayed on log in can be eliminated by removing /etc/motd. turnup init will do this when it is run.

After running turnup init and any additional system configuration you require you should run turnup disk or turnup nfs to create a new root partition on an attached hard disk or on an NFS partition. turnup includes help which explains the parameters required - turnup help.

to:

After loading the flash image into your NSLU2 the box will reboot. Eventually the ready/status LED will be solid green. At this point you can log in using ssh (this is the only way of logging in initially.) You must log in as root. The default name of the NSLU2 is on the MAC Address label on the bottom of the box. The initial password is opeNSLUg.

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network. If you have a DHCP server on your network you should use dhcp as the boot protocol, not static (which is the default).

Further initialisation is optional - it depends very much on what you want to do with OpenSlug. Some of the steps you can follow are:

  1. Run turnup init
  2. Do extra network configuration
  3. If necessary (see below) install packages to allow the NSLU2 to function correctly in your network.
  4. Format a hard disk.
  5. Run turnup disk.
  6. Reboot to the new disk partition.
  7. Install packages and configure the NSLU2.

Most of these steps are standard administration operations. Those which use turnup, however, are NSLU2 specific. turnup exists to capture NSLU2 specific aspects of system setup in one place. It's a shell script, you can load it into an editor and see what it does. It even contains comments.

Further details

At present this page is incomplete. No one really knows how OpenSlug will be used, so the information required for the typical user is difficult to determine. The rest of this wiki contains a vast amount of information relevant to OpenSlug. Much of the information gained from Unslung has relevance for OpenSlug.

What follows is basic information about how to configure an NSLU2 before turnup disk - in other words what can be, what should be, and what should not be done to the flash file system.

The flash file system is both a recovery file system - it works even if something goes wrong with the root file system on the disk - and a prototype file system. What is on the flash is copied to a new rootfs by turnup - so stuff necessary to be able to boot into a different root file system should be on the flash file system.

Avoiding turnup init

If you wish to set up the password and network yourself the message displayed on log in can be eliminated by removing /etc/motd. turnup init will do this when it is run. Network setup is concentrated in /etc/network/interfaces, but there is a hand-crafted script for udhcpc which ensures that the network is set up with the default (LinkSys?) static address 192.168.1.77 if DHCP fails.

Other options to turnup

The root file system doesn't have to be on a disk. turnup nfs will allow you to use an NFS partition. It just works (but you need to know how to set up the NFS partition export correctly.) turnup memstick is very similar to disk but it retains the RAM file systems to avoid putting frequently changing files on a USB flash device.

Package installation

Added lines 41-44:

If you have to run ipkg update to install files try to delete the downloaded information afterward. It is better to install the packages you require by copying them to /tmp and using ipkg install <file>. This avoids the overhead of downloading all the package information.

Gaining space on the flash file system

June 23, 2005, at 01:58 AM by jbowler --
Added lines 1-15:

Using OpenSlug

When OpenSlug is first booted a small amount of initialisation is required. Simply follow the instructions displayed when you first log in. These instructions say to run the command turnup init - this command prompts for information and setups up the root password and network.

If you wish to set up the password and network yourself the message displayed on log in can be eliminated by removing /etc/motd. turnup init will do this when it is run.

After running turnup init and any additional system configuration you require you should run turnup disk or turnup nfs to create a new root partition on an attached hard disk or on an NFS partition. turnup includes help which explains the parameters required - turnup help.

It is essential to change the root file system before doing any package installation. There is insufficient space on the flash file system for any significant amount of package installation.

It is possible to install one or two very small packages - such as ntp - and it may be necessary to install some packages (such as openldap) to make the NSLU2 work properly in your network. Be very careful if you choose to do this - be prepared for package installation to fail.

Once initialisation is complete you should remove /boot/zImage*. This removes the kernel image which releases about 800kbytes in the root flash partition. This provides some extra space to ensure that the system will be able to reboot.

If you reboot the system when the flash is full or close to full the NSLU2 will not be able to boot at all and you will have to reflash the image using UpSlug.

Page last modified on February 04, 2008, at 07:24 PM