NSLU2-Linux
view · edit · print · history

Puppy.ConfiguringNSLU2 History

Hide minor edits - Show changes to markup

January 27, 2005, at 02:17 PM by peteru --
Added line 1:

Before you go any further...

Added lines 5-88:

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. table border=0 width=100% bgcolor=#eeffee? cell?

 ipkg update
 ipkg install puppy

tableend?

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

table border=0 width=100% bgcolor=#eeffee? cell?

 ipkg update
 ipkg install busybox

tableend?

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. table border=0 width=100% bgcolor=#eeeeff? cell?

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

tableend? 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. table border=0 width=100% bgcolor=#eeffee? cell?

 chmod 755 ~/.profile

tableend?

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: table border=0 width=100% bgcolor=#eeffee? cell?

 which ls

tableend? and see this response: table border=0 width=100% bgcolor=#ffeeee? cell?

 /opt/bin/ls

tableend?

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. table border=0 width=100% bgcolor=#eeffee? cell?

 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

tableend? 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. table border=0 width=100% bgcolor=#eeffee? cell?

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

tableend?

Changing file permissions

The following will grant both read and write permissions for the named file to all users: table border=0 width=100% bgcolor=#eeffee? cell?

 chmod a+rw FileName

tableend?

Installing secure shell

Rather than manually enabling telnet on every reboot, you can install a secure shell, which will be enabled on every reboot. table border=0 width=100% bgcolor=#eeffee? cell?

 ipkg update
 ipkg install openssl
 ipkg install openssh

tableend?

January 23, 2005, at 06:32 AM by peteru --
Changed line 3 from:

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. %red%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.

to:

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. %red%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.

January 23, 2005, at 06:31 AM by peteru --
Deleted line 1:

At the time these instructions are being published, the unslung-3.x release is being prepared for beta and is not available for public download in binary form just yet. unslung-3.x alpha can be built from sources by anyone, please see instructions at OpenEmbedded.GettingStarted

Changed line 3 from:

The firmware image for unslung-able-2.x is available only by request for limited beta testing. Please contact toppy at urbanec dot net to obtain a copy of the firmware image.

to:

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. %red%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.

December 19, 2004, at 02:32 PM by peteru --
Changed lines 1-4 from:

Describe ConfiguringNSLU2 here.

to:

You will need either an unslung-able-2.x release or an unslung-3.x release to get the required USB support in firmware. At the time these instructions are being published, the unslung-3.x release is being prepared for beta and is not available for public download in binary form just yet. unslung-3.x alpha can be built from sources by anyone, please see instructions at OpenEmbedded.GettingStarted

The firmware image for unslung-able-2.x is available only by request for limited beta testing. Please contact toppy at urbanec dot net to obtain a copy of the firmware image.

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