| 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
| ||
|
Message-ID: <44C975C4.7040803@namesys.com> Date: Thu, 27 Jul 2006 20:26:12 -0600 From: Hans Reiser <reiser@...esys.com> To: Jeff Garzik <jeff@...zik.org> CC: Pavel Machek <pavel@....cz>, Matthias Andree <matthias.andree@....de>, lkml@...productions.com, Theodore Tso <tytso@....edu>, LKML <linux-kernel@...r.kernel.org>, ReiserFS List <reiserfs-list@...esys.com> Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion Jeff Garzik wrote: > > Actually, there is reiser4 brokenness lurking in Hans' statement, too: Where! Someone tell me!;-) > > A filesystem WITH plugins must still handle the standard Linux > compatibility stuff that other filesystems handle. Hmm, you mean we should first implement regular unix file plugins before implementing enhanced functionality ones? Are you aware that reiser4 plugins are per file, and thus if a user selects a plugin that is not the default, and which has user visible semantic differences, it means they said they want non-standard behavior? > > Plugins --do not-- mean that you can just change the filesystem format > willy-nilly, with zero impact. Yes they do..... > > Jeff > > > > > - 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