From: Boyd Roberts <boyd@noos.fr>
To: "Douglas A. Gwyn" <DAGwyn@null.net>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: fd2path
Date: Thu, 6 Jul 2000 07:57:52 +0100 [thread overview]
Message-ID: <39642DF0.F51183B9@noos.fr> (raw)
In-Reply-To: <395F031A.DCDEE0C@null.net>
Douglas A. Gwyn wrote:
>
> Boyd Roberts wrote:
> > In the last case you could loop on calling malloc until
> > you got the whole thing.
>
> Um, you really think that is a good design?
yeah doug, whatcha gonna do when yer char buf[1024]; just ain't
big enough, huh? upgrade to 5.n BSD?
--
But I doubt if our present system [U.S. Army] will produce such
an individual. They are too: _abrasive_, opinionated, undiplomatic,
nonconformist, and effective.
-- Colonel David H. Hackworth (U.S. Army, Ret.)
next prev parent reply other threads:[~2000-07-06 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-30 13:02 [9fans] fd2path Boyd Roberts
2000-07-03 9:36 ` [9fans] fd2path Douglas A. Gwyn
2000-07-06 6:57 ` Boyd Roberts [this message]
2000-07-06 15:11 ` Douglas A. Gwyn
2000-07-07 1:27 ` Boyd Roberts
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=39642DF0.F51183B9@noos.fr \
--to=boyd@noos.fr \
--cc=9fans@cse.psu.edu \
--cc=DAGwyn@null.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).