NSLU2-Linux
view · edit · print · history

Before you go any further...

You will need either an unslung-able-2.x release or an unslung-3.x release to get the required USB support in firmware.

The unslung-3.x release is available as a binary beta release for public download. Please visit the SourceForge download page at https://sourceforge.net/project/showfiles.php?group_id=116564 to obtain the firmware image and the relevant instructions for installation. Please make sure that you follow the instructions precisely. Do not skip any steps, and do not skip ahead thinking you know what you are doing and don't need to follow instructions step by step.

Typographic conventions.

  • Stuff in green boxes is what you should be typing in at the shell prompt.
  • Stuff in blue boxes is things that should go inside a file mentioned in the body of the text.
  • Stuff in pink boxes are the things you should see as a result of you doing something.

Installing puppy

First you need a working Internet connection to download and install any software.

 ipkg update
 ipkg install puppy

Upgrading the NSLU2 to handle large files and making new files accessible to everyone.

 ipkg update
 ipkg install busybox

Once the above completes without errors, put the following lines into a file named ~/.profile to configure your shell environment, You can use the vi editor to edit the file. See ViCrashCourse for some very basic instructions on how to use vi.

 PATH=/opt/sbin:/opt/bin:$PATH
 export PATH
 umask 0

The umask line makes sure that all users are granted full access to any new files created. This is normally considered insecure, but it will make life easier for those who don't understand any Linux.

Now change the permissions of the shell configuration file.

 chmod 755 ~/.profile

Now log in from another shell to verify that there are no problems with your ~/.profile and that you can still access your NSLU2 over the network. If things are working correctly, you should issue this command:

 which ls

and see this response:

 /opt/bin/ls

If everything looks good at this stage, close the old shell and keep using the new shell with the updated environment. If things are not right, use your original shell to fix things up before you close that shell.

Mounting a share from a network connected PC

This command will create a mount point, mount the network drive and create a link (shortcut) to the network drive in your current directory.

 mkdir -p /mnt/smb/computername/sharename
 smbmount //computername/sharename /mnt/smb/computername/sharename -o username=myName,password=myPassword
 ln -s /mnt/smb/computername/sharename sharename

Obviously you will need to replace computername, sharename, myName and myPassword with values that are appropriate for your configuration.

Transfering files from the Toppy directly to a network share on another PC.

Once you have mounted the netowrk share as detailed above, you can transfer directly to the remote PC.

 puppy -c get 'DataFiles\Enterprise-4.rec' sharename/video/Enterprise/Rajiin.rec

Changing file permissions

The following will grant both read and write permissions for the named file to all users:

 chmod a+rw FileName

Installing secure shell

Rather than manually enabling telnet on every reboot, you can install a secure shell, which will be enabled on every reboot.

 ipkg update
 ipkg install openssl
 ipkg install openssh
view · edit · print · history · Last edited by peteru.
Originally by peteru.
Page last modified on April 14, 2005, at 10:26 PM