Date: Wed, 06 Dec 2000 21:38:06 +0000 From: Brian Somers <brian@Awfulhak.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-arch@FreeBSD.org, brian@Awfulhak.org Subject: Re: Threads in the base system Message-ID: <200012062138.eB6Lc6t07375@hak.lan.Awfulhak.org> In-Reply-To: Message from Robert Watson <rwatson@FreeBSD.org> of "Tue, 05 Dec 2000 22:11:48 EST." <Pine.NEB.3.96L.1001205220943.95872B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Good spot. I believe NOLIBC_R should/must go.
> Recently, pppctl was made thread-enabled, meaning that it relies on
> libc_r. This makes the NOLIBC_R cannot be used with buildworld anymore.
> Given that making pppctl depend on !NOLIBC_R may not be all that helpful,
> it looks like we may need to lose NOLIBC_R. Presumably over time, threads
> in default system applications will only become more popular. Any
> thoughts (especially in light of upcoming KSE changes, which will make
> threading integral to the system architecture)?
>
> Robert N M Watson FreeBSD Core Team, TrustedBSD Project
> robert@fledge.watson.org NAI Labs, Safeport Network Services
--
Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012062138.eB6Lc6t07375>