[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14977.1299596999@redhat.com>
Date: Tue, 08 Mar 2011 15:09:59 +0000
From: David Howells <dhowells@...hat.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: dhowells@...hat.com, linux-security-module@...r.kernel.org,
keyrings@...ux-nfs.org, linux-arch@...r.kernel.org,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > Define ENONAMESERVICE to indicate "Network name service unavailable".
> > This can be used to indicate, for example, that an attempt was made by
> > dns_query() to make a query, but the name server (e.g. a DNS server) it is
> > supposed to contact didn't answer or that it couldn't determine the
> > location of a suitable server.
>
> Are these in glibc and are there glibc patches submitted and accepted for
> this ?
No.
Are you saying that I should push them through glibc first - and then submit
them to the kernel? Does the kernel lead or the C library? And, if the
latter, which C library? Can I not, for instance, push them through uclibc,
say?
Does submitting to glibc mean I have to sign my copyrights over to the FSF for
that code? I've never gone through this process.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists