Xref: utzoo comp.unix.questions:26433 comp.sys.next:8944
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!unisoft!greywolf
From: greywolf@unisoft.UUCP (The Grey Wolf)
Newsgroups: comp.unix.questions,comp.sys.next
Subject: Re: MACH kernel - source become pd?
Keywords: MACH
Message-ID: <3180@unisoft.UUCP>
Date: 23 Oct 90 23:20:35 GMT
References: <450@dill.UUCP> <26980@mimsy.umd.edu> <1369@mtxinu.UUCP>
Reply-To: greywolf@unisoft.UUCP (The Grey Wolf)
Organization: Foo Bar and Grill
Lines: 32

In article <1369@mtxinu.UUCP> shore@mtxinu.com (Melinda Shore) writes:
>In article <26980@mimsy.umd.edu> chris@mimsy.umd.edu (Chris Torek) writes:
>>(Things look good; CMU already gives away Mach
>>for free.  The problem is that you must first show your AT&T source
>>license.)
>
>And NFS and others.  AFS pulls out pretty easily if you don't want
>it or can't get a license, but the ufs filesystem is Sun vnode-based
>and (alas) doesn't come out as cleanly.  Drivers, math libraries,
>debuggers, etc. are also usually under somebody or other's license
>(different companies hold licenses for different platforms -
>representative companies include Sun, DEC, IBM, Prime).

I keep seeing references to the ufs; who technically owns the concepts
behind the original Berkeley FFS?  And couldn't some other schmo just as
easily come up with a scheme for a "Virtual File System" that wouldn't 
infringe upon Sun's vnode filesystem?

I know the original ufs (read: System V file system) is AT&T property,
but why anyone would want to be stuck with 14-byte filenames and u_short
inode numbers is beyond me.

>-- 
>Melinda Shore                                 shore@mtxinu.com
>mt Xinu                              ..!uunet!mtxinu.com!shore


-- 
"This is *not* going to work!"
				"Well, why didn't you say so before?"
"I *did* say so before!"
...!{ucbvax,acad,uunet,amdahl,pyramid}!unisoft!greywolf