pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2000-04-18	re-release 0.15 -- minor typo in a source file	explorer	1	-2/+2

2000-04-18	bump up to 0.15 to implement p{read,write}{,v}	explorer	2	-4/+4

2000-04-14	bump to 0.14 -- handle signals a little better. Bugs are still there, but ↵	explorer	2	-4/+4
	at least they _work_ now.
2000-04-07	bump to 0.13 -- fixes sigaction() brokenness	explorer	2	-4/+4

2000-03-27	bump to 0.12 which fixes a locking bug in dup2()	explorer	5	-30/+9

2000-02-22	add CONFLICTS. installs the same files as mit-pthreads	dmcmahill	1	-1/+2

2000-02-22	patch configure script to correctly recognise netbsd-1.4.* in addition	dmcmahill	3	-0/+26
	to netbsd-1.4[A-Z]
2000-01-27	upgrade to 0.11, and enable on m68k since I've been told it works there, too.	explorer	2	-6/+6

2000-01-18	update to 0.10 to include NetBSD-current's netdb.h, with ipv6 stuff. I	explorer	2	-4/+4
	really need to take the various getXbyY_r() functions and put them in the main source tree, and ditch this file.
2000-01-05	Strip trailing '.', and/or leading '(a\|an) '	abs	1	-1/+1

2000-01-02	replaced some commands by their ${COMMAND} counterparts	wiz	1	-4/+4

1999-12-28	replaced some commands by their ${COMMAND} counterparts	wiz	1	-4/+4

1999-12-11	version 0.9: fixes sendmsg() and recvmsg(), and fixes an errno tracking problem	explorer	2	-4/+4

1999-12-02	up to 0.8 now, whee. bind9 builds without warnings now.	explorer	2	-4/+4

1999-11-24	move to 0.7. This silences some rather annoying errno/sys_errlist noise.	explorer	2	-10/+4

1999-11-12	upgrade to 0.6, which should work on NetBSD-1.4.1/arm32	explorer	4	-9/+10

1999-11-12	Import unproven-pthreads, the mit-pthreads based cleanup I'm hacking on.	explorer	5	-0/+81
	Why am I using MIT-Pthreads? Because all the alternatives seem to have very low level problems. PTL2 has a locking problem of some sort that I cannot track down, and the author insists that lock = PTHREAD_MUTEX_INIT; is always to be legal, so he uses a pointer for locks. This means pthread_lock() can break in out of memory situations, and therefore so can pthread_once(), and if you're using that to protect logging, and you need to report a memory depletion, you're screwed. --Michael