TomatoUSB

I am trying to install optware on TomatoUSB on a WNR3500L.
Here is what I did so far:

1. Flash tomato-K26USB-1.28.9050MIPSR2-beta20-Ext.bin (worked)
2. Created EXT3 Partitions 'jffs', 'data' and 'optware' as well as swap partition 'swap' using Ubuntu in VMWare (worked)
3. Created /etc/fstab in nvram that automates the correct mounting (combined with automount enabled).

echo -e "#device Mountpoint FStype Options Dump Pass#
LABEL=swap none swap sw 0 0
LABEL=optware /opt ext3 rw,noatime,nodev 1 1
LABEL=jffs /jffs ext3 rw,noatime,nodev 1 1
LABEL=data /tmp/mnt/data ext3 rw,noatime,nodev 1 1" > /etc/fstab
nvram setfile2nvram /etc/fstab
nvram commit

Source:
http://www.xtremecoders.org/forums/f78/missing-files-linksys-wrtsl54gs-tomato-1-27-vpn-trying-install-optware-9-5-a-232/index3.html

4. Ran the sh script from http://www.dd-wrt.com/wiki/index.php/Optware%2C_the_Right_Way
It download optware but fails when trying to create the startup entry:
Error getting startup value… is this really DD-WRT?

What am I doing wrong? Is there a specific install script for TomatoUSB? If so, where can I find it?

Thanks in advance, Zak

EDIT: http://tomatousb.org/tutorial:optware-installation refers to an older optware installation guide. Is that advice still valid for TomatoUSB?
I also found some Tomato Optware Packages but I would rather have a "plain" optware installation that I can build on.

1. You do not need fstab. Get rid of it. In GUI, on USB and NAS>USB Support under USB Storage Support click Automount.
2. On same web page in Run after mounting put (there are other ways but this is what I use):

if [ -d /mnt/optware ]; then
  mount -o bind /mnt/optware /opt
fi

wget http://wd.mirmana.com/optware-install-ddwrt2.sh  -O - | tr -d '\r' > /tmp/optware-install.sh
sh /tmp/optware-install.sh

jffs is irrelevant to Optware. I don't know if you made it on your external storage but it refers to a flash file system that is created in your router's flash. You create it via the GUI under Administration>JFFS. JFFS is Journalling Flash File System.

DD-WRT scripts based on different nvram settings.

DD-WRT uses rc_

nvram get rc_startup >/dev/null
if [ ! $? -eq 0 ] ; then
  echo "Error getting startup value...  is this really DD-WRT?"
  exit 1
fi

if you write on telnet or Putty

nvram set rc_startup="#"

I don't agree with karog,
Partition labeling and fstab is very useful when you have to specify the destination devices for optware or DATA storage.

I did not say to not have labels on your partitions. In fact you should have them. Maybe you are not familiar with tomatousb but using the Automount I mentioned above, the partitions will be mounted with names that are their partition labels. You simply do not need fstab to mount them.

For example, a partition labeled optware will be mounted at /mnt/optware and a partition labeled data will be mounted at /mnt/data (actually /tmp/mnt but /mnt is a link to that).

tomatousb is great for many things. One is the GUI makes many configuration things very easy. Automount is one of them.

And why do you tell him how to get past the error he got with the script he used if you then say "probably nothing will run as it should?" I have used the approach I described with tomatousb and it works quite well.. Others have reported using this method I described for them and how well it worked.

Ok guys, don't fight.
I know what JFFS is and i only added that partition because the DD-WRT format/partitioning guide recommends that. I figured it might have to do with compatibility with non-optware code that was written when JFFS was the prefered way to store stuff ;)

Anyways I followed karog's advice on using the different script and it worked great. I am still using fstab but I'm launching asterisk via Run after mounting

The DD-WRT script installs a whole lot of services and is more like a distribution then an installation guide. Documentation on this seems to be rather hard to find, maybe we should extend the TomatoUSB wiki entry on Optware.

Thanks for you help. Now if only I could find out why Asterisk throws a segmentation fault when I enable the IAX2 module… but thats offtopic here.

Don't know if it is useful, but here is my "ipkg howto" on Tomato USB for Asus RT-N16: http://www.shcherbyna.com/?p=960

Karog,

I was speaking for DD_WRT prep_optware script (http://www.dd-wrt.com/wiki/index.php/Optware%2C_the_Right_Way) mentioned on the post of ZakMcRofl, and NOT the optware-install-ddwrt2.sh which is a complete different approach.

On the first script existing many nvram get queries which fail due to nvram nonexistence environment.
And i told that, even if we cheat the procedure and have a successful installation, the entire installation become broken and not usable.

Now regarding automounting i always prefer to specify manually the mount targets because in our scripts i use more complicated mountings and more than one HDDs.
I feel more safe to do it this way.

Example….

LABEL=swap none swap sw 0 0
LABEL=optware /opt ext3 rw,noatime,nodev 1 1
LABEL=harddisk /tmp/harddisk ext3 rw,noatime,nodev 1 1
LABEL=harddisk2 /tmp/harddisk2 ext3 rw,noatime,nodev 1 1" > /etc/fstab
nvram setfile2nvram /etc/fstab
return

The reason i use this method is to keep the scripts compatible on BOTH tomato and OLEG Firmwares.

BTW, i will study your method and optware-install-ddwrt2.sh script.
Thanks.

No worries mate. I looked at your work when I first got interested in optware. For myself, I prefer the minimalist approach which just installs uClibc and ipkg as Zak stated he was seeking at the end of his edit in the first post. Then you can add whatever else you like. And to be clear, I didn't write the script I referred to above.

À chacun son goût.

That's what I also prefer. But in fact you have to also specify a few conf files and create some dir structure, as it normally does not work without these small details … I automated this in my script (http://www.shcherbyna.com/?p=960)

Basically what I do is set ipkg, ipkg.conf, create dire structure, do ipkg update and install uClibc

New tutorial for Optware installation posted here.