Khalid Schofield wrote:
Given the Dev's have answered this one before, and have better things to
do, I shall take it upon myself. I'm sure they will correct me if I'm
mistaken.
The ZFS code is under a license which the OpenBSD team have deemed
incompatible with the BSD License they use. [0]
Whilst there could be a FUSE-based implementation of ZFS on OpenBSD, and
indeed I think one may have already been started, to properly take
advantage of the strength of ZFS the code would have to be in the
kernel. Performance will suck if nothing else.
If its not BSD-licensed code, its not going in the kernel. End of
discussion. Said policy has been a universal truism of OpenBSD since it
began.
I would suggest, if you want XFS in OpenBSD[1], set about persuading Sun
to re-release the ZFS code as BSD-licensed. Indeed, I think given it
would have to be kernel code, I really do mean BSD-licensed rather than
BSD-license-compatible.
And when you do, be sure to remember to buy Satan some mittens.
--
SD
[0] http://marc.info/?l=openbsd-tech&m=110806948606417&w=2
[1] Which I personally would love to see.
| Andrew Morton | -mm merge plans for 2.6.23 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mel Gorman | [PATCH 6/8] x86_64 - Specify amount of kernel memory at boot time |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) |
