From: Theodore Tso <tytso@mit.edu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Eric Hopper <hopper@omnifarious.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Question about Reiser4
Date: Mon, 23 Apr 2007 21:17:53 -0400 [thread overview]
Message-ID: <20070424011753.GD1663@thunk.org> (raw)
In-Reply-To: <462D4FE1.5040406@zytor.com>
On Mon, Apr 23, 2007 at 05:31:29PM -0700, H. Peter Anvin wrote:
> Heh. sys_read_tree() -- walk a directory tree and return it as a data
> structure in memory :)
But maybe you don't want every single file in the directory, but some
subset of the files in the directory tree. So before you know it:
sys_fs_sql("SELECT port,userid,daemon FROM /etc/inetd.conf.d "
"WHERE protocol=='tcp'", buf, sizeof(buf));
The question is where do you stop on the slippery slope, and is it
really all that harder than simply parsing a /etc/gitconfig or
/etc/e2fsck.conf file. There are plenty of parsers or database
libraries already written, and many of them are quite efficient. And
personally, I'd much rather edit a single /etc/gitconfig or
/etc/e2fsck.conf file using emacs than have to cd through 3 or 4
levels of directories to edit each 2-3 byte file one at a time. But
to each their own....
- Ted
next prev parent reply other threads:[~2007-04-24 1:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 2:00 Question about Reiser4 Eric Hopper
2007-04-23 2:31 ` Lee Revell
2007-04-23 3:56 ` Rik van Riel
2007-04-23 3:56 ` William Heimbigner
2007-04-23 5:47 ` Rik van Riel
2007-04-23 5:57 ` William Heimbigner
2007-04-23 6:07 ` Rik van Riel
2007-04-23 6:14 ` William Heimbigner
2007-04-23 6:20 ` Rik van Riel
2007-04-23 6:42 ` William Heimbigner
2007-04-23 8:04 ` Andrew Morton
2007-04-23 11:31 ` l.genoni
2007-04-23 13:52 ` Eric Hopper
2007-04-23 17:40 ` Andrew Morton
2007-04-23 18:36 ` Miguel Ojeda
2007-04-23 19:05 ` Andi Kleen
2007-04-23 22:56 ` Theodore Tso
2007-04-23 23:53 ` H. Peter Anvin
2007-04-24 0:14 ` Neil Brown
2007-04-24 0:21 ` H. Peter Anvin
2007-04-24 13:30 ` Jan Engelhardt
2007-04-24 0:19 ` Theodore Tso
2007-04-24 0:31 ` H. Peter Anvin
2007-04-24 1:17 ` Theodore Tso [this message]
2007-04-24 11:15 ` Denis Vlasenko
2007-04-25 6:39 ` Eric M. Hopper
2007-04-25 14:45 ` lkml777
2007-04-23 6:14 ` Jeff Chua
[not found] <20070423111939.c876c9cc.akpm@linux-foundation.org>
2007-04-24 14:43 ` Edward Shishkin
2007-04-24 19:39 ` Andi Kleen
2007-04-25 14:35 ` Edward Shishkin
2007-04-25 14:49 ` Jeff Chua
2007-04-25 15:06 ` lkml777
2007-04-25 15:50 ` Jeff Chua
2007-04-26 5:05 ` lkml777
2007-04-26 6:49 ` Jeff Chua
2007-04-26 5:09 ` lkml777
2007-04-26 6:48 ` Jeff Chua
2007-04-26 8:18 ` Jeff Chua
2007-04-27 7:16 ` lkml777
2007-04-26 0:44 ` lkml777
2007-04-25 0:12 ` lkml777
2007-04-25 6:26 ` Eric M. Hopper
2007-04-25 15:03 ` Edward Shishkin
2007-04-26 7:47 ` lkml777
2007-04-26 7:54 ` lkml777
2007-05-02 2:39 ` lkml777
2007-05-02 4:53 ` lkml777
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=20070424011753.GD1663@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=hopper@omnifarious.org \
--cc=hpa@zytor.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.