Re: kernel vs. pppd
> > glibc will provide a syscall return wrapper to check if it's returning
> > an _old_ EWOULDBLOCK value that needs to be translated to EAGAIN (not
> > sure if this ever happens in our kernel now, perhaps in the future?).
>
> I was under the impression the kernel would not. IIRC, previous
> discussions involving HPUX compatibility suggested the fix go into glibc.
The fix in glibc is a hack, glibc copies the linux kernel headers over
without modification. There are no two separate sources of headers.
> > To fix pppd, you have to rebuild it with a new glibc that changes
> > EWOULDBLOCK to EAGAIN in the headers, and if neccessary change syscalls
> > returning the old EWOULDBLOCK to the new EAGAIN.
>
> I thought patches had been submitted so pppd would accept both.
> I see that it (a) has not and (b) SunOS has EWOULDBLOCK handling
> in it's output() handler (see sys-sunos4.c).
It looks like (a) is true.
I don't see what you want to say about (b)?
c.
Reply to: