> Yep, check `-noleaf' in find(1). No.
At least the copy of find that I just looked at now, in findutils-4.1.20, makes no such assumption that "." and ".." are the first two directory entries. Rather what it does is allow you to suppress an optimization, on file systems that don't manage their directory link counts so that the link count on a directory is exactly two more than the number of child directories, which optimization avoids stat'ing every entry if you are using some set of find options that are only looking at names, not other stat data, and if by the link count on the directory, you've already stat'd all the child directories. The documentation for find -noleaf spells this out. The find command is enabling you to adapt to differing file system directory link counts with this option. It is not brokenly forcing a wrong assumption on you, and in any case, it is an issue of directory link counts, not of the opendir-readdir order of "." and ".." (if present). -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373, 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/