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: Wed, 29 Dec 2010 18:14:04 +0100 From: Olaf van der Spek <olafvdspek@...il.com> To: Christian Stroetmann <stroetmann@...olinux.com> Cc: linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-ext4 <linux-ext4@...r.kernel.org>, "Ted Ts'o" <tytso@....edu>, Neil Brown <neilb@...e.de>, Nick Piggin <npiggin@...il.com> Subject: Re: Atomic non-durable file write API On Wed, Dec 29, 2010 at 5:30 PM, Christian Stroetmann <stroetmann@...olinux.com> wrote: >> Additional steps compared to what? The temp file, fsync, rename case? > > read the paragraphs as a whole Reading stuff again isn't going to change my question. >>> And the advice to use a well-known DBMS is simply based on the knowledge >>> that it has all the needed functionality already implemented in a highly >>> performant way, and on the knowledge that such a solution is used oftenly >>> for comparable use cases due to the cost vs. benefit ratio. >>> To take a look at the Reiser4 FS could also help. >> >> I don't think storing all my conf files, executables, libraries etc in >> a DBMS is a good idea... > > read the whole both threads started by you again And then what? Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists