NSLU2-Linux
view · edit · print · history

OpenWrt.HomePage History

Hide minor edits - Show changes to markup

February 01, 2011, at 12:32 AM by OddballHero -- Backfile 10.03
Changed line 205 from:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management (Administration->System->LED Configuration) feature (works quite well) or edit the /etc/config/system after installing kmod-leds-gpio. GPIO Connections has some information to help with the setup. Sample /etc/config/system entry:
to:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management (Administration->System->LED Configuration) feature (works quite well) or edit the /etc/config/system. GPIO Connections has some information to help with the setup. Sample /etc/config/system entry:
February 01, 2011, at 12:19 AM by OddballHero -- Backfile 10.03
Changed lines 185-186 from:
  • If you want to keep eth0 static, you can just add "option gateway xxx.xxx.xxx.xxx" and "option dns xxx.xxx.xxx.xxx".
to:
  • If you want to keep eth0 static, you can just add "option gateway xxx.xxx.xxx.xxx" and "option dns xxx.xxx.xxx.xxx" to "option ipaddr xxx.xxx.xxx.xxx", "option netmask xxx.xxx.xxx.xxx", and "option proto static".
Changed lines 205-206 from:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management feature (works quite well) or edit the /etc/config/system after installing kmod-leds-gpio. GPIO Connections has some information to help with the setup.
to:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management (Administration->System->LED Configuration) feature (works quite well) or edit the /etc/config/system after installing kmod-leds-gpio. GPIO Connections has some information to help with the setup. Sample /etc/config/system entry:
config 'led'
      option 'name' 'GPIO2'
      option 'sysfs' 'nslu2:green:disk-2'
      option 'default' '1'
      option 'trigger' 'default-on'
Where additional choices for sysfs are 'nslu2:green:disk-1', 'nslu2:green:ready', and 'nslu2:red:status'.
Changed lines 220-250 from:
  • For system that will interact with Vista and newer Microsoft OS, it might be worth it to install samba3 instead of samba-server. No need to use regedit and less problems in the future.
to:
  • For system that will interact with Vista and newer Microsoft OS, it might be worth it to install samba3 instead of samba-server. No need to use regedit and less problems in the future. Sample smb.conf for samba3 (please modify to fit your security needs and system requirements):
[global]
        netbios name = Openwrt
        workgroup = WORKGROUP
        server string = NSLU2 OpenWrt Samba Server
        syslog = 10
        encrypt passwords = true
        passdb backend = smbpasswd
        obey pam restrictions = yes
        socket options = TCP_NODELAY
        unix charset = ISO-8859-1
        preferred master = yes
        os level = 20
        security = share
        guest account = root
        invalid users = guest
        smb passwd file = /etc/samba/smbpasswd

[HDD_1_1_1]
        comment = NSLU2 OpenWRT HD 1
        available = yes
        browseable = yes
        public = yes
        writeable = yes
        create mask = 0777
        path = /mnt/drive1
        read only = no
        guest ok = yes

January 31, 2011, at 09:44 PM by OddballHero -- Backfile 10.03
Changed lines 159-160 from:

Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03.

to:

Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03.

January 31, 2011, at 09:43 PM by OddballHero -- Backfile 10.03
Changed lines 159-160 from:

Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03.

to:

Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03.

January 31, 2011, at 09:40 PM by OddballHero -- Backfile 10.03
Changed lines 205-206 from:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management feature (works quite well) or edit the /etc/config/system. GPIO Connections has some information to help with the setup.
to:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management feature (works quite well) or edit the /etc/config/system after installing kmod-leds-gpio. GPIO Connections has some information to help with the setup.
January 31, 2011, at 09:35 PM by OddballHero -- Backfile 10.03
Changed lines 159-162 from:

Configuring DHCP and USB ports in OpenWRT? Kamikaze 8.09 and Backfire 10.03.

The current (April 2009) OpenWRT? bin image is hard coded to 192.168.1.1 and does not include USB port support by default. After upslugging the new 8.09 image to your NSLU2, you will need to telnet to it and make some minor reconfigurations. The 10.03 image also works the same way.

to:

Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03.

The current (April 2009) OpenWRT bin image is hard coded to 192.168.1.1 and does not include USB port support by default. After upslugging the new 8.09 image to your NSLU2, you will need to telnet to it and make some minor reconfigurations. The 10.03 image also works the same way.

Changed lines 205-206 from:
  • Backfire 10.03 Has most of the lights turned off (except for Ethernet) so use the either the web management feature (works quite well) or edit the /etc/config/system. GPIO Connections has some information to help with the setup.
to:
  • Backfire 10.03 has most of the lights turned off (except for Ethernet) so use the either the web management feature (works quite well) or edit the /etc/config/system. GPIO Connections has some information to help with the setup.
January 31, 2011, at 09:31 PM by OddballHero -- Backfile 10.03
Changed lines 159-162 from:

Configuring DHCP and USB ports in OpenWRT? Kamikaze 8.09 and Backfire

The current (April 2009) OpenWRT? bin image is hard coded to 192.168.1.1 and does not include USB port support by default. After upslugging the new 8.09 image to your NSLU2, you will need to telnet to it and make some minor reconfigurations.

to:

Configuring DHCP and USB ports in OpenWRT? Kamikaze 8.09 and Backfire 10.03.

The current (April 2009) OpenWRT? bin image is hard coded to 192.168.1.1 and does not include USB port support by default. After upslugging the new 8.09 image to your NSLU2, you will need to telnet to it and make some minor reconfigurations. The 10.03 image also works the same way.

Added lines 185-186:
  • If you want to keep eth0 static, you can just add "option gateway xxx.xxx.xxx.xxx" and "option dns xxx.xxx.xxx.xxx".
Added lines 203-206:
  • After booting or rebooting your system and if you want to add a package, do not forget to opkg update, since the package repository list is written to /tmp.
  • Backfire 10.03 Has most of the lights turned off (except for Ethernet) so use the either the web management feature (works quite well) or edit the /etc/config/system. GPIO Connections has some information to help with the setup.
Changed lines 212-213 from:
to:
  • Use httpd to serve your own web site and Webif
  • For system that will interact with Vista and newer Microsoft OS, it might be worth it to install samba3 instead of samba-server. No need to use regedit and less problems in the future.
October 23, 2010, at 06:24 PM by weirdow -- addendum for usb2 and openwrt backfire
Changed lines 159-160 from:

Configuring DHCP and USB ports in OpenWRT? 8.09

to:

Configuring DHCP and USB ports in OpenWRT? Kamikaze 8.09 and Backfire

Changed line 191 from:

opkg install kmod-usb-core kmod-usb-ohci kmod-scsi-core kmod-usb-storage kmod-usb-serial

to:

opkg install kmod-usb-core kmod-usb2 kmod-usb-ohci kmod-scsi-core kmod-usb-storage kmod-usb-serial

September 26, 2010, at 12:03 PM by ooswald --
Changed lines 17-18 from:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 (or 192.168.1.1 for version 8.09 and later, some people also encountered a DHCP assigned address) to which you need to telnet to get access for the first time. Note that the Ready/Status LED may remain dark, even if the system is up and running.

to:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 (or 192.168.1.1 for version 8.09 and later, some people also encountered a DHCP assigned address) to which you need to telnet to get access for the first time.

Note that the Ready/Status LED may remain dark in Backfire, even if the system is up and running. Change in Administration -> System -> LED Configuration.

September 26, 2010, at 11:42 AM by ooswald -- Updated with OpenWrt Backfire
Changed lines 11-12 from:

You can either build kamikaze, download the kamikaze-7.09 image from http://www.slug-firmware.net, or install the updated default image (version 8.09) from the OpenWrt project at http://downloads.openwrt.org/kamikaze/8.09/ixp4xx/openwrt-nslu2-squashfs.bin. Installation is the same in all cases.

to:

You can either build kamikaze, download the kamikaze-7.09 image from http://www.slug-firmware.net, or install the updated default image (version 8.09) from the OpenWrt project at http://downloads.openwrt.org/kamikaze/8.09/ixp4xx/openwrt-nslu2-squashfs.bin, or install 10.03.1-rc3 (aka Backfire) from http://downloads.openwrt.org/backfire/10.03.1-rc3/ixp4xx/openwrt-nslu2-squashfs.bin (or later). Installation is the same in all cases.

Changed lines 17-18 from:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 to which you need to telnet to get access for the first time. Version 8.09 (the current release) will have the IP address 192.168.1.1 .

to:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 (or 192.168.1.1 for version 8.09 and later, some people also encountered a DHCP assigned address) to which you need to telnet to get access for the first time. Note that the Ready/Status LED may remain dark, even if the system is up and running.

Changed line 32 from:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building. 8.09 uses 192.168.1.1 as the default.
to:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building. 8.09 and later use 192.168.1.1 as the default.
August 15, 2010, at 09:53 PM by krim -- typo
Changed line 201 from:
to:
May 23, 2009, at 07:58 PM by Hein Rigolo -- Add option to add an alias on eth0
Changed lines 163-164 from:
  • Reconfigure the IP address of your host system's ethernet port so that its in the same subnet as the freshly imaged NSLU2. ifconfig eth0 192.168.1.254
to:
  • Reconfigure the IP address of your host system's ethernet port so that its in the same subnet as the freshly imaged NSLU2. ifconfig eth0 192.168.1.254 or sudo ifconfig eth0:1 inet 192.168.1.254 broadcast 192.168.1.255 netmask 255.255.255.0
April 06, 2009, at 05:26 AM by stefan keller-tuberg --
Added lines 194-198:
  • You can also remove packages which may not be useful for your NSLU2 configuration
opkg remove -recursive ppp-mod-pppoe wireless-tools
(as examples)
April 06, 2009, at 05:17 AM by stefan keller-tuberg --
April 06, 2009, at 05:17 AM by stefan keller-tuberg --
Added line 191:

opkg install kmod-nls-base kmod-nls-cp437 kmod-nls-cp850 kmod-nls-utf8 kmod-nls-iso8859-1 kmod-nls-iso8859-2

April 06, 2009, at 05:02 AM by stefan keller-tuberg --
Added lines 183-184:
  • You can now reboot your NSLU2 by typing the command reboot. When it comes back up, it will fetch its IP address using your local DHCP server. You can now telnet to it directly from your local subnet without having to reconfigure your host terminal's ethernet port into the 192.168.1.0 subnet. Note that you'll need to query your DHCP server to find out what address its given the NSLU2!
April 06, 2009, at 04:59 AM by stefan keller-tuberg --
Added line 162:
Added line 164:
Added line 166:
Added line 168:
Changed lines 183-190 from:
to:
  • Install whatever opkg packages you require as follows (example)
opkg update
opkg install e2fsprogs cfdisk fdisk swap-utils usbutils
opkg install kmod-usb-core kmod-usb-ohci kmod-scsi-core kmod-usb-storage kmod-usb-serial
opkg install kmod-fs-msdos kmod-fs-nfs kmod-fs-nfsd kmod-fs-ntfs kmod-fs-vfat kmod-fs-ext2 kmod-fs-ext3
(Note. You must run opkg update each time you reboot the NSLU2)
April 06, 2009, at 04:55 AM by stefan keller-tuberg -- Notes for openwrt 8.09
Changed lines 42-43 from:

Optware packages use their own ipkg-opt packaging system that is independent of firmware. This also means that when upgrading OpenWrt theb Optware package list is not erased as it is stored in the /opt partition where also all Optware packages are installed.

to:

Optware packages use their own ipkg-opt packaging system that is independent of firmware. This also means that when upgrading OpenWrt theb Optware package list is not erased as it is stored in the /opt partition where also all Optware packages are installed.

Note: For OpenWrt 8.09, the command is called opkg, not ipkg

Added lines 157-179:

Configuring DHCP and USB ports in OpenWRT? 8.09

The current (April 2009) OpenWRT? bin image is hard coded to 192.168.1.1 and does not include USB port support by default. After upslugging the new 8.09 image to your NSLU2, you will need to telnet to it and make some minor reconfigurations.

The following instructions are if you're using a linux system. Adapt to suit other environments.

  • Reconfigure the IP address of your host system's ethernet port so that its in the same subnet as the freshly imaged NSLU2. ifconfig eth0 192.168.1.254
  • Telnet to the freshly imaged NSLU2. telnet 192.168.1.1
  • Disable the dnsmasq and firewall services that are on by default. /etc/init.d/dnsmasq disable and /etc/init.d/firewall disable
  • Rewrite the /etc/config/network file as follows:
cat > /etc/config/network
config interface loopback
        option ifname   lo
        option proto    static
        option ipaddr   127.0.0.1
        option netmask  255.0.0.0

config interface lan
        option ifname   eth0
        option proto    dhcp
(press CTRL-D to close the file)
March 02, 2009, at 02:21 AM by JohnPaulLorenti --
Changed lines 11-12 from:

You can either build kamikaze, download the kamikaze-7.09 image from http://www.slug-firmware.net, or install the updated default image from the OpenWrt project at http://downloads.openwrt.org/kamikaze/8.09/ixp4xx/openwrt-nslu2-squashfs.bin. Installation is the same in all cases.

to:

You can either build kamikaze, download the kamikaze-7.09 image from http://www.slug-firmware.net, or install the updated default image (version 8.09) from the OpenWrt project at http://downloads.openwrt.org/kamikaze/8.09/ixp4xx/openwrt-nslu2-squashfs.bin. Installation is the same in all cases.

March 02, 2009, at 02:19 AM by JohnPaulLorenti --
Changed lines 11-12 from:

You can either build kamikaze or download the kamikaze-7.09 image from http://www.slug-firmware.net. Installation is the same in both cases. You can find the developpement version (8.09RC1 in november 2008) in http://downloads.openwrt.org/kamikaze/8.09_RC1/ for sources or NSLU2 image in the ixp4xx directory.

to:

You can either build kamikaze, download the kamikaze-7.09 image from http://www.slug-firmware.net, or install the updated default image from the OpenWrt project at http://downloads.openwrt.org/kamikaze/8.09/ixp4xx/openwrt-nslu2-squashfs.bin. Installation is the same in all cases.

Changed lines 17-18 from:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 to which you need to telnet to get access for the first time.

to:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 to which you need to telnet to get access for the first time. Version 8.09 (the current release) will have the IP address 192.168.1.1 .

Changed line 32 from:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building.
to:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building. 8.09 uses 192.168.1.1 as the default.
January 23, 2009, at 04:41 PM by AdamBaker -- Add httpd shharing link
Changed lines 159-160 from:
  • Back up the flash
to:
January 07, 2009, at 12:41 AM by sf -- some more tips
Changed lines 37-40 from:
to:
  • Make sure you use the ehci driver (kmod-usb2) and not the ohci driver! You can test it with "hdparm -Tt /dev/sda" (or what you have instead of /dev/sda).
  • The package management program is now called "opkg"
  • Remember that you require "opkg update" after each restart, because openwrt stores the package descriptions in the /tmp directory and it gets deleted after every restart.
January 04, 2009, at 02:08 AM by lbenson -- Add link to back up flash
Changed lines 155-156 from:
  • UsbStorageHowto
to:
  • UsbStorageHowto
  • Back up the flash
November 13, 2008, at 11:27 AM by Vincent -- Updates for OpenWrt: more project description and version updates
Changed lines 1-6 from:

OpenWrt Kamikaze supports the NSLU2. See the KnownProblems page for known problems with the Kamikaze 7.07 release.

You can either build kamikaze or download the kamikaze-7.07 image from http://www.slug-firmware.net. Installation is the same in both cases.

From the HomePage, "The OpenWrt Kamikaze 7.09 release of firmware is in beta testing. A binary firmware download can be found at http://www.slug-firmware.net. Please report beta testing results to the nslu2-linux mailing list."

to:

OpenWrt is an open source project to create a free embedded operating system for network devices. Users wanting to use only internal flash memory to install the system should try OpenWrt. It has a large user community and is actively developped. SVN version (November 2008) for example uses linux-2.6.26.7.

OpenWrt Kamikaze supports the NSLU2. It has some advantages over SlugOS or other NSLU OS:

  • Since at its beginnings it targeted wireless embedded hardware, OpenWrt has full support of wireless hardware and software. For example, it ships the rt73 driver which can be sometimes complicated to install on other OS.
  • It uses µClibc by default, and the squashfs compressed read-only filesystem, giving a lot of free space on the internal flash. For example, a minimal image, with dropbear, busybox µClibc and wireless tools can take 832kB. Since this image is read-only, OpenWrt uses a JFFS2 for writeable space (still 5632kB in my case), allowing users to install software after the main image configuration.
  • With SlugOS, you basically spend time to remove what's unneeded, with OpenWrt, you spend time adding what you need.
  • Configuration and building the image is user-friendly, with make menuconfig. Including software in the firmware image or building it for packages is explicit and easy.

See the KnownProblems page for known problems with the Kamikaze 7.07 release.

You can either build kamikaze or download the kamikaze-7.09 image from http://www.slug-firmware.net. Installation is the same in both cases. You can find the developpement version (8.09RC1 in november 2008) in http://downloads.openwrt.org/kamikaze/8.09_RC1/ for sources or NSLU2 image in the ixp4xx directory.

Added lines 15-16:

There is some good documentation at http://nbd.name/openwrt.html. See also the OpenWrt wiki entry for the NSLU2 at OpenWrt wiki, which contains more information.

Deleted lines 18-19:

There is some good documentation at http://nbd.name/openwrt.html. See also the OpenWrt wiki entry for the NSLU2 at OpenWrt wiki, which contains more information.

Changed lines 32-33 from:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building. (true for pre-7.09 releases only?)
  • By default, both telnet and ssh are installed, but only telnet is enabled. To enable ssh and disable telnet (a very good choice, security-wise), telnet to the slug and then use the 'passwd' command to change your root password. The rest seems to be automatic.
to:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building.
  • By default, both telnet and ssh are installed, but only telnet is enabled. To enable ssh and disable telnet (a very good choice, security-wise), telnet to the slug and then use the 'passwd' command to change your root password. The rest seems to be automatic.
Changed lines 39-42 from:

Optware packages use their own ipkg-opt packaging system that is independent of firmware. This also means that when upgrading OpenWrt theb Optware package list is not erased as it is stored in the /opt partition where also all Optware packages are installed.

to:

Optware packages use their own ipkg-opt packaging system that is independent of firmware. This also means that when upgrading OpenWrt theb Optware package list is not erased as it is stored in the /opt partition where also all Optware packages are installed.

Changed lines 74-81 from:

Some Optware packages rely on libraries that are optional OpenWRT packages. Because these come from different repositories they can't easily be configured as dependencies. Either install the OpenWRT packages libssp, libpthread and libstdc++ now or be ready to install them if something breaks.

Optware also has a few other assumptions that aren't met by OpenWRT, it assumes that users called mail and lp exist in the password file so make sure you create them before installing email or printer spooler software. Another assumption is that /etc/services contains a sensible list of ports - I copied the file from another machine.

to:

Some Optware packages rely on libraries that are optional OpenWRT packages. Because these come from different repositories they can't easily be configured as dependencies. Either install the OpenWRT packages libssp, libpthread and libstdc++ now or be ready to install them if something breaks.

Optware also has a few other assumptions that aren't met by OpenWRT, it assumes that users called mail and lp exist in the password file so make sure you create them before installing email or printer spooler software. Another assumption is that /etc/services contains a sensible list of ports - I copied the file from another machine.

July 20, 2008, at 08:14 PM by BrianZhou -- make code ready for copy-n-paste
Changed lines 95-96 from:
 #!/bin/sh /etc/rc.common
to:

[@

  1. !/bin/sh /etc/rc.common
Changed line 98 from:
 START=80
to:

START=80

Changed lines 100-103 from:
 start() {
         echo "Starting Optware."
         [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware start
         }
to:

start() {

        echo "Starting Optware."
        [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware start
        }
Changed lines 105-109 from:
 stop() {
         echo "Shutting down Optware."
         [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware stop
        }
to:

stop() {

        echo "Shutting down Optware."
        [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware stop
       }

@]

Changed lines 113-114 from:
 #!/bin/sh
to:

[@

  1. !/bin/sh
Changed lines 116-124 from:
 # Start all init scripts in /opt/etc/init.d
 # executing them in numerical order.
 #
 if [ x$1 == xstop ] ; then
         progs="/opt/etc/init.d/K??*"
         rc=stop
 else
         progs="/opt/etc/init.d/S??*"
         rc=start
to:
  1. Start all init scripts in /opt/etc/init.d
  2. executing them in numerical order.

if [ x$1 == xstop ] ; then

        progs="/opt/etc/init.d/K??*"
        rc=stop

else

        progs="/opt/etc/init.d/S??*"
        rc=start

fi

Changed lines 127-150 from:
 fi

 for i in $progs ;do

         # Ignore dangling symlinks (if any).
         [ ! -f "$i" ] && continue

         echo starting $i
         case "$i" in
            *.sh)
                 # Source shell script for speed.
                 (
                         trap - INT QUIT TSTP
                         set $rc
                         . $i
                 )
                 ;;
            *)
                 # No sh extension, so fork subprocess.
                 $i $rc
                 ;;
         esac
 done
to:

for i in $progs ;do

        # Ignore dangling symlinks (if any).
        [ ! -f "$i" ] && continue

        echo starting $i
        case "$i" in
           *.sh)
                # Source shell script for speed.
                (
                        trap - INT QUIT TSTP
                        set $rc
                        . $i
                )
                ;;
           *)
                # No sh extension, so fork subprocess.
                $i $rc
                ;;
        esac

done @]

June 16, 2008, at 11:11 PM by BrianZhou -- see also openwrt UsbStorageHowto
Changed lines 151-152 from:
to:
May 15, 2008, at 09:39 PM by AdamBaker -- Tidy up English
Added line 38:
Added line 42:
Changed lines 60-61 from:

To ensure partitions are remounted after a reboot you need to add these commands to a startup script, I recommend /etc/init.d/custom-user-startup until new kamikaze builds supporting /etc/config/fstab are released

to:

To ensure partitions are remounted after a reboot you need to add the mount and swapon commands to a startup script, I recommend /etc/init.d/custom-user-startup until new kamikaze builds (after 7.09) supporting /etc/config/fstab are released

Changed line 79 from:

issuing /opt/etc/ipkg-opt update and installing aditional Optware packages. Depending upon how you use the slug

to:

issuing /opt/etc/ipkg-opt update and installing additional Optware packages. Depending upon how you use the slug

May 15, 2008, at 09:36 PM by AdamBaker -- Markup fixes etc
Changed lines 34-35 from:

with OpenWrt upgrade package list is not erased as it is stored in /opt partition where also all optware packages are installed.

to:

when upgrading OpenWrt theb Optware package list is not erased as it is stored in the /opt partition where also all Optware packages are installed.

Changed line 38 from:

[@ ipkg update

to:

[@ipkg update

Changed lines 42-43 from:

Allocate at least 2GB for /opt and 512MB for swap (AdamB? - 512MB seems excessive, I stuck to the unslung size of 120MB).

to:

Allocate at least 2GB for /opt and 512MB for swap (AdamB - 512MB seems excessive, I stuck to the unslung size of 120MB).

Changed lines 58-59 from:

To ensure partitions are remounted after a reboot you need to add these commands to a startup script, I recommend /etc/init.d/custom-user-startup until new builds supporting /etc/config/fstab are released

to:

To ensure partitions are remounted after a reboot you need to add these commands to a startup script, I recommend /etc/init.d/custom-user-startup until new kamikaze builds supporting /etc/config/fstab are released

Changed lines 66-69 from:

This will install required /opt/bin/ipkg-opt. I recommend removing the Optware package feeed from /etc/ipkg.conf and add the same line to /opt/etc/ipkg.conf.

Some optware packages rely on libraries that are optional OpenWRT? packages. Because these come from different repositories they can't be configured as dependencies. Either install the OpenWRT? packages libssp, libpthread and

to:

This will install required /opt/bin/ipkg-opt. I recommend removing the Optware package feed from /etc/ipkg.conf and add the same line to /opt/etc/ipkg.conf.

Some Optware packages rely on libraries that are optional OpenWRT packages. Because these come from different repositories they can't easily be configured as dependencies. Either install the OpenWRT packages libssp, libpthread and

Changed line 72 from:

Optware also has a few other assumptions that aren't met by OpenWRT?, it assumes that users called mail and lp exist

to:

Optware also has a few other assumptions that aren't met by OpenWRT, it assumes that users called mail and lp exist

Changed line 77 from:

issuing /opt/etc/ipkg-opt update and installing aditional optware packages. Depending upon how you use the slug

to:

issuing /opt/etc/ipkg-opt update and installing aditional Optware packages. Depending upon how you use the slug

Changed line 79 from:

which replace commands provided by openWRT with better ones then you probably want /opt/bin first, otherwise it

to:

which replace commands provided by OpenWRT with better ones then you probably want /opt/bin first, otherwise it

Changed line 90 from:

If you install any packages that include startup scripts then you'll discover that OpenWRT? doesn't call them. To

to:

If you install any packages that include startup scripts then you'll discover that OpenWRT doesn't call them. To

Changed lines 145-146 from:

and then as for other OpenWRT? services you enable it with /etc/init.d/optware enable

to:

and then as for other OpenWRT services you enable it with /etc/init.d/optware enable

May 15, 2008, at 09:30 PM by AdamBaker -- Expand the using optware with openwrt section
Changed line 33 from:

Optware packages use their own ipkg-opt packaging system that is independend on firmware. This also means that

to:

Optware packages use their own ipkg-opt packaging system that is independent of firmware. This also means that

Changed lines 41-42 from:

Allocate at least 2GB for /opt and 512MB for swap.

to:

Allocate at least 2GB for /opt and 512MB for swap (AdamB? - 512MB seems excessive, I stuck to the unslung size of 120MB).

Added lines 57-58:

To ensure partitions are remounted after a reboot you need to add these commands to a startup script, I recommend /etc/init.d/custom-user-startup until new builds supporting /etc/config/fstab are released

Added lines 67-74:

Some optware packages rely on libraries that are optional OpenWRT? packages. Because these come from different repositories they can't be configured as dependencies. Either install the OpenWRT? packages libssp, libpthread and libstdc++ now or be ready to install them if something breaks.

Optware also has a few other assumptions that aren't met by OpenWRT?, it assumes that users called mail and lp exist in the password file so make sure you create them before installing email or printer spooler software. Another assumption is that /etc/services contains a sensible list of ports - I copied the file from another machine.

Changed lines 76-77 from:

issuing /opt/etc/ipkg-opt update and installing aditional optware packages. /etc/profile line should look like

to:

issuing /opt/etc/ipkg-opt update and installing aditional optware packages. Depending upon how you use the slug you may prefer to include /opt/bin either before or after the default path. If you install packages like coreutils which replace commands provided by openWRT with better ones then you probably want /opt/bin first, otherwise it is probably best if it is last. If you put it first you will need to give the full path if you need to use the openWRT version of ipkg /etc/profile line should look like

Changed lines 84-145 from:
to:

or

 export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/opt/bin:/opt/sbin

If you install any packages that include startup scripts then you'll discover that OpenWRT? doesn't call them. To fix this you need to create /etc/init.d/optware that looks like

 #!/bin/sh /etc/rc.common

 START=80

 start() {
         echo "Starting Optware."
         [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware start
         }

 stop() {
         echo "Shutting down Optware."
         [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware stop
        }

and then a file /opt/etc/rc.optware that contains

 #!/bin/sh

 # Start all init scripts in /opt/etc/init.d
 # executing them in numerical order.
 #
 if [ x$1 == xstop ] ; then
         progs="/opt/etc/init.d/K??*"
         rc=stop
 else
         progs="/opt/etc/init.d/S??*"
         rc=start

 fi

 for i in $progs ;do

         # Ignore dangling symlinks (if any).
         [ ! -f "$i" ] && continue

         echo starting $i
         case "$i" in
            *.sh)
                 # Source shell script for speed.
                 (
                         trap - INT QUIT TSTP
                         set $rc
                         . $i
                 )
                 ;;
            *)
                 # No sh extension, so fork subprocess.
                 $i $rc
                 ;;
         esac
 done

and then as for other OpenWRT? services you enable it with /etc/init.d/optware enable

April 27, 2008, at 06:54 PM by axm --
Changed lines 30-31 from:
  • Binary: Mounting is a little off standard, kernel will mount sda1 as ext2 to /mnt/usbdrive. Other partitions can be mounted by creating /etc/fstab and a script (http://www.pug.org/index.php/OpenWRT - Automount for example) that executes it - but does a "sleep 5" (or so) before, so usb wil be available.
to:
  • Binary: Mounting is a little off standard, kernel will mount sda1 as ext2 to /mnt/usbdrive. Other partitions can be mounted by creating /etc/fstab and a script (http://www.pug.org/index.php/OpenWRT - Automount for example) that executes it - but does a "sleep 5" (or so) before, so usb wil be available. I consider this pretty dirty, so replace with a better way, if known.
April 27, 2008, at 06:52 PM by axm -- mounting a bit more than sda1
Changed lines 29-30 from:
  • ipkg.sh is not in the webif/web directory so you have to login to a terminal to update/install packages.
to:
  • ipkg.sh is not in the webif/web directory so you have to login to a terminal to update/install packages.
  • Binary: Mounting is a little off standard, kernel will mount sda1 as ext2 to /mnt/usbdrive. Other partitions can be mounted by creating /etc/fstab and a script (http://www.pug.org/index.php/OpenWRT - Automount for example) that executes it - but does a "sleep 5" (or so) before, so usb wil be available.
January 24, 2008, at 12:37 PM by fcarolo -- formatting
Changed lines 5-6 from:

From the HomePage, "The OpenWrt Kamikaze 7.09 release of firmware is in beta testing. A binary firmware download can be found at http://www.slug-firmware.net. Please report beta testing results to the nslu2-linux mailing list."

to:

From the HomePage, "The OpenWrt Kamikaze 7.09 release of firmware is in beta testing. A binary firmware download can be found at http://www.slug-firmware.net. Please report beta testing results to the nslu2-linux mailing list."

Changed lines 15-16 from:

For assistance, look in the #nslu2-linux (for nslu2-specific installation problems, be aware there will be very few openwrt users in this channel) or #openwrt (for general OpenWrt questions - this is where all the openwrt users hang out) IRC channels on Freenode.

to:

For assistance, look in the #nslu2-linux (for nslu2-specific installation problems, be aware there will be very few openwrt users in this channel) or #openwrt (for general OpenWrt questions - this is where all the openwrt users hang out) IRC channels on Freenode.

Changed lines 33-34 from:

with OpenWrt upgrade package list is not erased as it is stored in /opt partition where also all optware packages are installed.

to:

with OpenWrt upgrade package list is not erased as it is stored in /opt partition where also all optware packages are installed.

Changed lines 70-71 from:
to:

HowTo's for OpenWRT

January 24, 2008, at 02:26 AM by krim --
Changed lines 70-71 from:
to:
January 24, 2008, at 02:25 AM by krim -- Added HowTo\'s
Added lines 70-72:
January 21, 2008, at 03:00 AM by aidtwo --
Changed lines 17-19 from:

A tip flashing the Kamikaze 7.09 binary:

  • DHCP is enabled by default, (this was learned after what appeared several failed attempts to connect to the NSLU2 at IP address of 192.168.1.77 which had been set using the stock Linksys firmware)
to:

A tip flashing the Kamikaze 7.09 binary firmware:

  • DHCP is enabled by default, (this was learned after what appeared several failed attempts to first connect to the NSLU2 at IP address of 192.168.1.77 which had been set using the stock Linksys firmware)
Deleted lines 20-22:
  • http://ftp.osuosl.org/pub/nslu2/releases/OpenWrt-kamikaze-7.09-README.txt
  • An interesting forum post about Kamikaze 7.09 on NSLU2 - http://forum.openwrt.org/viewtopic.php?id=13034
  • Readme Notes - http://ftp.osuosl.org/pub/nslu2/releases/OpenWrt-kamikaze-7.09-README.txt
Changed lines 22-24 from:
to:
  • Readme Notes - http://ftp.osuosl.org/pub/nslu2/releases/OpenWrt-kamikaze-7.09-README.txt
  • An interesting forum post about Kamikaze 7.09 on NSLU2 - http://forum.openwrt.org/viewtopic.php?id=13034
January 21, 2008, at 02:57 AM by aidtwo --
Changed lines 13-14 from:

Here is the BootLog.

to:

Here is the BootLog (Kamikaze 7.06).

Changed line 20 from:

Other notes and references for Openwrt/NSLU2 Kamikaze 7.09

to:

Other notes and references for Openwrt/NSLU2 Kamikaze 7.09:

January 21, 2008, at 02:55 AM by aidtwo --
Added lines 5-6:

From the HomePage, "The OpenWrt Kamikaze 7.09 release of firmware is in beta testing. A binary firmware download can be found at http://www.slug-firmware.net. Please report beta testing results to the nslu2-linux mailing list."

Added lines 17-25:

A tip flashing the Kamikaze 7.09 binary:

  • DHCP is enabled by default, (this was learned after what appeared several failed attempts to connect to the NSLU2 at IP address of 192.168.1.77 which had been set using the stock Linksys firmware)

Other notes and references for Openwrt/NSLU2 Kamikaze 7.09

  • http://ftp.osuosl.org/pub/nslu2/releases/OpenWrt-kamikaze-7.09-README.txt
  • An interesting forum post about Kamikaze 7.09 on NSLU2 - http://forum.openwrt.org/viewtopic.php?id=13034
  • Readme Notes - http://ftp.osuosl.org/pub/nslu2/releases/OpenWrt-kamikaze-7.09-README.txt
  • ReleaseNotes7x09
Changed line 27 from:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building.
to:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building. (true for pre-7.09 releases only?)
December 24, 2007, at 04:14 AM by rwhitby --
Changed lines 13-14 from:

For assistance, look for rwhitby in the #nslu2-linux or #openwrt-devel IRC channels on Freenode.

to:

For assistance, look in the #nslu2-linux (for nslu2-specific installation problems, be aware there will be very few openwrt users in this channel) or #openwrt (for general OpenWrt questions - this is where all the openwrt users hang out) IRC channels on Freenode.

November 04, 2007, at 03:43 AM by Mr Street -- added mount target
Changed line 43 from:

root@OpenWrt:/# mount /dev/sda1

to:

root@OpenWrt:/# mount /dev/sda1 /opt/

October 17, 2007, at 07:34 PM by fcarolo -- formatted some links, typo
Changed lines 32-33 from:

Prepare partitions

to:

Prepare partitions:

Changed lines 39-41 from:

Mount partitions

to:

Mount partitions:

Changed line 46 from:

For initial instalation of optware package we need to install ipkg-opt package using /usr/bin/ipkg. This can be done

to:

For initial installation of Optware package we need to install ipkg-opt package using /usr/bin/ipkg. This can be done

Changed lines 52-53 from:

This will install required /opt/bin/ipkg-opt. I recommend removing optware package feeed from /etc/ipkg.conf and add the same line to /opt/etc/ipkg.conf.

to:

This will install required /opt/bin/ipkg-opt. I recommend removing the Optware package feeed from /etc/ipkg.conf and add the same line to /opt/etc/ipkg.conf.

Changed lines 56-59 from:
export PATH=/opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/usr/sbin
to:
 export PATH=/opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/usr/sbin
October 17, 2007, at 07:32 PM by fcarolo -- formatted some links
Changed lines 1-2 from:

OpenWrt Kamikaze supports the NSLU2. See the KnownProblems page for known problems with the Kamikaze 7.07 release.

to:

OpenWrt Kamikaze supports the NSLU2. See the KnownProblems page for known problems with the Kamikaze 7.07 release.

Changed lines 5-10 from:

To build, follow the OpenWrt BuildInstructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 to which you need to telnet to get access for the first time.

There is some good documentation at http://nbd.name/openwrt.html . See also the OpenWrt wiki entry for the NSLU2 at http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/NSLU2 , which contains more information.

to:

To build, follow the OpenWrt BuildInstructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 to which you need to telnet to get access for the first time.

There is some good documentation at http://nbd.name/openwrt.html. See also the OpenWrt wiki entry for the NSLU2 at OpenWrt wiki, which contains more information.

Changed line 21 from:

Adding Optware packages to OpenWRT?

to:

Adding Optware packages to OpenWrt

Changed lines 44-48 from:

by adding src optware http://ipkg.nslu2-linux.org/feeds/optware/openwrt-ixp4xx/cross/unstable to /etc/ipkg.conf using vi editor. Then we proceed with ipkg update and ipkg install ipkg-opt.

to:

by adding

 src optware http://ipkg.nslu2-linux.org/feeds/optware/openwrt-ixp4xx/cross/unstable

to /etc/ipkg.conf using vi editor. Then we proceed with ipkg update and ipkg install ipkg-opt.

October 17, 2007, at 05:14 PM by oleo -- Optware packages for NSLU2 OpenWRT
Changed lines 21-22 from:
to:

Adding Optware packages to OpenWRT?

Optware packages use their own ipkg-opt packaging system that is independend on firmware. This also means that with OpenWrt upgrade package list is not erased as it is stored in /opt partition where also all optware packages are installed.

For USB disk preparation one must first prepare disk partitions with

 ipkg update
ipkg install e2fsprogs cfdisk fdisk swap-utils

Partitioning disk into /opt swap and /home partition can be done with cfdisk /dev/sda or fdisk /dev/sda. Allocate at least 2GB for /opt and 512MB for swap.

Prepare partitions

root@OpenWrt:/# mkswap /dev/sda2
root@OpenWrt:/# mke2fs -j /dev/sda1
root@OpenWrt:/# swapon /dev/sda2
root@OpenWrt:/# mke2fs -j /dev/sda1

Mount partitions

root@OpenWrt:/# mkdir /opt
root@OpenWrt:/# mount /dev/sda1 

For initial instalation of optware package we need to install ipkg-opt package using /usr/bin/ipkg. This can be done by adding src optware http://ipkg.nslu2-linux.org/feeds/optware/openwrt-ixp4xx/cross/unstable to /etc/ipkg.conf using vi editor. Then we proceed with ipkg update and ipkg install ipkg-opt. This will install required /opt/bin/ipkg-opt. I recommend removing optware package feeed from /etc/ipkg.conf and add the same line to /opt/etc/ipkg.conf.

It is recommended that default search path is extended to /opt/bin:/opt/bin:$PATH in /etc/profile before issuing /opt/etc/ipkg-opt update and installing aditional optware packages. /etc/profile line should look like

export PATH=/opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/usr/sbin
October 17, 2007, at 01:45 PM by oleo -- build instructions link
Changed lines 5-6 from:

To build, follow the OpenWrt build instructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

to:

To build, follow the OpenWrt BuildInstructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

October 14, 2007, at 03:46 PM by Ruiqiang Huang --
Changed lines 3-4 from:

You can either build kamikaze or download the kamikaze-7.07 image from www.slug-firmware.net. Installation is the same in both cases.

to:

You can either build kamikaze or download the kamikaze-7.07 image from http://www.slug-firmware.net. Installation is the same in both cases.

September 21, 2007, at 02:31 AM by rwhitby --
Changed lines 7-8 from:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.1 to which you need to telnet to get access for the first time.

to:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.77 to which you need to telnet to get access for the first time.

August 09, 2007, at 11:00 AM by attila -- the slug\'s default IP is 192.168.1.77, not 192.168.1.1
Changed line 16 from:
  • By default, the slug uses 192.168.1.1 as the IP address, but you can change that in the network configuration when building.
to:
  • By default, the slug uses 192.168.1.77 as the IP address, but you can change that in the network configuration when building.
July 22, 2007, at 05:36 AM by rwhitby --
Changed lines 1-2 from:

OpenWrt Kamikaze supports the NSLU2.

to:

OpenWrt Kamikaze supports the NSLU2. See the KnownProblems page for known problems with the Kamikaze 7.07 release.

July 21, 2007, at 06:44 PM by drone -- added note on ipkg.sh missing
Changed lines 19-20 from:
to:
  • ipkg.sh is not in the webif/web directory so you have to login to a terminal to update/install packages.
July 21, 2007, at 06:08 AM by rwhitby --
Changed lines 3-4 from:

You can either build kamikaze or download the kamikaze-7.06 image from the OpenWrt download page (use the ixp4xx-2.6 in the kamikaze folder). Installation is the same in both cases.

to:

You can either build kamikaze or download the kamikaze-7.07 image from www.slug-firmware.net. Installation is the same in both cases.

Changed lines 7-8 from:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. As with openslug, it will retain the IP address settings from the firmware you used before. This is not standard behaviour for kamikaze and might be confusing for OpenWrt users (I personally find it very handy though).

to:

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. It will have an IP address of 192.168.1.1 to which you need to telnet to get access for the first time.

Deleted lines 12-15:

To get the full list of packages available (currently 683 of them), change the first line of your /etc/ipkg.conf file to read:

 src unstable http://ipkg.nslu2-linux.org/feeds/openwrt/unstable
Deleted lines 14-18:

If you want to build the Kamikaze-pre1 release, you can use the Master Makefile via "make build-openwrt-kamikaze_7.06". In that case, set your ipkg.conf to read:

 src kamikaze http://ipkg.nslu2-linux.org/feeds/openwrt/kamikaze-7.06

If you use this kamikaze_7.06 target, your files are going to be located in releases/openwrt-kamikaze_7.06/, with the image in bin in that directory.

Changed line 16 from:
  • By default, the slug uses dhcp, but you can change that in the network configuration when building.
to:
  • By default, the slug uses 192.168.1.1 as the IP address, but you can change that in the network configuration when building.
Changed lines 19-21 from:
  • You'll probably want to use a USB storage device. This means ipkg installing kmod-usb2, kmod-usb-storage, and then also kmod-fs-<whatever file system your usb device uses>
to:
June 26, 2007, at 02:03 PM by unverbraucht -- Added info on the wait period after installation and linked to OpenWrt wiki entry
Changed lines 3-6 from:

Follow the OpenWrt build instructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

There is some good documentation at http://nbd.name/openwrt.html

to:

You can either build kamikaze or download the kamikaze-7.06 image from the OpenWrt download page (use the ixp4xx-2.6 in the kamikaze folder). Installation is the same in both cases.

To build, follow the OpenWrt build instructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

After installation, OpenWrt will take a few minutes to initialize the JFFS2 partition. It took about five minutes for me. You should wait at least ten minutes before rebooting. As with openslug, it will retain the IP address settings from the firmware you used before. This is not standard behaviour for kamikaze and might be confusing for OpenWrt users (I personally find it very handy though).

There is some good documentation at http://nbd.name/openwrt.html . See also the OpenWrt wiki entry for the NSLU2 at http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/NSLU2 , which contains more information.

June 03, 2007, at 09:27 AM by rwhitby --
Added lines 5-6:

There is some good documentation at http://nbd.name/openwrt.html

June 01, 2007, at 01:15 PM by rwhitby --
Changed lines 13-17 from:

If you want to build the Kamikaze-pre1 release, you can use the Master Makefile via "make build-openwrt-kamikaze_pre1". In that case, set your ipkg.conf to read:

 src kamikaze-pre1 http://ipkg.nslu2-linux.org/feeds/openwrt/kamikaze-pre1

If you use this kamikaze_pre1 target, your files are going to be located in releases/openwrt-kamikaze_pre1/, with the image in bin in that directory.

to:

If you want to build the Kamikaze-pre1 release, you can use the Master Makefile via "make build-openwrt-kamikaze_7.06". In that case, set your ipkg.conf to read:

 src kamikaze http://ipkg.nslu2-linux.org/feeds/openwrt/kamikaze-7.06

If you use this kamikaze_7.06 target, your files are going to be located in releases/openwrt-kamikaze_7.06/, with the image in bin in that directory.

May 30, 2007, at 04:39 AM by rwhitby --
Changed lines 22-24 from:
  • You'll probably want to use a USB device. This means installing kmod-usb*.ipk, and then also kmod-fs-<whatever file system your usb device uses>.ipk
  • I have yet to figure out how to mount my usb hard drive, although I've gotten the slug to detect it at least.
to:
  • You'll probably want to use a USB storage device. This means ipkg installing kmod-usb2, kmod-usb-storage, and then also kmod-fs-<whatever file system your usb device uses>
May 30, 2007, at 04:31 AM by rwhitby --
Changed line 19 from:
  • By default, the slug uses dhcp.
to:
  • By default, the slug uses dhcp, but you can change that in the network configuration when building.
Changed lines 22-24 from:
  • You'll probably want to use a USB device. This means copying (you can use scp) some ipkg files from bin/packages to your slug and then using ipkg install <packages> to install them. Packages I used were kmod-usb*.ipk, and then also kmod-fs-<whatever file system your usb device uses>.ipk
  • I have yet to figure out how to mount my usb hard drive, although I've gotten the slug to detect it at least.
to:
  • You'll probably want to use a USB device. This means installing kmod-usb*.ipk, and then also kmod-fs-<whatever file system your usb device uses>.ipk
  • I have yet to figure out how to mount my usb hard drive, although I've gotten the slug to detect it at least.
May 30, 2007, at 04:25 AM by xitrium -- added some tips
Changed lines 16-17 from:
to:

If you use this kamikaze_pre1 target, your files are going to be located in releases/openwrt-kamikaze_pre1/, with the image in bin in that directory.

Some user tips!

  • By default, the slug uses dhcp.
  • By default, both telnet and ssh are installed, but only telnet is enabled. To enable ssh and disable telnet (a very good choice, security-wise), telnet to the slug and then use the 'passwd' command to change your root password. The rest seems to be automatic.
  • To change the banner that displays when you log in, edit /etc/banner
  • You'll probably want to use a USB device. This means copying (you can use scp) some ipkg files from bin/packages to your slug and then using ipkg install <packages> to install them. Packages I used were kmod-usb*.ipk, and then also kmod-fs-<whatever file system your usb device uses>.ipk
  • I have yet to figure out how to mount my usb hard drive, although I've gotten the slug to detect it at least.
May 30, 2007, at 02:12 AM by rwhitby --
Changed lines 3-4 from:

Follow the OpenWrt build instructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way.

to:

Follow the OpenWrt build instructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way. You can also use the "make openwrt-image" target in the Master Makefile.

Changed lines 9-11 from:
 src snapshots http://ipkg.nslu2-linux.org/feeds/openwrt/snapshots/ixp4xx-2.6

For assistance, look for rwhitby in the #nslu2-linux or #openwrt-devel IRC channels on Freenode.

to:
 src unstable http://ipkg.nslu2-linux.org/feeds/openwrt/unstable

For assistance, look for rwhitby in the #nslu2-linux or #openwrt-devel IRC channels on Freenode.

If you want to build the Kamikaze-pre1 release, you can use the Master Makefile via "make build-openwrt-kamikaze_pre1". In that case, set your ipkg.conf to read:

 src kamikaze-pre1 http://ipkg.nslu2-linux.org/feeds/openwrt/kamikaze-pre1
May 27, 2007, at 11:57 AM by rwhitby --
Changed lines 3-4 from:

Follow the OpenWrt build instructions for the Intel XScale? IXP4xx? [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way.

to:

Follow the OpenWrt build instructions for the Intel XScale IXP4xx [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way.

May 27, 2007, at 09:48 AM by rwhitby --
Changed lines 7-8 from:

To get the full list of packages available, change the first line of your /etc/ipkg.conf file to read:

to:

To get the full list of packages available (currently 683 of them), change the first line of your /etc/ipkg.conf file to read:

May 27, 2007, at 09:42 AM by rwhitby --
Changed line 11 from:

For assistance, look for #rwhitby in the #nslu2-linux or #openwrt-devel IRC channels on Freenode.

to:

For assistance, look for rwhitby in the #nslu2-linux or #openwrt-devel IRC channels on Freenode.

May 27, 2007, at 09:42 AM by rwhitby --
Added lines 3-4:

Follow the OpenWrt build instructions for the Intel XScale? IXP4xx? [2.6] target system (you can use the "Image configuration" section to set up your initial network configuration), and then flash the openwrt-nslu2-2.6-squashfs.bin 8MB image in the normal way.

Changed lines 11-12 from:
to:

For assistance, look for #rwhitby in the #nslu2-linux or #openwrt-devel IRC channels on Freenode.

May 27, 2007, at 09:39 AM by rwhitby --
Added lines 5-10:

To get the full list of packages available, change the first line of your /etc/ipkg.conf file to read:

 src snapshots http://ipkg.nslu2-linux.org/feeds/openwrt/snapshots/ixp4xx-2.6
May 27, 2007, at 04:13 AM by rwhitby --
Added lines 3-4:

Here is the BootLog.

May 27, 2007, at 04:06 AM by rwhitby --
Added lines 1-2:

OpenWrt Kamikaze supports the NSLU2.

May 27, 2007, at 04:05 AM by rwhitby --
Page last modified on February 01, 2011, at 12:32 AM