From: Ben Ford <ben@kalifornia.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Editing-in-place of a large file
Date: Mon, 03 Sep 2001 14:19:16 -0700 [thread overview]
Message-ID: <3B93F3D4.8020508@kalifornia.com> (raw)
In-Reply-To: <E15drHT-0001TX-00@the-village.bc.nu>
Alan Cox wrote:
>>That is reimplementing file system functionality in user space.
>>I'm in doubts that this is considered good design...
>>
>
>Keeping things out of the kernel is good design. Your block indirections
>are no different to other database formats. Perhaps you think we should
>have fsql_operation() and libdb in kernel 8)
>
From what I've read, that is where windows is going!
-b
--
Number of restrictions placed on "Alice in Wonderland" (public domain)
eBook: 5
Maximum penalty for reading "Alice in Wonderland" aloud (possible DMCA
violation): 5 years jail
Average sentence for commiting Rape: 5 years
next prev parent reply other threads:[~2001-09-03 21:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-02 20:21 Editing-in-place of a large file Bob McElrath
2001-09-02 21:28 ` COW fs (Re: Editing-in-place of a large file) VDA
2001-09-09 14:46 ` John Ripley
2001-09-09 16:30 ` John Ripley
2001-09-09 17:41 ` Xavier Bestel
2001-09-10 1:29 ` John Ripley
2001-09-10 6:45 ` Ragnar Kjørstad
2001-09-14 10:06 ` Pavel Machek
2001-09-10 11:11 ` Ihar Filipau
2001-09-10 16:10 ` Kari Hurtta
2001-09-10 2:43 ` Daniel Phillips
2001-09-10 2:58 ` David Lang
2001-09-10 9:28 ` VDA
2001-09-10 9:35 ` John P. Looney
2001-09-14 10:03 ` Pavel Machek
2001-09-02 21:30 ` Editing-in-place of a large file Ingo Oeser
2001-09-03 0:59 ` Larry McVoy
2001-09-03 1:24 ` Ingo Oeser
2001-09-03 1:31 ` Alan Cox
2001-09-03 1:50 ` Ingo Oeser
2001-09-03 10:48 ` Alan Cox
2001-09-03 14:31 ` Daniel Phillips
2001-09-03 14:46 ` Bob McElrath
2001-09-03 14:54 ` Alan Cox
2001-09-03 15:42 ` Doug McNaught
2001-09-03 15:11 ` Richard Guenther
2001-09-03 21:19 ` Ben Ford [this message]
2001-09-03 4:27 ` Bob McElrath
2001-09-03 1:30 ` Daniel Phillips
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=3B93F3D4.8020508@kalifornia.com \
--to=ben@kalifornia.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.