Sorry - I responded to the wrong email!
Rob
Ok, thanks for the response. I will review your diff and see what I can do.
Original Message
From: Ingo Schwarze
Sent: Sunday, October 9, 2016 2:26 PM
To: Gleydson Soares
Cc: tech@openbsd.org; j...@kerhand.co.uk
Subject: Re: fix uname.3 manpage.
Hi Gleydson,
Gleydson Soares wrote on Sat
On Sat, 8 Oct 2016, Gleydson Soares wrote:
> I stlumbled upon it, while reading uname(1) code.
...
> --- uname.c 24 Dec 2015 15:01:24 - 1.17
> +++ uname.c 9 Oct 2016 18:41:31 -
> @@ -101,7 +101,7 @@ main(int argc, char *argv[])
> print_mask = PRINT_SYSNAME;
> }
Philip Guenther writes:
>
> On Sat, 8 Oct 2016, Gleydson Soares wrote:
> > uname(3) function returns 0 on successful and -1 on failure.
> > "non-negative value" is wrong here.
>
> Hmm, that's a direct quote from the standard. While our implementation
> only returns zero
On Sat, 8 Oct 2016, Gleydson Soares wrote:
> uname(3) function returns 0 on successful and -1 on failure.
> "non-negative value" is wrong here.
Hmm, that's a direct quote from the standard. While our implementation
only returns zero on success, an application which checked for a return
value
Hi Gleydson,
Gleydson Soares wrote on Sat, Oct 08, 2016 at 05:50:00PM -0300:
> uname(3) function returns 0 on successful and -1 on failure.
> "non-negative value" is wrong here.
It is not wrong. When uname(3) succeeds, it does return a non-negative
value, even though that may always be 0
uname(3) function returns 0 on successful and -1 on failure.
"non-negative value" is wrong here.
Index: uname.3
===
RCS file: /cvs/src/lib/libc/gen/uname.3,v
retrieving revision 1.15
diff -u -p -r1.15 uname.3
--- uname.3 21 Jan