| 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
| ||
|
Date: Sun, 13 Apr 2008 04:01:30 -0400 From: Christoph Hellwig <hch@...radead.org> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Bob Copeland <me@...copeland.com>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH 0/7] OMFS filesystem version 3 On Sat, Apr 12, 2008 at 08:55:44PM -0700, Andrew Morton wrote: > > it's a dead filesystem that a very few people still have a reason to > > use. If FUSE is where this should live, then I'll just simply focus my > > time on that instead (since I already have it in FUSE). > > Yes, pursuing the FUSE implementation sounds a better approach - it avoids > burdening the kernel with a filesysstem which few will be interested in and > is more practical for use by those who _are_ interested in it. No way. For a normal foreign block filesystem a proper kernel implementation is much better. And this one is particularly well-written. Lately I really start wondering why we keep adding crap all over the core, but if we have a modular new filesystem that's quite nice people start complaining. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ---end quoted text--- -- 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