From owner-freebsd-chat Thu Jul 15 5:34: 9 1999 Delivered-To: freebsd-chat@freebsd.org Received: from beelzebubba.sysabend.org (beelzebubba.sysabend.org [208.243.107.6]) by hub.freebsd.org (Postfix) with ESMTP id AAA7315569 for ; Thu, 15 Jul 1999 05:34:07 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by beelzebubba.sysabend.org (Postfix, from userid 1004) id 234BC41D3; Thu, 15 Jul 1999 08:34:08 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by beelzebubba.sysabend.org (Postfix) with SMTP id 099D69B3F; Thu, 15 Jul 1999 08:34:08 -0400 (EDT) Date: Thu, 15 Jul 1999 08:34:07 -0400 (EDT) From: Jamie Bowden To: David Schwartz Cc: Doug , Terry Lambert , scrappy@hub.org, beyssac@enst.fr, chat@FreeBSD.ORG Subject: RE: Known MMAP() race conditions ... ? In-Reply-To: <000001bece24$65a5c5e0$021d85d1@youwant.to> Message-ID: X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 14 Jul 1999, David Schwartz wrote: : :> I can give you a list of things from my experience (not a :> webmaster.com employee). Threads, SMP, NFS, and purify. I can't think of :> anything NT does better than any unix though. :) : : Large RAID arrays. 4-way SMP. Applications requiring large numbers of :threads. Log-based system. There's nothing I know of in any UNIX that comes :close to NT's completion ports for efficient network I/O. Irix can do all that, and use different familys and speeds in the same box. Want to mix 200mhz R10k's and 250mhz R12k's in your Origin2k? Go for it. We have a half a terrabyte RAID onsite at NASA LaRC, hanging off an Irix box. That machine has more processors than NT can handle. Oh, and it doesn't go down. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message