From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <randolph@tausq.org>
Cc: Joel Soete <jsoe0708@tiscali.be>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] pppd, pthread and hppa-linux question?
Date: Mon, 10 Feb 2003 14:46:50 -0500 [thread overview]
Message-ID: <20030210194650.GG6139@systemhalted> (raw)
In-Reply-To: <20030210161304.GT11363@tausq.org>
On Mon, Feb 10, 2003 at 08:13:04AM -0800, Randolph Chung wrote:
> > All seems to work fine, never the less I notice some pppd messages which
> > I do not noticed on my i386 Debian GNU/Linux box:
> > ...
> > Feb 10 17:34:57 fw01 pppd[1543]: read: Resource temporarily unavailable
> > Feb 10 17:34:57 fw01 pppd[1543]: read /dev/ppp: Resource temporarily unavailable
>
> this probably comes from apps that assume EAGAIN==EWOULDBLOCK. we need
> to probably fix this in glibc.... let's add it to Carlos' todo list! :-)
It's already in my TODO :)
-- snip --
- EWOULDBLOCK emulation
= Is EWOULDBLOCK emulation required?
= What happens if we alias EWOULDBLOCK as EAGAIN
= from the kernel hearders?
- Break HPUX compat?
-- snip --
As JDA notes we still have broken atomic functions in atomicity. Which
we are planning to fix with a light weight syscall.
c.
next prev parent reply other threads:[~2003-02-10 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 16:55 [parisc-linux] pppd, pthread and hppa-linux question? Joel Soete
2003-02-10 16:13 ` Randolph Chung
2003-02-10 17:57 ` Joel Soete
2003-02-10 18:16 ` Joel Soete
2003-02-10 19:46 ` Carlos O'Donell [this message]
2003-02-11 6:30 ` Joel Soete
2003-02-11 19:00 ` Joel Soete
2003-02-10 17:32 ` John David Anglin
2003-02-10 17:42 ` Joel Soete
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=20030210194650.GG6139@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.