From owner-freebsd-arch Tue Dec 5 19:11:51 2000 From owner-freebsd-arch@FreeBSD.ORG Tue Dec 5 19:11:50 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 78A1E37B400 for ; Tue, 5 Dec 2000 19:11:49 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id eB63Bmf96881 for ; Tue, 5 Dec 2000 22:11:48 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 5 Dec 2000 22:11:48 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-arch@FreeBSD.org Subject: Threads in the base system Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: robert@fledge.watson.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message