Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!bbn!uwmcsd1!ig!agate!ucbvax!decwrl!hplabs!hpda!hpcuhb!hpihoah!shaker
From: shaker@hpihoah.HP.COM (Chris Shaker)
Newsgroups: comp.os.minix
Subject: Re: Status of V1.3
Message-ID: <4200003@hpihoah.HP.COM>
Date: 13 May 88 23:38:07 GMT
References: <709@ast.cs.vu.nl>
Organization: Hewlett Packard, Cupertino
Lines: 14

> drivers are different.)  The main problem is limited address space--the
> original BSD code was written on Vaxen where you can allocate plenty of
> room to mbufs.  Keith Bostic et al., when they added the Berkeley networking
> code to BSD2.10 (the PDP version of BSD), had to do all sorts of nasty
> mapping segments in and out to get it to run in the PDP's address space
> (roughly like the MINIX system of 64K I, 64K D space for each process).
> You'd almost have to add another system process (like FS and MM) just to
> handle the network.  

What's wrong with adding another system task for networking?  One of the
appealing things about MINIX as contrasted with System V UNIX is the system
task concept.  It is clean, elegant, and powerful.

Chris