From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: herbert@13thfloor.at
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: consting operations
Date: 12 Jul 2003 01:16:45 +0200 [thread overview]
Message-ID: <shsof00irhe.fsf@charged.uio.no> (raw)
In-Reply-To: <20030711224701.GA31052@www.13thfloor.at>
>>>>> " " == Herbert Pötzl <herbert@13thfloor.at> writes:
> why do you think that filesystem ops should be read only?
What possible reason could there be for making them overwritable?
Sounds like a recipe for disaster...
If you want to layer stuff on top of another filesystem, then surely
you can do that by methods that don't involve overwriting a globally
shared table.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-07-11 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 22:19 consting operations Matthew Wilcox
2003-07-11 22:30 ` Andrew Morton
2003-07-12 3:02 ` Matthew Wilcox
2003-07-11 22:47 ` Herbert Pötzl
2003-07-11 23:16 ` Trond Myklebust [this message]
2003-07-12 12:21 ` Herbert Pötzl
2003-07-14 7:08 ` David Woodhouse
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=shsof00irhe.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=herbert@13thfloor.at \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox