From: Doug McNaught <doug@wireboard.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org, shane@agendacomputing.com
Subject: Re: [PATCH] cramfs is ro only, so honour this in inode->mode
Date: 09 Jan 2001 17:33:29 -0500 [thread overview]
Message-ID: <m3ae90uzie.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <200101092203.f09M3oY327528@saturn.cs.uml.edu>
In-Reply-To: "Albert D. Cahalan"'s message of "Tue, 9 Jan 2001 17:03:50 -0500 (EST)"
"Albert D. Cahalan" <acahalan@cs.uml.edu> writes:
> Doug writes:
> > bash-2.03$ cd /tmp
> > bash-2.03$ cat >foo
> > This is a test.
> > bash-2.03$ chmod u-r foo
>
> No, you zeroed the owner's read bit. When the bit isn't
> implemented it must be always set.
>
> By "(owner may read own files)" I refer to what happens
> after you steal the bit, causing it to always appear set.
Ahh, OK, thanks for the clarification.
-Doug
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 13:17 [PATCH] cramfs is ro only, so honour this in inode->mode Ingo Oeser
2001-01-08 12:13 ` Shane Nay
2001-01-08 14:29 ` Ingo Oeser
2001-01-08 13:17 ` Shane Nay
2001-01-09 11:16 ` Albert D. Cahalan
2001-01-09 14:14 ` Doug McNaught
2001-01-09 22:03 ` Albert D. Cahalan
2001-01-09 22:33 ` Doug McNaught [this message]
2001-01-08 13:42 ` Alexander Viro
2001-01-08 16:59 ` Ingo Oeser
2001-01-08 17:37 ` Linus Torvalds
2001-01-09 1:25 ` Rusty Russell
2001-01-09 2:54 ` Linus Torvalds
2001-01-08 17:12 ` Linus Torvalds
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=m3ae90uzie.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=shane@agendacomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox