DragonFly BSD
DragonFly kernel List (threaded) for 2003-09
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cache_lookup() work this week.

To: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
From: Hiten Pandya <hmp@xxxxxxxxxxxxx>
Date: Mon, 08 Sep 2003 20:21:45 +0100

In-Reply-To: <200309081803.h88I3Fs6053054@xxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 34
X-Trace: 1063048971 crater_reader.dragonflybsd.org 267
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:1057

Matthew Dillon wrote:

> :My understanding is that you can't distribute a kernel binary with
> :GPL'd code statically linked into it without GPLing the whole kernel.
> :I think this is why EXT2FS, COMPAT_LINUX, and pcm aren't in FreeBSD's
> :GENERIC kernel.
> :
> : -jre
>     Ah.  That is true, I think you are right.  I'm not sure how significant
>     it is because while linux installs tend to put everyone on one or two
>     slices, BSD installs tend to partition things up more finely so having a
>     mostly read-only UFS / and, say, an ext2fs /usr, would not be a big deal.
>     At the point the gpl'd filesystems can be loaded as a KLD.

	My thoughts exactly.  Once the VFS layer is sorted out, it
	shouldn't be a problem to load the file system modules as
	KLDs later on.  Also, we could write something a pseudo-VFS
	module which can be used to stack a module for a root file
	system; this way, the actual root is a pseudo VFS and there
	is an on-disk file system which sit on top of it.

	This will make it easier for writing root support in file
	systems, and you wouldn't need to modify file systems so
	much for it.


Hiten Pandya

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]