[Mono-list] SYS_sigaction and NetBSD

[Marc Recht]

--==========1828449384==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

> SYS_sigaction is avalible in NetBSD, but it is not exported to the
> userland (ie. it is used only within the kernel), I hardcoded the value
I know, it's there for the compat stuff. It's now SYS_compat_13_sigaction13 =

or SYS___sigaction14 (which may be covered by COMPAT_16 at some time..).=20
(And, on -current it's also SYS___sigaction_sigtramp...)

> of it into the and it worked, I never got round to fixing it up properly.
Jason R. Thorpe told me in a mail to tech-kern that using sigaction() would =

be "The Right Thing". In fact, he said: "You should not be using the SYS_*=20
system call constants *at all*."

> NetBSD-current now has native pthreads and semephor.h, so a number of the
> changes I still haven't cleaned up and submited are now no-ops for
> NetBSD, does anyone know of another OS without native pthreads and
> semephor.h that its worth applying a patch to use pth and switch semephor
> calls to pthread_mutex's or should I consider this unessasry now (NOTE
> that the native threads will not be in 1.6.x of NetBSD as its been put
> into the non-1.6 branch iirc, so it may be worth patching anyway?). 	-
You're right, the first NetBSD release with native pthreads will be 2.0.

Regards,
Marc

--
"Premature optimization is the root of all evil." -- Donald E. Knuth
--==========1828449384==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE+Mo/J7YQCetAaG3MRAlxJAJ43MrHoQI0+ObIBqz/GfBTBg7ciawCfTzsM
V51NhC1ZhDL3ALW1Aii1NRw=
=5Thn
-----END PGP SIGNATURE-----

--==========1828449384==========--