From: Oleg Drokin <green@namesys.com>
To: Fong Vang <FVang@Zantaz.com>
Cc: "'reiserfs-list@namesys.com'" <reiserfs-list@namesys.com>
Subject: Re: Write-once file system
Date: Fri, 27 Jun 2003 19:46:15 +0400 [thread overview]
Message-ID: <20030627154615.GA13742@namesys.com> (raw)
In-Reply-To: <12C7D768CC8ED4118A9200508BEEC6FB033776C7@zanexch.zantaz.com>
Hello!
On Fri, Jun 27, 2003 at 08:43:06AM -0700, Fong Vang wrote:
> We rely heavily on reiserfs for some of our critical file systems. I'm just
> wondering what work would be involved and how difficult it would be to add
> an option (perhaps at mount time) to reiserfs that will allow a file to be
> written only once, i.e. once a file is created it should not be allowed to
> be modified or deleted (including the inode). We may consider paying for
> this modification.
Is the extended attributes support (man chattr) does what you want by any chance?
Bye,
Oleg
next prev parent reply other threads:[~2003-06-27 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 15:43 Write-once file system Fong Vang
2003-06-27 15:46 ` Oleg Drokin [this message]
2003-06-27 15:48 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-06-27 16:07 Fong Vang
2003-06-27 16:20 ` Oleg Drokin
2003-06-27 17:00 ` Andreas Dilger
2003-06-27 16:07 Fong Vang
2003-06-27 16:53 Fong Vang
2003-06-27 17:09 ` Jason Holt
2003-06-27 18:03 ` Russell Coker
2003-06-27 18:41 ` bscott
2003-06-27 17:07 Fong Vang
2003-06-27 17:27 ` 'Andreas Dilger'
2003-06-27 17:43 ` Oleg Drokin
2003-06-27 17:42 ` Oleg Drokin
2003-06-27 17:21 Fong Vang
2003-06-27 17:37 ` Jason Holt
2003-06-27 18:30 ` Russell Coker
2003-06-27 19:48 ` Jason Holt
[not found] <20030627225410.GK31002@jensbenecke.de>
2003-06-28 3:28 ` Mike Young
2003-06-28 7:45 ` Jason Holt
2003-06-28 9:48 ` Russell Coker
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=20030627154615.GA13742@namesys.com \
--to=green@namesys.com \
--cc=FVang@Zantaz.com \
--cc=reiserfs-list@namesys.com \
/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.