From owner-freebsd-arch@FreeBSD.ORG Tue Jun 27 00:22:42 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E93016A53F for ; Tue, 27 Jun 2006 00:22:42 +0000 (UTC) (envelope-from andrew@areilly.bpc-users.org) Received: from omta03sl.mx.bigpond.com (omta03sl.mx.bigpond.com [144.140.92.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB25144895 for ; Mon, 26 Jun 2006 23:58:42 +0000 (GMT) (envelope-from andrew@areilly.bpc-users.org) Received: from areilly.bpc-users.org ([141.168.7.22]) by omta03sl.mx.bigpond.com with ESMTP id <20060626235841.CSTR1089.omta03sl.mx.bigpond.com@areilly.bpc-users.org> for ; Mon, 26 Jun 2006 23:58:41 +0000 Received: (qmail 40335 invoked by uid 501); 26 Jun 2006 23:58:45 -0000 Date: Tue, 27 Jun 2006 09:58:45 +1000 From: Andrew Reilly To: Poul-Henning Kamp Message-ID: <20060626235845.GD92989@duncan.reilly.home> References: <20060626.093240.-432837692.imp@bsdimp.com> <52322.1151337322@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52322.1151337322@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i Cc: gurney_j@resnet.uoregon.edu, pjd@freebsd.org, freebsd-arch@freebsd.org Subject: OT: Re: Accessing disks via their serial numbers. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 00:22:42 -0000 On Mon, Jun 26, 2006 at 03:55:22PM +0000, Poul-Henning Kamp wrote: > The reason people have trouble understanding this very basic point is > that UCB strayed from the UNIX philosophy when they added all the socket > system calls instead of adding the /net filesystem. I don't know if anyone's interested, but I started to have a look at Minix-3 the other day. Andrew Tanenbaum is trying to make it grow into a real, useful embedded OS, so now it has a "TCP/IP" network stack (and fully scheduled user-mode device drivers...) The interesting thing is that the TCP/IP stack doesn't provide sockets. It provides /dev/rtk (etc) for raw ethernet drivers, and /dev/ip for raw IP and /dev/tcp for TCP sessions. You open /dev/tcp, do ioctl's to make a connection and then read()/write() to send and receive data. Totally off topic, but kind of interesting, too... Cheers, -- Andrew