From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] EWOULDBLOCK in APE
Date: Fri, 21 Mar 2008 16:19:44 +1100 [thread overview]
Message-ID: <775b8d190803202219t281128a7i50f5902411b2ef06@mail.gmail.com> (raw)
In-Reply-To: <84d462a30803202107n6bc5bcc4n4a36e583d68077c4@mail.gmail.com>
well to be honest i did use up more than my share of wood blocks ...
but my fire was raging. in the early 80s when a thousand new errnos
were introduced it was a cocktail afternoon at basser, and i think it
was andrew taylor who looked at ENAMELON and exclaimed "And A Melon?"
... so i made melon daiquiris.
brucee
On Fri, Mar 21, 2008 at 3:07 PM, Skip Tavakkolian
<skip.tavakkolian@gmail.com> wrote:
> a couple of weeks ago brucee and i were looking for "wood block" on linux :)
>
> here's a little torture: which header file has the errno's on linux?
>
>
> On Thu, Mar 20, 2008 at 12:09 PM, Federico G. Benavento
> <benavento@gmail.com> wrote:
> > > I think it's common on UNIX systems for EWOULDBLOCK to be a synonym for EAGAIN.
> >
> > that's correct, at least acording to my POSIX man pages I have in the
> > posix-man contrib package.
> >
> >
> >
> > --
> > Federico G. Benavento
> >
> >
>
>
>
> --
> Skip Tavakkolian - Founder/President
> 9Netics, Inc.
> 206.463.9600
> Want Secure Remote File Access From Anywhere?
> Visit: http://www.rangboom.com
>
>
next prev parent reply other threads:[~2008-03-21 5:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 18:48 lucio
2008-03-20 19:21 ` ron minnich
2008-03-20 19:23 ` Richard Bilson
2008-03-20 20:09 ` Federico G. Benavento
2008-03-21 4:07 ` Skip Tavakkolian
2008-03-21 5:19 ` Bruce Ellis [this message]
2008-03-21 5:53 ` ron minnich
2008-03-21 13:18 ` Pietro Gagliardi
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=775b8d190803202219t281128a7i50f5902411b2ef06@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=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).