- Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors
- From: David Howells <dhowells@xxxxxxxxxx>
- Date: Tue, 08 Mar 2011 15:09:59 +0000
- Cc: dhowells@xxxxxxxxxx, linux-security-module@xxxxxxxxxxxxxxx, keyrings@xxxxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- In-reply-to: <20110307160042.2ddc8e65@xxxxxxxxxxxxxxxxxxx>
- Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
- References: <20110307160042.2ddc8e65@xxxxxxxxxxxxxxxxxxx> <20110307150208.28218.89348.stgit@xxxxxxxxxxxxxxxxxxxxxx> <20110307150218.28218.84916.stgit@xxxxxxxxxxxxxxxxxxxxxx>
Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> 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-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Home]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]