You and me both Lobster.
Install goes fine, everything that's mentioned in the man page is there and where it should be, but it seems the 'locate' command just lists the database rather than searching it and providing a filtered output.
Could something be missing or in the wrong directory ?

Thanks for the feedback and sorry. It works fine for me and I tested it many times before uploading it.

However, I will go over everything tonight and see if I can find the problem.

I'll be back.

EDIT - I'm back

I manually uninstalled findutils and reinstalled it using the dotpup in this thread. It worked fine.

Puppy had three files which are not adequate for findutils:

1) sort
2) find
3) xargs

Findutils needs more powerful versions of these files and they are included. Updatedb is a script and has absolute paths to sort and find. For this reason Puppy's sort and find don't get in the way, even though they come earlier in the path statement.

I'm curious of you would do

# which xargs

to see where it is located. It should be in /usr/bin, the size should be 20600.

In any event the paths are extremely important for this utility, because we don't want to run Puppy's same name files which would occur if the updatedb script didn't have absolute paths for find and sort.

Maybe you could try rebuilding the database. A quick way to do it is specify one directory for testing.

this is potentially a very useful set of programs - so thanks for finding and persevering

Did you install the extra progs in the above dot pup that you updated?
The below is (part) of the output I am getting after rebuilding the database . . .
the command was locate vtcl.tcl
and the oupput enclosed is the last part

more or less the same after placing the files in the /usr/bin directory

I also ran the updatedb again to see if that was a problem
I got this - which may mean something wrong with my system (though it relates to leafpad . . .

Code:

/usr/bin/find: WARNING: Hard link count is wrong for /usr/lib: this may be a bug in your filesystem driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched.
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory
/usr/bin/find: /proc/837/fd/4: No such file or directory

Back on topic........
Just downloaded and installed the patch files for Findutils.
From the original install, I learned that nothing worked without a reboot anyway, so I rebooted the system, deleted the old locatedb database file ( the one in /root ) and ran updatedb again.

I got the same strange message that Lobster got ( which I didn't get originally ), but let it run it's course. Generating the initial database takes a minute or 2 so be patient here.

Then tried the 'locate gimp' opening gambit and it worked !
I can now locate files, all sorts of files !

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum