From: Florian Weimer <fw-d32yF4oPJVt0XxTmqZlbVQ@public.gmane.org>
To: Nikos Mavrogiannopoulos <nmav-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: getentropy clarifications
Date: Fri, 31 Mar 2017 13:31:21 +0200 [thread overview]
Message-ID: <87pogxlm2e.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1490791607.28079.8.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> (Nikos Mavrogiannopoulos's message of "Wed, 29 Mar 2017 14:46:47 +0200")
* Nikos Mavrogiannopoulos:
> +In earlier versions of glibc this function was avaible under the
> +.BR <sys/random.h>
> +header.
It's still available in <sys/random.h>, and the declaration there can
still be useful if you want to compile without feature test macros.
In addition, I don't think there ever was a released glibc version
where getentropy was declared in <sys/random.h>, but not in <unistd.h>
(with the relevant feature test macros).
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-03-31 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 12:46 getentropy clarifications Nikos Mavrogiannopoulos
[not found] ` <1490791607.28079.8.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-31 11:31 ` Florian Weimer [this message]
[not found] ` <87pogxlm2e.fsf-ZqZwdwZz9NfTBotR3TxKnbNAH6kLmebB@public.gmane.org>
2017-04-10 12:09 ` Michael Kerrisk (man-pages)
2017-04-10 12:06 ` Michael Kerrisk (man-pages)
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=87pogxlm2e.fsf@mid.deneb.enyo.de \
--to=fw-d32yf4opjvt0xxtmqzlbvq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=nmav-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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.