I made a schoolboy error. I ventured down the road named “Thinking your tools are broken instead of your code”. I haven’t done that in years.
My fancy-dancy and super-awesome SheevaPlug has certainly settled in at home.
It exposes my media from my NAS so I can access it anywhere; runs
transmission-daemon headless for all the ISO downloading of open source software I do; runs subversion/svn for my source code versioning needs; cleans the cat when it runs in with…OK, no. Honestly: it’s simply brilliant.
The latter function — subversion — was suffering from a teething problem or two. I run it via ssh login, so I configured
openssh-server to match a group and force running
svnserve as follows:
Match Group svn
ForceCommand /usr/bin/svnserve -t -r /mnt/code/scm/svn/repo/
which allows me to login using ssh users and be super-secure over-the-wire. Great.
I then mounted my NAS share (still on the SheevaPlug) that holds the (yet to be created) svn repo. using the following line in
//192.168.1.90/code /mnt/code smbfs username=alex,password=moo,uid=1002,gid=1002 0 0
I then create a repository and try to commit some code, but am presented with:
Transmitting file data .svn: Commit failed (details follow):
svn: Can't chmod '/mnt/code/scm/svn/repo/atc/db/tempfile.8.tmp': Operation not permitted
Turns out the
uid option in the fstab line was referring to a non-existing user. So I corrected it and added
umask=000 to the fstab line and it was all back up-and-running.
Off to code more bugs.