From owner-freebsd-chat Wed Jul 17 11:42:19 1996 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA09370 for chat-outgoing; Wed, 17 Jul 1996 11:42:19 -0700 (PDT) Received: from yucca.cs.odu.edu (root@yucca.cs.odu.edu [128.82.4.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA09365 for ; Wed, 17 Jul 1996 11:42:16 -0700 (PDT) Received: from fog.cs.odu.edu (bowden@fog.cs.odu.edu [128.82.4.35]) by yucca.cs.odu.edu (8.7.3/8.6.4) with SMTP id OAA07509; Wed, 17 Jul 1996 14:42:02 -0400 (EDT) Date: Wed, 17 Jul 1996 14:43:54 -0400 (EDT) From: Jamie Bowden To: obrien@cs.ucdavis.edu cc: freebsd-chat@freebsd.org Subject: Re: Opinions? In-Reply-To: <199607171753.KAA05601@kongur> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Jul 1996 obrien@cs.ucdavis.edu wrote: > > Intel, MIPS, DEC Alpha and PowerPC architectures. It is a lot easier > > to administer than a Unix box. It is more secure than OS/2 (certified > > Bull%*&t! [I used to administer an NT and Unix network] Individual Much stuff delted. > entries (one at a time). Takes for ever to read the event log. Installed nt4.0 beta on a machine last night just to have a look. It's Windows NT 97. But the machine, sitting idle, doing nothing was consuming 15.5 megs of RAM. There were no applications running, no icon menus up. The only thing up was th one utility to let me look at rescources. 15.5 meg, idle. X is a bloated pig, but doesn't use that kind of RAM. My biggest problem with NT (and OS/2 suffers from this as well) is the huge amount of overhead necessary to run it. It's pretty though. It might take 2 hours to do one thing on any machine with less than 64 megs of RAM, but boy does it look nice. Jamie I have my finger on the pulse of the planet.