From: Arnd Bergmann <arnd@arndb.de>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: hooanon05@yahoo.co.jp, Jamie Lokier <jamie@shareable.org>,
Phillip Lougher <phillip@lougher.demon.co.uk>,
David Newall <davidn@davidnewall.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@lst.de
Subject: Re: [RFC 0/7] [RFC] cramfs: fake write support
Date: Mon, 2 Jun 2008 19:42:23 +0200 [thread overview]
Message-ID: <200806021942.24750.arnd@arndb.de> (raw)
In-Reply-To: <20080602145404.GA22400@2ka.mipt.ru>
On Monday 02 June 2008, Evgeniy Polyakov wrote:
> > I personally think that a policy other than writing to the top is crazy
> > enough, but randomly writing to multiple places is much worse, as it
> > becomes unpredictable what the file system does, not just unexpected.
>
> Is this a double rot13 encoded "people will never use computers with
> more than 640 kb of ram" phrase? :)
No, it's more the "people don't need variable block size drives" argument.
They've been working fine for decades on mainframes, are incredibly
complicated to build and entirely pointless in practice ;-)
Arnd <><
next prev parent reply other threads:[~2008-06-02 17:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 15:37 [RFC 0/7] [RFC] cramfs: fake write support arnd
2008-05-31 18:56 ` David Newall
2008-05-31 20:40 ` Arnd Bergmann
2008-06-01 3:54 ` Phillip Lougher
2008-06-01 8:52 ` Arnd Bergmann
2008-06-01 12:28 ` Jamie Lokier
2008-06-01 21:49 ` Arnd Bergmann
2008-06-02 2:48 ` hooanon05
2008-06-02 3:25 ` Erez Zadok
2008-06-02 7:51 ` Arnd Bergmann
2008-06-02 18:13 ` Erez Zadok
2008-06-03 2:02 ` Phillip Lougher
2008-06-02 3:51 ` Erez Zadok
2008-06-02 11:07 ` Jamie Lokier
2008-06-02 4:37 ` Erez Zadok
2008-06-02 6:07 ` Bharata B Rao
2008-06-02 7:17 ` Jan Engelhardt
2008-06-02 7:12 ` Arnd Bergmann
2008-06-02 10:36 ` hooanon05
2008-06-02 11:15 ` Arnd Bergmann
2008-06-02 12:56 ` hooanon05
2008-06-02 14:13 ` Arnd Bergmann
2008-06-02 14:33 ` hooanon05
2008-06-02 15:01 ` Arnd Bergmann
2008-06-03 11:04 ` hooanon05
2008-06-02 14:54 ` Evgeniy Polyakov
2008-06-02 17:42 ` Arnd Bergmann [this message]
2008-06-02 15:35 ` Erez Zadok
2008-06-01 6:02 ` David Newall
2008-06-01 9:11 ` Jan Engelhardt
2008-06-01 16:25 ` Jörn Engel
2008-06-01 3:19 ` Phillip Lougher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200806021942.24750.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davidn@davidnewall.com \
--cc=hch@lst.de \
--cc=hooanon05@yahoo.co.jp \
--cc=jamie@shareable.org \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).