mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: Oliver.Soltys@rsel.renesas.com, linux-kernel@vger.kernel.org
Subject: Re: directory sort order no longer beginning with "." and ".."?
Date: Tue, 29 Jul 2008 09:35:32 -0700	[thread overview]
Message-ID: <2c0942db0807290935s67eba63te5bb826a0ab7c752@mail.gmail.com> (raw)
In-Reply-To: <488F2EDA.2090709@goop.org>

On Tue, Jul 29, 2008 at 7:53 AM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Oliver Soltys wrote:
>>
>> My question: is this a bug, or a feature? I could not find anything about
>> that
>> anywhere...
>>
>> Does anybody have an idea, how I can fix this? Unfortunately, our
>> application
>> can not be changed.
>
> No Unix-like system makes any guarantee about the order of '.' and '..' with
> respect to other directory entries.  They've often appeared first as an
> implementation side-effect, but that's highly system and filesystem
> dependent.
>
> If you can't modify the app, you might consider some LD_PRELOAD library to
> replace readdir with something that sorts the results in the order your app
> expects.  There's already examples of that kind of thing to sort the results
> by inode.

That's a good idea, though based on his description it's even easier.
The LD_PRELOAD just needs to artificially introduce . and .., at the
beginning and toss them out once it hits them in the list. No sorting
required.

  reply	other threads:[~2008-07-29 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  9:49 Oliver Soltys
2008-07-29 14:53 ` Jeremy Fitzhardinge
2008-07-29 16:35   ` Ray Lee [this message]
2008-07-29 17:11     ` David Collier-Brown
2008-07-29 17:24       ` Jeremy Fitzhardinge
2008-07-29 17:28     ` Jeremy Fitzhardinge

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=2c0942db0807290935s67eba63te5bb826a0ab7c752@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --cc=Oliver.Soltys@rsel.renesas.com \
    --cc=jeremy@goop.org \
    --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

Powered by JetHome