From owner-freebsd-current Tue Apr 13 14:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 92C5B14F47 for ; Tue, 13 Apr 1999 14:30:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id OAA17595; Tue, 13 Apr 1999 14:28:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA75294; Tue, 13 Apr 1999 14:28:25 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Date: Tue, 13 Apr 1999 14:28:25 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Thomas Schuerger Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Schuerger wrote: > cvsup is mostly based on disk (and network) I/O, so there shouldn't > be a problem with properly updating the GUI. Someone said it is > done in a separate process, so I still wonder why the GUI is updated > so slowly on my PII/450. Not a separate process -- a separate thread. It uses user-level threads. If the process blocks in a disk I/O call, all threads stop until the call completes. That's just the way Unix works. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message