[sleuthkit-users] RE: sleuthkit-users digest, Vol 1 #277 - 2 msgs

[Reava, J. <jef...@pf...>]

Brian Carrier:

I've noticed this is a common problem among several Linux bootable CDs
that feature the sleuthkit. For the ones that do execute sorter
correctly, the workaround seems to be that the authors hard-code the
path statements in the script.

Is it (easily) available to use relative path references in perl, so
that the only relationship that needs to be maintained is that of the
sorter script to its executables?

If it were a windows script, here's how I'd handle it:

sorter.bat
bindir=%0\..\..\bin
..
%bindir%\fls
..

"%0\..\.." in Windows unfortunately is different than the output of
'pwd', since I might be sitting in a temp directory when running sorter.
To work in all situations, the path needs to be relative to the script
directory, not the current directory.

Stumped on this one, mostly for lack of really trying ... 

Jeff

--------------

On Mar 18, 2005, at 4:42 PM, Brian Starr wrote:
> When trying to run the sorter on my image file, I am getting this =20
> error:=A0 Missing Sleuth Kit fls executable: =20
>
/usr/local/src/Packages/sleuthkit-1.61/build-tree/sleuthkit-1.61//bin/=2
0=
> fls. 
> Bootable CD and fls at the command line works totally fine.=A0

It sounds like they moved the sleuth kit directory after compiling it.
=20=