From: Jeremy Fitzhardinge jeremy@suede.sw.oz.au
Subject: where is 'find'?
Date: Wed, 4 Oct 1995 10:19:01 -0400 [thread overview]
Message-ID: <19951004141901.ggfNxdlJFyRmC5wx1IeD3p0NcxOXk-mH3sKdVoBKZdU@z> (raw)
On Sep 30, 12:30am, Scott Schwartz wrote:
> I hope it doesn't use chdir(), since ".." is unpredictable in Plan 9.
> du avoids that, but has a limit of 256 chars on total path length.
It doesn't use '..', so it is limited to 255 character pathnames.
I would have used fchdir, but it wasn't there.
J
next reply other threads:[~1995-10-04 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-04 14:19 Jeremy [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-08 19:19 stephen
1995-10-08 19:17 stephen
1995-10-04 5:55 ME
1995-09-30 19:46 Martin
1995-09-30 17:27 Jeremy
1995-09-30 15:00 John
1995-09-30 4:30 Scott
1995-09-27 15:26 Steve
1995-09-27 13:06 presotto
1995-09-27 7:11 Kenji
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=19951004141901.ggfNxdlJFyRmC5wx1IeD3p0NcxOXk-mH3sKdVoBKZdU@z \
--to=9fans@9fans.net \
/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).