From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 14 Oct 2008 15:22:10 +0300 From: Yaroslav To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <26c1814ccfc8559a96987385a144c4e7@quanstro.net> Subject: Re: [9fans] several things Topicbox-Message-UUID: 1e100522-ead4-11e9-9d60-3106f5b1d025 > But at least it means that the 'pwd' function returns a wrong answer > _without_warning_ when the path is longer. I tried it. This is not a nice > thing. Are these limitations listed in some document? The pwd(1) utility has this limitation for simplicity. The getwd(2) function and fd2path(2) syscall can work on arbitrary-sized buffers. So, to overcome the limit, you have few choices: 1) modify the pwd.c to allocate more memory; or 2) bind not-so-long parts of your path to /n/something to construct a namespace with shorter absolute paths; or 3) blame the tree holders. -- Best regards, Yaroslav.