Find doesn't work properly

[JoXo009]

Don't know if this is normal behaviour, but I feel the following very annoying:

Opening a root terminal in TC
using "cd /" to change to the root
and typing
find -name "*jwm*"
the terminal only shows
./usr/bin/jwm
./usr/bin/jwm_restart
and so on

but
doesn't show hidden files as
./etc/skel/.jwmc
./home/tc/.jwmc-tray

[Juanito]

That's probably with busybox find ("find --help" will confirm) - you could try the full version of find from the extension of the same name?

[JoXo009]

Yes, help presents
BusyBox v1.13.4

If there is another version, better working, that would be ok for me.

But I only know that version.

Which extension would I need?

Your findutils or your gtkfind?

[curaga]

Findutils would be the one.

[Juanito]

findutils will give the full version of the find command as opposed to the cut down busybox command.

gtkfind (which requires glib1 and gtk1) will give a gui version of the find command

[JoXo009]

Thanks, problem solved.

I installed both.

Typed find into the terminal - same (poor) result.

Typed gtkfind into the terminal - gtkfind GUI opened
- typed "*jwm*" into the Filename line, clicked wildcard
and both normal and hidden files were shown.

Thank you for your quick help.

postscript:
First reboot and than typing find into the terminal
works too and it's the full version then.

So if you don't need a GUI, findutils is enough,
you just need to reboot before first usage.

[Juanito]

Typed find into the terminal - same (poor) result.

Maybe "find --help" will shed some light on this?

[JoXo009]

Maybe "find --help" will shed some light on this?

Unfortunately not, as help underlined that findutils wasn't working.

Result nevertheless corrected, see above postcript.

The explanation didn't mention that findutils needs a reboot before it starts working.

[Jason W]

Findutils, or any extension that installs to /usr/local/bin that replaces busybox utilities that are in /usr/bin, /usr/sbin, /sbin, /bin should not need a reboot.  However, you will usually need to open a new terminal window to start using the executables in /usr/local/bin without specifying the path.  That is unless there is an issue with the findutils extension.

[JoXo009]

you will usually need to open a new terminal window

Good to know.

As well as the fact that there is a replacement process giving code in the folder /usr/local/bin greater priority.

Thanks for the info.

[Juanito]

Good to know.

As well as the fact that there is a replacement process giving code in the folder /usr/local/bin greater priority.

..not exactly a replacement process, the busybox "find" is still there, but /usr/local/bin is ahead of /usr/bin in the default path, so /usr/local/bin/find is found (sic) before /usr/bin/find.

You can display the path using "echo $PATH" and you can see which version of "find" will will run using "which find" .

[^thehatsrule^]

fwiw, it appears to mimick earlier versions

STANDARDS CONFORMANCE
       The  following  options  are  specified in the POSIX standard (IEEE Std
       1003.1, 2003 Edition):
[...]
       -name  This option is supported, but POSIX conformance depends  on  the
              POSIX  conformance  of the system's fnmatch(3) library function.
              As of findutils-4.2.2, shell metacharacters ('*'.  '?'  or  '[]'
              for  example) will match a leading '.', because IEEE PASC inter-
              pretation 126 requires this.   This is a  change  from  previous
              versions of findutils.

So to find these files with the BusyBox version, something like -name .*jwm* could be used