From owner-freebsd-hackers Tue May 27 12:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA00617 for hackers-outgoing; Tue, 27 May 1997 12:48:53 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA00612 for ; Tue, 27 May 1997 12:48:47 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id PAA03947; Tue, 27 May 1997 15:48:03 -0400 Date: Tue, 27 May 1997 15:48:01 -0400 (EDT) From: Ben Black To: "Justin T. Gibbs" cc: Christopher Sedore , Ruslan Shevchenko , FreeBSD-Hackers@FreeBSD.ORG Subject: Re: async socket stuff In-Reply-To: <199705271914.NAA04997@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk very true, but it doesn't change the fact that there is little in NT worth trying to put into FreeBSD. for an example of what i think is wrong with *both* systems look at their access control systems. both the full-blown ACLs of NT and the simple permissions of FreeBSD are inferior in most ways to capabilities. anyone want to make a FreeBSD server for VSTa? b3n On Tue, 27 May 1997, Justin T. Gibbs wrote: > >btw, NT is probably the WORST place to look for inspiration. just look > >at their TCP sequence generation algorithm. > > It is up to the farmer to separate the wheat from the chaff. Some of the > programing models in NT are extremely useful. For example, the fact that > almost every object in the system (FDs, sockets, threads, processes, > events, mutexes, critical sections) comes in the form of a handle you can > shove in an array with other handle types and wait on is something I think > would be very usefull to have in FreeBSD. > > >b3n > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > >