Re: sha512 program

2013-12-26 Thread Todd C. Miller
On Sun, 22 Dec 2013 19:08:53 -0500, Ted Unangst wrote: > 1. bigger is better. make a link to sha512. > > 2. simplify md5.c. there's really only two modes. OK. program_mode was originally used for more things but now it just for the getopt string and usage. > 3. add a note to sha256.1 about sha

Re: sha512 program

2013-12-26 Thread Todd C. Miller
On Mon, 23 Dec 2013 10:12:23 +0100, =?utf-8?Q?J=C3=A9r=C3=A9mie_Courr=C3=A8ges- Anglas?= wrote: > This should now be: > > static const char *optstr[2] = { > > "bcpqrs:tx", > > - "bcpqrs:tx", > > - "bcpqrs:tx", > > - "a:bco:pqrs:tx", > >

Re: small ssh refinements

2013-12-26 Thread Todd C. Miller
Note that yacc skeleton is a special case since there is no configure goo to rely on. With portable ssh we have configure checks available. - todd

Re: base64 b64_pton fix

2013-12-26 Thread Todd C. Miller
This is nit picking but it bugs me to see the conditional repeated like that. Perhaps instead of: if (nextbyte && tarindex + 1 >= targsize) return (-1); if (tarindex + 1 < targsize) target[tarindex+1] = nextbyte; Something more like: if (tarindex + 1 < targsize) {

Re: Add HISTORY section to locale.1

2013-12-26 Thread Ingo Schwarze
Hi Brian, Brian Callahan wrote on Wed, Dec 25, 2013 at 11:55:43PM -0700: > A user asked me earlier today when our locale(1) appeared. > Do we want to put that in the man page? Definitely. However, i'd suggest to reserve the wording "(first) appeared in" for original inventions in the operating

make async resolver API public

2013-12-26 Thread Eric Faurot
Hi, As suggested by theo@, it is probably time to make the async resolver API public, so that people can start using it. So, here is a diff that does two things (will be committed separately). First, move asr.h to include/ and install the manpages. It only exposes the API that has been in libc

Re: make async resolver API public

2013-12-26 Thread Mark Kettenis
> Date: Thu, 26 Dec 2013 18:02:55 +0100 > From: Eric Faurot > First, move asr.h to include/ and install the manpages. It only > exposes the API that has been in libc for a while now, so there is no > new symbol strictly speaking, but maybe it still deserves a minor bump. Makes no sense to do a

Re: make async resolver API public

2013-12-26 Thread Eric Faurot
On Thu, Dec 26, 2013 at 06:28:33PM +0100, Mark Kettenis wrote: > > Date: Thu, 26 Dec 2013 18:02:55 +0100 > > From: Eric Faurot > > > > +/* > > + * This is the structure through which async_run() returns async > > + * results to the caller. > > + */ > > +struct async_res { > > + int ar_cond;

Re: Add HISTORY section to locale.1

2013-12-26 Thread Brian Callahan
On 12/26/2013 7:59 AM, Ingo Schwarze wrote: Hi Brian, Brian Callahan wrote on Wed, Dec 25, 2013 at 11:55:43PM -0700: A user asked me earlier today when our locale(1) appeared. Do we want to put that in the man page? Definitely. However, i'd suggest to reserve the wording "(first) appeared i

bus_dmamap_sync semantics

2013-12-26 Thread Mark Kettenis
Our bus_dmamap(9) man page says: On platforms which implement reordered stores, bus_dmamap_sync() will always cause the store buffer to be flushed. In 2003 NetBSD actually changed that to: On platforms which implement a weak memory access ordering model, bus_dmamap_sync() will always cau

Re: make async resolver API public

2013-12-26 Thread Mark Kettenis
> Date: Thu, 26 Dec 2013 18:48:06 +0100 > From: Eric Faurot > > On Thu, Dec 26, 2013 at 06:28:33PM +0100, Mark Kettenis wrote: > > > Date: Thu, 26 Dec 2013 18:02:55 +0100 > > > From: Eric Faurot > > > > > > +/* > > > + * This is the structure through which async_run() returns async > > > + * res

Re: Add HISTORY section to locale.1

2013-12-26 Thread Philip Guenther
On Thu, Dec 26, 2013 at 10:14 AM, Brian Callahan wrote: > On 12/26/2013 7:59 AM, Ingo Schwarze wrote: ... >> If anybody knows where this abomination originally came from, >> i'd like to put something like this: > > The earliest mention I can find for locale(1) is in the SUSv2 docs from > 1997. But

Re: bus_dmamap_sync semantics

2013-12-26 Thread Theo de Raadt
> Our bus_dmamap(9) man page says: > > On platforms which implement reordered stores, bus_dmamap_sync() > will always cause the store buffer to be flushed. > > In 2003 NetBSD actually changed that to: > > On platforms which implement a weak memory access ordering model, > bus_dmamap_sync