DSM-G600, DNS-3xx and NSA-220 Hack Forum

I've added these two to optware. Expect ipk's in optware feeds the next time our autobuilder runs.

findup (part of fslint) produces the following error:

root@dns323:/mnt/HD_a2# findup \( -path "*/mnt/HD_a2/ipkg" \) -prune -o
   write failed: /tmp/sortor89wn: No space left on device

Is it possible to specify a different tmp location when compiling?  If so can you recompile is this tool is always going to fail I guess.  Also, /opt/bin/supprt/rmlint/merge_hardlinks fails because the shebang calls #!/usr/bin/env python and /usr/bin/env doesn't exist.  There is /opt/bin/env though.  Is it possible to change this in the .ipk package?  I haven't scanned the package to see if there are any more scripts with problems yet.
lu

Ok.  I have now tried out both fslint and fdupes.  Fdupes takes over 24 hours to compare approx 80,000 files (number of, not size, also some are large files).  Fslint (findup) takes a few minutes (10-30, not sure as I didn't time it).  fslint scripts (including, but not only, findup) contain several references to /usr/bin/env.  Can you:
replace all references of /usr/bin/env to /opt/bin/env in the scripts in this package?  It will then work with less configuration upon install.  I didn't actually realise that fslint was mostly (all?) scripts - hence my request for it to be compiled.  However, it is still very useful to have it as a package for install/deinstall purposes as well as dependency management.  I am not familiar with all of the inner workings of opt/.ipk packages, but is it possible to include an env variable when installing an opt package?  In order to get it to work on the dns323 I had to:
mkdir /mnt/HD_a2/tmp
export TMPDIR=/mnt/HD_a2/tmp
as well as changing the path to env.
I note your comment that you don't like to write outside of /opt.  Fair enough, so how about mkdir /opt/tmp and export TMPDIR=/opt/tmp when installing the package.  I assume that optware prefers not to modify the profile or fun_plug, otherwise one would not need to export the opt path manually (or via fun_plug/profile etc).
lu

bzhou wrote:

1) It's a Unix/Linux convention to use "#!/usr/bin/env python" so that the script can find the interpreter as long as it's in the PATH.
The /usr/bin/env is assumed to always be there.  I may consider changing the #! line to /opt/bin/python in next rev.

ok.  My dns323 does not have a /usr/bin/env

bzhou wrote:

TMPDIR is an environment variable that one can setup in profile. On most NAS I've seen, there're plenty of space in /tmp and the system should clean /tmp upon reboot.

findup (fslint) fails pretty quickly "write failed: /tmp/sortdc1Z5e: No space left on device" if you don't specify a different tmp via TMPDIR .

bzhou wrote:

Both of these two issues are quite specific to DNS-323 firmware. Remember there are more than a dozen devices that optware supports. If we have a dns-323 specific optware-bootstrap.xsh like other platforms, it makes some sense to do the PATH and TMPDIR setup there. Right now, I just added lines to http://www.nslu2-linux.org/wiki/Optware/Dns323

Ok, I was just making those suggestions so that fslint would work straight on installing the package.

Thanks for providing them.

lu