public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] ncdu 1.1
Date: Fri, 15 Jun 2007 06:46:00 -0000	[thread overview]
Message-ID: <20070615064627.GS4179@calimero.vinschen.de> (raw)
In-Reply-To: <46722AB4.4030400@t-online.de>

On Jun 15 07:59, Christian Franke wrote:
> DePriest, Jason R. wrote:
> >...
> >Incidentally, I downloaded the source from the
> >http://dev.yorhel.nl/ncdu/ and it compiled flawlessly under Cygwin.
> >
> >I ran it and had it start at the root folder, "/".
> >
> >I anticipated it taking a very long time to finish, but not hours.  I
> >let it run for around four hours during which my processor stayed > 90%
> >usage, even with On-access virus scanning disabled.
> >
> >During which time is dug through all of my mapped network drives, my
> >entire local hard drive, and the Windows registry via /proc/registry.
> >
> >  
> 
> Confirmed.
> Actually ncdu does not handle the special case "/" and calls e.g. 
> lstat("//bin",.).
> This is OK on Linux & friends, but specifies an UNC path on Cygwin.
> (I don't know whether POSIX specifies the behaviour on duplicate slashes).
> ncdu also does not handle the error returned by lstat() in this case.

POSIX allows double slashes having an implementation-defined meaning.
See SUSv3, chapter 4.11 Pathname Resolution:
http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_11
especially the last paragraph.  So NCDU is behaving non-portable in
this case (as a lot of other applications, too, unfortunately).


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

  reply	other threads:[~2007-06-15  6:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 19:05 Christian Franke
2007-06-13  6:03 ` Corinna Vinschen
2007-06-13 16:54   ` Christian Franke
2007-06-13  9:33 ` Dave Korn
2007-06-14 15:38 ` Dr. Volker Zell
2007-06-14 17:30 ` DePriest, Jason R.
2007-06-15  5:59   ` Christian Franke
2007-06-15  6:46     ` Corinna Vinschen [this message]
2007-06-15 17:48     ` DePriest, Jason R.
2007-06-16 19:29       ` Christian Franke
2007-06-17 14:43         ` Christian Franke
2007-06-17 15:01           ` Dave Korn
2007-06-17 17:08             ` Christian Franke
2007-06-18  7:17               ` Corinna Vinschen
2007-06-21  1:41                 ` Eric Blake
2007-06-21  5:24                   ` Christian Franke
2007-06-21  6:53                     ` Corinna Vinschen
2007-06-21 12:06                     ` Eric Blake
2007-06-21 12:23                       ` Dave Korn
2007-06-21 13:15                         ` Eric Blake
2007-06-15 21:17 ` Reini Urban
2007-06-13  6:22 Jörg Schaible
2007-06-13  6:29 ` Corinna Vinschen

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=20070615064627.GS4179@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).