[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debian-users:51082] Re: bsah 㧠cd //



> å¶ç„¶ typo ã—ã¦æ°—ã¥ã„ãŸã®ã§ã™ãŒï¼Œbash 㧠cd // ã¨ã™ã‚‹ã¨ï¼Œ
> $PWD ㌠// ã¨ãªã‚Šã¾ã™ï¼Ž
> ã“ã‚Œã¯ç§ã ã‘? ãã†ã„ã†ä»•æ§˜ï¼Ÿ ãƒã‚°ï¼Ÿ
> ã”存知ã®æ–¹ï¼Œå±…られã¾ã™ã§ã—ょã†ã‹ï¼Ÿ
> // ã£ã¦ã©ã‚“ãªä½¿ã„æ–¹ãŒã‚ã‚‹ã‹ç­‰ã‚ã‚Œã°æ•™ãˆã¦é ‚ã‘ã‚‹ã¨å¹¸ã„ã§ã™ï¼Ž
bash ã® source ã® doc/FAQ ã‚‚ã—ãã¯ã€ftp://ftp.cwru.edu/pub/bash/FAQ
ã® E10) ã«ã€

========================================================================
E10) Why does `cd //' leave $PWD as `//'?

POSIX.2, in its description of `cd', says that *three* or more leading
slashes may be replaced with a single slash when canonicalizing the
current working directory.

This is, I presume, for historical compatibility.  Certain versions of
Unix, and early network file systems, used paths of the form
//hostname/path to access `path' on server `hostname'.
========================================================================

ã¨ã‚ã‚Šã¾ã™ã­ã€‚


å‰ç”° 充@横浜ãƒãƒ¼ãƒ .情報基盤センター.ç†åŒ–学研究所 (mitsuru@xxxxxxxxxxxxxxxx)