fortunes(6) typo

2013-04-01 Thread Jason McIntyre
pesky amino acids! ok? jmc Index: fortunes === RCS file: /cvs/src/games/fortune/datfiles/fortunes,v retrieving revision 1.44 diff -u -r1.44 fortunes --- fortunes10 Feb 2013 15:21:28 - 1.44 +++ fortunes 1 Apr 2013

Re: fortunes(6) typo

2013-04-01 Thread Philip Guenther
On Sun, Mar 31, 2013 at 11:49 PM, Jason McIntyre j...@kerhand.co.uk wrote: pesky amino acids! ok? ... The chemical name for tryptophan synthetase A protein, a 1,913-letter enzyme with 267 amino acids. -- Mrs. Byrne's Dictionary of Unusual, Obscure, and Hmm,

remove invalid evergreen ids from radeondrm

2013-04-01 Thread Jonathan Gray
It seems some people were confused about what should be in radeondrm. In CHIP_* terms: HD6320 is PALM HD5450 is CEDAR These are both evergreen/R800 parts we have no support for and should not be listed. Index: radeon_drv.c === RCS

Active PS/2 Multiplexing

2013-04-01 Thread Tobias Stoeckmann
Hi, this issue is already quite old, but let's see if anyone else has still issues with active PS/2 multiplexing. Active PS/2 multiplexing is a method to attach multiple input devices on your AUX PS/2 slot. This should be as of today of no real use anymore, since it's easier to just add a USB

Sendmail 8.14.6 errata

2013-04-01 Thread Jérémie Courrèges-Anglas
Hi, while working on the Sendmail port, I noticed this: https://www.sendmail.com/sm/open_source/download/8.14.6/ I included this patch in my (still WIP) port, but I figured it would be better if it were fixed in base first. Regards, -- Jérémie Courrèges-Anglas GPG Key fingerprint: 61DB D9A0

Re: [NEW] ugold(4) driver for Microdia's USB TEMPer variant

2013-04-01 Thread Luis Coronado
Sasano, your patch applies without problems in -current. This is what I see: uname -a: $ uname -a OpenBSD obsdbox.ticoit.net 5.3 GENERIC.MP#15 amd64 from dmesg: OpenBSD 5.3-current (GENERIC.MP) #15: Mon Apr 1 13:44:48 CST 2013 . . . uhidev3 at uhub4 port 2 configuration 1 interface 0 RDing

sys/socket.h __BSD_VISIBLE

2013-04-01 Thread James Turner
I've come across a piece of software that defines __POSIX_C_SOURCE which causes __BSD_VISIBLE to bet set to 0. In sys/socket.h if __BSD_VISIBLE is 0 sys/_types.h is included instead of sys/types.h. This is fine however in three cases we reference u_int8_t (2) and u_int64_t (1) which requires

Re: sys/socket.h __BSD_VISIBLE

2013-04-01 Thread Ted Unangst
On Mon, Apr 01, 2013 at 22:54, James Turner wrote: I've come across a piece of software that defines __POSIX_C_SOURCE which causes __BSD_VISIBLE to bet set to 0. In sys/socket.h if __BSD_VISIBLE is 0 sys/_types.h is included instead of sys/types.h. This is fine however in three cases we

Re: sys/socket.h __BSD_VISIBLE

2013-04-01 Thread Philip Guenther
On Mon, Apr 1, 2013 at 8:35 PM, Ted Unangst t...@tedunangst.com wrote: On Mon, Apr 01, 2013 at 22:54, James Turner wrote: I've come across a piece of software that defines __POSIX_C_SOURCE which causes __BSD_VISIBLE to bet set to 0. In sys/socket.h if __BSD_VISIBLE is 0 sys/_types.h is

Re: sys/socket.h __BSD_VISIBLE

2013-04-01 Thread Ted Unangst
On Mon, Apr 01, 2013 at 20:40, Philip Guenther wrote: There won't be any side effects from using __uint64_t, but I think of it more like a building block for another type. Not to be used directly. Disagree. Indeed, I just committed James's diff (plus one additional change to CMSG_DATA()).

Re: sys/socket.h __BSD_VISIBLE

2013-04-01 Thread Philip Guenther
On Mon, Apr 1, 2013 at 9:06 PM, Ted Unangst t...@tedunangst.com wrote: My (admittedly weak) rationale is that if a struct contains a field, I would like to be able to declare local variables of the same type as that field. And I don't want my local variables in my code to be using __int