From: "Jörn Engel" <joern@lazybastard.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: akpm@osdl.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, shaggy@linux.vnet.ibm.com,
dgc@sgi.com, Theodore Tso <tytso@mit.edu>
Subject: Re: [PATCH 0/2] LogFS take two
Date: Wed, 9 May 2007 00:06:45 +0200 [thread overview]
Message-ID: <20070508220642.GF23056@lazybastard.org> (raw)
In-Reply-To: <787b0d920705072253vd9eb7c4o893412d28706c9a6@mail.gmail.com>
On Tue, 8 May 2007 01:53:38 -0400, Albert Cahalan wrote:
>
> You seem to be missing the immutable bit. This is really useful
> for dealing with buggy or badly-designed things running as root.
> I've used to to protect /dev/null from becoming a normal file
> filled with junk, and to protect /etc/resolv.conf from "helpful"
> network management daemons that don't know my DNS servers.
Sounds useful. Onto my todo list. And since the list is slowly getting
too long to be memorized, I've added it to my wiki:
http://logfs.org/logfs/todo
> Anything else missing?
>
> BTW, BSD offers an unprivileged immutable bit as well. I'm sure
> it's useful for the apps that trash their own config files.
> Actually, this bit alone would do fine, and we could really use
> a way to protect writable device files from deletion or permission
> bit changes.
It would be relatively easy to add this as well. The biggest obstacle I
see is getting support in chattr(1). Adding Ted to Cc:, as he is the
maintainer.
What remains to be decided is whether such a flag is a useful addition.
My gut feeling is yes, but I would like to have more than two votes in
favor.
Jörn
--
Fools ignore complexity. Pragmatists suffer it.
Some can avoid it. Geniuses remove it.
-- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982
-
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:[~2007-05-08 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 5:53 [PATCH 0/2] LogFS take two Albert Cahalan
2007-05-08 22:06 ` Jörn Engel [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 21:59 Jörn Engel
2007-05-08 7:39 ` Thomas Gleixner
2007-05-08 11:41 ` Jörn Engel
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=20070508220642.GF23056@lazybastard.org \
--to=joern@lazybastard.org \
--cc=acahalan@gmail.com \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
/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).