lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 16 Apr 2007 07:19:19 -0400 (EDT)
From:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
To:	Tomasz Kłoczko <kloczek@...y.mif.pg.gda.pl>
cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Mike Snitzer <snitzer@...il.com>, Neil Brown <neilb@...e.de>,
	"David R. Litwin" <presently42@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: ZFS with Linux: An Open Plea

> FUSE implemtation uses too many context switches on each I/O so on the same
> hardware it will never will be so fast as on Linux, BSD and MOX (yes ZFS is
> now avalaible on all this OSes .. and few people says Windows implemtation is
> very close). Current FUSE implemntation can't be comparable in aspects of
> speed and probably never will be on using threads (very simmilar case to ALSA
> and mixing in user space .. in both cases it is broken by design). Also ZFS on
> Solaris uses few other system abilities for example it interract with PSH.
> 
> So FUSE ZFS is IMO only kind of academic demo implemtation only but never will
> be usefull/ready for production (plain waste of time). If Linux licensing will
> not be relaxed probaly we can forget about ZFS on Linux (licensing problems in
> this case are obly on Linux side .. <ironically>in this case ZFS licensing is
> more oppened than Linux licensing </ironically>).
> 
> kloczek
> PS. IIRC implemting ZFS on FUSE was some kind of workaround for licensing
> issue but FUSE fill uses vfs layer and probaly still thinking about
> licensing is actual.

I'm just a lowly proto-hacker trying to get into kernel development, but 
even I know a few things, and I'm getting very tired of hearing FUSE 
slammed as stupid and the Linux licencing policy as foolish. I can sum 
things up in two short passages.

FUSE is intended for end-users, not critical server applications. 
End-users have plenty of processor to spare at lower-than-ever prices. So 
you have a simple and flexible end-user API that lets you do anything with 
anything in any way you want, all the time, without needing to (or even 
needing to be able to) alter your kernel. Win.

Linux licencing basically says, "If you want in on this good thing, you 
have to play by the rules. That means no cheating, no scamming, no 
profiting at the expense of others, and no getting on a high horse and 
proclaiming to the rest of the world that you are in control of their 
destinies. Play nice, kiddies." If you want to do something, you do it 
open and you do it Free, and if you don't want to, well...write your own 
kernel!

There is a wonderful quotation on the GNU site comparing agencies like 
Microsoft to crack dealers: They appear more open in theory in order to 
get people hooked, then trigger the beartrap around your foot. Linux has 
rules--hard, fast, and immutable--and they protect everybody from their 
own stupidities. Open-community development takes a whole lot longer, but 
you don't have to sell your soul to do it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ