linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: yuyichao-mit <yuyichao@mit.edu>
Cc: "richard -rw- weinberger" <richard.weinberger@gmail.com>,
	"Lars Täuber" <taeuber@bbaw.de>,
	linux-kernel@vger.kernel.org,
	linux-c-programming@vger.kernel.org
Subject: Re: extra slash in current path
Date: Thu, 23 Jun 2011 18:31:06 +0400	[thread overview]
Message-ID: <4E034E2A.1010100@msgid.tls.msk.ru> (raw)
In-Reply-To: <BANLkTin9bQ4hzs-odYU-Gxy-f-T+HLLAdQ@mail.gmail.com>

23.06.2011 18:11, yuyichao-mit wrote:

>>>> $ cd //
>>>> $ pwd
>>>> //

The current directory is cached in $PWD environment
variable by shell (bash at least).  This variable is
checked in glibc (getcwd() et al) - if it is set and
stat($PWD) is the same as stat("."), that value is used.

It has nothing to do with kernel, probably the issue
is in bash which somehow allows double slash for root
dir (but not triple).

/mjt

  parent reply	other threads:[~2011-06-23 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 13:14 extra slash in current path yuyichao-mit
2011-06-23 13:17 ` Alessandro Suardi
     [not found]   ` <BANLkTik3iMqZJiEY1+DYS2T9=+q2x2=5pQ@mail.gmail.com>
2011-06-23 13:26     ` yuyichao-mit
     [not found] ` <20110623153116.404f2a63.taeuber@bbaw.de>
     [not found]   ` <BANLkTinOb-4Xm_W2fmzivk6jBJwjeHYKVA@mail.gmail.com>
     [not found]     ` <BANLkTimXH8K91cZ69oPRu=wbYt9JgBadfA@mail.gmail.com>
2011-06-23 14:11       ` yuyichao-mit
2011-06-23 14:25         ` richard -rw- weinberger
2011-06-23 14:27         ` Nick Bowler
2011-06-23 14:31         ` Michael Tokarev [this message]
2011-06-23 14:53           ` yuyichao-mit
     [not found]           ` <20110623165206.d88dcbb3.taeuber@bbaw.de>
     [not found]             ` <BANLkTimdzyT6w2LoKtTjhHTKF5d6zWXFGw@mail.gmail.com>
2011-06-23 15:02               ` 俞颐超

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=4E034E2A.1010100@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=taeuber@bbaw.de \
    --cc=yuyichao@mit.edu \
    /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 NNTP newsgroup(s).