netdev
[Top] [All Lists]

Re: sin6_scope_id

To: pb@xxxxxxxxxxxxxxxxx
Subject: Re: sin6_scope_id
From: Yuji Sekiya <sekiya@xxxxxxx>
Date: Wed, 19 Jan 2000 14:46:35 -0800
Cc: lordbeatnik@xxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: In your message of "Wed, 19 Jan 2000 10:00:41 +0000" <E12Arur-0001m1-00@fountain.labs.futuretv.com>
Organization: Information Sciences Institute
References: <200001140114.RAA31198@ns1.filetron.com> <xmsln5ouy6w.wl@orb.isi.edu> <sekiya@ISI.EDU> <E12Arur-0001m1-00@fountain.labs.futuretv.com>
Sender: owner-netdev@xxxxxxxxxxx
User-agent: Wanderlust/2.2.15 (More Than Words) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (sparc-sun-solaris2.7)
At Wed, 19 Jan 2000 10:00:41 +0000,
Philip Blundell <pb@xxxxxxxxxxxxxxxxx> wrote:

Hello,

> >BTW, in addition to introducing sin6_scope_id into kernel,
> >I think we should intorduce it into glibc functions. It causes not
> >less changes into kernel and glibc.
> >Is there anyone who is a developper of glibc in this mailing list ? 
> 
> Yes.  I agree; it would be fairly futile to introduce sin6_scope_id into the 
> kernel without having matching changes in glibc.

Yoshifuji has made a patch for supporting sin6_scope_id.
It works well with current glibc which has no sin6_scope_id.

The patch can intorduce sin6_scope_id function into kernel
without any problem of existing userland applications.

But, in order to use sin6_scope_id function from userland
application, we have to take a crack at glibc.

I hope that the patch is applied to linux kernel...

-- 
SEKIYA Yuji     USC/ISI  Computer Networks Division 7
<sekiya@xxxxxxx / sekiya@xxxxxxxxxxxxxx / sekiya@xxxxxxxxxxxxxx>

<Prev in Thread] Current Thread [Next in Thread>