From: Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Squashfs without ./..
Date: Thu, 24 Mar 2005 13:36:28 -0600 [thread overview]
Message-ID: <20050324133628.196a4c41.Tommy.Reynolds@MegaCoder.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0503241855350.18295@numbat.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Uttered Geert Uytterhoeven <geert@linux-m68k.org>, spake thus:
> > There's probably a number of apps that skip the first two dirents, instead
> > of checking for the dot dirs.
>
> Yep, check `-noleaf' in find(1)
Then it is broken in several ways.
First, file systems are not required to implement ".." (only "." is
magical, ".." is a courtesy).
Second, skipping the first two entries carries an implied assumtion
about the file name sorting order that is not portable in a
non-US-ASCII world.
Cheers
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-24 19:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 15:47 Squashfs without ./ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20050324133628.196a4c41.Tommy.Reynolds@MegaCoder.com \
--to=tommy.reynolds@megacoder.com \
--cc=linux-kernel@vger.kernel.org \
/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