From: Paul Jackson <pj@engr.sgi.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: tmv@comcast.net, jengelh@linux01.gwdg.de, maillist@zuco.org,
linux-kernel@vger.kernel.org
Subject: Re: Squashfs without ./..
Date: Fri, 25 Mar 2005 18:39:25 -0800 [thread overview]
Message-ID: <20050325183925.79359c2e.pj@engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0503241855350.18295@numbat.sonytel.be>
> 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 <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-03-26 2:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 15:47 Jan Engelhardt
2005-03-22 15:59 ` Jesper Juhl
2005-03-23 16:40 ` Pietro Zuco
2005-03-23 17:31 ` Jan Engelhardt
2005-03-23 17:49 ` Tom Vier
2005-03-24 7:01 ` Jan Engelhardt
2005-03-24 17:55 ` Geert Uytterhoeven
2005-03-24 19:36 ` Tommy Reynolds
2005-03-24 19:47 ` Jan Engelhardt
2005-03-24 22:31 ` Andreas Schwab
2005-03-24 19:59 ` H. Peter Anvin
2005-03-24 20:13 ` Kyle Moffett
2005-03-24 20:36 ` H. Peter Anvin
2005-03-25 13:59 ` Jesper Juhl
2005-03-27 4:05 ` Jan Harkes
2005-03-27 9:16 ` Jesper Juhl
2005-03-25 14:39 ` Eric W. Biederman
2005-03-26 3:48 ` Phil Lougher
2005-03-26 3:52 ` H. Peter Anvin
2005-03-26 2:14 ` Phillip Lougher
2005-04-20 4:39 ` Jörn Engel
2005-03-26 10:03 ` Jan Engelhardt
2005-03-27 1:56 ` H. Peter Anvin
2005-03-26 2:39 ` Paul Jackson [this message]
2005-03-27 8:11 Adam J. Richter
2005-03-27 8:51 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050325183925.79359c2e.pj@engr.sgi.com \
--to=pj@engr.sgi.com \
--cc=geert@linux-m68k.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@zuco.org \
--cc=tmv@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®