Make the ls command show the path of each file?

That set of switches doesn't cause the path to be prefixed to the file name, which I want. It also lists paths separately, which I don't want.

Kappy wrote:

Could be you remember a Linux command that doesn't exist in BSD Unix.

That could be. I'd find that option useful when searching for a file on a network drive that Spotlight doesn't index. I could issue the ls command, then run the output through grep to search for whatever part of the file name that I remember. I could do that without the path option, but then all I'd know is the full file name, not where it resides.

A few times I've resorted to dumping the entire directory to a file, then searching the output file so that I can see the previous directory line to identify the location of the file.

I suppose some option of the find command could accomplish this, but I use find so seldom that I can never remember its syntax.

Niel wrote:

That wasn't an ls command at all, but a find variant which works on Mac OS X.

That "find . -type f -print" command does what I want, but I doubt that's what I was trying to recall. As I mentioned in another post, I've never been a find guru. Because of that, it's unlikely that what I remember using would have been the find command.

I'm trying to search directories recursively. The "-d" switch in your suggestion prevents that.

It seems that this command

find /Volumes/that_network_volume

will do what I want. Thanks for the nudge in that direction.

I understand that the find command is very powerful. The types of find command that I might use most commonly are those with the -exec switch. However, "most commonly" in my case means "rarely", so I can never remember the syntax from one use to the next.