Hi,
First, make sure you either have enough space in the root area or symlink /opt onto your /DataVolume (or another appropriate volume with a fair bit of space)
From http://mybookworld.wikidot.com/sharespace, I followed the following taken from this html page to get ipkg installed:
wget http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/unstable/ipkg-opt_0.99.163-10_arm.ipktar -xOvzf ipkg-opt_*_arm.ipk ./data.tar.gz | tar -C / -xzvf -mkdir -p /opt/etc/ipkgecho "src armel http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/unstable" > /opt/etc/ipkg/armel-feed.conf/opt/bin/ipkg update
After that I did
/opt/bin/ipkg install samba2
(if you do ‘/opt/bin/ipkg list | grep samba’ you’ll see the availabie options). This installs 2.2.12-2 of samba → it also installs several dependencies. The dependencies it pulled in for me are cyrus-sasl-libs, gdbm, libdb, ncurses, openldap-libs, openssl, popt, readline. I’m not sure which of these are required for file sharing vs printer sharing. I did not try installing without dependencies but ipkg does allow for this.
You should end up with your binaries in /opt/sbin - this will have nmbd and smbd. You’ll basically end up with samba install in /opt that mimics what you find off of /. for example, you’ll have /opt/etc/samba (similar to /etc/samba).
FYI, all of this took up 31.6 mb…but I believe it takes up more during the install since the pkg files exist as well…so you need to account for at least double this during the install.
Next I updated /etc/init.d/S90smbd - basically changing occurrences of /usr/sbin/smbd (or nmbd) to /opt/sbin/smbd (or nmbd). I also made a backup copy to s90smbd if I want to change back.
Next I copied /etc/samba/smb.conf to /opt/etc/samba/smb.conf (I would make a back up of the original first). I also touched /opt/etc/samba/smbpassword.
Next run /opt/bin/smbpasswd and add accounts for admin and your other smb users so you can connect. check out smbpasswd --help on how to do this.
Then start it up (/etc/init.d/S90smbd start). FYI, there were errors with reading some of the config parameters…I haven’t dug into those as this worked.
This is obviously very kludgy and not advisable unless you are comfortable mucking with this stuff (and potentially losing your stuff if something doesn’t work right). I’m accepting this risk hoping WD comes out with an updated firmware or at least more appropriate work around steps.
Hope this helps
Paul